Jump to content

Fernando 1

Member
  • Posts

    2,028
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by Fernando 1

  1. So you couldn't even successfully finish the work of nLite?Then you have done something wrong, which certainly has nothing to do with the Intel textmode drivers themselves. Did you use a clean source, that means an Original MS XP CD with or without SP? This is absulutely necessary. nLite is not able to work with an already processed source. Are you sure, that the XP source you have used, was not already customized for you and other users by adding some software, tools, tweaks, updates etc.? This would explain the error message you got. If you do what I have written within my guide (downloading and unzipping the linked 32bit driver, then integrating the content as textmode driver and choosing the suitable Controller), everything should work fine. nLite will do everything which is needed. You should not add or edit any file!
  2. You are welcome.Fine for you, that you succeeded at least, and fine for me, that your issue had nothing to do with the nForce SATARAID driver integration. Greetings Fernando
  3. This is what I suggest too.
  4. Another question regarding the F6 method, which has nothing to do with your current problem:Why did you want to edit the TXTSETUP.OEM file? Have you tried just to copy the content of disk1 and disk2 on 2 different formatted floppy disks and to insert disk1 when prompted? As I understand the TXTSETUP.OEM file, everything will go automaticly. You are asked for disk2, which contains the other needed files, and the driver loading precedure will complete.
  5. 2 GM RAM should be enough.I don't think, that your issue has something to do with the "unattended" install mode. Try to boot from the original (not nLited) XP CD and look what happens.
  6. How much RAM are you using?
  7. No, for a RAID array you need more than 1 hdd and you have to create the array before you get it. No, because you are neither running your S-ATA ports in AHCI mode nor do you use a RAID array.Nevertheless it is a good idea to integrate the nForce S-ATA driver (it's within the SATA_IDE subfolder of any actual nForce chipset package) into a bootable CD as "normal" device (=PnP) driver. You don't need to integrate any driver, because the OS Setup will detect your S-ATA hdd and will get properly installed, but it would be nevertheless a good idea to integrate the following nForce chipset drivers: S-ATA (take the SATA_IDE subfolder), Ethernet and SMBus.
  8. @ big_sid and Kelsenellenelvian: There is no need to change or edit any files. If you are going to integrate the nForce SataRaid drivers of NVIDIA's new nForce chipset driver packs 15.17 or 15.18, you should just take the content of the SATARAID folder (and additionally the SATA_IDE folder, if you have a LEGACY mode nForce chipset). Before you are doing this, you can delete the subfolder(s) named "Floppy". NVIDIA has created these "Floppy" subfolders just for the F6 method, because you won't get all these multilingual driver files onto 1 floppy disk. @ bratsj: As long as your hdd is connected to a Silicon Image S-ATA Controller, you cannot use any nForce SataRaid drivers.
  9. @ Chrysalis: Thanks for your comment about the development and abilities of INTEL's different textmode driver versions. So it was obviously not a bad idea to update my guide with the links to the brandnew Intel S-ATA and RAID drivers. Greetings Fernando
  10. You are right. The integration of both Intel textmode driver versions (v8.2.0.1001 for the ICH9DO and v7.8.0.1012 for the ICH6R SATA AHCI Controller will be a problem, because the drivers themselves have the same name (IASTOR.SYS) and will be overwritten, when additionally copied into the i386 directory by nLite (the presence of the SYS file within this directory is necessary during the TEXTMODE part of the OS installation). As a consequence one of the Controllers (ICH6R or ICH9DO) will not be detected, if you integrate both driver versions.Solution: You have to create 2 separate nLited CDs, 1 with integrated Intel textmode drivers v8.2.0.1001 (for the ICH9DO AHCI Controller) and 1 with integrated Intel textmode drivers v7.8.0.1012 (for the ICH6R AHCI Controller). @ all users, who are using my guide (start post of this thread): The guide now contains download links to the brandnew official Intel S-ATA and AHCI drivers v8.2.0.1001 dated 05/07/2008. As usual I have prepared them for an easy integration. Have fun! Fernando
  11. Thanks for your suggestion. I have already recognized the new Intel textmode drivers, but since I am not at home for a while, the users of my guide have to wait some days.I will update the linked drivers next week, when I am at home again. CU Fernando
  12. This is a known issue of any 32bit Windows OS, if you try to install it with 4GB of RAM.
  13. Hi Steve,since your hdd has been detected by Windows XP Setup, you obviously had integrated the correct Intel S-ATA AHCI Controller driver. I think, that your issue was caused by another driver you had integrated. My recommendation: Create a new nLited XP CD with just the integrated Intel S-ATA drivers. Don't add any other driver. If the installation should fail, try to additionally integrate the Intel INF (=chipset) drivers as PnP drivers. Once Windows XP is up, you can install the other needed drivers for your system. Good luck! Fernando
  14. Yes, it will work, there is nothing to do extra. Just integrate the SATARAID folder content as textmode driver. Your BSOD might be due to problems of handling 4 GB of RAM by Windows XP.Try to remove 1 memory stick while installing the OS. Once the OS is up, you can insert it again (but the 32bit OS will only be able to use 3 GB of your memory).
  15. Judging by the fact that it says it doesn't matter which INF file is clicked on when via the "Single driver" option, I'm guessing it also doesn't matter if one clicked on "Mulitiple driver folder" option instead rather than "single dirver"?You can use the "Multiple driver" button as well, but you have to pay more attention as with the "Single driver" option (to prevent, that you get more drivers integrated than you want). Yes. Thanks for this additional information. There is no problem at all, if you have integrated the textmode drivers. You are right regarding the F6/floppy driver loading option. OEM Preinstall should be disabled in this case.
  16. If your S-ATA drives are connected to these controllers, you have to integrate the INIC-162x S-ATA drivers. You certainly mean, that you have integrated SP3 into an XP SP2 CD, don't you? It wouldn't make any sense to integrate SP2 and SP3. No, you only should integrate the correct S-ATA drivers (from the Controller manufacturer, where your hdd's are connected) as TEXTMODE drivers.
  17. Take the Intel INF drivers (= "INF Update Utility") from here. This package is easy to unzip by tools like WinRar or 7-zip. You will find the INF files ready for the integration within the "All" folder.
  18. You are welcome.As you may have realized, your problem had nothing to do with the nForce SataRaid drivers. Fine, that you succeeded at least. CU Fernando
  19. Everyone with a suitable Intel S-ATA Controller is able to get XP installed. You must have done something wrong.If you don't want to have any stress, you should just go into the BIOS and set the S-ATA Controllers, where yor hdd is connected, to "IDE mode". Then you will be able to get XP installed without loading/integrating any separate textmode drivers. If you want to continue to get XP installed by using the AHCI features of your on-board S-ATA Controllers, you should try it again from scratch: Backup your datas and format your hdd with NTFS system. Furthermore you should give some more informations about your hardware, for example the number and sorts of hdd's.
  20. Maybe the XP Setup just "sees" 130 GB, but will be able to use the whole space.It should not be a problem to get XP installed onto your computer. Look here.
  21. @ Kuzco: 1. It is never a good idea to have different MBR's on the used hdd's. You got them by trying to install XP onto one of your hdd's (without RAID) and then onto the RAID. Solution: You should create the RAID by using 2 absolutely clean hdd's. Use the Seagate Tool to low format both hdd's. 2. You should know the error message why you get the endless reboots at the end iof the installation. Solution: Hit F8 while booting and choose the option "Don't reboot at system failure". Didn't you even come to the point, where the Setup shows your hard disk(s) with their partitions and you have to decide where you want to get XP installed?
  22. If you don't even come to the point where your hdd is detected (or not), you obviously have a problem with your nLited CD.You can verify it, if you try to boot off the original XP CD.
  23. I doubt, that your problem has anything to do with the integration of the Intel S-ATA AHCI driver.As all other users you will be able to get the OS installed with enabled AHCI mode Intel S-ATA Controllers. Questions: 1. Which mainboard do you use? 2. Are you sure, that your S-ATA hdd is connected to an Intel S-ATA port? 3. Is your optical drive (CD/DVD-ROM) ok? Are you able to boot off the original (not nLited) OS CD? If yes, try to load the Intel textmode driver by F6/floppy. If you succeed this way, you should create a new nLited CD, where you did only integrate the Intel textmode driver and nothing else.
  24. Dang, you're right. I just checked the specs and RAID5 isn't listed. I wonder if the pencil mod to make the Ultra-D an SLI-D adds RAID5 functionality.Ok, then we have detected at least the reason for your problem.RAID5 is only supported by newer mainboards.
  25. ACPI\PNP0510 *PNP0510 I haven't been able to figure out what this is. Whenever I tried to manually install driver sfor it it never works. I think, that it is the infrared device, which you obviously have removed by nLite. The missing MS drivers are named irsir.sys and serial.sys.Now back to your RAID5 issue: Since I had the same mainboard, I doubt, that the DFI Lanparty NF4 Ultra-D is fully supporting nForce RAID5. That is probably the reason why your RAID hasn't been detected by the OS.
×
×
  • Create New...