🚀 go-pugleaf

     I've got a rather nasty problem with OS9.  About two hours ago,
aa corrupted bootfile forced me to restore from a backup.  This boot
was an exact copy of the bootfile I have just been using.  However,
it booted up in the wrong colors, without a cursor.  I modpatched
the /TERM descriptor for the proper colors and cobblered a new boot
disk, but I _cannot_ generate a cursor!

    display 05 21

    does <not> work!  The cursor comes on momentarily, but only for
an instant, and is then erased as the next command line appears.   I
thought perhaps it was a palette problem (who knows?), so I played
with the palettes for about a half an hour.  Then, I thought, maybe
display is bunged up, so I started Basic09 and used

    run gfx2("curon")

    which also did not work.  Another interesting fact:  I have
KDUtils and the OSk dir command merged with Shell (and ident shows
Shell to be at the very top of the list in the file on disk).
However, on bootup, an MDir reveals that shell was the _last_ module
linked, behind the kdutils, dir, and also RunB, which is loaded by
startup!  Is it possible that a file gets loaded, and every included
module is linked with the exception of the first?

    At the moment, I am using KBCom, as it appears to generate its
own cursor (no other program has one, including, as explained,
shell, and one cannot be generated with CC3IO codes, also as
explained).

    Does anybody have any ideas?  As a last resort, I will replace
every module individually within OS9Boot.  However, even with EZGen,
it will be quite a task to track down a backup of each module, patch
it with PowerBoost and any other patches, configure it, and install
it in OS9Boot, and I'd rather not do it unless nothing else will
work.

    Thanx for any help anyone can give me!
  - A. Hsiao
  (jzr@onlybbs.via.mind.org)
  (lizarden!jzr@xmission.com)
  (zog!jzr@abode.ttank.com)

--
via Fortress Gateway at uumind.mind.ORG