Jump to content


Fresh XP OEM SP3 install - can't get AP to work


3 replies to this topic

#1 schwinn

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 07 November 2009 - 11:40 PM

Long time user of AP, but this is the first time I've run into this problem:

- Fresh install of XP SP3 OEM
- Downloaded APUP from the Autopatcher website and ran the updater to download the patches
- Everything downloads properly, but when I run AutoPatcher.exe, I get an error that it can't find FM20.dll (it is present in the Windows/system32 folder, dated 7/10/2007)
- Yes, Windows\system32 is part of the PATH for the machine...

If I copy that file over from the "bin" folder to the Autopatcher.exe path, I get another error for "0x7: Out of Memory"... wtf?

I tried installing vbrun60sp6.exe from the win9xnt folder, but this doesn't fix it either...

Autopatcher's error window/log shows me:
Spoiler

Does AP have some requirements that I simply don't have installed on a fresh install of XP? What am I missing here?

Edited by Cristiano, 08 November 2009 - 12:04 AM.
spoiler


#2 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 08 November 2009 - 12:02 AM

that's weird. i run autopatcher over oem versions of windows xp sp3 several times a day and never had any issue like this one. yes, autopatcher requires Microsoft Forms 2.0 (FM20.DLL), version 11.0.5601.0 or higher. this issue that you are having was designed to that by ms. you may try download and install this, that install Fm20.dll. more infos about can be found in here

by the way: this windows of yours was changed in any way by the oem reseller?

[]s

#3 schwinn

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 08 November 2009 - 01:39 AM

Nope... this is copy of an original OEM CD from Newegg... the original had the hologram and all, and I made the copy myself.

I just tried using the same CD on a Virtual Machine, and weird enough, AP works fine there... I tried wiping the drive with a linux boot disk (just in case) and then reinstalled windows again... and oddly enough, now it works. Very weird. Maybe some low-level HD driver or some dumb HP recovery thing was blocking the software from working... in any case, it's gone now, and the system is Auto-patching!

Sorry for the unnecessary post!

#4 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 08 November 2009 - 10:55 AM

my friend, your post wasn't unnecessary. maybe, just maybe, something gone wrong with the reading of the cd, etc. you know, a lot of things may go wrong and if this happens... but the good thing is that you was able to fix it :)

[]s





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users