LIGHTNING UK!

It wouldn't work like that. Although the options are mutually exclusive, it's also possible to not have either of them checked. With radio buttons, 1 of them always is.

ImgBurn will not help you (nor any members of this forum) with any protection related matters, sorry. Remember these are navigation discs that go into custom built drives / machines. I doubt a) they'd use any form of common protection method. b ) ClonyXXL would detect anything.

Well you said you'd tested all the different programs, not me! That rules out ImgBurn - yeah? You even said you'd burnt it on a MAC! There's nothing for me to fix (or have fixed!) on this, sorry. I never believed it was possible to burn Mode1 data and have something not readable - my own testing with your 'special' file (lol) kinda proves that

Exactly, that's my point. Your drive is not initialising the disc properly and so is reporting utter nonsense to ImgBurn. ImgBurn can only act on what it is told by the drive. So if the drive says it's a DVD+RW disc and it hasn't been formatted, ImgBurn will prompt you to format it.

ImgBurn will erase before it burns if it needs to. You don't need to worry about it.

No sorry, I skipped all the 75x models because I didn't like them. I have now also tested these though... LG-H22L - worked fine. LiteOn LH-18A1H - worked fine. Pioneer 111 - worked fine. BenQ 1655 - worked fine. Optiarc 7173 - worked fine. I hope that's enough testing

