home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!gatech!darwin.sura.net!haven.umd.edu!news.umbc.edu!gmuvax2!pfarrell
- From: pfarrell@gmuvax2.gmu.edu (Pat Farrell)
- Subject: Re: Compuserve Access
- Message-ID: <1992Aug21.204832.15236@gmuvax2.gmu.edu>
- Organization: George Mason University, Fairfax, Va.
- References: <635.1101.uupcb@satalink.com>
- Date: Fri, 21 Aug 1992 20:48:32 GMT
- Lines: 38
-
- In article <635.1101.uupcb@satalink.com> bert.tyler@satalink.com (Bert Tyler) writes:
- >MD> Personally, I found it difficult to muck around in CompuserveLand.
- >MD> I can't browse quickely and easily. Not like with a good news
- >MD> reader (trn is my current favorite).
- >
- >As with Unix and Usenet, a good access program is vital in the Compuserve
- >world. Logging onto Compuserve manually is not for the faint of heart
- >(or light of wallet) <grin>.
- >
- >I use TAPCIS,
- >Other folks prefer
- >the freeware ATO package.
- >your pay-by-the-minute access time, and both packages do an excellent
- >job of it.
- > Bert Tyler (bert.tyler@satalink.com)
- >---
- I recommend that you look at OZCIS. It is zero cost but
- supported by the author. You can find it in the IBMCOM forum.
- look for the OZCIS.REQ file, which explains the other files,
- hardware requirements, etc. Neither program has a concept like
- .kill files. Instead, they access CI$ in two passes. the first
- returns the subject line of messages, you "mark" the ones you
- like, and then the second pass retreives them. You do all of
- your reading, and composition of replies, offline.
-
- I used to use TAPCIS. I hated its terse user interface, but it
- works. OZCIS has a CUA style, windowing interface that is user
- friendly.
-
- None of the CI$ navagation programs are likely to save money,
- as once it gets easier, you spend more time=$$$ wandering
- arround.
-
-
- Pat Farrell, Grad Student pfarrell@cs.gmu.edu
- Department of Computer Science, George Mason University, Fairfax, VA
- #include standard.disclaimer
-
-