#: 7409 S12/OS9/68000 (OSK)
    16-Oct-90  01:09:55
Sb: #7403-Help with PT68-K4 OS9
Fm: Kevin Darling (UG Pres) 76703,4227
To: Jack Crenshaw 72325,1327 (X)

Hi Jack (btw, where do you live? might be some help nearby) -

The OS9boots are probably different because they added something to one or the
other.  Do an "ident -q /d0/os9boot"  and see what modules are in each disk's
os9boot file.

Yah, "fixmod -u filename" will update a CRC if you changed the module. However,
if you yourself didn't change it on purpose , using fixmod is a bad
idea... the CRC being bad indicates that surely something in the module is
hosed, and fixmod can't fix that.  The CRC is there just to prevent loading
such a bad module.

Backup - did you get Basic?  You could use it or C or asm to write a quick and
dirty backup util.  The first 3 bytes on any OS9 disk give the number of
sectors on that disk.  So a simple backup program in Basic would be:

 PROCEDURE backup
 DIM count(3),sector(256):BYTE
 DIM path1,path2,total,x:INTEGER
 INPUT "from drive name ",source$
 INPUT "to   drive name ",dest$
 OPEN #path1,source$+"@":READ
 OPEN #path2,dest$+"@":WRITE
 GET #path1,count
 total=count(1)*65536.+count(2)*256+count(3)
 SEEK #path1,0
 FOR x=1 TO total
  GET #path1,sector
  PUT #path2,sector
 NEXT x
 END

All that does it to open each disk in raw (full disk) mode (the "@" does that
special - like "/d0@")... then go through and copy each sector.  Lots of ways
to speed this up of course, like doing more bytes at a time.  You can also get
fancy and get the drive names from the parameter line, etc.

Did PT know how much RAM you had, btw?  The Init module needs to know that.
Does "mfree -e" jibe with your system? best  - kev