Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!brl-smoke!smoke!jcm@ORNL-MSR.arpa
From: jcm@ORNL-MSR.arpa (James A. Mullens)
Newsgroups: net.micro
Subject: Re: HELP with ProComm 2.3 problems please!
Message-ID: <3365@brl-smoke.ARPA>
Date: Wed, 27-Aug-86 21:47:10 EDT
Article-I.D.: brl-smok.3365
Posted: Wed Aug 27 21:47:10 1986
Date-Received: Thu, 28-Aug-86 21:32:53 EDT
Sender: news@brl-smoke.ARPA
Lines: 19

I missed the beginning of this discussion on ProComm problems, but I'll
contribute a suggestion which is at least interesting if not helpful.
I decided to take a look at ProComm recently, and found it wouldn't work
correctly until I set the date of the executable file (procomm.exe) up
to last June instead of its earlier creation date.

Perhaps the authors built in an expiration date?!

I found annoying problems in the vt100 emulation when used with the
UN*X vi editor on BSD 4.2, so I decided not to use it...

My apologies if this finds it way to net.micro ...  I'm on the arpanet
side of the fence and I seem to have no way to discriminate between
net.micro and net.micro.pc.  (All constructive suggestions greatly
appreciated).

Has anyone else seen this ProComm phenomenon, or did I just imagine it?

jim mullens / oak ridge national lab