TIP: Click on subject to list as thread! ANSI
echo: cis.telecommunications
to: REX GOODE 73777,3663 (X)
from: Pete Lyall 76703,4230
date: 1991-10-04 15:50:02
subject: #12501-#Age old deskmate problem

#: 12508 S7/Telecommunications
    04-Oct-91  15:50:02
Sb: #12501-#Age old deskmate problem
Fm: Pete Lyall 76703,4230
To: REX GOODE 73777,3663 (X)

Ugh...

Essentially you'll need to build a new bootfile using your favorite tool (i.e.
either OS9GEN, COBBLER, or CONFIG).

I believe that M1's associated driver is ACIAPAK. If that is true (you can do a
'dump M1' on the M1 device descriptor module on your disk and verify that it
says ACIAPAK), if your standard kernel already has ACIAPAK in it, you're not
too far off.... You can put the disk with M1 on it in the drive and type
something like:

   load /d1/modules/M1.dd

to get it into memory, and then insert your deskmate disk into a drive and type
something like:

  cobbler /d? (where ? is the target drive)

If none of this looks like it will work, you'll need to 'hand build' a new
kernel. That involves taking your current bootfile, splitting it into modules
(get the bootsplit utility in DL9 or DL10), making a list of them, and then
adding the M1 to both the list and the group of modules. Then you'd use OS9Gen
to glue them all together again, uisng the list to drive OS9Gen's input.

Let me know how (or if) you fare....

Pete



There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.