@Fernando 1

Maybe a stupid question, but 'm trying to understand it.
If I integrate the nvsata and nvraid drivers, the necessary changes
will be applied to txtsetup.sif.
nvatabus.sys and nvraid.sys will be copied to the I386 dir.
Untill this I understand. What I don't understand is the following.

A dir is created in I386 with the nForce drivers.
In the txtsetup.sif nLite is making extra "dirs" (1883,1884)
which point to the driver-dir in the I386 Folder.
Then under the file section i see this.
nvcoi.dll = 1883,,,,,,,,1883,,,,0,0
This means that nvcoi.dll is in the dir 1883 and copied to 1883.
My question is.
Is the extra directory in the I386 folder with the integrated drivers necessary?
I didn't find any connections to this folder and it's file

Thx

As I am not an expert in TXTSETUP.SIF, I am not sure, that I can give you a satisfactory answer.
The first step during the Windows Setup is the detection of the mass storage devices. If you want do avoid F6/floppy method, you have to integrate these unknown drivers (in this case the drivers NVATABUS.SYS and NVRAID.SYS) as textmode drivers. During the first (=TEXTMODE) part of the installation Windows Setup does not look into the driver folders (i386\NLDRV subfolders), but only into the TXTSETUP.OEM and some entries of the TXTSETUP.SIF (not the one you mentioned). The needed mass storage controller drivers (only the SYS files) have to be in the root of i386. Otherwise Setup would not find them.
During the second (=GUIMODE) part Windows Setup looks again into TXTSETUP.SIF, but now it uses all NLDRV driver subfolders.
That is the reason, why you find the compressed drivers NVATABUS.SY_ and NVRAID.SY_ twice within your nLited CD (within the i386 root and within one of the i386\NLDRV subfolders).
The files IDECOI.DLL and NVCOI.DLL are necessary Co-Installer files for the driver NVATABUS.SYS. You will find these entries within the NVATABUS.INF. All these files (SYS=drivers, INF=information files and DLL=coinstallers) have to be within the same folder. Otherwise the driver would not be installed during GUIMODE part of the Setup.
In earlier versions of nLite all PnP and textmode drivers were put into one folder (named NLDRV or OEMDIR). Since nLite RC7 each driver is stored within a separate subfolder. Other CD creating tools store the drivers within the $OEM$\§1\drivers folder.
So the answer to your question, if a separate folder for the integrated drivers is necessary, must be a "Yes!", but only for the GUIMODE part of the installation. The separation of each driver within the driver folder is not really necessary, but more clearly laid out for the user.

Is this answer satisfying for you?

@Fernando

Fernando your'e the best.
Thanx for the quick reply.

