UBCD4Win Forums > UBCD4 v3.22 SATA woes on MCP55 m/board

Krisbee

Nov 28 2008, 12:37 PM

My first 5 efforts to create a UBCD that will work on my PC have all failed. The problem is that in each case if I leave my SATA drive connected, after choosing to boot UBCD, the PC just hangs with a blank screen and the SATA HDD activity LED stays on until a power down.

If I disconnect the SATA drive the default UBCD v3.22 build, with mass storage drivers enabled, boots and works with all my other drives detected.

My hardware is:

Abit Kn9s m/board, which is has a MCP55 chipset (Nforce 550)
Dual Athlon x2
Floppy Dirve
Two optical drives
One PATA drive connected to a sil680 medley RAID card – used just as an additional IDE channel
One SATA drive connected to m/board's Nforce MCP55 four channel serial ATA controller

In the Kn9s BiOS you can either set SATA RAID disabled or enabled. Mine is disabled.

My five attmepts were:

1. Using UBCD4win 3.22 built ISO with default plugin options.
2. As 1, but using a later version of driver pack from here http://driverpacks.sytes.net/driverpacks/Nightlies/
3. As 1, but using an earlier version of the driver pack form UBCW4Win3.13
4. As 1, but with a modified version of original driver pack, so only [N-TM] Nforce section is used.
5. As 1, but with mass storage devices disabled, and used my own sil680 plugin.

Attempt 3 was based on a thread which said reverting to the driver pack from UBCD4WIN 3.13 got round a SATA hard drive problem on a MCP55EX m/board.

Attempt 4 was based on info in this thread, http://www.ubcd4win.com/forum/index.php?s=&...ost&p=61604, the "DriverPack_MassStorage_wnt5_x86-32.ini" is edited to comment out all Nforce sections except for [N-TM].

Attempt 5, I thought perhaps something else was the problem, and I hoped I might at least get to a F6 screen, but I didn't.

To be honest, I don't know that much about Windows and even less about UBCD4WIN and driver configuration. So any help will be much appreciated.

Looking at my current Windows XPSP2 install, I see that I never needed to install nvraid, or any other nvidia SATA driver. I believe this means WinXP is using “IDE emulation”. Perhaps this is the problem.

I've included my HWIDS below for those who understand it:

