Mike89

Thanks for the info. Yeah it was kinda weird. It wasn't try to access the drive Imgburn was using, it wouldn't let me access my other two DVD drives (the ones Imgburn was not using). When unlocking the drive in Imgburn, when Imgburn was using one drive, the other program would then let me access the other drives. That sounds like a strange glitch.

I have 3 DVD burners. One SATA on it's own channel and the other 2 on 1 IDE channel (my mb only has 1 IDE connection). As long as I burn using a combination where the two on the IDE channel aren't burning or off loading at the same time, I notice no slow down at all. I can even pull up two instances of Imgburn and burn on each one at the same time with no slow down at all. I can also do other things while all this is happening with none or negligible slow down (of course there are limits to that). The nice benefit of having a dual core cpu and having DVD drives on separate channels. My 2 HDDs are also on separate channels so I can go from one HDD to DVD Drive (or DVD drive to HDD) and the other HDD to DVD (or DVD to HDD) at the same time with no slow down. I figure since I've spent all these bucks for the system I built, I might as well utilize its capabilities. I like to test the system, to see what it can do and what it can't.

I had an issue where when burning an iso with Imgburn, another program I was running at the same time would not burn on another drive. It couldn't find the drive. I took the check out of the "Lock Volume - Exclusive Access" in Imgburn and that fixed that problem. I could then burn at the same time from Imgburn to one drive and another program to another drive. Is there any disadvantage to just leaving that box unchecked all the time? What's it even for?

Like RipIt4Me perhaps?

Thanks. I'll have to read the rest of the message next time I get it to see which of those two it is. Seems if it was the first one and it was drivers, I would get the message every time. This issue is very recent within the last couple of weeks and so far I've only seen the message maybe 3 times in 20 burns . Seems it would be every time for the second one too. Clicking "continue" starts the burn without further issues.

Sometimes when I try to burn, at the beginning I get a message, "Failed to Lock Volume". It says some other stuff too, didn't take a screenshot. The options then are, "retry", "cancel", "continue". If I click "Continue", the burn then takes place as usual. Dunno why I'm getting this message or what it means, and as I said, it doesn't happen every time.

As far as the 4x burning speed thing. I had posted once about my using the Max setting for burning using Memorex 16x DVD+r disks. My stubborness was disputing the holy grail of 4x burning. Needless to say I got the crap kicked out of me over this from those who knew a lot more about it than I did. I ended up being convinced of the errors of my thinking (more like getting my arms pinned behind me and screaming uncle). I then unceremoniously surrendered and I don't use Max anymore for burning (I did learn a lot about it through the process and I don't use Memorex anymore). Heh heh. That's what made me wonder if the read speed (in Verify) should also be slowed down.

I know most still recommend 4x for burning DVD ripped files. Does the same hold true when using Verify (read speed)? The default is set to Max.

I use an old program from my 98 days called Hotshot. Still works great.

Reading this thread so far, one word comes to mind. "Ouch"

Changed my post above before I read yours. I think I have a case of dumb ass itis!

Duh! I see it now (he says sheepishly) :&

Everytime I burn, the Verify box is checked on top. I have looked in the options to have this unchecked by default but I don't see it. How do you do this?

I wondered about this same thing myself when I was installing Imgburn 2.0. I stopped dead in my tracks and came to this forum when I saw that message. I was tripping if choosing yes was going to affect when a program was calling DVD Decrypter (like RipIt4Me, and Pfcedit with plugin). I did choose yes so I'm assuming now that there will be no issues with my above scenario?

Thanks. I assume this 1.3 version doesn't have those slow down issues I saw posted about version 1.2?. I got a little nervous reading about those posted issues concerning 1.2 and never did install it because of that.

Do you have to un-install version 1.1 first or can it be installed over it?

Thanks UK. That was a good explanation. That helped pull some of that stuff that was floating above my head and bring it down where I could grab it. My wife says I still have a lot of stuff up there (and a lot of grabbing to do).

Hmm. I do understand the FAT32/NTFS thing (sort of, heh heh) It's the structure of the file system and not the files themselves. Tell me if this is close. You're saying burning from files or from an .img file is sort of like one is FAT32 and one is NTFS? If that's the case, then what is one advantage over the other? Why are programs doing it two different ways? Patience with me UK. I'm not in your league but I am interested in this stuff. If I don't ask questions, the stuff will remain over my head. Right? Heh heh

There's an 0.6.2 out now

This may be a dumb question but I'm asking it anyway. I have heard people request that Imgburn be able to burn from files in addition to from an .img file. I don't know what the purpose of an .img file is to begin with. Looking on any DVD, there are all the files (in the VIDEO_TS). Some programs burn from these files. Others like Shrink turn these files into one .img file and still other programs like Imgburn then burn from the .img file. Then going into the burned CD to look and you see the files again (rather than one .img file). So why turn the files into one .img file to burn, when the result is the .img is turned back into all the files again? Why this extra conversion when it seems easier just to burn from the files to begin with (when that's what you end up with anyway)?