Hi everyone,

I'm still something of a Linux newb, so bear with me.

I'm running FC3 (fully updated) on a 2.4GHz P4, 512MB RAM, etc.

I'm attempting to run an in-house windows application in Wine. Wine has been running fairly well, although I've only got Remote Administrator and IE running in it successfully so far.

I went through the application installer, which seems to have gone through fine (albeit slowly). Before that I installed the windows ODBC drivers required by the app. They installed fine as well.

When I try to launch the app from a terminal, I get the splash screen, and then it exits with the following error:

Googling seems to indicate that this is an X problem, but I can't find anything useful. I tried editing the /etc/wine/config file to tweak the display settings, but it didn't make a bit of difference. Can anyone give me some direction? Once I get this, pcAnywhere, and outlook or evolution working I'll be able to completely be rid of windows! Thanks!

Steve

It sounds like your application is attempting to directly address the hard drive. Wine emulates a 32-bit Windows OS.

That makes it most likely a 16-bit application that won't even run on Windows NT. What are the system requirements for the app?

Honestly, I'm not sure exactly what the req's are. I can tell you that it's a hog. In Windows, it takes me what feels like two minutes to start the application. I know there are a few places in the company that run it on 98 boxes, but most use 2000 or XP.

Most of the reasons it's sluggish are network/DB related. The application connects to a database server , and because I have access to all of our branches, I have to connect to each of their individual databases (probably 40-50 databases spread over three SQL servers).

I can't imagine that it has much, if any 16-bit code. The original version was only developed a few years ago, and has never run on anything less than Win95. There would have been no sense in including 16-bit code. For the record, although this is an in-house application, we do have a lot of developers working on it, although I don't think any of them are interested in Linux compatibility =).

Steve

I found this link: http://www.accelrys.com/support/life...W_MESSAGE.html

Which is unrelated to my application, although it mentions that files owned by nobody cause the error for their application.

I ran ls -ARl /path | grep -i nobody and found a few files that didn't lok like they were related. I searched each major path individually, since scanning /dev gave me some issues, as did scanning some mounted smb shares.

I changed ownership of all of the files that came up as owned by nobody to root. It didn't make a difference.

Bump!