TIP: Click on subject to list as thread! ANSI
echo: cis.tandy.coco
to: Kevin Darling
from: Zack Sessions 76407,1524
date: 1990-05-05 12:00:51
subject: #Second Ramdisk solved

#: 3286 S10/Tandy CoCo
    05-May-90  12:00:51
Sb: #Second Ramdisk solved
Fm: Zack Sessions 76407,1524
To: Kevin Darling

Kev,

OK, I figured out this second ramdisk problem though a process of trial and
error. What I was doing wrong was that I was also patching the IT.DRV field
("Drive Number" @ $13) from a $00 to a $01. That appears to have been a no-no.
Leaving it a $00, patching $10 to a $01 and the drive name to /r1 (with upper
bit in 1 turned on, of course!) does the trick. FYI, one iteration involved
changing the Address field in the header to the value you use in your r0 dd in
drive /r0 and added one for /r1. That worked too! Wonder why the Dev Pack
ramdisk dd are all zeros in the address field?

Zack

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