CODE

            ===========

            PCI Devices

            ===========

            PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&2411E6FE&0&C0: PCI standard host CPU bridge

            PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&2411E6FE&0&C1: PCI standard host CPU bridge

            PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&2411E6FE&0&C2: PCI standard host CPU bridge

            PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&2411E6FE&0&C3: PCI standard host CPU bridge

            PCI\VEN_1095&DEV_0680&SUBSYS_36801095&REV_02\4&2BE4B97F&0&4830: Silicon Image SiI 0680 ATA/133 Controller

            PCI\VEN_10DE&DEV_0140&SUBSYS_31251458&REV_A2\4&5E1D6BE&0&0078: NVIDIA GeForce 6600 GT

            PCI\VEN_10DE&DEV_0363&SUBSYS_00000000&REV_A2\3&2411E6FE&0&08: PCI standard ISA bridge

            PCI\VEN_10DE&DEV_0368&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&09: NVIDIA nForce PCI System Management

            PCI\VEN_10DE&DEV_0369&SUBSYS_1C25147B&REV_A1\3&2411E6FE&0&00: PCI standard RAM Controller

            PCI\VEN_10DE&DEV_036C&SUBSYS_1C25147B&REV_A1\3&2411E6FE&0&10: Standard OpenHCD USB Host Controller

            PCI\VEN_10DE&DEV_036D&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&11: Standard Enhanced PCI to USB Host Controller

            PCI\VEN_10DE&DEV_036E&SUBSYS_1C25147B&REV_A1\3&2411E6FE&0&20: Standard Dual Channel PCI IDE Controller

            PCI\VEN_10DE&DEV_0370&SUBSYS_00000000&REV_A2\3&2411E6FE&0&30: PCI standard PCI-to-PCI bridge

            PCI\VEN_10DE&DEV_0373&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&40: NVIDIA Network Bus Enumerator

            PCI\VEN_10DE&DEV_0374&SUBSYS_00000000&REV_A2\3&2411E6FE&0&60: PCI standard PCI-to-PCI bridge

            PCI\VEN_10DE&DEV_0375&SUBSYS_00000000&REV_A2\3&2411E6FE&0&70: PCI standard PCI-to-PCI bridge

            PCI\VEN_10DE&DEV_0377&SUBSYS_00000000&REV_A2\3&2411E6FE&0&78: PCI standard PCI-to-PCI bridge

            PCI\VEN_10DE&DEV_0378&SUBSYS_00000000&REV_A2\3&2411E6FE&0&68: PCI standard PCI-to-PCI bridge

            PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&28: Standard Dual Channel PCI IDE Controller

            PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&29: Standard Dual Channel PCI IDE Controller

            PCI\VEN_1412&DEV_1724&SUBSYS_17241412&REV_01\4&2BE4B97F&0&5030: Envy24 Family Audio Controller WDM

            21 matching device(s) found.

            ===========

            USB Devices

            ===========

            USB\ROOT_HUB\4&1318DB1B&0 : USB Root Hub

            USB\ROOT_HUB20\4&3A8EBD0&0 : USB Root Hub

            USB\VID_04B3&PID_310C\5&2C5685A6&0&8 : USB Human Interface Device

            USB\VID_4348&PID_5584\5&2C5685A6&0&5 : USB Printing Support

            4 matching device(s) found.

            =============

            Input Devices

            =============

            HID\VID_04B3&PID_310C\6&13046CBE&0&0000 : HID-compliant mouse

            1 matching device(s) found.

            ============

            ACPI Devices

            ============

            ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_107\_0 : AMD Athlon" 64 X2 Dual Core Processor 4400+

            ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_107\_1 : AMD Athlon" 64 X2 Dual Core Processor 4400+

            ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button

            ACPI\PNP0000\3&2411E6FE&0 : Programmable interrupt controller

            ACPI\PNP0100\3&2411E6FE&0 : System timer

            ACPI\PNP0200\3&2411E6FE&0 : Direct memory access controller

            ACPI\PNP0303\3&2411E6FE&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard

            ACPI\PNP0700\3&2411E6FE&0 : Standard floppy disk controller

            ACPI\PNP0800\3&2411E6FE&0 : System speaker

            ACPI\PNP0A08\1 : PCI bus

            ACPI\PNP0B00\3&2411E6FE&0 : System CMOS/real time clock

            ACPI\PNP0C01\2&DABA3FF&0 : System board

            ACPI\PNP0C02\1 : Motherboard resources

            ACPI\PNP0C02\4 : Motherboard resources

            ACPI\PNP0C02\5 : Motherboard resources

            ACPI\PNP0C04\3&2411E6FE&0 : Numeric data processor

            ACPI\PNP0C0B\2&DABA3FF&0 : ACPI Fan

            ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button

            ACPI\THERMALZONE\THRM : ACPI Thermal Zone

            ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System

            ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC

            21 matching device(s) found.

            ============

            HDA Audio

            ============

            No matching devices found.

            ============

            RAID Devices

            ============

            PCI\VEN_1095&DEV_0680&SUBSYS_36801095&REV_02\4&2BE4B97F&0&4830

            Name: Silicon Image SiI 0680 ATA/133 Controller

            Hardware ID's:

            PCI\VEN_1095&DEV_0680&SUBSYS_36801095&REV_02

            PCI\VEN_1095&DEV_0680&SUBSYS_36801095

            PCI\VEN_1095&DEV_0680&CC_010400

            PCI\VEN_1095&DEV_0680&CC_0104

            Compatible ID's:

            PCI\VEN_1095&DEV_0680&REV_02

            PCI\VEN_1095&DEV_0680

            PCI\VEN_1095&CC_010400

            PCI\VEN_1095&CC_0104

            PCI\VEN_1095

            PCI\CC_010400

            PCI\CC_0104

            PCI\VEN_10DE&DEV_036E&SUBSYS_1C25147B&REV_A1\3&2411E6FE&0&20

            Name: Standard Dual Channel PCI IDE Controller

            Hardware ID's:

            PCI\VEN_10DE&DEV_036E&SUBSYS_1C25147B&REV_A1

            PCI\VEN_10DE&DEV_036E&SUBSYS_1C25147B

            PCI\VEN_10DE&DEV_036E&CC_01018A

            PCI\VEN_10DE&DEV_036E&CC_0101

            Compatible ID's:

            PCI\VEN_10DE&DEV_036E&REV_A1

            PCI\VEN_10DE&DEV_036E

            PCI\VEN_10DE&CC_01018A

            PCI\VEN_10DE&CC_0101

            PCI\VEN_10DE

            PCI\CC_01018A

            PCI\CC_0101

            PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&28

            Name: Standard Dual Channel PCI IDE Controller

            Hardware ID's:

            PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2

            PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B

            PCI\VEN_10DE&DEV_037F&CC_010185

            PCI\VEN_10DE&DEV_037F&CC_0101

            Compatible ID's:

            PCI\VEN_10DE&DEV_037F&REV_A2

            PCI\VEN_10DE&DEV_037F

            PCI\VEN_10DE&CC_010185

            PCI\VEN_10DE&CC_0101

            PCI\VEN_10DE

            PCI\CC_010185

            PCI\CC_0101

            PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&29

            Name: Standard Dual Channel PCI IDE Controller

            Hardware ID's:

            PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2

            PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B

            PCI\VEN_10DE&DEV_037F&CC_010185

            PCI\VEN_10DE&DEV_037F&CC_0101

            Compatible ID's:

            PCI\VEN_10DE&DEV_037F&REV_A2

            PCI\VEN_10DE&DEV_037F

            PCI\VEN_10DE&CC_010185

            PCI\VEN_10DE&CC_0101

            PCI\VEN_10DE

            PCI\CC_010185

            PCI\CC_0101

            4 matching device(s) found.

