Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.sys.apple2.programmer > #4974

Re: BASIC Commands Broken After Running BIN Program

Newsgroups comp.sys.apple2.programmer
Date 2019-01-26 14:50 -0800
References (3 earlier) <4a03f5d2-b236-4d05-b21a-f841f3f82f04@googlegroups.com> <934ac885-8490-4eb5-b1a7-c6c440469f3f@googlegroups.com> <d99090c1-e050-44b6-b9c3-23d7fb25d985@googlegroups.com> <f2ad5668-e00e-4752-8f15-40f0cdf24a85@googlegroups.com> <60564c0d-c83c-4b1c-860b-3d4fc3aa13a5@googlegroups.com>
Message-ID <de80393e-a0a9-48ec-8ae4-e64aed3e7eea@googlegroups.com> (permalink)
Subject Re: BASIC Commands Broken After Running BIN Program
From gids.rs@sasktel.net

Show all headers | View raw


On Saturday, January 26, 2019 at 3:46:16 PM UTC-6, Bill Chatfield wrote:
> On Saturday, January 26, 2019 at 2:34:47 PM UTC-5, Antoine Vignau wrote:
> > Keep it simple:
> > - either put your code at $9000,
> > - follow Marco's advice,
> > - then gid's one (ah, signature)
> > 
> > Antoine
> 
> I think loading it at $9000 is what I want to do for now. But thanks Marco and gid. Those are both good ideas. I have looked at those options and may eventually do that. But, those solutions require an extra setup step to load the extended commands and attach them to BASIC.SYSTEM. Then for the commands to work, that extra setup step has to be properly configured to run every time BASIC.SYSTEM is loaded on every startup disk you want to use them on. It's hard enough just to create a boot disk with PRODOS and BASIC.SYSTEM on it. It's hard just to copy a file since there is no copy command. I know there are copy commands out there but they're not in the default command set so it takes extra work to make them available.
> 
> For now, I want a free-standing command that doesn't require BASIC.SYSTEM, but can also run in the presence of BASIC.SYSTEM without screwing it up. If I can create a loading mechanism that can also optionally attach the command to BASIC.SYSTEM as per your suggestions, I'll probably go for that next.
> 
> Basically, I want to create something that works they way you expect it to regardless of how it is started. So it will probably have to have separate startup and end code for each scenario. These are my target startup scenarios so far:
> 
> 1. The PRODOS program that allows you to select the next SYSTEM program to run.
>    I forget what this is called.
> 2. Inside BASIC.SYSTEM as a free-standing program.
> 3. Inside BASIC.SYSTEM as an extended command.
> 4. From inside other shells like davex.
> 
> Of course, this might not be possible. I'm just having fun exploring the possibilities...  :-)


1.  BYE is built in to Prodos and is used to select the next system program and does not take up any extra memory.  Just type BYE at the prompt

2. the main reasons this is not popular is because the command has to be installed before an applesoft program is loaded into memory or risk trashing the applesoft program or its data

3. check out ProCMD, it installs all commands inside Basic.system and is protected from Applesoft programs, but should still be installed before running any applesoft programs.  Over 75 commands are available


An alternate solution is to collect and use the System applications to do the job, using the BYE command, then return to Basic.system.  Most major system applications automatically return to the internal BYE program and you can either return to the Basic environment or select another system program to do another job.

On a side note, I also wanted all commands to operate while working in Basic.  There was no method that I could find so I created a command-line structure that makes all commands external.  Meaning ... I stripped out all of Basic.systems commands such as LOAD, BLOAD, SAVE, BSAVE, CATALOG, STORE, RESTORE etc, and made them into disk commands.  The extra space that was saved with the internal command removal is then reserved and used to launch one command at a time.  Some pretty large applications can be made into commands and loaded into this protected area.  Some of my more noteable commands have a bit of power, one of my favorite being FIND "program" (uses wild card characters and finds by type, date, prefix and suffix of a filename and can sort files by filename, type or size)

You probably won't find programs with this much power and will have to write your own.

There is also a command installer that installs multiple commands into Aux memory if you have a 128kb IIe/IIGS, and there is a control panel program with quite a few commands that can be accessed with Ctrl-OA-ESC for use only on a IIGS.  I believe it is called Soft Witch or some such.

I can't point you to any disk images that contain these programs right now, but best you go to Asimov and check out the programs that are there.

Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

BASIC Commands Broken After Running BIN Program Bill Chatfield <billchatfield1@gmail.com> - 2019-01-25 21:01 -0800
  Re: BASIC Commands Broken After Running BIN Program kegs@provalid.com (Kent Dickey) - 2019-01-25 23:48 -0600
    Re: BASIC Commands Broken After Running BIN Program Antoine Vignau <antoine.vignau@laposte.net> - 2019-01-25 22:08 -0800
      Re: BASIC Commands Broken After Running BIN Program Bill Chatfield <billchatfield1@gmail.com> - 2019-01-25 23:04 -0800
        Re: BASIC Commands Broken After Running BIN Program Antoine Vignau <antoine.vignau@laposte.net> - 2019-01-25 23:31 -0800
    Re: BASIC Commands Broken After Running BIN Program Bill Chatfield <billchatfield1@gmail.com> - 2019-01-25 23:03 -0800
      Re: BASIC Commands Broken After Running BIN Program gids.rs@sasktel.net - 2019-01-26 09:33 -0800
        Re: BASIC Commands Broken After Running BIN Program Bill Chatfield <billchatfield1@gmail.com> - 2019-01-26 10:26 -0800
          Re: BASIC Commands Broken After Running BIN Program Marco Verpelli <mverpelli@libero.it> - 2019-01-26 10:52 -0800
          Re: BASIC Commands Broken After Running BIN Program gids.rs@sasktel.net - 2019-01-26 11:30 -0800
            Re: BASIC Commands Broken After Running BIN Program Antoine Vignau <antoine.vignau@laposte.net> - 2019-01-26 11:34 -0800
              Re: BASIC Commands Broken After Running BIN Program Bill Chatfield <billchatfield1@gmail.com> - 2019-01-26 13:46 -0800
                Re: BASIC Commands Broken After Running BIN Program gids.rs@sasktel.net - 2019-01-26 14:50 -0800
                Re: BASIC Commands Broken After Running BIN Program Bill Chatfield <billchatfield1@gmail.com> - 2019-01-27 15:04 -0800
                Re: BASIC Commands Broken After Running BIN Program gids.rs@sasktel.net - 2019-01-27 17:44 -0800
                Re: BASIC Commands Broken After Running BIN Program Brian Patrie <bpatrie@bellsouth.spamisicky.net> - 2019-01-27 21:41 -0600
                Re: BASIC Commands Broken After Running BIN Program Bill Chatfield <billchatfield1@gmail.com> - 2019-01-30 14:23 -0800
                Re: BASIC Commands Broken After Running BIN Program Michael Pohoreski <michael.pohoreski@gmail.com> - 2019-01-31 23:05 -0800
                Re: BASIC Commands Broken After Running BIN Program Brian Patrie <bpatrie@bellsouth.spamisicky.net> - 2019-02-02 13:15 -0600
              Re: BASIC Commands Broken After Running BIN Program Bill Chatfield <billchatfield1@gmail.com> - 2019-01-27 15:38 -0800
    Re: BASIC Commands Broken After Running BIN Program Brian Patrie <bpatrie@bellsouth.spamisicky.net> - 2019-01-26 14:04 -0600
  Re: BASIC Commands Broken After Running BIN Program Du Hast <duhast6377@gmail.com> - 2019-01-28 16:54 -0800

csiph-web