Excellent guide Fernando. I have a question that may have been answered already (I didn't find it). Is there any reason not to use the newest drivers? I have an Intel nForce4 SLI chipset and there are 7.15 drivers now.

You can take them, because they have a LEGACY subfolder. Just integrate this folder as TEXTMODE driver.

Thank you for the post. As a consequence I have just added these drivers to my guide (first post of this thread).

CU
Fernando

Hello -

I have an ASUS A8N-SLI DELUXE and have ensured the latest BIOS release has been flashed, as well as verified that the NVRAID BIOS is at 4.78 or higher.

I have followed the instructions in the first post of this thread, and tried each of the methods listed in section 1, 2, and 4 of that post (recommendation: please number these methods) and each time have gotten the same results when attempting to boot windows install CD creating from the resulting ISO:

When the CD boots, I get the normal "blue screen" that shows that the CD is booting and that the windows installation is being started. After all the drivers are loaded/reviewed at the bottom of the screen, the very last message displayed is "running windows" and what typically follows is another blue screen that has a license agreement/disclaimer before proceeding with the installation.

Instead, what is displayed, after 10 minutes of what appears to be "loading" is just a bunch of === characters, not many. It almost appears that the standard input from the keyboard might work, if one knew what to type, but instead, it is just a blank screen.

I have meticulously followed the instructions, ensured that no other devices are plugged into the PC (all other hard drives are disconnected except for the 2 WD SATA drives configured on the NVRAID controller.

I have kept the nlite installation to a bare minimum - I've slipstreamed SP2 and incorporated the aforementioned drivers as documented. And with each attempt, I've started from scratch with a fresh copy of the XP CD in a new subdirectory on my hard drive (which I also disconnected prior to attempting the installation).

Any thoughts on what I might be overlooking here?

What you probably need, if you want to integrate the newest nForce Raid drivers, is a RAID BIOS version 4.84 or higher.
There is only one single method used by nLite (it's the "Driver suppression method"). If you want to test the other method (called "OemInfFiles method") you should use the tool CD Creator. What you certainly mean are the different ways to integrate the needed driver files. If you have an nVRaid BIOS v. 4.84 or higher, I recommend the easiest way by integrating the LEGACY subfolder of the nForce chipset package v. 6.70.
The nForce SataRaid driver integration method I have desribed in my first post is approved on nearly every mainboard with an nForce Raid controller. If users have problems with my guide unless they have all done what I have written, this is mostly due to a hardware problem which has to be solved first.

My suggestion:
Try to install Windows XP by F6/floppy method. Before you do that, copy the content of the IDE\WinXP folder of the old nForce chipset driver package v. 6.53 onto a formatted floppy disk. If you don't have a floppy drive, create a new nLited CD and do nothing else but integrate the just mentioned SataRaid driver files as TEXTMODE driver. Burn the ISO and try to install XP this way.
If the installation fails even by doing this safe way, you have a hardware problem.

Good luck!
Fernando

Greetings Fernando,

I performed the nLite nVRaid as clearly stated at the begining of this thread and I believe it worked as intended. Since I haven't installed all my hard drives yet I am not completely sure if it worked as I only installed with minimum hardware (video, ram, dvd, memory).

However, I did notice after booting into WinXP the device manager indicated several items with yellow exclamation marks next to them. I didn't write them down but as I recall there were about 4, one had "bridge" in it and another one may have had "smbus" and one with an "unknown device."

The good news is I manually installed the "nForce4_amd_6.70_winxp2k_english.exe" driver along with the "84.21_forceware_winxp2k_english_whql.exe" and all the exclamation marks disappeared.

At the end of your Driver-Integration-Method process you state; "Then you can integrate the other nForce drivers (SMBus, Ethernet etc.) as "normal drivers". Only users with an nForce4 system may take them out of the same NVIDIA chipset package they used for the integration of the SataRaid drivers."

Question, would the integration of these other nForce drivers eliminate the exclamation marks and the need for manual installation of the drivers?

If so, could you either list the directories and the proper nLite integration procedure, such as integrate drivers using the "multiple or single driver folder" option or possibly point me where I can find it?

I would guess one sub folder should include the \LAN\Ethernet but since some files were pulled from the Legacy and SATA_IDE subfolders (as stated in the procedure) I am not sure to include them?

Grateful for your help.

Fernando, this maybe slightly off topic, but when I'm using the Windows Unattended CD Creator to add the Intel iaStor storage driver, the program asks me to pick one. Does it matter? Because the $OEM$ file that is created shows all of them, and the WINNT.SIF just makes reference to the file name.

I ask this because I have 2 machines I want the install disk to be good for. Both machines would pull from the same storage file, but one is a ICH6R - 82801FR, and the other is a ICH7R/DH - 82801GR/GH.

nLite would pull them all in. You would just have to pick one. Does the Windows Unattended CD Creator work the same way?

Thanks again

Yes! You should integrate all needed nForce chipset drivers and - if you use a NVIDIA graphic adapter - the last WHQL-certified Forceware driver at once.
When you have unzipped the 6.70 chipset driver package, you have the following folders: AudioDrv, AudioUtl, Ethernet, IDE and SMBus. After having integrated the IDE\WinXP\LEGACY subfolder (or the SATARAID + extra files) as textmode, you should integrate the other nForce4 chipset drivers as PnP. Not the easiest, but the safest method to integrate the different chipset drivers is the "single driver" option. Just point nLite - one after the other - to the AudioDrv, Ethernet and SMBus folder and integrate in each case any (doesn't matter which) INF file of the different folders. If you have done it this way, you get automaticly all needed nForce4 chipset drivers installed by your nLited XP CD.
Additionally you should integrate the NVIDIA Forceware driver 84.21. Before you can do it, you have to unzip the EXE file by using WinRar or WinZip.
As I have written above, you should integrate the Ethernet folder to get the nVLAN drivers installed by using the nLited CD. Don't do any file or folder mixture! The sequence of my guide concerning the transfer of some files into the SATARAID subfolder instead of just taking the LEGACY subfolder is only for purists or people, who had problems with the easy LEGACY subfolder integration of the nForce SataRaid drivers.

The integration of TEXTMODE and PnP drivers is done in a similar way. The difference is the method to enforce the installation of not or not correctly digitally signed mass storage controller drivers. If you are using the CD Creator, all files of the driver subfolder are copied and usable for Windows setup (as with nLite), but additionally you have the possibility to enhance the installation of a critical textmode driver by flag him as "bad" controller driver. After having done this, the "bad" controller driver is something like "privileged" during the later OS install.

Fernando, the Windows Unattended CD Creator funtionally only "embedded" the one TEXTMODE storage driver that I selected, and, based on what you've said, that is probably the intent. Even though the $OEM$ file shows all the drivers, it only picks up the one at install time. To verify, I re-did it selecting the other TEXTMODE driver, and, sure enough, the 2nd disk worked like a charm on my other machine, but wouldn't work on the original.

Are you aware of any simple program (besides nLite that's having problems in this area right now) that will TEXTMODE embed all of the storage drivers?

If not, I'm assuming the the CD Creator modifies the TXTSETUP.SIF - I can see the one driver. Can I add another line under [SCSI] for the other specific driver?

Thanks again

Did you try to flag both TEXTMODE drivers as "bad" controller driver?
After the CD Creator has done its processing, but before you create the ISO image file, have a look into the WINNT.SIF of the CD Creator processing folder. You find a section which looks like this:

Within the last line you can see all INF files of the embedded OEMDIR drivers. If there is an INF file missing, you may try to add it, but precondition is, that
- all driver files (SYS, INF and DLL) have to be within the OEMDIR folder and
- the TEXTMODE drivers themselves have to be copied into the \i386 root.
The TXTSETUP.SIF entries are made by the CD Creator, when you have integrated them within the "driver integration" section.

Maybe you find something here: http://www.msfn.org/board/-f107.html

@PVU:
do you have the same floppy for both machines? or different floppies ?
Can you send the content of this floppy(floppies) to me?

I will test it with Creator.

Fernando and LG, this may not mean a thing, but until Fernando asked about flagging both TEXTMODE drivers, I was not aware that you could flag more than one. So, I just created a disk by flagging both Intel SATA drivers (in the Intel TXTSETUP.OEM: iaAHCI_ICH7R = "Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)", and iaAHCI_ICH6R = "Intel® 82801FR SATA AHCI Controller (Desktop ICH6R)") which are both contained within the latest Intel Matrix Storage Manager, IATA55.EXE. I thought it was very much like nLite where you could only flag one. My mistake.

Fernando, one thing is that when I have used the CD Creator in the past, not only did I not realize that you could flag more than one TEXTMODE driver, I also didn’t realize that you could choose “bad” for more force-fitting of a stubborn driver. Unlike the nVRaid drivers, I don’t think that these Intel drivers require a “bad” selection, because they’ve worked. Since I have only chosen one in the past, it seems to have imbedded just one without issue. I’m at work right now. When I go home, I will try the new 2-driver selected disk on the other computer to see if there’s a problem. My guess is that there won’t be – I should have selected more than one. I’ll post my results no matter what.

As far as the CD Creator and PnP drivers are concerned, have you had any issues? nLite also seemed to have a tough time with my Intel NIC driver, so I’ve gotten a little skittish about trying to do too much. Your program installed the Intel chipset INF drivers without a problem. It also installed my ATI video drivers perfectly.

If all I had to do is select more than one driver, this is the $OEM$ driver install program I was asking about. It really is a nice program. I like the way it asked me to get rid of the useless folders in my (HFSLIP) Win2K installation.

Many thanks

@PVU
If I understood correctly, you integrated both drivers, Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH) and Intel® 82801FR SATA AHCI Controller (Desktop ICH6R).

Did you mark both drivers as "BAD" ? I think in your case one driver is enough!
Which files are in $OEM$\$$\OEMDIR on CD now ?

What is this!?

Instead of contacting me when some driver doesn't work you promote some other tool on nLite forum.
What a nerve.

If someone is willing to test this Intel driver with upcoming nlite send me a PM.

I am not promoting some other tool on nLite forum, I am just helping an nLite forum member to solve his problems.
On the other hand you are right - this is not the best place to discuss details about another tool.

@ PVU:
If you want an further assistance with the use of the CD Creator, please post your problem within the Creator Board.

@ PVU:
This is a good chance to get your problem solved within the next nLite version. I encourage you to accept Nuhi's invitation.

nLite only enables for nvidia multiselection, I guess it should have it enabled for all, done for next.

nuhi, this (RC8i) must have done it, because on the initial install it picked up the Intel® 82801FR SATA AHCI Controller (Desktop ICH6R). I will load it on the Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH) machine when I go to work. I'm assuming it will work. If I run into a problem I'll let you know. But no news will be good news.

I don't need to do a full install right now, so I can't tell you about the Intel NIC drivers. But, if they had the same multi-selection issue, you should be in good shape there also. If it is still an issue, we'll see folks discuss it, I'm sure. I almost feel like formating this machine to see how it would all go - interested to see how the integration worked out for the NICs, and SigmaTel and SoundMAX audio drivers. For the Sigmatel drivers, I deleted the STHDA64.INF (64 bit files) before integration.

Many thanks for your work on this specific issue. It may not have made it easier to deal with the NVidia drivers, but it looks like it took care on the Intel storage drivers. You might be done with RC8.

@ Lou Jacob



I've read somewhere that XP cannot be installed on only a raidset.
I meant 2 drives configured as raid and no other drives (SATA/IDE) present.

Try the same setup but add one nonraid disk to the system.

Maybe that will work.

I don't know where you have read this, but this is nonsense.
The truth is quite the contrary: You may get problems, when you have one or more hdd's outside the Raid array.
That is the reason why I suggest to unplug such non-Raid hdd during the Windows Setup.

CU
Fernando

i have some problems with the slipstreamed WinXP

I used sataraid + extras in the driver 6.70 for the VOL WinXP w/SP2

When i used the slipstreamed CD to boot, i can see the installer copying the nVIDIA raid driver. However, when it comes to "Setup in starting Windows"(still in the text mode, before the "press F8 to agree" screen), a BSOD is shown


the contents is like this: (sorry, i cant remember the text exactly )



could you help me to figure out the problem?

I have tried the legacy and sataraid w/extra, they show the same BSOD

With no informations about your system (mainboard and nForce chipset, nVRaid Bios version, numbers and sort of hdd's) I have no idea how I could help you.
Please betray some details about your computer.

CU
Fernando

sorry~
here is my config:

Gigabyte K8NU-9 (NF4U)
A64 3000+
3GB DDRRam

7200.10 320GB * 2 (RAID1)
NVRAID BIOS is 4.84

WinXP VOL w/SP2 (from MSDN)
nForce 6.70

thanks~!

Your config looks good. The integration of the nForce SataRaid drivers off the 6.70 package should work.
Preconditions: no hardware issues and a "healthy" Raid array.
Further questions:
a ) Has your Raid array been correctly detected as 1 device at the begin of the install?
b ) Did you low level format both hdd's before creating the array?
c ) Is the boot sector of your Raid shown as device C:?
d ) Have you tried the XP installation by using F6/floppy (without nLite)?
e ) Are you sure, that your memory sticks are ok (Tip: Retry the install with just 1 stick)?
f ) Did you unplug all unneeded devices (USB sticks, card reader etc.) during the install?

