R_Tim_Coslet@cup.portal.com (12/14/89)
Well, I just installed the _2_Chip_ TOS 1.4 in my MEGA ST2.
======
Came right up no problems, installed NeoDesk still no problems...
Tried several of my usual programs (one acted a little strange, but
I will have to look into it further, I wrote part of it and might be
doing something slightly illegal with AES that TOS 1.2 didn't mind but
TOS 1.4 won't tolerate).
Then I encountered a PROBLEM with UniTerm V2.0c...
... it gives 3 BOMBS on exit!!!!!
Trying an old copy of UniTerm V2.0a, it also BOMBS on exit (2 BOMBS this time)!
Other than this (BOMBS on exit) UniTerm seems to work fine under TOS 1.4.
Has anyone else encountered problems like this with UniTerm (any version)
under TOS 1.4?
R. Tim Coslet
Usenet: R_Tim_Coslet@cup.portal.com
BIX: r.tim_cosletfischer-michael@CS.YALE.EDU (Michael Fischer) (12/15/89)
In article <25010@cup.portal.com> R_Tim_Coslet@cup.portal.com writes: >Other than this (BOMBS on exit) UniTerm seems to work fine under TOS 1.4. >Has anyone else encountered problems like this with UniTerm (any version) >under TOS 1.4? I've noticed this problem with UniTerm V2.0e, and I don't think it is specific to TOS 1.4. UniTerm works fine when started from the desktop, but when started from the Mark Williams shell, it will give bombs on exiting, and sometimes the computer will subsequently crash. These bombs seem to occur with other programs compiled with OSS Pascal as well. I suspect the Pascal libraries are doing something incorrect with AES causing it to walk over memory that doesn't belong to it, and the particular memory that ends up getting trampled may well be different under TOS 1.4 than under previous versions, causing the change in behavior that you observe. You may find that it also depends on what TSR programs and desk accessories you have installed. I'd be interested if anyone ever manages to track this problem down. ================================================== | Michael Fischer | | Arpanet: <fischer-michael@cs.yale.edu> | | Bitnet: <fischer-michael@yalecs.bitnet> | | UUCP: <fischer-michael@yale.UUCP> | ==================================================
kclenden@silver.bacs.indiana.edu (Kevin Clendenien) (12/15/89)
In article <8554@cs.yale.edu> fischer-michael@CS.YALE.EDU (Michael Fischer) writes: >In article <25010@cup.portal.com> R_Tim_Coslet@cup.portal.com writes: >>Other than this (BOMBS on exit) UniTerm seems to work fine under TOS 1.4. >>Has anyone else encountered problems like this with UniTerm (any version) >>under TOS 1.4? > >I've noticed this problem with UniTerm V2.0e, and I don't think it is >specific to TOS 1.4. UniTerm works fine when started from the >desktop, but when started from the Mark Williams shell, it will give >bombs on exiting, and sometimes the computer will subsequently crash. I had problems with Uniterm and NeoDesk. My problems related to having TRANSWRP.PRG in my auto folder. For some reason, if I loaded TRANSWRP.PRG, Uniterm would bomb when exiting back to NeoDesk. This also happened from 1st Word when exiting back to NeoDesk, if I had TRANSWRP.PRG loaded. Included on the NeoDesk disk is a program call SHEL_FIX.PRG. It might fix your problems. According to the documentation with SHEL_FIX.PRG, some of the usual TOS functions concerning shells don't like be used anywhere except from the real desktop. This program intercepts calls to these functions. It was written by Dan Wilga, I think. Permission is given to pass it around so long as it isn't modified, and the documentation is included. If you need a copy, let me know. -------------------------------------------------------------------------- kclenden@silver.bacs.indiana.edu Kevin Clendenien BLoomington Atari ST users group BLAST, President BLAST BBS - (812) 332-0573 FNET node #141 "Of course any opinions or views stated above do not necessarily represent the official position of any person, or organization other that of Kevin Clendenien." --------------------------------------------------------------------------
R_Tim_Coslet@cup.portal.com (12/17/89)
In article <8554@cs.yale.edu> fischer-michael@CS.YALE.EDU (Michael Fischer) wri tes: >In article <25010@cup.portal.com> R_Tim_Coslet@cup.portal.com writes: >>Other than this (BOMBS on exit) UniTerm seems to work fine under TOS 1.4. >>Has anyone else encountered problems like this with UniTerm (any version) >>under TOS 1.4? > >I've noticed this problem with UniTerm V2.0e, and I don't think it is >specific to TOS 1.4. UniTerm works fine when started from the >desktop, but when started from the Mark Williams shell, it will give >bombs on exiting, and sometimes the computer will subsequently crash. I was finally able to play with it and located the cause of the problem I was having with UniTerm V2.0c. It bombed both from NeoDesk and the standard DeskTop (2 bombs from the DeskTop though instead of the 3 it gets under NeoDesk). By enabling and disabling accessories I got UniTerm to run with no bombs on exit. The accessory having problems with UniTerm was NeoQueue V2.03. I understand Gribnif has a newer release of NeoDesk... I think I will report this bug to them, and see if they can tell if the new release also has this problem... maybe it is time to upgrade... again. :-) By the way, I think the real source of the problem is inside UniTerm (probably in the OSS Libraries, as you said)... sometimes after UniTerm bombs AES acts very strangely, and a reboot (either warm or cold) completely corrects this strange behavior. R. Tim Coslet Usenet: R_Tim_Coslet@cup.portal.com BIX: r.tim_coslet
poole@chx400.switch.ch (Simon Poole) (12/17/89)
In article <25010@cup.portal.com> R_Tim_Coslet@cup.portal.com writes: ..... >Then I encountered a PROBLEM with UniTerm V2.0c... > > ... it gives 3 BOMBS on exit!!!!! > >Trying an old copy of UniTerm V2.0a, it also BOMBS on exit (2 BOMBS this time)! > >Other than this (BOMBS on exit) UniTerm seems to work fine under TOS 1.4. >Has anyone else encountered problems like this with UniTerm (any version) >under TOS 1.4? I used UniTerm with the May 1988 Beta version of TOS1.4 a lot without problems (mid 1988, till I noticed that nobody here was really interested). I would be supprised if anything serious changed after that (one problem that did exist at that time was that the memory allocation of the file selector was even more broken than under previous TOS versions). Anyway since TOS 1.4 doesn't actually exist in the german speaking part of Europe, there's no way that I can check on this. (Not that I would do anything that would imply that I think Atari has any future at all) -- ------------------------------------------------------------------------ Simon Poole poole@verw.switch.ch/poole@chx400.switch.ch/mcvax!cernvax!chx400!poole ------------------------------------------------------------------------
poole@chx400.switch.ch (Simon Poole) (12/18/89)
In article <25108@cup.portal.com> R_Tim_Coslet@cup.portal.com writes: .............. >By the way, I think the real source of the problem is inside UniTerm (probably >in the OSS Libraries, as you said)... sometimes after UniTerm bombs AES acts >very strangely, and a reboot (either warm or cold) completely corrects this >strange behavior. This doesn't really supprise me since depending where the crash happens a lot of stuff might not be (yet) in a state the desktop expects. Does NewQueue do anything odd with memory allocation? UniTerm grabs all available memory - 5k* (or whatever you have in the setup file) and sometimes it seems as if GEMDOS memory allocation gets slightly confused (which is not news to anybody). Simon * This is for the fileselector which doesn't check for enough memory before it runs (I increased the value in on of the later revs because the 1.4 fileselector needs a bit more (at least it did in the beta test version). -- ------------------------------------------------------------------------ Simon Poole poole@verw.switch.ch/poole@chx400.switch.ch/mcvax!cernvax!chx400!poole ------------------------------------------------------------------------
hase@netmbx.UUCP (Hartmut Semken) (12/20/89)
In article <25010@cup.portal.com> R_Tim_Coslet@cup.portal.com writes: >Well, I just installed the _2_Chip_ TOS 1.4 in my MEGA ST2. >Came right up no problems, installed NeoDesk still no problems... >Then I encountered a PROBLEM with UniTerm V2.0c... I do not have any problems with Uniterm 2.0e unter Rainbow TOS (german). No problems with Revolver or the like... I had problems when trying NeoDesk (with TOS 1.0): Uniterm, Signum2 and Tempus refused to PExec() programs (I use rz.ttp/sz.ttp from Uniterm for ZModem files transfers). I got rid of the problems when I got rid of NeoDesk... hase -- Hartmut Semken, Lupsteiner Weg 67, 1000 Berlin 37 hase@netmbx.UUCP Dennis had stepped up into the top seat whet its founder had died of a lethal overdose of brick wall, taken while under the influence of a Ferrari and a bottle of tequila. (Douglas Adams; the long dark teatime...)