LIGHTNING UK!

I/O Debug mode does exactly that. I really wouldn't recommend turning it on unless you have a real reason to, it's slow as hell and really just there for my own use when helping people solve problems.

I'll add a button to do this.

You need to forget about isobuster, that stage has been replaced by the daemon tools bit. Take the original image (the one with the boot image inside it) and mount that in DT. Then in ImgBurn -> Build mode -> Advanced tab -> Bootable Disc tab, select the virtual drive (E: ?) in the Extract Boot Image' drop down box and click the blue floppy disc. That'll get you the boot image from the image and also give you all the info you need in the log window (open it via the 'View' menu if you've closed it). Then you'll have info like the stuff I posted earlier. i.e. 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! Use the info in the log to fill out all the other fields on that 'Bootable Disc' tab.

No, it doesn't. ImgBurn can't extract the bootable bit from an image, it has to come from a drive. That's where DAEMON Tools comes in. We've been over this several times now. If you just do what I've said it'll be done in 5 minutes, you're making things hard for yourself by looking into it too much.

They're all disc errors! I/O errors are to do with the drive/firmware/media, they're not program related (99.9% of the time).

Buwhahahah

When you say you've 'checked' DMA, do you really just mean exactly that? i.e. you 'looked' at it but didn't actually do anything? It never hurts to follow the bit in the FAQ marked by the huge/bold 'Important' text. At least that would then be another thing you can rule out.

No, it won't automatically span discs or ask you to insert the next one. You'll just have to make 2 folders, copy 500 into each and then burn each folder in turn.

This issue isn't related to ImgBurn, it just does the burning (and that's done 'as-is'). You'll be better off asking for help on another forum that actually deals with that stuff - we don't here I'm afraid.

This is more of a sanity check than anything and very easy to get rid of. As El Torito works in sectors, the last one will always be padded with zeroes if it's not quite 512 bytes - there's no way around that. Beyond that, the Mode 1 CD/DVD is obviously 2048 bytes so that 512 is potentially padded by an extra 1536 zeroed bytes - but they won't be referenced in the 'Sectors to load' bit. What I don't understand is why that isolinux program doesn't just output it so it's a multiple of the sector size. I can't think where it could be used where 512 byte sector sizes DON'T come into it, so why not make it a multiple of 512 in the first place? I wouldn't dream of outputting an ISO that wasn't a multiple of 2048 or whatever.

I'm sure it'll happen one day.

lol just noticed the '100' bit. You don't look a day over 99 mate

Mode menu -> Build. Output menu -> Device Add files to source box. Click the 'Write' button. Even the buttons on the main 'Ez-Mode Picker' screen should give you clue as to what you need to do! There's one actually called 'Write files/folders to disc'.

Yes, just use build mode the same way you would use it for any other files.

I have done so already - for v2.4.1.0

There's nothing much else for me to say?! The DirectShow stuff is out of my hands. All I basically do is tell it the source file, tell it the 2 filters I need it to go through (and end with) and it's supposed to fill in the blanks. If it doesn't think it can do that then it errors out and my program then falls back to the ACM code - which was indeed broken. If you happen to still have a copy of the file that didn't work, try opening it in GraphEdit and see what it says.

This is nothing to do with ImgBurn, your drive is erroring out because it doesn't like the media you're using. Use some decent discs and the problems will go away.

Early again (48 mins)... Happy Birthday mate

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.