PROBLEM

Windows XP SP3 detects a disk problem at boot time and runs chkdsk.
Chkdsk displays screenfuls of NTFS index and file system corruption
messages with incomprehensible numeric files and indexes as targets.
File system may or may not be "fixed", but the system proceeds to boot
into Windows logon. Computer seems to be OK, and no "disk" errors in
Event Log.

On subsequent reboots, Windows detects errors and continues to invoke
chkdsk to "fix" them, which it proceeds to do with screenfuls of
adjustments to the file system. But this doesn't fix the problem, and
corrupted files are eventually identified on a large data drive (200GB
Seagate drive, attached as Secondary Master to a Promise Ultra100 TX2
IDE PCI controller). Files are moved off the drive in question, but
tests of some large .zip and .bkf files show them to be corrupt, and
some txt files have unreadable data. The NTFS file system has been
corrupted and the drive has to be reformatted.

Upon reformat and reboot, Windows detects an error in the freshly-
formatted file system and invokes chkdsk again, which identifies cross-
linked files and bad cluster attributes, which it proceeds to "fix".
No files have been loaded on the newly-formatted drive at this point.

Attempt to run chkdsk from a command window fails, absent using the "/
f" parameter. Running 'chkdsk /f' proceeds to make corrections to a
nominally bad file system. Complete removal of the partition is now
indicated.

Upon removal of the logical disk drive and the extended partition,
drive presents itself as a 128GB drive to Drive Manager (it is a 200GB
Seagate drive). This looks like the old "128GB / 137GB" 48-bit LBA
problem, but since this problem was solved with Windows XP SP2 and
this is SP3, that solution will probably not hold here.

