LIGHTNING UK!

That's due to your Via card (or its drivers). If you need to have the drive attached via a PCI card, get one using a Silicon Image chipset (e.g. the Sil3512 chipset). The alternative is to go USB 2.0 (or 3.0) -> SATA... but then there's always a risk of running into a 'semaphore timeout' issue.

Please copy + paste everything from the log window. If you go into Write mode (write image file to disc) when there's no disc in the drive and then insert a disc, you should notice the message in the statusbar at the bottom of the main window changing. If it just ends up on 'medium not present', I don't see how any other program can be working - unless that 'medium not present' error code is a false one supplied by a filter driver.

If no discs work at all (cds, dvds - originals, burnt discs and blanks), your drive has probably died.

Please don't follow that guide, it's all wrong/complete rubbish. You don't ever want to force PIO mode. Update the firmware on your drive - http://www.firmwarehq.com/Pioneer/DVR-112D/files.html Try cleaning the drive with a cleaning disc. Burn at the other supported write speeds - there's nothing to say 4x will produce the best quality burn - obviously in your case it isn't working at all!

If your drive can't see (recognise/initialise) the disc you've put in it, try some other discs.

This is nothing to do with ImgBurn. Assuming these are 'DVD Video' ISO images, the aspect ratio comes from the IFO and VOB files - and this information isn't modified in any way by the burning process.

Glad to read you got it sorted

Try burning at 8x. Your drive doesn't appear to like burning those 'RITEKF1' discs at 4x. (Notice 2x isn't even a valid option) Service Pack 1 is out for Windows 7 btw.

It's in progress

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

Ideally, try your drive in another machine and/or another drive in your machine.

Go back to SPTI if it's the same for all of them. It doesn't look like you're running in AHCI mode with the latest (v10.8) Intel RST drivers there... my devices show up as ATAPI, not SATA. What about if you boot from XP on Hiren's Boot CD? Do you have any USB -> SATA adapters you could try? If you've changed drives/cables and reinstalled from scratch, the motherboard is pretty much the only thing left.

Basically, I'd just need to add an option to disable auto assume DVD Video if the parent folder is added... and then it would revert to prompting each time or something. It's perfectly do-able but this issue pops up so infrequently (you might be the first), I just haven't had reason to do it yet.

There's no way to turn off specific assumptions for DVD Video stuff, no. It has been made more and more automatic with each version (to cut down on (for the most part) unnecessary prompting). You can do anything to break what I said in my previous post and it won't be able to assume anything. So if the video_ts folder isn't called video_ts and you add its parent, it won't be picked up. If you add the parent and a dummy file to the 'Source' box in standard input mode, it won't be picked up - because the auto DVD Video assumption stuff is mainly based around a single item in the source list. In my mind, that's the quickest, easiest and best way around the issue you're having.

It's normally printed on the packaging they came in - around the barcode area.

There are 3 ways of auto creating a DVD Video disc in ImgBurn - because everyone likes to do things differently. 1. Add the IFO/VOB/BUP files to the source window (ImgBurn knows to put them in a VIDEO_TS folder) 2. Add the VIDEO_TS (or folder of any other name) containing IFO/VOB/BUP files (ImgBurn knows to treat the folder as a VIDEO_TS folder) 3. Add the parent folder of a VIDEO_TS folder (ImgBurn knows to ignore the parent and just add its contents) Based on the above methods of doing things, the program has to work in one of two ways.... Either it assumes the user wants to 'backup' their DVD Video compilations (putting stuff exactly where the user tells it) or it assumes they want to burn a working DVD Video disc. 9 times out of 10 (probably way more) it's always going to be the latter - and so that's why it does what it does. Unfortunately, you're in the 1/10 group. Maybe you're also in the 9/10 group... just not when you created this thread.

Are the Verbs from Singapore? http://forum.imgburn.com/index.php?act=findpost&pid=136519 Look at that thread/post and scroll down to 'Attempt 8'. Basically, try burning at 4x with OPC off. EEPROM settings should be as follows: Advanced Settings - Force HT: Yes, Online HT: No, OverSpeed: No, SmartBurn: Yes Before attemting your first burn with those settings, clear OPC history and then power cycle the drive (i.e. turn your computer off and on again) If that doesn't work, you should probably get another spindle of Verbatim MKM-003-00 (MIS) and try it again.

If you use Advanced input, even if it finds your video_ts folder inside the folder you're adding, there's nothing stopping you from adding it back. If the VIDEO_TS folder is more than 1 folder deep, it won't find it either. i.e. It'll find the 'video_ts' folder in a folder called 'name_of_movie' if that's what you add, but it won't find it if 'name_of_movie' is in a 'movies' folder and that's what you add. Likewise, if you add 2 movie folders at the same time it won't auto find the video_ts folders - 'name_of_movie_1' and 'name_of_movie_2'. Even just adding a 'dummy.txt' alongside 'name_of_movie' in the standard build mode 'Source' box will stop it finding the video_ts folder and making a DVD Video disc.

Do you have an early non 'B3' revision motherboard by any chance? Your SATA ports might have died (as was the reason for B3). The 2 SATA3 (6gbps) ports should still work fine even if the 4 SATA2 ones don't. Keep the drive off any other 3rd party SATA controller ports you might have on the board - although they'd probably still be better than what you've got now!

Doing a full erase in ImgBurn would (by default) disable 'spare areas' on the disc and open up a bit more room for you to use.

The firmware update program checks for the correct drive type before flashing. It'll either work or it won't - there's no chance of it killing anything. Give it (the Firmware HQ one) a shot

Try installing both of these. http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20622&lang=eng http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20624&keyword=%22rapid%22&lang=eng A command getting stuck like this is not really an ImgBurn issue. It just submits the command and waits for success/failure.... it doesn't care which but it does need some sort of response - and your machine/drive isn't giving it one. Oh and there's a 1.06 firmware update available for your drive. http://www.firmwarehq.com/Pioneer/BDR-206D/files.html

Ah, it seems you were using a burnrights built into Nero... try using the standalone version. As I mentioned above, it's not 100% compatible with Windows 7 but I've done some testing and managed to go from it working, to getting 'Access Denied' and then back again to it working. http://www.nero.com/enu/support-nero6-tools-utilities.html Install it, run it via C:\Program Files\Ahead\NeroBurnRights\NeroBurnRights.exe - you'll have to right click and run as admin if you have UAC enabled. Switch to the extended options tab and click the reset button. I'd be interested to hear what MS 2nd line support have to say on the matter and what the fix is (if one is found).

The I/O interface is just the road the I/O commands travel down to get to the drive (or final driver that then talks to the drive... I'm not exactly sure!). The commands that reach the drive will be exactly the same no matter which one you use - and that's all that really matters. SPTI is the one that gets all the testing though.

I thought they stopped shipping 'burnrights' ages ago. The version of it that I've got actually makes Windows 7 pop up a box saying it's not compatible. As SPTI isn't working anyway, I guess there's no harm in running it again (ignoring the prompt) and trying to reset the permissions (or enable 'everyone' support) - sorry but I don't know which registry keys it manipulates. There's a similar tool by Poikosoft too - just Google 'poikosoft burnrights'. Give that one a go too. You've tried the MS Fix It tool yeah? http://support.microsoft.com/kb/314060 and you're quite sure the filter driver list is empty when you look at it in ImgBurn? (via the feature in the Tools menu)