View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010012 | MMW v4 | Burning / Disc Handling | public | 2012-11-19 16:29 | 2012-12-24 01:22 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Platform | Windows | OS | 8 | OS Version | - |
| Product Version | 4.0 | ||||
| Fixed in Version | 4.1 | ||||
| Summary | 0010012: Can not burn a file to DVD-RW after erasing DVD-RW (regression) | ||||
| Description | This was reproducible on my computer. | ||||
| Steps To Reproduce | 1) Insert a DVD-RW, that is almost full with content written over it. 2) Select Create CD/DVD/BD from Tools from the menu and launch the Disk Creation Wizard. 3) Select Create data CD/DVD/BD and press the next button. 4) Check a box beside Music and press the next button 5) Use defualt settings as they are and uncheck all the songs except one, and press the next button. 6) Use burn setting as default and start burning 7) Then you get "The selected files exceed available disc space. Do you want to span files across multiple discs?" message. 8) If you press "OK", You get the message "The inserted CD/DVD/BD cannot be written on unless it is first erased. Do you want to erase it before it is burned?" 9) If you press the erase disk button, data is erased. 10) But after erasing, "Please insert a disc to be burned..." is shown and you have to cacel this (this is wrong, a user should be able to start burning again) 11) If you I try to burn a file to DVD-RW, you get "Error: No writable drive!" | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1606 | ||||
|
|
I can repro the issue on my ASUS laptop, I can reproduce it just as follows: 1. Burn -> Erase CD/DVD/BD -> Quick Erase 2. After erasing go to Burn -> Burn data CD/DVD/BD -> No writable drive! The "No writable drive!" appears until MediaMonkey is restarted. |
|
|
This is clone of #9999 to track it for regular MM version as the issue exists in there too. |
|
|
Fixed in build 1606. |
|
|
Verified 1615 |
