Scribd
Upload
517 views3 pages

CAESAR II Startup Problem

The document describes a problem where CAESAR II modules fail to start after installation on Windows XP, Vista, and 7. This is caused by a Windows Performance Option setting called Data Execution Prevention. There are three corrective methods provided to clear the check next to "Windows Explorer" in the Data Execution Prevention tab, edit the registry to change a value, or temporarily run CAESAR II from the command prompt after changing a environment variable. Any of the methods require administrator privileges and may need IT assistance if settings are managed by the network.

Uploaded by

Gede Resa Udayana
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
517 views3 pages

CAESAR II Startup Problem

The document describes a problem where CAESAR II modules fail to start after installation on Windows XP, Vista, and 7. This is caused by a Windows Performance Option setting called Data Execution Prevention. There are three corrective methods provided to clear the check next to "Windows Explorer" in the Data Execution Prevention tab, edit the registry to change a value, or temporarily run CAESAR II from the command prompt after changing a environment variable. Any of the methods require administrator privileges and may need IT assistance if settings are managed by the network.

Uploaded by

Gede Resa Udayana
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Problem:

Many CAESAR II modules fail to start. Affected modules include (but aren’t necessarily limited to) Input,
Static Output, Output Animation and Isogen Output. This problem can occur on Windows XP, Windows
Vista and Windows 7.

Diagnosis & Solution:


CAESAR II runs normally after installation, but fails to run once the user logs off or the machine is
rebooted. Re-running the installation will restore the system to an operational state, but the repair is only
effective for that single session.

The problem was traced to a Windows Performance Option setting called Data Execution Prevention.
There are several ways to correct this problem, all of which require administrator privileges. It is also
possible that this value is set by your network administrator, in which case you will need assistance from
your IT department.

Corrective Method 1:

1. Right-click on “My Computer” (on Vista and Windows 7 systems, right-click “Computer”) and
select “Properties”.
2. Choose the “Advanced” tab.
3. On the “Advanced” properties page, click the “Settings” button in the Performance section.
4. On the Performance Options box, click the “Data Execution Prevention” tab

5. Clear the check next to “Windows Explorer” and press the “Apply” button.
6. Click “OK” and reboot the machine.

Corrective Method 2:

1. Start the Registry Editor (<Windows key>+R, type RegEdit in the box)
2. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\AppCompatFlags\Layers.

3. Edit the value under <Windows Install Folder>\explorer.exe to EnableNXShowUI


4. Close RegEditor and reboot.
Corrective Method 3 (temporary only, and then only for CAESAR II sessions
started with this method):

1. Open a Command Prompt window (XP, Vista, Windows7: Start|Accessories|Command Prompt.


Keyboard shortcut <WindowsKey>+r, type cmd<Enter>)
2. At the command prompt, type this series of commands:
cd “c:\Program Files\COADE\CAESAR II 5.20”<enter>
set __COMPAT_LAYER=<enter>
c2.exe<enter>

You might also like