Don't have a copy of the debug message yet, I'm going to go work in the lab some more now, but I thought I should mention that this is running on a fresh installation, so the ~/.wine folder had just been created. I'm going to try a couple of things, including copying a working configuration from another computer, and if all of that fails I'll be back sometime later today with a copy of the debug message. Thanks for the help! Ian Daniel Skorka wrote: > iwoloschin@xxxxxxxxx wrote: > > Not sure if this is a good thing or a bad thing (guessing bad), but now > > I'm getting "unhandled page faults on read access" when I try to run my > > program. It's followed by what appears to be a dump from > > processor/memory that is entirely in hex, and while I can make out what > > each value is, I haven't a clue what they relate to. The computer I'm > > running on is not on the internet, but I may be able to get a copy of > > the error later today or early tomorrow if anyone thinks that would > > help. > > That would be very helpful, yes. Also, those 'wine client error' > messages relate to communication with the wineserver. 'Bad file > descriptor' propably means that either the wineserver just died or that > wine is trying to use an old file descriptor. Please try with a fresh > ~/.wine and a clean /tmp. > > Daniel _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
