home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!mentor.cc.purdue.edu!expert.cc.purdue.edu!huebnere
- From: huebnere@expert.cc.purdue.edu (Robert Huebner)
- Newsgroups: comp.sys.amiga.datacomm
- Subject: Term 2.3 problem : a new one?
- Message-ID: <BuDpMo.K82@mentor.cc.purdue.edu>
- Date: 10 Sep 92 20:15:59 GMT
- Sender: news@mentor.cc.purdue.edu (USENET News)
- Organization: Purdue University Computing Center
- Lines: 23
-
-
- I've been reading about Term 2.3 bugs for some time and this is one
- I haven't seen mentioned before. First - I am running the 68000 version
- under Workbench 2.04 with NOTHING other than standard startup-sequence
- programs running in background:
-
- If I set the SERIAL parameters to 7N1 which is the setup required to
- dialup our University modems, Term will not recognize or process the
- VT100 emulation codes. The codes appear on my screen as ASCII. If I
- set to 8N1 and strip bit 8 in the TERMINAL menu, the same thing occurrs.
- If I DON'T strip bit 8, the text appears garbled.
-
- Just to verify that its not the fault of my UNIX account or the ISN
- server; NComm and one other PD term program handled this perfectly
- after switching to 7 Data Bits.
-
- I believe this WORKED under 2.2B but now is broken. Does anyone have
- suggestions or corroboration of this error?
-
- -----------------------------------------------------------------------------
- Robert Huebner huebnere@expert.cc.purdue.edu
- "Cthulhu in '92 : Why vote for the lesser evil?"
- -----------------------------------------------------------------------------
-