Hi there

Firstly i am sorry if i am being a complete noob here and all this has probably been asked and explained before, but i have been trying to get my head around these SATA drivers for ages and have now found this software (nlite), but i still cant get it to work.

I have read thru the opening post of this thread and about the first 10 pages of this, but i'm sorry to say none of it is making sense to me.

I have managed to do the simple bits like slipstream SP2 and hotfixes into XP, but i just do not understand what you mean about copying these files into the SATARAID and PATARAID folders. I cannot find this OEM folder that is being talked about and really am at a complete loss. Also all the driver files you point us to are for nForce 4 board and mine is only nForce 3 (using 5.11 drivers)

System is
Shuttle (SN95G5 v3) yes i read that that also seems to cause a few problems needing 2 drivers !!
BIOS version 6.00PG (dated 14/10/2005, but i cannot find what version of RAID BIOS i have)
AMD 3700+ socket 939
2Gb RAM (crucial)
74Gb Raptor drive (single, so not using RAID, just the SATA port)
no floppy

If anyone could help me (with a complete idiots guide) i would be SO grateful

Many Thanks in advance

P.S. could anyone link me to a thread that explains how to intergrate the rest of the nVidia chipset drivers and the Graphics as well?

There is no cause for you to be irritated about this thread, because neither my guide (first post) nor all other posts of this thread are useful for you. Reason: You have a non-Raid system.
If you have read the first post of this thread, you must have seen this:

