Re: Self-contained executables on Windows 7

Hi Chris,

The functions I use are all basic windows memory functions which take care
of any alignment needed. I have no control over it.

I haven't noticed anything like you say. Of course on large and complicated
programs you may (rarely) get "supernatural" behavior. It happens in all
languages (I've had it also in C). What I usually do (after running out of
hair to pull out) is rewrite a large section. Otherwise, g4c seems to be
working ok for me on win 7 (except some small quips). I have a quite large
exe which I use (gcview.exe) which works ok. Here's a link:

http://g4c.matinaki.com/gcview.exe

The last compilation I have (which I use) is on win 7, in MS Visual Studio
2008, which is quite current. Here the executable I use. Try it and see if
it makes a difference:

http://g4c.matinaki.com/gui4cli.exe

Hope it helps..
Dimitris



On Sun, Feb 5, 2012 at 3:38 PM, chris.kevany <[email protected]> wrote:

> **
>
>
> Hi Dimitris,
>
> I have the strong impression Gui4Cli has a memory problem on Win 7.
> When I create self-contained executables the behaviour is very
> unpredictable and depends on the size of the scripts and also on
> the path where it runs from.
>
> Once a compile seems to be ok, it fails when I simply add a command
> to one of the scripts. Then when I add something more it does fine
> again. When a executable runs ok in one folder, it fails in another
> one. Perhaps something with memory allignment?
>
> I use a small loader that loads a number of guis from disk and then
> runs the main gui. When I quit this loader after it has done its job,
> my main gui stops at unpredictable places without any eror message.
> I have the most success when I keep the loader open.
>
> Perhaps it would help to re-compile Gui4Cli with a Win 7 approved
> compiler?
>
> Regards,
> Chris
>
>  
>