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 agree, but point 2 might only be correct for you, if you want to install Windows Server 2003. Because of the lack of a LEGACY subfolder within the package 6.69 normal users have to add some files off the 6.70 package (see my first post).
  2. You should not take the drivers off a CD or DVD, which was already built by a tool like nLite. Why did you do this? This makes no sense. The OemInfFiles method does not work with the RC versions of nLite. The best nForce driver packege for your board (I have the same) is the 6.70 one.
  3. If you want to install a 32-bit OS like Windows XP or Windows Server 2003 you have to take one of the 32-bit nForce driver packages (look into the first post of this thread). As the NVRDX64.SYS is a 64-bit driver, the 32-bit OS cannot install it.CU Fernando
  4. I am sure, that they are not necessary, but nevertheless you may add them if you want.I think that either your system does not comply with the requirements of the driver integration method layed down in my first post (overclocked system, ACPI not enabled or nVRaid BIOS version lower than 4.84) or you have a hardware problem which has to be resolved first. Here is another nForce SataRaid driver integration method you may try:http://board.vitaligraf.de/showthread.php?...id=1011#pid1011 Good luck! Fernando
  5. Please give a short description about your system (mainboard, chipset, hdd's). Where did you get the drivers from? Who had created the string D:\UWCD\$OEM$\$$\OEMDIR? It seems, that you sampled all drivers from another CD you had created before with another tool (CD Creator?). If you have done this, you have made a big mistake. What have you done before and why?You have to integrate the drivers from the original driver folders, not from a CD with integrated drivers. No, the IDE (=P-ATA drivers) are included in the LEGACY subfolder of the nForce SataRaid driver package.
  6. Burn it at 8x or 16x speed, if you have a CD burner with a maximal speed of 48x or 52x.
  7. Maybe the burning speed was too high. Burn another CD with a lower speed.Have you tested your RAM sticks with MEMTEST? If not, do it. Try the install of Windows XP with only 1 RAM stick.
  8. You probably have a hardware or a CD problem.Are you sure, that your CD drive and your burned CD are ok? Please give more details about your system (graphic card, soundcard, IDE and USB devices etc).
  9. Thank you very much for this clarifying post. When a newbie reads the pages of this thread, he may get the impression, that the majority of the users did not succeed with the driver integration according my guide in the first post, but this impression is absolutely wrong. Most of the readers of this thread don't give a feedback, when they succeed with the integration of the nForce SataRaid drivers, but they do it, when it fails. In nearly almost cases this failure is due to a hardware problem or a mistake, which was done by the user himself (for example not doing what was layed down in the first post of this thread). Thanks again, bogd! Fernando
  10. The Windows XP setup may have asked for a file named "NVATA.CAT", not for a CAB file. As the NVATA.CAT is not necessary for a successful install of Windows XP onto an nForce Raid array, when you are using nLite, you can choose "skip", if the pop-up window comes up again.Which nForce driver subfolder (LEGACY or SATARAID plus some extra files) did you integrate? Did the Windows XP setup detect your Raid array correctly (as 1 disk)? What chipset does your mainboard have?
  11. What are the details of your system?Do you have a Raid array or a non-Raid Sata system? Did you enable the Sata and Raid Controller within BIOS? Are your drives detected by your BIOS?
  12. Sorry, I misunderstood your first post.If the installation fails at the beginning of the GUIMODE part, you probably have a hardware and not an nForce SataRaid driver problem. You can verify this by trying to install XP via F6/floppy and using the nForce SataRaid drivers off the 6.53 package. Have you put off all unnecessary devices? No overclocking? All cables ok?
  13. If you want help, you should betray some details about your system and the nForce SataRaid drivers you have used. Which program do you mean?
  14. Hi Tony,I am sorry, but I have no experience yet with nVidia nForce Pro 2200 (CK804) and nVidia nForce Pro 2050 (CKIO4) chipsets. Maybe this will help you: 1. There is a new BIOS for your MB dated april 7th. Did you try this new one? 2. As your MB has an nForce pro chipset, I would recommend the special pro drivers v. 6.70 from here: http://www.nvidia.com/object/nforce_nf_pro_winxp_6.70.html Please report here about the results of your driver integration efforts. This may help other users with similar nForce chipsets. CU Fernando
  15. Look here: http://support.microsoft.com/kb/314474/en-us
  16. As you have no nVRaid array, my guide (post 1 of this thread) is not useful for you.You should try to install Windows XP x64 without F6/floppy method. Normally Windows XP x64 will detect the SATA drive. After the successful install you may install the nForce4 S-ATA driver (NVATAx64.SYS) by updating the IDE ATA/ATAPI Controller within the device manager. If you want to use nLite for the creation of a bootable XP x64 CD, you should not integrate the nVRaid driver (NVRDx64.SYS), but only the nForce4 S-ATA driver (NVATAx64.SYS). Grrr... that is the most stupid thing I have ever heard! Why do they do that? Ah. I get it. They want to sell a new OS for those who don't have a 64bit CPU too. I just hope that the 64bit version will be pushed harder on the markets than the XP64 one ever was.If you like it or not - within some years you won't work with a 32-bit OS anymore. Do you like 16-bit operating systems? If yes, do you still work with DOS?
  17. Did you try to boot in safe mode (by hitting F8)?
  18. This pop-up window is nothing to warry about. It appears in that moment, when the MS setup routine detects the correct hardware device (nForce S-ATA Controller). If you mean the swapping of the MS Dual Channel IDE Controller against the nForce4 Parallel ATA Controller, this is a total normal behaviour. After a reboot the exchange of the devices and drivers should be done and everything will be ok.
  19. Hi Fetcher, why are you so anxious? You should not "jump" to a 64-bit OS, you should try it on a parallel partition with Windows XP. There is no risk if you do that. If you want to wait for Vista, you have to wait for a long time (and Vista is developed as a 32-bit and 64-bit version too).
  20. Your conclusion is wrong.As the nForce Serial ATA Controller and the nForce Parallel ATA (=IDEs/w) Controller uses the same driver named NVATABUS.SYS, both hardware devices and the related nForce driver are automaticly installed during XP setup. The nForce IDE (=P-ATA) driver works well with almost all IDE devices (CD-ROM/DVD). I personally have never installed the MS standard IDE drivers. When you get no access to your CD-ROM/DVD device (unless having flashed the newest firmware) after the installation of the nForce P-ATA driver, you can easily substitute this NVIDIA driver by the MS Dual Channel IDE Controller drivers: 1. Open the device manager and open the section IDE ATA/ATAPI Controller. 2. Rightclick on the Nforce Parallel ATA Controller und choose "properties" 3. Click "update driver" 4. Choose non-automatic search and enable "show compatible hardware devices" 5. Now you will see the 2 compatible devices, the nForce P-ATA( = IDE s/w) and the MS Dual Channel IDE Controller. 6. Choose the MS driver and reboot. You can check the substitution of the IDE driver by having a look into the device manager > IDE ATA/ATAPI Controller. The nForce Parallel ATA Controller will not be listed anymore. CU Fernando
  21. I think, that this should work (unless you will have wrong driver dates, when you look into the properties of the nForce4 S-ATA Controller driver, you can correct hese dates by editing line 11 of the NVATAX64.INF).If you want I can send you a modded SataRaid driver package via eMail. CU Fernando
  22. Thank you for your clearification.Some other users had reported the same thing, but the big majority was not able to install the newest nForce SataRaid drivers with an nVRaid BIOS lower than 4.84. There is a big variety regarding this point between the different mainboard types. CU Fernando EDIT: You should correct the link you posted. The mistake was, that you added the URL twice.
  23. Hello Vash,did you read the first post of this thread and did you realize, that you posted into the nLite forum? What do you want to say with your posting? I don't understand the message. By the way: The link you posted does not work. CU Fernando
  24. 1. Try the nForce3 Raid drivers off the chipset driver package 5.10 or 5.11.2. The nVRaid BIOS is a part of the mainboard BIOS. So you have to flash the newest mainboard BIOS to get the chance of a newer nVRaid BIOS version. CU Fernando
  25. Have you tried to boot in safe mode? 1. Both CAT files are within the driver package I have sent to you.2. You should not remove the SCSI/RAID drivers.
×
×
  • Create New...