Hi, I recently wanted to try out the new 0.9.53 version (previously I had 0.9.35 installed), so I downloaded it from http://wine.budgetdedicated.com/archive/index.html (32-bit for Ubuntu Edgy, though I'm on x86_64) and installed it (did dpkg -r wine before), which went fine. Then I went on trying out some programs, but upon starting (say, winecfg), it filled the screen with messages like> err:wineboot:ProcessWindowsFileProtection WFP: L"dpcdll.dll" error 0x800(about a hundred or so) which I attributed to my Windows C: partition being mounted read-only. It did start, but I didn't want to wait the half-minute, so I re-mounted the C: partition as read-write (which, in hindsight, I shound't have done!) and all went fine... But, now I can't seem to logon into Windows. It boots up to the login window, but when I actually log into my account, all it shows is the wallpaper. I ran Code: find /c -daystart -type f -mtime 1 -mmin -$((2*24*60-14*60-28)) -mmin +$((2*24*60-14*60-32)) to see what has changed on the C: partition when I ran Wine (which I've narrowed down to the time shown, namely yesterday between 14:28 and 14:32), and it came up with about 1000 files in c:/windows/system32 ... Has anyone else experienced something similar? Any other ideas what might be the cause? (I first though maybe it has messed up some configuration files, but their modification times are later (well, ok, I did login after all)). Why does Wine have to write to the Windows partition anyway?
On Thu, Feb 28, 2008 at 10:29 AM, helix <wineforum-user at winehq.org> wrote:> ... which I attributed to my Windows C: partition being mounted read-only. > It did start, but I didn't want to wait the half-minute, so I > re-mounted the C: partition as read-write (which, in hindsight, I > shound't have done!) and all went fine... > But, now I can't seem to logon into Windows. It boots up to the > login window, but when I actually log into my account, all it shows is the wallpaper.Hang on a sec. Why were you pointing Wine at a real Windows partition? Are you saying your Wine's C: was your real C:? That's not been supported or encouraged for years. If people are actually doing this, we should consider putting in a check to make wine abort when it detects this. - Dan
I don't think I ever explicitly said Wine to do so, but I went on because I thought it would need some configuration file or the like (although it was obviously searching for dll's, which I thought weren't needed?). And yes, it's a real Windows partition. Maybe, in the past, I configured wine to have its c: as my /c (in winecfg), so it came from there, but I thought that was just for having some paths set up in the Wine environment...
This is what I meant when I said I have its c: as my /c: (/windows/C is the same) [Image: http://xs124.xs.to/xs124/08094/winecfg606.png ] Can anyone please tell me where Wine looks for the path of the system files (some config file supposedly)? If I get it right, it's supposed to use the system files in ~/.wine/drive_c/windows/system32 or /usr/lib/wine, but apparently mine is looking in the wrong location...
What do I have to do to stop users doing this. Wine and Real Windows are not compad with each other at all. Think of it of trying to installing windows 2000 and XP in the same directory and expect to use both. Wine can share drives with other wines without many problems. XP can share drive with XP running on different hardware if you are really careful. Only solution to this is move wine to its own drive C and run a XP repair to remove the wine files from XP. Yep XP not working because Wine altered things to what they should be for wine.