AutoPatcher XP 4.5 Official Thread


Recommended Posts

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

What's wrong with it? The 180 day license? Prerelease?

The 180-day license I'm thinkin'... but who knows. I'll give it some more thought...

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

How big is the March update?

As it stands it will be about the same size as the Feb... wasn't too too much out. Just adding in the DBE (hopefully), replacing some things, etc. :)

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

blueshirt: hehe, as if it was news... new versions of those come almost every day hahaha

EXRec: dont worry, i already said "no" so it wont go in :D

Link to comment
Share on other sites

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

Link to comment
Share on other sites

aye... meant: if one of us says 'no' then the answer is 'no' (i.e 1 'no' and 1 'yes' equal 'no')

/Raptor

I got you, I know the rules now ;)

Link to comment
Share on other sites

thats how it works when you have 2 project managers :D

haha Yep... sorry, I'm dealin' with a semi-crisis here (two laptops went missing), and read your post wrong. :laugh:

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.