Search options (Page 4 of 99)

Hi,
>> DriverPacks Finisher 8.09.rc1 initialized. >>
What I see is an older DriverPacks BASE test build.
DPs_BASE_81127rc.exe exists, and your previous topic may very well have helped Jeff.

Since you seem to be able to find older, and I am not going to link to latest testpacks, it is up to you to decide what you will do.
YOU either find it and be an unofficial lurker/tester (with the risk of spending many hours fishing for answers.. on your own in the dark.), or you stick to official releases, or you OFFICIALLY do what you apparently like to do.

We welcome people with the gusto and means, and you did provide logs in both posts.
I think you have the balls.

>> bombastic previously posted this
http://forum.driverpacks.net/viewtopic.php?id=3294

OTOH, full WIM will NOT install on a lot of older hardware because that is barely sufficcient to run basic XP, and XP will "run" on that, or because they have no good driver.

(server 2008 core can run in 128Mb ram in a VM)

Hi Echo_platoon.
Can you tell us before-hand if this driver presents problems with installing when you do NOT have the hardware?

You are an old timer here and a trusted hand, and I think you have seen that we get some impossible requests.
For instance, when we use driver extraction tools, we sometimes see that nothing the team uses gets a usable driver, and then we either get in a situation where:
1; person with the hardware does not know how to extract the full set of files in usable folder.
2; driver install routine is propriatary to installer and extraction tools cannot extract the main from a non existing main because main deleted temps, and the DL exe wont extract without running that routine.
3:we get no response, and miss only a few files..

Hi
today I noticed that the VMware mouse driver was installed in 'live metal' test in XP. (on a 'el cheapo' asus P5M2E low feature "server" mobo).

The asus mobo has no sound on board and no sound card.
And, windows XP installs standard sound stuff none the less.
Life is fun.
Anyway. HID like mice and keyb are important, and while the mouse works with the VM driver, it struck me as 'very" odd that XP had not used the M$ driver.

edit>
I tried look up what version DriverPack Chipset I used, but I find no names..
Well, this was done with a super short path method one DVD I saved as ISO around June 2008.
(was in a hurry to get that thing running and used an older build.)

----------
@ the team.
I will try put in time and will attempt to collect data from the current Third Party DriverPacks and released main DriverPacks (and the latest main DP nightlies) and can (I hope) do some worthwhile work in excel.

Nobody likes conflicts, and sound/modem/TV/Graphics with HDMI, have sound.
I saw that an excel sheet was left in Third Party DriverPack modem. (with the hilite formula in it.)
This gave me the idea to do more of this.

Hi chud

that post starts half-way Lan (lan\sis) and ends with wan\z4.
it has NO %KTD%\3\

I think the full list would be "at least" twice as long.
(lan is huge and not all of it is seen here.. and DriverPack Graphics A b c mass chips and Third Party DriverPack are not listed.)

Some body will have to look at Third Party DriverPack.
Last time I looked there were some packs with awful long foldernames.

separate post.
suites with configurable AV can be configured.

a basic AV plug-in has no CPL.
I can not tell a OA+ user how to omit  folders 'on acces"
OA FW (no AV) still has a good FW and  HIPS feature.
That in itself is a problem for DriverPacks BASE and 7z.
I use avast alongside OA+.
Hence the need for an other live metal dedicated DriverPacks cruncher.

glad to see my back

hehe, I know what you meant.
(she giggles.. says snuff internet. get a real life. I gonna turn her over to DriverPacks.)

JakeLD will be thrilled.
Thanks.

Jon did a LOT of work
I was out of the loop for a few months.
I know I spoiled you all while I was housebound after surgery.
Jon took up the task and learned hard lessons.

They say these are the best.
I want to say I made more mistakes than he ever will.
I think new DP team members have the advantage of reading about mistakes old team members made.

EDIT
Those errors I make and tell you about in fora are usually caught in private tests.
The errors I missed and learned a LOT MORE from were exposed after I put up a testpack that had not been fully tested privately.

There are a good many tests a testpack has to go through, and I think nobody in the team can do all.
Par Example.
I usually did a VM or VPC test (on one or two OS°) and live real metal (for one or two OS°), and that is very limited.
(the ° stands for SP version)
Well, now consider the fact that nobody here has 150 different types of mobo, and that team members can spend as much as ten hours on testing out all variations the GUI offers on ONE mobo. Then do the maths for the variant OS/SP. (the OS SP version can play a role)...
You'll come to understand there are a good many reasons why a team member has to allow testpacks to a select public, or (what we sometimes do) has to throw it to the wide public.

I personally primarily test disc based install when I get the time and have suitable hardware.
Theory has to get empirically tested, and a release should be tested before release, right?
I still like to think disc based install is prime goal, PE and sysprep are benefiting by the same filtering we do for disc based, and the workarounds that get developed for PE and DPinst are made easier by your reports.

In this topic I aked for powerful filtering of duplicates.
I found out excel 2007 has powerful sort functions.

I found a powerful suite of excel add-ins (Sorry, not free.)
http://www.office-excel.com/excel-addin … undle.html

I found out that nothing one can automise will handle all permutaions, and the human should have the last decision, because of GiGo.
Garbage IN (what one uses as source of scanned file for output.)
Garbage OUT (what one can get if the developer does not corroberate findings to other findings.)

I will reword that.
You know?
AHCI/IDE/RAID/SAS at DriverPacks.net can NOT have overlap in HWID in the DriverPacks and that made life miserable for the driverpack teams.

The rewording is needed here because what we get at the download pages CAN and does have overlap, and we have to make fair (but oft times difficult) choices.
Not too long ago (this started with 7.xx), Intel chose to not support all AHCI in XP in their releases, and later on they offered AHCI for some HWIDs they had previously excluded from support in XP.
We have most likely an almost complete coverage for all modi, but Intel motheboard is not the only motherboard/chip combination, and the proprietary Intel-chip-based OEM chipped moboes found in large OEM branded computers will often have a driver RE-written for their specific modification.
And, we know that OEM RE-written drivers will often have "generic HWIDs" and the proprietary SYSTEMFILE will NOT work ok on standard intel.
That is why we need detail like HWIDs output.

updated. I hope you subscribe to topics of interest.

hi, just a comment about the way you wrote that name.
DP_IntelDriverDell360_wnt5_x86-32_08.11.27.7z
It has too many dots.

DP_myNONtxtModeDriver_wnt5_x86-32_081127.7z

hi,
welcome to DriverPacks.

ql40xx.sys is a QLogic file, and we don't carry it.