LIGHTNING UK!

NSIS based installers are forever falsely getting picked up as viruses, it just means the AV people haven't gotten round to tweaking their definitions after a new version was released (in this case, NSIS 2.38).

Don't worry, I have absolutely no intention of changing anything to do with the progress bars.

For people updating their translation to v1.0.0.5.... You need to redo frmSettings - number 11. frmMain - number 479 and 485

All those registry entries (apart from Drive.CDROM) are checked by default - and it's always been that way. Are you sure you haven't uninstalled powerdvd or anything?! Each context menu entry is its own unique registry key. Adding another one doesn't touch existing ones. The 'Drive' entry you want to change to 'DVD RW' is an internal windows name, you can't change it and you wouldn't want to. I don't believe there is any problem here. If your powerdvd has mucked up you could just reinstall it to fix the issue.

That would be in the pregap of a track (index 0) - players always start from index 1. You wouldn't generally make your own compilation like that, it seems a bit pointless! If you have an original disc with a track in the pregap (and that's normally only before Track 1) then it'll be captured just fine using Read mode. Within the CUE file, where you'd normally see something like: FILE "normal track.wav" WAVE TRACK 01 AUDIO INDEX 01 00:00:00 You'd then have something like: FILE "hidden track.wav" WAVE TRACK 01 AUDIO INDEX 00 00:00:00 FILE "normal track.wav" WAVE INDEX 01 03:32:00 So the 'hidden' bit of audio lasts 3 mins 32 seconds or whatever. Please note that the syntax there might be wrong!

