5 replies to this topic

[DesertJerry]

On computer #1:
XP Pro w/SP3 and Office 2003 w/SP3
XP Pro x64 w/SP2 and Office 2003 w/SP3
Win7 32-bit and Office 2010 beta 32-bit
Win7 64-bit and Office 2010 beta 64-bit

On computer #2:
XP Pro w/SP3 and Office XP w/SP3
Win7 32-bit and Office 2010 beta 32-bit

Computer #1 has four AutoPatcher folders corresponding to the setup above.

Computer #2 has two AutoPatcher folders.

Now that APUP and AutoPatcher for Win7 have been released and they are in use by many is there any reason I could not simply go to one AutoPatcher folder for ALL the versions of Windows and Office? Thus saving hard drive space and download time.

I would run APUP from within that one folder from any of the operating systems and select all operating systems and all versions of office plus all the addons. Then, going to any of the operating systems listed I would have a shorcut to AUTOPATCHER.EXE and run it from that operating system. I am assuming that when AutoPatcher is run, even though there are downloads for all operating systems and Office versions it would list and highlight only those updates/hotfixes/etc appropriate to the operating system I am presently running - right/wrong?

I figured I'd ask here before I try it and possibly make a mess of things. Also, friends ask many hardware and software questions so I figured I could copy this one folder to a flash drive and carry it to their place when the need arose.

I did read the FAQ and no similar item was posted.

Anyone?

[Cristiano]

> there any reason I could not simply go to one AutoPatcher folder for ALL the versions of Windows and Office?
now that most of the issues with shared files are fixed, then you can do that. but some extra shared folders may be still present, but not tracked. i was thinking that i've tracked them all about 6 months ago and a few days ago, an user has proven me wrong. if you have in the same folder an module that has the exact same name than other one that is in another script, but has an different content, then that file will be downloaded over and over again and booth script could become unofficial. also, the scripts aren't downloaded all at same time and this could lead to the same scenario

> it would list and highlight only those updates/hotfixes/etc appropriate to the operating system I am presently running - right/wrong?
right. the modules has an restriction to run only in their targets

[]s

[dkdk_it]

I care all module parameters, but some mistakes are possible!
I'll check AIO (All-In-One) compatibility when I'll finish to update all releases.

Bye.

[DesertJerry]

Thanks for the information.

Based on what you said I guess I'll do things in steps; I'll merge the XP Autopatchers into one folder and the Win7 Autopatchers and try each of them - one at a time. It will be interesting to see how things come out.

It may take a couple of days to do the tests along with all the other stuff I normally do so don't expect results for a few days.

Being retired gives me plenty of time to perform the tests.

[DesertJerry]

Two steps completed.

AutoPatcher for XP Pro combined and XP Pro w/SP3 and XP Pro x64 w/SP2 are seen ok by APUP and AutoPatcher.

AutoPatcher for Win7 combined and Win7 32-bit and 64-bit are seen OK by APUP and AutoPatcher.

Good start so far.

[DesertJerry]

Booted my #2 system and merged AutoPatcher for XP and AutoPatcher for Win7 folders - both APUP and AutoPatcher worked just fine in both when I tested each.

Things are really looking good.