Re: eComStation-USB-stack-20080507

Peter Brown wrote:

> Hi
> 
> I followed the instructions in the readme of this package to try to add
> this Bug Report to the bug tracker at
> http://trac.ecomstation.ru/USBstack/report
> 
> There the directions fell down: There is no "New Ticket" to click
to
> submit a report.
> 
> Hopefully someone will get that fixed and add this report:-
> 
> 
> Slows system down a lot and Trashed my USB drive
> 
> System: eCS1.2R, nForce430/MCP61 chipset
> 
> I copied the installed IBM 10.162 builds of usbmsd.add, usbd.sys and
> usbd.sym to another disk and deleted the existing copies in \os2\boot.
> 
> Unzipped the files from eComStation-USB-stack-20080507.zip to \os2\boot
> and rebooted.
> 
> Booting seemed slower, the Desktop was much slower in starting and is
> much slower in use, the USB trackball jumps around and is not very usable.
> 
> 
> I tried this package to see if it overcame a problem: I can only attach
> 1 USB drive at a time. If I attach USBDrive1 and then try to attach
> USBDrive2 the system totally ignores USBDrive2. It is necessary to Eject
> USBDrive1 and then re-attach USBDrive2 to successfully access USBDrive2.
> 
> I'm not sure if the problem is due to usbehcd.sys, usbmsd.add, usbd.sys,
> SMP14.104a kernel or ACPI driver (v2.22 to v3.09 inclusive) or a
> combination thereof.
> 
> 
> No, this stack does not help: in fact it does not seem to be able to
> access my 40Gb USB drive that is formatted JFS - and may have mucked it
> up badly!
> 
> Trying to access the drive from the WPS I am informed that "no
objects
> exist..." followed by "the disk is not formatted..."
> 
> 
> Here is what happens when I try a command line DIR:-
> 
> [H:\]dir o:
> 
> Volume in drive O has no label.
> The Volume Serial Number is 534E:4A52.
> Directory of O:\
> 
> SYS0026: The specified disk or diskette cannot be accessed.
> 
> [H:\]
> 
> 
> 
> Looks like this USB Stack has made a mess of that drive...
> 
> Back to the IBM drivers.
> 
> Following a reboot I find that the USB drive is still not accessible.
> Guess I'll have to try looking at the drive with DFSee and seeing if I
> can rescue the contents.
> 
> Could it be that the CHS values have got munged due to the different
> usbmsd.add driver?

Just on the off chance, did you set the USBMSD removables count to > 1?  I
get annoyed at all the spurious entries in LVM of DFSEE and have been known
to set that back - which causes it to only see 1 or so at a time.

I haven't tried the USB disc stuff yet but my results may be a bit weird as
I use a USB -> IDE adapter with standard IDE drives.

-- 

Hi

I followed the instructions in the readme of this package to try to add 
this Bug Report to the bug tracker at 
http://trac.ecomstation.ru/USBstack/report

There the directions fell down: There is no "New Ticket" to click to 
submit a report.

Hopefully someone will get that fixed and add this report:-


Slows system down a lot and Trashed my USB drive

System: eCS1.2R, nForce430/MCP61 chipset

I copied the installed IBM 10.162 builds of usbmsd.add, usbd.sys and 
usbd.sym to another disk and deleted the existing copies in \os2\boot.

Unzipped the files from eComStation-USB-stack-20080507.zip to \os2\boot 
and rebooted.

Booting seemed slower, the Desktop was much slower in starting and is 
much slower in use, the USB trackball jumps around and is not very usable.


I tried this package to see if it overcame a problem: I can only attach 
1 USB drive at a time. If I attach USBDrive1 and then try to attach 
USBDrive2 the system totally ignores USBDrive2. It is necessary to Eject 
USBDrive1 and then re-attach USBDrive2 to successfully access USBDrive2.

I'm not sure if the problem is due to usbehcd.sys, usbmsd.add, usbd.sys, 
SMP14.104a kernel or ACPI driver (v2.22 to v3.09 inclusive) or a 
combination thereof.


No, this stack does not help: in fact it does not seem to be able to 
access my 40Gb USB drive that is formatted JFS - and may have mucked it 
up badly!

Trying to access the drive from the WPS I am informed that "no objects 
exist..." followed by "the disk is not formatted..."


Here is what happens when I try a command line DIR:-

[H:\]dir o:

Volume in drive O has no label.
The Volume Serial Number is 534E:4A52.
Directory of O:\

SYS0026: The specified disk or diskette cannot be accessed.

[H:\]



