LIGHTNING UK!

The 'hint' is the only clue you should need! Install this: http://forum.doom9.org/showthread.php?t=130498

Basically your drivers a 'wrapping' the commands sent to the drive and are screwing everything up. When you've sorted them, the drive name will show up properly with it mentioning 'optiarc' AND the model name.

This is nothing to do with burning. Either your source files are to blame or your player is.

Wow, all this time and I never knew that FTP links were being messed up by the board's URL parsing! I've fixed it now, thanks!

Are they sata drives? Do you know which controller chip is actually used for the ports the drives are connected to? Maybe it's a jmicron one if the nvidia chipset doesn't actually handle all 6 ports. Incase it is, get the latest driver from here: ftp://driver.jmicron.com.tw/jmb36x/Win2k_xp_Vista/

If you have the original image file name you can probably just google that along with 'md5' and I bet you'll get a hit. For MD5'ing files I use a tool called HashTab. It's free.

It might not see it if it doesn't have the proper name. The VIDEO_TS folder is only allowed to have files with a certain format name in them. i.e. VIDEO_TS.*, VTS_XX_X.*. As per the default settings, ImgBurn will ignore any that don't fit with that naming scheme. You can probably use DVD Flick or ConvertXtoDVD to make the full set of IFO/BUP/VOB files using that VOB as the source. Or you can tell IfoEdit to make some IFO's for it. But without VIDEO_TS.IFO / BUP and VTS_01_X.* there's no point in burning it.

The liteon tab is the only one you should be playing with. Do you have another machine you could try the drive in? One with an intel chipset if possible! Have you tried googling the drive model and 'booktype' ? Maybe someone on another forum has mention booktyping with that drive in one way or another - maybe a review of the drive covers it?

Do none of the options on the liteon tab work? Maybe that drive just doesn't support manipulating the booktype and it's done automatically? Does the official liteon tool work? Does it work when you actually have a disc in the drive?

Do you have 'include archive files only' ticked in the options by any chance? btw, having a vob isn't going to be any use when it comes to playing it on a standalone player. You need the full dvd video structure - i.e. IFO/BUP/VOB files.

Stick it (wnaspi32.dll) in the ImgBurn folder.

If ImgBurn says it's bootable then it's bootable. I don't do anything special to make a disc bootable, it just doesn't work like that. The El Torito descriptors are either in the image or they're not. It's down to your machine to actually read that info from the disc when the machine is rebooted. Try finding an updated bios for your motherboard or something. I assume you've checked your image is ok via the MD5 hash value?

Well it's a combination of the drive, firmware and media. The 3 just aren't working well together. If you can find some 2.4x Verbs then give those a try. They're your best chance at getting a working DL burn.

Try here: http://h10025.www1.hp.com/ewfrf/wc/softwar...;product=502021

These are the speeds the drive supports on those discs... make sure you've tried them both. I 13:20:37 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 2,4x; 4x) The drives don't even have to be old for newer discs not to work very well, it all depends on how much effort the firmware programmers have put into making the drive burn them ok. Matshita are rubbish for firmware updates so there's your answer right there... they put almost zero effort in!

MN32SLI doesn't google very well but it looks like you have an NVIDIA 590 chipset or something? Their drivers are buggy and return bogus error codes to ImgBurn. Switch the I/O interface to something else and it should then work ok. I've worked around their problem in the next release of ImgBurn so it won't matter after that and you can go back on the recommended SPTI I/O interface.

Maybe your controller is blocking the command or it's returning bogus error codes. What chipset does your motherboard use?

It doesn't, no. Use some proper backup software.

Yes, if you follow the guide properly it'll work just fine.

Although they might be branded as 'Memorex', the dye is 'RITEKF1' and it's rubbish. Get some Verbatim / Taiyo Yuden discs instead. What make is your PC? Maybe the manufacturers website would have a firmware update listed for your drive?

If you have an ISO then that's an image file, as such you use Write mode.

For now you'll need to use another I/O interface (look in the settings) There's a bug in the NVIDIA drivers that stops SPTI from returning decent error codes to ImgBurn.

What version of the APE (Monkey Audio) codec do you have installed? I believe 4.0.5 came out yesterday. That said, it's a known issue with their filter and has been worked around in the next release of ImgBurn.

That still doesn't look right but you have your drive and its firmware to blame for that. Your initial log was ok in that it correctly reported 16x as a supported write speed.

lame would be having a picture that's 1mb in size! Use jpeg or png and it'll be much smaller than that. Can you post a copy/portion of the log from your latest burn attempt please, it's much better than you trying to explain what you're seeing. If you've already done the uninstalling of controllers, look for updated drivers and replace the cable going to your drive.