Windows 2003 Std On A Dell Pe 2850

[ibmrulz]

Hello all anyone that can give me any further ideas to solve this problem would be very much appreciated. I have a new Dell 2850 with a PERC 4E/Di running Windows 2003 STD that I am trying to get to work with Veritas Bare Metal restore. What is happening is the Mraid35x driver that comes on the Windows 2003 CD is too old and you MUST use the floppy with the new Mraid35x driver to install Windows, but I do not have this option during a Bare Metal Restore.

I have tried for the last two weeks to replace the Mraid35x driver and update txtsetup.sif to allow for the replacement driver, I have tried to slipstream the new raid driver onto the CD with Nlite.

We have Dell Gold support on this machine, they were totally useless after explaining that I must install with a Windows 2003 CD and nothing else they told me just to use the DOSA CD, which basically tells you what kind of people you are dealing with at Dell.

Also after creating a "new" windows 2003 CD with mraid35x driver put in and the updated tstsetup.sif the server will install Windows 2003 but just as the windows 2003 splash screen comes up it goes into a boot loop.

Please Help!

[Br4tt3]

Lo... had a similar problem.

I have Dell PE 2800 / 1850 & 2850 machines that needed to use the Veritas IDR (Intelligent Disaster Recovery).

U need to del the old mraid35x.sys and add the new one to the U.A CD.

then u need to add the specific entries to the txtsetup.sif file within the i386 folder as mentioned in this forum or @ link:

http://wug.lutteman.se/articles/ris-add-st...g_TXTSETUP.SIF_

then... when IDR questions u for the Win2003 CD, insert the new custom U.A CD so that the Veritas software can "absorb" the newly added driver....

Anyway, the thing u r looking for is the txtsetup.sif file. Do a search on the forum for it...

worked for me atleast...

[ibmrulz]

I tried this too! but had the same issue, after the install copies the files and restarts the server it goes into a boot loop.

But thanks for the reply.

[FeTT!]

***OFF TOPIC***

ibmrulz...

I love your nick name

i have at least 3-4 motherboards/week to change on IBM desktops

hehe, dont take it personnal, IBM are always in troubles..

[ibmrulz]

***OFF TOPIC***

ibmrulz... 

I love your nick name

  i have at least 3-4 motherboards/week to change on IBM desktops 

hehe, dont take it personnal, IBM are always in troubles..

<{POST_SNAPBACK}>

Not as bad as these pieces of crap Dells we now own!

[yaroz]

I don't believe it's a problem with the mraid35x driver, but the addresses assigned. I recently made a txtsetup.sif that should work (copied the PCI addresses out of the oemsetup.inf file from the diskette that we were using).

Copy/edit the following into the txtsetup.sif, in the mraid35x section (the driver that's on the diskette is the exact same as the one that's on the 2003 CD):

[HardwareIdsDatabase]
PCI\VEN_1028&DEV_000F&SUBSYS_014C1028 = "mraid35x"
PCI\VEN_1028&DEV_000F&SUBSYS_014A1028 = "mraid35x"
PCI\VEN_1028&DEV_000F&SUBSYS_013B1028 = "mraid35x"
PCI\VEN_1028&DEV_000E&SUBSYS_01231028 = "mraid35x"
PCI\VEN_1028&DEV_000F&SUBSYS_014D1028 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_11121111 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_11111111 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_09A0101E = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_11111028 = "mraid35x"
PCI\VEN_8086&DEV_1960&SUBSYS_04671028 = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_04711028 = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_04931028 = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_04751028 = "mraid35x"
PCI\VEN_101E&DEV_1960&SUBSYS_05111028 = "mraid35x"
PCI\VEN_1000&DEV_1960&SUBSYS_05181028 = "mraid35x"
PCI\VEN_1000&DEV_1960&SUBSYS_05201028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_016C1028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_016D1028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_016E1028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_016F1028 = "mraid35x"
PCI\VEN_1028&DEV_0013&SUBSYS_01701028 = "mraid35x"
PCI\VEN_1000&DEV_0408&SUBSYS_00011028 = "mraid35x"
PCI\VEN_1000&DEV_0408&SUBSYS_00021028 = "mraid35x"

[ibmrulz]

I don't believe it's a problem with the mraid35x driver, but the addresses assigned.  I recently made a txtsetup.sif that should work (copied the PCI addresses out of the oemsetup.inf file from the diskette that we were using).

Copy/edit the following into the txtsetup.sif, in the mraid35x section (the driver that's on the diskette is the exact same as the one that's on the 2003 CD):

<{POST_SNAPBACK}>

You are the MAN!!! I cannot belive it was that simple! I cannot thank you enough for this, But I will try!

Thanks.

[yaroz]

heh.. so did that work for you? I added that to the txtsetup file, and it works for the 1750, 1850, 2650 and 2750 for us.