rdsok

Nov 28 2008, 02:03 PM

As a test... try disabling the driverpacks and see if it can boot and recognize your hard drive as well.

If it can... report your results to the Driverpacks.net forum so it can be addressed fully within the driverpacks themselves.

If it still doesn't recognize your hard drive after that... your BIOS is probably not set to IDE emulation mode. Reporting this is also important but the following should be a work-around until it can be addressed.

UBCD4Win, arguably,has the most complete set of drivers included with it to help in this type of situation. They were developed by the Driverpacks.net development team which represents the most complete set of drivers available anywhere... but still it is limited to what has already been or can be included so it can't have every single driver since new ones are developed all of the time.

So in situations like this the user needs to add the proper drivers for their system and disable the included drivers so no conflicts will mess you up and overwrite the drivers you supply. We also strongly recommend that the user report the issue in the Driverpacks.net forum so that other users will not have to worry about it later as they develop new driverpacks.

First you must locate the proper drivers for your system or its motherboard. Go to the manufacturers or motherboard's website and download the XP ( or Win2k3 drivers if that is the source files you are building from ) Floppy/F6 drivers. These are the same drivers that a user would use when installing XP ( or Win2k3 ) so should be easy to locate.

Next you need to create a folder for them. In the [UBCD4Win]\drivers folder create a folder named SCSIAdapter and in that folder another for your drivers called MyDriver... the path should be [UBCD4Win]\drivers\SCSIAdapter\MyDriver. Then extract the drivers you downloaded into that folder.

Next in the UBCD4WinBuilder go into the Plugins area and disable the "# DriverPacks.net - MassStorage" plugin so you don't get a conflict with these drivers. Rebuild the project and create a new disk and test.

Krisbee

Nov 28 2008, 04:45 PM

I've already tried your first suggestion (my attempt 5) and putting the proper nvidia drivers in c:\UBCD4Win\drivers\SCSIAdapter\MyDriver with the mass storage plugin disabled doesn't work either. The system behaviour is always the same, with a SATA drive connected my system just hangs.