Googling around for a while yields mainly the old Windows XP SP1/SP2
or registry fix for large LBA drives, and no clear solution. Data loss
stories are evident ("Running chkdsk Results in a 220GB Loss Of Data?
Why? How? Help!!!"
http://groups.google.com/group/micro...6199509fc5deca)

DIAGNOSIS

The problem is with Windows XP and its rejection of the newer Promise
Ultra IDE controller device drivers, which are unsigned and not
Microsoft certified.

Windows XP SP3 automatically, intentionally and silently reverts to an
old version of Promise Ultra IDE driver ultra.sys, version 1.43, which
does not support 48-bit large LBA drives.

As a result, a system that has been otherwise functioning perfectly
well will fail and experience data corruption on any large hard drive
attached to a Promise controller after Windows is allowed to upgrade,
restore or repair itself auotmatically, and may emit only a single
error message to the System Event Log referencing NTFS file system
corruption.

DISCUSSION

It turns out that in this case my system contracted a nasty root kit
infection, for which I both ran System File Check and perhaps shortly
thereafter ran a repair and upgrade from CD from SP2 to SP3. In any
case either of these operations would have been enough to restore the
older Microsoft-certified ultra.sys driver. While I had had this
problem and solved it in the past, I had forgotten about this effect
at this point.

The Windows default Promise ultra.sys IDE driver, which does not
support large 48-bit LBA drives, can be identified by the string
'Promise Ultra IDE Controller, v1.43 (Build 0603)' per Device
Manager. Windows will restore this driver on an upgrade from SP2 to
SP3, when System File Check is invoked to restore known versions of
its drivers, or when the Windows installation is repaired from the
distribution CD. It even will do it on an unattended install when you
try to install the current driver, since the current driver loses out
in points with Windows Setup's contention and driver installation
system. It does this because the default driver is signed and
Microsoft certified, whereas the newer drivers are not. While there
are lines in setuplog.txt identifying this rejection, the versions are
not identified and no posting is made in the System Event Log.

Even though the system may have been set up at some point with the
correct and most recent Promise Ultra100 TX2 (or Ultra33 TX2) drivers,
since these Promise drivers are unsigned and not certified by
Microsoft, Windows setup rejects the installed or otherwise available
drivers.

The two most recent compatible but unsigned drivers for this
controller are:

WinXP Promise Ultra100 (tm) IDE Controller version 2.0.0.42
(3/28/2003)
WinXP Promise Ultra100 (tm) IDE Controller version 2.0.0.43
(5/16/2003)

It may have been possible to avoid any data corruption at all by
promptly manually installing the newer drivers immediately after the
use of sfc or the repair from CD. Since some of the drive data has
already been corrupted at this point, and the drive reformatted, this
is not a verified solution, but rather a diagnosis that could lead to
a full solution with no loss of data in the future if one were alert
enough to catch this problem in time.

-- Roy Zider

Is your boot partition larger than 137GB? If so read this
http://www.randem.com/discus/message...tml?1236319938


--
Randem Systems
Your Installation Specialist
The Top Inno Setup Script Generator
http://www.randem.com/innoscript.html
Disk Read Error Press Ctl+Alt+Del to Restart
http://www.randem.com/discus/message...tml?1236319938



"FUBARinSFO" <(E-Mail Removed)> wrote in message
news:3ac4fd97-b3e5-4790-ad30-(E-Mail Removed)...
> PROBLEM
>
> Windows XP SP3 detects a disk problem at boot time and runs chkdsk.
> Chkdsk displays screenfuls of NTFS index and file system corruption
> messages with incomprehensible numeric files and indexes as targets.
> File system may or may not be "fixed", but the system proceeds to boot
> into Windows logon. Computer seems to be OK, and no "disk" errors in
> Event Log.
>
> On subsequent reboots, Windows detects errors and continues to invoke
> chkdsk to "fix" them, which it proceeds to do with screenfuls of
> adjustments to the file system. But this doesn't fix the problem, and
> corrupted files are eventually identified on a large data drive (200GB
> Seagate drive, attached as Secondary Master to a Promise Ultra100 TX2
> IDE PCI controller). Files are moved off the drive in question, but
> tests of some large .zip and .bkf files show them to be corrupt, and
> some txt files have unreadable data. The NTFS file system has been
> corrupted and the drive has to be reformatted.
>
> Upon reformat and reboot, Windows detects an error in the freshly-
> formatted file system and invokes chkdsk again, which identifies cross-
> linked files and bad cluster attributes, which it proceeds to "fix".
> No files have been loaded on the newly-formatted drive at this point.
>
> Attempt to run chkdsk from a command window fails, absent using the "/
> f" parameter. Running 'chkdsk /f' proceeds to make corrections to a
> nominally bad file system. Complete removal of the partition is now
> indicated.
>
> Upon removal of the logical disk drive and the extended partition,
> drive presents itself as a 128GB drive to Drive Manager (it is a 200GB
> Seagate drive). This looks like the old "128GB / 137GB" 48-bit LBA
> problem, but since this problem was solved with Windows XP SP2 and
> this is SP3, that solution will probably not hold here.
>
> Googling around for a while yields mainly the old Windows XP SP1/SP2
> or registry fix for large LBA drives, and no clear solution. Data loss
> stories are evident ("Running chkdsk Results in a 220GB Loss Of Data?
> Why? How? Help!!!"
> http://groups.google.com/group/micro...6199509fc5deca)
>
> DIAGNOSIS
>
> The problem is with Windows XP and its rejection of the newer Promise
> Ultra IDE controller device drivers, which are unsigned and not
> Microsoft certified.
>
> Windows XP SP3 automatically, intentionally and silently reverts to an
> old version of Promise Ultra IDE driver ultra.sys, version 1.43, which
> does not support 48-bit large LBA drives.
>
> As a result, a system that has been otherwise functioning perfectly
> well will fail and experience data corruption on any large hard drive
> attached to a Promise controller after Windows is allowed to upgrade,
> restore or repair itself auotmatically, and may emit only a single
> error message to the System Event Log referencing NTFS file system
> corruption.
>
> DISCUSSION
>
> It turns out that in this case my system contracted a nasty root kit
> infection, for which I both ran System File Check and perhaps shortly
> thereafter ran a repair and upgrade from CD from SP2 to SP3. In any
> case either of these operations would have been enough to restore the
> older Microsoft-certified ultra.sys driver. While I had had this
> problem and solved it in the past, I had forgotten about this effect
> at this point.
>
> The Windows default Promise ultra.sys IDE driver, which does not
> support large 48-bit LBA drives, can be identified by the string
> 'Promise Ultra IDE Controller, v1.43 (Build 0603)' per Device
> Manager. Windows will restore this driver on an upgrade from SP2 to
> SP3, when System File Check is invoked to restore known versions of
> its drivers, or when the Windows installation is repaired from the
> distribution CD. It even will do it on an unattended install when you
> try to install the current driver, since the current driver loses out
> in points with Windows Setup's contention and driver installation
> system. It does this because the default driver is signed and
> Microsoft certified, whereas the newer drivers are not. While there
> are lines in setuplog.txt identifying this rejection, the versions are
> not identified and no posting is made in the System Event Log.
>
> Even though the system may have been set up at some point with the
> correct and most recent Promise Ultra100 TX2 (or Ultra33 TX2) drivers,
> since these Promise drivers are unsigned and not certified by
> Microsoft, Windows setup rejects the installed or otherwise available
> drivers.
>
> The two most recent compatible but unsigned drivers for this
> controller are:
>
> WinXP Promise Ultra100 (tm) IDE Controller version 2.0.0.42
> (3/28/2003)
> WinXP Promise Ultra100 (tm) IDE Controller version 2.0.0.43
> (5/16/2003)
>
> It may have been possible to avoid any data corruption at all by
> promptly manually installing the newer drivers immediately after the
> use of sfc or the repair from CD. Since some of the drive data has
> already been corrupted at this point, and the drive reformatted, this
> is not a verified solution, but rather a diagnosis that could lead to
> a full solution with no loss of data in the future if one were alert
> enough to catch this problem in time.
>
> -- Roy Zider

1. Randem: This is not a boot disk, it is a data disk as noted,
"extended partition" does not support boot volumes. In any case boot
disk is 60GB on this system.

2. John: SP2 and SP3 still depend on drivers. The ones from Promise
are unsigned, and therefore have not been certified by Microsoft. Most
likely Promise Technology was not willing to pay Microsoft whatever
fee they wanted. Perhaps also Microsoft is tired of having unsigned
drivers interfering with the integrity of their operating system.

In this case, when Windows SP2 or SP3 first install, the ultra.sys
only supports 128/137 GB drive. If it were left at that, there would
be no fear of data corruption, which is the real risk here. But
somebody who buys a 200GB drive is not going to be satisfied, so will
override the default driver with one of the newer drivers that do
support the larger drive geometry.

Unfortunately, when Windows detects this, it reverts back to the
default driver ultra.sys, resulting in data loss (unless you are smart
and alert enough to catch it before the drive is used again, not very
likely). Windows will detect this under the circumstances noted
above.

Below are the lines from C:\setupapi.log that show the overriding of
the detection of the unsigned driver when it it reinstalled manually.
(My original note is incorrect in stating that the versions are not
reported -- here in the manual install at least the dates are visible.
The version of the proposed driver is visible since it is in the disk
path. Also, it appears I installed the wrong driver -- Ultra100 TX2
-- rather than the Ultra100 which strictly speaking is the exact card
installed. But the TX2 is a superset of the other, so no harm done.)

-- Roy Zider


[2009/03/25 18:04:36 1108.368 Driver Install]
#-019 Searching for hardware ID(s): pci
\ven_105a&dev_4d30&subsys_4d33105a&rev_02,pci
\ven_105a&dev_4d30&subsys_4d33105a,pci\ven_105a&dev_4d30&cc_018000,pci
\ven_105a&dev_4d30&cc_0180
#-018 Searching for compatible ID(s): pci\ven_105a&dev_4d30&rev_02,pci
\ven_105a&dev_4d30,pci\ven_105a&cc_018000,pci\ven_105a&cc_0180,pci
\ven_105a,pci\cc_018000,pci\cc_0180
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" /s C:
\WINDOWS\system32\compmgmt.msc
#I063 Selected driver installs from section [ultra_Inst] in "c:\windows
\inf\pnpscsi.inf".
#I320 Class GUID of device remains: {4D36E97B-E325-11CE-
BFC1-08002BE10318}.
#I060 Set selected driver.

[2009/03/25 18:14:13 1108.378 Driver Install]
#-406 Obtaining rollback information for device "PCI
\VEN_105A&DEV_4D30&SUBSYS_4D33105A&REV_02\4&1FDC0565&0&2080":
#-019 Searching for hardware ID(s): pci
\ven_105a&dev_4d30&subsys_4d33105a&rev_02,pci
\ven_105a&dev_4d30&subsys_4d33105a,pci\ven_105a&dev_4d30&cc_018000,pci
\ven_105a&dev_4d30&cc_0180
#-018 Searching for compatible ID(s): pci\ven_105a&dev_4d30&rev_02,pci
\ven_105a&dev_4d30,pci\ven_105a&cc_018000,pci\ven_105a&cc_0180,pci
\ven_105a,pci\cc_018000,pci\cc_0180
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" /s C:
\WINDOWS\system32\compmgmt.msc
#I063 Selected driver installs from section [ultra_Inst] in "c:\windows
\inf\pnpscsi.inf".
#I320 Class GUID of device remains: {4D36E97B-E325-11CE-
BFC1-08002BE10318}.
#I060 Set selected driver.

