HI

MY COMPANY UPGRADE FROM CAESARII-5.1 TO 5.2 LATEST VERSION,WE INSTALL AND TRY FIRST TIME ITS WORKING,WHEN I RESTART MY PC AND OPEN 5.2 THE PIPING INPUT DIALOG BOX WILL NOT OPEN,PLEASE ANY BODY HELP ME HOW TO SOLVE THE PROBLEM

This is a problem that a handfull of people have experienced. The issue seems to be that upon a restart of the machine, Windows is replacing a "system level" DLL that was installed by one of the prerequesites (a Prerequesite is a non-COADE file loaded by the installation process on an as needed basis). Obviously this shouldn't be happening.

The InstallShield people have attempted to assist in this matter, but they don't know what is going on either, and the "log files" don't indicate where the problem is.

You can recover from this problem by putting the CAESAR II DVD back in the drive and letting it do a "Repair". After this, the input will work fine, until the next time you restart Windows.

We are working to resolve this issue, but as usual, this problem doesnt' occur here are COADE.

Thank you for your reply,if they will find any solution plaese let me know.


Thank you

Look down at your Task Bar. Any chance your input processor is opening in a "minimized" state? If you see a second CAESAR II listing in your Task Bar when you open your input, click on that item and select Maximize from the list.

we already check this ,it not open in minimized state also.
Thanks
N.M.V

Hi,

Any results regarding the above topic?


thanks
N.M.V

We have not found a solution to this issue so far.

I am also having this issue. Is it possible to revert back to the previous release until a solution is found? Thanks

Sure, you could uninstall 5.20 and then reinstall your last 5.10, but the 5.20 job files are not downward compatible.

We believe we have found the cause and a solution to this issue. Please refer to the associated PDF file here:

hai i am not able to open caesar 5.2. while opening iam getting this type of error
THE ERROR IS FATAL ERROR #5100
THE CPU time/date stamp is earlier then the last access time of the ESL device.This is usually caused by incorrect boot date.

so please anybody for this problem.

^
same here.

We cant use 5.2 at the moment because it just gives the machine the blue screen of death.

5.1 is buggy as hell as well.

ramprabhu1983,
This problem seems like we incountered while upgrading from Caear II 5.0 to 5.10. All we have to do is we re enter the autorization code. I'm not sure if this will work in your case. Try it, and see how it works!

Ramprabhu1983 - your problem is that the date stored on your ESL is later than the machine date on your computer - so CAESAR II thinks you've back-dated the machine. Send the ESL Access Codes to techsupport to get this ironed out.

Superpiper - The quirkyness can be elimnated by changing the (graphics) configuration to use the "Windows Basic Video" driver instead of the "Opengl" driver.

Nald - the reauthorization codes will only work once, and they are specific to an individual ESL.