Topic: FEEDBACK: Ideas concerning nLite and driverpacks
This is addressed to Bashrat since I cant find his email.
I like that you've added the GUI, much more pleasant to work with than the scripts. Though as a user of nLite and someone out to create an ultimate windows XP install CD, it occurred to me that it would be time saving if you could get in cahoots with nuhi and work out some sort of stage in the nLite process to integrate driver packs.
On the sound driver packs: have you considered making one pack for built in sound solutions and another for cards? Your current setup is very close to that already and this way seems better as it conveniently splits the packs into a physical decision (do i have a built in card? will i add one? will this CD be used for a comp that has one?) once the person answers those 3 questions they dont have to worry about the other pack.
You might want to rethink your driver update/cataloging method. Don't get me wrong I love that you've singlehandedly collected most drivers anyone could want, but have you though about how draining and inefficient that is? You not only have to find them all yourself but you also have to constantly get the new ones and update them, and of course update the driver packs in turn. You've gotta admit that someday you won't want to do that anymore and most Bâshrat the Sneaky driver pack users will kinda be left hanging (obviously its not that incredibly hard to do but unless SOMEONE keeps things up to date).
One idea I had was to create a program or website where people could, following guidelines, submit drivers which could then be added to the packs which could be released weekly or something. Another advantage of adding a layer like this would be driver rollbacks, if a driver was found to have issues you (or if you made this open someone else) could just select the previous driver instead of the problematic one and the decision could automatically be made apparent in the pack content list. Something like this would also give the ability to filter by other criteria such as WHQL certification. At any rate you wouldn't be responsible for hunting down the latest driver releases and ensuring that your packs are up to date.
Also if you DID get something with nLite worked out and you DID create this user-dependant-submission-interface working it could give people the ability to just select the drivers they wanted for their own computers and then have an install disc customized for that computer (not practical I know but some people might want it).
Another idea is to change the driverpack distribution model to a bit torrent based system, if you integrated a basic BT client into your driverpacks BASE users could ensure they had the latest packs on hand with the click of a button and your bandwidth needs would drop considerably (you could even use some other tracker than your own).
Last edited by Bâshrat the Sneaky (2006-07-26 03:31:14)
