OS2 World.Com Forum

Subject  :  Some problems with USB......
Author  :  warped warpme@o2.pl
Date  :  17 Apr, 2004 on 15:22
Hi all,

I have MoBO with USB 1.1 HW (Abit KG7), latest USB drivers (USBMSD v10.135, etc), but using USB is only partial success. My problems are:

1.Attaching 64MB mem key is properly served by system, but read speed is about 55-60 kB/s. I can write with 650-700kB/s, but reading is so slow. Is this normal in OS/2 & USB area ?

2. Attaching mem sticks with size above 64MB is impossible. I already tried 3 different 128M & 1 type of 256M keys - no joy. Have You any ideas what is wrong ?

3. I have 7in1 Genesys reader (ID:0x0927). USBRES recognize my card reader, but after inserting 256MB SD card nothing happens. Order of reader attaching/card inserting doesn't matter - it simply doesn't work. I made some tests with CW USBMSD v1.2b. Using it with IBMRSCSI.FLT & /FORCE_TO_REMOVABLE gives possibility to use my SD card but only one card at system up (for reading another card i need reboot system - there is no effect by refresh after card change - with new card system shows content of previous card).

Have somebody any ideas what is wrong here ?


Subject  :  Re:Some problems with USB......
Author  :  icebear
Date  :  19 Apr, 2004 on 10:57
IBMRSCSI.FLT & /FORCE_TO_REMOVABLE ...
... seems nothing having to do with USB !!!

It seems that your USB is either not complete done (Basic plus respective USB unit related)
or the CONFIG.SYS entries are missing or settings are not matching !

RTFM may help !?


Subject  :  Re:Some problems with USB......
Author  :  Kim
Date  :  19 Apr, 2004 on 12:50
Based on the board specs it can also be due to the fact that it's a non intel based chipset board. I have had problem with SIS-based boards earlier (in your case the board has VIA-chipset). In one case when using SIS-based board I had problem to get USB to work I just shifted over the hard drives to a board that used Intel based chipset and the system worked as supposed.

Having said that I know that it didn't sound that great. But are there other parts that works as it should? For example connecting an USB scanner and using Tame/2 for scanning? USB 3.5" diskette station?


Subject  :  Re:Some problems with USB......
Author  :  Kim
Date  :  19 Apr, 2004 on 18:44
Please attach your config.sys to a reply; it would be easier to check if it's correct.

Subject  :  Re:Some problems with USB......
Author  :  warped warpme@o2.pl
Date  :  20 Apr, 2004 on 21:43
Well,

OK, here is my CONFIG.SYS.
BTW: For last news regarding 7in1 Genesys card reader - please see my posts on "6in1 card reader - intern" thread on this forum...

