When trying to install OS to new bootable Raid 0 array with CyberPower Inc XP
Pro Recovery CD after the OS formats the Drive where the OS it to go it
starts to seek the Raid drivers again. If I do install with another XP Home
disk I have install is fine! Doing normal Raid install Hit F6 -> Add Raid
Drivers from Floopy -> OS sees drive and so on till it formats the drive.

CyberPower said I needed to add this File WINNT.SIF to the Raid Disc!

File has these call outs:

[Data]
AutoPartition = 1
MsDosInitiated = 0
UnattendedInstall = Yes

[Unattended]
UnattendMode = GUIattended
OemSkipEula = No
OemPreinstall = No
DriverSigningPolicy = Warn

[GuiUnattended]
AdminPassword = *
AutoLogon = Yes
AutoLogonCount = 1

[GUIRunOnce]

[UserData]
FullName = YourName
OrgName = CompanyName
ComputerName = *

[Display]
BitsPerPel = 32
XResolution = 1024
YResolution = 768
VRefresh = 70

[Identification]
JoinWorkgroup = Workgroup

[Networking]

[Shell]
DefaultThemesOff = No
DefaultStartPanelOff = yes

;For Server installations only
[LicenseFilePrintData]
AutoMode = PerSeat


I am not sure how this is going to work? The tech at CyberPower was extremly
rude and combative. I thought I paid extra for a full copy of XP Pro when I
purchased my system! Well anyhow I am guessing here that I need to add this
file to the Raid Driver disc for this to work. The tech at Cyber didnt
comfirm this or do I run this on its own. I am still in shock at how tech at
CyberPower Inc treated me for something I paid for something I paid for.

Thanks

Sorry I also posted this on the New User Section and it should have been
here....

So if a retail version of xp sees the RAID set,F6 is ok,then procceed to xp
cd boot screen and install xp.If youre oem copy isnt up to it,then purchase
a retail copy of xp.Cyberpower xp disk (if that what you have) is going to
be the problem.

"David" wrote:

> When trying to install OS to new bootable Raid 0 array with CyberPower Inc XP
> Pro Recovery CD after the OS formats the Drive where the OS it to go it
> starts to seek the Raid drivers again. If I do install with another XP Home
> disk I have install is fine! Doing normal Raid install Hit F6 -> Add Raid
> Drivers from Floopy -> OS sees drive and so on till it formats the drive.
>
> CyberPower said I needed to add this File WINNT.SIF to the Raid Disc!
>
> File has these call outs:
>
> [Data]
> AutoPartition = 1
> MsDosInitiated = 0
> UnattendedInstall = Yes
>
> [Unattended]
> UnattendMode = GUIattended
> OemSkipEula = No
> OemPreinstall = No
> DriverSigningPolicy = Warn
>
> [GuiUnattended]
> AdminPassword = *
> AutoLogon = Yes
> AutoLogonCount = 1
>
> [GUIRunOnce]
>
> [UserData]
> FullName = YourName
> OrgName = CompanyName
> ComputerName = *
>
> [Display]
> BitsPerPel = 32
> XResolution = 1024
> YResolution = 768
> VRefresh = 70
>
> [Identification]
> JoinWorkgroup = Workgroup
>
> [Networking]
>
> [Shell]
> DefaultThemesOff = No
> DefaultStartPanelOff = yes
>
> ;For Server installations only
> [LicenseFilePrintData]
> AutoMode = PerSeat
>
>
> I am not sure how this is going to work? The tech at CyberPower was extremly
> rude and combative. I thought I paid extra for a full copy of XP Pro when I
> purchased my system! Well anyhow I am guessing here that I need to add this
> file to the Raid Driver disc for this to work. The tech at Cyber didnt
> comfirm this or do I run this on its own. I am still in shock at how tech at
> CyberPower Inc treated me for something I paid for something I paid for.
>
> Thanks
>
> Sorry I also posted this on the New User Section and it should have been
> here....

Agreed I am trying it with the file they provided added to the Raid driver
floopy and it is still not working. When I purchased the system I paid extra
for an OS and even more for XP Pro due to the type systems CyberPower builds
I thought I was paying for a full working copy of XP Pro I cant see why I
should have to go out and spend 199 for upgrade or 299 for a full MS Version
of XP Pro when I that is what I paid for originally. Grrr.

"Andrew E." wrote:

> So if a retail version of xp sees the RAID set,F6 is ok,then procceed to xp
> cd boot screen and install xp.If youre oem copy isnt up to it,then purchase
> a retail copy of xp.Cyberpower xp disk (if that what you have) is going to
> be the problem.
>
> "David" wrote:
>
> > When trying to install OS to new bootable Raid 0 array with CyberPower Inc XP
> > Pro Recovery CD after the OS formats the Drive where the OS it to go it
> > starts to seek the Raid drivers again. If I do install with another XP Home
> > disk I have install is fine! Doing normal Raid install Hit F6 -> Add Raid
> > Drivers from Floopy -> OS sees drive and so on till it formats the drive.
> >
> > CyberPower said I needed to add this File WINNT.SIF to the Raid Disc!
> >
> > File has these call outs:
> >
> > [Data]
> > AutoPartition = 1
> > MsDosInitiated = 0
> > UnattendedInstall = Yes
> >
> > [Unattended]
> > UnattendMode = GUIattended
> > OemSkipEula = No
> > OemPreinstall = No
> > DriverSigningPolicy = Warn
> >
> > [GuiUnattended]
> > AdminPassword = *
> > AutoLogon = Yes
> > AutoLogonCount = 1
> >
> > [GUIRunOnce]
> >
> > [UserData]
> > FullName = YourName
> > OrgName = CompanyName
> > ComputerName = *
> >
> > [Display]
> > BitsPerPel = 32
> > XResolution = 1024
> > YResolution = 768
> > VRefresh = 70
> >
> > [Identification]
> > JoinWorkgroup = Workgroup
> >
> > [Networking]
> >
> > [Shell]
> > DefaultThemesOff = No
> > DefaultStartPanelOff = yes
> >
> > ;For Server installations only
> > [LicenseFilePrintData]
> > AutoMode = PerSeat
> >
> >
> > I am not sure how this is going to work? The tech at CyberPower was extremly
> > rude and combative. I thought I paid extra for a full copy of XP Pro when I
> > purchased my system! Well anyhow I am guessing here that I need to add this
> > file to the Raid Driver disc for this to work. The tech at Cyber didnt
> > comfirm this or do I run this on its own. I am still in shock at how tech at
> > CyberPower Inc treated me for something I paid for something I paid for.
> >
> > Thanks
> >
> > Sorry I also posted this on the New User Section and it should have been
> > here....