LIGHTNING UK!

You're obviously trying to do something with the file 'Build' mode. STOP! (well, for now anyway) At that size, the image must be a DVD one and DVD only supports one sector size / mode type. As such, you could probably just rename the .MDF file to .ISO. I don't really see where you're going with this though. If you just want to burn it, can't you just load the .MDS into 'Write' mode and click 'Start' ?

44 minutes?! That's 44 seconds and that's not even where the program does the parsing. The parsing takes place AFTER the 'Device Ready' message comes up. i.e. between these two: Making 3 seconds. The 44 seconds is the time taken for the drive to reinitialise the disc after the tray has been opened / closed - and that's nothing at all to do with the program.

I'm not even sure how that works?! I guess it must be using the 'bootable image' bit in Build mode. That's the only thing that would see non cdrom type devices and let you read from them! Unless it's just a normal build using the drive's drive letter as the only thing in the 'Source' box.

lol yeah, in that case, he must just be a drunk

I very much doubt there's massive call for this and then of course there are all the potential problem that go with it. If there was more of a 'standard' for encrypted images, I may consider it. I don't really like tying people down to just using 1 program though and of course that's what this would do. ... as such, it's a definite no at this momet, but I'll bare it in mind if it turns out that all the other burning programs start doing it. In the mean time, you could always just rar the files up with a password or something. That's much more universal.

Well if it was working fine until today, you must have changed something. (Ok, you say you changed your firmware so we'll go with that) If your old firmware supported the 'CMC MAG. AM3' discs and 1.21 doesn't, that's really bad of IOMEGA (or NEC). Your current version (1.21) doesn't list any supported write speeds. That normally happens when the drive doesn't support the media - that is to say, the media ID is not in the drives firmware and so it has no idea how to burn it. That media is 16x stuff and of course your drive is only 4x. It's like putting some 100 RON super unleaded fuel in an old Ford Fiesta from 1980 that only runs on leaded. So actually, what I said before is both logical and practical. You just need to think outside the box.

You can get firmware version 1.22 from here http://forum.rpc1.org/dl_firmware.php?download_id=1623 But at the end of the day, your drive is VERY old now and just wasn't built for today's media.

lol if I didn't know better Shamus, I'd say you were an alcoholic

I don't know how loading them into DT would tell you anyway?! A Mode1 image can quite happily be put onto CD or DVD, and you'd never know the difference.

There's no real difference. The only time there ever is, is when the ISO contains non Mode1 data. DVD only supports Mode1. To check that, yes you can load them into ImgBurn and see what it says by the 'Sectors' text on the main window.

The smilies were actually Falcon's idea in the 2nd post! I too like the smilies but I think they're a little unprofessional looking - not that ImgBurn isn't anyway! Perhaps I can make it optional to use those instead of stars, but leave stars as the default.

Hardly any drives will run with their buffer at 100%. It's not a big deal so long as it's not always on 10% !

Yup, and I'm guessing you have it checked

It probably has! As soon as it comes back to life, ImgBurn will continue. At the moment all you're seeing is it waiting for a response. It hasn't hung / frozen, it'll just wait and wait and wait and wait....

No, it only buffers what can fit in the allowed buffer size. i.e 20MB, 40MB etc. Getting back to the intial problem... I think it's when parsing the UDF filesystem more than anything. Due to the nature of it, there's a lot of single sector (random) reading that takes place and the overhead of that just kills network transfer speed. I've made a few more speed ups now so lets see if the next version is any better! That's not to say my tests came out ANYTHING like yours. I built an ISO containing 5500 files shared over 11 directories. It probably took 10 - 20 seconds to parse the filesystem. That to me, is a long time... but then I'm used to it taking about 1 - 2 seconds from a local hdd! This was just me going from machine to machine via a router - running at 1 gigabit. The actual throughput didn't exceed 10MB/s though during the parsing. This is my latest log after a those few extra changes. It would probably be quicker still, but I've got a memory checker running within the debug environment to check for access violations. I 01:11:52 Operation Successfully Completed! - Duration: 00:02:07 I 01:11:52 Average Write Rate: 6,195 KB/s (4.5x) - Maximum Write Rate: 6,984 KB/s (5.0x) I 01:11:52 Cycling Tray before Verify... I 01:12:36 Device Ready! I 01:12:39 Operation Started! I 01:12:39 Source Device: [3:3:0] Optiarc DVD RW AD-7173A 1-02 (R:) (SCSI) Please note that this was burning to a DVDRAM hence the 5x max speed

The box only comes up if the user hasn't entered a name in the main GUI and hasn't told the program to just automatically accept the generated name via the settings. When it does come up though, it always has the little button to insert the date.

Are you using different media? Even if the brand is the same, the discs might use a different dye. The read errors would have been picked up at the time of burning if you'd have verified at the same time. Might I suggest you leave the 'Verify' option enabled in future... at least until this issue is resolved. As for your Pioneer 111, just make sure you're running the most recent firmware. Disc wise, you should also make sure you're using decent ones. We recommend Verbatim (I prefer the DVD+R format ones) and Taiyo Yuden (I prefer the DVD-R format ones).

No. This is the ImgBurn forum and so if questions are not directly related to burning, they've no place on this forum.

If you build on the fly, the program knows the media you're building for and will tell you when you try to actually write the disc that it won't fit. When you're not building on the fly, no there's no way to tell it what media you're aiming for - the options for media type are purely there for the layerbreak stuff - they're not used for anything else. All you can do is hit 'calculate' and work from what it tells you. If you forget to calculate, it's tough luck I'm afraid!

What if you only add 1 file into Build mode for buring? Does it still takes ages to parse the filesystem during a verify? How does that time change as you add more files? Oh and is the EXACT text in the status bar 'Parsing File System' or does it say something in addition to that? I'd actually made 2.3.2.0 change the status a bit more depending on what it was doing. The exact message 'Parsing File System' shouldn't actually be visible for all that long. Just to be clear, this is with you burning + verifying an ISO file that you've already built yeah? Not one you're building on-the-fly direct to a disc?

Sorry, no, ImgBurn can't do it. Mount the image in Daemon Tools and then build a new image based on it, with the addition of the 2 files you want to add. Of you could try UltraISO or whatever the other ones is. MagicISO I think. Personally I'd rather build a new one than edit one.

What made the MDS file and yet gave you an image created by Nero? There's nothing to say the LB in that image is correct. Go back to the raw files (IFO, BUP, VOB etc) and have ImgBurn create it's own layer break position and then ISO file by using Build mode. Of course you'll need to be using Verbatims for it to be a fair test.

Ok, well there appear to be a readable filesystem on the disc. Can't explorer read it?

If you want files off the disc, just copy them in explorer!

Command Line support only. Read the 'ReadMe.txt' file that's installed alongside the program exe.