[gdogg]

sry for double post, just want it to be seen, and not forgotten about.

ok what I did to make it work was.

move sata_ide folder and legacy out of the same directory as sata_raid folder
intergated the sata_raid w/o sata_ide files

then intergrated the legacy folder as pnp.

this fixed the issue, it was the sata_ide drivers causing my issues, w/o them, issues gone. ( i tried using 3 different nforce driver sets, they all worked this way)

This was done under a full version of xp home oem, since shrinking only made it impossible for me to get it installed.

This post has been edited by gdogg: 30 October 2006 - 08:10 AM

[Fernando 1]

gdogg, on Oct 30 2006, 04:08 PM, said:

ok what I did to make it work was.
move sata_ide folder and legacy out of the same directory as sata_raid folder
intergated the sata_raid w/o sata_ide files
then intergrated the legacy folder as pnp.
this fixed the issue, it was the sata_ide drivers causing my issues, w/o them, issues gone. ( i tried using 3 different nforce driver sets, they all worked this way)

Fine, that you succeeded at least.

You probably would have gotten the same result by just integrating the LEGACY (instead of the SATARAID) subfolder as TEXTMODE driver. The LEGACY subfolder contains all needed files, there is no need for any additional IDE PnP driver, if you take this driver folder.

By the way: Nuhi has changed the nForce SataRaid driver installation routine a little bit with nLite 1.2.1. Now it is possible to integrate just the LEGACY subfolder even when you present the normal nForce chipset driver package. The SATA_IDE subfolder will only be additionally integrated, when the user decides to integrate the SATARAID subfolder. So there is no need any more to copy the LEGACY subfolder somewhere outside the chipset driver package prior to the driver integration.

[DrPhantum]

I can NOT get this to work. I have followed these directions to the best of my ability, too!

I currently have this setup:

ABIT AN8 Ultra mobo
1x 74GB SATA Raptor as C: Drive
2x 250GB WD SATA drives in 500GB RAID0 array as D: Drive

When I add SINGLE drivers w/ the latest version of nLite, and go through nLite setup... I can see the C: drive after windows is installed, but the D: drive is nowhere to be found. To get it recognized, I have to go into the device manager, click "disk drives" find "NVIDIA JBOD" and reinstall the driver. I have to choose Compaq > SCSI Drive Array as the driver to get the dual SATA raid D: drive to show up in windows explorer. At this point, the C: drive DISAPPEARS until I restart.

Now... the first few times I ran nLite, the D: partition worked... but I didn't have any support for USB flash drives OR external hard drives. This is very important to me, and so I have tried this over and over and over again. I can not seem to get my RAID array (D:) recognized at the same time as removable drives (USB Flash, external, etc). For some reason, no matter what order I add the drivers, or what drivers I use in general... I can't get support for EITHER any more. I only had luck the first 2 or 3 times I tried it... I'm sure I've done this 30 times or more by now. I'm ready to buy a dedicated SATA RAID card, cuz I think it's all NVIDIA's fault. (nforce4 on mobo)

