LIGHTNING UK!

>> I see what you mean. Instead of waiting all day for the Device Not Ready (Medium Not Present - Tray Closed) message to disappear, you are suggesting I eject the disk and then reinsert it for X amount of times. I will try that this weekend. Could it not be a problem with the disks themselves? Exactly. That message isn't going to change unless you actually do something - it's already a final / resting type message. It could be a problem with either of them. Something, somewhere isn't working very well if the drive thinks it has burnt the disc ok but then cannot reinitialise said disc after cycling the tray. It could be the discs, but you've used them before. The drive was able to initialise them when they were blank - it burn them and then couldn't initialise them 2nd time around... so maybe it's a hardware fault. Posting a log of the burn would help, as at the moment, we have no idea about which drive/discs you're using.

When it pops out (technically, it's cycling the tray between write and verify), you are just pushing the tray back in, yes? Don't remove the disc. If the disc is in the tray and yet the drive is returning that status (medium not present - tray closed), it sounds like a hardware issue to me. Please eject the tray and reinsert it. Does the drive manage to initialise the disc after x attempts at doing that? (The details of the disc will become visible in the info panel on the right within ImgBurn)

It's going back a good few years now, but only real LiteOn iHAS drives were capable of burning them nicely - and only really on the MKM-003-00 discs. The Vinpower Digital 'plus' drives have been designed (firmware modified appropriately) to support it. You'd have to get one of those and put it in a suitable USB enclosure.

Yes, I’d say it’s an issue with your drive. Also, you’re trying to burn one of those oversized images and you can only do that with certain drives. These days, you’ll need to buy a ‘plus’ model of one of the Vinpower Digital offerings (Plextor/ pioneer/optiarc).

Put a new blank disc in the drive and don’t touch it with anything other than ImgBurn. It’ll do what it needs to do in order to use it.

If you can’t even force close it, it’s probably not ImgBurn itself that you’re waiting for… it’ll be something lower level - a system driver or something.

It’s unlikely you’d have written/saved them to your hdd without an error popping up if there was actually a problem writing them to the disc. Likewise, if there was a problem reading any of the sectors they’re stored on, you’d have seen an error message. You can test the zip and rar files by opening them in your compression util and clicking the Test button. The util will tell you if the crc isn’t what it should be.

It tells the drive that you're about to burn a track of x sectors in size. What the drive does with that info is up to the drive It's required as part of the command sequence for burning DVD-R, but can optionally be issued for DVD+R too.

Pop the disc back in and go into Read mode. Copy and paste all of the info from the box on the right please. They’re probably fine if 2 drives can read them ok, just be open to the idea that you might have to exchange them if they don’t work for whoever buys them.

If you don’t want the program to prefer properly formatted discs, you can tell it not to via a single option in the settings. It’s on the ‘Write’ tab and probably called something like ‘Prefer properly formatted discs’.

Hmm that’s a tough one. So you’re moving the usb drive between machines and it’s behaving differently? How many burns have you tried on each machine? What percentage of those have failed on each machine? As drives are self contained, it shouldn’t really be possible for them to behave differently in different machines. Maybe it’s power related? Does the drive just take power from usb? If so, it’s probably from 2 ports yeah? Are they both usb 3 on both machines?

It looks like you’re meant to pass DEST as the 2nd command line argument. Of course, that isn’t possible by simply double clicking the bat file, you need to call it via something like this. Makeiso “c:\src” “d:\dest” Hardcoding the value, as suggested by dbminter, is therefore the way to go for you, but it kills off command line functionality.

Notice the drive/disc is saying 'Formatted: No (started)' in the box on the right - that's why it's telling you that. ImgBurn defaults to wanting properly formatted discs and will attempt to get them to that state before it burns them. Format it properly in ImgBurn so it says 'Yes' instead of 'No' and then don't use another app that's going to mess with the formatting.

As I doubt wincatalog is actually that clever, it’s probably just looking at the volume label of the discs. You can configure that to whatever you want it to be.

I did specifically say Erase -> Full too, but it looks like that log was from an attempted Quick Erase.

Yes, you can perform a full format of it within ImgBurn. Right click the drive selection drop down box and pick Erase -> Full. That won't make it accessible within Windows via a drive letter though, but maybe it'll allow Windows to actually try and prepare the disc if that's the type of access you require (i.e. use it like a large floppy disk).

You can’t erase a DVD-R, you need DVD-RW for that.

It doesn’t make much sense that it wouldn’t error out during the write phase but it does during verify. Must be a bug somewhere. Can you please tell me the exact size in bytes of the bin file?

That message box suggests the name of the file is actually blank. Same issue if you load the cue rather than the ccd file?

Could do with a screenshot of the initial error please. For some reason, the OS has decided the file is inaccessible, but it would help to see the name to check it’s ok.

There’s a tab in ImgBurn where you configure the volume labels for whichever file systems you’ve chosen to include. I simply meant to put a different value for each one. Your mkfsiso command line doesn’t appear to include UDF, so it could well be a problem with the parsing of that file system that’s causing the issue. In which case, try just setting ImgBurn to use ISO9660 + Joliet.

Did you try doing what I said? What was the result? Do you actually get to see the volume label of the mounted image anywhere? It won’t be any of the settings, disk image mounter just can’t understand the image properly.

Seeing as there’s no image conversion feature in ImgBurn, I’m going to assume you just mounted your img file using that other tool and then simply used Build mode to make a new ISO image. If the folders show up when you ‘browse’ the ISO in Windows, they must be there. I have no idea why they’re then not visible when doing the same using Ubuntu. Give each file system a different volume label when you build the ISO and then see which one gets shown by each operating system. If they both show the same one, it’s must be down to the way it’s parsing the descriptors of said file system.

Don't do it, I've heard really bad things about that website. Someone said they steal all your data and wipe your hard drive.

The privacy policy is linked at the bottom of every page on the website. They can't have looked too hard! Yes, the ImgBurn exe might appear old, but the optical disc world simply hasn't changed since then. The installer used to include a 3rd party plug-in that handled a bit of 'within the installation wizard' advertising of 3rd party programs. That plug-in is no longer included and the company that used to run it has closed off that section of their business. As such, that classification is out of date. Scan the current setup exe and you'll see it's perfectly clean.