Winterlight, Thanks for all the checks. Problem righted itself as soon as I returned the 3 cards to their original pci slots. It seems that either w2k or the u133tx2 is very sensetive to position. I'll take a "stupid" for this! I did not un-install anything before I moved stuff around. LOL! Live and learn.
As soon as the 3 cards were back in their original positions w2k was most happy and all is working peachy again. The bios of the u133tx2 is the latest as is its' drivers. The cable seems to be OK-the original cable. The mainboard is an Abit BX6r2, 440BX w/p2-450 slot 1. The u133tx2 is in pci1. Believe this to be shared only with agp1, but do not use an agp video card. Use Matrox Mill2 in pci2. The intel nic is in pci3. USB shares with pci4 and pci5, so both are empty. Both isa1 and isa2 are empty also. W2K will not install the XP drivers for the u133tx2. Will allow NT4 drivers, however. Silly, but I am use to this behavior. Do not have another OS to test the card with (yet). LOL! Card is very long time out-of-warranty! It will become a dust bin item when/if it does croak. From all the recent list comments about things "Promise," I'm actually surprised at how few problems I've had with my card. (knocks wood!) I am still a bit confused about all these oemX.inf files that w2k seems to create/use to identify the u133tx2. But, as I've now returned the machine to an operational condition and retired it to its' sleeping box, I'll wait for some time in the future to research this subject again. Sometimes this OS seems just too complicated. And, as I get older the complication grows. Thanks again. With your points and some "sit-and-look" the glitch is gone. Best, Duncan On Sun, 29 Jan 2006 15:08 , Winterlight <[EMAIL PROTECTED]> sent: > >First reseat the card, and ALL ribbon cables. This has been a recurring >problem for me on some PCs with Ultra 100's133s. It has even occurred to me >after putting on new cables > >Still a problem, then reinstall the drivers.... or switch from XP drivers >to Promise drivers. > You do have it in a unshared PCI slot right? > >If that doesn't help then try re-flashing your BIOS... note if you have a >Maxtor or WD version of the Ultra 133 TX2 then make sure you use their >flash and or drivers. > >If it isn't fixed then, if possible, boot into another OS, or put it in >another computer, which will tell you right away if this is a hardware problem. > >If nothing helps then it is time to check your warranty. I think this is >two years, Promise is good about it but make sure you try it in another PC >before calling. > >At 06:47 AM 1/29/2006, you wrote: > >>Understand recent traffic about the Promise ultra133 tx2 eide controller, >>sort of. >>I have not had any trouble, until today. My U133 is now showing up with >>the hated >>yellow exclamation point in DM. I have tried to reinstall drivers and/or >>un-install the >>device several times without much luck. I do notice that no matter where I >>point W2K >>for the drivers, W2K chooses its' own location, completes the install, >>and, again fails. >>For some reason W2K just will not do/go where I sent it. Odd? >> >>I do notice the W2K (sp4 pro) seems to have created oem0.inf through >>oem15.inf in >>the winnt/system32/inf location. Several of the these numbered oemx.inf >>files do >>discuss the Promise U133 controller at 3 different driver versions, the >>default MS version, >>the Promise v2.0.29, and the Promise v2.0.43. The v2.0.43 was was running >>before the machine was shutdown for a case change. >> >>Can the "promise-related oemx.inf files be deleted from the inf directory? >> >>Will this clean-up or reset the 0000-0005 keys in the "control set 001" >>area of the registry? >> >>It does seem that something is badly scrambled, but I'm confused about >>where to start any >>un-scramble work. I do NOT find any hidden installs for the controller in >>safe mode either. >> >>Ideas, tweaks, suggestions are welcome. Thanks >>Duncan >> >> >> >> >>This email scanned for Viruses and Spam by ZCloud.net > This email scanned for Viruses and Spam by ZCloud.net
