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. 1. The DriverPacks BASE is just a collection of scripts that automates the slipstreaming process. 2. See 1. 3. All of that will have been handled by the DriverPacks BASE .
  2. Thanks for your research, 5eraph! There's only one problem with that hotfix of yours: Prerequisites Microsoft Windows 2000 Service Pack 3 (SP3) It seems it's just not designed for Windows XP. Probably it's simply included in Service Pack 2?
  3. DriverPack WLAN V6.02 Changelog: V6.02 (28 Feb 06) -New: support for ALL Ralink PCI WLAN controllers. -New: support for Lite-On WN5401A WLAN controller. -Updated: Dell WLAN controllers driver from 02/10/2005, 3.100.35.1 to 11/02/2005, 4.10.40.0. Download
  4. DriverPack LAN V6.02.1 Changelog: V6.02.1 (22 Feb 06) -New: support for ADMtek AN983 & AN985 & ADM9510/ADM9511/ADM9513 NIC's. -New: support for Netgear FA120 NIC. Download
  5. BTS DriverPacks BASE V6.02.4 Changelog: V6.02.4 (22 Feb 06) -Fixed: [DPB]: RUN_ME.cmd: now you can enter wrong entries without letting the script crash! Download Known issues -none
  6. Probably it won't hurt to add it, but my guess is that it's only necessary for pre-SP2 Windows XP installations. At least, that's what I understand from that IBM article.
  7. Request implemented, topic closed.
  8. Glad it worked Unfortunately there's no easier/cleaner work-around for this nasty issue! Blame Microsoft! Problem solved, topic closed.
  9. What kind of errors do you get? Using which installation system?
  10. Request implemented, topic closed.
  11. Request implemented, topic closed.
  12. It seems only the .reg file is necessary for SP2 and newer: http://www-307.ibm.com/pc/support/site.wss...ocid=MIGR-57463.
  13. Request implemented, topic closed.
  14. Well... it IS supported by the .inf file :s %ATHER.DeviceDesc.1013% = XP_DEV_1013, PCI\VEN_168C&DEV_0013&SUBSYS_04081468 Could you do a manual driver update (through the device manager) and then point Windows to the folder D\W\AT\I (after extracting DriverPack WLAN obviously)? If then it still doesn't find the driver, something is seriously wrong. P.S.: the download link isn't working anymore!
  15. Ehm... the only HWID supported by the WG311T's .inf file is this one: PCI\VEN_168C&DEV_0013&SUBSYS_4D001385 . That means either you suck (nof ), Windows Update sucks or Netgears drivers' suck, since I've got the latest one already included. Probably it's Netgear Downloading the driver again... EDIT: that gave me the same result. Could you please send me the driver that you downloaded through Windows Update? (If I remember well, you can find it in %WinDir%\Downloaded Installations
  16. Request implemented, topic closed.
  17. Google for 'SetDevicePath.exe' if you want an easy-to-use CLI tool.
  18. I know. The fixed version is to be released today
  19. Is it a multiboot dvd? Please provide us with more details! One thing is sure: the slipstream was unsuccessful or incomplete.
  20. Request implemented, topic closed.
  21. That would be the only error
  22. Could some more people with X2 CPU's confirm that this problem exists or not?
  23. Could you please download the tool to get your HWIDs and then run the custom script below instead of the default one? copy, paste in a new .txt file, save as 'getcpuhwid.cmd', put in the same folder as get_hwids.cmd devcon find *amd* >> cpuhwid.txt Then post your result.
  24. There's a space in that path... But it seems the slipstream did work. Please tell me on what hardware you're installing. And switch to method 2, unless you really need method 3 (method 2 is better than method 3).
  25. Don't be so lazy Next time you should look for tutorials first If you still cannot get it to work, open a new topic, because this one is closed now.
×
×
  • Create New...