Hey
what's an open mind to be like?
I am not going to dive in like way back, at least not like I did in XP.
I came to DriverPacks for XP from out of the blue, as it were... and you know..
Way back when, you perhaps asked about how it got done because this was something that was potentially MUCH more worthy than a mere fleeting thought you had that day... few helped.
Nowadays, I still see people around who believe in what they started to believe once a few got to explain how we needed to explain how it got done, and how much help we really needed to help you help us help you.
I really need your help now.
I have a few niggles in setup, and I truly think there is a way to make a DUMB setup smarter.
And yes, in my question, it is all back to chipsets, hard drive controllers, and of course, LAN. (not neccesarily in that order)
I will need to get up to speed about how you guys nowadays filter out (script around)
I have NO idea about the inbuilt (on DVD.. once LAN is established, MSHQL has a massive base)
Back then, it was not so easy to get what was not supported by MSFT, and I still assume that the driver writers make the same goddamn assumption that all old hardware is """supported""" by their newest (even is it isn't)
I know Jeff know what this is about.
I don't know what the situation is right now.
Do you want me to spend six months to do the final XP sp3 pack so as to get back to learning how it is done?
h*ll, I have not even tried DriverPacks in a win7 install yet.
Does it work?
Should DriverPacks base try to do what other open source program groups try to do?
I personally think that there is a way to make myself useful again.
I know I gonna have to le&rn big time.
(hyll, I know more questions than answers.. you guys teach me how to answer them. It's that simple.)
show me what to test, and I'll try.
The answer was 42?
Kind regards, Jaak.