problems with vnews
bytebug at pertec.UUCP
bytebug at pertec.UUCP
Fri Jun 1 21:53:55 AEST 1984
I tried to report these problems directly to the author, through the
address found in the vnews(1) manual page, but my letter was returned.
If anyone knows the correct mail address, I'd appreciate hearing from
them. In the meantime, I'd be interested in hearing if anyone else has
seen and/or fixed the following bugs:
----- Transcript of session follows -----
bad system name: spanky
uux failed. code 68
550 spanky!ka... Host unknown
----- Unsent message follows -----
Received: by UCB-VAX.ARPA (4.28/4.27)
id AA10812; Fri, 1 Jun 84 03:13:14 pdt
Date: Fri, 1 Jun 84 03:13:14 pdt
From: unisoft!pertec!bytebug
Message-Id: <8406011013.AA10812 at UCB-VAX.ARPA>
To: unisoft!ucbvax!spanky!ka
Subject: Vnews
Greetings...
I recently brought my 68000-based UNIX system up on USENET, and
have had a couple of problems with `vnews'. I have no idea how
old or new my version of the software is, so it might be best
to just get the latest copy if you could send it to me.
My first problem comes from using an old IMSAI micro with a
memory-mapped video board as a terminal at home. When I try to
drive my screen at 1200 baud, certain control sequences require
padding, which vnews and or termcap seem to ignore. In
particular, the clear screen sequence always seems to mess up
the first cursor positioning sequence.
Secondly, the tab character really throws my system in a loop.
Tabs in messages seem to be handled okay, but when I typed `v'
to see the version number, there seemed to be a tab in that
when locked up my terminal.
As I said, these may have been fixed long ago, and all that's
needed is to get the latest version. From what I've seen so
far, `vnews' will be a much nicer way to read the news, and I
appreciate the work you've done.
Thanks.
-roger long
pertec computer corp.
ucbvax!unisoft!pertec!bytebug
More information about the Net.bugs
mailing list