AutoPatcher x64 December 2005 - CTP


Recommended Posts

post-51082-1134926670.gif

icon11.gifGeneral Information

This release is based on the all-new AutoPatcher 5.1. Although it was made with Windows x64 SP1 English in mind, it will load on any Windows x64 version, showing only the items which match the running environment.

This release is UNOFFICIAL! It's a CTP (Community Technical Preview) to test AP on x64 based systems. This Version is for Windows XP x64 & Windows Server 2003 x64!

I'll hope you enjoy it! Providing feedback will help the team and me to make a better version of ap x64!

Please don't share the file without a link to this topic! The user must know, that this is an UNOFFICIAL CTP release.

viewicon.gifWhat's included (English December 2005)

Windows x64 - Critical Updates

KB890046: Security Update for Windows x64 Edition

KB893756: Security Update for Windows x64 Edition

KB896358: Security Update for Windows x64 Edition

KB896422: Security Update for Windows x64 Edition

KB896424: Security Update for Windows x64 Edition

KB896428: Security Update for Windows x64 Edition

kb896727: Cumulative Security Update for Internet Explorer for Windows x64-bit Edition

KB899587: Security Update for Windows x64 Edition

KB899588: Security Update for Windows x64 Edition

KB899591: Security Update for Windows x64 Edition

KB900725: Security Update for Windows x64 Edition

KB901017: Security Update for Windows x64 Edition

KB901214: Security Update for Windows x64 Edition

KB902400: Security Update for Windows x64 Edition

KB904706: Security Update for Windows x64 Edition

KB905915: Cumulative Security Update for Internet Explorer for Windows x64-bit Edition

Windows x64 - Recommended updates

KB891957: Update for Windows x64 Edition

KB898060: Update for Windows x64 Edition

kb898715: Update for Windows x64 Edition

KB898900: Update for Windows x64 Edition

KB901105-v3: Update for Windows x64 Edition

KB903234: Update for Windows x64 Edition

KB904639: Update for Windows x64 Edition

KB904714: Update for Windows x64 Edition

KB907565: Update for Windows x64 Edition

KB907865: Update for Windows x64 Edition

KB907986: Update for Windows x64 Edition

KB908521: Update for Windows x64 Edition

KB909520: Microsoft Base Smart Card Cryptographic Service Provider Package

KB910437: Update for Windows x64 Edition

Components

Microsoft .NET Framework Version 2.0 Redistributable Package (x64)

Microsoft Journal Viewer 1.5.2316.0

Windows Media Connect 2.0

Windows Media Player 10.0.3802

Add-ons

ActiveSync 4.1

Google Toolbar 3.0.126.3

New XP Screensavers

Macromedia Shockwave Player 10.1

Macromedia Flash Player 8 for Internet Explorer

Macromedia Flash Player 8 for Mozilla, Firefox, Opera and Netscape

New Theme: Royale

New Wallpapers

New XP Style Wallpapers

New AutoPatcher Wallpaper

Sun Java 1.5.0_06

And of course some registry tweaks which improve speed, appearance, functionality and security!

icon11.gifBitTorrent is a P2P system that makes transfering large files (or groups of files) amongst a large group of people easy, fast and efficient. The BitTorrent network is impressive mostly for the speed and reliability with which you get files that have been recently released. As long as a .torrent file has enough people sharing then you can be assured that it will start quickly and maintain a good download speed. Always remember to leave your BitTorrent client open to help distribute the files!

icon13.gifRead the FAQ before installing AutoPatcher: v1.1 rtf.gifAP_FAQ_enu_v1.1.rtf (made by raptor)

icon13.gifWith this version, you don’t need to decompress the amp files before using AutoPatcher. Just insert the amp module you want in the specific folder (\addons, etc) and AutoPatcher will take care of it.

softicon.gifDownload Links

You may download AutoPatcher x64 from any of the following mirrors:

  • uk-flag.gifEnglisch
    Torrents provided by dVbPool Networkx: Download
    Mirror provided by dVbPool Networkx: Download

icon11.gifSizes & Hashes

  • English December 2005 Full-CTP File Size: 206 MB (216.161.209 Bytes)
    English December 2005 Full-CTP MD5 Hash: 9d4a57292e729a682202102622b09bbc

thumbs_up.gifThanks To

  • Raptor for making this all possible.
  • Gandolas for all the great work he's been doing.
  • Corteoz for the work in the Norwegian version.
  • Marcin.Riki for the work in the Polish version.
  • DaFlapDrol for the work in the Dutch version and the help in internal testing.
  • Tarnatos for the work in the German version.
  • I would also like to thank those who continue to help with hosting and distribution, along with: Frank (main download server), skyypunk, eXplosive, iverson0881, SteelTrepid, Storm, DigitalScar, M2Ys4U, LittlBUGer, mlazovjp, iSix, calidude, cpugeniusmv, SilentKnight, Mace68, Nexose Networks, Draganta, Homer, SHUR, allskin (windowsPT.net), rpaz (Univ. ?vora), Hogie, tkam, Amnezja.org, IDG.pl, XP.net.pl, cswadner, AgentOddstar, GamingZen.com, dev, wb-repa, Tarnatos, Gabbix Solutions,PlanetMirror >andAusGamer>.

https://www.neowin.net/forum/style_emoticons/default/biggrin.gif[/imgEnjoy!>

Tarnatos

www.autopatcher.com

New Layout by

raptor

Edited by Tarnatos
Link to comment
Share on other sites