I can fix the D: partition in device manager (although it really bothers me that it doesn't work, and i have to use COMPAQ drivers), but I can't fix the removable drive support.

SOMEBODY PLEASE HELP ME!

This post has been edited by DrPhantum: 29 November 2006 - 01:04 AM

[Fernando 1]

DrPhantum, on Nov 29 2006, 09:04 AM, said:

I can NOT get this to work. I have followed these directions to the best of my ability, too!
I currently have this setup:
ABIT AN8 Ultra mobo
1x 74GB SATA Raptor as C: Drive
2x 250GB WD SATA drives in 500GB RAID0 array as D: Drive
When I add SINGLE drivers w/ the latest version of nLite, and go through nLite setup... I can see the C: drive after windows is installed, but the D: drive is nowhere to be found.

This is quite normal when you are booting from a non-RAID hdd.
It would be better for you, if you would change the place of the MBR (put it onto the RAID instead of the non-RAID Raptor). If your RAID has been set as bootable, it will get drive letter C:, whereas your single Raptor drive will get drive letter D:. If you install any OS by booting with an nLited CD or DVD with integrated nForce SataRaid drivers (note: unplug your Raptor during the installation!), you will see at once all drives and partitions after having reconnected your non-RAID hdd.

DrPhantum, on Nov 29 2006, 09:04 AM, said:

Now... the first few times I ran nLite, the D: partition worked... but I didn't have any support for USB flash drives OR external hard drives. This is very important to me, and so I have tried this over and over and over again. I can not seem to get my RAID array (D:) recognized at the same time as removable drives (USB Flash, external, etc).

It is not your RAID, but your S-ATA drive which is detected as "removable drive". This is totally normal. All S-ATA drives with hot-swapping ability are detected as "removable drive" and get an icon within the systray. That is nothing to warry about.

[DrPhantum]

Thank you so much for your immediate reply... I still have some problems though.

Quote

(note: unplug your Raptor during the installation!)

I must have windows on the raptor, so I cannot unplug it during installation. The RAID array has all of my backup stuff, such as the My Documents folder, and every picture I've ever taken. The Raptor is what I use for windows, because it's small and fast. I simply cannot format the RAID array and use it for windows, because in doing so, I'd erase everything that I want to keep when reformatting and reinstalling windows.

Quote

It is not your RAID, but your S-ATA drive which is detected as "removable drive". This is totally normal. All S-ATA drives with hot-swapping ability are detected as "removable drive" and get an icon within the systray. That is nothing to warry about.

I must have been unclear when I described this problem... When I plug in my external hard drive (not the SATA RAID array) or a USB Flash Drive (a sandisk cruzer w/ U3), it goes into the "Found New Hardware Wizard", and it cannot find any drivers for it. Meaning: Otherwise Plug-N-Play drives require drivers... drivers that I do not have... drivers that are supposed to be part of windows when you install it. Anybody that has a USB Flash drive relies on the fact that all they have to do is plug it in for it to be recognized... These drives are SUPPOSED to be UPnP in Windows XP, but my computer "Cannot Install this Hardware" according to the Found New Hardware Wizard. I cannot get any Flash Drives or USB External Hard Drives to be recognized with a drive letter in my computer... This issue is completely separate from my SATA drives being recognized. A reboot does not help, and interestingly, the "where do you want to install" portion of the windows installation recognizes all three drives (raptor, raid array, and usb)... I would think that if windows recognizes them to install to, they would be recognized after installation.

What I was referring to when I said "the first few times I installed nLite, the D: partition was recognized," was the fact that, after the first 2 or 3 nLite installs of windows, both the Raptor and the SATA array were recognized w/o a problem... and I thought everything was perfect until I plugged in my flash drive, and Windows couldn't install it. After the 3rd install or so, and up until this most recent one (I'd estimate to be #30), my D: drive is no longer recognized immediately, and I have to pull the "Compaq SCSI disk array" trick in the Device Manager to get it in Windows Explorer.

One other thing that I just remembered... The only time that I can remember that I got all my drives (raptor, sata array, and usb) recognized perfectly, I had turned "Data Execution Protection" on the Unattended tab to "Always On." It was nice being able to recognize all my drives without pulling any tricks... but DEP wouldn't let me do ANYTHING, since even opening Internet Explorer was going to "cause damage to my computer." When I put DEP back to default using the preset config from the disk I had just burned, and ONLY changed the DEP setting... it went right back to not recognizing my sata array or external usb drives.

What does Data Execution Protection have to do with recognition of my raid array or usb drives?


Thanks again for your immediate response. You seem to be very knowledgable, so I look forward to your next reply.

This post has been edited by DrPhantum: 29 November 2006 - 10:03 AM

[DrPhantum]

By the way...

If all of my problems are because I have my SATA drives connected to an NVIDIA nForce chipset... Would buying a new SATA controller card help? If, for instance, it had a silicon image chip on the new card, wouldn't I no longer have all these problems with NVRAID installation?

Also, I have a suspicion that plugging my SATAII (3gbps) drives into a PCI card will not end up in SATAII speed. Would a PCI-Express SATA card be able to handle this? Or is having the chip ON THE MOTHERBOARD the only way I'm going to get SATAII speed?

[Fernando 1]

DrPhantum, on Nov 29 2006, 07:01 PM, said:

If all of my problems are because I have my SATA drives connected to an NVIDIA nForce chipset... Would buying a new SATA controller card help? If, for instance, it had a silicon image chip on the new card, wouldn't I no longer have all these problems with NVRAID installation?
Also, I have a suspicion that plugging my SATAII (3gbps) drives into a PCI card will not end up in SATAII speed. Would a PCI-Express SATA card be able to handle this? Or is having the chip ON THE MOTHERBOARD the only way I'm going to get SATAII speed?

Stay with your on-board NVIDIA nForce4 RAID controller. All other options are worse.

I suppose, that your problem has another cause and suggest the following:
1. Flash the newest mainboard BIOS.
2. Don't install the NVIDIA firewall (Network Access Manager=NAM).
3. Disable the "Enable command Queuing" option of your S-ATA Controller (device manager -> IDE ATA/ATAPI-Controller -> NVIDIA nForce4 Serial ATA Controller -> Properties).
If all these actions don't help, try to run your S-ATA drives with S-ATA1 level (150 MB/s).

[DrPhantum]

Quote

I suppose, that your problem has another cause and suggest the following:
1. Flash the newest mainboard BIOS.
2. Don't install the NVIDIA firewall (Network Access Manager=NAM).
3. Disable the "Enable command Queuing" option of your S-ATA Controller (device manager -> IDE ATA/ATAPI-Controller -> NVIDIA nForce4 Serial ATA Controller -> Properties).
If all these actions don't help, try to run your S-ATA drives with S-ATA1 level (150 MB/s).

1. ABIT hasn't released a BIOS update since February... I've already got the latest BIOS

2. The problem I'm having happens some time before windows even runs for the first time, therefore before I have the opportunity to install ANY software, let alone the NVIDIA firewall software specifically. Also, I am not trying to integrate the NVIDIA package installer into my windows installation, just the drivers from it, so I am not unknowingly trying to install the NVIDIA Firewall software.

3. Again, the problems I'm having happen before I have a chance to enter the device manager... However, I checked it out in a "bad" install that didn't work perfectly...

In the device manager, I have TWO NVIDIA nForce4 controllers each with two channels... one for the raptor & a sata dvd burner, and the other for each of my two RAID hard drives... "Enable command queuing" is grayed-out and disabled on both... So I don't think this is the problem

As far as "run your sata drives at sataI level... Why would I buy SATAII drives, and why would I make sure I had a SATAII controller on my motherboard if I was just going to slow it down? I would buy a ferrari just to glue a wooden block under the gas pedal so I couldn't floor it... and I won't buy a SATAII hard drive just to neuter it back to SATAI. (Don't mean to sound harsh... just making a point. )

And why, finally... did my raid array get recognized normally the first few times I tried nLite, and not the 30x after that?

[Fernando 1]

DrPhantum, on Nov 29 2006, 10:48 PM, said:

2. The problem I'm having happens some time before windows even runs for the first time, therefore before I have the opportunity to install ANY software, let alone the NVIDIA firewall software specifically. Also, I am not trying to integrate the NVIDIA package installer into my windows installation, just the drivers from it, so I am not unknowingly trying to install the NVIDIA Firewall software.
3. Again, the problems I'm having happen before I have a chance to enter the device manager...

You are right, both suggestions will not solve your problem.

DrPhantum, on Nov 29 2006, 10:48 PM, said:

As far as "run your sata drives at sataI level... Why would I buy SATAII drives, and why would I make sure I had a SATAII controller on my motherboard if I was just going to slow it down? I would buy a ferrari just to glue a wooden block under the gas pedal so I couldn't floor it... and I won't buy a SATAII hard drive just to neuter it back to SATAI. (Don't mean to sound harsh... just making a point. )

My advice was just a method to find out, which hardware might be responsable for your trouble.

DrPhantum, on Nov 29 2006, 10:48 PM, said:

And why, finally... did my raid array get recognized normally the first few times I tried nLite, and not the 30x after that?

I have only 2 options: Either you have done something wrong the last 30 times or one of your hardware components has gone defective.

[DrPhantum]

Quote

Stay with your on-board NVIDIA nForce4 RAID controller. All other options are worse.

Define WORSE... Is there any support at all for them?

I don't see anyone complaining about Silicon Image chips... but that could be because I keep searching in the NVIDIA-based threads.

EDIT:

I'd still like to know why neither my USB flash drive nor my USB external hard drive are recognized by nLite'd windows installs... (once or twice they were recognized, but at the expense of some other critical problem, like DEP not allowing me to run any programs whatsoever without "causing damage to my system")

Where are these drivers usually stored? Why can't I download them and integrate them specifically? I know on other working machines, the driver details say that windows is using some generically named .sys file ("disk.sys" or something). Am I removing this from nLite when I take out some of the drivers? The author of the software explicitly says if I'm installing drivers later or integrating them, I may check the box. I've gone without removing any of the drivers, and yet I still get the same problem. What gives?

I don't mean to bug anyone here... but I haven't solved my problems yet.

This post has been edited by DrPhantum: 01 December 2006 - 01:05 AM

[DrPhantum]

UPDATE:

I've tried this a bunch more times... using a variety of different drivers, and still nothing.

I do have a new incompatibility, though... My Logitech Harmony remote isn't recognized, either...

Can somebody tell me what NOT to do that makes my modified windows install incompatible with my flash drive, external USB hard drive, and my harmony remote? Am I removing part of windows that I shouldn't? I'll leave everything the way it's supposed to be if it'll help; I just remove stuff to make the installs faster.

[Fernando 1]

DrPhantum, on Dec 7 2006, 07:52 AM, said:

Can somebody tell me what NOT to do that makes my modified windows install incompatible with my flash drive, external USB hard drive, and my harmony remote? Am I removing part of windows that I shouldn't? I'll leave everything the way it's supposed to be if it'll help; I just remove stuff to make the installs faster.

For testing purposes you should not remove anything from your original OS CD.

[mswaine]

I've just tried this with the nVidea chipset drivers on an ACER ASPIRE 5050 notebook after experiencing the same problems. Because there were ‘warranty is void' stickers stopping me from cracking open the notebook I had to make a guess at the chipset manufacturer and which drivers I required - and chose nVidea's 64Bit

MY BIOS IS NOW CORRUPT

During the install windows informed me 'these driver are wrong for your hardware' or something to that effect and the installation was halted. OK, fair enough windows, the drivers are wrong, thanks for telling me, I'll try something else, ATI is the next best bet. After a reboot though, nothing zilch. I can't even flash the BIOS because

1) blank screen (also tested with another monitor off aux VGA port)
2) wont boot off CD / DVD / USB Floppy

