Hi,
Firstly, I wouldn't use the Add Duplicate function unless such
usage is warranted..ie; if you're trying to debug a program, and
the test bottle has a prepared makeup (includes runtime dependencies
and the like), then I would use Add Duplicate to save myself time
having to setup that bottle content again -- the other 99% of the
time, when just adding a new pristine bottle, creating a new bottle
with the Add function (not add duplicate) is preferred...
As to your problem (and, here, also answering your other post), I
think you're trying to get something running, and that something
(or a process associated with it) is crashing, leaving an orphaned
process running in your tasklist -- when this happens, it's entirely
possible to delete the bottle from the CX bottle manager, but the
bottle lock will be held by the rogue process. Even though the bottle
in question may appear deleted in the CX GUI, when you try to add
(or duplicate) a bottle of the same name, you'll hit the bottle lock
instantiated from the previous execution of the win32 app, and CX
will return the error you're seeing.
This aligns with your other post about rebooting the OS fixing things.
All that's happened is the rogue win32 got killed off during the reboot,
released the bottle lock as consequence, and as such everything will
start working as expected again....
...so, most of this is procedural...not a bug perse. If you discover
something like this happening, check your Activity Monitor for any
wineloader processes still running >after> you exit Crossover -- there
should be none. Alternately (and somewhat as rule of thumb on OSX), if
you're trying to get something going and it's being problematic, it's
always advisable to routinely click Quit or Force Quit bottle after a
test run, to ensure all win32 apps in that bottle have shutdown.
Cheers!
