LIGHTNING UK!

Update your drives firmware. http://www.pioneer.eu/eur/download.jsp?dir...112_FW124EU.zip

The drive has to be far more precise when burning DVDs. That's why they can hold so much more data, everything is on a smaller scale.

Thanks for your kind words and the donation :-)

If the image (and it must be an image - i.e. in Write mode) is small enough to fit on the first layer of the disc, it should prompt you and ask if you want to just write to the first layer.

There's a timeout on how long that window will wait for when looking to see if the drive is ready to burn. The code behind it is not in a thread and so anything I do in it kills the main thread that deals with all the drawing and keeping the program GUI responsive. It won't accept that the drive is ready to burn until the main window (behind it) says it is and has enabled the big 'Write' button again - so basically it relies on that happening. You can easily check what's going on by looking at the status bar of the main window. When you click the 'Ok' button and the drive reports it's not ready, ImgBurn will attempt to close the tray - and it waits until that command has finished processing. If the time taken for that was over 1 second (which it normally is), it'll enable the 'Auto Ok' timer event (even if disabled in the settings) so that it keeps checking the status of the Write button in the main window. As soon as that button gets enabled the 'Auto Ok in x seconds' will pop up (x defaults to 10). In this (your) situation maybe it's better I don't go by the value set in the settings but just make it happen straight away and use '1' as the value of seconds. If the time taken was under 1 second it'll continue to poll the drive for a bit longer. If the drive report's it's ready it'll then check the status of the Write button for a bit longer - before eventually timing out. There are loads of reasons it might not become ready and so it's no good me just waiting forever. So anyway, I've now done it so the tray loading time is over 500ms instead of 1000ms (1 second) - I can only assume your drive was doing it too quickly and hence not running the correct bit of code. I've also set the 'Auto OK' timeout after it's ready again to 1 second instead of whatever's configured in the settings. They're minor tweaks but it might help.

Sorry Cynthia, this isn't something I'd automate. It sounds like a bit of a '1 person only' request. Just drag + drop the folder onto the source box in Write mode or into the Queue window and it'll drill through the folders and add all the images. That's the best I can do.

Have you tried with a more recent verifier? http://www.hitech-projects.com/udf/download.html As I say though, I have tweaked some stuff but the two anchor points have ALWAYS been written.

Drives only write to certain media at certain speeds. I very much doubt any new drive would still support 1x burning - except maybe on the very early 2x or 4x discs. Update your drive to the 1.07 firmware btw, you're a bit behind there.

You've already done the firmware update and you're already using (one of) the best media (MCC-004-00) - as such, there's not really anything to 'fix'. You could get yourself one of the latest and greatest LiteOn drives for under £20 now, or you could spend the next week trying everything known to mankind to fix it and then still have to buy a new drive anyway. If you want to mess about with it, put the drive in another PC and test it in that. If you don't get the same problems, look at changing cables and reinstalling your OS on the machine where it fails.

Time for a new drive I guess?

Correct, you can't just copy files from the disc and hope that it's bootable. What do you mean 'source selection' ? The dialog boxes are just the standard windows ones (GetOpenFileName) and the drop down list for grabbing bootable images is my own code. I simply wasn't interested in making it work for old OS's, hence no code is run at all unless you're on an NT based OS. It's one thing opening a file on the A: drive... CreateFile("A:\\somefile.txt".... and another opening the physical device for raw access. CreateFile("\\\\.\\A:"...

happy birthday db

It uses 'CreateFile' to obtain a handle to the physical device... the msdn documentation has been updated (to just cater for win2k and newer) but I'm sure the old version said that kind of access wasn't possible under non NT OS's. Have you considered getting a USB floppy drive? At least that would then work on your XP machine(s). Winimage can be used for floppy related stuff, no idea if it works with 98 though. You might also find 'rawread.exe' can do the job.

You're worrying about nothing. Postgap is just digital silence - i.e. writing 0's to the sector. If I was to do that when burning an image it would change the image and that of course is useless. Your discs will be fine - I often compare what I do against other tools and we all do things the same way. The postgap is really just a run-off area to make it easier to see the difference between tracks. That might be useful if burning two or more tracks on a disc but I don't see where it's useful if you're burning just the one.

Ah that'll be why then. When you run 10 year old operating systems you don't get to use the cool new stuff! Ever thought about updating?!

Sorry, I did mean full erase (within ImgBurn). Ok, install this LL0C firmware (as you can see, yours is old now - LL0A). http://www.liteonit.eu/eu/DOWNLOADS/ODD/LH...re/RW20LL0C.zip EDIT: Post a log of the full erase too please, it's much more useful than a screenshot.

Try a full erase/format on it. (or was that error after you'd done one of those?) I assume you've checked for firmware updates?

Are you running an old OS? It only works on newer ones due to the commands used to read the discs.

It writes 2, one at sector 256, the other in the last sector on the disc. I've checked 2.4.0.0 with the philips verifer some time ago and it passed everything with flying colours (after a few modifications) - and that's using UDF 1.02 -> 2.60. That's not to say 2.3.2.0 didn't write 2 anchor points, it did. All I can think that happened here is the 'end of the disc' changed between ImgBurn building the ISO and you testing the disc.

Do you have a proper desktop PC or a laptop? If you have a laptop, fair enough, get an external drive - otherwise you're much better off replacing the one in your PC.

That's the average speed, not the actual speed it went up to. Think of it like a car. If I told you to drive at 100mph, you can't just start the car off at that speed can you, you have to build up to it. When you burn at 16x it hits 16x at the VERY outer edges of the disc. It'll start off at 4x / 8x and then build up to it slowly. It all comes down to the RPM of the drive spindle.

Slow the burn down to 12x or 8x. At the moment your drive is just producing bad burns. You might also like to try the JYS3 firmware from here: http://www.cdr.cz/dvd_rekordery/sony/dru720a.html

Sorry, we can't discuss that stuff on this forum.

Have you already tried those drives in another PC? Get confirmation that they work in another machine using the exact same media and then take it from there.

You do realise this forum is specifically for ImgBurn yeah? As ImgBurn isn't a conversion program (and nowhere does it say it is), no talk on the subject is really anything to do with ImgBurn and hence doesn't belong on this forum. There are a million and one other forums FAR better suited to helping you out. To name but a few... www.doom9.org www.videohelp.com www.digital-digest.com www.afterdawn.com If you're telling me you Googled 'Convert VCD to DVD' and somehow got linked to the ImgBurn forum that I sincerely apologise - I just don't believe for a second that would actually happen.