LIGHTNING UK!

Yup, that's the bit i mentioned about IBB text field stuff overriding GUI (even from CLI) stuff - even if it wasn't actually specified in the IBB. That won't happen in the next version. (2.3.2.0 / 2.4.0.0 etc)

From an advanced users point of view (which I like to think I am ), I quite like that you can burn as much as will fit onto the disc even though it'll probably error out at the end. It's known as overburning - but not all drives support it. You're more likely to have it error out at the start if you use DVD-R/RW media (because the initial 'Reserve Track' command will fail). With DVD+R/RW media it would error out at the end (No 'Reserve Track' command is issued). I also find it useful during testing where I can burn any image I want to on a smaller disc, if say I know I only need the first part anyway.

OH... well it seemed to work ok on mine If you have 'Auto Calculate' enabled, try unchecking that box and try again. Also, your command line should include /BUILDMODE IMAGEFILE Oh and incase it's of any interest, if you pass an IBB as the source and do so without a path name (hence it can't be found), I've now made it so it'll look in the current directory for the file, and if it finds one, use that file. That means you can leave off the 'F:\' bit if it's in the same folder as your batch file.

If you want an updated DVD Shrink, just look towards Nero Recode. It's not anything I'd ever do.

It says unknown if all your images are ISO9660 / Joliet only. Otherwise, that info is available.

wow, dial up in this day and age! 5k/s would drive me totally nuts!

Try upping the buffer to 40MB. It would seem your machine just wont sustain a constant flow of data from the hdd to the program's internal buffer. As you have a new machine, I doubt this is the case, but are your drives sharing the same cable? Whilst you're here, I'll just mention the ImgBurn 2.3.1.0 update, and firmware 1.15 for your Pioneer Remember to check for updates or you'll get left behind!

It's fine to leave stuff out of the IBB (as well you know), but due to the way things work at startup, the IBB will normally load after some of the CLI bits (i.e. volume labels) have been shoved in the approriate boxes. I've just made a few changes (I noticed some odd goings on!) and have added additional code to the IBB loading function so that it won't erase the text from fields that weren't actually present in the IBB. It should have worked like that right from the start to be honest, my bad! Do you have an example of where the program gets nonresponsive? I obviously need to stop it ever getting to that stage! - although having said that, some of the changes I've just made might already do it.

