Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Darkfalz

  1. =============================================== Filter Driver Load Order - ImgBurn v2.5.5.0 =============================================== Upper Device Filter: redbook Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: PxHelp20 Lower Device Filter: imapi Filter Name: redbook File Name: C:\WINDOWS\system32\DRIVERS\redbook.sys File Version: 5.1.2600.5512 (xpsp.080413-2108) File Description: Redbook Audio Filter Driver Product Name: Microsoft® Windows® Operating System Product Version: 5.1.2600.5512 Company Name: Microsoft Corporation Copyright: © Microsoft Corporation. All rights reserved. Filter Name: PxHelp20 File Name: C:\WINDOWS\System32\Drivers\PxHelp20.sys File Version: 3.00.43J [] File Description: Px Engine Device Driver for Windows 2000/XP Product Name: PxHelp20 Product Version: [] Company Name: Sonic Solutions Copyright: Copyright © Sonic Solutions Filter Name: imapi File Name: C:\WINDOWS\system32\DRIVERS\imapi.sys File Version: 5.1.2600.5512 (xpsp.080413-2108) File Description: IMAPI Kernel Driver Product Name: Microsoft® Windows® Operating System Product Version: 5.1.2600.5512 Company Name: Microsoft Corporation Copyright: © Microsoft Corporation. All rights reserved.
  2. Having a major problem with ImgBurn It will burn fine, then at a random point through the verify process, it just stops (no read errors or popups). CD drive continues to spin fast, but no LED light - clicking on abort sits on "Waiting for Read Thread (Device)..." but only a hard reboot gets the system back. Can't open explorer as the device is locked, pressing eject button does nothing. Thing is, after a reboot, I can verify against the file and it works fine. This only happens after a burn, never when I do a read/verify by itself. I am cycling the tray after burn. It is frustrating to say the least. If it helps, I am burning CDI (multisession files) onto CD-Rs. Drive is LiteOn DH20A4P with 9P59 firmware. I seem to remember a utility that could forcibly unlock a non-responding device (command line), but I don't remember what it was called... I 02:40:14 ImgBurn Version started! I 02:40:14 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 02:40:14 Total Physical Memory: 2,096,208 KB - Available: 1,730,624 KB I 02:40:14 Initialising SPTI... I 02:40:14 Searching for SCSI / ATAPI devices... I 02:40:14 -> Drive 1 - Info: ATAPI DVD A DH20A4P 9P59 (D:) (ATA) I 02:40:14 Found 1 DVD±RW/RAM! I 02:40:24 Operation Started! I 02:40:24 Source Device: [0:1:0] ATAPI DVD A DH20A4P 9P59 (D:) (ATA) I 02:40:24 Source Media Type: CD-R (Disc ID: 97m24s16f, Sony Corp.) (Speeds: 8x, 16x) I 02:40:24 Image File: C:\Documents and Settings\Michael\My Documents\dol-ud.cdi I 02:40:24 Image File Sectors: 328,918 (MODE2/FORM1/2336) I 02:40:24 Image File Size: 768,352,448 bytes I 02:40:24 Image File Volume Identifier: UNDER_DEFEAT I 02:40:24 Image File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR I 02:40:24 Image File File System(s): ISO9660 I 02:40:24 Read Speed (Data/Audio): MAX / MAX I 02:40:29 Verifying Session 1 of 2... (1 Track, LBA: 0 - 33599) I 02:40:30 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 0 - 33599) I 02:40:52 Verifying Session 2 of 2... (1 Track, LBA: 45000 - 328917) I 02:40:52 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 45000 - 328917) I 02:42:35 Exporting Graph Data... I 02:42:35 Graph Data File: C:\Documents and Settings\Michael\Application Data\ImgBurn\Graph Data Files\ATAPI_DVD_A_DH20A4P_9P59_MONDAY-3-OCTOBER-2011_2-40_AM_97m24s16f.ibg I 02:42:35 Export Successfully Completed! I 02:42:35 Operation Successfully Completed! - Duration: 00:02:11 I 02:42:35 Average Verify Rate: 6,002 KB/s (40.0x) - Maximum Verify Rate: 8,090 KB/s (53.9x) I 02:43:20 Operation Started! I 02:43:20 Source File: C:\Documents and Settings\Michael\My Documents\dol-rrrr.cdi I 02:43:20 Source File Sectors: 357,569 (AUDIO/2352) I 02:43:20 Source File Size: 835,468,416 bytes I 02:43:20 Source File Volume Identifier: RRRR I 02:43:20 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING I 02:43:20 Source File File System(s): ISO9660, Joliet I 02:43:20 Destination Device: [0:1:0] ATAPI DVD A DH20A4P 9P59 (D:) (ATA) I 02:43:20 Destination Media Type: CD-R (Disc ID: 97m24s16f, Sony Corp.) (Speeds: 8x, 16x) I 02:43:20 Destination Media Sectors: 359,847 I 02:43:20 Write Mode: CD I 02:43:20 Write Type: SAO I 02:43:20 Write Speed: MAX I 02:43:20 Lock Volume: Yes I 02:43:20 Test Mode: No I 02:43:20 OPC: No I 02:43:20 BURN-Proof: Enabled I 02:43:20 Write Speed Successfully Set! - Effective: 2,822 KB/s (16x) I 02:43:20 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes I 02:43:20 Filling Buffer... (40 MB) I 02:43:20 Writing LeadIn... I 02:43:39 Writing Session 1 of 2... (1 Track, LBA: 0 - 301) I 02:43:39 Writing Track 1 of 1... (AUDIO/2352, LBA: 0 - 301) I 02:43:39 Synchronising Cache... I 02:43:46 Filling Buffer... (40 MB) I 02:43:46 Writing LeadIn... I 02:43:53 Writing Session 2 of 2... (1 Track, LBA: 11702 - 357568) I 02:43:53 Writing Track 1 of 1... (MODE2/FORM1/2352, LBA: 11702 - 357568) I 02:48:41 Synchronising Cache... I 02:48:44 Exporting Graph Data... I 02:48:44 Graph Data File: C:\Documents and Settings\Michael\Application Data\ImgBurn\Graph Data Files\ATAPI_DVD_A_DH20A4P_9P59_MONDAY-3-OCTOBER-2011_2-43_AM_97m24s16f_MAX.ibg I 02:48:44 Export Successfully Completed! I 02:48:44 Operation Successfully Completed! - Duration: 00:05:23 I 02:48:44 Average Write Rate: 2,710 KB/s (15.7x) - Maximum Write Rate: 2,763 KB/s (16.0x) I 02:48:44 Cycling Tray before Verify... W 02:48:50 Waiting for device to become ready... I 02:49:00 Device Ready! I 02:49:00 Operation Started! I 02:49:00 Source Device: [0:1:0] ATAPI DVD A DH20A4P 9P59 (D:) (ATA) I 02:49:00 Source Media Type: CD-R (Disc ID: 97m24s16f, Sony Corp.) (Speeds: 8x, 16x) I 02:49:00 Source Media Sectors: 357,569 I 02:49:00 Source Media Size: 835,468,416 bytes I 02:49:00 Verify Against Image File: No I 02:49:00 Read Speed (Data/Audio): MAX / MAX I 02:49:00 Verifying Session 1 of 2... (1 Track, LBA: 0 - 301) I 02:49:00 Verifying Track 1 of 1... (AUDIO/2352, LBA: 0 - 301) I 02:49:04 Verifying Session 2 of 2... (1 Track, LBA: 11702 - 357568) I 02:49:04 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 11702 - 357568) I 02:54:39 Abort Request Acknowledged
  3. Naturally that is the first thing I tried, I unticked that and pressed OK, then closed ImgBurn, and it was still there. I even rebooted, but it was still there. So I had to delete it from the registry.
  4. I won't go into how much I despise programs which decide to add context menus to Windows, especially without asking you, but I couldn't find the option to remove this. I deleted it from the registry, but there should still be an option. Am I missing something?
  5. 8x is usually P-CAV, starts at 4x and kicks up to 6x and then 8x at different stages. 16x is true CAV with a linear increase from 4x (I think) to 16x by the end of the DVD.
  6. Hooray for read mode! I will never have to install that system instrusive Alcohol 120% again!
  7. Sounds like you are breaking spec, whether it works or not :}
  8. I read many places files > 2GB are not possible on ISO9660, but doesn't seem a problem for ImgBurn. Then I read this on Wikipedia: So, is this what ImgBurn does? I'll probably only ever be reading the files in Windows (maybe a standalone DivX player if I ever find a decent one) so is it okay or should I maybe switch to UDF? UDF filesystem overhead is huge, which is why I don't use it at the moment, plus Joliet is better supported ATM for devices such as DivX players.
  9. I'm using it to backup regular files, not for making DVD Videos. But I wonder if I might just stop using ISO9660 and Joliet and use just UDF. My only concern is that I would like a cheapo DVD player which can play DVDs full of MPG files (many can, but my current one doesn't) and it may not parse UDF by itself. Other than that I can't think of any reason to use multiple file systems, not like I'm going to using my burned DVDs on Win95 or DOS or something.
  10. If I want to use ISO9660 + Joliet + UDF, it would be nice if I only had to enter a volume label once, instead of three times. I looked through options but there was no option to synchronise them or anything. Have I missed something? If not this would be a good idea as an option for a new version. Obviously ISO has to be in uppercase of the Joliet/UDF one, but that's a simple thing. Thanks.
  11. Woohoo.............. I was going to add "yet" but didn't want to be presumptuous.
  12. ImgBurn does not build ISOs....
  13. Okay. I remember trying with both CDRWin and mkisofs to make an ISO with file over 2GB and failing. Most likely limitations of the software (all my stuff has the 2GB limit also because of VB6 limitation). Anyone know a free (preferably open source) ISO builder with > 2GB support?
  14. Because it's 32bit signed integer. Any greater than 2GB would give a negative number. I would have thought that would be obvious to someone like you.
  15. Nope, ISO9660 only supports a max of 2GB. Unfortunately the majority of UDF building programs are bugged (some support only 1GB max, ie. CDRWin).
  16. Is it planned? I have a huge number of Multi Session images I backed up to DVD-R, was hoping to use ImgBurn to burn them rather than requiring the rather evil Alcohol 120%.
  17. There's no point in burning 1x, if you want the best quality burn, stick to 4x - this is the highest CLV with no speed switches (although I have an older drive, perhaps there are 8x CLV now, or smoother CAV burning rather than the stepping thing that I have).
  18. Neither do I! Which is why Standby is awesome. YOu can leave IE etc. open, and your computer is ready to use after only a few seconds. Power consumption in Standby is something like 10 watts, ie. nothing.
  19. I'd like a selection of things to do with done... maybe rewrite the option so it can do any of three things, close program, enter standby, or turn off computer. I don't know many people who turn off their computer more than once in a while, I almost always use standby.
  20. I don't suggest it as an alternative to "Verify against file", I suggest it as an alternative to the cheap "just see if it can be read" verify. It would take the same amount of time and reading, but it would also verify the data was all correct. Where's the downside?
  21. You need to read the file anyway as you burn it. To calculate a CRC32 or MD5 at the same time is trivial and will barely consume any CPU. Of course, a bad burn will result in a wrong CRC32/MD5 on verify, which will tell you there was an error somewhere but not where it is. That being said, I've never had a bad burn where I could actually read the disc but the data was bad. So it would be the same as comparing to file, just without needing to read the file again on verify. True, you wouldn't know which sectors are mismatched, but the point of verify isn't really to catch errors (a rare occurance) but to give the warm and fuzzy feeling that your burn was successful. What advantage is knowing where the burn went wrong, really? Unless it's a persistant problem. I don't know who would keep a only slighty corrupt burn.
  22. Indeed many of my DVD+RW were "In process" of formatting (even though I'd used them a few times). Now they are all properly formatted. A bit weird behaviour of the drive though, with the LED going off while formatting. So it has three modes Blinking - writing DVD+R On - writing DVD+RW Blinking then off - formatting DVD+RW Weird. But I'm glad now I know what's going on and that my drive works as it should. It's amazing to think so many tiny phase change crystals packed onto one disc, and how many millions are written every second! Sometimes if you think hard enough about it technology blows your mind.
  23. No, because it doesn't require a second pass through the image file on verify. It already read it once while burning, it shouldn't have to read it again while verifying. Once you've burned it, it's nice if you can free up all hard disk activity while verifying (like you can begin creating the next ISO you want to burn).
  24. Okay, it seems this was my fault. It was formatting. It blinks for a few seconds then the light goes out, but it continues formatting without the LED on. Lo and behold 15 minutes later it completed and started to write the file. I was confused all this time because it seems like it just dies. Forgive me.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.