access violation on initial macroscheduler run: Vista 64

[roguesrus]

Vista64, all the latest updates. I read all the posts with similar errors suggesting this problem goes back a year or more in varying forms.

I get two kinds of errors (randomly) upon startup:

"Exception EReadError in module msched.exe at 000291EF. Error reading StatusBar1.Panels: Access violation at address 028E0000. Write of address 028E0000."

and

"Access violation at address 00910000. Write of address 00920000."

The addresses will vary somewhat, but the outcome is the same: The program won't work upon install.

[roguesrus]

I found this solution on the website of your competitor, Tethys. The problem appears to be the Date Execution Protection. When I disabled this, macro scheduler worked.

The problem that occurs on your machine shows up on CPUs that support "Data Execution Protection (DEP)" and Vista has it turned on for all programs as it's an important security feature.

We would request you to please go to Control Panel, System-> Advanced and change DEP to be for "Microsoft essential programs only". This crash only happens when DEP is set to "Turn on DEP for all programs and services". Switch DEP to "Turn on DEP for essential Windows programs and services only" and try to launch Workspace Macro Pro again and see if this helps.

Also, try disabling the DEP (Data Execution Prevention) for Workspace Macro Pro.

1) Open the Windows Vista control panel, then the "System and Maintenance" item.
2) Open the "System" item there, then the "Advanced System Settings" on the left side.
3) On the Advanced tab, click the Settings button in the Performance area.
4) Finally on the Data Execution Prevention, add Workspace Macro Pro to the list of exceptions.