From: baffoni@aludra.usc.edu (Juxtaposer)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: MiNT, TCSH, CoNnect, Warp9...what they have in common?
Date: 7 Nov 92 04:01:57 GMT
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: aludra.usc.edu

In article <1992Nov6.173721.4625@elroy.jpl.nasa.gov> hyc@hanauma.jpl.nasa.gov (Howard Chu) writes:
>In article <1dd85mINNlra@skat.usc.edu> mbaffoni@skat.usc.edu (Michael Baffoni) writes:

>Which version of MiNT?

	Sorry - MiNT .95

>>	When I load _just_ MiNT and TOSwin(1.1), I am completely, utterly
>>unable to run another GEM program - PID errors and such.

>Mebbe you should get the Toswin 1.4 that Eric Smith recently put on a.a.

	I will.  Is it moved out of the New directory yet?

>>	If I load _just_ MiNT and TOSwin and have something "INIT="ed,
>>it says "leaving MiNT" just before it drops me into the desktop, nothing
>>running, and every .acc except TOSwin is loaded.  I can't run .prgs.

>If you specify an INIT in your MINT.CNF file then it ordinarily will not
>make it to the GEM desktop, so TOSwin is irrelevant then. The "leaving MiNT"
>message means your INIT program exited, so MiNT shuts down. TOSwin is
>absent from the resulting desktop because it only installs itself if MiNT
>is active.

	Right, but once it can't/isn't loading the program that is to be INITed
shouldn't it reinstate MiNT and therefore TOSwin?  Besides, are there 
limitations on what can and can't be INITed?  Like is it a bad idea to INIT a
GEM program?  If not, then why is it not running say CoNnect from the INIT=
when it works perfectly fine from the desktop?

>>	If I load Warp9 (as well as all the rest of my junk), MiNT, TOSwin,
>>Warp9.acc, then everything has the new font, but I still can't run any
>>.prgs. Warp9.acc is accessible, no bombs.

>Strange. Warp9.acc almost always caused a lockup for me. I've only installed
>the patch for 3.71 tho, I'm not up to the current (3.73?) yet.

	BTW, I placed the updates from 3.70->3.71->3.72->3.73 up on a.a. a
couple of weeks ago so it should be available in the usual place (whereever
that is).

>>	If I load Warp9 (as well as all the rest of my junk), MiNT, TOSwin,
>>Warp9.acc and have ConNect set to autorun (from the inst app of GEM), it runs 
>>at bootup, just like it should, Warp9 is active, MiNT and TOSwin are active,
>>and I have no problems whatsoever accessing the Warp9.acc.  In fact I can
>>quit CoNnect, it puts me at the desktop, I can run most of my .prgs (including
>>the old, original First Word!) and both Warp9 and TOSwin accs are accessible.
>>No bombs.  This would be idyllic....EXCEPT EVERY ONCE IN A WHILE IT SEMI-LOCKS
>>UP!

>I've noticed that the Warp9 screen saver tends to lock up my MiNT sessions.
>I haven't figured out how to disable the screen saver yet.

	I thought about that, but I turned the screensaver off (since I had
access to it) and it didn't help.  BTW, why don't you just put "scrnsave.off"
in your warp9.dat file and it will turn it off for the entire session, or
configure your warp9.dat file so that it shuts the screensaver off whenever
you run a program that has problems with it?

>I also have problems with a lot of programs when BIOSBUFfering is active.
>Uniterm exits with a bus error when it detects the CONNECT string after
>auto-dialing a number. Big pain, haven't been able to track it.

	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....

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

-Mike