Jump to content

"Locking volume for Exclusive access" problem


tuck1s

Recommended Posts

I have been getting this "Locking Volume for Exclusive Access" problem repeatedly, under version 2.4.0.0. Just upgraded to latest 2.4.1.0 and still got the same problem.

 

I looked at the FAQ here: http://forum.imgburn.com/index.php?showtop...xclusive+access

and downloaded / ran Process Explorer.

Searched for processes using handle 'cdrom' and saw that the (frozen) imgburn.exe and task "cisvc.exe" are using this handle.

 

According to this site http://www.liutilities.com/products/wintas...slibrary/cisvc/

the task is part of the Windows OS and should not usually be killed.

 

I killed it anyway, imgburn.exe then got the drive exclusive lock and was able to make the burn.

 

Has anyone else seen this particular task locking the drive?

Has Microsoft changed something in Win XP that now upsets imgburn?

 

Can Imgburn give us more helpful options in interactive mode, other than just having to wait 5 mins for an error message?

 

Seems like this needs a bit more investigation/debug. Happy to help if I can.

 

BR

Steve

Edited by tuck1s
Link to comment
Share on other sites

So it's part of the indexing service really, doesn't sound that important to me?!

 

Maybe you can use this info to disable it for your optical drives - you might need a disc in the drive first?

 

http://nzpcmad.blogspot.com/2007/01/window...hard-drive.html

 

There should certainly not be a 5 minute wait. The program retries the lock 5 times before erroring out, with a 1 second pause between each.

 

If it's taking significantly longer than that then the OS is holding onto the function call for a LOT longer than it should do.

 

Maybe it tries to ask the programs to let go of the handle and they're just not playing nicely - so the OS has control for 1 minute per request or something (which ImgBurn doesn't know about).

 

I've never seen it take anything more than 5 - 10 seconds to bring up the error box or I might have already done something about it (i.e. not performed so many retries!)

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.