>Hi,
>
>I checked to see if anyone has reported this problem in the past year, but no one has, so I hope someone out there has experience with it. I have an installation running a LAN that has just been upgraded to Netware 5, using Netware Client 4.5. The workstations are running NT SP5. When they try to launch the FPW26 application (as an EXE) they get this message: WinExec Failed -- Error code = 8. Any ideas why? Is it possible that there is no support for 16-bit Windows applications in the Netware 5/Client 4.5 setup?
>
>As always, your help will be most appreciated. This forum is a life-saver.
>
>Regards,
>
>Cheryl Royle
>British Virgin Islands
Doesn't look good - on the Novell site
http://support.novell.com they show a Technical Information Document (TID) 10026153 (March 17, 2000) with contents as follows:
Fact
Client32 3.1 SP2
Client32 3.1 sp1
Client32 3.2
Novell NetWare 5.0
NW5
Novell Netware 4.11
NW4.11
Custom Foxpro 2.6 application
--------------------------------------------------------------------------------
Symptom
Foxpro application error running application on NW5
Foxpro application error: Winexec failed error code = 8
Foxpro application error after upgrading from NW 4.11 to NW5.
--------------------------------------------------------------------------------
Change
Customer upgraded the server where the application is being run on from NW 4.11 to NW5.
--------------------------------------------------------------------------------
Fix
Customer chose to run their application on a NW 4.11 server since they cannot find out anywhere what Winexec error 8 means.
******
From this TID it looks like Novell doesn't know what the error means; you might want to try MS.
You could also try setting the Client 4.5 parameters that relate to caching, file and record locking etc. to their least aggressive settings.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up