LIGHTNING UK!

Importing keys/values isn't a problem (obviously!), but if the program doesn't look for it, it's not magically going to add features to the program just by it being there! Or at least that's what I understood Movie Junkie's question to be asking. Would be a nice idea though... HKLM\Software\Microsoft\Windows BootUpInXSeconds = 1 AllowToCrash = 0

lol if ImgBurn is such an evil app, maybe I should pass the code to some virus writers so they can wreak havoc and destroy everyones dvd drives. Oh wait... what's that.... destroy hardware via a simple software application, that would be silly!

No, your 'sales' email address box is full. I keep getting NDR's from my email server.

lol how did you manage to lose stuff?! That program is just an exe within a zip file!

Any additional reg keys would be ignored. It would need that information to be coded into it before it could take advantage of the extra stuff.

cdcheck ?

All you could do is compare it against the original folder structure. Something like 'Beyond Compare' could do that with ease. Personally I'd just forget about that backup and carry on with the next one!

Yeah, that one of annoying things about old pioneer updates! The flash update program doesn't work with many IDE drivers. Use this 3rd party flasher instead. http://forum.rpc1.org/viewtopic.php?t=36448 Just extract dvrflash.exe to the folder you extracted the real pioneer flasher/firmware to. The from the command prompt window, change to that directory. ie. type: cd \DVR107D\FW122 The prompt should then say C:\DVR107D\FW122> Then type: dvrflash g: R7100107.122 Follow any onscreen prompts (cant help you any more because I don't have a 107 installed!)

In theory, yes. It could have corrupted the filesystem on the disc though so just be careful

That's quite a nasty error really. Quite uncommon when burning. Switching brands of discs doesn't mean a whole lot I'm afraid, it's the dye used by those brands that's important. If you've used some Verbatim discs with TYG02 dye, MCC dye, or some Taiyo Yuden discs and it still won't burn, I'd have to guess your drive is on it's way out. The Sony 530 certainly sounds old to me so please don't say it's a new one! If it is, take it back and try to buy something else.

Indeed, there is no conflict between two copies of app, but as shamus said, they wound share reg settings. If you change anything, the last copy to be closed down would be the one who's settings would be default next time you start up.

The ISO9660 volume label will always be as specified above. (A-Z 0-9 _) Like I said, the one you're seeing is the volume label that's part of the UDF (or Joliet) file system. Those filesystems DO allow for other characters.

Dude, where do you get the time! Do you have a day job? Other than spinning plastic all day?! lol sorry, I didn't mean I test ALL 40 drives every day.... that would just be silly! The ones that get tested all the time are the ones physically in my pc. At the moment they are: Plextor 716 Pioneer 110 NEC 4551 BenQ 1655 LG 4166 NEC 4550 BenQ 1640 LiteOn 1635 The others sit in a cupboard and get swapped in and out of a some external ubs enclosures when the need arises.

It's perfectly allowable to have different volume names for ISO and UDF file systems. Windows etc will read the UDF one by default anyway. As corny said, just make sure you only use uppercase letters, numbers and the '_' in the ISO one.

There is no problem with doing this, but it works best if all devices are on their own channels. Reading from/sending to devices on the same channel will give much lower performanace. So the best setup would be something like. Hdd 1 - SATA Hdd 2 - SATA DVDRW 1 - IDE 1 - Master/Slave DVDRW 2 - IDE 2 - Master/Slave. The Sata Hdd's could of course be scsi.... basically just anything other than on the IDE ports with the dvd drives. With that combo you'll get full speed from both programs (or at least you should do )

You can't do that. Converting PAL to NTSC means re-encoding the entire disc. You should be able to find a guide to do such things via Google if that really is a path you want to take. To save yourself time in future, probably best you stick to buying NTSC discs in the first place! Apologies for sounding negative before. Please remember this forum is for ImgBurn. It's not about helping people mess around encoding / stripping down dvds. There are plenty of other forums that do that and do it way better than this one.

I expect something else running on that PC already has control of the drive and has 'locked' it so nothing else can use it. Follow the post in the FAQ about finding out which other program is accessing your drive and why 'lock volume' fails with an 'access denied' error. You might then find out what's causing it. It involves using 'Process Explorer'.