As I already said. my BIOS does not have an option to set "IDE emulation", the on board RAID device is either enabled or disabled, that's it.

It's so long since I installed Windows on this PC I can't remember exactly what I did, but I'm sure there was no special action.

I'll leave a post at the Driverpacks.net forum, but if you have any other suggestions for a fix, please let me know.

cdob

Nov 28 2008, 05:07 PM

QUOTE (Krisbee @ Nov 28 2008, 05:45 PM)

I've already tried your first suggestion (my attempt 5) and putting the proper nvidia drivers in c:\UBCD4Win\drivers\SCSIAdapter\MyDriver with the mass storage plugin disabled doesn't work either.

Add nvgts addon too http://www.ubcd4win.com/forum/index.php?s=&...ost&p=61862

QUOTE

The system behaviour is always the same, with a SATA drive connected my system just hangs.

I understand: system hangs early. There is no F6 screen.
That early there there are no mass storage drivers loaded. Most likely there is another reason.
Maybe a strange partition or a half broken hardware.
Which partitions do you use?

Krisbee

Nov 28 2008, 06:07 PM

QUOTE (cdob @ Nov 28 2008, 10:07 PM)

QUOTE (Krisbee @ Nov 28 2008, 05:45 PM)

I've already tried your first suggestion (my attempt 5) and putting the proper nvidia drivers in c:\UBCD4Win\drivers\SCSIAdapter\MyDriver with the mass storage plugin disabled doesn't work either.

Add nvgts addon too http://www.ubcd4win.com/forum/index.php?s=&...ost&p=61862

QUOTE

The system behaviour is always the same, with a SATA drive connected my system just hangs.

I understand: system hangs early. There is no F6 screen.
That early there there are no mass storage drivers loaded. Most likely there is another reason.
Maybe a strange partition or a half broken hardware.
Which partitions do you use?

I haven't tried your first suggestion yet, but to answer your other question, the SATA drive is partitioned as below and all partitions are healthy. It's been my main drive for quite a while. It's got four different Linux distros on it, two 32bit and two 64bit.

fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2040 16386268+ 7 HPFS/NTFS
/dev/sda2 2041 2805 6144862+ b W95 FAT32
/dev/sda3 2806 13248 83883397+ 83 Linux
/dev/sda4 13249 30401 137781472+ 5 Extended
/dev/sda5 13249 13379 1052226 82 Linux swap / Solaris
/dev/sda6 13380 14730 10851876 83 Linux
/dev/sda7 14731 14763 265041 83 Linux
/dev/sda8 14764 19991 41993878+ 83 Linux
/dev/sda9 19992 20013 176683+ 83 Linux
/dev/sda10 20014 21395 11100883+ 83 Linux
/dev/sda11 21396 24789 27262273+ 83 Linux
/dev/sda12 24790 24805 128488+ 83 Linux
/dev/sda13 24806 30401 44949838+ 83 Linux

It's clear from my HWIDS that as I have no RAID installed/enabled and that my Windows install just has two the MS Standard Dual Channel PCI IDE Controller entries. So, to ask a dumb question, why do I need any nvidia drivers from the mass storage driver pack at all and/or how do you get UBCD4WIN to pick up just what would be the content of the SATA_IDE subfolder of the actual nForce chipset driver package?

You suggest there be another reason for my system hang, but why then does UBCD4WIn work as expected when the SATA drive is disconnected?

Re-building UBCD will have to wait until tomorrow.

rdsok

Nov 28 2008, 07:09 PM

Note.... to avoid confusion on what you are refering too..

UBCD - is a DOS based boot CD with utils to repair / recover computers

UBCD4Win - is a Windows based boot CD to also repair / recover computers and also can include UBCD with it...

So when talking about UBCD4Win please don't call it UBCD since that is another project

mbarnes

Nov 29 2008, 07:03 AM

Hi Krisbee

It has been reported that some UNIX / LINUX create a partition cylinder which prevents even a real XP CD booting and this also affects BartPE / UBCD4WIN CD's

