Posted by Tom Fulton on September 15, 2004 at 06:15:01:
is still a problem at Grey Watkins. Although the Comet is now cut over to Windows Server, their Novell network is still in use and operating - so workstations still have Novell clients installed and
Novell protocol running. The symptom is that if Comet is idle for a
number of minutes ( operator answering a phone, doing an Email, etc. )
and then comes back into Comet, the first keystroke gets no response
for approximately 12 seconds. I connected up to a PC with PCAW and
counted the time myself. Once Comet starts up its response is fine.
I removed the one Power Management feature on the network adaptor ( written up in a thread below ) and I also wrote a program that would
activate in background and FSTAT a file on the server every 30 seconds
just to see if that type of activity would keep Comet "awake". That did not work either. So I'm somewhat out of ideas at this point. Any advice? Thanks in advance, Tom.