• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About calderstrake

  • Birthday 01/15/1979

Contact Methods

  • MSN
  • Website URL
  • Yahoo
  1. Just a report. This method did NOT work for me. I created the SVCPACK directory inside the i386 directory and put the files listed above inside. I then created a SVCPACK.INF file and copied the text from above and placed it in the i386 directory. It appears that none of the code executed because when I booted into Windows I did not have IE7, WMP11 or any of the updates installed.
  2. Thanks lokelo for the tip on how to acquire WINDOWSXP-KB892130-ENU-X86.EXE. After some research, it seems that NDP1.1SP1-KB867460-X86.EXE is the same as Microsoft .NET Framework 1.1 Service Pack 1. Apparently, it cannot be searched by the KB number. I'm still not clear what "the file REG.EXE is extracted from the Windows source" means. Is this on the OEM disc or from an active Windows installation? I was able to find the ROOTSUPD.EXE mentioned in a thread in the ms newsgroups. It appears that it is an older version, but in fact the file is dated December 2007, so I think it is the right one. Someone please correct me if I am mistaken. Here is the direct link.
  3. I may have missed some previously assumed information, so I apologize in advance. A few questions on this section... Do I simply download the .NET Framework Version 1.1 Redistributable Package and .NET Framework Version 2.0 Redistributable Package (x86) and rename them according to your information above? If so, do I still need .NET Framework 1.1 Service Pack 1? I could not find the following for download from the Microsoft Download Center. Is there another place I should be look for these? NDP1.1SP1-KB867460-X86.EXE WINDOWSXP-KB892130-ENU-X86.EXE For the REG.EXE, do I simply take the file from a working Windows XP SP2 installation? Where did the ROOTSUPD.EXE come from? Is this the Root Certificates Update hotfix? If so, can you list the kb number? Thanks in advance for your clarification.
  4. I'm curious to know what key words everyone is using to search the catalog. I am simply using 'security update for vista'. Any other words or phrases helpful for anyone else?
  5. I extract the files normally and then 'Insert' the driver in the directory created by the installer.
  6. This is not accurate information in regards to A8N-SLI Deluxe on BIOS 1016. nvraid does NOT need to be enabled if you are merely running SATA drives in a normal fashion. If you want to run a RAID array, then you need to a) enable the nvraid and B) enable the channels you want the RAID configured on.
  7. Yes, it is a sound recommendation which is why I attempted to do that first, but with no success. Yes I am sure. I tested it 3 times and each time I removed the 'Display Drivers' it did not install the newer, integrated drivers. If I remove the 'Display Drivers (Old)' everything works as it should. It only breaks if you remove the plain 'Display Drivers'.
  8. 84.21 Works with RC8; I just used them today. Make sure you don't remove the Display Driver category or it will not install during setup and you will find yourself at the desktop with 2x '!' in your Device Manager.
  9. I am working on a fresh CD using RC8 of nLite to see if I can fix the problem this way. I will let you know how it goes. **EDIT** It looks like the 'make from scratch' method works. I recommend this to anyone who thinks their Windows CD is good. Just do it again, only takes about an hour and you will be happy with the first result instead of spending enldess hours pulling your hair out.
  10. The only thing I added was drivers, so I didn't even get to the selection screen you mention. I installed the RAID as txt and the others as PnP.
  11. -- I realize that this is probably not the correct place to post this information, so please forgive me in advance. -- I am trying to install the nvRaid drivers using nLite, but nLite is crashing my windows install. I have: Asus A8N-SLI Deluxe BIOS 1016 nvRaid 4.84 Windows XP Pro SP2 and patches up to May 06 nForce 6.70 I tried for over 8 hours using every method described in post 1 (Legacy, combo sataraid splicing); nothing worked. At this point, I decded to try using just the chipset drivers to test if it was nLite causing the problem. Guess what, it is. Here is what happens: Windows boots to txtsetup. When it reaches the point of 'Loading Windows Executive', it halts to a screen that reads "Setup could not determine what type of computer you have..." with the only option in the middle as 'Other'. When you press Enter and select this, the following screen says: "The file txtsetup.oem could not be found..." Any ideas?