wishiknewmore
Technical User
We have a problem with Windows 2000 Pro slowing down, running out of memory/resources
and even locking up.
Here is the background information. Previously, we had a Windows NT 4.0 domain server
and 10 workstations all running Windows NT 4.0. Our basic database program is Epicor's
Platinum for Dos v4.6. The db resides on the server and we login to each workstation,
not to the server. The program requirements are to un-rem the dosonly statement in the
config.nt file and change the files and buffers values. All went well with that setup.
Currently, we are still using Platinum, but are in the process of converting to a
completely new db program which requires Windows 2000 Professional on the workstations.
We have converted all workstations to the new O/S and upgraded the hardware as
necessary. Also, the config.nt file has been changed as required by Platinum.
Now, we're finding the problems as stated earlier. Using my workstation as an example:
My previous setup was a Pentium 3 with 128 MB RAM. I now have a Dell Pentium-4 with 256
MB RAM yet it is having all the aforementioned problems.
There are no more programs running at startup than before and the same applications are
being run on a daily basis for the same amount of time. I just can't put my finger on
the problem (other than the reset button). I'm wondering if the dosonly statement in
config.nt doesn't get along with Windows 2000.
Nothing has changed on the server, it's still running Win NT 4.0.
Can anyone enlighten me please.
Thanks.
Ron
and even locking up.
Here is the background information. Previously, we had a Windows NT 4.0 domain server
and 10 workstations all running Windows NT 4.0. Our basic database program is Epicor's
Platinum for Dos v4.6. The db resides on the server and we login to each workstation,
not to the server. The program requirements are to un-rem the dosonly statement in the
config.nt file and change the files and buffers values. All went well with that setup.
Currently, we are still using Platinum, but are in the process of converting to a
completely new db program which requires Windows 2000 Professional on the workstations.
We have converted all workstations to the new O/S and upgraded the hardware as
necessary. Also, the config.nt file has been changed as required by Platinum.
Now, we're finding the problems as stated earlier. Using my workstation as an example:
My previous setup was a Pentium 3 with 128 MB RAM. I now have a Dell Pentium-4 with 256
MB RAM yet it is having all the aforementioned problems.
There are no more programs running at startup than before and the same applications are
being run on a daily basis for the same amount of time. I just can't put my finger on
the problem (other than the reset button). I'm wondering if the dosonly statement in
config.nt doesn't get along with Windows 2000.
Nothing has changed on the server, it's still running Win NT 4.0.
Can anyone enlighten me please.
Thanks.
Ron