Upgrade patch 5003

[John_Klassek]

The error still exists on a system that had 5002 but now is upgraded to 5003.

FYI: On Friday I upgraded my main system (Xp Pro) from 5001 to 5002 to discover the runtime/startup error.

Last night I updated my laptop (also Xp Pro) from 5001 to 5003, and that seemed to resolve the issue, with no error at runtime.

However, this morning I have updated my main system from 5002 to 5003 and the error still persists.

The project on my laptop works fine (5001 > 5003), and over the network will run fine on the main system.

But the copy of the project on the main system ( 5001 > 5002 > 5003) still returns the error message as again captured below.

My own summary from this is that somehow the upgrade from 5002 has left some residual dlls or scripts that haven't been overwritten by 5003, but the upgrade from 5001 to 5003 works fine?

I notice, FWIW, that the file size of the autorun.exe for the version 5003 that works okay is 1436KB, as opposed the the file size of the autorun on the version with the error at runtime which is only 1392KB (and under properties shows it to only be v 5000).

How this is so I'm not sure because both systems were upgraded to 5003, but only one went via 5002.

Hope this info is helpful in getting to the bottom of this issue.

Regards,

John

[John_Klassek]

As the screen capture below shows, if I rename the autorun.exe that returns the runtime error, and copy the working autorun.exe version on my laptop, the project works fine.

What is of note, that even though both my systems are now upgraded to 5.0.0.3 the "properties" of the autorun.exe from my main system is only listed as 5.0.0.0

Hope this additional info helps.

John

[Corey]

What would the holidays be without a last minute wrinkle?

Corey Milner
Creative Director, Indigo Rose Software

[leebos]

For what it's worth I am having the same problem on my laptop, XP home upgraded the same way, 5.0.0.1 > 5.0.0.3 > 5.0.0.3.
Can't test on desktop as I'm away for the holidays.
What is the recomended way to revert to the last working version?

Lee

[John_Klassek]

Originally posted by Corey
What would the holidays be without a last minute wrinkle?

Don't we just love holidays!

For that matter, I suppose it doesn't matter whether this issue isn't sorted out until mid January, -- because most of us will be either on holidays with the family, or recovering with hot black coffee.

And, those of us still sitting half dazed in front of our monitors should be taking a break anyway!

Cheers,

John

[John_Klassek]

It's the holiday season, and... I still can't get away from this monitor!

Just one question: Whatever may have gone amiss with the patch update from 5001 > 5002 > 5003, if I were to uninstall APMS5, and then reinstall it, before applying 5003 over 5000, would that affect my product activation?

Windows Xp Product Activation has been discussed sufficiently as to how it's tied to your hardware, and I was wondering whether the same method is used for APMS5 ?

Some of us tend to canabilise our PCs, gradually changing HDDs, mainboards, memory and CPUs every 3 - 6 months, and Windows Xp Product Activation so far has proven faithful. (I doubt whether a full reformat would be permitted, but incrementally like a drivers license demerit point system, every three months you can be tempted by, for example, "that latest amazing graphics card".

Cheers,

John

[leebos]

Oops...mistake. I did not apply 5002, went from 5001 to 5003. Uninstalled, (in order to go back to 5000), and then found out I do not have my original CD with me, will have to wait until after the holidays. I guess I really didn't want to work during the holidays.

Lee

[Brett]

If you are having troubles with the upgrade, please email me at brett@indigorose.com. Please include a full description of what you have tried and what the problem is. As well, include your contact information and your AMS50 serial.