LIGHTNING UK!

The updates probably fixed lots of things. Service packs (especially number SP2) change loads of stuff and update loads of system files. Any one of those files in the I/O chain could have been causing an issue, just be thankful it works ok now. The error you were getting should not have been drive related at all, it was a driver in the system causing a timeout to occur before it was supposed to, that then caused a bus reset. Not all drives keep the buffer at 100% all the time, it varies from drive to drive. A lot of drives also perform checks during the burn to see what the burn quality is like. These checks cause the (averaged) write speed to drop - because it's not burning during these times. So basically, don't worry

'Close -> Track' is the one that should be used first. If/when that works properly, the other 2 won't give that 'incomplete track' error. Most players won't read an unfinalised disc, that's probably why it won't play it at the moment. The drive also won't bitset to DVDROM until that's done.

Yes, that's possible but ImgBurn doesn't have a 'Read' feature yet. You can only burn from existing ISO files (in Write mode), or other files on your hdd (in Build mode). There is no facility for 1:1 (sector by sector) reading / writing at the moment.

No.

If you installed it ok on your laptop, just copy the ImgBurn.exe from 'C:\Program Files\ImgBurn' over to your other PC that keeps deleting the installer. Then run ImgBurn.exe, reset to default settings and you're good to go. You could actually find the reason for it being deleted by running FileMon from www.sysinternals.com and setting the filtering to 'SetupImgBurn_2.1.0.0.exe'. The log will then show programs that try and touch the file and what the file itself is doing. You can examine that log and see what's issuing the 'delete' call.

Your IDE drivers or some Filter driver is blocking the 'Format' command. Fix those and the problem will go away. If you have the drive on an IDE controller that's NOT part of your main motherboard chipset (i.e. a non Intel / Via / nVidia etc) one, move it so it is on the main one. Optical drives don't often work on 3rd party ones.

1. Even the volume label bit is only used/copied/there because I was feeling generous, the others never would be. 2. 99.99% of people don't care about these field or even know they exist. I don't add things that have no real place in the application. 3. It's not supposed to work like that, so that's why it doesn't. You can't add a file from 2 places to the same place on the disc, so it doesn't let you. Organise your source folders/files so you only have 1 file going to any given folder on the disc. 4. Again, it's not supposed to. 5. If you leave it blank it uses the application's default one - so basically, it can't be blank. 6. There's no such thing as unattended execution. It's a GUI program and you have to issue a series of CLI switches to make it bypass the various dialog boxes. 7. The option says "Don't Add ';1' Version Number To Files'. Unchecking it would make it add them - as is normal. What makes you think this isn't working? The code looks fine to me. 8. The 'Source' box IS the root folder. If you drag a folder into it, that folder is visible in the root, NOT just its contents. If you only have 1 folder in the 'Source' box, it'll prompt if you want to make that 1 folder the root folder - so only its contents are shown. This is all by design. If you want a custom application you can call from your own, you should ask someone to create one and pay them for it. Or better still, make your own.

I'd like to refer you to this post... http://forum.imgburn.com/index.php?s=&...ost&p=31393 This is me burning that same media with your drive (on the original 1.01 firmware). As you can see from the top picture, the white buffer line drops down at regular intervals - IT'S SUPPOSED TO DO THAT! - As I said before, it's part of the WOPC process. Also note it quite happily reached the full 18x that it's supposed to. You're trying to pick out problems that just don't exist. You came here looking for help and yet are unwilling to accept what we're telling you. Even if you don't believe the other members, you should at least have a tiny bit of faith in me! I've been programming this thing (and it's predecessor) for over 6 years and I bet I've seen/offered support for almost all the problems that could ever occur.

Ok I'm working on this now so it'll be available as an option in the next version. It will be disabled by default though.

NEC drives perform WOPC during the burn, that's why the buffer drops, it's totally normal. Look at the 'Write Speed Data Graph' via DVDInfoPro and you'll see the buffer dips quite clearly.

The drive is erroring out at the end of the burn. Nothing you can do except update the firmware and try again. If it still fails, ditch those discs and find some other ones it supports properly.

