OverFlow's instructions for removing the ALI IDE driver from the DriverPacks MassStorage inf file were good, and as a result my new UBCD4Win now properly recognizes my hard drive and all the partitions on it.  Thanks to all involved for your help.

Thanks for the explanations.  No thank you, I don't want to go the complicated route, I'll give your instructions a try and report back.

Well, I do not fully understand everything that goes on.  So I need to unpack the DriverPack, do the edit you mentioned, repack with 7zip, and config; I cannot go into my UBCD4Win project directory, where the drivers seem to already be sitting in the folder plugins\DriverPacks.net\MassStorage\Winxp  ?  (BTW, \Winxp does not contain the aliide.sy_ file).  If not, then I'll give it a try.  What is the MassStorage.sif file sitting in plugin\DriverPacks.net\ ?  Oddly, it contains an entry for aliide.sys.

Thanks for your great help!

I suppose you just want the PCI Devices that HWID found, right, but if you want it all, let me know:

===========
PCI Devices
===========
PCI\VEN_1002&DEV_4C4D&SUBSYS_10041025&REV_64\4&15E6A2C8&0&0008: ATI RAGE Mobility  (ACER)
PCI\VEN_104C&DEV_8400&SUBSYS_3B001186&REV_00\4&2A24BFBA&0&0098: D-Link AirPlus DWL-650+ Wireless Cardbus Adapter
PCI\VEN_10B9&DEV_1533&SUBSYS_00000000&REV_0A\3&61AAA01&0&38 : ALi PCI to ISA bridge
PCI\VEN_10B9&DEV_1621&SUBSYS_00000000&REV_05\3&61AAA01&0&00 : ALi CPU to PCI bridge
PCI\VEN_10B9&DEV_5229&SUBSYS_00000000&REV_20\3&61AAA01&0&78 : ALi M5229 PCI Bus Master IDE Controller
PCI\VEN_10B9&DEV_5237&SUBSYS_00000000&REV_03\3&61AAA01&0&A0 : ALi PCI to USB Open Host Controller
PCI\VEN_10B9&DEV_5247&SUBSYS_00000000&REV_01\3&61AAA01&0&08 : ALi PCI to AGP Controller
PCI\VEN_10B9&DEV_7101&SUBSYS_10041025&REV_09\3&61AAA01&0&88 : ALi 7101 Power Management Controller
PCI\VEN_11C1&DEV_0449&SUBSYS_04401468&REV_01\3&61AAA01&0&30 : Lucent Win Modem
PCI\VEN_1217&DEV_6872&SUBSYS_10041025&REV_05\3&61AAA01&0&98 : O2Micro OZ6812 CardBus Controller
PCI\VEN_125D&DEV_1969&SUBSYS_10041025&REV_02\3&61AAA01&0&40 : ESS 1969 PCI AudioDrive (WDM)
11 matching device(s) found.

I believe you are right, OverFlow.  I disabled the DriverPacks MassStorage drivers in UBCD4Win, created a new ISO, booted it, and it now finds and understands the FAT32 D: partition on my laptop.  So what does that mean, if anything?  Perhaps the Win XP running on UBCD4Win is choosing the wrong driver?  Or the right driver, but the wrong . . something else?

I appreciate your input, Jaak.  This is all happening on an old IBM Thinkpad Celeron laptop.  There is only one hard drive.  It has two partitions on it, and both partitions show up in UBCD4Win; one says volume C: Type NTFS, the other says volume D: Type Unknown.

OverFlow, I found your tutorial, thanks.  I'll try to make a UBCD4Win without DriverPacks MassStorage driver and see how it works.  Ya know, there is a lot to this UBCD4Win, I'll try not to mess it all up.

I'm fine with leaving this open here on Driverpacks, just didnt' want to get slammed for posting two different places.  If I find a cause and resolution to this issue, I'll post a summary here.  This issue is being discussed in the UBCD4Win forum at

http://ubcd4win.com/forum/index.php?showtopic=11501

Gee, and I almost posted to UBCD4Win, but it sounded like a driver issue. 

If the Admin doesn't mind: if this is not a driver issue, I'd rather discuss it over in the UBCD4Win forum at ubcd4win.com.  This thread could be closed out here.  Thanks.

I built and ran the latest UBCD4Win, version 3.20, yesterday, and was astounded that though it recognized and accessed my C: partition fine (standard NTFS), it couldn't recognize my D: partition (standard FAT32).  It said the D: volume was of unknown type.  These are two partitions on one 30 GB IDE drive.  This UBCD4Win was built with XP with SP2.

Now, this was partitioned with a standard FDISK, DOS/Win98 version I believe, to create D: in an extended partition with a logical DOS drive.  These style of partitions have been used forever and are recognized by DOS, Win95, Win98, WinME, and WinXP with and without service packs.  This is on a fairly old IBM Thinkpad laptop with a Celeron CPU.   My older UBCD4Win has always recognized these partitons fine; it is UBCD4WinV25 with UBCD4WinDriversV12, and was built with XP with SP1a.

Plugin information from .inf files on the new UBCD4Win Version 3.20 is:

BASE.inf:
; PE Builder v3 plug-in INF file
; Dynamically generated by DriverPacks BASE Version 7.05.2
; DriverPacks.net and UBCD4WIN.COM PROUDLY PRESENT...
; Driver support for XP & 2003 32 bit OS's
; BASE.inf
;
; This Plugin's DriverPack info: BASE, 7.05.2

MassStorage.inf:
; PE Builder v3 plug-in INF file
; Dynamically generated by DriverPacks BASE Version 8.05
; DriverPacks.net and UBCD4WIN.COM PROUDLY PRESENT...
; Driver support for XP & 2003 32 bit OS's
; MassStorage.inf
;
; This Plugin's DriverPack info: MassStorage, 8.05

Has anyone else seen anything like this?