> Your advice was great!
>=20
> I've managed to see all the disc capacity installing Chris's USB
> Mass Storage Device Driver, on a IBM USB driver, as stated on
> http://www.os2warp.be/index2.php?name=3Dusbremovables for a not so
> different Maxtor 120 GiB unit. But there lacks the information
> on the partitioning problem, so i'll report it.
>=20
> The FORCE_TO_REMOVABLE option was mandatory to see the disc
> registered in the system.
>=20
>=20
> Thanks!
>=20
> Delf=ED
>=20
> P.S This way we can go for larger drives, without fear of going
> out of space.

Hi Delfi

The latest IBM drivers should have worked also.  Chris's driver was
the only solution in town until IBM released their last drivers.  To
illustrate, here is my list of the USB devices I have working with eCS
1.2, that I can plug in at any time, eject, and plug in again without
any problems.

Sandisk       128 MB USB stick
Pony Attache  256 MB USB stick
Sandisk       512 MB USB stick
Memorex         1 GB USB stick

USB Zip drive - 100 MB

8 GB drive in an USB BAFO hard drive enclosure
4.3 GB 2.5" drive in an USB BAFO hard drive enclosure
40 GB 2.5" drive in an USB Enermax enclosure

All formatted FAT32. All read by Windows and eCS 1.2 with the latest
FAT32 driver installed.

6-in1 generic card reader

IOMagic CDRW 52x24x53 USB writer with 6-in-i reader built in.=20
Although I can't write to the writer, it has no problems reading a
CDROM. Also the 6-in-1 card reader works fine.=20

Here is a procedure I use to get my USB devices to work.

GETTING THE USB DRIVER TO WORK WITH REMOVABE MEDIA

If your USB removable drive is not recognized, or you are unable to
read and write to it, read the following procedure.

 1.Your motherboard bios must support USB devices.  Make sure USB
support is enabled in the motherboard bios.  A very good control card
to use is the Belkin 5 port USB 2.0 card if you are having problems
with the USB controllers on your motherboard.

 2.The USB drivers by IBM work best with the most recent os2krnl,
os2ldr, and ibmdasd drivers. Install them next if you have not already
done so.

 3.Always update to IBM's latest USB drivers. Reboot and test USB
devices. If they work, you need go no further. If not, proceed to to
next step.

 4.Check to make sure that you have lines similar to those listed
below in your config.sys. I like using the /V option because it tells
one whether the necessary drivers are loaded or not at bootup.  The /V
option can always be removed later when your USB device are working
properly.

REM BASEDEV=3DUSEUHCD.SYS /V
BASEDEV=3DUSBOHCD.SYS /V
BASEDEV=3DUSBOHCD.SYS /V
BASEDEV=3DUSBEHCD.SYS /V
BASEDEV=3DUSBD.SYS
BASEDEV=3DUSBHID.SYS
BASEDEV=3DUSBMSD.ADD /FLOPPIES:0 /REMOVABLES:2 /V
rem BASEDEV=3DUSBCDROM.ADD

Set the REMOVABLES option to the max number of USB devices you plan to
have plugged in at one time.

Keep a copy of the file "hcimonit.exe" in a directory found in your
config.sys Path statement. This file normally comes with the IBM's USB
drivers. This program will list the type of host controllers found on
your system.  At a command prompt, type "hcimonit.exe".

In this example, this computer has 2 USB OHCI host controllers and 1
USB EHCI host controller.  Thus, the following three lines would need
to be found and if, not added to the config.sys file.

BASEDEV=3DUSBOHCD.SYS /V
BASEDEV=3DUSBOHCD.SYS /V
BASEDEV=3DUSBEHCD.SYS /V

 5.Create a compatibility volume using LVM if you have not already
done so. Check to see if your drive is recognized by LVM. Removable
drives usually have an * instead of a drive letter. I suggest that you
assign a permanent drive letter. I have found that some USB media
won't be recognized unless they are assigned a drive letter. If your
media still is not recognized, go to next step.

 6.If the drive worked in the past, try running "chkdsk : /F".
Continue on if your drive still doesn't work.

 7.Check to see if you have the following statement in your config.sys
file.

BASEDEV=3DOS2PCARD.DMD

If it does exist, try remming it out and rebooting. Try your USB
devices again. If your USB devices are found and functioning properly,
you need go no further.

