Hi ramcorp,
Good day and thanks for your question.
There are a number of reasons why the slowdown occurs.
1. Are the files located in the "My Documents" folder? If so, try
changing the location of the files. I've read about a memory leak in
one of the routines of mydocs.dll. The mydocs.dll file is associated
with the "My Documents" folder.
2. If even after shifting the files (or the folder the files are
stored in is not "My documents"), is there possibly a large number of
files in the folder? If so, create new folders and spread the files
over these folders.
3. Make sure that Windows 98 automatically handles your virtual memory
settings. Lack of memory could be a cause for the slowdown.
4. Try running utilities like Defragmenter, and Norton Optimizer.
Disable Rambooster if you're using it. Make sure as few as possible
background programs are running. Background processes hog up the
memory and processor.
5. The hard drive may be getting full. Operating systems need a
certain amount of hard drive space for "swap files" (these are files
used to store data in order to free up more of the computer's RAM for
the application you're currently running). One Web site I visited said
that Windows needs a minimum of 200MB free hard drive space; the rule
of thumb I've always heard is to keep at least 10 percent of your hard
drive space free, though this depends on the size of the hard drive
you've got.
6. You may need more RAM. But if you're running an operating system
that needs a bit more RAM than you've got in your computer, that will
definitely slow things down at startup. You should have a minimum of
32 megabytes for Windows 95 and Windows 98, 64 MB for Windows Me, and
128 MB for Windows 2000 and Windows XP.
I hope one of the above solves your problem. In case you have any
clarifications, then please don't hesitate to ask. Also include your
System Configuration please.
Thank you for using this service and have a good day
Warm regards,
Aditya2K |
Request for Answer Clarification by
ramcorp-ga
on
03 Nov 2002 10:38 PST
The question relates to not just one machine but several that I work
with. The data is in numerous folders on some systems and in the My
Documents folder on others. The data is stored on a Windows NT 4.0
server, a Windows 2000 server and locally. The problem seems to exist
across all instances. Each of the machine have at least 256 MB of RAM
and there is >20% HDD free space. Defrag and scandisk have been run on
the local systems.
|
Clarification of Answer by
aditya2k-ga
on
03 Nov 2002 11:10 PST
Hi again,
Now that you mention that there are a number of systems invoved, it
changes the entire scenario.
Whenever data is to be accessed from a remote PC, time is taken in the
transfer of data in packets (fragments of data). It has to first
establish a connection to the remote PC. Once a connection is
established, Windows (NT or 2000) loads the profile settings for the
user. This takes a bulk of the time. Once it is established that the
user has the rights to perform the action requested, it goeas ahead.
You also mention that even when accessing data from the local machine,
it takes time. Do you possibly connect to a terminal server and then
access the data? If this is the case, then the data has to be sent to
the terminal server, and the above explanation applies
Another thing that slows down the operation of a system is the
presence of a virus scanner. All files capable of being viruses
(.exe,.dll etc.) are scanned when initiated. It would not be very wise
to switch the scanner off, especially in a network. Even if the
scanner slows down system operation, it would save a lot of time in
the event of a virus attack.
Cheers,
Aditya2K
|
Clarification of Answer by
aditya2k-ga
on
03 Nov 2002 11:14 PST
One more thing just came to mind. Do you by chance have mapped drives,
i.e. drives assigned to network paths. These drives are typically F:,
G: through Z:
The running of Virtual CD, or such programs which create virtual CD
drives could also be the culprit.
I mention this because the "Look In" drop-down box in the 'Open File'
dialog in MS Word first loads all the drives, and if you have mapped
network drives, the connection first has to be established. There is a
considerable time delay. In case you have a number of mapped drives
mapped to various computers, a lot of time is spent in first
connecting to the computers and mapping the drives.
Please tell me if I am on the right track or not.
Cheers,
Aditya2K
|
Request for Answer Clarification by
ramcorp-ga
on
03 Nov 2002 18:09 PST
Thank you for your answers but I perhaps am not making myself clear.
Although I work on several machines, they are not all connected via a
LAN or WAN. I am not attempting to access data remotely in the sense
of a terminal session for example. Yes I do have mapped drives but
when I request files open on mapped drive "W:" for example, the only
files that I am seeking to load and that eventually do load, are those
on the mapped drive or partition. This is where the delay takes place.
I have tried turning on Microsoft Find Fast, to no avail.It seems that
once the drive has been accessed once, there is not the same delay.
Following that logic, I included a "host" file to direct the
workstation to the specific location of the server. That did not work
either. I do have anti virus programs running but they are different
in each location; Norton, PC cillin, AVG. I also have a software
firewall, ZoneAlarm Pro, running at two locations. I have a hardware
firewall, Sonic Wall, running at the third location. I know that this
is a lot of material, but I wanted to clarify the scenario as much as
possible.
|
Clarification of Answer by
aditya2k-ga
on
03 Nov 2002 22:21 PST
Hi again,
One of my fellow researchers (duncan) suggested that the problem
sounds like a network authentication delay, the type of delay that
might be caused if the client computer is running Win9x and has set
the client for Microsoft Networking to "Quick Logon". In this mode,
mapped network shares aren't connected until the first time they're
used, causing delay on first access.
The alternative would be to go into the network control panel, select
the properties of the client for Microft Networking, and switch from
"Quick Logon" to "Logon and Restore connections", which states that
"When you log onto the network, Windows verifies that each network
drive is ready for use."
Slows the initial login process, but might mean no initial delay
during first file open dialog.
Cheers,
Aditya2K
|