I've built a legacy DOS boot disk with the Acer flash bios program (phlash16) also on the disk. Inside the autoexec.bat it says something to the effect of

beep (I have no visual confirmation so i.e. echo ^G is the only way I know if the disk has booted)
run phlash16.exe with the correct parameters pointing to the file supplied by ACER for this BIOS
beep again to let me know the bios phlashing program returned

but theres not a lot of beeping going on sadly, so I assume theres not a lot of booting going on either...

I've also tried the 'emergency BIOS restore' method with a USB floppy as detailed in this article - no luck.

Wim's BIOS Page

n.b. I've since cracked the machine open, removed the watch battery and let it sit there for 10 hours hoping that by some miracle the BIOS configuration was kept alive by the watch battery.

I didnt realize it was possible to do so much damage with an installation of an OS. The machine has been sent back to Acer dealer - no doubt they'll want to charge me for a new motherboard.

Nightmare... !!!

This post has been edited by mswaine: 13 December 2006 - 02:25 PM

[mattson]

this might be a stupid question, but I can't afford to do a full rebuild at this point in time, is it possible to integrate the drivers without reinstalling windows xp x64?

Cheers,

Matt

[mattson]

anyone?

[Fernando 1]

mattson, on Dec 12 2006, 02:39 AM, said:

