[Coco] OS9 Script scope.

[Bill Pierce]

This happen because the shell being run during "startup" is only temporary and dies with startup so any settings to that shell die with it.
There is an alternative "sysgo" in the repo that allows you to set multiple cmd directories during the boot. I think the source is labled "sysgo_bd.asm" as the original was by Bob Devries.
I use this particular sysgo in the Coco3FPGA build in the repo, so if you get one of the Coco3FPGA disks, you can pull the sysgo from that. Just replace the stock sysgo with the one from the CocoFPGA disk.
To use this feature, you must create a text file in /DD/SYS named "config.os9". In this file you type one line:

i=/1 PATH=/dd/cmds /x1/cmds (etc) chd /dd

This will set both /dd/cmds & /x1/cmds as default as well as /dd as default data dir. If this file is not found, it will default to /dd/cmds and /dd

hope this helps :-)
 
 
 
-----Original Message-----
From: coco <coco at jechar.ca>
To: Coco List <coco at maltedmedia.com>
Sent: Mon, Feb 25, 2019 9:40 pm
Subject: [Coco] OS9 Script scope.


  When a paticular Nitro system I am working with starts up it runs the
  "startup" program.

  One command in the startup script is

  cx /x2/cmds

  to access the much larger set of commands on the drive wire server as 
verses
  the 35 track /dd.

  If I start a new shell from the script with

  shell i=/w7&

  it has access to all these extra commands.

  But the /term window loses access to the drive wire command directory 
as soon as
  the startup script exits and I need to type cx /x2/cmds to gain access 
again.

  Is there any way to make the cx /x2/cmds in startup stick around after 
startup exits.

-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco