Re: [cc65] Atari Disk Image Tool ?

Hi Oliver,

On 28.09.10 13:20, Oliver Schmidt wrote:
> Just to make sure I'm not getting this wrong. The "standard" way to
> run a cc65 program using DOS 2.5 is the L option from the "DOS menu" -
> correct? If the program ends then a message 'need mem.sav to load this
> file' is printed and then the DOS menu comes up again. Is this the
> expected experience?

 From the documentation:

   N. CREATE MEM.SAV Reserves space on a diskette for the
           program in RAM to be stored while the DUP.SYS file is being
           used.  For some applications like programming, it is a good
           idea to create a MEM.SAV file on each new diskette you intend
           to use as a System Diskette.  As you become more familiar
           with DOS, you may find there are cases where a MEM.SAV file
           serves no useful function.  The inconvenience of waiting for
           MEM.SAV to load into memory may warrant deleting it from the
           disk.

DUP.SYS is the DOS menu. If it's present, the memory used by DUP.SYS
will be saved to MEM.SAV and restored when you leave DOS. Mostly useful if
you enter DOS from BASIC and don't want the BASIC program to be destroyed.
You can ignore the message.


> If I omit DUP.SYS from a DOS 2.5 disk then the emulator tells me that
> the Atari crashed. If I omit DUP.SYS from a disk containing a
> STARTUP.SYS, then that program gets successufully loaded. However when
> the program ends, there's again the crash. From that I deduct that
> (beside DOS.SYS) DUP.SYS is more or less obligatory (at least for DOS
> 2.5) - correct?

STARTUP.SYS? As said, DUP.SYS is the DOS menu and as long as you never
enter the menu (an autostart program which never exits), it's probably not
needed.


> For the Apple2 I've created a C library function named
> rebootafterexit(). If it is called at some time then exiting the cc65
> program some time later will not try to get back into DOS but will
> rather reboot the machine. Maybe something like this would be feasable
> / would makes sense for the Atari too. Then omitting DUP.SYS would
> work - but maybe I'm missing some point...

Would an atexit() routine also work, wouldn't it?

Btw., is space so tight that you need to omit DUP.SYS?

regards,
chris
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.