Nope the CDB's are pretty straight forward. It's all explained and broken down with the MMC docs. Byte 0 in the CDB is always the command operation code - i.e. where you tell it you want to Read a sector or write to one. and then maybe bytes 3 - 6 will be the LBA address of where to read from / write to. and bytes 8 - 9 will be the number of sectors to read. (that's simplified but you get the idea) Yes you can test CDB's with DVDInfoPro if you like. I'm sure you'll find it's more fun to code your own functions though. There are 3 ways to enumerate really. Go by the drive letters, go by the CdRom class or use the SetupDi functions. ImgBurn can use either of the first 2. Yes an ISO is created by reading a sector from the disc and writing it out to a file, moving onto the next sector and repeating the process. It's a 1:1 copy of the disc. So when you burn you read the first sectors worth of data from the image and then write it to the appropriate lba on the disc.

Start by looking at the mmc command specs document and then all you really need to do is figure out how to enumerate the drives and send a command to them - this is done via the functions CreateFile and DeviceIoControl (with the parameter 'SCSI_PASS_THROUGH_DIRECT'). Microsoft have a few basic examples of how to communicate with drives. You just have to swap out the MMC commands they issue for the ones you want to issue - and that's just a case of changing what's in the CDB (command descriptor block).

Windows picks its own order for these things, all I do is add a context menu entry depending on the options in the settings - on the 'Registry' tab.

Oh and I noticed from your other thread that your Pioneer Bluray drive is the IDE model but showing as SCSI. I assume that means it's not on a motherboard chipset port and instead on a 3rd party one? Well, it's that or the drivers just make it look like a SCSI device. Which motherboard is it connected to and which chipset is it running? (Intel, Nvidia etc) A lot of controllers don't like optical drives all that much and it's important that the bios for the motherboard/controller is kept up-to-date (much like the firmware on the drive!) and also the drivers. JMicron controllers are common on newer motherboards where legacy IDE controllers have been removed from the main chipset. (ICH8 onwards on Intel boards I believe) Updated drivers for the most common one can be found here: ftp://driver.jmicron.com.tw/jmb36x/Win2k_xp_Vista/

Before putting the disc in just press F8 to enable I/O debug mode. Then we'll be able to see which command the drive is having trouble processing via all the stuff in the log window - you can just copy & paste from it. When I/O gets stuck, it REALLY gets stuck. The only way out is to force a bus reset (which you need special software for) or to just reset / power off the machine.

The 'boot image' should point to the isolinux\isolinux.bin file in your file structure. The sectors to load should be 4. I'm not so sure you want 'Preserve Full Pathnames' enabled - that could prevent things from working correctly. If the folder & file 'isolinux\isolinux.bin' doesn't exist in the root of the image then no patching will take place. For testing without burning you can just build an ISO and try to boot it in vmware / some other virtual machine program (having mounted the image as a drive).

All the drive is saying is that it can't write to the disc. The media might be fine in some drives, just not yours. Likewise, other media might be fine in your drive, just not that one. If you're going to change one of the variables, it's got to be the discs first as Verbatims are just better - full stop.

It's got exactly the same file hash as the ImgBurn.com mirror one - so basically it's 100% fine.

2.4.2.0 ? The file must be exactly as I describe in the changelog though.

As usual, you can download it and view the changelog by visiting the main website. http://www.imgburn.com/ Special 'Thanks' to all the beta testers, translators and donors!

Your drive is probably not very good a burning that media. You *might* have more luck with it at 4x rather than 'MAX'. If possible, try looking for a firmware update for the drive on the website of whoever made your PC. If all else fails (and I'd actually recommend you do this anyway), switch to some better DL discs. Verbatim 2.4x DVD+R DL (MKM-001-00 dye) are the ones to go for.

Auto doesn't really exist in the way you think it does... 'AUTO' just means that the program uses whatever speed you've configured in the 'Automatic Write Speed' feature. There's a guide to explain what it does and how to use it.

You've already made your mind up so lets just leave it at that. Stick to using a different program if ImgBurn doesn't work on your system. It's free so it's not as if you've lost anything.

Yes, the CUE file is the important thing. If you don't have one for a given set of files you can use ImgBurn to make one. If it's embedded (and ImgBurn supports the file type as an image - i.e. can extract the embedded CUE from the audio file)), you can just try and load/burn the audio file directly as if it were an image.

You really should. Firmware is just the software / OS for the drive and like all other software, it's important that you keep it up-to-date. If you don't update it, you'll stay running 'Windows 95' for the rest of the drives life

Formatting is different to erasing. DVD+RW need to formatted before the drive will accept any 'Write' commands. ImgBurn extends on that slightly and basically, unless the disc info on the right states 'Formatted: Yes' for a DVD+RW disc, ImgBurn will prompt to format it. (that status comes direct from the drive) Once it's been formatted properly by ImgBurn you won't need to format it again unless another program messes it up - or the drive didn't do it properly in the first place (bad media support?). If there's something on the disc and it's formatted properly, ImgBurn will just use what's known as 'direct overwrite'. That's to say you can just issue write commands to sectors that already have data on them without the need to erase them first (this is where DVD-RW is inferior because it would need quick erasing first). A full format on DVD+RW disc at 4x would indeed be about 15 - 20 minutes so there's nothing to worry about there. From your log I'd have to guess that the drive/firmware doesn't like that media, there's a 1.07 firmware update available so I'd try that first. http://www.pioneer.eu/files/support/BDC/BDC202_FW107EU.zip

Update your firmware, it might improve support for the media you're using. http://www.liteonit.com/DOWNLOADS/ODD/SOHW...re/DR16KS0B.zip If it still doesn't work you'll have to get yourself some Verbatim 2.4x DVD+R DL (MKM-001-00 dye) discs instead.

4 of them are SATA the other 2 are IDE 2 are on an ICH9R controller (running in the proper 'optical drive friendly' ATA mode). 2 others are on a Silicon Image 3512 PCI controller card. The 2 IDE's are on a Silicon Image 680 PCI controller card. I know I only mentioned 6 drives but I actually have a cupboard full of them dating back several years. What you have to understand is that it makes no difference to the program (well, programs in general) how the drives are connected. All drives follow the MMC specs (available from www.t10.org) so they all talk the same language and that's independent of the interface used. Drives are like cars, they might have different engines to make them go faster but at the end of the days the user still deals with a clutch, brake and accelerator. If you push the accelerator and the car doesn't respond then there's something wrong with the car. It's no good trying to blame the user saying their right foot doesn't work when it's pretty clear that it's fine - and you'll know that because they've shoved it up your arse to prove it.

It won't do an on-the-fly copy, no. Why not? I haven't gotten round to it. Will it ever? Probably. In the mean time you can follow the 'how to copy a disc' guide in the Guides forum.

lol yeah and then we'd need a thread to correct the translation of the thread correcting the german translation.