DEVICE=C:\OS2\LOG.SYS
device=C:\os2\boot\excphead.sys
device=C:\os2\boot\unicode.sys
IFS=C:\eCS\boot\ntfs.ifs /CACHE:4096
REM IFS=C:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:* /CACHE:32000
IFS=C:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:32000
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:64 /AUTOCHECK:C
DEVICE=C:\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
IFS=C:\OS2\FAT32.IFS /Q
CALL=C:\OS2\CACHEF32.EXE /S
IFS=C:\OS2\BOOT\UDF.IFS /Q
IFS=C:\OS2\BOOT\CDFS.IFS /Q /W
PROTSHELL=C:\OS2\PMSHELL.EXE
SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET COMSPEC=C:\OS2\CMD.EXE
LIBPATH=C:\IBMLAN\NETLIB;C:\MUGLIB\DLL;C:\ecs\dll;.;C:\OS2\DLL;C:\MPTN\DLL;C:\IBMCOM\DLL;C:\TCPIP\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\Util\emx\dll;C:\MMOS2\DLL;C:\Util\WarpIN;C:\Util\AMOUSE;C:\Util\StHealth;
SET PATH=C:\MPTN\BIN;C:\IBMCOM;C:\IBMLAN\NETPROG;C:\MUGLIB;C:\ecs\bin;C:\TCPIP\BIN;C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;C:\Util\emx\bin;C:\MMOS2;E:\Cmd;E:\UTIL\Arc;
SET DPATH=C:\MPTN;C:\IBMCOM;C:\IBMLAN\NETPROG;C:\IBMLAN;C:\MUGLIB;C:\ecs\lang;C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\MMOS2;C:\MMOS2\INSTALL;
SET PROMPT=[$p]
SET RESTARTOBJECTS=STARTUPFOLDERSONLY,REBOOTONLY
SET OS=ecs
SET OSDIR=C:\ecs
SET TMP=E:\temp
SET TEMP=E:\temp
SET TMPDIR=E:\temp
SET LOGFILES=C:\Os2\var\log
SET PROGRAMS=E:\programs
SET HOME=E:\home\default
SET UNZIPOPT=-C
AUTOFAIL=YES
SUPPRESSPOPUPS=C
SET DIRCMD=/O:GN/V
SET SHELLHANDLESINC=32
SET NOLARGENTEXEICON=1
VIRTUALADDRESSLIMIT=2048
SET TIMESYNC=0
SET SDDFONTSIZE=MEDIUM
SET SCKILLFEATUREENABLED=ON
SET ENH_STRETCH=NO
SET HELP=C:\MPTN;C:\MPTN\HELP;C:\ecs\help;C:\OS2\HELP;C:\IBMLAN\NETPROG;C:\TCPIP\HELP;C:\MMOS2\HELP;C:\Util\AMOUSE
SET GLOSSARY=C:\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=YES
FILES=64
RESERVEDRIVELETTER=Q
BASEDEV=IBMKBD.SYS
DEVICE=C:\OS2\BOOT\OS2CDROM.DMD
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
DEVICE=C:\OS2\BOOT\TESTCFG.SYS
DEVICE=C:\OS2\BOOT\DOS.SYS
DEVICE=C:\OS2\BOOT\PMDD.SYS
COUNTRY=048,C:\OS2\SYSTEM\COUNTRY.SYS
CODEPAGE=852,850
DEVINFO=KBD,PL457,C:\OS2\KEYBOARD.DCP
SET LANG=pl_PL
SET TZ=CET-1CEST,3,-1,0,3600,10,-1,0,7200,3600
SET ULSPATH=C:\LANGUAGE
BUFFERS=90
IOPL=YES
DISKCACHE=1024,LW,32
MAXWAIT=1
MEMMAN=SWAP,PROTECT
SWAPPATH=C:\OS2\SYSTEM 2048 2048
BREAK=OFF
THREADS=1024
PRINTMONBUFSIZE=134,134,134
SET KEYS=ON
SET BOOKSHELF=C:\IBMLAN\NETPROG;C:\ecs\book;C:\OS2\BOOK;C:\Util\emx\book;C:\TCPIP\HELP;C:\MMOS2;
SET SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;C:\OS2\ETC\WPDSERV.IR;C:\OS2\ETC\REXX.IR
SET SOMDDIR=C:\OS2\ETC\DSOM
BASEDEV=TIMER0.SYS
RUN=C:\OS2\EPW.EXE
RUN=C:\OS2\SYSTEM\LVMALERT.EXE
RUN=C:\OS2\EXTENDFS.EXE *
REM SET DELDIR=C:\DELETE,512;E:\DELETE,512;S:\DELETE,512;Z:\DELETE,512;
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
REM BASEDEV=IBM2FLPY.ADD
BASEDEV=DANIS506.ADD
REM BASEDEV=I2OXPORT.SYS
REM BASEDEV=I2OSOSM.ADD
BASEDEV=OS2DASD.DMD
BASEDEV=OS2LVM.DMD
BASEDEV=CHKDSK.SYS

BASEDEV=IBMRSCSI.FLT

SET EPMPATH=C:\OS2\APPS;
PROTECTONLY=NO
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=C:\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C:\OS2\MDOS\VDPMI.SYS
DEVICE=C:\OS2\MDOS\VDPX.SYS
DEVICE=C:\OS2\MDOS\VWIN.SYS
DEVICE=C:\OS2\MDOS\VW32S.SYS

DEVICE=C:\OS2\BOOT\APM.SYS
DEVICE=C:\OS2\MDOS\VAPM.SYS
RUN=C:\OS2\APMDAEMN.EXE

DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\BOOT\POINTDD.SYS
REM *AMouse* DEVICE=C:\OS2\BOOT\MOUSE.SYS
DEVICE=C:\Util\AMOUSE\AMOUSE.SYS
DEVICE=C:\OS2\BOOT\COM.SYS
DEVICE=C:\OS2\MDOS\VCOM.SYS
SET DEVICEFONTDISABLED=NO

BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$
BASEDEV=USBHID.SYS
REM BASEDEV=USBMSD.ADD /MAX_FLOPPY /FLOPPIES:0
BASEDEV=USBMSD.ADD /FLOPPIES:0 /REMOVABLES:4 /FIXED_DISKS:0 /FORCE_TO_REMOVABLE
REM BASEDEV=USBCDROM.ADD
REM DEVICE=C:\OS2\BOOT\USBKBD.SYS
REM DEVICE=C:\OS2\BOOT\USBMOUSE.SYS
REM DEVICE=C:\OS2\BOOT\USBCOM.SYS
REM DEVICE=C:\OS2\BOOT\USBPRT.SYS
DEVICE=C:\OS2\BOOT\USBRESMG.SYS

REM BASEDEV=CWUSBUHC.SYS /V
REM BASEDEV=CWUSBD.SYS /V
REM BASEDEV=CWUSBMSD.ADD /V /FLOPPIES:0 /REMOVABLES:1 /FIXED_DISKS:0 /FORCE_TO_REMOVABLE
REM DEVICE=C:\OS2\BOOT\USBRESMG.SYS

SET DISPLAYTYPE=VGA
CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
SET NLSPATH=C:\MPTN\MSG\NLS\%N;C:\TCPIP\msg\ENUS850\%N;
SET ETC=C:\MPTN\ETC
DEVICE=C:\MPTN\PROTOCOL\SOCKETSK.SYS
DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS
DEVICE=C:\MPTN\PROTOCOL\AFINETK.SYS
DEVICE=C:\MPTN\BIN\VDOSTCP.VDD
RUN=C:\MPTN\BIN\CNTRL.EXE
CALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL
RUN=C:\IBMCOM\PROTOCOL\NBTCP.EXE
RUN=C:\MPTN\BIN\VDOSCTL.EXE
DEVICE=C:\IBMCOM\PROTOCOL\TCPBEUI.OS2
DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2

REM BASEDEV=DANIATAP.FLT

CLOCKSCALE=4
RUN=C:\ECS\SYSTEM\ECLOCK\CLKBASIC.EXE
SET DMIPATH=C:\OS2\DMISL\BIN
RUN=C:\OS2\SMSTART.EXE
SET CLASSPATH=
RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE
DEVICE=C:\IBMLAN\NETPROG\VNETAPI.OS2
RUN=C:\IBMLAN\NETPROG\VNRMINIT.EXE
RUN=C:\OS2\SYSTEM\LOGDAEM.EXE
RUN=C:\OS2\EPWROUT.EXE 1
SET NWDBPATH=C:\IBMLAN\NETPROG
SET DLSINI=C:\IBMLAN\NETPROG\NETGUI.INI
SET INIT_FILE_NAMES=netgui
SET INIT_FILE_RANGES=200
SET WPS_COMMUNICATION=YES
SET LANINSTEP=S:\cid\server\ibmls
SET TCPLANG=pl_PL
DEVICE=C:\TCPIP\bin\vdostcp.sys
SET VCFG_NO_DDC=TRUE
SET USE_HOSTS_FIRST=1
SET HOSTNAME =MyComputer
SET MMBASE=C:\MMOS2;
SET DSPPATH=C:\MMOS2\DSP;
SET NCDEBUG=4000
RUN=C:\MMOS2\MIDIDMON.EXE
DEVICE=C:\MMOS2\SSMDD.SYS
DEVICE=C:\MMOS2\R0STUB.SYS
DEVICE=C:\MMOS2\MIDI.SYS
DEVICE=C:\MMOS2\VCSHDD.SYS
RUN=C:\MMOS2\QRYMMCD.EXE
SET MOZILLA_HOME=E:\OS2Apl\Ns50
DEVICE=C:\IBMCOM\MACS\E100B.OS2
RUN=C:\Util\StHealth\StHDaem.exe
DEVICE=C:\MMOS2\UNIAUD32kee.SYS
DEVICE=C:\MMOS2\UNIAUD16.SYS /C
DEVICE=C:\Util\VirtualPC\vpcapp.sys /Q
DEVICE=C:\OS2\BOOT\ASPIROUT.SYS
BASEDEV=OS2ASPI.DMD /ALL

