laserfan Posted March 29, 2009 Posted March 29, 2009 (edited) Attempting to burn a BDMV fileset, I got the subject error which I"ve never seen before (though I'm not sure I've ever tried burning a DL disc on my new Quadcore XP x64 computer before either). What might this error mean? I have another P4 pc with the same drive type, and with *it* the disc burned without the error, no problem. ; //****************************************\\; ImgBurn Version 2.4.2.0 - Log; Saturday, 28 March 2009, 23:11:51; \\****************************************//;;I 22:00:40 ImgBurn Version 2.4.2.0 started!I 22:00:40 Microsoft Windows XP Professional x64 Edition (5.2, Build 3790 : Service Pack 2)I 22:00:40 Total Physical Memory: 8,387,448 KB - Available: 7,458,884 KBI 22:00:42 Initialising SPTI...I 22:00:42 Searching for SCSI / ATAPI devices...I 22:00:42 Found 1 DVD-RW, 1 DVD Edited March 29, 2009 by laserfan
LIGHTNING UK! Posted March 29, 2009 Posted March 29, 2009 What does the actual error box that pops up say? Just CTRL+C when it's on the screen and then paste into your reply.
laserfan Posted March 29, 2009 Author Posted March 29, 2009 Thanks for looking--here's what I get: ---------------------------ImgBurn --------------------------- This image is smaller than the media specified 'Read Compatibility LBA'. Image Sectors: 4102752 Read Compatibility LBA: 623195916 Do you want to write it to multiple layers anyway? --------------------------- Yes No Cancel --------------------------- Any thoughts? I did a search here and found only 3 references to this message (Read Compatibility LBA) but none in this context, so I guess this is very unusual...
LIGHTNING UK! Posted March 29, 2009 Posted March 29, 2009 Looks like your drive is returning bogus info to me. Eject the disc, press f8, insert disc and wait until it says 'ready' before pressing f8 again. Save the log and upload it here for me please.
laserfan Posted March 29, 2009 Author Posted March 29, 2009 Hope this means something to you and can advise, i.e. driver? hardware? If you suspect a hw problem, I could swap with my other PC... I 17:33:17 ImgBurn Version 2.4.2.0 started!I 17:33:17 Microsoft Windows XP Professional x64 Edition (5.2, Build 3790 : Service Pack 2)I 17:33:17 Total Physical Memory: 8,387,448 KB - Available: 7,484,000 KBI 17:33:17 Initialising SPTI...I 17:33:17 Searching for SCSI / ATAPI devices...I 17:33:17 Found 1 DVD-RW, 1 DVD
LIGHTNING UK! Posted March 30, 2009 Posted March 30, 2009 I 17:34:13 [3:0:0] HL-DT-ST BDDVDRW GGC-H20L 1.03 (G:) (ATA)I 17:34:13 CDB: AD 00 00 00 00 00 00 00 08 04 00 00 I 17:34:13 CDB Interpretation: Read Disc Structure - Physical Information I 17:34:13 BUFFER: 08 02 00 00 E1 0F 32 10 00 03 00 00 00 FC FF FF 00 22 D7 FF 00 00 00 4D 4B 4D 00 00 00 00 00 30 30 31 00 40 25 25 37 0C 02 2F 63 02 2F 63 21 23 0D 0E 14 14 02 01 01 10 00 21 23 0D 0E 14 14 02 I 17:34:13 [3:0:0] HL-DT-ST BDDVDRW GGC-H20L 1.03 (G:) (ATA)I 17:34:13 CDB: 52 01 00 00 00 01 00 00 30 00 I 17:34:13 CDB Interpretation: Read Track Information I 17:34:13 BUFFER: 00 22 01 01 00 07 41 01 00 00 00 00 00 00 00 00 00 3F B0 00 00 00 00 10 00 3F B0 00 00 00 00 00 00 00 00 00 25 25 37 0C 02 2F 63 02 2F 63 21 23 Looking at that I'd have to say you've got a dodgy (filter) driver installed. There are lots of values being carried over to the next 'buffer' that shouldn't be there. ImgBurn always zero fills the buffers before sending I/O so that should not happen... but it is here because a driver is messing things up. Your drive says it's returning '00 22' ( = 34) bytes for the 2nd command but your driver must know the 'READ TRACK INFORMATION' command output descriptor is 46 in length (and that's how much ImgBurn asks for), and it's making up the last 12 based on left over junk in its internal buffer rather than using the nice zeroed out buffer that ImgBurn provided it with. This in turn is making ImgBurn think the 'Read Compatibility LBA' is valid (because it's not zero), only the value is totally bogus and hence you're running into this problem.
laserfan Posted March 30, 2009 Author Posted March 30, 2009 ...Looking at that I'd have to say you've got a dodgy (filter) driver installed. There are lots of values being carried over to the next 'buffer' that shouldn't be there. ImgBurn always zero fills the buffers before sending I/O so that should not happen... but it is here because a driver is messing things up. Thanks very much for your analysis LUK--I will post-back once I've found and fixed this!
laserfan Posted March 30, 2009 Author Posted March 30, 2009 Well, I deleted a couple of filter drivers I wasn't sure about, then my drive wasn't recognized at all so I put those back. Then I found something in Device Manager (hidden in DVD/CD-ROM drives) that I have no idea what it was or how it got there: IDAB 63GXUJC SCSI CdRom Device. Deleted that, tried ImgBurn again and this time my GGC-H20L worked ie. I didn't get the LBA error. Here's the comparison w/the above you snipped LUK: I 17:49:14 [3:0:0] HL-DT-ST BDDVDRW GGC-H20L 1.03 (G:) (ATA)I 17:49:14 CDB: AD 00 00 00 00 00 00 00 08 04 00 00 I 17:49:14 CDB Interpretation: Read Disc Structure - Physical Information I 17:49:14 BUFFER: 08 02 00 00 E1 0F 32 10 00 03 00 00 00 FC FF FF 00 22 D7 FF 00 00 00 4D 4B 4D 00 00 00 00 00 30 30 31 00 40 25 25 37 0C 02 2F 63 02 2F 63 21 23 0D 0E 14 14 02 01 01 10 00 21 23 0D 0E 14 14 02 I 17:49:14 [3:0:0] HL-DT-ST BDDVDRW GGC-H20L 1.03 (G:) (ATA) I 17:49:14 CDB: 25 00 00 00 00 00 00 00 00 00 I 17:49:14 CDB Interpretation: Read Capacity I 17:49:14 BUFFER: 00 00 00 00 00 00 08 00 I 17:49:14 [3:0:0] HL-DT-ST BDDVDRW GGC-H20L 1.03 (G:) (ATA) I 17:49:14 CDB: 51 00 00 00 00 00 00 00 20 00 I 17:49:14 CDB Interpretation: Read Disc Information I 17:49:14 BUFFER: 00 20 00 01 01 01 01 20 00 00 00 00 00 00 00 00 00 00 00 00 00 3F B0 00 00 00 00 00 00 00 00 00 I 17:49:14 [3:0:0] HL-DT-ST BDDVDRW GGC-H20L 1.03 (G:) (ATA) I 17:49:14 CDB: 52 01 00 00 00 01 00 00 30 00 I 17:49:14 CDB Interpretation: Read Track Information I 17:49:14 BUFFER: 00 22 01 01 00 07 41 01 00 00 00 00 00 00 00 00 00 3F B0 00 00 00 00 10 00 3F B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The "Read Disc Structure" is the same, but then the "Read Track Info" has zeros--I assume that's good and correct. I dunno whether that bogus drive (which I really am puzzled about--this is a new PC) had anything to do with this, but decided I'd post-back for posterity. Hopefully I'll not see this again. Thanks LUK for providing the direction I needed!
LIGHTNING UK! Posted March 30, 2009 Posted March 30, 2009 Yes, zeroes are good (of course a proper 'valid' number is also good!) That weird drive was probably something from Alcohol / DAEMON Tools - and they're the kind of tools that can mess I/O up due to the problematic SPTD driver.
laserfan Posted March 31, 2009 Author Posted March 31, 2009 Yes, zeroes are good (of course a proper 'valid' number is also good!) That weird drive was probably something from Alcohol / DAEMON Tools - and they're the kind of tools that can mess I/O up due to the problematic SPTD driver.Yes, I did have Daemon Tools installed for a while but ditched not too long ago it in favor of Virtual Clone Drive! Thank you again...maybe that was the cause of my problem! :fingers crossed:
laserfan Posted March 31, 2009 Author Posted March 31, 2009 (edited) Oops duplicate post! Sorry! Edited March 31, 2009 by laserfan
Cynthia Posted March 31, 2009 Posted March 31, 2009 Even if you uninstall Daemon Tolls - the SPTD driver seems to be left behind. Atleast it did on my system.
mmalves Posted March 31, 2009 Posted March 31, 2009 You can use the SPTD installer to uninstall the driver from your system. Even they know it's piece of junk for adding the uninstall option to the installer
laserfan Posted March 31, 2009 Author Posted March 31, 2009 You can use the SPTD installer to uninstall the driver from your system. Even they know it's piece of junk for adding the uninstall option to the installer Thanks mmalves and Cynthia--I will take a look and see if sptd.sys is still on that computer...!
LIGHTNING UK! Posted March 31, 2009 Posted March 31, 2009 A nice way to get rid of leftover junk is to add a 'system' environment variable called 'DEVMGR_SHOW_NONPRESENT_DEVICES' and set the value to 1. Then when you go into Device Manager and select 'Show hidden devices' from the 'View' menu, you'll be able to see a lot more of what's on (and was once on) your machine. 'SPTD' shows up under the 'Non-plug and play drivers' branch and you can enable/disable/uninstall it from there too.
laserfan Posted March 31, 2009 Author Posted March 31, 2009 A nice way to get rid of leftover junk is to add a 'system' environment variable called 'DEVMGR_SHOW_NONPRESENT_DEVICES' and set the value to 1.Yes I know that very valuable trick & have used it for years. I did have sptd.sys driver still in my system folder, and the Install/Uninstall removed it, but there was still a ton of junk left in the Registry for SPTD and DT. Why don't un-installers un-install all the crap they put on one's drive??? Oh well, I think I've eradicated this one. Wonder if it had anything to do with a few odd disk.sys BSODs I've gotten recently too. Well we'll see. Thanks again for all the help.
Recommended Posts