Mark Abramowitz wrote:

>In , on 05/24/04 
>   at 03:33 AM, Mike O'Connor  said:
>
>>Just wondering, how did you manage to get a copy of usbmon.exe in 
>>C:\os2\boot?
>>I only get a copy in X:\os2 here.
>>    
>>
>Doing some reading of some posts on the hardware support newsgroup for
>eCS, I learned that the usbmon in C:\os2\boot is a different one, but with
>the same name.
>
>The one in C:\os2\boot is placed there (or should be, I believe) when usb
>support is added.  From the command line in C:\os2\boot, if you want it to
>automatically start up at boot, run usbicon.cmd.
>
Hi Mark,

No matter which selections I make at installation time with either MCPx 
or eCS 1.x, and I have done *many* additional parallel  installations, I 
have never had an additional one placed in x:\os2\boot. I could only 
think that possibly [I never attempted any pre-release versions of eCS] 
this could have happened when installing a GA version *over* an existing 
previous version which used different paths for the executable, and thus 
didn't get overwritten?

I don't have any USB peripherals, but always install the USB support for 
the ports detected on installation, and recently checked out whether the 
system would recognise a SONY digital Camera with 128MB SD Memory chip 
belonging to a friend, after enabling the USBMSD driver and the xHCI 
drivers.  USBMON did indeed detect the device status, when it was 
connected and detached,  although I wasn't actually able to access it, 
in the short time available,  I presumed I needed to do some tweaking.

When my friend left with his camera I omitted to [again] disable the 
drivers in config.sys and it wasn't until the next time I actually 
looked in the Drives folder, quite a few days later, that I found I 
still had an additional drive "P:" [3D-floppy icon] there.  In addition 
running the LVMGUI.CMD rsulted in a "phantom" [96MB]
"unpartioned" 
[Drive 2] suffering from "incorrect partition information", to 
paraphrase the error message.  I was able to delete the Object using the 
O.D. Object Inspector, but reopening the Drives folder, resulted in its 
reappearance.  REMming the config.sys entries resulted in its permanent 
disappearance.

Shortly before discovering the oversight, I had two consecutive 
occurrences of shutdown failing to complete [XWP extended shutdown].  
This had never been evident in the previous 12 months, and resulted in 
two bad chkdsks on boot [> 50MB of OS/2-IBMLAN etc., scrambled :-( ]with 
that H: partition,  following consecutive 24-hour sessions.  No problems 
whatsoever during
those two sessions, only after shutdown commenced - screen didn't clear 
- needed physical power-off.

Following discovery of the overlooked active USB drivers, there have 
since been no further occurrences of shutdown problems.

Don't know whether anyone else has experienced this situation, but the 
possibility is something to be aware of!

-- 
Regards,
Mike

Failed the exam for
--------------------
MCSE - Minesweeper Consultant and Solitaire Expert
--------------------
[ISP blocks *.exe, *.cmd, *.bat, *.reg attachments]
[Please use zipped versions of above]




------------------------ Yahoo! Groups Sponsor ---------------------~-->
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/9rHolB/TM
---------------------------------------------------------------------~->

 
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/
 


---