REM *** WatchCat 2.1 device driver - REQUIRED
REM DEVICE=c:\util\wc\WATCHCAT.SYS /Q KEYB:A-W
REM *** WatchCat 2.1 main program - REQUIRED
REM RUN=c:\util\wc\WATCHCAT.EXE
REM *** WatchCat 2.1 Process Manipluation Center Driver
REM DEVICE=c:\util\wc\KILLER.SYS /Q
REM *** WatchCat 2.1 CAD Package Virtual Device Driver
REM DEVICE=c:\util\wc\VWCAT.SYS
REM *** WatchCat 2.1 CAD Package Control Program
REM RUN=c:\util\wc\WCCAD.EXE

DEVICE=C:\Util\wc\xf86sup.sys
DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=C:\OS2\MDOS\VSVGA.SYS
SET GRADD_CHAINS=C1
DEVICE=C:\OS2\GRADD.SYS
DEVICE=C:\OS2\MDOS\VMANWIN.SYS
SET GREEXT=SDDGREXT
SET C1=SDDGRADD,VRAMMNGR,WOVERLAY
DEVICE=C:\OS2\SDDHELP.SYS /Q
DEVICE=C:\IBMCOM\PROTOCOL\SWITCH.OS2

BASEDEV=cadh.sys
BASEDEV=IBMATAPI.FLT


Subject  :  Re:Some problems with USB......
Author  :  Kim
Date  :  21 Apr, 2004 on 12:21

warped (20 Apr, 2004 21:43):
Well,

OK, here is my CONFIG.SYS.
BTW: For last news regarding 7in1 Genesys card reader - please see my posts on "6in1 card reader - intern" thread on this forum...


Ups! This got hard to read; please modify the posting by removing the entire config.sys and instead attache the config.sys as a file attachment. This is done by marking the Preview your post and/or attach a file? just above the Post button.


Subject  :  Re:Some problems with USB......
Author  :  warpcafe warpcafe@yahoo.de
Date  :  21 Apr, 2004 on 17:04

sam (19 Apr, 2004 10:57):
IBMRSCSI.FLT & /FORCE_TO_REMOVABLE ...
... seems nothing having to do with USB !!!

It seems that your USB is either not complete done (Basic plus respective USB unit related)
or the CONFIG.SYS entries are missing or settings are not matching !

RTFM may help !?


Sam,
I'm not sure about what you mean by this... does that really mean, that IBMRSCSI.FLT and /FORCE_TO_REMOVABLE have nothing to do with USB-attached MSD devices?
I doubt that this is correct if Manolo runs a SCSI-drives based system...
Also, "RTFM" may not really be of great help here, unless you precise the actual manual in question...: The IBM USB drivers manual, CW's drivers manual, the USB group red book, the RSCSI readme...? I run both IDE and SCSI-only systems here. While the IDE systems work quite "out-of-the-box" in matters of USB, the SCSI systems require a lot of additional work in order to make them "recognize" USB MSD devices at least.

Manolo:
How did you actually do the "refresh" of the drives folder? By using the LVM "refresh removable drives" object? Did the system "react" to this at least - e.g. "pausing" a little?

Greetings
Thomas


Subject  :  Re:Some problems with USB......
Author  :  Cris
Date  :  23 Apr, 2004 on 11:34
Hi Warpcafe,

> the SCSI systems require a lot of additional work in order to make them "recognize" USB MSD devices at least.

What do you mean by this? I have a mixed scsi-ide system, and I'm having *BIG* problems using an USB memory key (You can find a thread in this same area, regarding problems with an Hamlet eXagerate 128Mb pen drive). I can not even have the system *recognize* that the key has been inserted (even with the new 10.135 MSD drivers).

Please, if you have some more suggestions I'd like to hear from you. I didn't even know that having a SCSI system might change the way USB MSD devices are recognized.

Thankyou!
Bye

Cris