can you try a real XP or 2003 CD and a LINUX CD to see if this is the problem, rather than a problem with disk controller drivers

Regards

Mike Barnes

Krisbee

Nov 30 2008, 05:44 AM

Thanks for everyone’s help, and sorry for getting sloppy with names: ubcd4win, ubcd , etc.

Just to reiterate, my Abit KN9s m/broad has a MCP55 serial ATA controller with RAID capability provided by a MediaShield ROM. In the BIOS the RAID ROM can either be disabled or enabled, and each SATA channel is either enabled or disabled on the RAID. There are no other options.

I have always used this PC with the SATA RAID ROM disabled and WindowsXP runs with “IDE emulation” with two standard MS dual channel IDE controllers.

1. MrBarnes - About the only thing I'm confident of is that Linux is not the problem. Firstly, my original install XP cd boots, as do various other Llinux Live CDs that I have used. Secondly, as a test, I even replaced the exisiting GRUB bootloader in sector zero with a standard DOS MBR. This made no difference, my UBCD4WIN cds still end in a system hang.

2. Cdob - Following your advice to insert a nvgts plugin as per http://www.ubcd4win.com/forum/index.php?s=&...ost&p=61862, as well as modifying the "DriverPack_MassStorage_wnt5_x86-32.ini", does seems to result in the correct Nvidia RAID drivers being added to the build as show by this log extract:

Copying file "C:\UBCD4Win\plugin\DriverPacks.net\MassStorage\wnt5\NVATABUS.SY_" to "C:\UBCD4Win\BartPE\I386\system32\drivers\NVATABUS.SY_"
Copying file "C:\UBCD4Win\plugin\DriverPacks.net\MassStorage\wnt5\NVRAID.SY_" to "C:\UBCD4Win\BartPE\I386\system32\drivers\NVRAID.SY_"

But the ubcd4win hangs on booting because my SATA controller has the RAID ROM disabled.

3. rdsok - What is odd to me is when I build without the "mass storage" driver pack and insert the Nvidia SATA_IDE drivers under C:\UBCD4Win\drivers\SCSIAdapter\SATA_IDE, a cross check of the build log against my HWIDS seems to show the correct pnp devices are present, apart from a small discrepancy in the RAID device HWIDS. Each MS Standard Dual Channel PCI IDE Controller has two channel but only three appear to detected by the save_HWID program. I don’t know if this is significant.

The relevant part of the buld log is:

Processing OEM file: C:\UBCD4Win\drivers\SCSIAdapter\sata_ide\txtsetup.oem
SCSI hardware ID: BUSDRV, component: NVIDIA nForce Storage Controller (required)
Adding PnP ID: PCI\VEN_10DE&DEV_0036
Adding PnP ID: PCI\VEN_10DE&DEV_003E
Adding PnP ID: PCI\VEN_10DE&DEV_0054
Adding PnP ID: PCI\VEN_10DE&DEV_0055
Adding PnP ID: PCI\VEN_10DE&DEV_0266
Adding PnP ID: PCI\VEN_10DE&DEV_0267
Adding PnP ID: PCI\VEN_10DE&DEV_037E
Adding PnP ID: PCI\VEN_10DE&DEV_037F
Adding PnP ID: PCI\VEN_10DE&DEV_036F
Adding PnP ID: PCI\VEN_10DE&DEV_03F6
Adding PnP ID: PCI\VEN_10DE&DEV_03F7
Adding PnP ID: PCI\VEN_10DE&DEV_03E7
Adding PnP ID: PCI\VEN_10DE&DEV_044D
Adding PnP ID: PCI\VEN_10DE&DEV_044E
Adding PnP ID: PCI\VEN_10DE&DEV_044F
Adding PnP ID: PCI\VEN_10DE&DEV_0554
Adding PnP ID: PCI\VEN_10DE&DEV_0555
Adding PnP ID: PCI\VEN_10DE&DEV_0556
Adding PnP ID: PCI\VEN_10DE&DEV_07F4
Adding PnP ID: PCI\VEN_10DE&DEV_07F5
Adding PnP ID: PCI\VEN_10DE&DEV_07F6
Adding PnP ID: PCI\VEN_10DE&DEV_07F7
Adding PnP ID: PCI\VEN_10DE&DEV_0768
Adding PnP ID: PCI\VEN_10DE&DEV_0AD5
Adding PnP ID: PCI\VEN_10DE&DEV_0AD4
Adding PnP ID: PCI\VEN_10DE&DEV_0AB9
Adding PnP ID: PCI\VEN_10DE&DEV_0AB8
Adding PnP ID: PCI\VEN_10DE&DEV_0BCC
Adding PnP ID: PCI\VEN_10DE&DEV_0BCD

