_dee wrote:
> On Thu, 17 Sep 2009 02:36:35 -0400, Paul <> wrote:
>
>> _dee wrote:
>> <<snip>>
>>
>>> A couple glitches remain... The main one:
>>>
>>> A device called "Promise SATA Console SCSI Processor Device" has
>>> started popping up as a new device at boot. It's listed as such in
>>> Dev Mgr. Problem is that I can't find a driver that it likes. Tried
>>> the standard Asus Promise folders (both ATA and RAID), but I get a
>>> "Cannot Install This Hardware" message.
>> If you're not using the Promise, maybe you can disable it in the
>> BIOS ? I always used to leave mine disabled.
>>
>> If your computer crashes, and the Asus BIOS does a recovery
>> to defaults, that turns the Promise back on again. So I've had to
>> go into the BIOS and turn the Promise off again, because of
>> that.
>>
>> Otherwise, the board was pretty good to me, and the P4C800-E is
>> currently my backup computer, if the one I'm typing on has a
>> problem.
>>
>> I wish Promise had provided a real installer for the driver,
>> instead of an INF based one. As then you'd have an uninstaller
>> in Add/Remove that you could use.
>>
>> Paul
>
> Yeah, Promise has never had great driver support for any of their
> products that I've owned. You'd think that drivers would be valued
> more highly by hardware manufacturers, as that is the final make or
> break for their hardware.
>
> The mystery in this case is why XP won't load the ASUS-supplied
> drivers. I doubt that that in itself is BIOS-related, since I've
> tried both the RAID and plain ATA drivers, and both fail to load.
>
My P4C800-E Deluxe is running Win2K, so won't be exactly the
same as your machine running WinXP. The driver architecture is
similar.
You can try the driver here. What MSI seems to have done, is put
the IDE and RAID drivers in the same folders. I don't think this
driver is materially different, but it is what I used for an experiment.
http://www.msi.com/index.php?func=do...=1&prod_no=544
http://download2.msi.com/files/downl...exe/378_55.exe (5,409,190 bytes)
I extracted this with 7ZIP and had a look around. I expect the
file extracts on its own, but I use 7ZIP for virtually all downloads,
to have a look around.
If I look at the Driver\WinXP directory, I can find...
UlSata.inf
fasttx2k.INF
IF I "Update Driver" and point to the appropriate Windows
directory in the install folders, I get three entries.
Two of the entries come from the fasttx2k.INF file.
None of those exactly matches what you're seeing, You claim
to be seeing
"Promise SATA Console SCSI Processor Device"
and the fasttx2k.INF has
"WinXP Promise Raid Console SCSI Processor Device"
and yet the UlSata.inf file has no string of that type in
the file. The name suggests your BIOS has Promise enabled,
but set to IDE mode.
I would try updating the driver, and point it to the FastTrak
version, if the controller in the BIOS is enabled and set
to RAID mode. If the controller is set to IDE mode in the BIOS,
then you want the UlSata.inf one instead.
I experimented, by changing modes for the Promise, in the BIOS.
I could see no difference in what Everest declared for the
device, so the Promise software must have a way of determine
how the device has been soft configured.
Both drivers can coexist in the machine at the same time. I
didn't have to use "uninstall" in Device Manager for the entry,
for me to be able to change modes and install the other driver
type.
The install seems to consist of two files.
RAID IDE
fasttx2k.sys ulsata.sys <--- boot time service ?
ptipbmf.dll ptipbm.dll <--- controls caching
Using the Sysinternals Autoruns tool, you can see the "pti..."
file added to
HKLM\software\Microsoft\Windows\CurrentVersion\Run
The other file, seems to be set up as a service that starts
at boot time. Yet the service is not listed if you look
in Services from Admin tools.
HKLM\System\CurrentControlSet\Services
If you "Show Hidden Devices" in Device Manager, and look in
"Non-Plug and Play Drivers", the driver type that is not
currently running, seems to be listed in there. So when you've
installed both fasttx2k.sys and ulsata.sys, the type that matches
the hardware operating mode is used normally, while the
unused file shows up in "Non-Plug and Play Drivers" items.
You could try using the "uninstall" option for the driver,
and then reinstall it. Maybe it will take flipping modes in
the BIOS, uninstall, then flip it back, to remove as much
as possible of the existing drivers.
Since I didn't find an exact match for
"Promise SATA Console SCSI Processor Device"
in the files, I don't know whether any of this will fix it.
I tried, but wasn't able to "break" mine :-)
Have fun,
Paul
Similar Threads
Linear Mode
