LIGHTNING UK!

This isn't your thread, therefore by posting in it with anything other than help for the owner is hijacking. The FAQ is a single thread with about 20 odd posts. Just find the one where it mentions slow burning in the 'problem' bit at the top of the post. If you avoid reading stuff you'll stay an idiot. (Your words, not mine!)

Take a look on the packaging and see if they're made in the same country. Maybe you've got some from Singapore and some from India or something. The ones from Singapore are probably what the drive's firmware is setup for. Tweaks might be required for discs from other countries where the dye is ever so slightly different. You can't 'force' anything, the drive does what it thinks is best.

Try turning off the 'DVD+R Reserve Track' option in the settings (on the Write tab). It's not an option that should be causing a problem but tiny problems with some drives (all liteon's from what I've seen) make the DVD+R come out like DVD+RW for some reason. That said, where I've seen this problem before, other drives can normally read the disc just fine. It's only the liteon burner that has a problem initialising the disc properly and reading it back. It's the drive that's messing up here, not ImgBurn itself - I just want to make that clear!

No, it all comes down to what the drive/firmware supports on the media you're using. Look at the 'Supported Write Speeds' bit in the disc info panel on the right side of the main screen.

Layer break info is normally stored in a file that goes along with the main data file (i.e. a '*.mds' file or '*.dvd' file). There shouldn't really be any need to enter it manually. If you really must enter it manually, just remember that it then applies to ALL DL images / discs you burn until it's set back to 'Automatic'. 'Tools' menu -> 'Settings' option -> 'Write' tab.

You probably don't have a DVD burner (it's probably just a DVD reader).

You know this is the ImgBurn forum yeah? If you're going to post a log from a program, surely it should be one from ImgBurn?!

Maybe I should change 'AUTO' to 'AWS' as it seems to catch a lot of people out that don't really know ImgBurn.

ImgBurn will only write to media once and it has to be blank (or erased by automatically by the program) before use. Settings read/write flags inside the UDF descriptors wouldn't do anything towards allowing ImgBurn to add to it. If you want to use the disc like a big floppy drive, install one of those horrible packet writing utils. Personally I prefer to use media better suited to the task - i.e. DVD-RAM or a USB memory stick/pen.

Probably a bad disc. Try a firmware update though. http://www.liteonit.com/DOWNLOADS/ODD/LH-2...rmware/LL0D.zip

You can see the 'wine configuration' screenshot in that guide. Clicking 'Autodetect' always just worked for me. There is an issue with wine forgetting drives if you eject / load a disc though (It sometimes vanishes from the config screen). I never bothered to get to the bottom of it. Someone that actually uses linux / wine should report it to winehq as a bug and get them to fix it.

If you'd exceeded the 5 second window for pressing a key the existing OS should have loaded. That's the whole point in making you press a key and not just going straight into the installation! That's where a bios update would come in. You can normally tell the bios to take control of the keyboard too instead of waiting for the OS to initialise it. Press DEL / F2 etc next time you reboot and go through the bios options.

You must have 2 machines (or more) or you wouldn't have a network at all - right? So make an image of a disc on 1 machine and then (via drag + drop), copy it to the other one. I don't know how to dumb it down any more than that, sorry! Copying a file is a pretty simple process. EDIT: Thinking about it, you totally hijacked this thread so maybe your problem is totally unrelated to network issues. In which case your problem might be down to a DMA configuration issue - Read the FAQ and uninstall your IDE controller + reboot like it tells you to.

Not in 2.4.1.0 but the standby thing has been added for the next version already (as per a previous request).

The guide in the forum tells you everything I know and there aren't that many linux users on this forum... this is a generic wine config problem so you're better off asking the question on a linux forum of sorts.

He means the 'Help' menu.

ImgBurn isn't DVD Decrypter. The programs have very different purposes, ImgBurn is a burning tool.

That's because ImgBurn doesn't support multi-session at the moment.

The burning code is the same no matter if you're burning an image or burning files. Post the log and maybe it'll help.

Try something like convertxtodvd. - www.vsosoftware.fr That program should be able to convert it to a DVD Video disc format.

Once you've tried Verbatim / Taiyo Yuden media and are still getting the same error with those, try a cleaning disc in the drive. If it still doesn't work even after that, consider having it replaced as there appears to be something wrong with it.

It would only take 2 minutes for you to install 'DU Meter' and start to copy a large (1GB or more ) file over the network to get an idea of how fast it can go. http://www.dumeter.com/

There's no problem with the disc then. Have you actually hit a key when the disc boots up? That part is perfectly normally as all the windows bootable discs do the same thing. If you don't press a key within 5 seconds or so it should then just continue to load any existing windows installation. Of course if your machine won't accept keystrokes and it won't continue to load windows then it's probably a bios issue - in which case you need to find the manufacturer of your PC (or motherboard if it's a DIY job) and update it.

Use something like 'HashTab' to generate the MD5/SHA-1 of the image and compare it to what TechNet says it should be. You can then verify the disc against the image file in Verify mode once you've checked the SHA-1's match. Are you actually trying to use the disc in the drive that just burnt it? Obviously the Verify bit only checks that it's readable in that specific drive - there's nothing to say a different drive will be able to read it correctly (RITEK media isn't exactly the best on the planet I'm afraid).