🚀 go-pugleaf

On Tue, 06 Mar 2001 06:19:45 GMT, "David Ray" <david@timecalc.com> wrote:

>>File opening should not be a slow process under NT.  If it is, it is at
>>least an indication that you are suffering some other network difficulty OR
>>the PC is just way, way too slow to be a server.

If the "PC" is too slow to be a Server, then I guess it is just an illusion
that my client is actually doing work every day, using said Server. Perhaps
the solution to your 'puzzle'  is that economics play a role in what is "too
slow" versus what is "acceptable performance."

As I noted, defragmentation created a great improvement. That was the purpose
of my post.

>>The structure of NTFS is such that file opens and closes are faster than
>>with any other popular OS (other than Linux, maybe...)

I never said it was slower than Apple or Netware. I just said it was
sluggish. Note that NTFS is a file system, not an OS.

>>
>>
>><r_brummel@NOworldnet.JUNKatt.net> wrote in message
>>news:3aa9870f.24370559@news.mindspring.com...
>>> I was stumped by a slow QB company file running from a slow 3-year old
>>> Server. But defragmenting the Server (NTFS drives) made a huge difference;
>>> while files still open sluggishly, once open they are adequately
>>responsive
>>> (ie no more sclerotic "Searching....." etc messages.) At least for now.
>>>
>>> So, I recommend defragmenting, particularly NTFS. (I used Raxco's Perfect
>>> Disk, which was discussed in the comp.os.ms-windows.nt.admin.misc forum (I
>>> think).
>>>
>>> Richard Brummel
>>>
>>>
>>>
>>
>>
>>
>>