if i did start a topic in the wrong place i'm sorry let me know and i'll go where i'm told by the powers that be to do pennance .... i figured i would get to the meat of the matter ....... 9xme driver pack solution ........
i have access to probably 10 -20 gig of old drivers with new being found all the time, so i'm going to start building up a database of drivers for 9xme ....... now, if i was to do this, would this be helpful? it should easy enough to unpack withh any number of available unpackers, change the inf and repack but i do have a few questions:
if the driver is based on the wdm (windows driver model) theoretically you should be able to use the newest driver for that hardware on a 9xme box (as long as its 32 bit?), but not be able to use the drivers enhanced features for the newer os for the most part .... would this be the correct assumption?
with the newest drivers being digitally signed, is there a way to bypass or rewrite or hack the signature ( it's gotta be sha'd or some type of hash) or just install drivers offline first
i'm still new to this driver pack thing, i was searching out of necessity for ways to cut down install sizes and deleting multi instances of duplicate files ..... it's called SIS or single instance storage ...... if the driver packs are packed efficiently this way, hopefully the ultimate DP solution could be brought to heel in a 900mb cd which can be read by most older cd roms ..... I wanted to make a win3.x9xme install cd with os install and programs for all os on one cd (like a linux multi-distro full package)
i would assume that there is a lot of duplicate code that isn't hardware specific that can be concatenated to build the driver executable on the fly (or is that a flight of fancy?) i guess what im saying is making the drivers universally modular.
i know its an old subject, but it's like a bad rash, it just won't go away