[crazyal12]

It wont let me integrate the sata_ide driver as a textmode driver, only a pnp driver (no option box comes up).

this is for nforce 430.

What should I do?

Thanks,

[Fernando 1]

@ crayzal12:
Welcome at MSFN Forums!

You are not able to integrate the SATA_IDE folder content as TEXTMODE driver, because it doesn't have a TXTSETUP.OEM file.
Since you neither have a LEGACY mode nForce chipset nor an AHCI capable hardware configuration, there is no need to integrate any nForce SATA_IDE driver folder.

Questions:
1. Why do you want to integrate the SATA_IDE driver at all?
2. Which SATA mode are you running (IDE or RAID)?
3. Which driver version did you take?
4. Have you tried to get Windows XP with integrated SP2 or SP3 installed without having integrated or loaded any nForce SATA driver?

Regards
Fernando

[crazyal12]

Fernando 1, on 20 July 2011 - 01:29 AM, said:

@ crayzal12:
Welcome at MSFN Forums!

You are not able to integrate the SATA_IDE folder content as TEXTMODE driver, because it doesn't have a TXTSETUP.OEM file.
Since you neither have a LEGACY mode nForce chipset nor an AHCI capable hardware configuration, there is no need to integrate any nForce SATA_IDE driver folder.

Questions:
1. Why do you want to integrate the SATA_IDE driver at all?
2. Which SATA mode are you running (IDE or RAID)?
3. Which driver version did you take?
4. Have you tried to get Windows XP with integrated SP2 or SP3 installed without having integrated or loaded any nForce SATA driver?

Regards
Fernando

Thanks,

1. Because the Windows XP SP2 disc will not recognise the SATA hard drive. (Hard drive works fine).
2. I am not sure, it is a laptop which gives no options in the BIOS to change SATA mode.
3. One from the nvidia website as I have no idea which one of yours to download.
4. The disc is a Windows XP SP2 disc, the problem is that it does not give me an option to do text mode in nlite.

BTW this is a compaq F500 laptop.

Thanks.

[Fernando 1]

crazyal12, on 20 July 2011 - 01:37 AM, said:

1. Because the Windows XP SP2 disc will not recognise the SATA hard drive. (Hard drive works fine).

Since the SATA Controllers of nForce 430 chipset systems do not support the "AHCI" mode, I suspect, that they have been set to "RAID" mode by default.

Quote

2. I am not sure, it is a laptop which gives no options in the BIOS to change SATA mode.

Are you sure about that?
Enter the BIOS and look for the "SATA Operations" settings. If you find them, choose "Raid Autodetect/ATA". After having done that, you should be able to get XP SP2 installed without having integrated or loaded any third party SATA driver.

Quote

3. One from the nvidia website as I have no idea which one of yours to download.

If you should not be able to change the SATA settings within the BIOS, I recommend to integrate just the SATARAID folder content of my nForce IDE driver package v9.99.09. That should work for your current RAID mode system.

Quote

4. The disc is a Windows XP SP2 disc, the problem is that it does not give me an option to do text mode in nlite.

As I already have written you have integrated the wrong driver folder (SATA_IDE instead of SATARAID)). The SATA Controllers of your HP notebook obviously have been set to RAID mode.by default.

Regards
Fernando

[DBF68]

I apologize if I'm posting this request for help in the wrong place. Since my problem seems to be a Fernando Specialty, this seemed to be the appropriate place to post. Let me know if I should have posted elsewhere.

Maybe I’m going about this OS build and install the wrong way. For some background info, I’ve been building PCs since 1996. So, I know my way around a computer. As for OS knowledge, I’m familiar with Windows beyond the basic user level, i.e. point and click. Even so, I’m really stumped as to why I’m having a problem getting nLite to work properly. It’s been a serious week of hell.

Attached is the Last Session file.

Let me know if you want the TXTSETUP.SIF too.


Problem: Nvidia SATA AHCI & RAID drivers will not load during OS textmode install

