Re: Starting project EuphoriaVista Interpreter
- Posted by jimcbrown (admin) Jan 02, 2009
- 1297 views
Other than stating that 3.1.1 caused Vista to BSOD and the issue with DEP that iis being fixed in 4.0 alpha 3 (the DEP issue also applies to XP), you have not given a clear statement on what specifically is broken on Euphoria that makes it Vista incompatible. A few basic tests were done on Vista and eu 4.0 seems to work fine there. (More testing and bug reports are welcome of course.)
Specifically, I would not run ex.exe on Vista even with DEP "off".
have you tried:
C:\> set EUVISTA=1 c:\> ex
DOS programs that actually use graphics require you to switch to the standard VGA driver before they can be run on Vista (and they'll require full screen mode).
With DEP "on" window.exw doesn't work (but I heard that is being fixed). It returns with an error, the ex.err dump begins with:
<snip>
It fails at the Window creation. I don't know if many of the programmers have tested it with DEP "on" so that's why I'm sharing this output. With DEP "off" it will run even with sound, however, it makes the system more unstable (and vulnerable). In my opinion, it would be best to leave DEP "on" if you get Vista. I don't know how Genuine Windows protection works on WinXP, as far as I know it just disables updates. On Vista it can lock you out with only limited Internet connection, until it can be restored under Safe Mode. Changing the DEP option while working with exw.exe activated the Genuine windows protection mode. I don't know what exactly set it off, but I would be glad when exw.exe fully supports DEP "on" with Windowed Apps.
Yep, this sounds like a known issue. You can download a DEP enabled version of euphoria from the rapideuphoria.com archives already (by Shawn Pringle, the same person who is adding support to the main 4.0 branch).
As a side note, what is failing is the c_func() call itself (because of the "tricks" it uses to pass an arbiturary number of parameters of arbiturary types to the c function), not the CreateWindow api. We crash before we actually reach that point.
Integration with .NET and Java isn't necessarily bad. It is very complex (and would probably need to be a separate development branch at a minimum), but it could be worthwhile. Also, JNI and Mono work on non Windows platforms, so this could benefit other OSes besides Vista. (Mono even has some API compatibility with .NET I believe.)
You have some great ideas, jcmarsh. I look forward to seeing how you progress your project with them.
Deciding which ideas I have time for and the know-how to do is a tough question for me. I can design things that will work, but they might not be the best way to do them. That's one reason I'll need help on creating something other people can make use of as well.
I am happy to help with the little that I am able to give.
