LIGHTNING UK!

...and that is a very common problem on USB drives. Search google and you'll see what I mean.

Turns out I'd already sorted the shortcut character problem in all the other places, but as the queue window is new(ish), it didn't have the correct options applied to it. That bit has now been sorted.

The program doesn't make up the percentages, it gets them from the drive - maybe the drive just sits on 98% for a while until is finishes. If it can't finish, it'll probably report 98% forever.

Windows only ever has a split second to react to the handle being closed before it's then reopened. To be honest, I'm amazed that refresh ever worked in the first place - especially as virtual drives react so much faster than real ones. The drive is always 'given up' by the program, it's just a case of it Windows gets a chance to butt in or not. You'd probably need to refresh ImgBurn and refresh explorer at exactly the same time. Of course you could just switch to another drive, but the closing / reopening the program may be just as quick.

changing modes always kills the drive handle, so if that didn't work, refreshing orders was not the problem. Also the refresh procedure does not rely on the file refreshing to be successful for it to refresh the drive. The file refresh does happen first though and must stay that way. It's done in the foreground by the main thread. The drive one is done in the back ground by a 2nd thread and the refresh function does not wait for that to finish.

Kenadjian This is just when the program tries to initialise the drives on startup, we're not talking about trying to burn to it or anything

Discovery mode doesn't burn real content to the disc. It's purely for testing purposes. As for what to enter for a file in 'Write' mode.... well the ISO image of course. You do have an Image that you want to burn - yeah?

Well your ASUS DVDROM is the problem. A query of it's regional code is hanging. Nothing I can do, in a properly working system, it should work fine.

No problem mate, just glad you popped back eventually

If this were as simple as it seems to you guys, it would already have been in the program - although like shamus, I doubt I'd have seen any real need for this particular feature! Trouble is, that list in the Queue window doesn't actually go anywhere. It's just a list of names. The other 'Source' / 'Destination' drive lists have an actual device attached to them - and only 1 device is active at any one time. As the list of drives in the queue window could be on a different drive to that of the main list, this presents a problem. I will see what I can do.

Read + follow + do what it says in the FAQ please.

Your drive does not support the discs you're using. Try looking for a firmware update for it.

Ah well support for burning files is actually almost done! We now have a new 'Build' mode With files so large though, it would probably only work with just UDF as the filesystem - of course if it's only a single layer burn, ISO9660 might be enough.

I don't really understand what I'm supporting! Doesn't Acronis expect the tib file to be on the hdd somewhere as an actual file? At the moment, it sounds like I'd be doing the same things as burning the raw content that is a RAR image to a disc. Nothing would then be able to open it again! If Acronis really does create an image that's self bootable off a DVD, then yes, there is point to this whole thing. I however, could not find such an option within the program (but then I don't really use it )

Well they don't look like anything special so just open them in a hex editor and see what they contain. It could just be 4GB worth of 0's!

Doesn't look like it supports that media with the 101 firmware. Either that or you've got some duff Verbatims. It might be an idea to check out the BenQ forum over at cdfreaks.com and see if anyone else has mentioned it.

I dunno but I tend to think about it in terms of driving a car. Tell 2 people to drive 100 miles at a steady 80 MPH. 1 has a Ferrari, the other a VW Golf TDI. They'd both reach the 100 mile way-point just fine but would use very different amounts of fuel. So it's impossible to say 100 miles will use up X amount of fuel - FULL STOP. But what you can say is 100 miles will use up X amount of fuel IN A FERRARI when driven at a constant 80 MPH. All drives are different and have different reading abilities. That's why it's never a good idea to compare scans between drives - some are just going to report less errors as they're more able to read through problems areas that others may find quite taxing. Hopefully that explains the drives side of things. As for differences between programs... well in all honesty, there should be. The drive reports the data/values, the software just has to plot it on a graph. Trouble is, (from what I've heard) some report in a different way to others and so it's the softwares job to try and find a common ground between ALL the drives - messing around using certain calculations to make them all seem the same. This is where the anomalies can creep in. Again, every attempt to read the disc could end with a different result. A scratch that you couldn't get past on your first attempt may be invisible on the second... that's just drives for you!

It's impossible to turn burnproof off for dvd+r, it's part of the spec that it's ALWAYS enabled. Or at least that's what the MMC specs say Re: the DVDInfoPro thing, I just deleted my 'HKEY_CURRENT_USER\Software\SWN\' key and then ran dvdinfo pro. It makes that key again but doesn't appear to be creating the 'Installation Directory' value again. I will report this to Nic and get him to fix it.

ImgTool Classic doesn't do anything with the layerbreak. You should use PgcEdit instead for DL burning.

1) Ok, well you should do! Maybe you didn't install it properly or are using an old version. Or maybe there is a problem writing to that key on your pc. 2) It's normal for the buffer to drop during the burn. It does it every time the drive performs any sort of WOPC - as such, it would be very difficult to actually say for sure how many REAL buffer underruns occurred. Anyway, with all the zero loss linking stuff these drives do now, it's not important.

Whilst doing the scans for the media forum, I often had one that registered high PIF's or some POF's when the graph didn't show anything of the sort. For me though, it was normally just a case of closing DVDInfoPro down again, ejecting + reinserting the disc and then scanning again. It's hard to say where the fault lies as I would expect dvdinfopro to just display the info the drive is returning - there shouldn't really be any room for error. It is weird and very annoying though so hopefully one of them will fix it! I didn't try going between CDSpeed and DVDInfoPro as I knew a rescan in DVDInfoPro would probably fix the issue too - and therefore it wouldn't have been a fair test. If in doubt, submit it to the dvdinfopro 'mantis' bug tracking page and have a moan

Ignore the 'write protected' bit... that's my problem due to some bad memory copying on my part. The other two are yours though I'm afraid. The drive is reporting errors while it's off doing its own thing - in this case, closing the track and finalising the disc. ImgBurn simply issues those commands and then polls the drive to check it's status. The drive is then reporting those errors in the data it replies with. This could well be a problem with iSCSI.

You must be reading the size figures from somewhere weird. The image won't grow when you burn it - except by a max of 15 sectors (so 15 * 2048 bytes) if you burn to DVD+R and the filesize (in sectors) is not a multiple of 16.

I'll look into that multisession stuff, thanks pfeerick

DIP says that for mine too but that's just because thats what the drive reports. It CAN be flashed though.