• Getting BSOD associated with OS install program not being able to find either nLite provided SATA AHCI or RAID drivers
• STOP 0x0000007B (0xFFFFFADF90A323C0, 0Xffffffffc0000034, 0x 16 0’s, 0x 16 0’s)


Using nLite 1.4.9.1 - Last build as of 2008.09.11

• OS build being saved on root of K: drive as file name WXPPx64_SP2_nLite.iso

Instead of using a CD-RW disc, I’m trying to install the ISO with my flash drive loaded only with manufacturer provided software. Why am I trying to use a flash drive? Well, of the five seldom used Memorex CD-RW discs I have, three separate ISO burn programs have found read errors on all five discs. So, rather than messing with old fashioned junk CD-RW media again, I thought I’d try using a bootable flash drive. Even so, maybe I’m doing something wrong.

• Flash Voyager 4GB USB Flash Drive SKU# CMFUSB2.0-4GB
• Formatted with Corsair provided “Ultimate Bootable USB Flash Drive” software
• http://blog.corsair.com/?p=2619
o GRUB4DOS 2004-2009
o Syslinux 1994-2009
o Memtest86+ 2009
o FreeDOS
 COPYING
 fdboot.img
 grub.exe
 memtest86+-4.10.iso
 menu.lst
 pmagic-6.6.iso
 Readme.txt
 syslinux.cfg


Computer System Info:

Operating System: Microsoft Windows XP Pro x64
• SP2 and all hotfixes up to date
• Dual-boot system along with WXPP x32

Motherboard: ASUS M3N-HT
• BIOS 2904 12-7-2009 (Most current - 3401 2011.04.29)
• MediaShield 10.x.x
• MCP = Northbridge & Southbridge in one 780a chip
• Using Nvidia 780a 15.57-nforce-novideodriver-winxp-64bit-international-whql drivers - 2011.05.02
• WinXP 64-bit nForce UDA driver package for C51M/MCP51, C55/MCP51, C72, C73, MCP77, and MCP79
o Ethernet Driver (v73.30) WHQL
o Network Management Tools (v73.25) "Sedona"
o SATAIDE Driver (v11.1.0.43) WHQL
o SATARAID Driver (v11.1.0.43) WHQL
o RAIDTOOL Application (v11.1.0.43) WHQL
o SMBUS Driver (v4.79) WHQL
o SMU Driver (v2.08) WHQL
o Installer (v8.36)

Hard Drives: 2 Seagate Barracuda 7200.10 160GB drives in individual RAID Stripe Configuration per drive, not as RAID-0
2 Western Digital 120 GB & 160 GB drives set up as a RAID-1 mirrored array for backup and storage

Processor: AMD Phenom II X3 720 Black Edition Heka 2.8 GHz (Not OC’ed)

Memory: 4GB of OCZ Platinum DDR2 1066 DC (5 5 5 15 20 2T) (Not OC’ed)

Video: MSI N460GTX CYCLONE 1GD5/OC GeForce GTX 460 (Fermi) 1GB 256-bit GDDR5 PCI Express 2.0 x16 (Not OC’ed)

Audio: SB X-Fi XtremeGamer Fatal1ty Pro

Network Adapter: Intel Gigabit CT Desktop Adapter


USB flash drive install methods tried without success

• Read more than one version of nLite user instructions/manuals.
• Clicked on each nLite help icon to read information concerning that program page OS build step.
• Downloaded and tried using CDImage.exe for ISO building instead of using default Mkisofs.exe program.
• Tried building ISO image with ImgBurn and vaguely remember same BSOD or Grub4DOS saying invalid image.

• Prior to trying any new nForce drivers, deleted old nLite OS build and created a new one.
• Tried older Nvidia nForce Driver Version 15.24 (15.25 “no video driver included” set).
• Tried older Asus Nvidia NVIDIAnForceMCP72_Chipsetpackage_V1808_XP drivers.
• Moved Nvidia nForce drivers to root of K: drive in case nLite had a problem with long folder path.
o H:\Drivers-Progs-Updates\Drivers\Nvidia\nForce\15.57-nforce-novideodriver-winxp-64bit-international-whql
• Created an nForce driver only build sans SP2 integration and PE tweaking.