Subject  :  Re:Some problems with USB......
Author  :  Kim
Date  :  23 Apr, 2004 on 12:19
What about the system IRQs are there any overlaps? If the USB controller share the irq with some other device, try to use another IRQ if possible. I noticed on an laptop that shared IRQ betwen the cardbus and USB-controller made the system to not pick up the usb key memory.

Subject  :  Re:Some problems with USB......
Author  :  Kim
Date  :  23 Apr, 2004 on 12:24
Regarding the following line:

BASEDEV=USBMSD.ADD /FLOPPIES:0 /REMOVABLES:4 /FIXED_DISKS:0 /FORCE_TO_REMOVABLE

Have you tried just to run with:

BASEDEV=USBMSD.ADD

I played around with the parameters as well, but adding too many parameters just made my system to ignore the USB memory. Do you actually have 4 removable units? Try to strip of the paramters and see how it works out.


Subject  :  Re:Some problems with USB......
Author  :  warpcafe warpcafe@yahoo.de
Date  :  23 Apr, 2004 on 17:07

Kim (23 Apr, 2004 12:19):
What about the system IRQs are there any overlaps? If the USB controller share the irq with some other device, try to use another IRQ if possible. I noticed on an laptop that shared IRQ betwen the cardbus and USB-controller made the system to not pick up the usb key memory.

Folks,

this reminds of another fact - maybe this could help to some degree:
If the USB controller is "onboard" (I don't remember if that was said above somewhere already) you can always try to run it "IRQ-free". Most of the contemporary BIOSes support a setting of "assign IRQ to USB = disabled" or something like this. As far as I've tested it with one of my IDE machines, it seems to run flawlessly in eCS. The controller thus operates without IRQ assignment and it'll not only free up an IRQ but also avoid possible IRQ conflicts. You might know the same kind of BIOS setting from the graphics adapters ("assign IRQ to VGA = disabled").

Greetings
Thomas


Subject  :  Re:Some problems with USB......
Author  :  warpcafe warpcafe@yahoo.de
Date  :  23 Apr, 2004 on 18:42

Cris (23 Apr, 2004 11:34):
Hi Warpcafe,

> the SCSI systems require a lot of additional work in order to make them "recognize" USB MSD devices at least.
(snip)
Please, if you have some more suggestions I'd like to hear from you. I didn't even know that having a SCSI system might change the way USB MSD devices are recognized.

Thankyou!
Bye
Cris


Cris,

I'll do my best, but I can't promise you the perfect solution to this question. Certainly, I might not know all the facts about how OS/2 operates with MSD's in general and how this is related to SCSI... but I
am quite sure, that the device driver model of OS/2 relates somehow to
the MSD stuff...

I always wanted to find someone who explains me how the layers of drivers are ordered and how they operate in conjunction, but... maybe I'll ask Daniela Engert at Warpstock Europe. Storage device driver programmers should at least be able to explain what depends on what... so be warned, that I might have a wrong picture of it!

With USB, you first have the lowest "layer" of drivers: Those who operate UHCI, OHCI or EHCI controllers (like USBUHCD.SYS).
On top of that, you'll find the next layer which basically "unifies" the different controllers towards the next layer. This is USBD.SYS.
Then, the USB drivers start to differ depending on the type of USB devices (USBCDROM.ADD, USBMSD.ADD, ...).

The *core* question now is, whether USBMSD.ADD does everything needed to show up a USB MSD device as a drive. I'm not sure. I think that there is some more dependency with the OS2DASD.DMD driver. But again, I'm not sure.
I think that USBMSD.ADD simply provides the driver layer to OS/2 so that the next layers of drivers treat the USB device like a disk, maybe by prividing a kind of "hook" into either IDE or SCSI drivers.

In addition, I don't know if the IBMRSCSI.FLT does provide a "parallel yet different" way of talking to such devices or if it needs to run on top of the other stuff.
Gheee... I knew everything about SCSI and OS/2 before USB came out. Now it sometimes leaves me puzzled. Most of the time, when USB doesn't work in OS/2, I find it extremely difficult to find out *where* the problem actually is - at least on SCSI systems...

Maybe some day, I'll know the truth about USB on OS/2... if I will, I'll certainly drop by here to let you know. But for now: sorry,
I think, I'll better ask some device driver programmers...

Greetings
Thomas


Powered by UltraBoard 2000 <www.ub2k.com>