Jump to content

Fernando 1

Member
  • Posts

    2,028
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by Fernando 1

  1. ... and which S-ATA driver did you integrate using nLite? You have to integrate the S-ATA driver as TEXTMODE driver. A TXTSETUP.OEM file is needed within the driver folder.
  2. No. Even if you choose the "Fully Automated" Unattended Mode, you are asked at the beginning of the OS Setup where you want to install the OS and get the opportunity to format the selected hdd partition. So this option is not really a "fully" automated installation. It has secutity reasons why nLite handles it like this, because otherwise the OS Setup would choose automaticly the partition where to get installed and you won't get the opportunity to choose it yourself, format or partition it previously etc. If you want a really fully automated installation without being asked where and how you want to get the OS installed, you should do the following: 1. Run nLite, choose the "Fully Automated" Unattended Mode and do all needed entries. 2. Let nLite do its work, but without creating the ISO file. 3. Go into the nLited OS directory and search for the file WINNT.SIF file. You find it within the i386 folder. 4. Open the WINNT.SIF file by using the Editor (notepad) and look into the [Data] section. You will find an entry "Autopartition=0". 5. Replace the "0" by a "1". The new entry is "Autopartition=1" (without quotation marks). 6. Let nLite create the ISO file and burn it. Now you get a really fully unattended bootable OS CD, but be aware of the fact, that you won't get the opportunity to choose the partition where the OS will be installed.
  3. I could not find a thing. I tried a variety of search terms even joining the words and using *: Integration_of_nVRaid_drivers_into_XP_W2k_and_W2k3_(32-bit) Integration_of_nVRaid_drivers_into_XP* Integration_of_nVRaid_drivers* Why don't you just double click the links given by legolash2o?
  4. This has probably nothing to do with the nForce IDE drivers.My suggestions: 1. Check, if you have flashed the latest mainboard BIOS version. 2. Hit F8 while booting and choose the advanced option "don't reboot at system failure". Then you can read the error message, which may help to find the issue reason.
  5. This thread was dedicated for nLite 1.0 Beta5 and was started more than 2 years ago.Please look here for actual instructions how to get Windows XP x64 installed onto an nForce SataRaid system. Actual is nLite v.1.4 RC2
  6. Yes, try it again by just integrating the SATARAID driver folder as textmode driver (without integrating the SATA_IDE driver folder). Some new mainboards with nForce 5xx or nForce 6xx chipset don't like the SATARAID/SATA_IDE mix.Please reply if this fixed your problem.
  7. You already got an answer here at the NVIDIA Forum. CU Fernando
  8. Exactly this was the reason why I wrote this special guide for the nForce RAID driver integration into Windows XP x64 and Windows Server 2003 x64. There you will find usable 64bit drivers too.If you have any further questions regarding nForce RAID and XP x64, please post into the linked 64bit thread. They should work too, but you won't get WHQL signed nForce IDE drivers installed this way.
  9. It is not easy to help you to find the suitable and actual RAID drivers you need, because you gave us only very little informations about your system regarding the sort of Highpoint RAID Controllers of your mainboard (look into the manual) and the sort of your RAID (P-ATA or S-ATA). Nevertheless I can give you some advices: 1. If you want to get a Highpoint RAID detected, you have to load/integrate Highpoint drivers. My guide was written only for users with a NVIDIA nForce RAID system. The nForce SataRaid drivers don't work at all with your Highpoint RAID Controllers. 2. You will find the correct TEXTMODE drivers for your Highpoint RAID Controller either here at Abit's download page or here at Highpoint's download page.
  10. You are right: The guide was mainly written for users with an nForce RAID array. As you don't have and don't want to create a RAID, only the Annex II part of my guide is useful for you. Probably yes, but you should remember, that the nForce SATA_IDE folder cannot be used as textmode driver (no TXTSETUP.OEM inside). When the Windows XP Setup detects your S-ATA hdd at the beginning of the installation, everything is fine, but if your mainboard BIOS doesn't allow to set the nForce S-ATA ports to the "IDE" mode, I recommend to integrate the SATARAID driver folder as textmode driver (although you don't have a real RAID array).
  11. It's the first option.Windows Setup will only install drivers, if it detects the corresponding hardware.
  12. Fine, that you succeeded at least. You obviously mean this Vista and nVRaid installation guide, but this is not valid for Windows XP. The easiest way to get NVIDIA's Raidtool installed is to run the installer of the associated nForce chipset driver package. As long as I used Windows XP with my nForce4 chipset mainboard I have never used or installed NVIDIA's Raidtool.
  13. I am sorry, that footwo didn't get any advice and that he didn't report here how he managed to solve his problem.Now to your issue: It is not easy to find the reason for your endless reboots. 1. Try to read the error message by hitting F8 during the reboot and choosing the option not to reboot at any system failure. 2. If you have a dual or multi boot system, have a look into the SETUPLOG.TXT (only the last lines are interesting), SETUPERR.LOG and SETUPAPI.LOG files. You find them within the Windows directory of the partition where you tried to install XP. As the SETUPAPI.LOG file is not easy to read, let the editor search for "Serial ATA Controller" and find out, if the "nForceXXX Serial ATA Controller" has been installed (or the wrong "Standard Dual Channel PCI IDE Controller").
  14. Your Amilo PI 1505 notebook has the following chipset: Intel 945GM.Here you can get the newest chipset drivers for your notebook.
  15. Look here:FIXBOOT FIXMBR
  16. Did you remove the old hdd? If not, have you set your new hdd at first place of the "HARD DISK BOOT PRIORITY" settings within the mainboard BIOS (Advanced BIOS Features)?Have you tried to boot off the XP CD and using the FIXBOOT/FIXMBR option?
  17. Thanks for your feedback!This may encourage other users with an nForce3 SataRaid system to integrate the nForce IDE drivers v.6.95 instead of the old official ones v.4.46.
  18. At first I have to beg your pardon for my very late response. Reason: I have not been at home for several weeks and your post disappeared within the nLite forum.... Little side note: This would not have been happened, if you would have posted within this thread, which is the correct one for your problem, because you are not planning to create a bootable CD with the 64bit version of Windows XP. Now to your problem: Within my instructions (first posts of both threads for XP 32bit and 64bit) you don't find any advice to hit the F6 button during the OS installation and to load any driver from a floppy disk. Contrary to this I suggest to integrate the nForce SataRaid drivers into the bootable XP CD by using nLite. If you create a bootable CD by nLite or a similar tool and use the "Unattended Install" option (for example by just editing the user name or the CD key), the Windows Setup routine "forgets" all drivers you will load via F6/floppy while installing the OS. This is a wellknown issue of the Windows Setup routine! The users have 2 options to prevent this Windows Setup issue: a ) by booting off a Windows OS CD with integraed TEXTMODE drivers (without hitting F6 during the installation) or b ) by booting off a Windows OS CD without using any "Unattended Install" modifications (no WINNT.SIF file within the i386 directory of the CD) and using the F6/floppy option. Unfortunately the latter option leads very often to an endless reboot at the end of the installation. That is why I always recommend to integrate the nForce Sataraid drivers into a bootable OS CD. Thanks for your description how you managed to get a perfectly running dual boot system with your nForce Raid array.This may help other users with similar problems.
  19. 1. It is possible to flash a higher Raid BIOS version into your mainboard BIOS, but the new nV Raid BIOS version would not work for you, because nVRaid BIOS versions higher than 4.81 do not support nForce3 Raid Controllers.2. Yes, take the unofficial nForce IDE drivers v. 6.95. There are working fine with nForce3 chipsets. 3. No (see point 1). You should give me some more details about your hardware configuration, the OS you want to install, the OS source you were using and the drivers (sort and version) you have integrated by using nLite.
  20. It depends on what you want - a non-Raid or a Raid system. If you want to rebuild the nForce Raid0 array, you should do what I have written within the first post of this thread. Very important: After having (re)created your Raid array, you have to set it as bootable. You will not be able to do it unless you have changed the boot priority of your hard disk drives within your mainboard BIOS. The NVIDIA Raid array has to be set on the first position! Otherwise you will not be able to get any OS installed. The HARD DISK Boot Priority has nothing to do with the "normal" boot order of the storage devices (1. CD-ROM. 2. HDD etc.).
  21. Here are the essential sentences within my guide (first post of this thread): Do you think, that I should mention separately nForce 680i and nForce 680a chipsets?
  22. What do you think should be updated or included?If you follow my guide, you will download this official nForce chipset driver package v.9.53, which is designed for all nForce 680i chipset mainboards. If you integrate the included SATARAID driver folder, you should get no problems with the later XP installation. I know, that the nForce SataRaid drivers v. 6.91 are not the newest and maybe not the best ones, but they are currently the latest official nForce IDE drivers for nForce 850i chipsets. Do you think, that I should give a link to the nForce IDE drivers v.6.99 into my guide? I would do it, if I get the feedback, that they are better for nForce680i chipsets than the official nForce IDE drivers v.6.91.
  23. If you want to unpack an EXE file, you will need a tool like WinRar or 7-zip. After having installed any (un)packing tool, you will be able to unzip the nForce chipset driver package by right clicking onto the EXE file. You can extract the package wherever you want and name the created folder with the extracted files and subfolders as you like.
  24. What you need to integrate is the VIA Raid driver which will be needed for the installation of the built-in VIA VT6421 RAID Controller. You get the actual VIA RAID driver package here. 1. Unzip the package 2. During the Driver Integration part of nLite you should point to the VRAIDDrv\drvdisk folder of the package. This will integrate the needed VIA Raid driver as textmode driver.
  25. Everything seems to be fine.1. Don't warry about the "iaStor_ICH8R" within the [Drivers] section of the Last Session.ini file. The correct name is "iaStor_ICH8R/ICH9R", but the last digits were cut. Yes, the ICH8R and ICH9R Controllers are using the same drivers. nLite has copied all files (even the not needed ones) of the Intel SATARAID driver package I had uploaded for you. 2. The last line is ok too. nLite has copied the entire content of the Intel INF driver folder "All", that means all files, into your bootable XP CD. The 5000XZVP.inf file obviously was the one you pointed to. 3. If you want to integrate the TCP/IP patch, you should disable the SFC.
×
×
  • Create New...