If you have troubles with the integration of the nForce SATA drivers, don't do it. Windows XP can be installed without any third party IDE drivers onto a non-Raid system.
Here is the guide you probably are searching for:
http://www.nliteos.com/guide/index.html

CU
Fernando

thanks for that

i have to say i am a little bit puzzled as when i had an ASUS AV8 board, even though i only had the one drive in it (in fact it was all the same internals that i have moved to my shuttle) it would not see the hard drive unless i did the F6 trick and loaded the RAID driver disk

I have just checked with XP disk and you are quite right that it does not need the boot disk to see the hard drive on my shuttle

Is this a glitch with VIA chipsets? (or is this the wrong place to ask this question )

That's really not the right place for this question, because I don't have any experience with VIA chipsets.

Hi all. I thought it was too good to be true! I can't seem to get my floppy drive to work (tried a new one but it looks like it might be the actual port on my Asus A8N-sli and Windows needs to be installed). So I have no choice but to get this slipstream thing working!

I've managed to install windows and gte it to detect my RAID array but at the final stages of loading the files needed for the installation, it says it can't find any of the RAID drivers and proceeds to list them all giving the option of quitting, ignoring or retry. I try ignoring and when the installation is finished it reboots every time at the same point.

I've tried using 6.53 and 6.70 but I am confused over a few things. In the initial guide and a few posts after the PATA folder is mentioned, in particular copying the nvatabus.sys from this folder into the SATA folder. I don't have a PATA folder????? I only have RAID tool. legacy, sata_ide and sataraid.

