From: baffoni@aludra.usc.edu (Juxtaposer)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: MiNT, TCSH, CoNnect, Warp9...what they have in common?
Date: 9 Nov 1992 18:07:45 -0800
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: aludra.usc.edu

In article <1992Nov7.234210.24329@elroy.jpl.nasa.gov> hyc@hanauma.jpl.nasa.gov (Howard Chu) writes:
>In article <1dff3lINN3b5@aludra.usc.edu> baffoni@aludra.usc.edu (Juxtaposer) writes:

>>	You know something, I can 100% gurantee a lockup whenever I get a
>>Connect message from the modem, regardless of whether I am in the dial
>>menu or whether I am in the "direct" terminal.  In fact, I believe I remember
>>ctl-alt-deling while connected, and it being frozen before I could do anything
>>(which is unusual since it usually takes some action on my part before 
>>something crashes).  I wonder if just being actively connected to the modem
>>has anything to do with it....
>
>That would be pretty unusual. Well, there *is* an interrupt vector for the
>Carrier Detect signal, but that is initially disabled and I can't imagine any
>program ever needing to enable it. Also, I can't understand why the interrupt
>would cause a problem even if it was enabled...
>
>In Uniterm the CONNECT message only makes Uniterm crash, and only if I used
>the auto-dialer. You're saying you get a lockup even if you dial manually?
>When you're in this state does Ctrl-Alt-F6 work (list active processes)?

	Yes, this occurs even when I am manually dialing (and it is after 
the modem sends the connect 9600 message.  I doubt it has anything to do with
the CD signal because it doesn't crash while dialing - I can break out of 
dialing and it works fine.  No, it dies right after receiving "connect 9600"
so it proabably has something to do with some code that CoNect and Uniterm have
in common right after there is a terminal connection.  Any ideas?
	I cannot use any key sequence except cnt-alt-del from the locked
up state, and only if that is my only keypress after being locked up.  None
of the other cnt-alt keys work. I did have it set to debug_1, and printer so 
I got a:  PID 7 (CONNECT)BUS ERROR: User PC = 1b7efc (base page=186cf0)
after it connected and locked up.  BTW,  I can still hear keyclicks, it just
doesn't do anything.

	Oh, I set it up to debug when all I do is load MiNT and TOSwin, which
normally results in my inability to run any program (whether .prg or .ttp)
unless I run it through TOSwin.  It dies running CoNect1.80 from the desktop
and :

pid 2 (GEM): malloc: out of memory
pid 2 (GEM): BUS ERROR: User PC=e33d88 (basepage = 489d0)
pid 5 (GEM): malloc: out of memory
pid 5 (GEM): malloc: out of memory
pid 5 (GEM): malloc: out of memory
pid 5 (GEM): malloc: out of memory

	Right now I am using UNITERM, and that was after using alt-1 to
auto dial my mainframe.  Did you use the mouse auto-dialer to have your 
problems or does the alt-# also give you lockups?  I have noticed that 
trying to use the mouse menu locks up my machine, even before I get to dial
with it - the menu comes up briefly and then disappears, and it is locked from
that point on.  Darn, Uniterm takes over cntl-alt1 and cntl-alt3 or I'd 
set the debug before I use the mouse, but since it does, I can't debug it (I 
have to set Uniterm to GEM autoboot (from desktop install app autoboot) or
I can't get it to run.

>-- 
>  -- Howard Chu @ Jet Propulsion Laboratory, Pasadena, CA
>
>All true wisdom is conveyed in one-line witticisms.

-MikeB