LIGHTNING UK!

Do you have a log of you burning the 'other' discs too? The drive appears to have made a dodgy burn there as the booktype hasn't been changed either - that indicates the drive is having problems.

Well by not finishing, it kinda is picking up on the problem! There's no check for track sizes between drive and image file, just the actual number of sessions/tracks and their data formats. After that it's just down to the byte level data comparison. Obviously you have run into a situation that shouldn't ever occur and if I'm honest, ImgBurn could have handled it a little better rather than just 'waiting' to compare more data when the thread that reads the info from the drive had actually finished. For that reason, I've done some tweaking today so that the track sizes are now compared and you'll get a warning if the device one is smaller than the image file one (can't really check the other way around because that can actually happen). Assuming you want to go ahead and compare it anyway, the program will pad out the track (as read from the drive) with empty sectors until they're the same size.

You can't write off any advice we may or may not give until you've actually tried it.

a. When you use the 'Extract Boot Image' option in ImgBurn ('Build' mode -> 'Advanced' tab -> 'Bootable Disc' tab), this is what gets up in the log (JUST an example).... I 16:41:51 Creating Boot Image... I 16:41:51 Original Emulation Type: None (Custom) I 16:41:51 Original Developer ID: Microsoft Corporation I 16:41:51 Original Load Segment: 07C0 I 16:41:51 Original Sectors To Load: 4 I 16:41:51 Wrote 2,048 bytes to boot image file. I 16:41:51 Operation Successfully Completed! b. If you look at the other controls on the 'Bootable Disc' tab you'll see that the info in the log (from step a) fits in with it perfectly. c. You want to create a new (bootable) disc yeah?! In ImgBurn that's known as 'Building'.

lol course we do. McDonalds, Burger King, KFC... they're all good Seriously though, if someone reports that their drive has been permanently damaged by a command ImgBurn issues and I cannot say with 100% certainty that the command is safe then I have a responsibility to ensure it doesn't happen again by removing said command from the program (or at least any automatic calls to it).

You can but ImgBurn actually provides you the info in the log window exactly as you need to then input it for building your new disc. Without that info you need to guess it correctly yourself - and judging by your current questions, you're not quite at that level yet.

1. You have to enable the option in the settings to make build mode use the order of the 'Source' box. 2. Look in the log window and you'll see that it DOES tell you if file names have been truncated due to your settings.

This was already mentioned in your other thread. You need Build mode, then click the 'Advanced' tab, then the 'Bootable Disc' one. 'Extract Boot Image' is on that one.

You have an ISO (as an actual file) stored on a disc? You need to mount the ISO in daemon tools so the virtual drive will then show its contents. Then point imgburn at the virtual drive (E:) and extract the boot image from it.

ImgBurn extracts it from drives only. So mount the image in your DAEMON Tools virtual drive (which you might need to install of course!) and then point the 'Extract Boot Image' bit in build mode at that virtual drive and click the blue floppy disc picture. Keep an eye on what it says in the log when you extract it because you'll need to enter that info when you use it again in a new image.

Correct, if the file doesn't exist then it can't load the settings from it. The ones from the registry are then used and the ini is created on shutdown with those settings in it. The splash screen is ONLY on the screen when the forms and other stuff vital to program are being loaded. It's not there to slow down the loading by any preset annoying amount of time. Just live with it cus I'm not going to make it optional. Besides, the settings are loaded whilst it's on the screen so it really wouldn't help anyway (and no I'm not going to add yet more code to just check that one setting). The /portable one really just stops the shell extension stuff from being written to the registry whilst still allowing the settings to get saved. If you're not running it from a usb stick that you take around everywhere with you, why go to so much trouble?! On your own PC at home, just let it do it's thing.

'Files' aren't bootable. You have to do special things when you copy them to a real floppy disc to make it bootable. So without the disc / drive you're out of luck. Get yourself a usb floppy drive, you can probably pick one up for £10 or something. They're quite handy to have. Failing that, download an already bootable floppy disc image and try using WinImage or something to manipulate it and add the files that you need on there.

Before the burn... I 15:23:59 Source File Sectors: 2,752,112 (MODE1/2048) I 20:20:12 Image File Size: 5,636,325,376 bytes Size on disc after the burn... Sectors: 2,752,096 Size: 5,636,292,608 bytes So somewhere along the line it appears to have lost the last ECC block of sectors. The ??? is also worrying.

If it lists them alphabetically then that option in the settings won't do anything for you. It's to do with their physical placement on the disc. They're always put in the file system in alphabetical order, that's part of the file system specs.

You know the brand name means nothing yeah? It's the dye that the discs use that's important. In your case, it's RITEK-S04-66. We only ever recommend 1 type of DL disc on this forum as it's proven itself to work when other discs fail. That is, Verbatim DVD+R DL 2.4x (MKM-001-00). The ones made in Singapore are believed to be the best. Don't forget to check the LG site for firmware updates every now and then.

The physical order of file data shouldn't have anything to do with it. Can't you select the file you want to play on your player?

I just checked... yes it's Chaos.

What do the ImgBurn shortened names come out to? How does that compare to the Nero ones?

you could also make the E: drive! Just use 'subst' from the command prompt window. Any of these methods will work.

You could also extract the contents of the ISO and rebuild it. Mount it in DAEMON Tools, create a new temp folder on your desktop and copy the files into it using explorer. Then add your new/updates files. Then use ImgBurn to extract the bootable bit from the virtual drive. Use build mode to create a new ISO from the folder on your desktop and the bootable image it had already extracted.

In the booktype window, hit the advanced button and do what it says. ImgBurn needs to be told that your Sony drive is really a LiteOn.

DVD+RW MUST be formatted before the drive will accept any 'Write' commands. If you look in the info panel on the right you'll see a bit that says 'Formatted:'. If that doesn't read 'Yes', ImgBurn will (by default) do a full format. When it's done, it won't have to do it again so it's a one time only thing. If however another program messes up the 'Formatted' status (done by starting off a new 'format' and then terminating it early), you'll have to start all over again. ImgBurn will never do this but Nero can/does, leaving the disc's formatted status in limbo. I chose to NOT leave the formatted status in limbo so I make it run all the way though. Each to their own and all that.

You can correct the existing file if you like and email it back to me - via the address in the 'About' window. If the author is on the forum, by all means PM them.

Assuming discovery mode works fine, keep an eye on the buffer the next time you do a network burn. If you can see it dropping off slowly whilst the device buffer remains constand you'll then need to look at the network speed. Stick a trial version of DU Meter on or something and watch the pretty graph to see what speeds ImgBurn is able to read from your networked PC at. 8x *might* be pushing it on a 100mb lan, but it certainly should do more than 2x. Doing fake burns during testing, I've easily had ImgBurn hitting 35 - 40 MB/s from a network machine (connected via gigabit lan). That's basically the same speed I get doing a file copy in explorer. btw, optical drives DO NOT like being on controllers in RAID mode. ATA mode is by far the most compatible, use AHCI if you really need to RAID your HDDs and can't avoid it. Better still, buy a

Burn a disc in discovery mode and see what happens with that. This takes other drives out of the equation as everything comes from memory. What mode is your SATA controller in? ATA, RAID or AHCI? (This is a bios setting) What controller is it connected to? What's the controller called in device manager? Have you installed special drivers for it?