LIGHTNING UK!

Tries to reinstall itself?! I'm not even sure that's possible! Programs using MSI's might try that but ImgBurn doesn't use that, it uses NSIS. Where's it installing to? 'C:\Program Files\ImgBurn' as normal? Once installed, the folder / files are all present and correct yeah? If it's not there after a reboot I'd guess you have something that's removing it or your hdd is corrupt.

Ok so when's it getting stuck? Still after going into standby? What if you don't let it go into standby, does it still get stuck after a few hours? If standby is the problem, get it outputting I/O debug info (press F8) to the log window and ensure the log window is open. Then let it drop into standby. Leave it 5 mins and then resume. Take note of what's going on in the log window. Is it still processing commands or was the last entry from before standby kicked in? Copy + paste (or save and upload) eveything from the log window. Then click the Tools menu and goto the filter drivers feature. Hit the clipboard button and then 'paste' that info into your next post too.

You must have weird settings if it's only saving the log for 1 burn. Normally it would append to the log each time the program closes down - you might want to correct your settings.

It could just be your choice of media - perhaps the standalone can't read it? It would certainly appear that is the case. Post a log of the burn + verify and we'll take a look.

IBB's are for Build mode, not Write mode. The fix? Issue the /mode command - it's probably the most important one!

The clarity of the questions are even more important. If you can't describe the problems you're having in a clear and concise manner, how are we supposed to help? We already know what we're doing and we shouldn't have to keep prompting you to tell us exactly what you're doing / looking at. The use of log files and screen-shots plays a very important part in problem solving and should be used to get your message across whenever there's a need. Although we often joke about it, none of us do actually have / use crystal balls

Yup, the next version can actually read it properly to a bin/cue and then burn it back from said bin/cue. So if you just want to copy them, this will then do it. You could also mount the cue in something like daemon tools and play it from the virtual drive as if it were a real vcd disc.

A VCD is NOT handled within the ISO container format. At true VCD contains 2 different tracks, both with different sector format - an ISO can't represent that (not on it's own anyway). Whilst it might work on some forgiving players to read/write the disc as a single track, I really wouldn't recommend it. By copying the dat file, all you're doing is making a data disc, it's no longer a vcd. It's just a disc with mpeg content.

I swear some people shouldn't be allowed to purchase a PC.

Are you reading in 'Build' mode or something? If you want to copy a disc you use 'Read' mode - and if you try that you'll see VCD's aren't supported (yet - and certainly not as an ISO). It would however get around any OS errors (which that is) and give you the real reason as to why a sector from that file could not be read.

ImgBurn won't read copy protected discs.

There's no real explaination for this. If you can swap the cables and the error goes wherever sata 1 goes (100% of the time - you'd probably need to test this 10 times or something), it must be a controller issue or a driver that's messing up the burns on just that one channel (unlikely). Have you actually done the SB01 firmware update now? Did you try burning at 12x?

an old drive too, perhaps it's worn out?

If it's on an ide port, I mean the ide controller. Perhaps you have it on a jmicron one? You might see a clue when you reboot the machine and look at the bios screens.

You've got it connected to a controller that blocks the 'format' command. See if there's an updated driver for it or remove the driver and hope the windows one works. Of course if you have another controller to connect it to, do that.

Because random info doesn't let people trace back where it came from (what made it) in case of problems / bugs. What's the big deal anyway?!

You might find it easier to actually follow the guides. That's what they're there for. Look in the 'Guides' forum. btw, all the other screens (besides Build mode I mean) would always show you files, build mode is the only one that 'could' give you the folder selection dialog. If you aren't seeing the files you expect to see it's because of the 'Filter' - whereby only image files are displayed.

Does the process actually go away when you do that or does it just close the app window? Sounds to me as if one of your drivers isn't processing I/O commands and that's why it's stuck. When you click the close button, what do you see in the log window? Copy + paste it. I never use standby so I've never tested this stuff personally.

I remember the name, have been reminded about the guides you once wrote and can't seem to get the idea out of my head that I should remember a picture you had up on the old forum. Maybe it was your avatar? Your profile pic? I dunno! Oh well, welcome back anyway

Hey, I can be a 'dude' with the best of 'em

Yup, you have single sided, double layer discs. I'd just go for automatic, you'll be re-doing it with ImgBurn anyway so it doesn't really matter.

Are you using double sided discs? (Notice that it's saying 'sided', not 'layer' - the two are very different). I'd stick with 1 side as nobody uses flipper discs these days.

If that doesn't normally happen, just ignore it. You do get fluke failures now and then. If the firmware on the drive is up-to-date, there's nothing you can do about it short of getting a different drive.

Ejecting + reinserting the disc could have fixed it anyway. As I say, it's not normal for a drive to get stuck 'becoming ready' forever.

Protected or not, if the drive can't read the disc then you can't play it! - and I'm sure you'll agree that's a bit of a problem