• Searched nLite forum and Fernando’s post for similar problems to find solutions.
• Read Fernando’s Nvidia SATA/RAID driver post and followed the quick instructions.
• Read the long detailed info in Fernando’s Nvidia SATA/RAID driver post to see if I missed anything.
• Downloaded and tried Nvidia SATA/RAID drivers Fernando provided via Mediafire.
o 64bit nForce SATARAID drivers v11.1.0.43 WHQL for XPx64

• Used Comodo Internet Security to scan nLite OS folder build ARMPXOEM_EN_WXPP_x64_Disc.
• Set the Comodo Internet Security settings for AV and Defense to disabled.
• Uninstalled Comodo Internet Security program entirely.

• Have tried to create a service pack free barebones build with just Nvidia nForce drivers.
• Removed old SCSI support drivers in Component screen as nLite help recommended.

• Tried to create a WXPP x64 nLite build on the dual-boot WXPP x32 OS.
• Could only create an nForce driver build sans SP2 slipstream because WXPP SP2 x64 is 64-bit.
• Created an nForce driver only build sans PE tweaking.

• Tried installing nLite OS builds with all drives powered and using RAID controller.
• Tried installing nLite OS builds with only the 2 stripped Seagate drives powered and using RAID controller.
o nForce RAID drivers rolled into nLite OS build
• Tried installing nLite OS builds with only 2 Seagate drives powered and using AHCI controller.
o nForce AHCI drivers rolled into nLite OS build

• Oddly enough, a WinSetup-1-0-beta7 flash drive install of an nLite WXPP x64 build works without a BSOD.
o Drawback: 7700+ files from the ARMPXOEM_EN_WXPP_x64_Disc folder are slowly loaded to flash drive.
o If nLite ISOs won’t work, would love to find a way to make a WinSetup-1-0-beta7 compatible ISO.

Since it's been a whole week that I've been working on this problem, I might have forgotten some other things I've tried too.

What else might I try to get things to work?

Thanks.

Attached File(s)

•  Last Session (2011.09.03-03.48.34).ini (8.54K)
  Number of downloads: 4

[cdob]

DBF68, on 05 September 2011 - 07:14 PM, said:

I apologize if I'm posting this request for help in the wrong place.

There is a Install Windows from USB section too. http://www.msfn.org/...ndows-from-usb/

Quote

I’m trying to install the ISO with my flash drive loaded only with manufacturer provided software.
Flash Voyager 4GB USB Flash Drive SKU# CMFUSB2.0-4GB

BSOD 0x7B refers to boot drive too. That's the USB Flash Drive.

Do you like to copy a ISO file to USB Flash Drive?
OS manufacturer provided software dosn't support this. There is no default ISO file driver.
This task is impossible to solve.

Contrary there are third party open source ISO file driver.
And some Flash firmware can simulate a USB CD-ROM drive.
Read the above link.

Quote

Oddly enough, a WinSetup-1-0-beta7 flash drive install of an nLite WXPP x64 build works without a BSOD.
Drawback: 7700+ files from the ARMPXOEM_EN_WXPP_x64_Disc folder are slowly loaded to flash drive.

OS manufacturer provided software does find single files at a USB Flash Drive.
That's possible within OS manufacturer provided software.

This post has been edited by cdob: 05 September 2011 - 10:25 PM

[DBF68]

cdob, on 05 September 2011 - 10:09 PM, said:

DBF68, on 05 September 2011 - 07:14 PM, said:

I apologize if I'm posting this request for help in the wrong place.

There is a Install Windows from USB section too. http://www.msfn.org/...ndows-from-usb/

I saw that section prior to posting here and looked at it a little. Rather than take off in some other direction for another week of frustration, I thought I'd start asking questions here. Still, I'll take a look at that section too. It seems some people have had success.

cdob said:

DBF68 said:

I’m trying to install the ISO with my flash drive loaded only with manufacturer provided software.
Flash Voyager 4GB USB Flash Drive SKU# CMFUSB2.0-4GB

