Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!cfchiesa
From: cfchiesa@bsu-cs.UUCP (Sir Xetwnk)
Newsgroups: comp.sys.atari.8bit
Subject: Re: (none)
Message-ID: <2063@bsu-cs.UUCP>
Date: 9 Feb 88 07:13:11 GMT
References: <8802081447.AA27452@ucbvax.Berkeley.EDU>
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 44
Summary: I've noticed the same bug in Kermit65...

In article <8802081447.AA27452@ucbvax.Berkeley.EDU>, CCSCHR@UWOCC1.UWO.CDN writes:
> 
   [stuff about using Kermit65 with Ramdisk under DOS 2.5 deleted]

> K-65 provides an exit back to DOS thru the Exit or Quit commands and as
> you might guess, this part of the puzzle is being a little inconsistent
> as well.
> - What is the approved/most successful/correct way to exit from a piece
>   of object code back to DOS (2.0 / 2.5 / any other DOSs)?
> - What is the difference between exiting from a piece of object code
>   loaded as an AUTORUN.SYS file as opposed to the same code loaded by
>   the "L"oad function of DUP.SYS? (For various DOSs, as above).
> 
> K-65 loaded as AUTORUN.SYS on DOS 2.0 exits normally. If I boot DOS 2.0
> and then load K-65 or AUTORUN.SYS from the DUP.SYS menu, EVERYTHING
> works just fine until I attempt to return to DOS; then BOOM! I think
> John Dunning mentioned that K-65 simply attempts a RTS to return to
> DOS. He may have the luxury of being able to use a more structured
> DOS allowing a simple return such as this.
> - Any comments?

Yes.  I've noticed that K65's behavior on "Quit" or "Exit" differs depending
on the DOS under which it is run.  My most striking observation to date is  
that behavior differs between OSS's "OS/A+" and "OS/XL" products - two nearly-
identical DOSes (sp?) which until now I had thought WERE identical.  When run 
under OS/XL, K65's quit/exit works as intended and you get back to DOS; under 
OS/A+, the quit/exit command LOCKS UP the machine.  The funny thing about this 
is that I am running an 800, NOT an 800XL - and yet it is the "XL" DOS - the
"wrong one", which allows K65 to operate properly!  

Why in the world the folks at OSS would change the linkage-back-to-DOS between
OS/A+ and the later OS/XL, I don't know, but that seems to be the case.  I
also have a program or two that will run under OS/A+ but NOT under OS/XL -
kind of the "opposite" of the K65 situation.

Well, that's my two cents.  Hope it was worth the 'vi' session to create it!

Chris Chiesa


<><><><><><><><><><><><><><><><><><><><><><><><><><><><> Chris Chiesa <><><><><>
<> {ihpn4|seismo}!{iuvax|pur-ee}!bsu-cs!cfchiesa                              <>
<> cfchiesa@bsu-cs.UUCP                                                       <>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>