Recommended Posts

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? ;)

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"

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

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

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

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:

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)

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. :)

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 :-\

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

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.

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

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.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!