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. Huh? Did you repack my DriverPacks? Because they HAVE to be in the OEM folder when using this method! And if you don't, then you have to edit the presetup.cmd, which you haven't... I see you're using some sort of hybrid method here... My DriverPacks + drivers in $OEM$\Drivers. Move your drivers to $OEM$\DP and everything will work if you use my default settings
  2. @RogueSpear: did you already check this topic?
  3. Updated 17th of February 2005 BTS DriverPacks BASE V5.02.6 Download! V5.02.6 (17 Feb 05) -Fixed: problems with 3ware drivers installation and the "IDE CD-ROM (ATAPI 1.2)/PCI IDE CONTROLLER" bug -Fixed: the cleanup. Now the Control Panel batchfiles will work when using method 1. -Fixed: I386_original folder not deleted when using Method 1 -Fixed: feature: 'original I386\*.sy_ driver files restored (because DriverPack MassStorage N/A)' when using method 1 Now everything should work smoothly... I know I said this already before, but this time... I'd really be astonished if anything didn't work properly....
  4. Please just remove that entry DisableDynamicUpdates=Yes and try again. I don't have it and it has never searched for drivers... EDIT: what is that image in your signature?
  5. Of course! I'll add support for them in the next release. I don't promise to make another version this month, but you can expect it for sure in V5.03 (March)!
  6. It's something like 'DynamicUpdate=0' if I remember well... Please check the deploy.chm to find the correct entry.
  7. This bug is fixed. Will be included in V5.02.6 (not yet available)
  8. Are you using my DriverPacks? They use the folder DP, not Drivers! And did you also make the necessary changes in the presetup.cmd file?
  9. Hmm... any idea what the difference between those two is? PS sorry for the late reply... working on my DPs lately, lost track of this topic..
  10. I think I've fixed the "IDE CD-ROM (ATAPI 1.2)/PCI IDE CONTROLLER" bug: two entries of the txtsetup.oem file still had 'dll=' while it had to be 'inf='.
  11. Did you use nLite? Did you remove some system files?
  12. I won't add any options to (de)select drivers. If I start with that option for ONE driver, I will have to add it for all of them, and that's the opposite of what I wanted to achieve: adding support for as many devices as possible as fast as possible... Believe me, I'm searching to get it fixed!
  13. @moesasji: huh? Now I've really made it /impossible/ that my DriverPacks could cause that... 1) Are you sure you didn't integrate DP MassStorage? Please open your txtsetup.sif and search for 'aac0' (without the quotes) and tell me if you can find it. 2) I'd say apply my DriverPacks AFTER nLite, AFTER RyanVM's updatepacks. @lilweirddude: huh WTF? I've tested this in particular and it worked without any problems... pfff... I'll investigate it again.... @Ghostrider: oh... I will edit that one if it bothers you @erik_demon: hmm... you're the only one and first one getting this error... Please read this KB article. I doubt this is related to my DriverPacks. Please tell me if you formatted your partition before instaling Win XP onto it? @mextrom: same thing as lilweirddude @jeff: hmm... really need to fix this bug, but I have absolutely no clue how @mextrom: LOL that isn't the solution... That way method 1 won't work at all...
  14. My GOAL is a FLAWLESS pack I will keep working on it untill it's working perfectly and then keep on improving it.... @njdouglas: are you using a multiboot DVD? Or anything special? I didn't get that error....
  15. Are there any feature requests? Already requested: -support for online stores (wmlaunch.exe, 120KB uncompressed)
  16. Updated 16 Feb 05 DriverPack Sound V5.02.1 Fixed: Creative Live!/Audigy Control Panels (thanks to mc134)
  17. Updated 16th of February 2005 BTS DriverPacks BASE V5.02.5 Download! All bugs are fixed, except the 'ATAPI 1.2 CD' bug. Let's first see if it still exists with this version...
  18. This one is integrated in the brand new DriverPack Sound V5.02.1 Thanks again, mc134!
  19. I already have a custom setup, that wasn't what i was referring to, i was under the impression that nircmd was what showed the 'Please Wait updates in background" or words to that effect, i wanted to know how to change that box.. ← Errr... Where is that? Please post a screenie. P.S.: then you are in some appropriate topic, I guess... But I've never seen it...
  20. And what has that to do with nircmd? I think you mean customising the GUI setup screen? Look for Setup Billboards in that case... Wrong topic
  21. I don't completely understand what you're saying... What message bar heading?
  22. Now I did a real life install and I still got the same error! What *COULD* be wrong??? All DriverPacks have been confirmed working, only MassStorage is new. But even when you install all DriverPacks except the MassStorage one, this error shows up. So without any editing to the txtsetup.sif file... Anyone any clue? EDIT: FOUND the solution, and it's working! I have to provide the necessary entries under [DATA], then this won't happen. (I was using an empty winnt.sif, to see if it would then work also. So someone who already has a complete winnt.sif file won't suffer this problem.) [Data] MSDOSinitiated = 0 Now all bugs should be fixed... I'll first do a real-life test with ALL DriverPacks and if it works... then you can expect BASE V5.02.5 tonight as well as DP Sound V5.02.1 (with fixed Creative Live!/Audigy control panel!) /crossed fingers
  23. @mextrom: that's the exact same error I'm getting... Which DriverPacks did you use?
  24. Yes indeed! VERY handy! I found it by accident, lucky me
  25. Thanks for your fix! I will update DriverPack Sound!
×
×
  • Create New...