You can't change the booktype of a +R DL disc at that precise second, it'll happen when you burn it. Yes it is possible your Pioneer doesn't support +R DL. Maybe it will once you've got the booktype bit sorted. Also have a look for any firmware updates, maybe there's a newer one that supports that media without the need to change the booktype.

No software has anything to do with PIE/PIF stuff. The program sends a 'Write' command and passes the drive the data, that's all it does. The drive and it's firmware controls how well it actually burns to the media. Keep an eye on it if/when you burn any more and see if it really is consistently higher. Maybe alternate between 1.1.0.0 and 1.2.0.0 so you're comparing over a larger number of burns.

Come on kirk, pick those toys back up! Nobody wants you gone, you're one of the old timers!

I'm pretty sure you answered this yourself in your other thread?! Your player can't play discs with the wrong TV system type - i.e. NTSC or PAL. If it's a region free disc, there can't really be any other reason for it to not work.

Windows always caches files as programs read them. Recently however, they stopped doing it if you read in 64kb chunks at a time - size may also be a factor, I don't know, I didn't code windows Because I switched to reading 256KB at a time - in an attempt to lessen the workload - I made windows think it wanted to cache the files again. It's a shame I didn't notice the ram going on my pc.... but then like I said earlier, I have 2gb and never burn off my C: drive. It has been fixed for a couple of days now, just doing some other little bits and then I'll release 1.2.1.0. Sorry for any inconvenience caused

Look at all the logs in the media forum - yes, there's about 250 of them. Oh funny, it shows the names for all of them just fine! Hmmm strange that it just doesn't work for you drive. Must be a glitch. LOL Feedback is valuable to me, yes. I take bug reports and suggestions very seriously unless I know them to be complete bullshit. Again, take a look in those forums and see for yourself. What you're accusing ImgBurn of doing (stuffing up your drive) is total nonsense. I don't send any nasty commands to the drive and so if it messes up, it only has itself to blame. It's like me asking you to walk forwards and you taking it upon yourself to walk in the direction of an oncoming bus. If you get run over, that's your fault, not mine. Does it not occur to you that something as serious as killing drives MIGHT just have been reported elsewhere if it were a real issue?! Software that's been around for 3 years would have generally had something written about it if that was the case. I have about 40 drives in total now, testing the program on a daily basis. Not once have I had anything go wrong with them. Going back to the media forum, those 250 odd logs prove it works with several drives without killing them, and on pretty much every bit of media we could find. You can see that with your own eyes. I'm sorry but all that really doesn't work in your favour.

No, it says it doesn't support cue files A bin can be a simple disc image. ImgBurn examines the bin to see if it's a data one. If it is, chances are it can burn it. It knows it can't do audio and the image won't pass the internal checks. Audio CDs are burnt differently to Data and one would have to consider multiple tracks - something ImgBurn doesn't currently support. I think it says single session / track images. Like I said 2 seconds ago, ImgBurn doesn't support multiple tracks (or sessions). The number of files going to make up that image is not really relevant. Normally, the second (small) file that these other programs produce is just a file that describes the data in the bigger one. The most common being the CUE file. No, a mono audio file is not a single file... you're totally lost here You cannot in any way, shape or forum burn a CDDA disc/image with ImgBurn. If I ever get around to adding support for multiple tracks... THEN it may well be possible. Until that time, best stick to using whatever read the audiocd in the first place.

The program follows the MMC specs. All drives since about 2000 are supposed to follow them. As such, there is no need for a compatibility list. Oh and according to the log, your drive reports its name as ATAPI DVD RW 8XMax 150D I see no 'name' in there, nor do I see 160D firmware. Like I said earlier, I don't like guessing games so I can only go on the info you provide. Recommended media is what 9 out of 10 forums tell you to buy. i.e. Verbatim (MCC dye), Taiyo Yuden etc. Drive wise, go for the big names. NEC, BenQ, Plextor, Pioneer, LiteOn. Those makes are popular for a reason... they tend to work and generally have decent firmware with frequent updates! This arguing is getting us nowhere. If the program isn't working for you, and you're still looking to blame the program rather than anything else, go find some other tool to do your burning. It's free to use so just cast it aside and forget you ever set eyes on it.