Search options (Page 1 of 99)

techdude, for UEFI ports to work in esata, X64 is a MUST, and XP64 dont have UEFI recognition (so it is 7x64 and up)

I dont think I have this wrong, Sir.
Man, I read what you did for us here at DriverPacks.. I am gonna take lessons from you real soon, god willing.

Note to Jeff,
remember when we had to create HWID finder from scratch? The early SED filter I originally used, the russinicof and de microsoft scripting guy tool found less..
Very early on we found HWID that early windows filter (win orig setup) missed, and that got us help from warmsnow (a DriverPacks guru back then)
And so on, and so on.

Our work had kinda eliminated all error driver writers left in by scripting around it, or by culling (pruning) out known conflicting duplicates.

a month later, a new driver for realtek came out, and it had all but two new HWIDS, and a known 7526 conflicts with its OWN legacy drivers.
The problem with driver writers was that they did NOT delete the HWID it was no longer suitable for.

The great job we did was that we had finally figured this out and once we knew what what worked in old and not in new, people like Jeff and Mr Smartepants could script around it.
Finding the culprit duplicates and generics way back when was one step. (I think I can honestly  say I was a great help in that)
Developing software to help filter out them conflicts was not  something I could do.

You know, I came on board by asking a question.
years ater, late 2009 I saw that ideas we'd discussed really got going, and I had a tough time in real life (steelplant issues, health issues)

in 2010 I got in a seriuos accident, and was immobile left side for months. it took 10 month revalidation, and I am still partially invalid.

But my brain started to work again.

Nibus, any driver uses machine language, and help files use what's there.

the crux to SIZE is, the HWID really only needs one set..  of all these languages

There were (in the past) WDM files. them are not needed (all in wdm can be safely deleted)

language for help, is not needed (and that alone will save big space)

default language in windooz in amerikaneez ingleez, and you will most likely NOT see EN folder
(you do know that even British English have to get american ingleez out of our language choices?)

the point is, I figure 3.8Gb from your driver collection are not needed at all.

That was the help I can offer you.

Now I need your help

Can you upload for me to download your collection, so I can filter this for drivers you dont even need at all

say where to, i will DL them next thursday
fellow geek

Hi Jeff, indeed, and perhaps too long.