Try updating the drives firmware, you're 9 versions behind! http://forum.rpc1.org/dl_firmware.php?download_id=1651 Get the 1.12 version. When you've done that, try again. You should also probably invest in some decent Verbatim / Taiyo Yuden discs.

In your case db, ImgBurn would error out if duplicate files exist in the 2 source directories and they're going to end up in the same folder on the CD/DVD. So there IS already a check in place for that kinda thing. Hardlinking might not actually be that difficult to implement, it just means an extra stage of MD5'ing all the files and linking the duplicates before calculating the size of the image and building up the filesystems with the correct LBA for each file.

Truncating the file names is not (and should not) in any way, shape or form be considered an error. It's just part of what building an ISO is all about. It's unfortunate that whatever you're burning relies on long file names that break the spec for normal CD/DVD burning using ISO9660 and Joliet filesystems but that really isn't ImgBurn's problem and again, it's NOT something that verifying should/would pick up on. If you want to be notified of names being truncated etc, go into the settings and on the 'Build' tab, find the 'Logging' box and check the 'Non Compliant Folder / File Names' box.

Follow the guide in the 'Guides' section step by step and it'll work.

lol is that it?! It doesn't look like you've ever installed anything! Oh well, back to the drawing board.

lol I can assure you, there's NO room on the build tab now! but yes, I had also been thinking along the lines of letting the user select the format for this text. Maybe just a context menu on the 'insert date' button where it lists the options (and remembers which one you want to use).

Why would you class it as a verification failure?! The spec only allows for 64 characters so that's what it builds the ISO using. Verify is to compare what's supposed to have been written against the actual data on the cd/dvd. It's not to compare it to the original file names on the hdd as they're often expected to change - especially if say you use just ISO9660 where you're limited to 8.3 style of naming.

Power on / bus resets are never a good thing. The disc verified ok though so I doubt there's any problem with it. Visit www.bustrace.com and find the filter driver load order 'free' utility on the site. Run it, select your plextor drive and then copy + paste what it say for filter drivers loaded on your PC. Maybe there's another old one that's messing things up.

It's a shame media player does what it does but I guess it has it's reasons. You'd kind expect it to just keep a handle open to the optical drives when it's actually playing a CD - but that's not the case, it keeps them open even when you're playing MP3's etc. I assume media player 11 is the same? Anyone tried it?

No, that's totally unrelated. As far as the OS is concerned, as soon as you open Media Player, all your optical drives are 'in use'.

Don't worry about the ISO / MDS file stuff, ImgBurn is clever enough to take care of it - and it certainly would just attempt to burn a 9k file! The MDS (NOT MD5, that's TOTALLY different!) file is just used to provide ImgBurn a little more info about the ISO file. In this case, it's needed so that the layer break is in the correct place. Without the MDS file ImgBurn has no way of knowing where it's supposed to be, hence the MDS is very important.

Use Joliet instead of UDF. There was a problem with my UDF implementation on old Win9x based OS's that didn't/doesn't show up under XP etc. That has been fixed for the next version (it was fixed a couple of months ago in 'beta' versions - which of course you don't have access to, sorry!).

I probably wouldn't have bothered installing the 'Intel Application Accelerator Driver'. There's been a long standing issue with it doing weird things. The standard Microsoft drivers are fine. Looks like you've got a mixture of 'ForceASPI' and Adaptecs real ASPI installed there. Again, I wouldn't have bothered. No modern software uses ASPI (MS did away with it from the base install of the OS for a reason!) and any that do still require it can use something like FrogASPI - which is an SPTI wrapper (or Nero's WNASPI32.DLL which I believe does the same thing).

The errors are just what your drive reports, I can't do anything about them. Very rarely do I see a drive showing as '(ATAPI)', you might want to check your motherboard / ide drivers. 99% of the time it says '(ATA)'. If it's on a 3rd party controller card the drive would show up as '(SCSI)'. God knows what makes it show up as '(ATAPI)' - but it's certainly not 'normal'.