Jump to content


XP/2003 x64 release was suspended now resumed


114 replies to this topic

#21 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 988 posts
  • Gender:Male
  • Location:Victorville, California

Posted 19 February 2012 - 02:37 AM

Booted into XP Pro x64 w/SP2 and started AutoPatcher.

Noticed all of the critical updates were in black - which I know is incorrect.

Checked the .APM's - found they had the same error as commented on earlier concerning other updates:

[DetectionRegistry]
RegistryPath=HKEY_LOCAL_MACHINE\

instead of:

[DetectionRegistry]
RegistryPath=HKLM\

A bit of editing is required to fix.

#22 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 19 February 2012 - 03:05 AM

Ya... I stopped updating the script file once I got it up to date the first time there are probably a few updates to add since then but, ya.. I need to edit all the APM's to fix that.

#23 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 19 February 2012 - 05:41 AM

I have placed the X64 script in the main release list and added BETA to its title. I have edited all the APMs to fix that HKLM issue. I have uploaded the new script and modules too.
The only thing is I can't test it or sign it till I download all those files. I lost them when I reinstalled my OS a while ago. Give me a shout if there is something wrong.

Edited by ViroMan, 19 February 2012 - 05:42 AM.


#24 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 988 posts
  • Gender:Male
  • Location:Victorville, California

Posted 19 February 2012 - 11:28 PM

 ViroMan, on 19 February 2012 - 05:41 AM, said:

I have placed the X64 script in the main release list and added BETA to its title. I have edited all the APMs to fix that HKLM issue. I have uploaded the new script and modules too.
The only thing is I can't test it or sign it till I download all those files. I lost them when I reinstalled my OS a while ago. Give me a shout if there is something wrong.
Ran APUP and downloaded the BETA for X64; ran AutoPatcher - everything listed in Critical Updates is now in blue, as expected.

#25 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 20 February 2012 - 12:16 AM

Are there any errors in the AP log?

#26 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 988 posts
  • Gender:Male
  • Location:Victorville, California

Posted 20 February 2012 - 09:41 PM

Booted into XP Pro x64 w/SP2 and ran AutoPatcher, the log file is attached. If there is anything out of the ordinary in the log file let me know and I'lltry to answer the question(s).

New Item:

Presently AutoPatcher displays XP Pro x86 WMP11 hotfixes/updates with no problems.

In XP Pro x64 w/SP2 WMP11 hotfixes/updates are not displayed. There really is no reason for this disparity as the only difference between the two is the file name.

For instance, an x86 hotfix/update is: windowsmedia11-kb928788-x86-intl

and the same x64 hotfix/update is: windowsmedia11-kb928788-x64-intl

Should this not make it easy to update the script and edit the APM files?

Edited by DesertJerry, 20 February 2012 - 10:38 PM.


#27 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 20 February 2012 - 11:39 PM

hmm.. well it shouldn't show any x86 updates if there is an x64 equivalent. It must be in the old part of the script. I took the old script and just kept updating from that point... I didn't bother too see if there was any crap in it. I guess I should look into it.

#28 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 742 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 31 March 2012 - 02:12 PM

Built a new folder for just doing XP x64 and downloaded the updates..Ran ap and brought os to a level where some 40 odd files needed to come from windows update.
Looked at ap log after cleaning up temp files and found errors listed at the end of the log

Spoiler

I know this is a beta release and ap shows as unofficial so it's just a heads up

#29 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 01 April 2012 - 12:29 AM

ohh ya I already knew about those. Damn I smashed my middle finger this morning. it takes forever to type anything without using it and I can't play games. I might as well kill myself now that my life is over. You know it took like 2 minutes to type this whole thing out on one hand?

Edited by ViroMan, 01 April 2012 - 12:30 AM.


#30 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 02 July 2012 - 08:54 AM

We are nearing completion with Whatacrock's new script. Expect a release some time soon this week if things are smooth.

#31 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 742 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 03 July 2012 - 05:52 AM

After much testing by mself and ViroMan, we are ready for those interested in public testing of this release.
If you do want to test this release then PLEASE ENSURE YOU BACKUP your current autopatcher directory...NO responsibly held for those who don't.