BSOD 0x7B refers to boot drive too. That's the USB Flash Drive.

After the fact, I wondered if those BSODs might have been due to going through the USB subsystem vs. the controller subsystem. So, it made sense that I'd be getting those BSOD. Although, I got the impression that if the bootable USB software provided by my flash drive maker could load ISOs, and nLite could pack up current SATA drivers into the ISO, then the install program should have found them, installed them, and let me be on my way. Since the setup program installed USB drivers, I didn't think I'd have a problem with USB or SATA driver detection. Even so, I guess there's more to the process than I realize.

cdob said:

Do you like to copy a ISO file to USB Flash Drive?
OS manufacturer provided software dosn't support this. There is no default ISO file driver.
This task is impossible to solve.

Contrary there are third party open source ISO file driver.
And some Flash firmware can simulate a USB CD-ROM drive.
Read the above link.

I thought I'd give it a try since there are implications other people have got it to work for them. From what I've read, some people have even been able to re-purpose the Windows 7 USB DVD Download Tool for XP installs. Although, it doesn't always work. There's something about making sure the ISO image is 9660 and UDF compliant that's worked for some people, but I didn't have any luck.

cdob said:

DBF68 said:

Oddly enough, a WinSetup-1-0-beta7 flash drive install of an nLite WXPP x64 build works without a BSOD.
Drawback: 7700+ files from the ARMPXOEM_EN_WXPP_x64_Disc folder are slowly loaded to flash drive.

OS manufacturer provided software does find single files at a USB Flash Drive.
That's possible within OS manufacturer provided software.

Maybe the USB install forum has the answers. Worst case scenario, I'll just rely on WinSetup. Worst-Worst case scenario, I'll go buy another 5-pack of CD-RW media, but a better brand.

Usually, I create an OS build by installing service packs and hotfixes, drivers, software, tweak everything, and then create an image of the OS for storage. Then, if I need to blow out an OS install, I just backup my critical files, and use the Acronis software to install the fresh image. After going through all this rigmarole of trying to create a custom image with nLite and install the ISO via USB drive, I might just go back to the tried and true method.

This post has been edited by DBF68: 06 September 2011 - 07:17 AM

[Fernando 1]

@ SwissReplicaWatches:
Welcome at MSFN Forums!

Quote

I have tried this with the SATA drivers from Nvidia Release 6.53, it worked , Motherboard is an A8N-Sli Deluxe. just needed to change nvatabus.inf to nvraid.inf and it worked without a hitch

Is this an answer to any question/ask for help or just an information for users with an nForce4 RAID system?
Please explain what you have done:
1. Which nForce IDE driver subfolder (SATA_IDE or SATARAID) did you integrate?
2. What means, that you changed nvatabus.inf to nvraid.inf? Did you replace the nvatabus.inf by the nvraid.inf one or did you just rename it?

Regards
Fernando

[topcat989]

Fernando 1, on 19 September 2011 - 11:56 AM, said:

@ SwissReplicaWatches:
Welcome at MSFN Forums!

Quote

I have tried this with the SATA drivers from Nvidia Release 6.53, it worked , Motherboard is an A8N-Sli Deluxe. just needed to change nvatabus.inf to nvraid.inf and it worked without a hitch

Is this an answer to any question/ask for help or just an information for users with an nForce4 RAID system?
Please explain what you have done:
1. Which nForce IDE driver subfolder (SATA_IDE or SATARAID) did you integrate?
2. What means, that you changed nvatabus.inf to nvraid.inf? Did you replace the nvatabus.inf by the nvraid.inf one or did you just rename it?

Regards
Fernando

I'd like to know as well, I have an A8n32-SLI Deluxe mobo as well.

[FBratwurst]

Hi there,

I've been looking quit a while on this topic for a solution for my similar problem. I can't get my new SSD working with AHCI enabled on my nForce mobo. In IDE mode everything works fine, but I really want to get it working with AHCI. Hopefully you can help me. As far as I read on this topic I do believe in the expertise of Fernando. The things I've read so far has only to do with Windows XP while I'm using Windows 7. Please help!