Looks like this USB Stack has made a mess of that drive...

Back to the IBM drivers.

Following a reboot I find that the USB drive is still not accessible. 
Guess I'll have to try looking at the drive with DFSee and seeing if I 
can rescue the contents.

Could it be that the CHS values have got munged due to the different 
usbmsd.add driver?


Regards

Hi ill

Will Honea wrote:
> Peter Brown wrote:
> 
>> Hi
>>
>> I followed the instructions in the readme of this package to try to
add
>> this Bug Report to the bug tracker at
>> http://trac.ecomstation.ru/USBstack/report
>>
>> There the directions fell down: There is no "New Ticket" to
click to
>> submit a report.
>>
>> Hopefully someone will get that fixed and add this report:-
>>


----- snip -----
> 
> Just on the off chance, did you set the USBMSD removables count to > 1? 
I
> get annoyed at all the spurious entries in LVM of DFSEE and have been
known
> to set that back - which causes it to only see 1 or so at a time.
> 

I use USBcfg to set various USB values and have /REMOVABLES:5


Talking of LVM: that shows some detail about the last USB drive attached 
- even though the USB drive may have been ejected hours ago. The detail 
is fairly skimpy but displays the size of the drive and declares it is 
[Free Space 1] which is not correct.

Looks like something does not work right when the disk s Ejected...


> I haven't tried the USB disc stuff yet but my results may be a bit weird
as
> I use a USB -> IDE adapter with standard IDE drives.
> 


Just what do you think a USB drive is comprised of?  :-)

A box, a disk plus a bridge between disk type and USB connector ie a 
SATA drive needs a SATA to USB bridge, an IDE drive needs an IDE to USB 
bridge. These bidges are supplied with the external caddy (box) to put 
your old IDE/SATA drive in.

Obviously the above does not apply to flash drives/card readers.


On the subject of will DFSee rescue my trashed data: Yes, that worked fine.


Regards

Peter Brown wrote:
> Hi
> 
> I followed the instructions in the readme of this package to try to add 
> this Bug Report to the bug tracker at 
> http://trac.ecomstation.ru/USBstack/report
> 
> There the directions fell down: There is no "New Ticket" to click
to 
> submit a report.
> 
> Hopefully someone will get that fixed and add this report:-
> 
> 
> Slows system down a lot and Trashed my USB drive
> 
> System: eCS1.2R, nForce430/MCP61 chipset
> 
> I copied the installed IBM 10.162 builds of usbmsd.add, usbd.sys and 
> usbd.sym to another disk and deleted the existing copies in \os2\boot.
> 
> Unzipped the files from eComStation-USB-stack-20080507.zip to \os2\boot 
> and rebooted.
> 
> Booting seemed slower, the Desktop was much slower in starting and is 
> much slower in use, the USB trackball jumps around and is not very usable.
> 
> 
> I tried this package to see if it overcame a problem: I can only attach 
> 1 USB drive at a time. If I attach USBDrive1 and then try to attach 
> USBDrive2 the system totally ignores USBDrive2. It is necessary to Eject 
> USBDrive1 and then re-attach USBDrive2 to successfully access USBDrive2.
> 
> I'm not sure if the problem is due to usbehcd.sys, usbmsd.add, usbd.sys, 
> SMP14.104a kernel or ACPI driver (v2.22 to v3.09 inclusive) or a 
> combination thereof.
> 
> 
> No, this stack does not help: in fact it does not seem to be able to 
> access my 40Gb USB drive that is formatted JFS - and may have mucked it 
> up badly!
> 
> Trying to access the drive from the WPS I am informed that "no objects

> exist..." followed by "the disk is not formatted..."
> 
> 
> Here is what happens when I try a command line DIR:-
> 
> [H:\]dir o:
> 
> Volume in drive O has no label.
> The Volume Serial Number is 534E:4A52.
> Directory of O:\
> 
> SYS0026: The specified disk or diskette cannot be accessed.
> 
> [H:\]
> 
> 
> 
> Looks like this USB Stack has made a mess of that drive...
> 
> Back to the IBM drivers.
> 
> Following a reboot I find that the USB drive is still not accessible. 
> Guess I'll have to try looking at the drive with DFSee and seeing if I 
> can rescue the contents.
> 
> Could it be that the CHS values have got munged due to the different 
> usbmsd.add driver?
> 
> 
> Regards
> 
> Pete
For me this usb stack made my big (250 GB) usb hard disk to report
itself as 32 MB drive and could not be accessed. I have reported the
problem to the site given in readme.