I can't afford to do a full rebuild at this point in time, is it possible to integrate the drivers without reinstalling windows xp x64?

Why else would you integrate the drivers into a bootable Windows XP x64 CD if not for reinstalling the OS?
If you have a running XP x64, there is not need for any reinstallation.

[DarkPoe]

Hi guys, i have tried like 1000000000000000...0000...000000 times to install windows x64, i did once but then the trial period expired, so i tried to reinstall but this time it doesnt recognize my RAID 0 array (2x Raptors 74GB) i have a nForce 4 chipset, x2 4400+ and DFI sli-dr eXpert board, dunno what is happening, it gives me 7F, 08 error and well im integrating all kinds of drivers (official, custom builds, etc..)

Any help?

[Fernando 1]

DarkPoe, on Feb 19 2007, 07:53 AM, said:

Hi guys, i have tried like 1000000000000000...0000...000000 times to install windows x64, i did once but then the trial period expired, so i tried to reinstall but this time it doesnt recognize my RAID 0 array (2x Raptors 74GB) i have a nForce 4 chipset, x2 4400+ and DFI sli-dr eXpert board, dunno what is happening, it gives me 7F, 08 error and well im integrating all kinds of drivers (official, custom builds, etc..)

Why don't you just follow my guide?
Nearly 100.00 users cannot be wrong!

[DarkPoe]

I always based all the installations with your guide, i also tried others, the installation goes fine, but then when im loading windows for the first time :S

I tried without integrating drivers and loading the files from a floppy, but then gives me Error 1024 with a file oemsumthing

[Fernando 1]

DarkPoe, on Feb 20 2007, 11:05 PM, said:

I always based all the installations with your guide, i also tried others, the installation goes fine, but then when im loading windows for the first time :S
I tried without integrating drivers and loading the files from a floppy, but then gives me Error 1024 with a file oemsumthing

Did you get the message "File txtsetup.oem caused an unexpected error (1024)..."?
If yes and provided, that you booted off the clean (not modified or nLited) XPx64 CD, you probably took a wrong or corrupt driver combination.

You either have done something wrong or you really have a hardware/configuration problem.
There is a way to exclude the latter:
1. Download the old and not really native 64-bit nForce chipset driver package v. 6.56 (you get it here), unzip it and copy the content of the IDE\WinXP folder onto an empty floppy.
2. Try to install XPx64 by booting off the original XPx64 CD and loading the just prepared floppy drivers by hitting F6 at the begin of the OS installation.

If even this standard and safe XPx64 installation fails, you probably have a hardware problem.
First option: Check your RAM sticks!

This post has been edited by Fernando 1: 21 February 2007 - 05:11 AM