Further specs of my system:
OS: Windows 7 x64
Mobo: M3N-HT Deluxe (nForce 780a SLI)
SSD: OCZ Vertex 3 (firmware 2.15)
HDD: Samsung Spinpoint 103SJ
MEM: 4GB Kingston 1066Mhz
VGA: Onboard (external just died, looking for a new one)
DVD-RAM: LG or something.
FLOPPY: nope, but I do have a bootable USB

What I've tried:
After 2 months working on Windows 7 x64 on IDE mode I decided I wanted to change to AHCI mode. Tried the register tweak (change .../msahci/start value from 3 to 0), reboot, change IDE to AHCI in BIOS. Results in endless reboot at the point of loading Windows. After that I tried to reinstall directly on AHCI mode. Same results. Tried other SATA ports on my mobo. Didn't work as well. Again installed on IDE mode and searched for ours and ours to a solution. Nothing comes close as this topic but I'm quit dizzy right now of all the research.

I put all my trust in you guys. Thanks in advance!

FBratwurst

By the way: it's not an issue for me to reinstall.

This post has been edited by FBratwurst: 02 November 2011 - 03:24 PM

[Fernando 1]

@ FBratwurst:
Welcome to the nLite Forum as part of the MSFN Forum!

Your problem has nothing to do with nLite and nothing to do with the topic of this thread.
If you want to get help, you should post your issues within a Forum, which is supporting nForce storage driver problems. The nForcersHQ Forum (>LINK< or the NVIDIA Forums (>LINK<) may be a better address.

Usually it is no problem to get Windows 7 installed onto a hdd or SSD after having set the SATA Controllers to AHCI mode, because the OS has a generic MS AHCI driver in the box, which should be able to detect and manage all nForce AHCI systems. If the installation should fail nevertheless, you should ask the NVIDIA support for a suitable nForce AHCI driver, which definitively works with your nForce 780a Southbridge. I doubt, that there is any official nForce SATA driver available for the DeviceID DEV_07B5.

Regards
Fernando

[DBF68]

FBratwurst, on 02 November 2011 - 03:16 PM, said:

Hi there,

I've been looking quit a while on this topic for a solution for my similar problem. I can't get my new SSD working with AHCI enabled on my nForce mobo. In IDE mode everything works fine, but I really want to get it working with AHCI. Hopefully you can help me. As far as I read on this topic I do believe in the expertise of Fernando. The things I've read so far has only to do with Windows XP while I'm using Windows 7. Please help!

Further specs of my system:
OS: Windows 7 x64
Mobo: M3N-HT Deluxe (nForce 780a SLI)
SSD: OCZ Vertex 3 (firmware 2.15)
HDD: Samsung Spinpoint 103SJ
MEM: 4GB Kingston 1066Mhz
VGA: Onboard (external just died, looking for a new one)
DVD-RAM: LG or something.
FLOPPY: nope, but I do have a bootable USB

What I've tried:

After 2 months working on Windows 7 x64 on IDE mode I decided I wanted to change to AHCI mode. Tried the register tweak (change .../msahci/start value from 3 to 0), reboot, change IDE to AHCI in BIOS. Results in endless reboot at the point of loading Windows. After that I tried to reinstall directly on AHCI mode. Same results. Tried other SATA ports on my mobo. Didn't work as well. Again installed on IDE mode and searched for ours and ours to a solution. Nothing comes close as this topic but I'm quit dizzy right now of all the research.

I put all my trust in you guys. Thanks in advance!

FBratwurst

By the way: it's not an issue for me to reinstall.

Hi FBratwurst,

I feel your pain with troubleshooting oddball things. Although, as Fernando stated, it seems like you're having a non-nLite related problem, but posted in the nLite Nvidia driver related forum. I'm not familar with SSD drives other than they are exceedingly fast. Although, I've gotten the impression from some readings that they have nuances that need to be considered prior to just popping them in the case and installing an OS on them. Then gain, I could be wrong on that point.

I'm sort of surprised that you're having problems getting W7 installed on the SSD drive with the mobo in AHCI mode. When I tried the W7 trial release, I didn't have any problems installing on a primary partition on my SATA drive connected to my 780a chipset mobo while in AHCI mode. Granted, I'm comparing apples to oranges to some extent between storage device types. Although, the 780a chipset can be a PITA. Some design limitations were imposed on its users when it comes to switching between AHCI and RAID mode.

With the 590 chipset, installing a WXPP (Windows XP Pro) OS was a piece of cake, regardless of what mode you used. The reason why it was easy is because there were dedicated AHCI/IDE, RAID/IDE, and IDE modes. So, WXPP automatically detected the AHCI or RAID controller and asked for the drivers. Because you were in this kind of 50/50 controller mode, it didn't just BSOD all over you due to a driver finding problem.

With the 780a chipset, it's all or nothing when it comes to choosing a controller option. There's only AHCI, RAID, or IDE mode. The IDE mode is kind of an all purpose failsafe mode that (should) work all the time because of the generic IDE drivers included with WXPP. Where you get into a problem is having to choose either AHCI or RAID during the OS WXPP install process (F6). You can only choose one controller mode, install the drivers, and your choice is set in stone unless you want to blow out your OS and create a RAID controller build.

Even though I got pretty familiar with nLite to the point I believe I was doing everything correctly, it did not do a good enough job of rolling in the compatible 780a AHCI and RAID drivers into the final slipstreamed ISO file. What I expected was for it to pack in those drivers and make registry modifications or notations "somewhere" so the installing OS knew it had access to both AHCI and RAID drivers if I chose to switch between controllers. Well, nLite never did what it should have done in that regard. If I switched between controllers, I'd get a BSOD based on what drivers the OS couldn't find, but had access to in the Windows folder. So, I was forced to rely on my old tried and true method for getting dual AHCI and RAID driver access within WXPP.

My tried and true method does depend on having at least one PATA drive. From that point, I install a raw uncustomized nor updated WXPP copy on a primary partition while in IDE mode. Once that process is done, I reboot and go through the process of enabling the AHCI controller in the mobo BIOS, have WXPP detect it, and then install the AHCI drivers. Then, I just repeat the process for the RAID controller until I have a raw WXPP copy on the PATA drive that has both driver sets installed. Afterwards, I use my Segate provided copy of Acronis True Image to copy that OS image to a SATA drive primary partition while in either AHCI or RAID mode. Then, I boot to that SATA primary partition and continue my OS build process until I've got something I want to image and put on the storage drive for safe keeping. This is sort of a PITA rigamarole process, but it's the best method I've found to work.

Anyway, this info probably won't help you with your particular problem, but if sparks an idea for a breakthrough or helps someone else with a 780a chipset, great.

Good luck on your efforts.

P.S. Make sure you've got the most recent BIOS version from your mobo manufacturer installed. Since W7 walks you through the process of choosing a hard drive, formatting it, and then creating a primary partition on the soon to be OS system drive, I'm assuming you've gone through that process without any success. The only other thing I suggest like Fernando suggested is to check out the Nvidia 780a mobo chipset forums and the forums related to your mobo on the manufacturer's website.

This post has been edited by DBF68: 03 November 2011 - 04:20 AM

[Fernando 1]

@ DBF68:
Thanks for your post, which may encourage FBratwurst to continue his efforts to get any Windows OS installed onto his nForce 780a chipset system after having set the NVIDIA nForce SATA Controllers to AHCI mode..
I disagree with you regarding the simultaneous integration of AHCI and RAID drivers. That doesn't make sense and reduces the chance to succeed with the OS installation.

@ FBratwurst:
The statement of DBF68 verifies, that it is possible to get Win7 installed onto an nForce 780a chipset system running in AHCI mode without the necessity to load or integrate any special AHCI driver.
This is what I suggest for you:
1. Set the nForce SATA Controllers to AHCI mode.
2. Unplug the power cable of your hdd and make sure, that your SSD is connected with port0 of your mainboard.
3. Boot off the Win7 media (DVD or USB) and try to get Win7 installed onto your SSD.
If the Win7 Setup should not detect your SSD, retry the Win7 installation onto your hdd. This is just a test to find out the reason for the failure with the SSD.

Regards
Fernando

[DBF68]

Fernando 1, on 03 November 2011 - 03:47 AM, said:

@ DBF68:
...
I disagree with you regarding the simultaneous integration of AHCI and RAID drivers. That doesn't make sense and reduces the chance to succeed with the OS installation.

Well, WXPP isn't going to install an AHCI driver when you have the RAID controller enabled any more than it's going to install a RAID driver when the AHCI controller enabled. You know far better than I do that the OS install routine is going to be looking for parameters that verify whether or not a set of drivers is compatible with the enabled hardware. So, by its design nature, WXPP is going to install the right drivers or give you a BSOD. Short of trying to give the OS install routine a file that says a set of drivers you're trying to feed it are something they're not, you usually don't have to worry about the OS getting confused.

Based on how nLite operates, from my pov, it seems to imply it's going to retrieve, incorporate, and make availabe all compatible drive controller drivers for your mobo. For instance, it has the ability to allow you to point it at a folder containing a drive controller driver package. When it scanned a folder for compatible 780a controller drivers, it came up with a list containing "both" AHCI and RAID drivers and associated files. Afterwards, nLite didn't pop up a message that said, "I'm going to roll both of these driver sets into the ISO, but the OS install routine will only be aware of one driver set based on what driver controller you've selected in your mobo BIOS.". Instead, it rolled both driver sets into a folder contained in the Windows folder and didn't let the OS install routine know it had access to both sets of drivers. In hindsight, I probably should be saying that it should be leaving some notation for the installed OS that the other set of drivers are available in a folder in the Windows folder.

Why bother rolling both drive controller drivers into the ISO if you're only going to allow the Windows install routine to be aware that there's only one that works based on the user's drive controller selection? It seems like a wasted effort. The WXPP install routine has its cache of drivers it goes through during the text mode phase to check for compatible drivers via process of elimination. It doesn't get hung up on the fact that there are a lot of drivers rolled into it that aren't compatible with the system where it's trying to be installed. So, it would make sense for nLite to make the text mode OS install process aware that it had both AHCI and RAID drivers available.

The primary reason why nLite's driver roll-up efforts seem odd to me is because it restricts any future hard drive controller choice. Say for instance a person using AHCI mode wants to use the RAID controller to create a RAID-1 mirrored array for storage and backup purposes. Well, that scenario would be possible if nLite made some kind of notation for the Windows install routine so it knew it has access to both AHCI and RAID drivers in the Windows folder. Unfortunately, this is not the way nLite works, and blowing out the old OS is the only real option. Again, it just seems like a wasted effort to role up both sets of drivers into the ISO if you're not going to have the future option to use both of them.

Sorry for the long ramble.

-------

As for your other suggestion to FBratwurst, that's an excellent idea. As I was reading your suggestion, I was reminded of the annoying backwards hierarchy of importance that both WXPP and W7 give to older hard drive technology. For instance, when doing a new OS build, I have to remind myself to unplug the power plug to any older PATA drive technolgoy drives first. Otherwise, the WXPP install process will detect the PATA drives and give them install priority over the newer SATA technology hard drives. W7 does the same dumb thing, i.e. it'll give install priority to PATA drives before SATA drives. So, maybe that's part of FBratwurst's problem. In his case, it'd give the Samsung SATA drive install priority over the OCZ Vertex 3 SSD.

This post has been edited by DBF68: 03 November 2011 - 05:57 AM

[Fernando 1]

@ DBF68:
You are right regarding the ability of Windows XP to take just the suitable drivers and to avoid the wrong ones, but this is only valid for PnP drivers, which are installed after the first reboot, that means during the second (GUIMODE) part of the OS installation, when the detailed hardware detection and PnP driver installation takes place. XP users will never get a BSOD, if they have integrated absolutely unusual or corrupted PnP drivers, not even with a wrong architecture (mixing 32/64bit drivers).
Things are totally different with the AHCI and RAID drivers, which have to be used by the OS Setup already during the first=TEXTMODE part of the installation. The OS does not know by its own the AHCI/RAID Controller details of the system and has no idea regarding the appropriate textmode driver(s), which are present within the i386 resp. amd64 directory of the OS image. That is why the XP Setup presents a textmode driver Pop-Up window and the user has to decide, which of the available AHCI or RAID Controllers (and the related driver) should be chosen (installed) by the OS. Any wrong textmode driver may induce a BSOD.

Quote

The primary reason why nLite's driver roll-up efforts seem odd to me is because it restricts any future hard drive controller choice. Say for instance a person using AHCI mode wants to use the RAID controller to create a RAID-1 mirrored array for storage and backup purposes. Well, that scenario would be possible if nLite made some kind of notation for the Windows install routine so it knew it has access to both AHCI and RAID drivers in the Windows folder. Unfortunately, this is not the way nLite works, and blowing out the old OS is the only real option. Again, it just seems like a wasted effort to role up both sets of drivers into the ISO if you're not going to have the future option to use both of them.

That is not correct. nLite allows you to integrate as many AHCI and RAID drivers as you want into the same XP image and you can highlight all listed AHCI and RAID Controllers, when you get the textmode driver pop-up window during the XP installation, but usually this will end with a BSOD, which is OS and not nLite related.

[FBratwurst]

Thanks for quick responding. And sorry for posting in the wrong topic, but still thanks. It helped me out in some way. Yesterday I did all the things that Fernando suggested. No satisfying results... But this is what I found out (sorry for my bad English)

Installing windows 7 on the SSD didn't worked in AHCI mode. But it did work on a normal HDD in AHCI mode. Therefore I used an old HDD from a broken laptop. So I do have a working OS in the house When I tried to install WIN 7 x64 on the SSD in AHCI mode it goes untill after the first restart while installing. I see the Windows logo and it won't go through that point. I unplugged al other devices except for the DVD ROM. After a couple hopeless restarts I switched back to IDE mode in the BIOS and then the installation of Windows continued normal. So I guess there is a problem with the combination of AHCI and the Vertex 3 on my mobo.

But that's not everything. Between al this problems I struggled (and still struggling) with the BIOS that won't detect my SSD at all times. I have to shut down power, remove the battery of my mobo and then restart. Only then the BIOS detects the SSD. This is some problem I had a couple of months ago with an earlier Vertex 3, wich I send back for RMA. Seems like this one is also ready for RMA. So now I contacted the reseller where I bought the SSD and explained this problem. I'm quit done with the Vertex and I have let them known that I want to exchange it for a Crucial M4.

So what do you think about this? Broken SSD, or do I miss something?

[Fernando 1]

FBratwurst, on 04 November 2011 - 12:36 PM, said:

So what do you think about this? Broken SSD, or do I miss something?

I agree with you and I am pretty sure, that your problem will be solved after having inserted the Crucial M4 SSD.

Regards
Fernando

[siinain]

Can somebody please tell me which drivers should I pick?

from these:

Windows XP or Windows Server 2003 (32bit)
for nForce2/3/4 SataRAID and nForce2/3/4/5 PataRAID systems:
>32bit nForce LEGACY drivers v6.99 mod by Fernando
for nForce 560/520 (MCP65) and nForce 630a (MCP67) SataRAID systems:
>32bit nForce SATARAID drivers v10.3.0.46 WHQL
for all other nForce SataRAID systems:
>32bit nForce SATARAID drivers v11.1.0.43 WHQL

Thank you

[Fernando 1]

@ siinain:
Welcome at MSFN Forum!

siinain, on 12 November 2011 - 04:07 AM, said:

Can somebody please tell me which drivers should I pick?

As long as you don't post the details about your system (nForce chipset or name and vendor of your pc resp. mainboard), nobody will be able to give you a correct answer.

Regards
Fernando