LIGHTNING UK!

This looks like a problem with the controller you've attached the drive to (or its drivers).

The discs are copy protected and ImgBurn will never touch that stuff.

The 'ADIP' values never change, they aren't supposed to. The 'Last Recorded' ones do though - but only after you've actually burnt the disc as that's when the drive updates that info.

You can find some newer (v11.6 Versus v10.0) Intel Rapid Storage Tech. drivers over here. http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=%22rapid%22&sort=Date&sortDir=descending Installing those may fix the issue with the drive disconnecting from the system.

It's probably due to the controller you've attached the drive to and the drivers it's running. Go into Write mode, right click the drive selection box and click 'Family Tree'. Close the prompt and copy + paste the contents of the Log window.

When you're using Advanced build mode it saves the name of each source file + its destination path/name within the image. Obviously it can't do that for files that simply don't exist yet and 'refreshing' isn't an option. I've already added (in the next release) the ability to use a '*' in the project file so it adds all files/folders in a folder to the specified destination folder within the image. That might allow you to do what you're after - but will require a bit of manual editing of the project file (in notepad or whatever) on your part.

It's basically the same problem as before - your drive is failing to write to the media (reporting a 'Write Error'). As such, my previous reply still applies.

ImgBurn only relays what your drive reports. So if the drive reports and error during the format or zeroing (writing 0's to all of the sectors), ImgBurn just tells you about it. If it doesn't error out, ImgBurn will consider the process a success. So basically, this is purely an issue between your drive and the media. Different methods of formatting could produce different results. One that formats/zeros the entire disc (and checks that has been done correctly via certification) is obviously more likely to fail/error out than one that just takes a couple of seconds to complete.

You'd probably need to use Standard Input mode for that and just add the top level folder - then all the other files/folders below it get pulled in via the 'Resurse Subdirectories' option.

What's the deal here? Do you still have a problem or not?

The drive will error out if it can't read something so just leave it on 'MAX'. It defaults to 8x for Audio tracks because there's no error correction and you *might* get a better read at a slower speed.

1 frame is 1 sector and that's just how CD (CD-DA) times get listed. You can't burn part of a sector, it's all or nothing, hence the rounding.

If it just stops burning, it's probably due to the controller the drive is attached to and the drivers you've got loaded for it.

No idea what you've been reading but that message means the drive doesn't think there's a disc in the tray. Setting a regional code on the drive isn't going to change that. Your drive has an issue with the disc. Try cleaning it or get another copy and see if that one works.

Create an image of the disc, saving it to your external hdd. Then just mount the image in DAEMON Tools when you want to play it. This will of course only work on unprotected DVDs. Copy protection on commercial discs will prevent ImgBurn from working.

It's a single large exe file? That sounds like a compressed package to me. Try and decompress/extract it. Google might be able to help.

http://forum.imgburn.com/index.php?showtopic=8000

Can you post a screenshot please?

How fast something fast forwards is down to whatever player you're playing the disc on. The file system being used on the disc should have nothing to do with anything.

This could be something simple like rip lock - a feature in the drives firmware.

No, like I said above, ImgBurn just burns what you give it. If you're seeing a menu that you say wasn't there in the first place, it must be coming from your player. What sort of files are you actually burning?

ImgBurn burns exactly what you give it. So if your source file(s) don't already allow for / do that, what ends up on the disc won't do it either.

Ah, I see you have an nvidia chipset motherboard... I'm not a fan of anything non-Intel really! All I can suggest is that you try some different motherboard/chipset drivers - or possibly try to revert to the standard Microsoft ones built into Windows. You may even like to try switching your controller into AHCI mode via the BIOS and see if that makes a difference - you may need to make a quick registry edit in order to make the machine boot up in AHCI mode (do it when back in ATA/IDE mode). Try it and see.

Yeah this is a drive/firmware/media combo issue. I'm sure the LiteOn should be able to handle that MID ok. Assuming the discs are up to the normal standards expected, it could be that there's something wrong with your drive. You should probably take it up with LiteOn.

Ok, load the program again and switch to Write mode. Then right click the drive selection box and pick 'Family Tree'. Close the prompt and copy + paste the contents of the log window again please.