The system is FC5 and wine is the latest .17. There are two users configured on the system, A and B. They are configured to be as alike as possible. Diff of set output shows only the expected differences. Wine is built from CVS. winecfg is configured to the same profile with only the appropriate user path names changed. The problem is wine works well for one of the users and not well at all for the second. The second user gets error 2's on freecell cards.dll, it gets a read error on a second program, etc. Some programs do run, such as sol.exe and notepad. This is really confusing. Where would I even start to debug this? Thanks - Dan
Start by moving away each user's .wine directory. If the systems are working properly and wine has no configuration yet for that user, then it should work. But if wine's configuration exists and is broken, it won't work. On 7/23/06, Dan Sawyer <dansawyer@earthlink.net> wrote:> The system is FC5 and wine is the latest .17. There are two users > configured on the system, A and B. They are configured to be as alike as > possible. Diff of set output shows only the expected differences. Wine > is built from CVS. > > winecfg is configured to the same profile with only the appropriate user > path names changed. > > The problem is wine works well for one of the users and not well at all > for the second. The second user gets error 2's on freecell cards.dll, it > gets a read error on a second program, etc. Some programs do run, such > as sol.exe and notepad. > > This is really confusing. Where would I even start to debug this? > > Thanks - Dan > > > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users >-- Vincent Povirk
Actually, come to think of it, dosdevices could also cause problems. c: needs to point to ../drive_c, since that's where Wine puts its c: folder (and using a c drive from real windows won't work properly). z: should also point to / or Wine might not be able to give a dos filename to some files. If c: points to something called fakewindows, that probably means the .wine folder was created for an old version and could explain why things aren't working. On 7/25/06, Vincent Povirk <madewokherd+d41d@gmail.com> wrote:> That should be ok, but I don't think Wine will figure out that it > needs to recreate the registry and fake C drive. You can do that > manually by running wineprefixcreate. > > On 7/25/06, Dan Sawyer <dansawyer@earthlink.net> wrote: > > Thank you. Would it work as well to erase everything except dosdevices? > > > > - Dan > > -- > Vincent Povirk >-- Vincent Povirk