6rtury
June 27th, 2006, 01:07 PM
Installed TI Home 9, latest build, and it appeared to go OK. Was not asked to make recovery disks at install, so went in and tried to do that first thing. I get a BlueScreen with an error message that reads:
ULSATA.sys- ADRESS F74898D0 base at F7487000, DATESTAMP 3edcoF62
It appears to be a driver conflict, so I've checked all my SATA drivers (of whichWin XP Promise SATA 378 IDE Controller 1.0.90.26 is the latest one). Nothing newer. This is an Intel 82801 EB Ultra ATA chipset, and I have the latest for it.
I reinstalled, and this time as it rebooted at the end I saw an Acronis error message about a memory violation somewhere. It flashed past. Still bluescreened. Tried installing TI in safemode and found I could not do that.
The bluescreen message suggested I also turn of Bios Shadowing, but my Bios setup has no such option.
Running WinXP PRO SP2 on an Intel P4 chip, 2MB memory. System is 4 yrs old.
Before I contact Cus Support has this problem been discussed previously? Have not found any mention of similar problems on the forum, but thought someone may have run into it. BTW, I was a user of PowerQuest's DriveImage before it was bought out by Symantec. It ran beautifully on this same system.
ULSATA.sys- ADRESS F74898D0 base at F7487000, DATESTAMP 3edcoF62
It appears to be a driver conflict, so I've checked all my SATA drivers (of whichWin XP Promise SATA 378 IDE Controller 1.0.90.26 is the latest one). Nothing newer. This is an Intel 82801 EB Ultra ATA chipset, and I have the latest for it.
I reinstalled, and this time as it rebooted at the end I saw an Acronis error message about a memory violation somewhere. It flashed past. Still bluescreened. Tried installing TI in safemode and found I could not do that.
The bluescreen message suggested I also turn of Bios Shadowing, but my Bios setup has no such option.
Running WinXP PRO SP2 on an Intel P4 chip, 2MB memory. System is 4 yrs old.
Before I contact Cus Support has this problem been discussed previously? Have not found any mention of similar problems on the forum, but thought someone may have run into it. BTW, I was a user of PowerQuest's DriveImage before it was bought out by Symantec. It ran beautifully on this same system.