>>>>>>ShellExecute doesn't return the value that GetExitCodeProcess needs. It returns the instance handle, not the process handle, which is what's required. If you were to start the process with CreateThread() I think (but am not 100% sure) that you'll get the value you need.
>>>>>
>>>>>CreateProcess(), not CreateThread(). CreateThread() launches a thread in the memory context of the current process. VFP has kittens if you try this...
>>>>
>>>>
>>>>Thanks Ed. I knew it was one of those two (I first typed CreateProcess()).
>>>>
>>>>BTW, I finally got MS Client for Netware going (don't ask about the gruesome details:-)). I'll post back on that other thread as soon as I've got some more info.
>>>
>>>Hopefully you had better results than I did; through at least version 2.2, Novell's Client32 didn't cleanly uninstall itself; short of a reinstall, the only thing that worked reliablywas to run netWare's Uninstall, then delete all the adapters that had attached to it, and readd them and their protocols and clients. Please tell me it was easier than that...
>>
>>I wish I could.:-( What you just described was just about what I went through. Had I known that the frame type for the IPX/SPX had to be set based on the net card (a 3Com Fast EtherLink XL) it might have been shorter. I had finally given up and was trying to re-install Client 32, when I decided to remove the card from the Device Manager and let it re-install itself. Then I set it on MS Client, and set all the IPX/SPX, TCP/IP and the rest of that stuff, re-boot and it came up. With Client 32, I could only get it to boot in Safe Mode. Only one problem, the video was real dim. So I removed the Video Card from the Device Manager, re-booted and I was finally back in business.
>
>The 3C905B? Great little NIC - that's what I run both here at home and in all the client workstations at Weatherhill (we use Bay Networks cards in the servers, mostly because 3COM was a PITA about drivers for NetWare 3.11/3.12 with the 905B.) Make sure you use the diagnostic to tune it for you, and if you're on a 100Mbit leg, run \WINDOWS\SYSTEM\DACONFIG.EXE -e (on NT boxes, it's in \WinNT\System32) to force the card to try negotiating a 100Mbit connection. There are new utilities at 3COM's Web page for the 905B Drivers
>
>You should have asked first...been there, done that, and burned the tee shirt once I got it!

Oh jeez, Ed. Yeah, it's the 3C905B-TX. And in my dispair, I thought, "I wonder if Ed (meaning you) knows anything about this." In fact, if I hadn't gotten this going today, I was going to either send an email or a private asking about it.

Many thanks for the URL, I'll be sure to check it out. I did take the diagnostics out of the system tray. Bad idea?