Bug Reports for AutoPatcher 4.2

By ITinerant
in Software created by our members

 Share

Recommended Posts

Grand Master

FlishFun Veteran

Posted
  • Veteran
Posted

First... did a Japanese one sneak in?? Whoops! :pinch: That will be fixed... and did I use the wrong slash on a switch? Hrmm... let me know if that works... very interesting! Good work guys! (Y) What would I do without ya? ;)

Veteran

cpugeniusmv

Posted
Posted

worked like a charm with the reversed slash!

only error i got was windows messenger.

and if you're going to make a tweak to remove java shortcuts, here's the whole thing:

del/q "%systemdrive%\Documents and Settings\All Users\Desktop\Java Web Start.lnk"
rd/s/q "%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Java Web Start"

Grand Master

FlishFun Veteran

Posted
  • Veteran
Posted
worked like a charm with the reversed slash!

only error i got was windows messenger.

and if you're going to make a tweak to remove java shortcuts, here's the whole thing:

del/q "%systemdrive%\Documents and Settings\All Users\Desktop\Java Web Start.lnk"
rd/s/q "%systemdrive%\Documents and Settings\All Users\Start Menu\Programs\Java Web Start"

Sweet!!! (Y) Good job! :D

Collaborator

ITinerant

Posted
  • Author
Posted
i think i've found a solution to the .NET question mark problem...

in "AutoPatcher XP\AXPFiles\NETFrame11.axp"

"%AutoPatcherXP_Dir%\ProgFiles\dotnetfx.exe" /q /c:"install \q"

should be

"%AutoPatcherXP_Dir%\ProgFiles\dotnetfx.exe" /q /c:"install /q"

(the backslash shouldn't be a backslash :) )

i'm getting ready to test it.

Thanks cpugeniusmv, After reversing the offending slash, ticking the .NET Framework box and saving as Defaults I burned a CD and tested on a clean install of WinXP SP-1. 114 patches and tweaks took 35 minutes and went off without a hitch. I checked Windows Update just to be sure and all was A-Okay! Thanks to one and all! :p

Grand Master

FlishFun Veteran

Posted
  • Veteran
Posted

Well I'll be... all that cause of one slash. Well I am truly sorry I didn't catch it... still amazed that on my PC and all the people I had test it, it never came up with the error. Well thanks, and know that it will be fixed in the Jan release. :D

Collaborator

ITinerant

Posted
  • Author
Posted
Well I'll be... all that cause of one slash. Well I am truly sorry I didn't catch it... still amazed that on my PC and all the people I had test it, it never came up with the error. Well thanks, and know that it will be fixed in the Jan release. :D

FlishFun, you is still da Man! If there is a wish list for January's release, I'd like to suggest all the stuff that's on Anti-Spy 3.72; I know you already have some of the stuff, but the first thing I do after AutoPatcher is install Anti-Spy and it stops the rest of the "Phone Home" features of WinXP.

http://www.xp-antispy.org/index.php?option...itory&Itemid=26 :whistle:

Grand Master

FlishFun Veteran

Posted
  • Veteran
Posted
I know you probably saw it, and I hate to repeat myself...

but are you going to make the January release so that you can uninstall Windows Messenger without having to install MSN Messenger 6.1?

Whoops! Good thing ya repeated yourself! :) I didn't see that. Yes, I meant to do it this time and didn't... so in Jan it will be in the same section, but underneath (so you don't have to install MSN Messenger). :)

@ITinerant - I'll check it out. (Y)

Grand Master

FlishFun Veteran

Posted
  • Veteran
Posted
FLISHFUN: about the bootstrapper (install.exe)

can we just delete it "NOT NEEDED"

or if it's important for the setup >>>>can you post here the english version of the file (just 96 k) so we can replace it...

thanks to all

It's not needed, must have slipped in there without me noticing... just delete it. :)

Veteran

cpugeniusmv

Posted
Posted

Some of these issues have been resolved, and will be fixed in the next release (january)

Instructions on fixing the last two errors:

1. Find the file called "NETFrame11.axp" in "AutoPatcherXP\AXPFiles"

2. Open it up in notepad

3. At the end of the line, notice the install \q"

4. change the backslash ( \ ) to a forward slash ( / )

5. Save the file

now those last two errors won't show up anymore.

as for the first one, it might help if you could find out which update that happend during...the error box is covering it up :-\

Grand Master

soldier1st

Posted
Posted

the error of the .net framework is caused by the demember update if you didn't have the .net framework from the november release and try to install the .net framework from december it will give you that error

solution:install the .net framework from the november release and run the december update of the .net framework and it will install properly

it's been tested

Veteran

cpugeniusmv

Posted
Posted
the error of the .net framework is caused by the demember update if you didn't have the .net framework from the november release and try to install the .net framework from december it will give you that error

solution:install the .net framework from the november release and run the december update of the .net framework and it will install properly

it's been tested

no, it was a mistyped slash....a backslash ( \ ) instead of a forward slash ( / ) in the "NETFrame11.axp" file...

i ran the Dec AP on a clean installation (no november update) with the adjusted slash, and that fixed it.

Grand Master

FlishFun Veteran

Posted
  • Veteran
Posted
no, it was a mistyped slash....a backslash ( \ ) instead of a forward slash ( / ) in the "NETFrame11.axp" file...

i ran the Dec AP on a clean installation (no november update) with the adjusted slash, and that fixed it.

You're 100% correct. I thank you all for your hard work in helpin' me stamp out these last remaining bugs! :D

Apprentice

1ComputerGuru

Posted
Posted

Okay.....1st my compliments on an outstanding program. Then will add some additional info ref'd to the minor problem with the .NET installations (on the Dec Full install program). I'm sure that this small problem has been addressed to some extent; but, this is what was noticed on 2 seperate computer updates. The updates were done from a burnt CD in which I had already corrected the \q to /q typo within the "NETFrame11.axp" file.

On the 1st machine, I left the default (both items ticked) to install both the .net framework and the update. An error ballon?? occurred for the Update installation (NDP1.1-KB824629-x86.exe) and the update stalled until you pressed the "ok" button and then preceeded until the autoupdater ending. Apparently neither the .net framework or the update patch installed; because, after rebooting - ran the windows update and it listed the .net installation as still needing to be installed. Now on the 2nd machine, ran same cd configuration but only leaving the .net framework install ticked and untick the .net update. This setup ran flawlessly from begining to end and installed the .net files properly.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.