c:\\windows is not accessible message

[Mike Hearn]

Hi guys,

It seems quite a few people have been seeing this message lately, and I'm
not sure why. This occurs even with a non-existant ~/.wine directory, so
wineprefixcreate should set up a correct system for them.

Examples:

http://www.linuxquestions.org/questions/showthread.php?s=&threadid=204255&hi...
http://forums.devshed.com/archive/t-166324

This one seems to imply that the symlinks aren't being created properly:
http://www.winehq.org/hypermail/wine-users/2004/07/0022.html

but that sounds like a migration issue rather than something you'd
see with a clean .wine

If anybody has any ideas I'd love to track this one down. I am wondering
if it's to do with packaging, I have never been able to reproduce this
with Wine CVS builds (ie from source) but I know some packagers are still
shipping custom ~/.wine building scripts.

thanks -mike

[Dan McGhee]

> http://www.linuxquestions.org/questions/showthread.php?s=&threadid=204255&hi...

I'm farmerdan in this thread.  I used to get this message when I first 
started using wine.  It came when I tried to use the windows partition 
AND when I had installed wine from a package.

I have not recreated it since I have learned to use a "fake" windows, 
but I suspect that this was a symptom of either a packaging error or the 
bug that got corrected (Bug 2356) in the latest snapshot.
> I am wondering
> if it's to do with packaging,

I think it does.

Dan