As I said, if the disc exceeds 99 mins, it won't work. I guess that the mpg + filesystem etc is just too big for it. If you wanted to burn the mpg as a vcd or whatever, no ImgBurn doesn't do that. If you wanted it as a file that explorer could still see, ImgBurn is fine (except for when you've made the mpg too big!). Build mode is for creating data style Mode 1 ISO's, not Mode 2 VCD/SVCD style ones (which are also multiple track - another thing ImgBurn doesn't do).

Erm if it's a 99minute disc, it doesn't make sense that it would display a warning if you're only trying to burn 99 mins! Unless of course you were like a sector or two over the standard size? Any chance of a screenshot of the 'overburn' messagebox or a copy of the log?

Well those discs are ?250 to buy, no wonder they want to protect them. That's not to say I'm happy about it. I can buy a whole new navigation system for the price I'm forced to pay for a single DVD (ok, 2 DVDs in this latest map).... where's the logic in that?!

Sorry, I'm just not seeing it! I 20:23:08 Operation Started! I 20:23:08 Source File: -==/\/[bUILD IMAGE]\/\==- I 20:23:08 Source File Sectors: 10,272 (MODE1/2048) I 20:23:08 Source File Size: 21,037,056 bytes I 20:23:08 Source File Volume Identifier: Desktop I 20:23:08 Source File Application Identifier: IMGBURN V2.2.0.0 - THE ULTIMATE IMAGE BURNER! I 20:23:08 Source File Implementation Identifier: ImgBurn I 20:23:08 Source File File System(s): ISO9660, UDF (1.02) I 20:23:08 Destination Device: [0:0:0] PLEXTOR DVDR PX-760A 1.05 (M:) (ATA) I 20:23:08 Destination Media Type: DVD-RW (Disc ID: MKM 01RW6X01) (Speeds: 4x, 6x) I 20:23:08 Destination Media Sectors: 2,297,888 I 20:23:08 Write Mode: DVD I 20:23:08 Write Type: DAO I 20:23:08 Write Speed: MAX I 20:23:08 Link Size: Auto I 20:23:08 Test Mode: No I 20:23:08 BURN-Proof: Enabled I 20:23:08 Filling Buffer... (40 MB) I 20:23:09 Writing LeadIn... I 20:23:33 Writing Image... I 20:23:36 Synchronising Cache... I 20:25:45 Image MD5: 44e714a20afba1981f602ccb24deb751 I 20:25:45 Exporting Graph Data... I 20:25:45 Graph Data File: C:\IBG\PLEXTOR_DVDR_PX-760A_1.05_13-NOVEMBER-2006_20-23_MKM_01RW6X01_MAX.ibg I 20:25:45 Export Successfully Completed! I 20:25:45 Operation Successfully Completed! - Duration: 00:02:37 I 20:25:45 Average Write Rate: 10,272 KB/s (7.4x) - Maximum Write Rate: 10,272 KB/s (7.4x) I 20:25:45 Cycling Tray before Verify... I 20:26:09 Device Ready! I 20:26:11 Operation Started! I 20:26:11 Source Device: [0:0:0] PLEXTOR DVDR PX-760A 1.05 (M:) (ATA) I 20:26:11 Source Media Type: DVD-RW (Book Type: DVD-RW) (Disc ID: MKM 01RW6X01) (Speeds: 4x, 6x) I 20:26:11 Image File: -==/\/[bUILD IMAGE]\/\==- I 20:26:11 Image File Sectors: 10,272 (MODE1/2048) I 20:26:11 Image File Size: 21,037,056 bytes I 20:26:11 Image File Volume Identifier: Desktop I 20:26:11 Image File Application Identifier: IMGBURN V2.2.0.0 - THE ULTIMATE IMAGE BURNER! I 20:26:11 Image File Implementation Identifier: ImgBurn I 20:26:11 Image File File System(s): ISO9660, UDF (1.02) I 20:26:11 Verifying Sectors... (LBA: 0 - 10271) I 20:26:14 Device MD5: 44e714a20afba1981f602ccb24deb751 I 20:26:14 Image MD5: 44e714a20afba1981f602ccb24deb751 I 20:26:14 Exporting Graph Data... I 20:26:14 Graph Data File: C:\IBG\PLEXTOR_DVDR_PX-760A_1.05_13-NOVEMBER-2006_20-23_MKM_01RW6X01_MAX.ibg I 20:26:14 Export Successfully Completed! I 20:26:14 Operation Successfully Completed! - Duration: 00:00:03 I 20:26:14 Average Verify Rate: 6,848 KB/s (4.9x) - Maximum Verify Rate: 6,848 KB/s (4.9x) md5 of that file on the disc is 53f5e3413923e57a3876d5cf7df47135 Are you sure that's the same as yours?

There is nothing in ImgBurn to limit you. You simply accept that it won't fit on the disc going by standard sizes and it'll automatically try to overburn to whatever size it needs to be. I'm not sure it's possible to specify anything over 99mins though as that's all SAO allows for due to the 'Send Cue Sheet' command being limited to 00 - 99 for 'minutes'. There's no way to send a 3rd hex character, as you would need if going to 100+.

lol, graph wise, they look about the same to me! (The PI / PIF numbers are obviously lower on the 'accuracy' one though) How much faster was the 'faster' one? From what I can remember, scanning on a plextor takes aaaaaaaggggeeees. BenQ and LiteOn owners can do it in minutes

lol the drive is making a complete mess of trying to initialise that media. Reported as DVD+RW ?! Erm yeah ok! Nice speeds too. As spinner said, try some Verbatim (MCC dye) or Taiyo Yuden discs.

lol I like my Dell 2407 WFP too

It should burn ok to that too. The basic commands used between the formats are all the same. The only bits that might need tweaking are for things like performing a full erase on the media (or formatting it) and, when the time comes, double layer 'set layer break' type commands.

It already burns them just fine. One of the mods/admin over at cdfreaks got given a drive for review purposes and he tested it all for me.

Why is it set to use ASPI for the I/O Manager? Leave it on SPTI and maybe the issues will go away.

I could have sworn a decent burn on Verbatim DVD+R DL media with the DVDROM booktype is supposed to work. I must admit though, I've not tried it myself. I've had my alpine CD in the car for a year and took it out the other day to update the disc with the new map (new map = new disc). The old one still looked perfect. How is yours getting scratched?!

You can't. The media we buy is OTP and you cannot change that.

Yep it's in there for the next release (v2.2.0.0). Out of interest, why aren't you just using hd2iso.exe ? It comes with XPe and lives in some utilities folder somewhere.

I was just messing But it is worth remembering that I/O errors are almost never anything to do with the application, they're just where the drive errors out due to a drive/firmware/media issue. If it's an app issue, THEN I may require the F8 debug log.

That's not the final v2.2, just a beta before it.

So now the log correctly shows Windows XP yeah?

So in that log, you just burnt the file on it's own via build mode yeah? Rename that file to something else and then burn it again (on a rewritable of course). Does it verify ok then? What if you build an ISO from that file and mount in DAEMON Tools. Can you then verify the mounted drive (uncheck the 'verify against image file' box) ? It could either be the content of the file that's the problem, the name of it or some combination of the two. If everything you've said about your testing is true, it certainly looks like something fishy is going on... it's almost 'rootkit' like. There's no way I know of to burn anything in mode 1 using tao/sao/dao write modes that then cannot be read back - so it's like some other driver (hence the rootkit part) is reading some signature in the file and returning the seek error.

Software is only as good as the hardware it's running on. For all we know you've ordered the worst burner in the world and are running the oldest firmware....and that really isn't my problem, that's yours. If the burn fails for any reason, you only have the hardware to blame. I/O Errors are not ImgBurn errors, they're drive errors. So if you're getting an I/O Error with the message 'Write Error' (which you say you are), I would have to say you've either got a duff batch of Verbatims (fake ones maybe) or your drive just can't even burn to the best DL media they make.