LIGHTNING UK!

It can mess up the verify, yes. You'll know if it does because it'll fail with miscompare errors. Normally if you have a bad burn you're more likely to get a read error durning the verify stage than you are a miscompare error.

Already done it ready for v2.1

I think you've hit the glitch in v2 with 32k ifo/bup padding. This has been fixed and will be available when I finish v2.1

Mount the ISO in DAEMON Tools and then either copy the contents of the virtual drive to a folder on your hdd, or just use the virtual drive directly. Point ImgBurn's 'Build' mode at those files and have it create a new image. You then burn that to a double layer disc (or just burn on-the-fly as it builds) If that's no good for you (i.e. you want it on a single layer disc), you should go back to your AVI -> DVD program and tell it to make it a little smaller! That or run the DVD through any one of the million DVD compression programs available on the web. Get it to the right size and then burn it.

If seamless is ticked, it'll change the cell flag to 'yes' if it needs to. If seamless is not ticked, it'll change the cell flag to 'no' if it needs to.

Ok, to sum up this thread.... Cal wants options to check for updates less frequently. I implemented this feature. Everyone and their dog think Cal is a total arsehole. Now you get the idea, thread closed

There's a very fine line between something working and not working. If the media is borderline, you could try a disc 10 times and 5 it might fail, the other 5 it might not. Just because your drive managed to burn it before (or those 5 our of 10 times) doesn't mean it was actually a decent quality burn. With good discs you'll get 10 out of 10 burns being successful and they'll all be decent quality burns. The 'Drives and Media' forum is there to help people decide on what media to get - trouble is, there have been no tests with your exact drive. Still, you can get a rough idea by taking an average of all the other drives. Decent discs tend to produce excellent results on all drives, not just 1 or 2. Anyway, glad it's sorted.

If the buffers get too low, the buffer recovery stuff kicks in. When that happens, the program basically pauses until the buffers have filled up again and waits until hdd activity reaches a set level before burning continues. Take a look in the log and see if you can see what I've described above actually happening. I've never had a need to burn from 2 instances of the program at the same time so it's not something I'd test. If I want multiple burns I simply queue them up and share between drives. If buffer recovery is causing issues with the way you like to work, simply disable it in the settings.

The stuff you knew in the old version is still there (almost exactly the same) in this newer one. As such, you have nothing to worry about. Just remember to switch to 'Write' mode when you need to burn ISO images, and 'Build' mode when you need to burn a bunch of files. There are guides in the 'Guides' forum that will tell you (complete with nice screenshots!) exactly how to make image/burn on-the-fly using the new 'Build' mode. If you've ever burnt a disc from files on your hdd (not images), you should recognise most of the options that ImgBurn offers you. The default settings tend to work best, that's why they're default. If you have a question about any one of them specifically, please don't hesitate to ask.

I've read about so many issues with laptop drives over the years, they're nothing on their desktop counterparts I'm afraid. I think that's why a lot of people just buy usb enclosures and use external ones. Seriously though, before spending too much time on it, get some MCC or Taiyo Yuden discs and try burning those.

Do you have any decent discs you can try with? Your drive is just having real trouble burning to those one - which is understandable because prodisc are certainly not one of the 'better' ones! You might also like to go searching for a firmware update for the drive. Visit the website of whoever made your PC. EDIT: This thread might be useful to you. http://forum.digital-digest.com/archive/in...hp/t-66029.html

The program won't let you build an image or burn the disc (on-the-fly) if you don't add a file/folder to the 'Source' box. That doesn't sound like it'll be a problem here because the 'plus file on the CD as device D:' would cover that. Those files are what you'd add to the cd compilation (i.e. the 'Source' box). Oh and yes I've seen it done before and it's quite usefull once you've got your floppy boot image just right. Just be sure to have a bootable floppy that actually loads your cdrom drivers! If you don't, that 'D:' drive will never exist

Ok, pinned! (no, not really )

Ah Win Me....that's a shame Yes, you'll have to search the net for a tool that can create a raw image of a floppy disc. It'll end up being a file of 1.44mb in size. 'WinImage' is one tool I know of that can do it. Once you have that bootable image, yes you can use that as the 'bootable image' in ImgBurn. You will need to add at least 1 file/folder to the compilation before you can burn the disc though. Simply specifying the bootable image part is not sufficient.

Are you supposed to be having a go a Jill there MJ ?! 'Cus you are (if you didn't realise) !

6KB/s?! That must have taken about 24hours to burn a disc! Anyway, I'm glad it seems to have sorted itself out.

Depending on who makes the enclosure (or rather the chipset it uses), you may be able to update the firmware on it. Prolific chipsets are quite common and there are firmware updates for those - I have a couple of them myself.

When you rebuild it, you must change the 'Double Layer' profile to 'DVD-R DL' (It defaults to DVD+R DL). This is on the 'Advanced' -> 'Media' tab within Build mode. If you burn on the fly rather than going to an image file, this should all be automatic. Remember to change the profile back when you're done with DVD-R DL and move onto DVD+R DL.

Seriously, don't be surprised if you see it again sometime! On the old forum we had a 40 page thread on semaphore timeout errors. There's an even longer one over at the afterdawn forums.

The semaphore timeout period expires because something in the USB chain overrides the timeout period I specify in the program. This is not supposed to happen but it's actually very common with usb drives / enclosures. Basically if the drive takes too long to do anything it just gives up and resets

An image must be built in a specific way for burning onto DVD-R DL media if you want to stick to the DVD Video specs regarding layerbreaks. You'll have to rebuild it with a layerbreak in the correct place - which is a 'fixed' position on DVD-R DL (It can be moved on DVD+R DL which is why they're better for this kind of thing).

Have you just installed some software that could be messing with things? Even though the buffer stuff isn't being displayed, are you finding the burn times any different? The drive (or some buggy software) might just not be reporting the correct buffer values.

It looks like it burns / verifies ok to me. The problem here is that it ejects the disc and then tries to reinsert it before the verify starts. The eject works but the reinsert (load) then fails. Bit odd really!

You need a RAW image of the bootable floppy disc. Copying files + sticking them in a folder + making an image is not enough. Put the disc in the floppy drive and use the 'Create Boot Image' option to do a raw read. This will only be available in NT based OS's though. If it works, you'll end up with a file 1,474,560 bytes in size.

Oh I dunno, I remember calweycn being despised equally as much on the old forum. Thankfully he got the message on that one, went away and never came back. I used to cringe every time he emailed 'support'. Seems he's stopped doing that now and instead just comes on here to wind everyone up. I think I preferred it when it was just me that he pissed off.