View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003007 | MMW v4 | Burning / Disc Handling | public | 2007-04-17 22:10 | 2008-12-07 16:46 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Fixed in Version | 3.1 | ||||
| Summary | 0003007: Disc fails to refresh in Explorer (XP) after several burns | ||||
| Description | If MM is used to burn a CD (noticed this problem after burning Data CDs and DVDs), then although the CDs/DVDs are burned correctly, neither Windows nor MediaMonkey can show the contents of the disc UNTIL MM is closed! I would like to test this further but don't have time. Try to replicate by burning a couple of DVDs and then a couple of CDs and then try browsing the contents of the burned discs. Note: This may be related to bug 2934 in which MM fails to burn a second CD | ||||
| Additional Information | http://help.lockergnome.com/general/Cdrom-Drive-Won-39-Refresh-Xp-ftopict6968.html | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
| related to | 0002072 | resolved | Ludek | Data Disc Burning: Verify Data functionality (fails for auto-conversion) |
| related to | 0002934 | resolved | Ludek | MediaMonkey often fails to burn > 1 CD |
| related to | 0004180 | closed | Ludek | CD Burning: Improved status bar feedback during + on completion |
| related to | 0002741 | closed | rusty | No writeable drive is reported when burned CD is inserted |
| related to | 0004910 | closed | Ludek | HPCDE Primo: new version 2.5.8 engine should be included |
|
|
I found out a method in hpcde. It is IDevice11::Reset. By using this method the problem seems to be resolved, but I've tested it only 10x times. This method is also useful to reset the device when a writing operation failed (there is no need to reboot system now). So I hope that by adding this method it is resolved, if is not then re-open this issue, please. |
|
|
After some other attempts it still doesn't seem to be resolved :-( |
|
|
This seems to be resolved in via the v2.5 sdk. |
|
|
Verified 1193. |
