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. iwoloschin@xxxxxxxxx wrote: > I'm running wine 0.9.2 on a specialized Fedora Core 2 linux computer. > I've actually had this running in similar setups on several computers > now, along with a custom program. I had everything working, and it was > all very nice, until I moved to a new linux setup, so I know it's > something in the wine configuration, not in my program. It's still FC2 > and wine 0.9.2, but it's the "production release" version of FC2 that > was setup for me by someone in IT. > > Now when I run my program, it runs, but I get errors, both in wine and > in the program itself (caused by wine not running properly, I believe). > The one I've noticed the most is the subject: > > wine client error:b: write: Bad file descriptor > > I have no idea how or why this could be an issue, and while I haven't > really extensively tested anything myself yet, I decided to post here > in the hopes that someone else has had a similar problem and found a > solution. _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