A CD image onto a DVD is fine (assuming it's possible to convert the image format to one that fits DVD), but you can't go the other way unless the image happens to b If you can't boot from DVD, update your motherboard bios / drive firmware. There's no reason for it not to work. Failing that, just download the CD installer version!

The Image must have already contained those folders. Nothing to worry about in that sense, it might just be some extra PC DVD-ROM content on the disc.

You're not supposed to decipher the one in the screenshot, that's my job. The first one though, that should be easy. What's 'ambiguous' about it?! It basically says (in simple terms): You want to put 10 litres of fuel in a car that only has room for 5. Clearly that's never going to work and the last 5 will no doubt spill on the floor. Do you want to continue?

To be honest, if you can burn them and they play, I'd have to say your drive is just playing silly buggers. If that's a real DVDROM you have listed there in the log and not a virtual drive, do the burnt discs work in it? Do the burnt discs EVER work in your burner, or just not straight after a burn? Oh and be sure to update to 2.3.1.0 before trying any more!

To be honest, I don't know! You'd have to ask the people who make the drives / firmware. I only know about it as specifying one number or another number in a structure I fill out to set the write parameters. Oh and about ImgBurn not being compatible.... that's the thing, it SHOULD be! The drives are supposed to follow the MMC specs (www.t10.org), and I do too. The program works just fine with the cupboard full of drives that I have (including a 7173 which should be similar to your 7170), so I can only assume ImgBurn has found a glitch in the drives firmware. If you could test the drive in another pc (without the raid / ahci thing enable), it would really help. I'll happily fork out for a 7170S if there's actually going to be something for me too look at. What annoys me is when I get a drive, install it and it works fine! (yes this has happened on several occasions, hence the cupboard full of drives ) When I asked about the 'locking' of the drive, I simply mean that you should not be able to eject the disc at that time. The tray would normally get locked at the start of the burn and only then unlocked once it's has finished. Pressing the eject button shouldn't do anything until it's unlocked. So if the settings were still configured such that the tray is locked during a write operation (this is on the 'Device' tab in the settings), it's weird that the eject button worked.

I guess your programs need updating to recognise NSIS 2.25 based installers or something. The exe I posted up on the ImgBurn mirror is 100% free of all that nasty stuff.

You need something like Acronis TrueImage.

You never actually answered this: Leave it going for at least 10 minutes before you eject the disc and leave it logging with I/O debug mode enabled. Oh and I guess that you must be disabling all the tray locking stuff if that's actually possible? - normally you wouldn't/shouldn't be able to do it!

So where it changes from 'Logical Unit not ready, Long Write in progress' to 'Medium Not Present', is that you ejecting the disc? As you can see from the log, the program asks the drive 'Have you finished yet?' every second via the 'Read Capacity' command. Up until the point when the status changed to 'Medium Not Present', the drive was still responding 'No, I haven't finished', along with the error code 'Logical Unit not ready, Long Write in progress'. That's what I'd expect it to say. If the drive doesn't think it's ready, the drive doesn't think it's ready. Again, the drive is doing all the work at this point, ImgBurn is simply querying it's status. Make from that what you will.

At this time, I honestly have no idea why it's saying that. Attempt another burn, but this time, before you click the 'Write' button, press F8 to enable I/O debug mode. Then once it's errored out and you've kinda exited the burn (pressed 'ok' or whatever), save the log to a file and upload it to the forum. This might be a big ask, but do you have any other machines you could try that drive in? or perhaps under another OS? I'd just like to figure out where the problem lies exactly. If it ends up being the drive, I guess I'll have to buy one - unless they fix the issue in a firmware update.

I'm not against translations, I'm just saying that you need to 'hack' at it because there's no other way of doing it.

Look in the Tools -> Filter Driver options feature. What does it list for your PC? When you use Vista's own burning interface (IMAPI), or indeed ISO Recorder (because it uses that too), it might be going in at a lower level. Something higher up is probably messing with things. You might also like to try changing the write mode to 'Incremental' (rather than 'SAO') in the settings. Then you try manually forcing the transfer length to 16. As for the actual errors, the command sequence one is bogus, there's nothing wrong with the command sequence or everyone else in the world would have this issue - and on all OS's. The commands I send do not vary according to OS. The 2nd one 'No Additional Sense Information' is not one I've seen in years! If a drive fails to complete a command issued to it, it should at least return the error code - yours isn't. Now again, that's either because the some filter driver is messing with things or it's because the drive's firmware is just crap. I'd very much like to see a test with some decent discs (i.e. TYG02, MCC-003-00 etc). Ritek haven't made anything decent in about 4 years. (Since RITEKG04 !)

Bwhahahahah

Are you trying to put 8GB on a 4.37GB disc?! Did you not get a prompt about overburning?!

Well that's why you can't load it then! ImgBurn (for the most part) burns ISO images. Well, at least that's all the 'Write' mode does. If you want to burn a random file(s) to a disc (remembering that ImgBurn DOESN'T convert anything), use 'Build' mode. Read the Guides forum if you get stuck.

'Invalid or unsupported file format' - This means exactly what it says. The file isn't supported. That's either because ImgBurn simply doesn't understand it, or because it's full of rubbish that shouldn't be in there (or stuff that should be in there isn't). It says 'Ready (Disc Needs Formatting)' yeah? So when you start the burn (once you've got a good image), the program will automatically format the media and then burn. ImgBurn only formats DVD+RW and BD-RE discs, and as you don't appear to have a BD drive, I'm guessing it's a DVD+RW disc. You should also update to the latest version, you're a few behind now.

As usual, you can download it and view the changelog by visiting the main website http://www.imgburn.com/