On Tue, 09 Nov 2004 21:25:05 +0100, Holly Bostick <motub@xxxxxxxxx> wrote: > > In all of this discussion, have we in fact checked the error itself; > i.e., is the folder that Wine is using for /temp valid? Well, you're basically right Holly. I have asked a couple of times for the dosdevices part of the equation, but not the specific temp directory. > > Wine by default uses /temp (the Linux temp folder) for its temp folder. Depends, I think. What I see is that with the newest versions of Wine you do not get a config file. This means I jsut don't know where the temp directory is. However when I copy in an existing config it has an entry "Temp" = "c:\windows\temp" so that would place it as a directory in his home account. If the directory doesn't exist then this could certainly be the issue. > > Does the user have write permission to this directory? If not, any > attempt to install anything will fail, because most (if not all) > installers extract files to /temp before the install begins (that's what > that progress bar on the InstallShield installer is doing, that's why > you have to wait a few seconds before the big blue install screen pops up). > > The other issue (somewhat related, actually) > > Warning: the specified Windows directory L"C:\\Windows" is not accessible. > > is an error we've seen several times when people who had an > "old-fashioned" Wine install (pre-dosdevices) try to upgrade to a > "new-fangled" Wine install-- and doesn't SuSE install some old version > of Wine during its install (in the name of user-friendliness)? > > I forget atm how it is solved, but the answer is surely in the archives. A little Googling resulted in the always fun 'rm -rf .wine and run wine again to create a new .wine directory'... Take care, Mark _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
