OS/2 DriverJuneVersERROR
6 messages in this thread
Hallo Jack,
here are my problem report about OS/2 add drivers June / May Versions
Hardware: IBM P70 with T228 and HD FUJITSU M2623S-512
and CDROM NEC CDR 38
and MO FUITSU 2511A
second P70 with T338
Softeware: IBM dos 5.02 and trantor dos aspi drivers
OS/2 2.1 and trantor drivers
June Version T128SCSI ADD 25857 22.06.93 11.47
T338SCSI ADD 24881 7.06.93 14.15
May Version T128SCSI ADD 22521 4.05.93 14.28
T338SCSI ADD 23125 4.05.93 14.28
April Version T128SCSI ADD 22213 13.04.93 15.51
T338SCSI ADD 22837 13.04.93 15.51
Sep. 92 Vers. T128SCSI ADD 22125 15.09.92 15.59 :
T338SCSI ADD 21817 15.09.92 15.59
The following problems are in JUNE / May / April Version
1. Check disk on SCSI HD report errors.
see enclosure for check disk output with june version
CHKDSK with /F option destroys the FAT
works fine with Sept 92 Version
2. Does not work with Bookmanager Read/2
by condition of scsi HD and CDROM access from same application.
IBM CD Online Starter Kit SK2T-2071-00
June Version stops with sys2070
May und April report different error messages
Application works with Sept. Version
3. Option /o for the add driver: no differece, MO still a floppy
This is tested with june 93 and sept 93 Version
4. Use of optical.sys Version 2.1
OPTICAL.SYS 16436 22.02.93 16.09
reports at boot:
IBM Optical Device Driver
Version 2.01
SCSI-DD linked
SCSI-DD error = FF0C
NO SCSI devices found
This is tested with june 93 and sept 93 Version
Looking forwared for solutions
regrads
Rainer
enclosure:
The volume label in drive G is G_LOG_100.
The Volume Serial Number is E5FA:5014
Directory of G:\
COBINFO BTX 1487888 13.04.91 10.11
E-ALT <DIR> 20.09.92 20.52
TWIN-C <DIR> 20.09.92 21.03
TWIN-E <DIR> 20.09.92 21.04
CDRIVE <DIR> 20.09.92 21.18
WORD5 <DIR> 20.09.92 21.32
C600 <DIR> 20.09.92 21.34
DOS50 <DIR> 20.01.93 21.43
DOS50C <DIR> 20.01.93 21.46
OS20-D <DIR> 9.07.93 21.42
OS2-D <DIR> 9.07.93 21.54
11 file(s) 1487888 bytes used
12333056 bytes free
The type of file system for the disk is FAT.
The volume label is G_LOG_100.
The Volume Serial Number is E5FA-5014
Errors found. F parameter not specified.
Corrections will not be written to disk.
The first cluster number of G:\E-ALT\VIR91\SCAN91.DOC is incorrect.
The entry has been truncated.
The first cluster number of G:\E-ALT\VIR91\SCAN91!.EXE is incorrect.
The entry has been truncated.
The first cluster number of G:\TWIN-C\DOS\MOUSE.COM is incorrect.
The entry has been truncated.
.
.
. etc etc
.
The first cluster number of G:\TWIN-C\DOS\……… is incorrect.
The entry has been truncated.
G:\TWIN-C\DOS\……… attempted to claim an extended attribute that does
not exist. The error was corrected.
The first cluster number of G:\TWIN-C\DOS\……. is incorrect.
The entry has been truncated.
G:\TWIN-C\DOS\……. attempted to claim an extended attribute that does
not exist. The error was corrected.
SYS1349: G:\TWIN-C\DOS\….. is an incorrect subdirectory.
ENDE OF OUTPUT CHKDSK G: > F:\rep.000
The …. in the last file names repesents just nonprintable,
rubbisch ascii symbols.
a lot of sys1349 messages on con , but not
by CHKDSK G: > f:\rep.000
by redirection of output the OS Command machine hang
just after this last line on the file and 6-7 messages lines
of sys1349 on con.
> 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.
We're revisiting the OPTICAL.SYS driver to see if we cam get it released with
the shrink wrap. No promises yet, but we are working on it. I'll post any
updated information here.
We're also looking into making MOs more than just large floppies…. and to
allow HPFS and caching. Stay tuned.
–Steve
Steve, thanks for dropping by! That's good news, all right.
I look forward to the new level of support you guys can provide.
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
If you use the /o option, OPTICAL.SYS will not load.
You then have to select it and use the FORMAT program to format it. It will
report being a floppy drive since that is the way all removable media is seen
right now. Format it as a floppy… if you don't format it under OS/2, then
you won't be able to read it. You can not take a DOS formatted disk and use it
under OS/2.
If OPTICAL.SYS doesn't load, it usually means the MO drive isn't responding
with the correct information… it must report that it is an optical drive so
OPTICAL.SYS will load. The MO drive under OS/2 NEVER gets treated like a hard
disk drive by the operating system. IBM is working on a fix for that, from
what I hear.