Compare this with the relevant parts of the HWIDS list:

===========
PCI Devices
===========

PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&28: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&29: Standard Dual Channel PCI IDE Controller

============
RAID Devices
============
PCI\VEN_1095&DEV_0680&SUBSYS_36801095&REV_02\4&2BE4B97F&0&4830
Name: Silicon Image SiI 0680 ATA/133 Controller
Hardware ID's:
PCI\VEN_1095&DEV_0680&SUBSYS_36801095&REV_02
PCI\VEN_1095&DEV_0680&SUBSYS_36801095
PCI\VEN_1095&DEV_0680&CC_010400
PCI\VEN_1095&DEV_0680&CC_0104
Compatible ID's:
PCI\VEN_1095&DEV_0680&REV_02
PCI\VEN_1095&DEV_0680
PCI\VEN_1095&CC_010400
PCI\VEN_1095&CC_0104
PCI\VEN_1095
PCI\CC_010400
PCI\CC_0104
PCI\VEN_10DE&DEV_036E&SUBSYS_1C25147B&REV_A1\3&2411E6FE&0&20
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_10DE&DEV_036E&SUBSYS_1C25147B&REV_A1
PCI\VEN_10DE&DEV_036E&SUBSYS_1C25147B
PCI\VEN_10DE&DEV_036E&CC_01018A
PCI\VEN_10DE&DEV_036E&CC_0101
Compatible ID's:
PCI\VEN_10DE&DEV_036E&REV_A1
PCI\VEN_10DE&DEV_036E
PCI\VEN_10DE&CC_01018A
PCI\VEN_10DE&CC_0101
PCI\VEN_10DE
PCI\CC_01018A
PCI\CC_0101
PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&28
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2
PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B
PCI\VEN_10DE&DEV_037F&CC_010185
PCI\VEN_10DE&DEV_037F&CC_0101
Compatible ID's:
PCI\VEN_10DE&DEV_037F&REV_A2
PCI\VEN_10DE&DEV_037F
PCI\VEN_10DE&CC_010185
PCI\VEN_10DE&CC_0101
PCI\VEN_10DE
PCI\CC_010185
PCI\CC_0101
PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2\3&2411E6FE&0&29
Name: Standard Dual Channel PCI IDE Controller
Hardware ID's:
PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B&REV_A2
PCI\VEN_10DE&DEV_037F&SUBSYS_1C25147B
PCI\VEN_10DE&DEV_037F&CC_010185
PCI\VEN_10DE&DEV_037F&CC_0101
Compatible ID's:
PCI\VEN_10DE&DEV_037F&REV_A2
PCI\VEN_10DE&DEV_037F
PCI\VEN_10DE&CC_010185
PCI\VEN_10DE&CC_0101
PCI\VEN_10DE
PCI\CC_010185
PCI\CC_0101
4 matching device(s) found.

But the ubcd4win hangs on booting.

I seem to have no way to get UBCD4WIN to work while using my current system configuration. UBCD4win does not behave like a standard WINDOWS Install CD which is able to detect the SATA drive, requires no additional drivers and uses a pair of Standard Dual Channel PCI IDE Controllers.

cdob

Nov 30 2008, 07:34 AM

@Krisbee

Again, if you don't get a F6 message, there are no mass storage drivers involved so far.

A false mass storage driver would not mount hard disk. But would no prohibit booting.
Again, mass strorage drivers are loaded at F6 message.
If you don't get a F6 message, there are no mass storage drivers loaded so far.

