[Prev][Next][Index][Thread]

Re: Beta 0 #3 cannot see HFS drives.



On 25 Apr 96 at 21:30, EADEANS wrote:

>I tried out Beta 0 #3 last night and saw that it (like 1.99q12) cannot see
>HFS volumes attached to my computer via my Adaptec SCSI card under Warp.
>Version 1.99 could see the volume but not write/read--some kind of
>browser/executor "access error"...
>
>It works fine under DOS 5 but Warp support for reading HFS volumes is
>*extremely* important to me. I'm using the latest Adaptec drivers (Warp
>FixPak 17).

Two thoughts come to mind:

1. (probably obvious) You need to have virtual ASPI support for DOS 
sessions loaded, which if memory serves is done by having the lines

BASEDEV=OS2ASPI.DMD
DEVICE=x:\OS2\MDOS\VASPI.SYS (where x = boot drive)

in CONFIG.SYS.

2. It is possible that the OS/2 drive manager, OS2DASD.DMD, is allocating 
the drive preventing it from been seen via ASPI (unlike DOS, under OS/2 
only devices not allocated by other managers can be accessed via ASPI). There 
are two possible workarounds for this situation:

a) There's a switch for the BASEDEV (.ADD) that prevents specified SCSI 
IDs from being allocated by OS2DASD.DMD - I can't remember what it is, 
but HELP BASEDEV should provide the starting point. The disadvantage, if 
the device is removable, is that PC-format disks will be inaccessible to 
OS/2 with this switch in effect.

b) Adding the switch /ALL to the OS2ASPI.DMD command line will allow 
access to all devices even if allocated to other managers. This is risky 
as this potentially allows other DOS programs to affect/corrupt devices 
in use by OS/2. You may also require the switch /SHARE as well to prevent 
devices from being locked by the DOS session; see online help for more 
info.

Hope this helps.