Just to keep this forum up to date....
I think I have gotten past the base disk driver thing. Appears not be a driver issue at all but a geometry based thing. I used a Windows XP Install CD to clean all partitions out and start over.
One very odd thing though. Even on a completely clean disk with no partitions, the ECS installer STILL only sees 4GB, initially. I created a Boot Manager and a 3GB ECS install partition (volume) and added it to the boot menu. I cancelled the install at that time and rebooted to Windows CD. Created a 25 GB partition for WinXP and installed that. Went back to ECS install and BOOM! installer now saw all 100GB of the disk??
It had the boot manger, ECS 3GB partition, and the 25 GB WinXP partion as a compatability volume and about 70GB of free space. Added WinXP to the boot menu and installed ECS.
Tried to reboot to WinXP off the ECS boot menu and WinXP boot hung for some reason. Will have to investigate that later. Tried to use LVM in ECS to create some Linux install partitions as well. Linux did alright until trying to install Grub or Lilo to it's root (boot) partition. It failed.
So even though ECS can now "see" all 100GB, I still have disk issues.
On the other hardware front....
Broadcom Gigabit Ethernet works just fine. I have full network and inet connectivity via DHCP.
Video is very nice.
Actually got the PCMCIA subsystem working with Daniela's latest driver for that (even though I have nothing to use it with).
Sound is still a no go but the Uniaud folks are looking at a pci.exe dump I game them. Results of that are that my card requires acpi/2 capability, being an ICH5,6,7 family chipset. The Uniaud driver does not have that capability yet, but they are working on it.
My main question(s), at this point is/are
1) Why does miniLVM on ECS install boot still only see 4GB even on a clean, non-partitioned disk?
2) Why does adding WinXP to the ECS Boot Manager menu cause WinXP reboot to hang?
3) Why can't I get Grub or Lilo to install on my LVM created Linux volumes (all created as compatability volumes)?
My hunch is that the MBR is still screwed up from using Linux Kernel 2.6 installer to create the initial partitions. DFSee might be of use here to completely reinitialize the disk, including zeroing out the MBR entirely.
Cross platform zealot