There is another reason.

This maybe a strange partition.
Yes, some Linux partition prohibit booting.
Boot loader dosn't matter, it's the partition table. Maybe partition type or CHS translation.
PE use CHS translation that early to verify partitions.

Read the fdisk manpage about C/H/S fields and absolute number of sectors.

Or there maybe another BIOS setting: like USB legacy emulation.
At some strange BIOS, this prohibit booting too.

BartPE / UBCD4WIN use setupldr.bin at PE mode.
Setupldr.bin behave different at PE mode or at installation mode.

Clarify again: do you get a F6 message now?

Krisbee

Nov 30 2008, 10:27 AM

QUOTE (cdob @ Nov 30 2008, 12:34 PM)

@Krisbee

Again, if you don't get a F6 message, there are no mass storage drivers involved so far.

A false mass storage driver would not mount hard disk. But would no prohibit booting.
Again, mass strorage drivers are loaded at F6 message.
If you don't get a F6 message, there are no mass storage drivers loaded so far.

There is another reason.

This maybe a strange partition.
Yes, some Linux partition prohibit booting.
Boot loader dosn't matter, it's the partition table. Maybe partition type or CHS translation.
PE use CHS translation that early to verify partitions.

Read the fdisk manpage about C/H/S fields and absolute number of sectors.

Or there maybe another BIOS setting: like USB legacy emulation.
At some strange BIOS, this prohibit booting too.

BartPE / UBCD4WIN use setupldr.bin at PE mode.
Setupldr.bin behave different at PE mode or at installation mode.

Clarify again: do you get a F6 message now?

I can only get to a F6 message when:

A. The m/board's SATA RAID device is enabled in the BIOS together with the SATA channnel the drive is connected to.
B. The UBCD4win CD has been built without the "mass storage drivers" and the nvidia SATA_IDE drivers have been added manually to the appropriate directory.

Under these conditions UBCD4win boots and loads but does NOT see the SATA drive. I wouldn't expect it to. The reason is obvious, as the SATA drive was partitioned when not part of any RAID, the partition table is no longer visible when the RAID device is activated in the BIOS before booting.

This isn't really the issue, as its the failure to boot when using "IDE emulation" mode that is the problem.

So, the problem remains the same, when using my configuration on the m/board with the RAID device disabled it functions in "ide emulation" mode. UBCD4win seems for some reason unable to boot under these conditions. ALL other system discs I have used on my configuration appear to work as expected, so I doubt if my SATA drive's partition table is corrupt in any way, and my m/board's SATA controller is fully functional.

cdob

Nov 30 2008, 11:16 AM

Partition table is not corrupt. But may not support PE requirements.
Or there maybe another reason.

For testing purposes:

Try a UBCD4win CD without the "mass storage drivers" and withot the nvidia SATA_IDE drivers.

Use your default BIOS settings: IDE emulation mode.

Disconnect SATA drive.

Does UBCD4win boot?

Attach a new SATA drive.
Partition and format this drive use winows default tools.
Does UBCD4win boot?

Krisbee

Nov 30 2008, 01:06 PM

QUOTE (cdob @ Nov 30 2008, 04:16 PM)

Partition table is not corrupt. But may not support PE requirements.
Or there maybe another reason.

For testing purposes:

Try a UBCD4win CD without the "mass storage drivers" and withot the nvidia SATA_IDE drivers.

Use your default BIOS settings: IDE emulation mode.

Disconnect SATA drive.

Does UBCD4win boot?

Attach a new SATA drive.
Partition and format this drive use winows default tools.
Does UBCD4win boot?

I agree that these are all the test I should do, unfortunately I don't have a spare SATA drive to to use.

But I have just discoverd something I can't believe I missed before. I was convinced I tested this after Mr.Barnes' post.

I was totally wrong to say that my original WIN XP install CD boots OK with my current partition mix of NTFS, FAT32, Linux ext3, and swap. It doesn't boot, it hangs just as the UBCD4WIn cd does.

My sincere apologies to yourself and Mr. Barnes.

