Jump to content

Bâshrat the Sneaky

Member
  • Posts

    5,580
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

Everything posted by Bâshrat the Sneaky

  1. Request implemented, topic closed.
  2. Some patience please! I'm not getting paid to do this and I still have school too... Your winnt.sif file is incorrect. Please merge both OemPnPDriversPath entries, right now the second one is overwriting the first one when setup reads the file. EDIT: the drivers you've added yourself manually, are also included in DriverPack Chipset and DriverPack Graphics B... It's easier if you use ONLY DriverPacks, no more manual slipstreaming. You can always create your own custom DriverPack, which makes slipstreaming alot easier! You can find a tutorial right here[/url.
  3. Problem solved in DriverPack Graphics A V6.02 & DriverPacks BASE V6.02.1. Topic closed.
  4. That problem sounds really weird! Maybe you removed some critical system components with nLite?
  5. @midiboy & 5eraph: thanks! Fixed in DriverPack Graphics A V6.02.
  6. Request implemented, topic closed.
  7. It was yet another typo in the config files. /me dreaming of the moment where all of that will be fully automated... *sigh*
  8. You seem to be correct, according to this page. I'll add this driver to DriverPack Graphics B V6.02. Request implemented, topic closed.
  9. Your first link is indeed the nForce 4 SLI X16 driver, but works for both the AMD and Intel platforms. The second link links to the Windows x64 Edition driver. Request implemented, topic closed.
  10. Are you VERY sure about that performance difference? SiS' chipset drivers haven't been updated since... a VERY long time, so I'd doubt there's any performance difference. (*IF* the drivers you mentioned are even newer than the default ones included in Windows XP...) I would want at least one other person to confirm this.
  11. Request implemented, topic closed.
  12. Yes there is support for the nVidia nF4 SLI X16, but the driver indeed needs to be updated to the latest version.
  13. But did the graphics driver itself get installed? If not, please post your HWID...
  14. As I've told you in a PM, gilesw, please submit the tutorial above to the uAwiki!
  15. All DriverPacks unzipped should give you a total size of ~860MB, not ~1300MB... Using method 1, it should be around 350MB.
  16. Well the website is now on a server protected by some Cisco stuff to prevent DDoS attacks. Probably your IP has been marked as a possible zombie-pc's IP. My suggestions are: scan your pc for any malware and possibly reinstall ityou were just unlucky: renew your IPThere's nothing I can do about it...
  17. I can tell you the error described in the first post of this topic is one that I have not yet seen before: I suppose it's an error on the CD-R(W) of that guy or a data corruption of another kind. He should restart from scratch.
  18. Sorry, it's being caused by your RAM, according to the MSKB. It's the 0x7B BSOD that refers to a buggy/wrong driver.
  19. Actually it's kind of a mix between 'used more frequently & updated more frequently' and 'used less frequently & updated less frequently'. But the main reason was bandwidth. The conditions above only determined which drivers would get in the A pack and which ones in the B pack.
  20. Maybe you don't have admin rights?
  21. Did you enter the 'www'? ...
  22. Please download the DriverPacks BASE again... it seems it got corrupted somehow. (You should only redownload the DriverPacks BASE ... no need to download all DriverPacks again!)
  23. No, simply wait for the next version
  24. It *SHOULD* be 6.01.1... fixed it right away. AGAIN an error : that's why we're automating everything now... Did you slipstream the DriverPacks again completely or did you just copy/paste over the old DriverPack Graphics A? Note that for V6.01.1 of DP Graphics A, the BTS_DPs_finish.cmd file also has been updated!
×
×
  • Create New...