17 replies to this topic

[xaneth]

apup needs a driver area like

http://drp.su/

aka "driverpacks"

[ViroMan]

hmm... I am torn between thinking the above post is spam or whether it was an actual suggestion.

I will treat it as a suggestion. A drivers area would be fairly hard for us to maintain. Its difficult enough for us to maintain the current scripts as they are. Adding dozens of more scripts to the pile would be a huge nightmare. If you are willing to create and maintain such scripts I would be willing to open up such an area.

[_def_x_]

ViroMan, on 20 May 2012 - 01:36 AM, said:

hmm... I am torn between thinking the above post is spam or whether it was an actual suggestion.

Me too Spam, or worse

[Whatacrock]

Looks to me as a suggestion...maybe

Have to agree with ViroMan as to it being a nightmare especially with the amount of different hardware that's in use worldwide.
Even with these driverspacks sometimes the right driver is not found,usually as that some drivers are generic and the hardware doesn't like it.
I would strongly protest having drivers added to AP as it's designed to update operating systems not to update systems with latest drivers for hardware used.

My 2 bob's worth

[DesertJerry]

If the time spent at DriverPacks: http://forum.driverpacks.net/ updating and maintaining drivers is any kind of an example I would NOT recommend they be added to AutoPatcher. A NO VOTE here.

[ViroMan]

You mean to say you have spent a bit of time there?

[DesertJerry]

ViroMan, on 20 May 2012 - 09:41 PM, said:

You mean to say you have spent a bit of time there?

I usually go there once a day to check on any and all possible driver updates for my systems. Doing that I've noticed that some of the updates take weeks to get finalized or are never completed or are too difficult to continue updating because the driver download from the vendor has become more difficult to successfully extract and be used in DriverPacks.

[ViroMan]

sounds like they might have the same issue we do... not enough people/time to take care of things.

[_def_x_]

DesertJerry, on 21 May 2012 - 08:44 PM, said:

<snip>... are too difficult to continue updating because the driver download from the vendor has become more difficult to successfully extract and be used in DriverPacks.

If I'm not mistaken, they extract the exe and try to get the needed drivers and put them in a cab file - lots of work. Similarly, a release manager would download Microsoft updates, extract them, get the dll out, find needed registry info, drop the dll and a .reg file in a cab, when run it would add or replace said file.

[DesertJerry]

Actually they are .7Z files and are invoked by the DriverPacks Base program which can be downloaded from the forum. Works just fine when slipstreaming/integrating XP Pro. Does not work with XP Pro x64 - no 64-bit drivers. Since Win7 does not update via slipstreaming they recommend a different method - all info available, again, at the forum.

[ViroMan]

No shit? Can't slipstream win7? wtf? How do you update win7 install disks?

http://www.sevenforu...d-iso-file.html

ohh that was quick search and answer. A quick glance and it looks like it works like nLight in that it can integrate sp's and updates and then make a disk/usb for you.

Edited by ViroMan, 22 May 2012 - 07:01 AM.

[_def_x_]

DesertJerry, on 22 May 2012 - 03:46 AM, said:

Actually they are .7Z files and are invoked by the DriverPacks Base program which can be downloaded from the forum. Works just fine when slipstreaming/integrating XP Pro. Does not work with XP Pro x64 - no 64-bit drivers. Since Win7 does not update via slipstreaming they recommend a different method - all info available, again, at the forum.

Sorry, I might have been thinking of RyanVM, when I checked out a few scripts some time ago they had the dll files in a cab that you downloaded. Most all these methods do use the same basic principles that are built into the OS, the 'sif' file, 'runonce' etc. It does look like Windows 7 has changed the process but since I don't have the OS I haven't looked into it yet - soon though

[DesertJerry]

ViroMan, on 22 May 2012 - 06:57 AM, said:

No ######? Can't slipstream win7? wtf? How do you update win7 install disks?

At http://www.wincert.net/forum/ you go to the Win7Tookit forum and use the W7Tookit to add updates to the original install DVD. Last time I did it it took over four hours to update Win7 Ultimate 32- or 64-bit with over 300 updates posted by SoLor as part of the W7Toolkit. I did this prior to installing Win7 Ultimate on my new system; as a result of adding these updates to the original install DVD AutoPatcher is unable to detect all of the updates that came out after SP1 and up to the date of the SoLor updates.

[ViroMan]

That is possibly due to not having registry entries related to those updates because they were not actually installed. The detections that look for cab files will see those as installed though.... I think.

[DesertJerry]

A bit of AutoPatcher testing.

Booted into Win7 Ultimate w/SP1 64-bit (which was installed after source DVD updated using W7Tookit and SoLor's 300+ updates).

Microsoft Windows - Critical Updates:
Security Update for Windows 7 for x64-based Systems (KB2425227) - shown in black
Security Update for Windows 7 for x64-based Systems (KB2479943) - shown in blue

Checked:
[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=Package_for_KB2425227~31bf3856ad364e35~amd64~~6.1.1.1.cat
FileVersion=ANY
FileMD5=ANY

[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=Package_for_KB2479943~31bf3856ad364e35~amd64~~6.1.1.0.cat
FileVersion=ANY
FileMD5=ANY

For KB2425227 there was no listing in the referenced Catroot folder; for KB2479943 the listing existed.

A registry search on KB2425227 resulted in one location being identified:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache\Package_for_KB2425227~31bf3856ad364e35~amd64~~6.1.1.1

so I would assume that merging the SoLor updates into the original source DVD resulted in the KB being listed in the source so it could also be listed as installed when the source was used to install Win7 Ultimate on the computer.

The problem then becomes what edits would be necessary to update the various APM files to correctly identify the SoLor updates now integrated in the source. As the SoLor updates I included number over 300 this becomes fairly impossible to accomplish and at this time I can think of no ready solution.

Edited by DesertJerry, 23 May 2012 - 08:53 PM.

[ViroMan]

huh... funny. The registry points to a cab files name but, there is no cab file.

[click-click]

Solor has not updated his hotfix repository since the beginning of April. There are even more fixes than what you mention. Also, I think I previously did mention that APUP did not support hotfixes because of the effort involved.

BTW, KB2526946 replaced KB2425227 which is why KB2425227 is showing black. This is the kind of problem one will run into when installing hot fixes.

Edited by click-click, 23 May 2012 - 10:20 PM.

[xaneth]

for your info this is not spam i thought it would be a decent idea to have a all in one os and hardware installer
yes i see what u r all saying lots of work

i've used this stuff aka driverpacks with no issues in xp or win 7 64 and 86 versions

from xaneth