So now it's obvious, I can get UBCD4WIN to boot when my RAID ROM is enabled because the change in the BIOS setting means the partition on the SATA drive is not visible, and so the boot is succesful. I didn't have my lateral thinking working. If it can boot when the partition table is not seen, but cannot when the partition table is seen, then it's partition table which is the problem, exactly as your said.

UBCD4win is an impressive project and it's a pity it does seem to like my SATA drive which has both Windows and Linux on it.

But at least I have learnt enough to try building a UBCD4win disk that works on my partner's IBM laptop.

I don't use WinXP much, but I think it is time I had a second (small) SATA drive for my home PC and did not mix Windows and Linux type partitions on one drive.

Thanks again for your help.

Should I mark this as solved?

cdob

Nov 30 2008, 03:37 PM

QUOTE (Krisbee @ Nov 30 2008, 02:06 PM)

I was totally wrong to say that my original WIN XP install CD boots OK with my current partition mix of NTFS, FAT32, Linux ext3, and swap. It doesn't boot, it hangs just as the UBCD4WIn cd does.

Thanks for clarify. This behaviour has been reported in the past.
Linux fdisk may create partitions not compatible with setupldr.bin.
Linux fdisk manpage contain a general description about CHS mapping. This may cause conflicts.
However I don't have a full explanation.

In general UBCD4Win does boot at disks with ext3 partitions.

Backup data. Create multi boot friendly partitions at SATA hard disk.

QUOTE

Should I mark this as solved?

It's not solved. Do you find setupldr.bin requirements?

Krisbee

Nov 30 2008, 03:56 PM

QUOTE (cdob @ Nov 30 2008, 08:37 PM)

QUOTE (Krisbee @ Nov 30 2008, 02:06 PM)

I was totally wrong to say that my original WIN XP install CD boots OK with my current partition mix of NTFS, FAT32, Linux ext3, and swap. It doesn't boot, it hangs just as the UBCD4WIn cd does.

Thanks for clarify. This behaviour has been reported in the past.
Linux fdisk may create partitions not compatible with setupldr.bin.
Linux fdisk manpage contain a general description about CHS mapping. This may cause conflicts.
However I don't have a full explanation.

In general UBCD4Win does boot at disks with ext3 partitions.

Backup data. Create multi boot friendly partitions at SATA hard disk.

QUOTE

Should I mark this as solved?

It's not solved. Do you find setupldr.bin requirements?

OK, I'll have to do a bit more research and juggle my hard drives to see if I can make some progress. One thing I haven't tried yet is to hide all the non-windows partitions on the SATA drive.

I'll report hopefully within 24hrs.

Krisbee

Dec 2 2008, 04:51 PM

I haven't had a chance to spend much more time on this except a quick couple additional tests.

Firstly, I attached a hard drive with both windows and linux partitions to my sil680 ide controller and ubcd4win booted and loaded normally.

As a second further test, I dug out an Abit serillel IDE to SATA converter which allows an IDE drive to be attached to a SATA controller. Using the same IDE drive, but this time connected to the SATA controller, ubcd4win booted and loaded normally.

I used the same linux program, gparted, to partition and format this ide drive as I had done when setting up the sata drive. So it's still a mystery as to why the SATA drive causes a system hang with ubcd4win, but functions perfectly well in normal use.

cdob

Dec 3 2008, 11:06 AM

QUOTE (Krisbee @ Dec 2 2008, 05:51 PM)

I used the same linux program, gparted, to partition and format this ide drive as I had done when setting up the sata drive.

Does IDE and SATA drive use different size?
The same application may partition and format different drives differently.
Different partition and format drives may get different results.

I guess still setupldr.bin / ntdetect.com dosn't like MBR or partitions.

Azshiva

Dec 17 2008, 04:29 PM

If it was me I would erase the sata drive and reformat it. Reinstall all Os. It does sound like the MBR or partitions aren't being reconized. Yes all hdd drives do start having problems with more than one Os installed and if you have installed newer versions over your other Os. Bits and pieces do get lost and over written. Sometimes ya just have to start over.