Okay, here's the deal.

Because of some changes in the registry on 64-bit systems, AutoPatcher 5.1 will not be able to detect installed hotfixes. This is because 32-bit programs (such as the autopatcher executable) are locked into a specific area of the registry. So when AutoPatcher queries for, let's say

HKLM\Software\Microsoft\Windows NT\CurrentVersion\HotFix\KB123456

Windows redirects it to

HKLM\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\HotFix\KB123456

...which doesn't exist.

As most of you know, I don't have a 64-bit system, so I found out when Gandolas was making an x64 release based on... AutoPatcher 6. Oh, and yes, AutoPatcher 6, although still a 32-bit executable, is aware of the x64 differences and will have no trouble getting around that registry issue...

/Raptor

Link to comment
Share on other sites

HKLM\Software\Microsoft\Windows NT\CurrentVersion\HotFix\KB123456

Windows redirects it to

HKLM\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\HotFix\KB123456

...which doesn't exist.

I know about this limitation. But there are still more. On x64 based windows versions the information witch hotfix is installed isn't stored in the registry. So ap have to create a new reg key to detect the hotfixes in the future.

That are all reasons for me to create a ctp version auf ap x64. So we can test if ap 5.1 is able to update a x64 system. Maybe itcan help with the development of ap 6.0.

Link to comment
Share on other sites

I know about this limitation. But there are still more. On x64 based windows versions the information witch hotfix is installed isn't stored in the registry. So ap have to create a new reg key to detect the hotfixes in the future.

That are all reasons for me to create a ctp version auf ap x64. So we can test if ap 5.1 is able to update a x64 system. Maybe itcan help with the development of ap 6.0.

Beep. Wrong answer. 64-bit Windows versions still store that info in the registry... They even store it in two parts... The one is the good old HKLM\Software\Microsoft\Windows NT\CurrentVersion\HotFix and the new one is the HKLM\Software\Microsoft\Update (if i'm not mistaken)

/Raptor

Link to comment
Share on other sites

Beep. Wrong answer. 64-bit Windows versions still store that info in the registry... They even store it in two parts... The one is the good old HKLM\Software\Microsoft\Windows NT\CurrentVersion\HotFix and the new one is the HKLM\Software\Microsoft\Update (if i'm not mistaken)

I'm sorry but that isn't so!!

Just look at this litte video (xvid needed!): Download

Windows x64 store *some* hofix information in "C:\WINDOWS\$hf_mig$"!

Link to comment
Share on other sites

You are using the 32-bit version of Registry in that video... which has the effect i describe above... It actually redirects you to Wow6432Node. Use the 64-bit Registry Editor.

Link to comment
Share on other sites

Ah there is the probem.... The 32bit version has been overwritten by a 32bit version. A probem with the german mui pack i think. I had to restore the original one from the cd... -_-

Edited by Tarnatos
Link to comment
Share on other sites

good job. Some issues though. WMP 10 is included in x64 versions of Windows.

You could also add some of the following:

-MSN Messenger 7.5

-Flash 8.

These have been confirmed working for when I made my x64 version (now scrapped as of seeing this)

the_guy

Link to comment
Share on other sites

WMP 10 is included in x64 versions of Windows.

That's right, but in a older version!

wmp.png

In this pack Windows Media Player 10.0.3802 is included.

-Flash 8.

Allready included?!

Link to comment
Share on other sites

Will that version install on x64?

1 other thing, 896727 is replaced by 905915.

Yes!

No!

- KB896727 replaces KB883939 & KB903235

- KB905915 replaces KB896688

Thank you for making an x64 autopatcher

No probelm, but remember that's no official version. It's only for testing!

Link to comment
Share on other sites

well im upgrading to x64 windows and downloading your file as a backup for later update

cant wait to play hl2 64 bit, wohoo?!!!

Playing @ x64 isn't really amazing. Often Win32 is much faster.:(( I have a dual boot system for working and gaming.

If you wish to test it, heres a dowload location:

Windows XP Pro x64: http://download.microsoft.com/download/8/1...1830_PX6_EN.iso

Reg to get a key: http://www.microsoft.com/windowsxp/64bit/e...tion/trial.mspx

Link to comment
Share on other sites

As raptor said, i've been workin AutoPatcher XP x64 based on the brand new version 6. There are some big differences between the "old" 5.1 and 6.x...

Edit:

And there are some problems with your settings.

1st. - You are using the old 5.1.31 (the newest is 5.1.36);

2nd. - You have "TargetOS=ANY_OS" and it should be "ANY_XP_X64" (and i think "ANY_2K3_X64"), but even with the ANY_OS string, i can't see any module but tweaks because of:

3rd. - Lot's of fields have errors. Example:

Default=Wahr

Expand=Wahr

...

NeedsRestart=Wahr

Edited by gandolas
Link to comment
Share on other sites

about x64 environment tags:

Tags are constructed using the following:

1. Operating System Family (i.e. XP)

2. Operating System Suite (i.e. X64)

3. Operating System Service Pack (i.e. SP1)

With that information, AutoPatcher creates the tag FAMILY_SUITE_SERVICEPACK

The running environment is also considered to be a 'member' of:

ANY_FAMILY_VERSION

ANY_FAMILY_SUITE

ANY_FAMILY_SERVICEPACK

And of course a member of:

ANY_OS

Windows XP Professional x64 Edition is XP_X64_SP1 so it would be a member of ANY_XP_VERSION, ANY_XP_X64 and ANY_XP_SP1

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.