Note:  It has been reported that the Card bus 8 driver does not
conflict with the USB drivers. However, other problems are introduced.
eCS 1.2 comes with the Card bus 5 driver. Thus, if you are using eCS
1.2, you will either need to rem out the driver or install the Card
bus 8 driver. If you still don't have your device(s) working, read
further.  NOTE: It has been reported that the latest just recently
released Cardbus 8 drivers by IBM conflict with the USB drivers again.

 8.Some USB flash media comes with security software. With this
software on the media, the drive(s) cannot be read by the IBM drivers
{LVM included). To overcome this, try the following:

 Use DFSee (in my opinion, this is a must utility for every eCS and
OS/2 user) to create a new Master Boot Record with the tables erased.
If you don't have it, download the latest version. It can be used in
demo mode.

DFSOS2.EXE > Mode=3Dfdisk > New MBR code, ERASE tables > Select the
correct drive > OK

 9.Use LVM create a new partition.

10.Make the drive Primary.

11.Using LVM, make the media a compatibility volume.

LVM > Volume > Create Volume > Create non-bootable volume > Create
Compatibility Volume

12. Format the media next. You can either format the media FAT, HPFS,
FAT32, or JFS. Formatting FAT32 requires that you have access to a
Windows machine with either Windows 98 second addition, Windows ME, or
Windows XP. Programs such as Parition Commander 8 and 9 can be used to
format the partition also.

=07Windows 98 second addition can only format FAT32 above 512 GB to
127.5 MB.

=07Windows ME can only format FAT32 above 512 GB to 2 TB.

=07Windows XP can only format FAT32 less than 32 GB.

Note:  After formatting, always run chkdsk under eCS if using the OS/2
FAT32 driver.  This is probaby true for any file system after formatting.

If you still cannot get your drive to work, you can try the next steps.

13.Download Chris Wohlgemuth's USB driver package
(cw-usbmsd-v1_2b.zip) and install his USB mass storage driver
(CWUSBMSD.ADD), replacing the IBM driver. Copy his CWUSBMSD.ADD driver
to the OS2\BOOT directory. Rem out IBM's USBMSD.ADD driver. Add a line
similar to the following to your config.sys file. Be sure and read his
documentation.

Example:

REM BASEDEV=3DUSBUHCD.SYS
BASEDEV=3DUSBEHCD.SYS /V
BASEDEV=3DUSBOHCD.SYS /V
BASEDEV=3DUSBOHCD.SYS /V
BASEDEV=3DUSBD.SYS
BASEDEV=3DUSBHID.SYS
REM BASEDEV=3DUSBMSD.ADD /REMOVABLES:3
BASEDEV=3DCWUSBMSD.ADD /FLOPPIES:0 /REMOVABLES:4 /FIXED_DISKS:2
/FORCE_TO_REMOVABLE

Adjust the REMOVABLES options to the max number of removables you my
have plugged in at one time. Be aware that LVM will still list drives
whether you have them plugged in or not. These drives will show up as
96 MB volumes.

14.Reboot and see if your device(s) are now recognized. If not try the
next step.

15.Download M. Kiewitz's driver package, MMPORTv1.zip, from Hobbes.
You will need to replace IBM's USBD.SYS driver with Martin's USBD.SYS
driver. Attempting to use this driver has risks. To be safe, rename
the IBM driver to something like USBD_BCKUP.SYS. That way if something
goes wrong, you can either boot to a command prompt or a maintenance
partition to copy the IBM driver back over Martin's driver. Martin's
driver can trap on boot up. What Martin's driver does different is
that it attempts to find USB media the Microsoft way instead of the
USB Standards way. When it works, it can be a life saver. If it
doesn't work with the latest IBM drivers, you might try downloading
some of the earlier versions of the USB drivers from the eComStation
ftp site. The closer the IBM drivers are to the date of his released
driver, the greater the chance of his driver working. Since he does
not have access to the latest code, he had to use the the last
available code from the DDK site. If you have a usbcalls.dll on your
eComStation system, replace it with Martin's fixed usbcalls.dll. The
driver has been patched to fix a nasty bug.

Hopefully one of the above techniques will solve your problem.

IMPORTANT:  If plugging the drive into different computers, make sure
ALL the USB drivers are the same on these systems. File corruption can
result when using different drivers and versions.


David=20





=20
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
=20




---