LIGHTNING UK!

ImgBurn is designed to work fine with Wine configured to XP. That's what I test it under - and I've checked it on RC3.

Nope, I have no interest in anything other than the Windows version. Sorry.

It should indeed just be reading from a single buffer, that's the whole point of it. I doubt I'll be implementing parallel burning within ImgBurn any time soon. Stick with the bigger apps for that. Running multiple instances (of ImgBurn) is a bad idea but it does work for some people. HDD thrashing is inevitable though. If you really must burn to 2 drives at once, why not get 2 drives that are the same make/model? That's what the feature is designed for.

Nope, the drive just doesn't support them (hence the crazy write speeds it's reporting).

Try ejecting/reinserting the disc a few times, maybe the drive will initialise it properly. Check for any available firmware updates for the drive. You should also perhaps think about getting some new CDRW. New ones would be 24x / 32x rather than 4x.

You can't burn CD-DA to a DVD, it just doesn't work like that. CD-DA uses 2352 bytes per sector and DVD only supports 2048.

What's in your filters list? (Access it via the 'Tools' menu, copy to clipboard and then paste into your reply). Have you tried burning at 4x? Some drives actually prefer that.

I found this bug ages ago and it's fixed for the next version. Currently it's treating wv files as if they don't need to be run though directshow to decode them.

If 10/10 work on SP2 and 10/10 fail on SP3 then it would appear your ide/atapi driver is messed up. ImgBurn follows the MMC specs which are nothing to do with drivers, the OS or anything else. It should burn equally well under any operating system that you can get it running under. Personally I'd try the drive with some 8x Taiyo Yuden TYG02 discs and if it's still failing then I'd throw it in the bin. The 105 pretty much belongs in a museum now.

Your drive crapping out is nothing to do with ImgBurn.

Look on the Advanced -> Restrictions -> Joliet tab. If you're saying the longer names have worked before in your player, yes it must be compatible.

Well you can't ignore pathnames on some files / folders and not on others so I don't really see how the column would help. With preserve full pathnames off, if you drag a file to the source box it'll be in the root. If you drag a folder it'll be in the root (unless it's the ONLY thing in the source box in which case that's optional). With preserve full pathnames on that files / folders you drag over will be exactly as they are on your hdd - with only the drive letter being different.

Doesn't ReactOS run normal Windows programs? So if it does its job properly it should work aready shouldn't it?!

Are your verbatims from Singapore? Have you tried the other supported speeds? (i.e. 4x, 6x, 8x) Maybe the drive just died on you? It's probably easier / cheaper to spend

It always makes a log... either open the log window via the 'View' menu (it should be left open all the time really) and copy+paste from it or click the 'Help' menu and the 'ImgBurn Logs...' option. The disc information in the area on the right of the main screen is also very useful.

I'm glad you did... I've added a description for that 'unknown' error code now so at least it'll be more obvious to the user next time this crops up

If you're going to post a log, please at least post the ImgBurn one!!!

Are they protected (with DRM) WMA files? You might find that only media player can deal with those properly.

ISO9660 + Joliet will allow you 64 characters in the filename. UDF gives you more characters but not all players will read it for data discs. You probably need to break the specs and change the restrictions for the Joliet file system to 'Level X' - giving you 110 to play with.

Copy and paste works too.

Just look in the log, it'll be telling you what's cutting the names. (That's why you shouldn't shut the log window) Copy + paste what you see and I'll be able to help you some more.

Maybe your email blocked it as SPAM, that's what normally happens. No software can do anything with the media until the drive says it contains something. Try it in another drive.

Did you buy the 8x verbatims? You might be better off with the 2.4x ones. At the moment the drive doesn't appear to be initialising them properly - meaning it doesn't fully support them. I certainly wouldn't try burning to them.

If your drive can't read the disc, no not really. Your drive does support DVD's yeah? It's not just a CD drive? You could try updating the firmware on the drive, it might then be able to read it.

The old one doesn't work because the 'version' of the program was never the problem in the first place.