Fernando 1
Content Type
Profiles
Forums
Events
Posts posted by Fernando 1
-
-
Why did you integrate the NVIDIA nForce SATARAID drivers? These drivers will only be able to detect HDDs/SSDs, which are running in "RAID" mode.You´re very right, did replace the driver for the 32 bits one. But the problem remains that windows-install cannot find a harddisk.If you have an nForce chipset mainboard, please give us more informations:
1. What sort of nForce chipset has your system?
2. Is your SSD connected with an nForce SATA Controller at all?
3. Which SATA mode (IDE/AHCI/RAID) did you choose within the BIOS?
0 -
You got the message, that the file NVRD64.SYS is corrupt (not damaged). This always happens, when you try to integrate a 64bit driver into a 32bit OS like Windows XP. 32bit Operating Systems cannot use any 64bit driver. That is why you get the message.Cleaned the xp-cd and Nlite picked it up now. Downloaded the 64 bit SATARAID v10.3.0.46 which I think is the one for my ASUS P5RDI-VM motherboard, and burned the iso-file. Plugged out my old HDD and plugged in the SSD. Installation started! But then the message nvrd64.sys is damaged... Looked an saw this file in the driverpack.0 -
Since I neither have an X79 RAID system nor trying to get Windows XP installed, I am not able to answer your question.I'm asking, is the megasr.sys driver that intel provide for X79 RAID - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20963〈=eng&OSVersion=%0A&DownloadType=Drivers)HWID: PCI\VEN_8086&DEV_2826&CC_0104
Is this driver in fact incompatible for XP Textmode with RAID?
According to my knowledge none of Intel's regular RSTe drivers iaStorA.sys+iaStorF.sys can be used under Windows XP (32bit) for systems with an "Intel® C600 Series Chipset SATA AHCI Controller" (DEV_1D02) or "Intel® C600 Series Chipset SATA RAID Controller" (DEV_2826).
I have no idea, if the Intel ESRT2 driverpack will support "normal" non-Server X79 RAID systems.
This is what I found within the attached ESRT2_Windows_v.15.00.0811.2012_Readme.TXT:
Supported RAID Controllers
==========================
This download provides support for the Intel(R) C600 chipset on both AHCI Capable SATA Controller and SATA/SAS Capable Controller in Intel(R) Embedded Server RAID Technology 2 (ESRT2) mode.
NO OTHER INTEL(R) ESRT2 DEVICES ARE SUPPORTED WITH THIS PACKAGE0 -
No, the version of the package doesn't mean, that the INF files content have been edited by Intel at different dates.I need to update the Chipset drivers for XP. Should I use the latest Intel has to offer, or should I integrate the Chipset Drivers with your extracted pack "Intel_Chipset_Device_INF_Files_Set_V9.3.0.1020_WHQL_for_XP_Integration"? Would there be an issue with the latest by Intel? Any conflicts since I am using Windows XP SP3 32bit?Since you have a very actual chipset, it may nevertheless be a good idea to install the newest version 9.3.0.1026 of the Intel chipset device software (there are no real drivers, but just text files within the package).
Where resp. when did you see a link to the INF files v9.3.0.1020 within the start post of this thread? I ask it, because I have updated the link to the actual pack version 9.3.0.1026 at 11/22/2012.
Have a nice weekend!
Fernando.
0 -
Hello Larry,** I solved this issue ** When I selected the driver(s) from the 32bit Intel RST Textmode v10.5.2.10.10 I inadvertently selected, by highlighting, both the AHCI and RAID. So the OS installed based on the RAID, but when it went to enter Windows it must have defaulted to AHCI, which caused the BSOD. It's the only thing that makes any logical sense to me. I've been doing stuff like this for a long time, but the conditions have changed since 2009. Anyway, I backed up to a clean nLite XPSP3 image and ran Textmode again, this time realizing the difference in what I was looking at and chose the RAID option. This worked and now I have Windows XP 32bit once again.it is fine, that you succeeded at least with the XP installation onto your X79 RAID array.
Just to prevent any future problems regarding the integration of an Intel RST driver: If you have an Intel RAID system, you should not highlight any of the listed Intel SATA AHCI Controllers, when you get the nite textmode driver popup.
Enjoy your Windows XP!
Regards
Fernando
0 -
Yes, as Sp0iiLedBrAt has written you have to integrate >this< special 32bit Intel RST driver, which is working with just 1 driver named iaStor.sys.You mean the point c of the guide?
The XP installation would fail, if you would integrate any of Intel's RSTe drivers, because they use an addidtional SCSI driver named iaStorF.sys. Windows XP (32bit) is not able to manage this SCSI filter driver.I understand that for Windows XP 32-bit can not be integrated in the installation CD.
No, you should have set the Intel SATA Controller to "AHCI" mode and boot off the Windows XP CD with integrated Intel RST driver I jhave linked above.The solution would be to install Windows XP 32-bit on IDE mode, once installed change BIOS to AHCI mode and install the driver RSTe. Is this OK?You won't be able to get any Intel RSTe driverpack installed while running Windows XP (32bit).
0 -
Just do what I have written within my guide (start post of this thread).How should I do it?
Este es un foro de habla Inglés y no foro de habla Español.Por cierto, hablas español? Como te llamas Fernando...0 -
@ jovigom:
Welcome at MSFN Forum!
It is not only possible,you have to integrate it, if your system drive is connected to an Intel SATA port, which has been set to "AHCI" mode.I have a motherboard Gigabyte GA-X79-UD3 and I want to install Windows XP 32-bit.I'd like to ask if it is possible to integrate the AHCI drivers on the installation CD.
Regards
Fernando
0 -
You should not choose the correct driver (there is only 1 driver inside the package), but the correct SATA AHCI Controller of your X79 chipset..I'm going to run nLite and choose Drivers, which should give me the Driver Integration Option box for Storage Device Textmode Driver, which I then point to your folder '32bit Intel RST textmode drivers v10.5.2.1010 for X79' and I will choose the correct SATA/RAID driver from there.
The Intel Chipset Device INF files have nothing to do with the textmode driver, which is within the "32bit Intel TST textmode driver v10.5.2.1010".But then I noticed you also included the 'Intel_Chipset_Device_INF_Files_Set_v9.3.0.1020_WHQL_for_XP_Integration.rar' and suggested to Integrate the "drivers" by pointing to any of the various INF files within the folder. I'm confused between the 1st option and 2nd option. They are different versions and I thought the first one was specifically for the TEXTMODE single driver?
Although there will probably no need to integrate them into the XP CD, I recommend to do it, because your X79 chipset will be rather unknown for the XP Setup. Just point to any of the INF files (doesn't matter which one) and all the INF files will be integrated. That has nothing to do with the single/multiple driver option.So what do I do with the Intel Chip Device INF you provided?0 -
This is absolutely correct.nlite asks me for an inf file, and there are two there to choose from iaAHCI.inf and iaStor.inf. Which one do I choose?Fernando, correct me if I'm wrong, but I think that regardless of which you choose, both will be copied and the appropriate will be used if they are in the same folder. Please, wait for confirmation for this.
Much more important than the choice of the correct INF file is the choice of the correct on-board Intel SATA AHCI/RAID Controller, when nLite shows the Textmode Driver Popup window.
0 -
No, because there is no TXTSETUP.OEM within your nLited XP CD.would it be possible to modify the TXTSETUP.OEM file just for the X79 chipset to recognize the XP 32bit Install on my Raid setup?All driver related details are layed down within the files named TXTSETUP.SIF and DOSNET.INF. You may open them with the editor and change what you want, but don't expect any help from my side.
Good luck!
Fernando
0 -
@ Caleb37:
As Sp0iLedBrAt already has written, you should forget your idea to modify your old nLited Windows XP SP3 image, which had been customized for being used with an Intel X58 chipset system. You will waste a lot of time and probably will get a dissappointing result.
Provided that you are the owner of an original (= untouched) Windows XP CD with a valid Retail or OEM CD key, I recommend to create a new XP SP3 CD with integrated 32bit Intel X79 RAID driver from scratch. Additionally you may integrate the newest Intel X79 chipset "drivers" (they are just INF files) for Windows XP. You can download this small INF "drivers" package just for your X79 chipset from >here<.
There is no need to integrate anything else. Once Windows XP is up, you can install the actual versions of the other missing drivers (maybe you have to download them from another computer, which has internet connection). The Windows XP Device Manager will show you the devices, which are missing by a yellow mark.
Regards
Fernando
0 -
Although working download links to modified versions of the most actual AMD AHCI/RAID drivers for Windows XP (32/64bit) have been already presented by me in the post No 234 of this thread, I have just updated my first post too.So can you please update your package with all of amd sata drivers for XP and update your first post please?
It may work, but generally I do not recommend to integrate more than 1 textmode driver, if you are using nLite.Can amd sata drivers and intel sata drivers co-exist in the same iso?If you want to create an All-In-One XP CD containing a lot of different textmode drivers, I recommend to use the "Mass Storage DriverPack" and the tool DriverPacks Base for the integration procedure.
Regards
Fernando
0 -
@ bramke:
welcome at MSFN Forum!
Your mainboard has at least 6 Intel SATA2 ports and 2 Marvell SATA3 ports. As long as you run the SATA Controllers in IDE mode (=BIOS setting), you don't need to load or integrate any special textmode driver!the sata controller is intel yes when i look at ide it says this driver is installed in ide mode intel ® 5 series/3400 seriesIf your SATA Controllers have been set to "AHCI" within the BIOS, you have to load (F6) or integrate the appropriate 64bit textmode driver (depending on the port,where the SSD is connected).
Here are the download links to both drivers, which come into consideration, but you should just integrate one of them (that one, where the SSD is connected):
>64bit Intel RST driver v11.2.0.1006 WHQL for Windows XP x64<
Important: If you should integrate this driver and get the TEXTMODE driver popup with a list of different Intel SATA Controllers, you should highlight just the listed "Intel® 5 Series/3400 Series SATA AHCI Controller".
> 64bit Marvell 91xx AHCI driver v1.2.0.1027 WHQL for Windows XP x64<
The correct driver is the "Marvell 91xx SATA Controller 64bit Driver".
That consequence is quite normal, if you try to integrate a lot of different actual textmode drivers at once. As I have written above, you should integrate just 1 single textmode driver (the appropriate one).i tryed slipstream all drivers at once from the website but its not workingi only get blue screens and setup not finding my ssd
Good luck!
Fernando
0 -
This is the nLite Forum and not the DriverPacks Forum.Please show me the sticky for the driver packs method.0 -
If anyone starts a new thread with the topic "Guide to build XP/SP3 setup drivers included and more" within the Forum named "nLite Forum", the visitors do expect,I chose a wrong word maybe to the name of the thread. Found this as a part of what guide means. "pamphlet, etc., giving information, instructions, or advice; handbook: an investment guide".1. that there is something like a "Guide" (and not a simple link) within the start post,
2. that the thread starter has written the "Guide" himself and
3. that the "Guide" has been designed for users of the tool nLite.
None of these preconditions are given. The title is absolutely misleading. I even doubt, that this thread is really helpful for nLite users.
Please compair your "guide" with my "sticky" ones within this Forum.
The correct title for this thread would be "Link to another Forum with a description of the DriverPacks method".
Additional information for all visitors of this thread:
The most important reason to use a tool like nLite is the integration of the appropriate AHCI or RAID driver into the XP CD, because otherwise the XP Setup will not detect the HDD/SSD, which is running in AHCI or RAID mode.
Unfortunately none of the DriverPacks, not even the "Mass Storage" DP, contains a file named TXTSETUP.OEM, which is absolutely needed, if the user tries to load an AHCI or RAID driver via F6 or to integrate it into the XP CD by using a tool like nLite.
That is why it doesn't make much sense to combine the DriverPacks with nLite.
0 -
According to my knowledge the Driverpacks tool named DP Base is not limited to private usage.Since I cant use nLite as I setup this terminal, would you be open to suggest another slipstream software that would be OK fine for my use?>Here< you can find all needed informations about the Driverpacks method. The needed DriverPacks Application named DP Base and the special DriverPacks themselves (e.g. the "DriverPack Mass Storage") can be downloaded from >here<.
Or in the alternative' date=' is it possible to pay for a commercial version of Nlite so I can use it for this install?[/quote']There is no commercial version of nLite available.Thank you for your understanding.
Regards
Fernando
0 -
Nobody said that.Commercial version? Bear in mind it is not my job to cusomize operating systems.Here is an extract of the nLite Licence Agreement you have accepted during the nLite installation:
"1. nLite is freeware and can be freely used for any personal non-commercial purposes.
5. nLite is free for personal use only, you cannot use it for any company or business purposes at this time."
0 -
Sp0iLedBrAt:
Thanks for your assistance, which helped login123 to solve his problem. I haven't seen his posts until now.
@ login123:
Welcome at MSFN Forum!
It is fine, that you succeeded with the XP installation in AHCI mode using the special AMD AHCI driverpack I have customized for this purpose.
Yes, the installation is very easy: Run the Device Manager, which will show the missing drivers by yellow marks. Then point to the INF files of the downloaded AMD chipset drivers. The hardware detection will find and install the appropriate drivers. Once all yellow marks are gone, everything will work fine.I must quit this project for a while, but still would like to know, can i install the new drivers from their .inf files?Regards
Fernando
0 -
The 32bit Intel RST driver package 11.2.0.1006 contains only 1 driver named iaStor.sys.I am using CD-R as my media, so I assumed I had to make a new disk for each slipstream. By both drivers I was referring to the 7 series with 316 and 7 series without. You are suggesting the one driver method and silipstream them both individually into the same install disk, Yes?What I suggested was, that you may highlight both Intel 7-series SATA AHCI Controllers, if you don't know the exact Controller name of your mainboard. That is not the integration of 2 drivers, but the try to enable the support of 2 different Controllers by 1 single driver.
If you have created 2 different CDs, each of them wiith the support of a differen Intel 7-Series Chipset SATA AHCI Controller, it is even better.
That is why you have to restart the complete nLite procedure from scratch by copying the original untouched XP CD content, if the XP installation failed and you are going to create a new CD with integrated driver. Furthermore you should not load any ini file with a previous nLite session in this case.Also I noticed that after the nLite procedeure, the folder that I copied the sp3 disk into now has additional files showing (the slipstreamed files no doubt). Are these the files that are in nLite when I am asked if I want to use the previous session? I usually right click and delete them in nLite but noticed they are still there in the source folder.
So you think, that you bought a pirate copy of a Windows XP CD? Doesn't it have a Microsoft hologram?Also Just discovered my XP sp3 disk is likely a volume licence version, possibly meaning it could be a nock off
There are many ways to purchase a legal original XP CD as Retail version showing the Microsoft hologram.How does one source a known legit XP sp3 disk these days?
The use of nLite is only allowed for private purposes, not for business.
Yes it is for work, Several legacy programs and we're stuck with XP until they pull the trigger on a company wide upgrade.Is that for work ?If it is your job to customize Operating Systems like Windows XP, you have to use another tool or method.
0 -
Why do you want to create a second disk? And which "both chipet drivers" do you mean?But if that gets this terminal up an running I still have to revisit the B75 board and will probably make a disk with both chipset drivers.
I always recommend to use the "one driver" integration method, because it is the safest one to get just the driver you want and nothing else.when I intigrate should setup to do it selecting the one driver at a time or multi driver folder?0 -
If there is no WINNT.SIF file within the i386 directory, your XP CD may work for the driver integration task.To your suggestions, I wish I could say I am 100% sure my XP CD is genuine, but I can not. It was an OEM version purchased off ebay a while back. Visually it compares well to a sp2 disk I have and it passes the test above, No WINNT.SIF file.
If you don't know the exact name of the Intel SATA AHCI Controller (with or without C216), you may integrate them both. If you should know the Controller name you had integrated the last time (with the installation failure), you may take the other one now.Regarding the controller, I was unable to find anywhere in the boards manual that identified if the controller was the "Intel® 7 Series/C216 Chipset Family" or the "Intel® 7 Series Chipset". On the other hand it makes no reference to the C216 controller either.0 -
@ cozinbob2:
If you are happy with the driverpacks instead of the nLite integration method, why do you post it into the nLite Forum?
Users may think, that they can integrate the "Mass Storage driverpack" by using nLite and this is absolutely misleading.
This thread has meanwhile more than 1.2 millions of visitors and if you compare this with the numbers of users, who posted about problems, the big majority of them obviously succeeded with the nlite integration method.
Regards
Fernando
0 -
@ lioninstreet:
I suspect, that you have chosen the wrong SATA Controller while integrating or loading the Intel AHCI driver. Alternatively your BSOD problem may be caused by using an already modified XP CD as source.
This is what I recommend to do:
- Look into your mainboard manual and check, if the SATA Controller of your mainboard belongs to the "Intel® 7 Series/C216 Chipset Family" or to the "Intel® 7 Series Chipset Family".
- Download >this< RST driverpack and unzip it.
- Restart the creation of an XP SP3 CD with integrated Intel AHCI driver from scratch by copying the content of a clean (untouched) XP CD onto a separate folder of your HDD.
- Let nLite integrate the RST driver v11.2.0.1006 as textmode driver. When you get the popup window with the list of all available SATA Controllers, just check the "Intel® 7 Series/C216 Chipset Family SATA AHCI Controller" or the "Intel® 7 Series Chipset Family SATA AHCI Controller" depending on the result of your previous check (point 1).
- Let nLite create the ISO file and burn the ISO file as bootable image.
- Set the SATA Controller of your system to "AHC mode".
- Install Windows XP by booting off the just created CD.
Good luck!
Fernando
P.S.:
No, the driver was not wrong, but maybe the chosen Controller.Is the 7 series chipset driver wrong?
No, that is not true.As I was researching this I read somewhere that the 7 series chipset will not work with XP in AHCI. Any truth to that?0 - Look into your mainboard manual and check, if the SATA Controller of your mainboard belongs to the "Intel® 7 Series/C216 Chipset Family" or to the "Intel® 7 Series Chipset Family".
nLite dead end
in nLite
Posted
If the ULI SATA Controller should be set to "RAID" mode, you will succeed with the XP installation after having integrated >this< 32bit ULI SATARAID driver as TEXTMODE driver.