>>>>>>Has anybody else had trouble running VFP (3 & 5) under nt40? I've
>>>>>>installed it on 3 different computers and it only runs on 1 of them.
>>>>>
>>>>>Sorry, but I haven't had any problems running under NT4.0 (with 32M) -- several different computers, too. How does NT work otherwise? We've seen problems with an "L2" cache, but that wouldn't even let NT start....
>>>>
>>>>Ran it on NT Server 4.0 & NTW 4.0 (SP2) and no problems.
>>>>
>>>>Tom
>>>
>>>I've got a NT4 workstation connected to a Netware 3.11 server. I managed to get it running by removing the client services for netware and installing it, but now it locks up every time I get into it. (sigh) I'll keep trying.
>>>
>>>Thanks for the info.
>>>
>>>Greg
>>
>>We just discovered a problem today. Accessing data across our WAN was incredibly slow. We looked at everything. Finally, we formatted the hard drive and reinstalled NT 4.0. Everything works fine. So, the answer is, don't install a 4.0 upgrade over 3.5x. Reformat the drive and start from scratch.
>>
>>Craig
>
>This is a brand new system with only NT40 installed. I've had other problems with the system locking up w/o ever installing vfp also. I've reinstalled it 4 times now and everytime it just refuses to cooperate. One time I installed NT and then VFP before anything else and it still locked up. It's getting pretty frustrating on this end. Hopefully we'll get an NT server soon and that will solve some of the probs.

Greg

Lockups are generally because of hardware. Dr. Watson is generally software (or Blue Screen). A buddy of mine swaped out RAM & it cured his lockup problem. It was a purely accidental fix.

Tom