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. Well, ZileXa, you really got a point with your last line
  2. Thanks. Please make your own DriverPack with these drivers (check the stickied tutorial in the DriverPacks General Discussion forum) and tell me if that solved the problem. If it solves it (which is VERY probable), then I'll add them to the next version of DP Sound B.
  3. Because the information Microsoft gives us is apparently NOT sufficient, I've started to investigate the txtsetup.sif file in detail. And what seems? MassStorage drivers of this kind: cmdide.sys = 1,,,,,,3_,4,1,,,1,4 (note the 3_), are 'BusExtenders' and are therefor listed under [busExtenders] witht their according name. Like this: cmdide = "CMD IDE Bus Driver",files.cmdide,cmdide Yes, that's right it refers to the 'files.cmdide' section, which looks like [files.cmdide] cmdide.sys,4 pciidex.sys,4 AND they're listed here: [BusExtenders.Load] cmdide = cmdide.sys This is why I MUST use 3_ and not 4_ for aliide.sys. EDIT: and maybe for more? But how are these determined? Also, I've noticed some very strange things: ipsraidn, nfrd960, symmpi entries in txtsetup.sif that contain the names only, without any files/driversIf anyone can explain me what I'm doing wrong to get these 'internal data structures corrupted' error, please go ahead!
  4. Could you point me to their drivers? I'll add them and the problem should be fixed.
  5. Will be added in the next version.
  6. Well, I discussed this with RyanVM and this is the way he does it. Except that he replaces the file in driver.cab, a feature that I won't add, because that would take too long. This way it should work too (however I had some negative reports about this issue with MassStorage drivers). Please try and let me know.
  7. Yes you can, if you mean the MassStorage section in the winnt.sif file. But then you'll have to copy the files to other locations as well. Check the stickied guide for that (TEXTMODE method).
  8. @SiMoNsAyS: in fact they are not even hacked . If I remember well, you were the one (or one of them) who linked to that guide 'How to hack the Audigy 2 ZS driver', right? Well, that guide only hacked the setup files, none of these files are included in my drivers. The .inf file itself supports ALL SoundBlaster/Audigy devices
  9. @muiz: this error existed for some versions of V5.03 of the DPs BASE, but was solved then. Now this error seems to return, while most of us DON'T have it... I'll try to figure out what's going wrong... ahpt3xx: There are TWO drivers with the name hpt3xx, one Adaptec and one Highpoint. To add both, I HAD to apply this trick. I CABbed one of the hpt3xx drivers as ahpt3xx and changed its txtsetup.sif entries accordingly. @eagle00789: there's another topic running where people seem to have that problem. However, it's not there for most of us (again: how can that be possible?). In that topic rebuilding the UWXPCD solved it. Maybe you could try that too? @muiz: please attach your dosnet.inf, drvindex.inf and txtsetup.sif. That's a critical error that normally couldn't be caused by my DriverPacks...
  10. It starts BEFORE the actual setup starts. So yes, you can use the presetup.cmd as sort of a 'OemPreinstall function'. Without any problems
  11. This will only affect Intel chipsets. Please check the $OEM$\$$\Inf folder for any .inf files. If they are there, nothing is wrong, if they're not there.... then there must be some kind of error somewhere...
  12. Of course there is... Only download DP MassStorage and put it in the DriverPacks folder. The batch files slipstream only the DriverPacks they detect
  13. Thank you guys for your reports
  14. I found that out yesterday too. I have already fixed it and will be uploading a new version tonight, with some other slight improvements. Thank you anyway, zookeeper
  15. Ehm several changes: dosnet.inf, drvindex.inf, single entries in txtsetup.sif (as you suggested, buletov). Check the changelog for details. For S0mE0nesMiNd1 it worked, buletov
  16. YES I'll leave this topic open for more confirmations
  17. The large spaces are default, nothing I can do about it. The aliide.sys error... Still unsolved :'( But I think there's a solution. Are you using it on a ALi mobo? Because I never have that error...
  18. Please mail it to me But don't exclude any .cat files please. I will add them into the next version.
  19. Not sure, but I though that when you use the /integrate switch, it wasn't completely applied untill after svcpack.inf had run. Not then?
  20. How will that be very hard? There aren't THAT much graphic artists or experience nLite users I think. I think it's a really good idea!
  21. Well, I guess removing the older drivers might be the best option then... If you're lucky, nLite could do it for you!
  22. Shortly: check out this KB article And add the right entries to the dosnet.inf file.
  23. Err... Issn't that the obvious? Clearly you have to become a Super Moderator, Administartor, Developer or Reviewer. Those are states you can't obtain by posting, but they'r handpicked! And it seems the group of 'Moderators' doesn't exist anymore. EDIT: oops this post was meant for indianarchie...
  24. OK, found the error: the server is currently down for maintenance. It should be online by tonight (tonight in GMT+1)
  25. Hmm, everything is possible! B) However, if I have to add all SoundMAX control panels... The size of DP Sound B would in the best case only be the triple...
×
×
  • Create New...