#OS/2 DriverJuneVersERROR
13-Jul-93 15:07:04
Sb: #907-#OS/2 DriverJuneVersERROR
Fm: Rainer-Detlef Stroebel 100064,3470
To: Jack [ Trantor Systems ] 71333,2450
Hallo Jack,
thanks for your quick answer about point 4 of my problem report.
I assume Trantor is working on point 1 to 3.
Now to point 4:
> Option /o for the add driver: no differece, MO still a floppy
Yes, this is the way IBM sees removable media. That's not a bug, it's a
feature! <
>>If you use the IBM OPTICAL.SYS driver, you need to format the MO cartridge as
though it is a floppy… and don't use the /o option in that case. I chose
1.44M as a floppy capacity and OS/2 happily formatted it to 120M. <<
I have made two additional test:
Test 1 Optical.sys in config.sys
T128SCSI.ADD with /O
Result: Optical.sys not installed ( message see problem Report )
Drive folder: MO is floppy ICON
Action Check DISK: okay 128 MB
Action eject : Error Message:
Drive J: is not formatted correctly,
or is not wroking correctly.
Test 2 Optical.sys in config.sys
T128SCSI.ADD without /O
Result: Optical.sys not installed ( message see problem Report )
Drive folder: MO is floppy ICON
Action Check DISK: okay 128 MB
Action eject : Error Message:
Drive J: is not formatted correctly,
or is not wroking correctly.
Questions:
So when is the MO handled as HD ??
By handling the MO as floppy the eject action should work !
Rainer