Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!mcsun!unido!gmdzi!strobl From: strobl@gmdzi.UUCP (Wolfgang Strobl) Newsgroups: comp.windows.ms Subject: Re: Still looking... Good Win 3.0 Comm program. Message-ID: <3259@gmdzi.UUCP> Date: 28 Aug 90 13:42:08 GMT References: <1990Aug25.160852.25287@amd.com> <1990Aug27.234514.6869@chinet.chi.il.us> Organization: GMD, Sankt Augustin, F. R. Germany Lines: 21 patrickd@chinet.chi.il.us (Patrick Deupree) writes: > ... I'm using DynaComm (as a matter of fact, I'm >using it right now) on both a Unix machine and on CompuServe. I like it a >lot. The Scripting language isn't too bad (I didn't have the manual for >the script language, so I used another script and modified it for my >purposes). For CompuServe it's great because it supports the Compuserve >B protocol for downloading. It also happens to be one of the rare packages >that supports the combios (for use with network modems). >FutureSoft (the same guys that make the current Terminal) make the program >and should be listed in your application reference guide if you want a #. All this sounds great, but ... The current Terminal is broken outside the US, i.e. it does not work with non US keyboards. I reported this in a previos message. Does DynaComm behave similar? Wolfgang Strobl #include