Point you APUP to http://www.autopatch.../releases2.list , scroll to bottom of the page to find the release.

Any comments and/or suggestions will be welcome

#32 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 988 posts
  • Gender:Male
  • Location:Victorville, California

Posted 03 July 2012 - 08:31 PM

I'm just going to plead ignorance here - I followd the link, scrolled down and found a heading: "WhataCrocks" release list/script - and what exactly am I supposed to do next? I looked through the apup1 and apup2 ini files I have and found no similar list/script. Can't run a test on my two installations of XP Pro x64 if I don't undedrstand how to proceed.

#33 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 03 July 2012 - 09:15 PM

You need to run APUP and use that release list to get the selection list.

apup /log /LISTFILE:http://www.autopatcher.com/releases/releases2.list

edit: corrected link ... sorry

Edited by click-click, 04 July 2012 - 07:50 AM.


#34 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 03 July 2012 - 10:23 PM

Well anyone who has used the releases2.list would know that... I would rather not have new people trying to test it but, then again we are talking about desertjerry's post. I thought you have tested with the second release.list before desertjerry.

edit: btw click click that link you gave is bad. it has dotnet in it.
I created a small batch file and attached it. Anyone wanting to use the test release list can unzip it into your apup dir. It will call apup and point it to the proper location for you.

IF you have a working version of apup2 you can just go into option and change the address by adding a 2 in it like this "releases2.list" and then hit ok... then work as normal. DON'T FORGET to set it back to normal once your done using the test list. Just remove the 2 or hit the default button.

Attached Files


Edited by ViroMan, 03 July 2012 - 10:35 PM.


#35 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 988 posts
  • Gender:Male
  • Location:Victorville, California

Posted 04 July 2012 - 05:27 AM

 ViroMan, on 03 July 2012 - 10:23 PM, said:

Well anyone who has used the releases2.list would know that... I would rather not have new people trying to test it but, then again we are talking about desertjerry's post. I thought you have tested with the second release.list before desertjerry.

edit: btw click click that link you gave is bad. it has dotnet in it.
I created a small batch file and attached it. Anyone wanting to use the test release list can unzip it into your apup dir. It will call apup and point it to the proper location for you.

IF you have a working version of apup2 you can just go into option and change the address by adding a 2 in it like this "releases2.list" and then hit ok... then work as normal. DON'T FORGET to set it back to normal once your done using the test list. Just remove the 2 or hit the default button.
I had used releases2.list a while ago and it was mentioned here a while back that I should not and to revert back to releases.list. I did that and had forgotten that to get to releases2.list I just had to modify the file name - as mentioned. So, I started APUP2 (1.0.5.13) > Options and added the '2' as menioned > OK > list > reviewed the list > nothing shown has a date newer than 2012 May 31 - WhatACrocks Test (I expected something newer) > Ohh ###### there is an error > Permission denied > OK > everyhting disappeared.

I'm assuming this error did not occur because I ran the update from within Win7 Ultimate 64bit w/SP1.

Oh well - tiem to quit - 2230 hours here - bed.

#36 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 04 July 2012 - 07:20 AM

no use apup... that version of apup2 probably has the dos bug(or one of the other wired bugs others started reporting)... I forget which one I stomped out the dos bug in. use the batch file I provided to run apup v1

Edited by ViroMan, 04 July 2012 - 07:20 AM.


#37 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 988 posts
  • Gender:Male
  • Location:Victorville, California

Posted 04 July 2012 - 08:17 PM

OK - downloaded ZIP > Ran Bat > Downloaded WhatACrock Test > got verification failed message > OK > Finished! > Finish button.

Will report back later (today/tonoght/tomorrow) when I reboot into XP Pro x64. (Am in Win7 Ultimate right now.)

Reboot > XP Pro x64 w/SP2 > AutoPatcher > Windows XP x64 (new item) > Windows XP x64 - Critical Updates > 11 items shown in blue, all others black (I doubt very much if this is really true - Microsoft Updates indicate none are needed.)

