If you get my program working the way I want it, you win. If several people contribute, I'll split the 600 points in a way I think is fair, based on each contribution.
I run Virtual Pascal v2.1 build 243. It works fine in XP and Vista.
When I run it in Windows 7, I get an error about 90% of the time when I compile and run any program, even a "Hello World" program. The error is:
Exception XCPT_ACESS_VIOLATION (C0000005) at 00404D96, TID = 17E4.
All the addresses change each time you reload it. If you don't reload it, but rerun it, you get an identical error with identical addresses.
The workaround is to close the VP integrated environment compiler, reload it and rerun it. Eventually, it works. It runs correctly about 10% of the time, requiring about 10 loads per attempt.
It's extremely aggravating. Most of my modeling software is written in this primitive (but easy to use) environment.
I want a solution that lets me run this in Windows 7, and never gives me this (or some other) error much of the time.
I run Virtual Pascal v2.1 build 243. It works fine in XP and Vista.
When I run it in Windows 7, I get an error about 90% of the time when I compile and run any program, even a "Hello World" program. The error is:
Exception XCPT_ACESS_VIOLATION (C0000005) at 00404D96, TID = 17E4.
All the addresses change each time you reload it. If you don't reload it, but rerun it, you get an identical error with identical addresses.
The workaround is to close the VP integrated environment compiler, reload it and rerun it. Eventually, it works. It runs correctly about 10% of the time, requiring about 10 loads per attempt.
It's extremely aggravating. Most of my modeling software is written in this primitive (but easy to use) environment.
I want a solution that lets me run this in Windows 7, and never gives me this (or some other) error much of the time.

buy a macbook
anyway 7 is one big big big shit


hihehehe