Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ncar!gatech!psuvax1!psuvm!cunyvm!ndsuvm1!mtus5!ldshaner From: LDSHANER@MTUS5.BITNET (Leon D. Shaner) Newsgroups: comp.sys.amiga.datacomm Subject: Re: Handshake 2.20c already crashed on me!!! Message-ID: <91044.161446LDSHANER@MTUS5.BITNET> Date: 13 Feb 91 21:14:46 GMT References: <1991Feb9.193018.14518@rodan.acs.syr.edu> <1991Feb10.144548.9365@rodan.acs.syr.e <2594.27b81f21@incstar.uucp> Distribution: usa Organization: Computing Technology Services, Michigan Technological Univ. Lines: 24 The crashes I've had were due to the serial port contention... I run a BBS and when I invoke HandShake it is through a script which deactivates the BBS from the commandline-specified serial port... The problem was that the port hadn't had enough time to settle before HandShake re-opened it and hence I got a guru when I did things as simple as trying to dial... I don't know if it was necessary, but I also upped the stack size... I've not tried the XPR stuff... Something that might help some of you is to just go to the DEVICE driver menu item and hit okay on serial.device... This forces it to close the device momentarilly and re-open it... It may have some effect, since in essence the XPR stuff is "borrowing" the port from HandShake and if it wasn't properly opened in the first place, problems are to be expected... BTW, most of this is theory, but it works for me, now... --Leon ---------------------------------------------------------------------- | Leon D. Shaner - EE Undergrad / Amiga Bitswap Central Dispatch / | / (906)482-8248 - DLG PRO! BETA / | / FREE! :24 HOURS :80 MB :2 LINES!/ ------------------------------------------------------------------