Windows XP x64 - Non-Critical Updates > 9 items blue; all others black, two have a check mark in the box: KB925876 and KB954430

Windows XP x64 - Component Updates > one item - blue: Windows Media Player 11 for Windows XP (64-bit)

Microsoft Windows - Critical Updates > Six items listed; five black with check mark in box, one blue: Malicious Software v4.9 x64

Microsoft Windows - Recommended Updates > one item - black: Image Mastering API v2.0 ...

Microsoft Windows - Updated Components > .NET Framework 1.1 > all blue

Microsoft Windows - Updated Components > .NET Framework 3.5 and Family > all blue excpet for one: .Net Framework 3.0 SP2 > Microsoft ... (KB958483)

Microsoft Windows - Updated Components > .NET Framework 4.0 > all blue

Microsoft Windows - Updated Components > Microsoft XML Parser > all blue

Microsoft Windows - Updated Components > IE7 > black: not needed IE8 installed

Microsoft Windows - Updated Components > Journal Viewer 1.5 is blue and listed twice

Microsoft Windows - Updated Components > Windows Update 7 > black

Microsoft Windows - Updated Components > Windows Installer 4.5 is blue and listed twice

Microsoft Windows - Updated Components > Windows Search 4.0 is black and listed twice

Microsoft Windows - Updated Components > Windows Update Agent ... test - 64-bit is black with check mark - not needed, have latest from Microsoft.

Microsoft Windows - Updated Components > DirectX > blue

Microsoft Windows - Updated Components > WMP11 > blue - why here? Previously shown above under Windows XP x64 - Component Updates.

Microsoft Office Addons > not sure of validity - I have Office 2010 installed

Windows Addons > Windows Desktop Search > both black > not installed (will not be installed by me)

Windows Addons > Network Monitor and Parsers . all blue

Windows Addons > all other item are blue

Stand Alone > all blue

Be advised that I installed this XP Pro x64 w/SP2 on 18 March 2012 after I created an updated install source using the RyanVM Integrator and the March 2012 XP Pro x64 Update Pack - this may or may not be the reason AutoPatcher lists many updates as not being installed.

Edited by DesertJerry, 04 July 2012 - 09:29 PM.


#38 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 05 July 2012 - 01:57 AM

I fixed the verification problem... was a size and md5 miss-match but, I noticed there are several APM errors.... they will not install using AP because the paths are set wrong. We should have noticed that bug before going to public testing... sorry.

Edited by ViroMan, 05 July 2012 - 02:01 AM.


#39 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 988 posts
  • Gender:Male
  • Location:Victorville, California

Posted 05 July 2012 - 02:20 AM

Clarification - the informtion I posted above was what AutoPatcher listed after I ran the releases2.list and Started Autoptacher in XP Pro x64 - I did not try to install any of the items listed in black; mainly because I doubted they were really not installed; that's why I made the advisory comment about the updated source.

Also, when I booted into XP Pro w/SP3 and started AutoPatcher I noticed the first/top listing was, again, XP Pro x64 but, this time, only the major sub-items were listed. I'm assuming there is no way to not show XP Pro x64 items when running Autoptacher from XP Pro and vice versa. (Not showing could reduce some possible confusion by novices - maybe.)

Don't know if this may help but I have used Windows Update List and it provides a list of what has been updated on my system. If that information is available to it I can only assume it is available to others. A description follows:

WinUpdatesList v1.31
Copyright © 2004 - 2011 Nir Sofer
Web site: http://www.nirsoft.net
Description
===========
WinUpdatesList displays the list of all Windows updates (Service Packs
and Hotfixes) installed on your local computer. For hotfix updates, this
utility also displays the list of files updated with these hotfixes. In
addition, it allows you to instantly open the Web link in Microsoft Web
site that provides more information about the selected update, uninstall
an update, copy the update information to the clipboard, or save it to
text/HTML/XML file.

Edited by DesertJerry, 05 July 2012 - 03:05 AM.


#40 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,162 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 05 July 2012 - 03:48 AM

XP x64 should only show when in an XP x64 system. We will look into it. perhaps tomarow... now its happy 4th of july time here in America.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users