From: Karl-Heinz on
Folks,

i noticed a strange behaviour running 2.5b3 on a Win7 Prof 32-bit machine. I
start 2.5 via a desktop linkage. All works fine until i select one
of the compatibility modes e.g "XP (SP2)". Afterwards only the editors
"Source code" "Menu" and "Report" are usable. Trying to edit e.g. a window
binary via a doubleclick ends up with the "subsystem not available" msg.
Also, within the VO-Menu the corresponding menuitems
are grayed out. As soon as i deactivate the compatibility mode all editors
are reachable again.

Anyone noticed the same 2.5 behaviour ?


BTW:

- i have full access to my "CAVO25" directory. So i doubt it�s a common
rights problem.

- There are no such problems using VO 2.8


regards
Karl-Heinz








From: Geoff Schaller on
K-H,

I guess I have two questions <g>.

Why on earth use compatibility mode (it shouldn't be required for any
win32 application) and why are even worrying about VO 2.5? I chucked my
2.5 disk onto my W7 (which is 64 bit though) and it runs as expected
(although I had to cheat the lic prog). But hey, VO 2.8 SP3 runs just
fine.

Geoff


"Karl-Heinz" <invalid(a)invalid.invalid> wrote in message
news:7s544tF4o0U1(a)mid.individual.net:

> Folks,
>
> i noticed a strange behaviour running 2.5b3 on a Win7 Prof 32-bit machine. I
> start 2.5 via a desktop linkage. All works fine until i select one
> of the compatibility modes e.g "XP (SP2)". Afterwards only the editors
> "Source code" "Menu" and "Report" are usable. Trying to edit e.g. a window
> binary via a doubleclick ends up with the "subsystem not available" msg.
> Also, within the VO-Menu the corresponding menuitems
> are grayed out. As soon as i deactivate the compatibility mode all editors
> are reachable again.
>
> Anyone noticed the same 2.5 behaviour ?
>
>
> BTW:
>
> - i have full access to my "CAVO25" directory. So i doubt it�s a common
> rights problem.
>
> - There are no such problems using VO 2.8
>
>
> regards
> Karl-Heinz