LIGHTNING UK!

You need to go back to pinnacle studio and recreate the ISO. It messed up the first time. Personally, I'd tell Pinnacle to just output a VIDEO_TS folder (with IFO/VOB/BUP files) and then make ImgBurn 'Build' the ISO instead.

That log shows the disc are still using the same SONY16D1 MID/dye and are therefore the same as the others. You're also using 8x which I already said was the same as 'Max' and therefore what you've already been trying. You'd need to try 3x, 4x or 6x. See, the 'Max' speed is 8x for your drive/firmware/media combo. So it doesn't matter if you set it to 8x or 'Max', it'll still burn at 8x. That leaves you with 3x, 4x, 6x to try out - personally I'd go with 4x first and then the remaining 2 in whichever order you fancy.

The feature you're trying to use is for *creating* CUE files, not editing them - hence why it's called 'Create CUE File'. You have an BIN/CUE image file combo and it must be burnt in Write mode just as you would do any other image file. I don't know why you can't click and drag... maybe you were dragging from somewhere that doesn't support dragging? You have to drag from an Explorer (or similar) window, not anything you may or may not be able to bring up within ImgBurn itself (i.e. a 'Browse' box).

Your drive is reporting a 'Write Error' when attempting to burn those discs. It's unlikely you'll find a firmware update to fix the issue with burning that media (SONY16D1) so try burning at a lower supported speed (something other than 'Max' a.k.a. 8x) and/or getting different discs (Verbatim or Taiyo Yuden).

Correct, it'll attempt to use the CDT file as specified in the CUE file. If it can't find it, it tries a few other methods such as using the same name as the CUE file (but with '.CDT' file extension). No, it's not reported anywhere that a (successful) substitution has been made.

It doesn't just rely on what's written in the CUE file, it also uses its head a little bit based on the CUE file name etc. If it doesn't tell you it's missing, it found it. Click the 'View Image Information' button and you should see the CD-TEXT related info (of course that title/performer info would need to be missing from the CUE to tell for sure).

It already does... or at least it certainly looks like the code is performing various checks for a CDT file before complaining it doesn't exist if it can't find it.

http://groups.google.com/group/microsoft.public.win32.programmer.directx.video/browse_thread/thread/2f508e5944d2111e?q=qedit.dll+windows+server+2008# The first post may help. I guess you'd get it from Vista or Windows 7 depending on if you have 2008 or 2008 R2.

Does it start ok when there's no disc in the drive? You'll have to enable I/O debug mode to capture which I/O command the virtual machine/drive is failing to process. This is covered in the FAQ where it talks about getting stuck searching for devices.

This isn't a bug, your OS just doesn't have what's required for audio decoding. (I'll move this thread to the correct place - 'Support') Installing the full DirectX suite may fix it. If it doesn't work, google for 'SampleGrabber Windows 2008' or something. btw, if you're running Windows Server 2008, why does it say Windows 2000 Pro in the log? Don't mess with the compatiblity options on ImgBurn.exe.

No, what you've done is 'Read' a disc to an Image File. Now you need to 'Write' an Image File to a disc. As all you wanted to do was copy a disc, you should have followed this guide - http://forum.imgburn.com/index.php?showtopic=6380

I'm not sure I understand what you're doing? Do you already have a bootable Windows 7 disc or are you trying to make one from scratch? If you already have one, you just put it in the drive and use ImgBurn's Read mode ('Create Image File From Disc') to create an ISO of it. To me, it looks like you've already done that - hence the 'Windows_7_Ultimate_64.iso' file in your screenshot. If you don't already have one, you're pretty much out of luck - unless you happen to have a copy of all the required files (with correct folder structure) on your hdd - only then you would try and follow the Windows 7 installation CD guide in the Guides forum.

Try watching it on the PC with something like 'Media Player Classic Home Cinema' or a proper DVD player like PowerDVD. If it's not a problem with the player itself, it'll be a problem with the source files (i.e. DVDFab's output). It's not going to be an issue with the burn - unless you're using cheapo discs that are hard to read back. You haven't posted a log (read the pink box up the top ) so I can be sure on that one.

How are you playing the disc and in what? A standalone player doesn't even see the vob files. They're recorded sequentially and can therefore be treated as a large chunk of data.

No and No. 9x support will only be dropped when I update to a newer development environment - and that's only because it dropped it, not me.

I'm not sure that would work Cynthia. To me, it looks like 'Disc 2.iso' is incomplete/corrupt. Create it again from the source files/disc.

Notice I did say you need to use DVD-R for the Test Mode thing, DVD+R won't do. If you don't have any DVD-R then you won't be able to do any Discovery mode testing without wasting discs. You could try enabling the 'Reading - Always Use Buffered I/O' option in the Settings (I/O tab). If you have an Intel chipset board, can I assume you have the latest inf / chipset and (if the controller is in ACHI mode) 'Rapid Storage Technology' SATA controller drivers installed?

The default 20 / 40 meg buffer will only be enough for about 2 or 3 seconds worth of hdd streaming interruption. If the buffer wasn't being filled at all, it would therefore empty out almost immediately. What I expect you're seeing is the buffer level slowly dwindle off down to zero as the hdd just can't keep up. How long does it take to recover from an empty buffer? The amount of free space on the disc (controlling where the file are located - notice the drive gets a lot slower as it fills up) and fragmentation are both important factors. Stick DVD-R's in all 3 burners, go into discovery mode and enable 'Test Mode' (so as to not waste discs), then start burning. In theory, you should be able to max out all 3 drives doing that because the program is making the image data up as it goes along - there's no reading from the hdd. That'll at least rule everything from ImgBurn -> Burner out of the equation.

Run something like HD Tune on your hdd and post the benchmark graph please. Before you start it though, go into the option and make sure it's set for a full test. 3 x 12x burns would be ~50mb/s at peak speeds... to me, that seems an awful lot for a normal mechanical hdd to handle when random accessing 3 image files (plus usual windows I/O going on in the background).

I won't pretend to actually know what I'm doing here but maybe the obvious 'firmware' folder isn't actually the right place for them? Searching all files on the disc for 'firmware' seems to have loads of hits in the file 'dists\squeeze\non-free\binary-amd64\Packages' and opening that file in notepad shows it pointing at firmware files in the folder 'pool\non-free\f\firmware-nonfree'. Are you perhaps meant to put your files in there and add their info to the 'Packages' file so it knows they exist?

Correction, you need ISO9660:1999 and Joliet. Without Joliet the installer just fails a bit later on complaining about a 'Release' something or other.

Ok so it's an AMD controller. Do you have their latest chipset/sata controller drivers installed? Get them from the AMD website. Have you tried burning at 4x?

I'm guessing the installer/bootloader doesn't work with Joliet (or UDF) and so relies on the Rock Ridge file system for long file names. As ImgBurn doesn't support that you're left with using ISO9660:1999. So set the 'File System' to 'ISO9660' and then click the '1999' link on Advanced -> Restrictions -> ISO9660. Build a new image and then try that one.

That's not building it but don't worry now, I see the issue. It brings up the first menu but just keeps reloading it when you select an option from it.

Do you have the log from when you built the new ISO please?