Search options (Page 98 of 213)

that it the function of the install by HWIDs prep tool that will be integrated into DriverPacks BASE

sndrec32.exe Should be in %SystemRoot%\system32\ and that folder should be in the path.

if either of these things is not true then I would consider that a corrupt install...

Furthurmore
If you intentionaly corrupted it, then
I expect you have the smarts to disable that line in the DP_Inst_Tool.cmd - lol

finisher is deleted after a reboot...

sound recorder is part of windows...
i assume that you most likely removed it with nlite,
or you simply have a corrupt target machine.

The error is not critical as it was just trying to play a ding sound to let you know it was done

Well, it depends whether you refer to SAD or a normal Slipstream with DriverPacks BASE...
The focus of this thread is SlipStream so i will answer assuming that...

the short answer is: We don't install the drivers with method 2... windows setup.exe does it for us.

We simply put them where windows setup can find them just before Windows runs setup.exe on the machine as part of the normal installation process.

Basicaly we pause setup, expand the driver library by two gig and resume setup.

now that windows has a complete library to use during the install it wins (almost) every time.

Some drivers absolutely will not install without their personal setup.exe running...
We use the finisher to address that.
Most drivers therefore will not have a finisher entry (and therefore will not have an INI entry...
If a driver folder does have an entry in the packs INI then that driver/folder is a problem child ...

i hope i understood you correctly...

As far as reducing the size... i already wrote the code for that in the testing team forum...
you were/are there
It is resonable & feasable and likely that hwidstool code will appear as a sub option for each platform...

IE the Alpha of installbyhwidstool is already written
making it a new "Include" or Function is like adding a plugin...

Except for the GUI part... That part is always a mess to deal with...
It is some of the oldest parts that Wim wrote when he was 14,
and this was the first program that he ever wrote... God love him.

if you take a peak at the TO-DO list i updated yesterday you can get a fell for what i think is a priority ATM...
http://forum.driverpacks.net/viewtopic.php?id=71

Since Win7 has promised that all Vista drivers will be compatable with Win7... it becomes a non issue as the Vista DriverPacks Muiz provides will provide full support initially for Win7 naturally we wil migrate those to thier respective official Win7 updates as they are released and tested known good..

I second your motion for a new Windows 7 forum
- So I created the catagory and primary forum.

and moved your thread so it is now the first post in that topic !

Ryan VM Integrator is the prefered choice of DriverPacks
HFSlip is very popular too....
there are literaly dozens of people that provide these packs
Some of them offer support for specific languages too.
many of them are respected freinds of DriverPacks...

that would be true...

that part of the code involves thousands of lines and i don't have every one of them commited to memory

I belive that the tag name if duplicated will result in last driver with that name added is the only driver added (LILO). I am not positive without grabbing a BIG cup of coffee and running some tests and reading the debug output of base. or adding some flags...

But I agree with your assessment that an invalid entry would be skipped (or overwritten)

Either way i look at this like a feature request... it makes sense, Although these files do have a common name they will NOT all be copied to the same source in any supported platform. So they SHOULD be allowed to share a tagname... I just don't think it works that way now.

But I think you can look forward to this being a new feature of DriverPacks BASE, if it is not now...

Falconfour jsut made the ban list too speaking of the other fool for fodder...

you may be correct...
That is only a theory
until i verify that the code actually does allow it,
without messing something up.

I will have to check the bartpe code and other related functions too

Well Thank you for associating us with piracy...

that gains you the coveted "banned for life" award...

Link to be removed soon -
I want the team, our freinds at MS and UBCD4WIn all to see that you are pie rat scum first.

REMINDER TO SELF: If Helmi doesn't like somebody... I ban them right out of the chute

i have visited the promised land... and it was good.