Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

Bâshrat the Sneaky

Member
  • Content Count

    5,580
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by Bâshrat the Sneaky

  1. Is it an A-brand pc? (HP, Toshiba, Dell, Acer, ... ) If so, please tell me the model number.
  2. Sorry, no can do, I stick with the official drivers. You won't notice the difference in performance probably, and this breaks WHQL signing, so I won't apply your request. Topic closed.
  3. Support will be added, after my June exams probably.
  4. The problem with those newer beta drivers is that they are ONLY WHQL certified for the latest devices... No WHQL for the older ones... shame on you, nVidia.
  5. I hope the latest nVidia driver supports all devices at once, if not, I'll have to add both the newer driver that supports only the latest devices (6 series and up) AND the older driver (2 series and up to mid-7 series).
  6. This means their .inf file isn't written 100% correctly. I COULD fix it, but that would break WHQL signing. Are you sure your device was enabled during installation (during that reinstall)? It'd amaze me if the driver itself would disable the device, but ... everything is possible in Windows Please post your HWIDs, so I can verify that your WLAN device is indeed supported by that driver.
  7. The value that SetDevicePath.exe changes is (if I remember well): HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath Topic moved to DriverPacks General Discussion.
  8. What's the exact issue? (So I know why ATI told you to update your SiS AGP driver...) Moved to Device Drivers forum.
  9. Please read the tutorial on how to make your own DriverPack. Make sure your filename(s) is/are compliant with the rule. If I may ask: why would you want to change that? Just stick to the default directories, if you don't, you'll have to figure out problems yourself.
  10. Eh... I've already contacted Sereby more than a month ago and I've just added support for detecting his UpdatePack: serepack.inf/.in_ is the identifier for that pack. And for what it's worth... KB888111 is compatible with Windows Server 2003, but only if Service Pack 1 is slipstreamed. That's also all implemented in the next version, of course.
  11. If not many bugs are found and everyone reports a succesful installation: this weekend. No features are being added anymore, everything is finished. Pure debugging.
  12. Very odd indeed. I suppose you're only using ONE monitor, by the way? Please post your HWIDs as well, that should help finding the cause. (Check my sig for a tool to find 'em.)
  13. Why there is an OEM folder: http://www.uawiki.org/doku.php?id=wxp:ua:d...ers_from_cd_dvd
  14. I suppose you're quite experienced with Sysprep? If so, please contact me at BashratTheSneaky AT gmail DOT com. I was indeed about to start looking for someone who could help me in the process of adding support for that platform.
  15. Could you please make a screenshot to clarify this issue?
  16. In the next version of the DriverPacks BASE (the one that's in beta currently), there will be full support for Windows 2000, XP and Server 2003. This implies that I've fixed everything regarding default included mass storage text mode drivers.
  17. On parle seulement l'anglais sur ces forums-ci. Please ask your question again, but in English - AFTER you've used the search function. Welcome to MSFN!
  18. So what DID you modify then after slipstreaming my DriverPacks. I think there must be SOMETHING...
  19. I agree, it must be files with a certain pattern on which makecab.exe chokes... And then not even always, but only on systems with a certain version of a certain file, etc. It must be something like that...
  20. Your order is correct, but that is a very weird error. Never seen it before. Google gives also extremely little hits. My only suggestion is: rebuild your disk... And do everything step-by-step, and test between each step. Though my first guess would be that your CD/DVD is corrupted. IF it's written on a CD/DVD (or a rewritable), then you could try again after writing the ISO to a different disk.
×
×
  • Create New...