[comp.sys.atari.8bit] Kermit-65 troubles

jrd@STONY-BROOK.SCRC.SYMBOLICS.COM (John R. Dunning) (02/14/88)

    Date: Mon, 8 Feb 88 06:47:36 PST
    From: CCSCHR%UWOCC1.UWO.CDN@forsythe.stanford.edu

[...]
    DOS 2.5 when booted will always load the 850 interface if it finds this
    device powered on. This happens just after the Ramdisk is initialized.
    I then load K-65 from the DUP.SYS menu and K-65 has problems with what
    DOS 2.5 has done to the 850, claiming the "850 is not responding".

That's not a problem.  What that message really should say is something
like "I tried to load the driver, but couldn't.  Maybe it's already
loaded?"  In your case that's what's happening; it's already there, so
when Kermit-65 tries to load it again, the 850 tells it to shut up.

    My circumvention is to turn off the 850 while DOS 2.5 is loading and
    then power it back up before loading K-65. This works fine but is
    clumsy as hell and will definitely shorten the life of my 850!!!

You don't need to do that.  It's completely harmless to let Kermit try
to load the driver again.

    So at this point, I can get the data to the Ramdisk but must then insure
    that any D/Ls done during the session are moved to a "real" disk
    before powering off the 130XE. K-65 does not provide a Copy command
    as one of the (very handy) disk-handling commands currently supported.
    I must then exit back to DOS (DUP.SYS actually) in order to move the
    datasets from the virtual to the real disk.
    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)?

I believe I've asked the net about this before, and never gotten a
definitive answer.  Kermit-65 exits by doing an RTS.  That works with
DOS XL, and apparently some other things as well, but not everything.

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

As far as I know, none.  Anyone know better?