There are lots of identical files in the SATA_ide and SATA raid, should I be replacing some with others? All I know is that I followed the beginning guide to the letter and it hasn't worked for me, and I don't relish the task of going through 40+ pages! Am I doing something wrong or is there another method I can try?

If the XP setup cannot find the necessary nForce SataRaid drivers although you have integrated them by nLite, you have either a CD problem (not correctly burned CD / not correctly working CD drive) or you did not exactly what I have written in the first post of this thread. If the XP setup only misses some CAT files (NVATA.CAT and NVRAID.CAT), there is nothing to warry about if you skip the install of these files, because they are useless.
The LEGACY is nothing else as the former PATARAID subfolder. NVIDIA has just renamed this folder to LEGACY.
You won't get your problem fixed by a mixture of files of several IDE\WinXP subfolders.

Make sure, that
a ) your hardware is OK (RAM, PSU and cables),
b ) your mainboard BIOS contains an actual nVRaid BIOS (v. 4.84 or higher),
c ) you have integrated the content of the IDE\WinXP\LEGACY subfolder of the 6.70 chipset driver package as TEXTMODE and have chosen both required drivers.
Then burn a new bootable XP CD with lower speed (8x or 16x) and retry the installation.

hello~

i finally can solve my problem simply using the latest unofficial 9.16 WHQL driver

link:
http://www.station-drivers.com/page/nvidia%20nforce.htm

thanks very much

That is very interesting for all of us, because the chipset driver package 9.16 is designed for nForce5 and nForce430_410 chipsets.
How did you manage the integration? Which IDE\WinXP subfolder and which files did you integrate?

-- I realize that this is probably not the correct place to post this information, so please forgive me in advance. --

I am trying to install the nvRaid drivers using nLite, but nLite is crashing my windows install.

I have:

Asus A8N-SLI Deluxe
BIOS 1016
nvRaid 4.84
Windows XP Pro SP2 and patches up to May 06
nForce 6.70

I tried for over 8 hours using every method described in post 1 (Legacy, combo sataraid splicing); nothing worked. At this point, I decded to try using just the chipset drivers to test if it was nLite causing the problem. Guess what, it is.

Here is what happens:

Windows boots to txtsetup. When it reaches the point of 'Loading Windows Executive', it halts to a screen that reads "Setup could not determine what type of computer you have..." with the only option in the middle as 'Other'. When you press Enter and select this, the following screen says: "The file txtsetup.oem could not be found..."

Any ideas?

Just a stab in the dark: did you change the nLite entry concerning the type of computer (you know single processor, Advanced Power Management Interface, et al)? I scrolled too far by mistake once without noticing, and it took me forever to discover the error, but I seem to remember it causing an setup failure in the same ballpark as yours.

Also what mode did you answer the drivers as being?

The only thing I added was drivers, so I didn't even get to the selection screen you mention.

I installed the RAID as txt and the others as PnP.

I am working on a fresh CD using RC8 of nLite to see if I can fix the problem this way. I will let you know how it goes.

**EDIT** It looks like the 'make from scratch' method works. I recommend this to anyone who thinks their Windows CD is good. Just do it again, only takes about an hour and you will be happy with the first result instead of spending enldess hours pulling your hair out.

Good simple point. Don't keep messing with likely broken or otherwise corrupt base files.