the public saw me vanish somewhere in 2008 after a few great filtering jobs.
I should have tried to help more in your later TEAM work in filtering out super generics for XP after 2009, but hey, you were one of the team I explained to what I had done, and why, and how it made sense.
And, SOON after, I helped test the filter you wrote in dpBase (so that the repetitive driver writer caused release error findings I had discosed could be filtered out ""more easily"" (but could not be released untested.. somewhere 2009.)

And yes, somewhat later you saw me drop off the earth.
I still regret having done that, but I really had to.
You, above all people,  MUST know DriverPacks was not let go willy nilly.
At the moment I am retired, and after five years of different health issues (an accident that caused 10 months immobillty in between), I am what... not what I was.

Hi,
At first, when torrent distribution became fact (and that a good while ago), I thought we would have some reports from people working in IT that had a rule to work from behind some intra-zone access server not being able to use a torrent client.
But then, well, company I.T. admins can work the permissions so they get what they damn well know saves them LOTS of time.

Individuals, well, nowadays, even if they do not know what DriverPacks can do for them they are are probably wise to what a torrent can do, and if they weren't wise to what a torrent cleient is, they don't run setup.

One of these days I (or we) should update the old tute (2007), to show all what the later Base app can do.
I have been somewhat out of the picture while still using DriverPacks, but, you know, at this time ((June 2011) windows 7 has proved to me that in several machines, it could not install itself without  the extra drivers properly made available to it.

Let's say that way back (until 2010, actually, off screen) I tried make some companies aware of what caused conflict in apparently un-related drivers, and let's say that super-generics are still not gone, but, let's also say that a LOT OF YOU helped figure out how to effeciently deal with that.

You've all helped this project to be of greater use than many would have ever believed possible.
Kind regards, Jaak

hmmm, the $OEM folder still had 347 subs.. 
Your idea about scripting the unzip process could become a fruitless effort.
You see, those INI have exceptions written in them for good reason, and how are you going to handle that?

Hi, welcome to DriverPacks.

I once made a set with all DriverPacks on it and worked on the content of the DriverPacks to get a super short path. One can indeed move files into folders that have no file in there with same name.. .
I must tell you that a dp's INI has to point to the folder you merged files into, so that is some extra work.
It took me some hours to get it right, but I had all packs and a path way under 4096.
The result worked.

Why did we not use it at DriverPacks site? Maintaining the packs would have become hyll for the teams.
Because drivers were thrown in several big folders, it made it hard for the guy who has to update a driver. Where is it? Which files had it? (a driver update may have different named files, and then you'd have remnants of the old in the folder.)

So I had a very useful disc, M1 uses windows setup, so it can be used to repair a broken windows..
I think I still have that DVD and CDR with the supershort M1 path, but I did not see how the team could do the maintenance of the DriverPacks on such a layout.

what I am saying is that it can be done.
There are a few caveats. You have to carefully study what is done in The INI in some driverpacks, since split packs sometimes relied on files in another pack.

if you search the fora here,you may find over a year old posts about what I did.
Best of luck.

Hi,
Let's consider 'past' support by MSFT for XP x64 (which, incidentally, ran like Jolly jumper when powered by a 'quite old CPU' like the Q6600 Erik has in his desktop)
MSFT does not write drivers, and far too many people got bit by legacy programs having to run in either compatibility mode or in a virtual machine..
(I can tell you, and should, that the speed/stability benefit of the X64 OS of the past have shown much greater promise in the newer server 2008 OS and Vista X64, and, YES, also in Win7.)

We are, like mentioned more than once, a small group of people doing this.
The regular old timer with core knowledge may have other interests, or may have a limitation (like too few suited hardware long-term test motherboards).

There was a time people not only spent time, they also availed hardware for longer term tests, and I (speaking for myself) I cannot afford the losses caused by fast depreciation of hardware.
Time... or history.
When you look it over you find A good many core member old timers dropped off long before, and some other will, and still other members will come aboard and become core.
The smart old timer might find he has too little of something. (time, resources, expertise, help, programming skills...)
When I think about this, I know I ain't smart.

now think as a sailor, on other tack.
If I tell you I have too few machines, and limited expertise, that is true.
DriverPacks has grown, and its members helped think of new ways to do things.
There was a time I got carried away, while things were easier.. My personal time and thought was on problems caused bu driver writers.. my free time was dwindling.
Others like I have suffered same. And all of us do it for free.
We help you help.
I still want to.

One of the major handicaps I once complained about was that we no longer had access to a post where the great majority of hardware download sites were referenced.
(we also had/have an understanding that we did not use a site where beta drivers got catalogued.)

so, at DriverPacks, for my personal need (as a wannabee helper...) I have needs.
I (and DriverPacks) need to have as many as possible NOT EDITED drivers, and that possibly means all those we have not yet pruned out.
I need to understand all the differences between the X32 OS in its various Service pack (as in, what is supported in this version of win2000 server gold that is not supported in win 2000 client sp4.. and by extensis, XP32 gold and SP3, Vista gold, and vista SP2.. in 32bit/64bit.)

More to the point, we really need the guru to tell us where, in which files, you find the differences about support.
Do you know why we need YOUR expertise about this?
Because driver writers will not always adhere to the standard for that OS, and our old sore (dupes in variants) is not only about the many OS, but also about the ways drivers get distributed (SAD, RIS, DISC, WWW-windows-update or WUP+RIS)

about WUP.
I have this gutfeeling that MSFT were listening.
Their database.. I wish we had access, and then show them how to do the filter. (or, show where the problem are.)
it has X64.
it has X32,
and it has a problem, because driver writers of the past (and the now) still do not always adhere to standard.

sonbd2, welcome to DriverPacks.

A CD image on hard disk is not the same as an copy you made to a folder.
A virtual CD created by a program acts like the CD. (it cannot be written to. It is not seen as an ISO either.)
The CD in the optical drive, cannot be written to, even if it were a CDRW disk in a burner.

a (or our) slipstream utility can write to a copy on hard disk where you have the content of the CD or DVD, and another utility like Nlite or RVM or Nero can burn to a bootable DVD from slipstreamed content.

I should have asked what DriverPacks BASE and DriverPacks you ran. and the logs.
I did not. I assumed you picked up on what you used, and what you read, and I dare bet there is a year's difference between what you read and searched for.
Get by, and welcome to US. We help you.
We CAN talk layman. We always assume you are a PRO.

Jeff answerd to this, but he put you on the wrong leg.

What do you mean by root folder tally?
Let's do a live test.
I scan OLD DriverPacks (2007) LAN, with the tool I used  (part of utilityscan05.exe / SED too )
I do a tally for root (zero HWID in scan gets filtered out)
I do a tally by DIR pipe.. and find out scan tool has blind spots.
(I double checked by other means, scanner skipped INF, I had more folder in DriverPacks than I got in excel.)

This was what makes your effort needed.
we need a standard, and no blind spots.

I also said;
Q; why are we not standardised.
A; because we have no standard

When I reread this entire topic, I know I sometimes allude to things mentioned in other topics.
(e.g. FAQ "can you edit DriverPack MassStorage" )

I will have a new testplank (that's good)
Right now, I can perhaps spare 18 hours/month for DriverPacks. (That's bad)

Kickarse?
I know you did not do it for the prize I once offered, but the comments our peers make indicate you are eligble to it.
(I am still honour bound to it, and think I still have an English version to ship.)

this BB is daft, no merge post. (I also still hate that edits can be done in a post of five weeks/days/years ago)