Re: USB "WD Passport" HDD w/Warp4 FP17

Hi Al

Al Savage wrote:
On Thu, 29 Mar 2007 19:07:02 UTC, Al Savage <asavage@xxxxxxxxx> wrote:

I have W4 FP17 and the 10.162 (I think) USB drivers.

With the advice of several, and the help of a friend to loan me the 10.162 USB driver pack


I think you also need os2dasd.dmd buildlevel 14.104


(if I can determine that the 10.162 stack will do what I want, I'll pony
up the bux for the eCS path), I am now at this point:

Non-LVM, of course.



Any reason for that?

LVM is pretty easy to get on with - once you get used to it - and also allows rejigging of drive letters ie changing drive letter from d: to t: if required.


OS2DASD.DMD = 10.83 (latest for Warp 4.00)


The 14.104 os2dasd.dmd should be an improvement over the above.


USB basic stack = 10.162
USB MSD driver = 10.162

HCIMONIT.exe :
You have 2 PCI USB UHCI host controller(s)

CONFIG.SYS:
DEVICE=d:\Tame\usbresmg.sys
BASEDEV=USBUHCD.SYS /V
BASEDEV=USBUHCD.SYS /V
BASEDEV=USBD.SYS /REQ:USBUHCD$,USBOHCD$,USBEHCD$ /V


Current advice is that the above line only needs to be like this:-

BASEDEV=USBD.SYS



BASEDEV=USBHID.SYS /V
BASEDEV=USBMSD.ADD /FLOPPIES:0 /REMOVABLES:3 /CHS /V

o /CHS is required for proper detection of the USB 160GiB HDD; without /CHS the wrong size is reported.


Be interesting to discover if the later os2dasd.dmd removes the /CHS requirement.


o With /REMOVABLES:3 , I get three new drive letters: I:, J:, K:



I: is the formatted partition on the USB drive.

J: and K: are "placeholders" for whatever other USB drive you may attach.


DFSee 8.13 (best viewed with monospace typeface):
ÚÄÄÄÂÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄ¿
ÃÄÄÄÅÄÄ<disk 3>ÄÄÄ</dev/hdc>ÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ<Disk3 - 1>ÄÄÄÄÄÄÄÄ´
³08 ³ ³FreeSpace Primary³ ³-- -- --³-- -- --³- - - - - -³ ³ 7.8³
³08 ³ ³Log 07 Inst-FSys³ 5³HPFS ³IBM 4.50³DRIVE_1 ³ ³ 65522.8³
³09 ³ ³Log 07 Inst-FSys³ 6³- ³unknown ³ ³ ³ 65530.7³
³10 ³ ³Log 07 Inst-FSys³ 7³- ³unknown ³ ³ ³ 21563.7³
ÀÄÄÄÁÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÙ

Disk 3 is the USB 160GiB HDD

As you can see, I have managed to use FDISK to delete the as-shipped FAT32 partition, and
create three partitions. I have formatted the first partition on the USB drive for HPFS, and it is

usable as drive letter I:

However, although J: & K: are "in the system", the other two partitions are not assigned those (or any) drive letters.



Those partitions are *Not* J: and K:



FDISK reports FIVE disks; the first two are internal, the third is the USB HDD, and the 4th/5th are bogus. The 4th/5th FDISK-reported disks occured when I changed /REMOVABLES:1 to /REMOVABLES:3



Not bogus - just placeholders.


The Lon Hooker article on removable USB media at
http://www.os2voice.org/VNL/past_issues/VNL0606H/feature_2.html
says that the OS2DASD.DMD /MP parameter is for partitionable, removable media, not fixed media:
----------------------------------------------------
/MP

Used to support allocating a predetermined number of drive letters for a partitioned removable media device. Note that this option only applies to partitioned removable devices, and is ignored for any other device type.

This switch applies only to Iomega ZIP drives allowing them to use partitioned removable media. It has nothing to do with USB devices which use partitioned fixed media and are controlled by the usbmsd.add /REMOVABLES:[n] statement.
----------------------------------------------------

So, I have not tried using the OS2DASD.DMD parameter /MP .

Q1: Any suggestions on how to tie drive letters (apparently reserved by the /REMOVABLES:3 parameter)


All /REMOVABLES:3 does is set the expected maximum number of Removable drives - which should always be 1 more than you expect.


to the last two partitions of the USB HDD?

Q2: Does DFSee perform HPFS formatting?



If you read through the above FAQ and the USB MSD docs you will find that /REMOVABLES:1 is all you actually need to be able to hookup a USB drive with several partitions on. Think of /REMOVABLES as being a count of the number of physical containers rather than the number of partitions.

Your 4th/5th partitions are placeholders for the 2 /REMOVABLES specified in config.sys which do not currently have any media attached.

Not sure why the other 2 partitions are not assigned drive letters... It could be os2dasd.dmd related or maybe fdisk does not work with multiple partitions on removable media.


You could try resetting to /REMOVABLES:1, reboot, then attach the USB drive and see if using fdisk to delete and then recreate the 2 unformatted partitions works to get them drive letters.

I think I would be tempted to install the current os2dasd.dmd before trying the above.

Hope the above helps

Pete
.

Relevant Pages

  • XP and Hard disks
    ... I have two HDs each with several partitions and a USB HD. ... the partitions took the drive letters D-H. ... rebooting, I was unavailable and everything was up one. ...
    (microsoft.public.windowsxp.basics)
  • Re: USB "WD Passport" HDD w/Warp4 FP17
    ... and the help of a friend to loan me the 10.162 USB ... I have formatted the first partition on the USB drive for HPFS, ... those drive letters. ... says that the OS2DASD.DMD /MP parameter is for partitionable, removable media, ...
    (comp.os.os2.setup.storage)
  • RE: XP and Hard disks
    ... the partitions took the drive letters D-H. ... The USB Hard ... > rebooting, I was unavailable and everything was up one. ...
    (microsoft.public.windowsxp.basics)
  • Severe problems with drive letter assignments under windows xp
    ... When he bought the computer I carved out two partitions on the drive ... WINDOWS will NOT boot because it is looking for programs ... Diskpart in the recovery console CAN NOT CHANGE drive letters. ... Is there anything I can do from the recover console to do the job - the ...
    (microsoft.public.windowsxp.hardware)
  • Re: recover partition(s) deleted during window xp pro resintall
    ... any tool that works with partitions. ... The poster mentions both a USB drive ... >> Windows help - www.rickrogers.org ...
    (microsoft.public.windowsxp.setup_deployment)