TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Zack Sessions 71532,1555 (X)
from: Bob van der Poel 76510,2203
date: 1993-05-27 19:32:35
subject: #18191-#strange happening?!?

#: 18194 S12/OS9/68000 (OSK)
    27-May-93  19:32:35
Sb: #18191-#strange happening?!?
Fm: Bob van der Poel 76510,2203
To: Zack Sessions 71532,1555 (X)

This really sounds just like the problem I had when I first got my 2nd HD! But,
I find it hard to believe that it is only hitting you now...must be another
problem. But, just in case it isn't (and for others too), when I got my 2nd HD
I followed the instructions in the mm/1 tech manual to create a descriptor for
H1. Kids--don't do this at home; it doesn't work!

Each descriptor for a HD on a SCSI bus must have a different controller ID AND
it must have a different PORT. To check, do a DMODE -p /h1 and then /h0. Make
sure the port=xxx is different. This is easy to do if you use the desc.
supplied with the upgrade stuff.

From my understanding (which could be WRONG) the least significant byte in the
port address is ignored as far as finding the scsi port is concerned; but it is
used by the driver to determine that /h1 and /h0 are different devices. I'm not
sure why it just doesn't use the controller ID, but it doesn't.

BTW, as a matter of interest I have the attributes on /h1 set to super-only
access. If I logon as user 3.3 I CAN do a free /h1; but not a dir /h1.

Hope this helps...

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