Hi Tom and listers,

I remember back when I was a kid and My Dad went to the doctor because his
shoulder was hurting him.  The doc asked what caused the pain.  My Dad
explained that when he reached over his head and slightly behind, his
shoulder really hurt.  The doctor simply said,
"don't do that".

I guess what I'm trying to say is that if your 133 megahertz computer works
with everything else you want to do, then echo link just demands too much
out of the slow computer.  You might try an external synthesizer with echo
link as that will reduce the work load on the computer.
Bob Tinney, K8LR, [log in to unmask]
Peace takes Brains!
----- Original Message -----
From: "Tom Behler" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, March 07, 2003 11:42 PM
Subject: echolink on a dinosaur computer


Hello all.

Please try not to laugh too hard at this question, but here goes:

I am trying to get Echolink to run on an old Pentium 133 Dell computer in my
ham shack.  It has a windows 98 SE operating system, 128 megs of RAM, and I
am using Jaws 3.7U.  The computer has a 56K modem.

The computer constantly gets hung up in the middle of operations.  In fact,
I can't even get through the echolink test, which can be accessed by
clicking on node 9999.

Could it be that this computer is just too obsolete to handle echolink, in
conjunction with Jaws?

Does anyone know of anything I can do to solve this problem, short of
putting the old computer to rest and sending it to the great computer heaven
in the sky?

Any suggestions would be appreciated.

Thanks as always, and best 73 from Tom Behler:  KB8TYJ