[Coco] NOS9 mb script
Chester A Patterson
vchester at setec-cr.com
Tue Oct 31 08:46:39 EST 2006
I EZGen'd scbbt and T1 (in that order) in right after SCF, rebooted, and
it didn't work (freeze boot)
I'll try other locations.
Another curious problem.
I made a TERM_32 bootfile. Boots fine, until startup gets to wcreate,
then everything freezes. If I omit the wcreate commands in startup,
boots fine. When I try to wcreate from TERM (32), again deep freeze.
What gives? Thanks.
-----Original Message-----
From: Robert Gault [mailto:robert.gault at worldnet.att.net]
Sent: Monday, October 30, 2006 6:40 PM
To: CoCoList for Color Computer Enthusiasts
Subject: Re: [Coco] NOS9 mb script
Chester A Patterson wrote:
> The mb script in NOS9 MODULES/SCRIPTS has a line that confuses me
> Merge ../MODULES/BOOTTRACK/rel_80 ../MODULES/BOOTTRACK/boot_1772_6ms
> ../MODULES/krn >-bttemp
> Note the dash ("-") at the beginning of -bttemp OS9Gen %1 -t=bttemp
> <../BOOTLISTS/standard.bl Where'd the dash go? Is it a typo? If not,
> what's its purpose?
> Reason I ask is I'm manually making different boot disks. I merged
> several different rel boot krn combinations, naming them one thing or
> another, and OS9Gen isn't cooperating completely when I do the
> -t=boottrack option.
> Also, where's the best place to locate the T1.dd and it's
> corresponding driver? Right after SCF on boot gives me either
> sparklies or just freezes.
> Thanks. /Chester
>
I've removed the - from >-btemp whenever I've used this script. In
short, I think it is a typo.
The location of T1 in os9boot should not be an issue. You normally place
descriptors closely after their driver probably so it increases the
chance they are in the same block of memory. For recent NitrOS-9
distributions, the driver is scbbt not SCF which is the manager.
More information about the Coco
mailing list