| |
KB2VXA > IBM 02.06.03 21:01l 39 Lines 1456 Bytes #999 (0) @ WW
BID : 8452_WT3V
Read: GUEST DB0FHN DC9BM
Subj: Re: G0EMM > COM 2
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<WA7V<VE1ATT<WB0TAX<KB2TXP<KB2FAF<WB2VPY<
WA3LWR<W2LV<WA2SNA<WA2PNU<KC2COJ<WT3V
Sent: 030602/1755Z @:WT3V.#CNJ.NJ.USA.NOAM #:8452 [Lakehurst] $:8452_WT3V
From: KB2VXA@WT3V.#CNJ.NJ.USA.NOAM
To : IBM@WW
Hello Kieth,
In days of old when knights were bold, and computers were invented, we
had to manually configure the com ports. With todays phug n' play the
software that uses them does it for us. THAT'S where you should be
looking.
While the commercial software that uses it configures it automatically
(consider a reinstall, may be corrupted) the Wndows communicatons feature
must be manually configured to the device in use on it. This is also true
for Amateur software, particularly that for a packet TNC.
Now here's an odd one for you to chew on. When I used Win Me (sucks) my
e-mailer quit after a couple of connections and the only way to fix it
was a reboot. I still have no idea why the computer diagnostics couldn't
find the port for the internal modem. After a reboot it checked out
normally. Since I dumped that Mistake Edition for XP Pro all my problems
vanished as if by magic. Of course it took a lot of work to get
everything back in order but well worth it.
While the doctor hasn't much to go on with your rather vague symptoms AND
I'm not all that much of a doctor, I hope I have given you some clues to
go on. Very best of luck OM!
73 de Warren, KB2VXA @ WT3V
E-MAIL: kb2vxa@juno.com
**************************************
Preserve the integrety of our network,
stop Internet forwarding!
**************************************
Message timed: 18:01 on 2003-Jun-02 GMT
Read previous mail | Read next mail
| |
