LIGHTNING UK!

1. As you have probably now read, the media stuff is for the program to work out when a double layer disc (and hence a layer break) is required, nothing more. Build on the fly (i.e. where 'Output' is set to 'Device') and it'll go by the media in the drive. 2. Boot images don't have a name and all the info you need to faithfully reproduce its details is put into the log when you extract it. The next version even asks you if you want to reuse all the info from the place you extracted the image and fill out the fields for you. It doesn't get any better than that.

That log doesn't show any error. Is your drive old? That media should do 16x speed so I guess it must be as it's only offering up to 8x. As such you might have better luck with 8x (older) media. Try some Taiyo Yuden DVD-R with the TYG02 dye.

Memorex don't really make discs, they just use the dye made by some other company and stick their name on it. Unless you're using MKM-001-00 or MKM-003-00 dye (which is all Verbatims use) discs, they're regarded as 'low quality' by most people that provide support rather than ask for it.

Just so long as you're aware that the brand name stamped on a disc doesn't mean anything. It's the dye they're using that's important - and in this last case that was 'RITEK-S04-66'.

The 500 changes is a hardware thing. NEC probably added it so the chip that has to be flashed/changed/programmed doesn't die. As corny said though, you pick the option you want - i.e. DVD-ROM or DVD+R and just leave it at that. I can't see any reason to keep changing if the drive should booktype to DVD-ROM or not.

Multiple simultaneous (and therefore 'random') access kills hdd transfer speeds. You really want to avoid any other disk I/O on the same physical drive that you're burning from.

If you have a problem burning with ImgBurn, please tell us exactly what the problem is and include a copy of the log file showing you burning (and verifying). If you have a problem with anything else, it probably doesn't belong on this forum.

I'm sure you must be able to cross flash it to the real LG firmware, check with the peeps on the forum at cdfreaks.com

Yes, recreate the image. You can do that directly within ImgBurn to save using multiple programs.

Yes but it's the driver that has the issue, not ImgBurn. You should get on to nvidia and have them fix it.

Hmm I could have sworn I replied to this thread saying you should try unregistering / renaming / removing the entire file that's in charge of the 'Arcsoft Audio Decoder HD'.... oh well!

The choices that are currently available within ImgBurn are there because the manufacturers have actually added special commands for the purpose of changing the booktype. Pioneer haven't added any commands and booktype stuff is controlled entirely by the firmware.

Right click the file and select 'Sector View'. The sector for a given file is shown in the 'LBA' column... but right clicking on a certain file should just jump straight to it anyway.

LiteOn changed the identifier format on their newer drives. It used to say 'LITEON', now it just says 'ATAPI'. This has been sorted for the next release of ImgBurn - but it's no big deal because you can do it manually so it then knows it's a LiteOn drive and will auto booktype/show advanced settings like it used to.

Because it's old and the dye used on those discs is quite new.

You can't, they're different formats and the DVD-R one makes you reserve a track of the size you will be burning. If you want to just burn half the image (which to be honest is pretty insane!), make the image smaller by cutting the last part off in a hex editor or something. (or burn to DVD+RW and read that disc back to a new ISO).

Yes ImgBurn burns bin/cue files. Just load it (the CUE file) in Write mode as you would do any other image file.

As someone who actually wants to use Wine properly, you could always submit a bug report over at WineHQ and hope that they fix it. If they're not told an issue exists, there's little chance of it ever getting fixed

The origin of the data you're burning makes no difference to anything. It's all just a bunch of 1's and 0's to the drive.

I would have to say that it's a very odd mp3 file then! Do all your other mp3's also pull in that filter? If you email the dodgy mp3 to the support email (in the program's About box) I'll take a closer look.

Exactly my point! There's something buggy / odd about Wine remembering the drive list.

Yes it's with the media.

Thank you for allowing us a whole 8 minutes to answer your question... yes, that was sarcasm. It sounds like you're trying to use media the drive doesn't like. Are you using decent quality discs? and by that I mean Taiyo Yuden or Verbatim. If not, try getting some of those instead of whatever you're using now.

Rewritables aren't that good in general, you might have more luck with the DVD+RW's though. It all depends on the drive / firmware.

Wine has to 'publish' your drives, if it doesn't do that properly then they won't be available for use within ImgBurn. This is NOT an ImgBurn issue, it's a Wine issue. You need to go into the Wine configuration area and click the 'AutoDetect' button so your drives list gets populated properly with the correct number of 'cdrom' devices.