TIP: Click on subject to list as thread! ANSI
echo: cis.os9.6809.coco
to: Kevin Darling (UG Pres) 76703,4227 (X)
from: Paul Hanke 73467,403
date: 1990-10-04 17:33:41
subject: #7089-#Rdisk

#: 7179 S10/OS9/6809 (CoCo)
    04-Oct-90  17:33:41
Sb: #7089-#Rdisk
Fm: Paul Hanke 73467,403
To: Kevin Darling (UG Pres) 76703,4227 (X)

Well, I did it!  I got /d2 to work from the MV screen.  Had to edit BUILDMV so
that d2_35S.DD got copied.  Made a new mv #2 disk and it worked out fine.  If I
am catching on to what is happening, buildmv copies selected files already in
memory from the initial OS9 system disk.  Then it generates a bootable OS9 type
procedure on track 34 using OS9GEN and creates a bootlist.mv besides.  This is
necessary because there cannot be any uncontiguous sectors during the mv boot
which would occur if one tried to add a module to a previously made boot disk
as I tried to do initially.   -ph-

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™.