[2009/03/25 18:06:17 1108.370]
#-198 Command line processed: "C:\WINDOWS\system32\mmc.exe" /s C:
\WINDOWS\system32\compmgmt.msc
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci
\ven_105a&dev_4d30&subsys_4d33105a&rev_02,pci
\ven_105a&dev_4d30&subsys_4d33105a,pci\ven_105a&dev_4d30&cc_018000,pci
\ven_105a&dev_4d30&cc_0180
#-018 Searching for compatible ID(s): pci\ven_105a&dev_4d30&rev_02,pci
\ven_105a&dev_4d30,pci\ven_105a&cc_018000,pci\ven_105a&cc_0180,pci
\ven_105a,pci\cc_018000,pci\cc_0180
#I022 Found "PCI\VEN_105A&DEV_4D30&CC_0180" in C:\WINDOWS\inf
\pnpscsi.inf; Device: "Promise Technology Inc. Ultra IDE Controller";
Driver: "Promise Technology Inc. Ultra IDE Controller"; Provider:
"Microsoft"; Mfg: "PROMISE"; Section name: "ultra_Inst".
#I023 Actual install section: [ultra_Inst]. Rank: 0x00000003.
Effective driver date: 07/01/2001.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem0.inf; Device: "WinNT Promise Ultra100 (tm) IDE Controller";
Driver: "WinNT Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NT]. Rank: 0x00008001.
Effective driver date: 03/28/2003.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem1.inf; Device: "WinXP Promise Ultra100 (tm) IDE Controller";
Driver: "WinXP Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NTx86]. Rank: 0x00008001.
Effective driver date: 05/16/2003.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem6.inf; Device: "WinXP Promise Ultra100 (tm) IDE Controller";
Driver: "WinXP Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NTx86]. Rank: 0x00008001.
Effective driver date: 03/28/2003.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ultra_Inst] in "c:\windows
\inf\pnpscsi.inf".
#I320 Class GUID of device remains: {4D36E97B-E325-11CE-
BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ultra_Inst] in "c:\windows
\inf\pnpscsi.inf".
#I320 Class GUID of device remains: {4D36E97B-E325-11CE-
BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci
\ven_105a&dev_4d30&subsys_4d33105a&rev_02,pci
\ven_105a&dev_4d30&subsys_4d33105a,pci\ven_105a&dev_4d30&cc_018000,pci
\ven_105a&dev_4d30&cc_0180
#-018 Searching for compatible ID(s): pci\ven_105a&dev_4d30&rev_02,pci
\ven_105a&dev_4d30,pci\ven_105a&cc_018000,pci\ven_105a&cc_0180,pci
\ven_105a,pci\cc_018000,pci\cc_0180
#I022 Found "PCI\VEN_105A&DEV_4D30&CC_0180" in C:\WINDOWS\inf
\pnpscsi.inf; Device: "Promise Technology Inc. Ultra IDE Controller";
Driver: "Promise Technology Inc. Ultra IDE Controller"; Provider:
"Microsoft"; Mfg: "PROMISE"; Section name: "ultra_Inst".
#I023 Actual install section: [ultra_Inst]. Rank: 0x00000003.
Effective driver date: 07/01/2001.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem0.inf; Device: "WinNT Promise Ultra100 (tm) IDE Controller";
Driver: "WinNT Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NT]. Rank: 0x00008001.
Effective driver date: 03/28/2003.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem1.inf; Device: "WinXP Promise Ultra100 (tm) IDE Controller";
Driver: "WinXP Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NTx86]. Rank: 0x00008001.
Effective driver date: 05/16/2003.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem6.inf; Device: "WinXP Promise Ultra100 (tm) IDE Controller";
Driver: "WinXP Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NTx86]. Rank: 0x00008001.
Effective driver date: 03/28/2003.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ultra_Inst] in "c:\windows
\inf\pnpscsi.inf".
#I320 Class GUID of device remains: {4D36E97B-E325-11CE-
BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ultra_Inst] in "c:\windows
\inf\pnpscsi.inf".
#I320 Class GUID of device remains: {4D36E97B-E325-11CE-
BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci
\ven_105a&dev_4d30&subsys_4d33105a&rev_02,pci
\ven_105a&dev_4d30&subsys_4d33105a,pci\ven_105a&dev_4d30&cc_018000,pci
\ven_105a&dev_4d30&cc_0180
#-018 Searching for compatible ID(s): pci\ven_105a&dev_4d30&rev_02,pci
\ven_105a&dev_4d30,pci\ven_105a&cc_018000,pci\ven_105a&cc_0180,pci
\ven_105a,pci\cc_018000,pci\cc_0180
#I022 Found "PCI\VEN_105A&DEV_4D30&CC_0180" in C:\WINDOWS\inf
\pnpscsi.inf; Device: "Promise Technology Inc. Ultra IDE Controller";
Driver: "Promise Technology Inc. Ultra IDE Controller"; Provider:
"Microsoft"; Mfg: "PROMISE"; Section name: "ultra_Inst".
#I023 Actual install section: [ultra_Inst]. Rank: 0x00000003.
Effective driver date: 07/01/2001.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem0.inf; Device: "WinNT Promise Ultra100 (tm) IDE Controller";
Driver: "WinNT Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NT]. Rank: 0x00008001.
Effective driver date: 03/28/2003.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem1.inf; Device: "WinXP Promise Ultra100 (tm) IDE Controller";
Driver: "WinXP Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NTx86]. Rank: 0x00008001.
Effective driver date: 05/16/2003.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem6.inf; Device: "WinXP Promise Ultra100 (tm) IDE Controller";
Driver: "WinXP Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NTx86]. Rank: 0x00008001.
Effective driver date: 03/28/2003.
#-019 Searching for hardware ID(s): pci
\ven_105a&dev_4d30&subsys_4d33105a&rev_02,pci
\ven_105a&dev_4d30&subsys_4d33105a,pci\ven_105a&dev_4d30&cc_018000,pci
\ven_105a&dev_4d30&cc_0180
#-018 Searching for compatible ID(s): pci\ven_105a&dev_4d30&rev_02,pci
\ven_105a&dev_4d30,pci\ven_105a&cc_018000,pci\ven_105a&cc_0180,pci
\ven_105a,pci\cc_018000,pci\cc_0180
#I060 Set selected driver.
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci
\ven_105a&dev_4d30&subsys_4d33105a&rev_02,pci
\ven_105a&dev_4d30&subsys_4d33105a,pci\ven_105a&dev_4d30&cc_018000,pci
\ven_105a&dev_4d30&cc_0180
#-018 Searching for compatible ID(s): pci\ven_105a&dev_4d30&rev_02,pci
\ven_105a&dev_4d30,pci\ven_105a&cc_018000,pci\ven_105a&cc_0180,pci
\ven_105a,pci\cc_018000,pci\cc_0180
#I022 Found "PCI\VEN_105A&DEV_4D30&CC_0180" in C:\WINDOWS\inf
\pnpscsi.inf; Device: "Promise Technology Inc. Ultra IDE Controller";
Driver: "Promise Technology Inc. Ultra IDE Controller"; Provider:
"Microsoft"; Mfg: "PROMISE"; Section name: "ultra_Inst".
#I023 Actual install section: [ultra_Inst]. Rank: 0x00000003.
Effective driver date: 07/01/2001.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem0.inf; Device: "WinNT Promise Ultra100 (tm) IDE Controller";
Driver: "WinNT Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NT]. Rank: 0x00008001.
Effective driver date: 03/28/2003.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem1.inf; Device: "WinXP Promise Ultra100 (tm) IDE Controller";
Driver: "WinXP Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NTx86]. Rank: 0x00008001.
Effective driver date: 05/16/2003.
#I022 Found "PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A" in C:\WINDOWS\inf
\oem6.inf; Device: "WinXP Promise Ultra100 (tm) IDE Controller";
Driver: "WinXP Promise Ultra100 (tm) IDE Controller"; Provider:
"Promise Technology"; Mfg: "Promise Technology"; Section name:
"ultra100PCI".
#I087 Driver node not trusted, rank changed from 0x00000001 to
0x00008001.
#I023 Actual install section: [ultra100PCI.NTx86]. Rank: 0x00008001.
Effective driver date: 03/28/2003.
#-019 Searching for hardware ID(s): pci
\ven_105a&dev_4d30&subsys_4d33105a&rev_02,pci
\ven_105a&dev_4d30&subsys_4d33105a,pci\ven_105a&dev_4d30&cc_018000,pci
\ven_105a&dev_4d30&cc_0180
#-018 Searching for compatible ID(s): pci\ven_105a&dev_4d30&rev_02,pci
\ven_105a&dev_4d30,pci\ven_105a&cc_018000,pci\ven_105a&cc_0180,pci
\ven_105a,pci\cc_018000,pci\cc_0180
#-124 Doing copy-only install of "PCI
\VEN_105A&DEV_4D30&SUBSYS_4D33105A&REV_02\4&1FDC0565&0&2080".
#W334 Failed to verify catalog when scanning file queue. Error 1168:
Element not found.
#E360 An unsigned or incorrectly signed file "c:\windows\inf\oem6.inf"
for driver "WinXP Promise Ultra100 (tm) IDE Controller" will be
installed (Policy=Ignore). Error 1168: Element not found.
#W187 Install failed, attempting to restore original files.
#E360 An unsigned or incorrectly signed file "c:\windows\inf\oem6.inf"
for driver "WinXP Promise Ultra100 (tm) IDE Controller" will be
installed (Policy=Ignore). Error 1168: Element not found.
#-024 Copying file "\\mpx\srcdsks\system\hdd\promise\ultra100
tx2\drivers\2.00.0.42\tt\ultra 133_100 tx2 driver_b42\winxp\Ultra.sys"
to "C:\WINDOWS\system32\DRIVERS\Ultra.sys".
#E245 The device installation digital signature failure policy has
been elevated from Ignore to Warn due to a proposed replacement of a
protected system file.
#E366 An unsigned or incorrectly signed file "\\mpx\srcdsks\system\hdd
\promise\ultra100 tx2\drivers\2.00.0.42\tt\ultra 133_100 tx2
driver_b42\winxp\Ultra.sys" for driver "WinXP Promise Ultra100 (tm)
IDE Controller" will be installed (Policy=Warn, user said ok). Error
1168: Element not found.
#E243 Exemption obtained for protected system file "C:\WINDOWS
\system32\DRIVERS\Ultra.sys".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ultra100PCI.NTx86.Interfaces] from "c:
\windows\inf\oem6.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI
\VEN_105A&DEV_4D30&SUBSYS_4D33105A&REV_02\4&1FDC0565&0&2080".
#I121 Device install of "PCI
\VEN_105A&DEV_4D30&SUBSYS_4D33105A&REV_02\4&1FDC0565&0&2080" finished
successfully.