rokicki@navajo.STANFORD.EDU (Tomas Rokicki) (09/12/86)
[ And then there were none . . . ] I just got the vt100 emulator; great little program. Glad to see someone can make the Amiga sing. Does the Amiga support parity, though? I modified the program to set parity and everything, but it doesn't seem to be sending it. Perhaps I should use a parity translation table on the output side . . . this is for interface to MVS . . . Also, the code seems to open a screen of 205 (or something like that) lines . . . how well is this supported by the library routines? -tom
dave@uwmcsd1.UUCP (Dave Rasmussen) (10/16/86)
I compiled the vt100 sources again today with lattice 3.03 and still have no beep coming out of my stereo. VOLUME is defined as 64 in my vt100.init file. I've double checked the stereo with the "say why doesn't this work" command. Anyone else got beeps out of their version? -- The views above are those of my keyboard, not my organization. Dave Rasmussen c/o Computing Services Division @ U of WI - Milwaukee INTERNET: uwmcsd1!dave@rsch.wisc.edu UUCP: ihnp4!uwmcsd1!dave
dgg@ci-dandelion.UUCP (Dave Grubbs) (10/29/86)
I spent last weekend trying to make the vt100 emulator (version 2.2) work under Lattice. I had moved the source code over to my Amiga the weekend before and had applied all the patches from the summary posted to the net. I was stopped by switches on the "cc" commands in the makefile, which I didn't think were appropriate for Lattice, so I sent a query to Dave Wecker who cleared up my problem. I compiled it using lc1 and lc2 commands with no switches. I got the GURU Meditation listed in the next paragraph (Same exact numbers). So, on a guess, I upped the stack to 12000 and compiled it again. This time it compiled, so I tested it. And changed the switches and compiled it. And tested it. And changed the switches. And tested it. Every possible combination of Lattice switches. EVERY time I executed it I got a "Software Error" alert. When I "Cancel"ed the alert, I got a GURU Meditation of 00000004.000097B0. Without fail and before it did anything else. I even added "printf"s to the beginning of the program and they never even showed up. I conclude from this that the program is not doing anything weird, rather that the compiler and linker syntax I used is wrong. (I also tried executing it with various stack sizes.) Does anyone have any idea what is going on?
mwm@eris.BERKELEY.EDU (Mike (Don't have strength to leave) Meyer) (11/01/86)
Looks like nows a good time to post this. Following is the Makefile I use with VT100 v2.2 and Lattice C. The make is from one of the early fish disks, and it expects Fred's cc command to be in c: I twiddled the MANX and LATTICE defines to 0 and 1 (respectively) in vt100.h, fixed a few other things relating to screen placement, and ran a make, and everything worked like a charm. <mike ###################################################################### # # Makefile to build vt100 terminal emulator # # v2.1 860915 DBW - new features (see README) # 860823 DBW - Integrated and rewrote lots of code # v2.0 860809 DBW - Major release.. LOTS of changes # v1.1 860720 DBW - Switches, 80 cols, colors, bug fixes # v1.0 860712 DBW - First version released # ###################################################################### OBJS = vt100.o init.o window.o xmodem.o remote.o kermit.o script.o expand.o INCL = vt100.h #INCL = vt100 : $(OBJS) cc -o vt100 $(OBJS) vt100.o : vt100.c $(INCL) cc -c vt100.c init.o : init.c $(INCL) cc -c init.c window.o : window.c $(INCL) cc -c window.c xmodem.o : xmodem.c $(INCL) cc -c xmodem.c remote.o : remote.c $(INCL) cc -c remote.c kermit.o : kermit.c $(INCL) cc -c kermit.c script.o : script.c $(INCL) cc -c script.c expand.o : expand.c $(INCL) cc -c expand.c