Recommended Posts

I have the same problem as Yochanan describes in his post and Gary too!

1) I install clean Windows XP SP2

2) Drivers

3) Autoatcher 5.1 Windows XP Dec 05 Full

4) Autoatcher 5.1 Windows XP Jan 06 Update

5) When I try Autoatcher 5.1 Windows XP Feb 06 Update the same error occur!

Please give any suggestion?!

Thank you in advance!

yochanan experienced it because he was using the release on its own instead of on top of a previous release.

when you say you have dec05, jan06 and feb06, are you actually installing jan06 on top of dec05, and then feb06 on top of jan06. or are you clearing the autopatcher folder before installing each new one, because you should only do that with new full/lite releases.

i couldnt find a user called gary...

What exactly is this Feb06 full BETA at softpedia.com ?!?

I'm not sure I understood correctly: did softpedia just unpacked both Dec05 and ap's official update, and then re-packed the whole thing, but used some sort of a beta AP6 wrapping?

If so, what exactly does that mean? The contents are 100% the same and only the installer is different?

Will future AP's official update packs may be applied to wherever this beta thingy extracts to, in the same manner they're to be applied to official full packs?

I'm sorry if it's somehow obvious for anyone else here, I've definately missed something :blush:

thanks.

P.S.

Are there any other known problems with the beta? better yet - any known advanteges over the original ap besides some new comforts?

@maxkohl

i thought maybe they have packed up there own full release at first too, but actually gandolas made it and its using ap6 beta.

im not really sure whats going to happen next month.

ap6 is still in beta, so i dont think were making a switch yet, in fact i havent even made a start on prepairing any of the 2k or 2k3 modules.

next month im going to be handling the xp release because gandolas is busy, but he didnt mention the ap6 beta releases.

i dont know whether he'll be doing anything for those, whether i should make some update releases for them, or whether i should just leave them as is, just for people to use for testing purposes, and only make a new one when a big change occurs or else when its out of beta....

^^ Softpedia decided to host the file, they didn't make it. I did. Is, as Blaze said, a release based in the test version 6.0. I did a January internal test build, and tested it in my computer.

This month, i've updated it, and asked raptor if i could release it (since i released a Portuguese test version), and he gaved me green light.

I'll see if i'll have time to do the beta release. I'm having problems with lack of time, i've asked Blaze to do next month release.

I downloaded the AutoPatcher XP February 2006 Beta Full . I instaled it but when i try to open it it gives me an: Run-time error '372' Failed to load control 'RichTextBox' from RICHTX32.OCX. Your version of RICHTX32.OCX. may be outdated. Make sure you are using the version of the control that was provided with your application .

Please help !

Hello,

Not sure if I have found a bug, or some weird occurance. To duplicate, here is how I found it.

1: installed Dec 05 - Full

2: updated Jan 06 - lite

3: updated to Feb 06 - lite.

I am running Autopatcher 5.1, and the above patches. Everything works great, and no install *issues* but as the picture shows, when I click in the X region (between Update and Module Description) .. Click there once, and you will notice that this will open up a CMD (command line) box.

I have done this on 2 machines so far.. Is my install fooobared ? ..

Let me know..

Wil.

post-157103-1140468886.jpg

When installing the XP beta under Win2k, it refused to run (gave that error from last month's 2k update - there's this unsupported code - it's in Jan06 2k update thread...) - Of course, I wasn't expecting to do a full-blown patch of 2k w/the XP patcher, but I got the impression that compatible modules should still be relevant - after all, the loader do has an OS detection code...this problem will be more of an issue if one combines installations of AP packages for different OSes...

BTW - Last month it was solved simply by replacing AutoPatcher.exe with an older version, and it all worked just fine - wasn't the new code addition neccessary at all for the smooth operation?!? If so, why won't fall back to the older version for all releases...but better yet o/c - find a compatible piece of code ;)

Another issue with the beta, is that it failed to uninstalled correctly (at least the icons were left on my Win2k desktop, and a temp folder, "C:\# AutoPatcher Temp #" if I recall, was not deleted - I guess that this folder was coutesy of the failed launch attempt prior to uninstalling it?)

Oh well, I really wanted to see this new AP6 thingy :D

I haven't really got it though - will TheBlazingAngel's efforts in refining the script apply to AP6 as well? Is it part of it?

@cc979, i dont believe any part of the royle theme was included in the feb update. are you trying to use it as a standalone and your complaint is actully that you cant find the module. or are you using the feb full BETA that uses APv6, and you cant get the royale theme to install?

I?m downloading the FULL version of PTBR, but the host isn?t very good (only 10K/bs Max! 0o).

Im very grateful for gondolas on his hard job, when I get the file I?ll host on another mirror so the download maybe will be more fast.

Gondolas, if u want, everytime that u launch the PTBR file I can help u uploading it on some mirrors, just talk with me...I?ll be glad helping.

P.S. I can give u my msn if u send me a PM so we can work together on this part of the job.


You can create your own full :

Dec full + jan & feb lite = feb full!!!

Solution is out there...

Generally, you are right.

However, only for this month, I understood that Blaze incorporated the Jan06 update into the Feb06 update too, rendering the Jan06 for itself, redundant :cool:

But your method is "failsafe" for the future, where updates won't necessarily be commulative (like this month's AP 2k update).

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.