acid45
08-04-2004, 04:01 PM
I'm having troubles with a RAID card under windows XP home and I don't know where I should ask. Promise doesn't seem to have a forum I can find. I don't think it's an OS issue, but could be.
Where would I ask for help?
And just in case someone here has worked with raids under windows XP I'll post it here...just in case.
Well people are going to be mad, this isn't a Linux BOX. Someone paid me to build them a system. They have the parts and they want a raid, for VERY IMPORTANT information. It's a business at home computer. I'm only having one problem, and that's getting windows XP home to boot with the raid card.
I've checked the Promise Technologies site checked out the FAQ and followed all instructions that pretained to my solution and some that didn't.
I've re-installed windows XP. First time I had it set up in the raid for a mirror raid. The second time I had it on the onboard IDE and then once I got into windows I installed the raid card drivers, set up the raid again, and still the same problem.
USB is disabled
NO other PCI devices
NO AGP card
onboard S3 graphics
IDE channel 0 is disabled
QuickBoot is disabled
Everything but the bare minimum is disabled.
SCSI boot device on Phoenix BIOS
I see the Promise BIOS after the IDE checking. It detects the raid and I've had no problems with the installation, other than if I had the floppy in the drive BEFORE I started the windows setup from CD it would cause a reading error, I just removed the floppy, re-inserted it and it worked fine.
When windows boot the first time it got to the windows loading screen. the "green load bar" got half way across the screen and then the OS reboots.
Since then when the "Windows failed to load" screen the screen is a bunch of greyscaled lines going up and down the screen--this was fixed by disabling the AGP--and then the "green load bar" gets half way across the "load meter" and the same thing happens.
If I boot in "SAFE MODE" it gets to "c:\...\Mup.sys" freezes for a second then reboots.
Because of the "grey lines" I THINK it may be a conflict between the S3 and the RAID card. This is my first raid installation, thus the noobishness.
I've read some posts about people rebooting at the Mup.sys and they had problems where removing USB, physically, on boot and then plugging them in worked. that would get annoying. I couldn't find anything that had to do with a RAID card causing the problems. I found one about PCI devices causing it but well it seems to be booting if I don't use the PCI RAID controller and so I think it's a conflict somewhere and I HOPE it's something I can fix and don't have to replace anything or tell them what they ordered is incompatible. I havn't been able to find any hardware conflict lists. I was using a USB mouse but I had USB disabled and removed it and still the same thing.
===============================================
Again, just somewhere else I can post a question would be great, somewhere where the members don't type "liek dis all da time cuz i dont lkfie it that much". Punctuations is good not only for pausing and whatnot, but for identifying like out of "lkfie."
Something to try but someone found the solution and it could be a driver, although they had a different promise raid card but the same problem.
Where would I ask for help?
And just in case someone here has worked with raids under windows XP I'll post it here...just in case.
Well people are going to be mad, this isn't a Linux BOX. Someone paid me to build them a system. They have the parts and they want a raid, for VERY IMPORTANT information. It's a business at home computer. I'm only having one problem, and that's getting windows XP home to boot with the raid card.
I've checked the Promise Technologies site checked out the FAQ and followed all instructions that pretained to my solution and some that didn't.
I've re-installed windows XP. First time I had it set up in the raid for a mirror raid. The second time I had it on the onboard IDE and then once I got into windows I installed the raid card drivers, set up the raid again, and still the same problem.
USB is disabled
NO other PCI devices
NO AGP card
onboard S3 graphics
IDE channel 0 is disabled
QuickBoot is disabled
Everything but the bare minimum is disabled.
SCSI boot device on Phoenix BIOS
I see the Promise BIOS after the IDE checking. It detects the raid and I've had no problems with the installation, other than if I had the floppy in the drive BEFORE I started the windows setup from CD it would cause a reading error, I just removed the floppy, re-inserted it and it worked fine.
When windows boot the first time it got to the windows loading screen. the "green load bar" got half way across the screen and then the OS reboots.
Since then when the "Windows failed to load" screen the screen is a bunch of greyscaled lines going up and down the screen--this was fixed by disabling the AGP--and then the "green load bar" gets half way across the "load meter" and the same thing happens.
If I boot in "SAFE MODE" it gets to "c:\...\Mup.sys" freezes for a second then reboots.
Because of the "grey lines" I THINK it may be a conflict between the S3 and the RAID card. This is my first raid installation, thus the noobishness.
I've read some posts about people rebooting at the Mup.sys and they had problems where removing USB, physically, on boot and then plugging them in worked. that would get annoying. I couldn't find anything that had to do with a RAID card causing the problems. I found one about PCI devices causing it but well it seems to be booting if I don't use the PCI RAID controller and so I think it's a conflict somewhere and I HOPE it's something I can fix and don't have to replace anything or tell them what they ordered is incompatible. I havn't been able to find any hardware conflict lists. I was using a USB mouse but I had USB disabled and removed it and still the same thing.
===============================================
Again, just somewhere else I can post a question would be great, somewhere where the members don't type "liek dis all da time cuz i dont lkfie it that much". Punctuations is good not only for pausing and whatnot, but for identifying like out of "lkfie."
Something to try but someone found the solution and it could be a driver, although they had a different promise raid card but the same problem.