The same thing just happened to me!
I just got very similar results, doing something after upgrading my system that I had been doing in the predecessor system with no problems:
| Warning: the specified Windows directory L"c:\\windows" is not accessible.
| Warning: the specified System directory L"c:\\windows\\system" is not accessible.
| Warning: could not find DOS drive for current working directory '/foo/bar',
| starting in the Windows directory.
| wine: cannot open (null)
I had been using SuSE Linux 9.0, and just upgraded to 10.0. I'm wondering whether it's more than a coincidence that both Matt and I were using SuSE versions that probably have a lot in common with one another. (BTW, "/foo/bar" is not the actual name of the directory where I was at the time - I just edited the message, since the directory name is not important. However, the directory does exist, and it does contain the same thing it always has. I have the old system on another partition, so I can prove that things still work (I assume) under SuSE 9.0).
I'm wondering whether wine could be trying to look in the "windows" directory because it can't open a DLL or some such.
Ahhhh. After carefully reading all the postings in this thread, and doing some poking around based on what I learned thereby, I've solved my problem, and suspect the same might work for Matt.
It turns out that I had copied my old ~/.wine directory and its contents from my old home directory when I did an upgrade from SuSE 9.0 to SuSE 10.0 - which I think gave wine indigestion. I just renamed the old .wine and ran winecfg, letting it create a new .wine dir. Now all is well.
BTW, I tend to think that all that speculation about NTFS partitions and such is a red herring - it has nothing to do with the problem, afaik. I'm running from Reiser and ext2 filesystems, partition sizes from 5 gigs to about 30 gigs. There's no Windoze nonsense involved, since everything lives on Linux filesystems.
Last edited by linluvr; 12-02-2005 at 04:41 PM.