All this talk of RAID is a bit confusing. Which folder / files do I need if I'm not using a RAID array (ie. just 1 single SATAII in the appropriate nvidia port).

Motherboard, Asus A8n Premium, nForce 4 (6.70) (XPO Home)

If I had to guess I would use:

IDE\WinXP\legacy\nvatabus, and

IDE\WinXP\sata_ide\nvata

Would this be correct or do I need to install the Raid files regardless of whether i'm using a Raid array (as explained at the top of the thread)

As an afterthought I have my raid devices disabled in BIOS, will I need to enable them for the nvidia drivers to install. Ive had problems in the past with installing the nvidia drivers through the exe... yes I am a bit thick!

many thanks


Somebody help me plaese I can'nt do it!

As you have no Raid, this thread and the guide for the nForce SataRaid driver integration is not useful for you.
Normally non-Raid nForce Sata systems don't need any third party drivers at all for the proper install of Windows XP. You can check this by booting off the original XP CD without hitting F6. If your Sata hdd is detected, you don't need a special nForce driver for the installation.
If you want to integrate the nForce IDE drivers (S-ATA and P-ATA) into a bootable XP CD, you should integrate the SATA_IDE subfolder of the 6.70 driver package as PnP driver.
There are some Asus boards, where the Raid ports have to be enabled within BIOS even when no Raidarray is built. So you have to check this in the user's manual of your mobo.

The ASUS point is important: and, if I'm not mistaken, there's some that require you to have SATA enabled in the BIOS even if there are no SATA drives (I'm almost sure this was the case on recent board I worked on--which, after pulling my hair out, turned out to be a simple, but non-intuitive, BIOS setting)... User beware!

This is not accurate information in regards to A8N-SLI Deluxe on BIOS 1016. nvraid does NOT need to be enabled if you are merely running SATA drives in a normal fashion. If you want to run a RAID array, then you need to a) enable the nvraid and enable the channels you want the RAID configured on.

Sincere thanks for the advice folks!

Good news for users, who always want the newest drivers:

NVIDIA has published a new nForce chipset driver package v. 9.34. Although this package is mainly designed for the future nForce5 chipsets, it is also usable for nForce4 chipsets.
For the integration of the nForce SataRaid drivers I do not recommend to take the "normal" 9.34 package, but the one laying here: ftp://download.nvidia.com/Windows/vista/beta2/
The SataRaid drivers off the 32-bit package are designed for Vista Beta2, but very good usable for XP too. Important is the presence of a full compatible LEGACY subfolder with all necessary files.
I have added these drivers into my guide (first post of this thread).

CU
Fernando

Fernando, I have a problem with stop code 7B but I have no problem installing windows server 2003 using the 6.69 drivers as is during F6. Are those instructions outdated? (doubt due to amount of repies). I have an ASUS A8N5X with nForce 4 and RAID.

I'll tell you my issue with 7B. I have a W2K3 server running on another hardware that I moved using Symantec Livestate Recovery advanced server 6.0 suite using a recover anyware option that allows to recover to dissimilar hardware. Actually, it does not work for me. Here is what I have seen:

If I use the Symantec tool I get a BSOD with 7B stop code upon reboot
If I run a repair using W2K3 SP1 slipstreamed bootable CD(lets call it CD1) without using the method described in this thread I still get the STOP code 7B upon reboot (this could be due to the cause explained in this thread)
If I run a repair using W2K3 SP1 slipstreamed bootable CD(lets call it CD2) using the method described in this thread I STILLget the STOP code 7B upon reboot.

Now, if I use CD1 and do a fresh install of W2K3 on the raid disk, all is OK and I don't get the STOP code.

Why is this happeing?
Why don't I get 7B stop code using CD1
What could I do to make W2K3 work (if you know)?

Thanks a million

Correction: My hardware builder said this was not ASUS, but a peculiarity in a MSI board because of a faulty BIOS--flashing fixed it.

If you have integrated the nForce SataRaid drivers into your W2k3 CD, you should not hit the F6 button! If you do it nevertheless, you may get a BSOD with a 7B stop message.

I did not hit F6 when using the integrated CD1 or CD2. Fernando, do you have any idean on the 3 questions in my last post?


Actually what I was trying to say is: when doing a fresh install using a regular windows 2003 CD and the 6.69 drivers through F6, I do not get the stop code 7B

1. Do you have a P-ATA or a S-ATA Raid?
2. The content of which driver subfolder or which sort of mixture did you put onto the floppy for F6?

S-ATA Raid is what I have