Re: Sweet16 and GS/OS Booting

[A2Aviator <a2aviator@gmail.com>]

It's basically never not worked that way for me, ever since System
Disk 1.1, the first time I put ProDOS onto a hard drive, it took me
several months after the IIgs came out to finally switch to ProDOS. I
had DOS 3.3 on the hard drives until the Summer of 1987 when I
switched it. A friend came over one day and saw my drive boot into
ProDOS and about had a heart attack. Cold turkey, I switched. The IIgs
file sizes and running a BBS, dealing with downloads at the time
pushed me over the edge. I switched the whole BBS to ProDOS, that was
a marathon 16 hour session of redoing BASIC files, all the chain
commands I was using to retain variables between loads, etc.

.. so I switched to having ProDOS 16 be a file called "P16" in the
root, and I'd just boot into ProDOS 8 and do '-P16' when I wanted to
launch something for the IIgs.  Because it took so long to load, if I
didn't want it, I had to wait.

Pressing '8' at boot on Sweet 16 is a real challenge. You have to be
fast.

I've never had the -GSOS method employed on Sweet 16 because it
boots .. *fast*. Three eyeblinks and it's at ProSEL 16. I can easily
select BASIC from there, if I didn't manage to get the '8' pressed in
time.

So, I tried doing the rename thing this morning and after a short
delay I am presented with "Unable to load START.GS.OS file. Error=
$0046" which is file not found.

Works on GuS, KEGS.. even on Virtual II - except I'm presented with
the proper error there, "GSOS REQUIRES APPLE IIGS HARDWARE" ;-)

So I moved the 'GSOS' file into the system directory just for craps
and laughs. Same thing, it's probably hardwired to look inside /system
anyway.

Sweet 16 does nothing on the high level, but it would appear that the
path is somehow getting mangled. The GSOS Boot loader needs to
determine if the SmartPort or ProDOS is called. I suspect it's
determining to call the SmartPort and not ProDOS here, and the former
isn't working.