home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!sdd.hp.com!network.ucsd.edu!sdcc12!icogsci1!cg18ffl
- From: cg18ffl@icogsci1.ucsd.edu (Spumoni...)
- Newsgroups: comp.sys.amiga.applications
- Subject: Re: Anyone have experience with X-Comm V1.00?
- Keywords: Ka-SPLATTT!!!
- Message-ID: <43370@sdcc12.ucsd.edu>
- Date: 12 Jan 93 07:13:10 GMT
- References: <43365@sdcc12.ucsd.edu>
- Sender: news@sdcc12.ucsd.edu
- Followup-To: comp.sys.amiga.applications
- Organization: University of California, San Diego
- Lines: 76
- Nntp-Posting-Host: icogsci1.ucsd.edu
-
- Jeremy Friesner writes:
-
- .I downloaded X-Comm v1.00 today, and although I really like
- .the interface and multitude of options, it seems very unstable.
-
- .It causes enforcer hits on startup, sometimes makes the mouse
- ."jerky", sometimes writes garbage on the screen, but mostly
- .just goes straight to nuclear-meltdown-guru..
-
- .Is anyone else using this program yet? If so, do you have
- .any trouble with it crashing? I'm trying to find out if
- .it is X-Comm at fault, or one of the (many) other programs
- .I have running in the background.
-
-
- .Thanks for any input,
-
- .Jeremy
-
- I downloaded X-Comm1.0 today to test it out. (I have a 3000) Yes, the
- program is VERY, EXTREMELY unstable. In fact, I would go so far as to say that
- this program should have remained in beta testing for a few more months at
- least.
- Here's a short rundown of the problems:
-
- 1) Sometimes the program will instantly GURU while opening it's screen.
- 2) Using the REXX server (ex: for instance, automating the dialing of numbers
- with a hotkey) Usually causes the modem to behave erratically, and often
- crashes the Arexx server, input.device, and then corrupts the freemem list and
- LOCKS the computer up DEAD. The computer will not boot after this happens. It
- must be turned off.
- 3) The IFF beep server (the one that you select with the ASL requester) is a
- suspected cause of the system crashing when the modem sends a carrier detect
- to the program.
- 4) Calling my VAX server causes XComm to crash horrendously. Sometimes (not
- always) I will get to the part where the terminal will reset itself. Then, the
- screen will start spitting out garbage, whereupon the system will attempt to
- put up an Abort/retry Software Failure requester, at which point the system
- will lock up DEAD again.
- 5) Playing with the macros too much causes equally horrendous memory
- corrupting crashes.
- 6) The user interface will lock up often, becoming numb to all user input.
- 7) And many more.
-
- In short, there are a HELL OF A LOT OF BUGS. In fact, I have decided to ignore
- XComm for the time being, until there is a suitable bugfix. The interface and
- ideas behind the program are far more excellent than Term (IMHO). This is not
- surprising, since it looks likt the authors studied the source to Term and
- embellished upon it. It is very user configurable (the only part of the
- program that was reliable), font-sensitive, and sports some INCREDIBLY
- powerful features.
- I am actually impressed with Xcomm, though, because it's not often
- that a program so new shows so much potential. Ususally the first version is
- lacking features (on top of being bug-ridden) and other things are added
- later.
-
- I believe if XComm is further developed into a stable, reliable
- product, it will be one of, if not THE, best comm programs out there. For now,
- though, I'll keep a respectful distance. You have to do that when the program
- crashes your Amiga more times than it's been crashed in the last year. :)
-
-
- ----------------------------------------
- ...nverenin@sdcc13.ucsd.edu
-
-
-
-
-
-
-
-
-
-
-
-
-