Jump to content

Fernando 1

Member
  • Posts

    2,026
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by Fernando 1

  1. I don't know, if somebody could successfully integrate the nVRaid drivers into Windows XP by using nLite Beta6 without any "handmade" changes. All my tests failed at the end of the installation procedure by endless reboots of my computer, even when I rebooted in safe mode. So the answer is: The issue appears straight during the installation of the OS, there is no chance to use it. The reason for this issue is, that the Windows XP setup routine installs the wrong driver (Standard PCI IDE Controller) during the GUIMODE part of the installation. The [OemInfFiles]-method, which is able to prevent this strange behaviour, has not been completely implemented into nLite Beta6.
  2. I have a DFI Lanparty UT NF4 Ultra-D with the Bios from 06/23/05. This Bios includes the Raid Bios version 4.84.
  3. Please post the result of your work within this thread. Good luck! Fernando
  4. You can't install the nForce Raid drivers from the chipset package 6.66 with an nVRaid Bios v. 4.81. What you need is a Raid Bios version 4.84! If Asus has no newer Bios version, you have to take drivers from an nForce package lower than 6.66.
  5. Hi Willdoicu, thank you very much for your posting. Your comment verifies, that the method described in my first post works even with mainboards, which have an nForce3 chipset. For other users with an Nforce3 SataRaid or PataRaid system would it be very helpfull, if you would answer the following questions: 1. Do you have an nVRaid array with S-ATA drives or P-ATA drives? 2. Which nForce chipset driver version did you use? 3. Which subfolder (SATARAID or PATARAID) did you use, when you integrated the textmode drivers? 4. Did you change something within the TEXTSETUP.OEM file? If yes, what? CU Fernando
  6. Have you tried it with the PATARAID subfolder (from the nForce chipset package 6.66)? Although you have no Raid, there is a SATA driver (nvatabus.sys) within that folder, which is suitable for nForce3 chipsets. Please post here the result of your work. This way you can help other users with an nForce3 SATA system.
  7. Do you have a Raid array? If yes, you can do it as I explained it in post 1 of this thread. There is even something said about users with an nForce3 chipset mainboard. You can take the SATARAID drivers from the nForce chipset driver package v. 6.66. nForce3 Sata controllers are supported by that drivers. CU Fernando
  8. Yes, but nLite Beta6 does not work with XP x64. Look here: http://www.msfn.org/board/index.php?showto...ndpost&p=383241 That is the newest version of what you have done. If this one is correct, why did you write, that it is necessary to copy the nvatabus.inf and the raidtool into the SATARAID subfolder????? Yust be happy with your XP with integrated nVRaid drivers. As you may have seen within this thread, other users with an nForce SataRaid system are not so lucky as you.....
  9. You are right, it's already out of the download page. Send me a PM with your eMail adress and I will mail it to you.
  10. @ Dale: Thank you very much for your several posts. I know, that you really want to help us all, but, I'm sorry to say, your posts are a little bit confusing for me. Once you wrote this: Then you wrote this: Within the next post you propose this: Your next idea: And this was your last recommendation: At least I decided to do exactly, what you recommended within your last post. Result: Endless reboots! Dale, please think about the following: 1. There is no need to help me, but others. I don't have any problem integrating nForce SataRaid drivers into a bootable Windows XP CD (see Post Nr. 1 within this thread). What I am trying, is to search for an easy method for those people, who had no success with the full integration of these drivers by nLite. 2. Your message, that the integration of nVRaid drivers is fully supported by nLite Beta6, is definitely wrong. Fully supported means, that it can be successfully used by all users with nVRaid systems and no special preparations of the files/drivers/packages are necessary. Even you have done some "handmade" changes or preparations of the driver folders and special nLite settings (although you do not know exactly which ones). 3. If there really would be a need for the raidtool folder within the SATARAID folder, no user with an nForce SataRaid system could install XP via F6/floppy method (not enough space on the floppy). 4. The main problems for users with nVRaid systems are resolved, when they want to install Windows XP. The new version of nLite (Beta6) makes it very easy to integrate the awfull NVIDIA drivers into the 32-bit OS. But there is still a lot to do for users, who want to integrate the native 64-bit drivers into an 64-bit OS. Please help us to find an easy solution for Windows XP x64! CU Fernando
  11. That seems to be an interesting method. I will try it tomorrow. What I cannot understand is, that you wrote you were able to create a Windows XP CD with integrated nForce SataRaid drivers by using nLite Beta6 without any "handmade action" .
  12. Yesterday I tried to integrate the nForce SataRaid drivers into Windows XP x64 by using the new version of nLite Beta6. The first test was made without any "handmade changes", the second by using the same method I have described for the 32-Bit version of Windows XP. Both installations were stopped by an error message at the end of the Textmode part. Details can be seen here: http://www.msfn.org/board/index.php?showto...ndpost&p=383069 Nuhi already knows about these findings. Maybe he can find a solution for this issue. If anybody succeeded using nLite Beta6 with XP x64, please report here.
  13. My board has an nForce4 Ultra chipset (DFI Lanparty NF4 Ultra-D). For my last tests I used the 6.66 driver package too (the nvatabus.sys is not WHQL!). Since I use nLite Beta6, I take the default options for the unattended install (with activated "Oem Preinstall" and as "FullUnattended"). This weekend I will try it the way you have done it (precopy the nvatabus.inf into the SATARAID subfolder and with disabled "Oem Preinstall"). As you may have seen some posts above, just to take the PATARAID subfolder does not work for me. EDIT: I just tried to integrate the SataRaid drivers by the way dale5605 had described above. I copied the nvatabus.inf into the SATARAID subfolder, integrated the drivers from the SATARAID subfolder as textmode drivers, deactivated "OEM PreInstall" and choosed "GuiAttended Install". Result: Endless reboots! So this is not the solution for all users. CU Fernando
  14. I am not sure, that there is no need for the $OEM$\$$\OEMDIR folder. AFAIK is the presence of the NVATABUS.INF file not very helpful during TEXTMODE section, but necessary during GUIMODE section of the installation. Tomorrow I will test it by copying the NVATABUS.INF file into the SATARAID subfolder, before integrating the SataRaid drivers as Textmode drivers. Nevertheless should "nvatabus.inf" been added within the [OemInfFiles] section of the WINNT.SIF for systems with nForce4 SataRaid . EDIT: As Nuhi proposed, I just tried to integrate the drivers from the PATARAID subfolder (which have NVRAID.INF and NVATABUS.INF inside). The result was: endless reboots. But I was astonished, that the OS install routine detected my SataRaid Array within TEXTMODE part of the installation. As I recognized now, nLite Beta6 does integrate both INF-files into the [OemInfFiles] section, when you integrate the PATARAID instead of the SATARAID drivers. But due to a reason I don't know, the full integration of the nVRaid drivers is not realized by nLite Beta6. So we have still to do some manual work.....
  15. I just tested, if the new version Beta6 of nLite has brought the full integration of the NVIDIA SataRaid drivers. The bad message: The installation of Windows XP with an unattended install CD created by nLite 1.0 Beta6 failed, because I got again my wellknown endless reboots at the end of the installation. The good message: Because of the integration of parts of the [OemInfFiles] method into the Beta6 version of nLite, it will be easier than ever to get a perfect Windows XP CD with fully integrated nForce SataRaid drivers. As a result of my findings I modified the description of the method in post 1 of this thread. I am nearly sure, that the problems with the nForce Raid drivers will be resolved by the next version of nLite. CU Fernando
  16. Look here: http://www.nlite-guide.com/index.php/NLite...usf%FChrlich%29 Here is the link to the German nLite forum: http://www.german-nlite.de/index.php?act=idx
  17. 1. If you can install your nVRaid drivers with F6 and floppy, you do not need to create an unattended install. An "unattended install" does not mean, that everything is done for you during installation. The installation routine lets you choose the partition where the OS should be installed and you can decide, if you want to format this partition and the file system (NTFS or FAT32). 2. Please read the nLite FAQ, if you do not unterstand the lines in WINNT.SIF. As I know, that you are German, here is my description in German language: http://www.winfuture-forum.de/index.php?sh...ndpost&p=362434 CU Fernando
  18. Did you really read in my description, that you should create a file named WINNT.SIF? You should make an "Unattended Install CD" by nLite and - as a result - nLite creates a file named WINNT.SIF. Then you can add the lines you have written into that file. CU Fernando
  19. It has nothing to do with the integration of the nForce SataRaid drivers. There is a mistake in WINNT.SIF. Make a new nLite CD. CU Fernando
  20. The easiest way is to create a new partition within your Raid array.
  21. Congratulation! The boot manager for multiple boot systems is the boot.ini. You will find this file in the root of your boot partition (normally C:\). It is very easy to edit this ini-file from each partition.
  22. Have you been successfull with the installation of XP x64? Where did you install the OS (which partition)? What is about your "data disk"? Is this a normal hard disk device? Has this "data disk" something to do with your Raid array? Did you plug it in after the installation of XP x64? Write, what you have done. Otherwise we can't help you.
  23. 1. You see the OEM-Preinstall option, when you open the section "Unattended Install". 2. Use nLite 1.0 Beta4.
  24. Take these ones, if you have an AMD nForce4 chipset. Before you start installing XP x64, be aware, that you have flashed the latest BIOS version, because the new nVidia Raid drivers need the nVidia Raid BIOS version 4.84.
  25. 1. The latest NVIDIA nForce chipset driver package is v. 7.13 (unless it is specified for SLI Intel chipsets). 2. The WINNT.SIF is created by nLite, when you choose the unattended install. If you stop nLite before it ends the processing of all requested tasks (integration of drivers etc.), you will not see a WINNT.SIF. 3.When you are going to integrate the drivers, there is an option "OEM Pre-Install". Let it as it is (activated), when you want to integrate the SataRaid drivers.
×
×
  • Create New...