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. I suppose you mean patje's 'Mobility Modder'? Well, yes, it works just fine, but it doesn't support all cards yet. And you can only add support for one card at the time! But on my request, patje will add the possiblity to add support for all cards at once! So I'm waiting for that ATM... So you'll have to mod it manually if you want support for your card...
  2. Well, I'm not erik, but... Already 1 positive report... another advantage is that also monitor and printer drivers are installed!!! That's something we haven't been able to achieve with the OemPnPDriversMethod in a correct way.
  3. I'm not saying that you should use my DriverPacks... not at all... I've NEVER heard of ANY problems with this method, when you're using the nForce drivers :blink... It really works just fine. In fact, it's even easier than a silent installation. Please note that it won't work from DetachedProgram (T-39), because the InstallShield Setup needs a complete Windows to get installed...
  4. If everything had went well, all DriverPacks would be online now (well, in fact they are), but unfortunately there was (*IS*) a (minor?) error in Fedit.exe, a small CLI program written by my good helper djbe, to edit the .inf , .sif and .cmd files. This makes it impossible to release the DriverPacks tonight. And what are the DriverPacks without the DriverPacks BASE? As a note: all DriverPacks (except DPs BASE) are now ~145MB, so 56k users, be aware! If all goes well, you can expect everything online tomorrow night!
  5. Yes, but you don't actually have to install Windows, of course...
  6. I changed the topic title for a better description. Don't shoot me, schalti! EDIT: and now some good reason for this post (this edit was planned of course ): I added the option to let Windows keep the drivers or not to the DriverPacks BASE!
  7. OK, I don't know if you guys noticed, I think not, but please check this newly stickied topic: http://www.msfn.org/board/index.php?showtopic=43795 I think it's better, because it's already fully operational, plus it's very easy in use. What do you guys think?
  8. :blink Well, that is the EXACT entry that is in the txtsetup.sif file :s I guess it gets another hwid when it gets into windows???? (however that would strongly amaze me) Please check this: boot with your current uwxpcd, and tell me which id is assigned to those partitions/harddisks: whether it is 'pnp680' or 'pnp680r'. That will proove my right or wrong!
  9. ... and they're added to DP Sound B V5.04.3.
  10. Could you please tell us the hwid of your pnp680r? If I can add them, that will definetely fix the problem You can find it with tools like Everest Home Edition or devcon.exe.
  11. Indeed! And this has been asked numerous times before AND you've posted this topic in the wrong forum... Search better next time Topic moved to Device Drivers
  12. Poll ended. The conclusion: 1) there is enough animo for an English-only edition; 2) it's not worth it for DriverPack Sound A: not all of these drivers are available in an English-only edition; 3) however, it is worth it for DriverPack Graphics A, so there will come a English-only edition for this one!
  13. It's not 2400 people... it's 2400 views... of which easily 75 from me But you're definetely right Stickied!
  14. Why would you want to do that? Then the nVidia nForce drivers would get installed on ALL systems... It's easier to simply install them using the OemPnPDriversPath in your winnt.sif
  15. @BAM: this is really strange... Tell me when you've found a solution! @the_unknown: I removed drvindex.inf patching because I thought it was unnecessary... ****, I'll re-add it... @larciel: superb @iwod: you can first run with an unedited version of the DPs BASE - without ANY DriverPacks, then all DriverPack files will get removed. After that, run your modified batch files. Or wait for the next version of all DriverPacks. If all goes well, that will be for tonight!
  16. Thanks for the confirmation. djbe is working on a new version of AddLine.exe, that can add multiple instances of the same entry to different sections. That will get it fixed
  17. Do I get this right? A VIA audio utility, while you're using a nVidia nForce 4 mobo with onboard sound? Can't be correct P.S.: you've made a double post...
  18. Huh? I already told you how to do it, MtK... You should just put all the files in the I386 directory, also the portcls.sys file. You can compress them if you want. Then add the necessary entries to the dosnet.inf file. (Check RyanVM's updatepack manual instructions for that) Last, but most importantly: add this to your dosnet.inf file: [ForceCopyDriverCabFiles] portcls.sys and the new portcls.sys in the i386 directory will be used. Of course you could also just use RyanVM's updatepack, which will simply update driver.cab...
  19. layout.inf is digitally signed... You can't edit it without getting errors. Unless you hack some file(s), but that makes it harder again... But I thought it was complaining about filesize? EDIT: I mean, your error message has changed?
  20. 3 is the original setting. I thought it might cause trouble in some special cases... (like setups initiated through winnt.exe/winnt32.exe?)
  21. Thanks for that report You're right on all statements
  22. Thank you for your donation If it's complaining about wrong filesize, please check the dosnet.inf file for a [ForceCopyDriverCabFiles] section. Check if aliide.sys is listed there.
  23. Why don't you try the Windows XP drivers? Probably they'll work just fine
  24. They're added in the new version
  25. DOH Please DON'T PM and POST at the same time! This is wrong: PCI\VEN_105A&DEV_3375.DeviceDesc="WinXP Promise SATA150 TX Series ™ IDE Controller" it should be: PCI\VEN_105A&DEV_3375="WinXP Promise SATA150 TX Series ™ IDE Controller"
×
×
  • Create New...