vt100 2.2 finally works for me
Dave Grubbs
I received nearly a dozen responses to my description of my
attempt to make applications compile and run on the Amiga.
I was universally noted that 1) much of the PD software compiles
only under one of the compilers (some of it doesn't compile at all)
and 2) most of the PD software requires the +L and 32 bit libraries
when using the Manx compiler.
My own problem was that I underestimated the time and effort it
takes to get up to speed as a developer on the Amiga. I knew it would
be a tougher job than on a stable (and faster) system like the VAX, but
I was not prepared for what I found. Even an old Z80 computer running
CP/M that I worked on 6 years ago was easier to figure out.
I simply had the bad luck to choose the compiler and options that
were least likely to work for each file I tried to compile. They are
not always labelled with the compiler one needs to use. After another
attempt, I found some correct combinations. Manx + 32bit-libs seems
cleanest -- It even compiles most of the Unix sources I have tried.
The next level of problems:
When I linked a Unix program which used "perror", "ln" told me that
the Unix variables ("int sys_nerr" & "char *sys_errlist[]") were undefined.
Since I didn't refer to them in my program, there must be a perror in the
Manx library without the table definitions. OK, where are they?
I got Wecker's vt100 2.2 working. But it doesn't work perfectly.
- It doesn't beep or flash. I read of problems with Lattice, but
I used Manx. I'd prefer a flash, since I use my Amiga at night.
- What is the best combination of background/foreground to reduce
the effect of the interlace flicker?
- File/Kermit-BYE works, but "$" doesn't. The remote kermit keeps
sending "# N3". The doc said "$" was a BYE.
- Kermit Get works fine, but what is "Kermit Receive" supposed to do?
I thought it would be something like 1) prompt for file (or wildcard)
2) send the string "kermit -s" (or "kermit -i -s" if Comm/Xfer/image
is set), then 3) go into response mode. What is it for? The only
use I can think of is as a "server", which is not what a terminal
emulator is for.
- (Warning: trivial semantic complaint ;-)) I believe the "get" and
"receive" labels are switched. Receive is a "continuous" condition,
(send/receive) whereas "get" has the connotation of "go grab one".
- I found that on Ultrix (and probably by default on 4.2 and 4.3,
though we fixed this at Athena) you have to remember to use the
-8 option when using "rlogin", or kermit doesn't work.
- The "script" handler needs a "prompt" command to pick a string up from
the screen. (I'll write one, if no one else is hacking this program
any more.) It would be nice to have a library of scripts that could
prompt for variables.
Mike Farren
>
> - Kermit Get works fine, but what is "Kermit Receive" supposed to do?
> I thought it would be something like 1) prompt for file (or wildcard)
> 2) send the string "kermit -s" (or "kermit -i -s" if Comm/Xfer/image
> is set), then 3) go into response mode. What is it for? The only
> use I can think of is as a "server", which is not what a terminal
> emulator is for.
>
> - (Warning: trivial semantic complaint ;-)) I believe the "get" and
> "receive" labels are switched. Receive is a "continuous" condition,
> (send/receive) whereas "get" has the connotation of "go grab one".
>
The labels aren't switched. "Get" implies that the other end of the line
has a Kermit server active. It will send the filename you request to the
server, which will then send you the file. "Receive", on the other hand,
implies that you have entered a command such as "kermit -s <filename>"
on the remote system, and then entered receive mode on your end, to receive
the requested files.
--
----------------
"... if the church put in half the time on covetousness
Mike Farren that it does on lust, this would be a better world ..."
hoptoad!farren Garrison Keillor, "Lake Wobegon Days"