AutoPatcher XP 4.5 Official Thread

By FlishFun
in Software created by our members

 Share

Recommended Posts

Enthusiast

coucou

Posted
Posted

Hi,

Regarding the WindowsXP-KB821253-x86-ENU.exe batch file inside Autopatcher Core.db , i think there is an error.

Here the code inside Autopatcher Core.db 

<batch uniqueID="Q821253">
"{apdirectory}\ProgFiles\Q821253_WXP_SP2_x86_ENU.exe" /q /z
set ERRORLEVEL=0</batch>
<batch uniqueID="Q821253b">
"{apdirectory}\ProgFiles\Q821253_WXP_SP2_x86_ENU.exe" /q /n /o /z
set ERRORLEVEL=0</batch>

Which should be

<batch uniqueID="Q821253">
"{apdirectory}\ProgFiles\WindowsXP-KB821253-x86-ENU.exe" /q /z
set ERRORLEVEL=0</batch>
<batch uniqueID="Q821253">
"{apdirectory}\ProgFiles\WindowsXP-KB821253-x86-ENU.exe" /q /n /o /z
set ERRORLEVEL=0</batch>

Isn't it??? Please confirm!

Regards

coucou

Grand Master

FlishFun Veteran

Posted
  • Author
  • Veteran
Posted
Hi,

Regarding the WindowsXP-KB821253-x86-ENU.exe batch file inside Autopatcher Core.db , i think there is an error.

Here the code inside Autopatcher Core.db 

<batch uniqueID="Q821253">
"{apdirectory}\ProgFiles\Q821253_WXP_SP2_x86_ENU.exe" /q /z
set ERRORLEVEL=0</batch>
<batch uniqueID="Q821253b">
"{apdirectory}\ProgFiles\Q821253_WXP_SP2_x86_ENU.exe" /q /n /o /z
set ERRORLEVEL=0</batch>

Which should be

<batch uniqueID="Q821253">
"{apdirectory}\ProgFiles\WindowsXP-KB821253-x86-ENU.exe" /q /z
set ERRORLEVEL=0</batch>
<batch uniqueID="Q821253">
"{apdirectory}\ProgFiles\WindowsXP-KB821253-x86-ENU.exe" /q /n /o /z
set ERRORLEVEL=0</batch>

Isn't it??? Please confirm!

Regards

coucou

Nope, it's fine. BUT! It turns out I have the same file in twice, so I'll just delete WindowsXP-KB821253-x86-ENU.exe from the next release. :)

@blueshirt - I'm thinking about it... this makes me wary:

post-8-1079962372.jpg

Grand Master

FlishFun Veteran

Posted
  • Author
  • Veteran
Posted
aye, but even like that, wouldnt it be kinda lame to include a 180-day public preview release in autopatcher?

See, that's what I was thinking. Of course, part of me knows there will be a new release in less than 180 days, so I'm torn. :s

Grand Master

FlishFun Veteran

Posted
  • Author
  • Veteran
Posted
of course there will be a new build in less than 180 days, but lets just keep quality software in... its hard to handle all those mystirious hotfix issues (i.e slowdowns) as it is...

I know. I said earlier I was leaning towards "no". Plus, the size of the package is stagering.

Veteran

EZRecovery

Posted
Posted
I know. I said earlier I was leaning towards "no". Plus, the size of the package is stagering.

I'm with you guys, APXP is a great program plus is quality like Raptor said.

If it was me working on APXP and you guys ask for my opinion, i would say "NO" to add the 180day release. :D

Grand Master

FlishFun Veteran

Posted
  • Author
  • Veteran
Posted
dunno if DBE will make it... apparently memodude is busy lately, and he hasnt finished the save routine... and no, dont even think of puting me to do it... i'm not messing with XML...

Dang it Memo! :crazy:

@blueshirt - I know, will be ready for the next release. :)

And Raptor, what you mean "dont worry, i already said 'no' so it wont go in"? Don't make me come down there and put a smack down on ya! :laugh: We both said "no", foo'! :p

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

  • Recently Browsing   0 members

    • No registered users viewing this page.