1. RE: EuGrid - was Runs w/I FOR JONAS
Jonas Temple wrote:
> jbrown,
>
> Thanks for the suggestion, I'll give it a try.
>
> And yes, I did try using safe.e in place of machine.e. Of course the
> problem you run into when using win32lib is that tk_mem uses the Windows
> memory management routines so when a routine in tk_mem does a peek or
> poke against that memory safe.e shows an error, which is not true. My
> solution was to create a version of tk_mem that uses Euphoria's allocate
> and free routines instead (I also had to use register_block in other
> places in my code as well). Of course the bound program ran fine
> then...
>
> Derek, I would also like to get the traceable version of win32lib as
> well. Anything to help.
>
> Now if I can just have some Tylenol and antacid delivered.....
>
Jonas:
I don't know if you read my last post so I'll try again.
I can't seem to post using the web interface.
Are you sure that your public domain exw.exe file that
you are binding to is patched to run win32 programs above
version 4.00. If you search the old messages in the archive
you find out more about this problem. You may be running your
program with a newer version of the interpreter and
binding with an older version of the public domain interpreter.
======= Heres about how to do the patch from the archive
=================================================================
RE: win32 programmers.....CBEX and work around Derek Parnell
Jul 25, 2002 16:42 PDT
Thanks Tone,
this "fix" works fine for me too.
I just used Code-Genie to edit the exw.exe file and that did it.
At byte offset #C8, change the three bytes there (#03 #00 #0A in my case)
to #04 #00 #00
==================================================================
Bernie
2. RE: EuGrid - was Runs w/I FOR JONAS
Bernie,
No, I have never applied this patch. I just checked the referenced
bytes and they are {3,0,10}. Should this patch be applied to exw.exe
AND pdexw.exe?
Thanks for the tip!
Jonas
Bernie Ryan wrote:
> Jonas:
>
>
> I don't know if you read my last post so I'll try again.
>
> I can't seem to post using the web interface.
>
> Are you sure that your public domain exw.exe file that
> you are binding to is patched to run win32 programs above
> version 4.00. If you search the old messages in the archive
> you find out more about this problem. You may be running your
> program with a newer version of the interpreter and
> binding with an older version of the public domain interpreter.
>
3. RE: EuGrid - was Runs w/I FOR JONAS
After I posted my question about running the patch against exw.exe and
pdexw.exe I read through the documentation on bind. When you bind a
program it uses pdexw.exe instead of exw.exe (that is, if you have the
complete edition). I applied the patch to pdexw.exe only. I then
rebound the program and am still getting the same error. :(
Jonas
jordah at btopenworld.com wrote:
> yes it should,
> Tone helped me figure out the never ending bug with the comboboxex by
> presenting this fix
>
> Jordah
> ----- Original Message -----
> From: "Jonas Temple" <jktemple at yhti.net>
> To: "EUforum" <EUforum at topica.com>
> Subject: RE: EuGrid - was Runs w/I FOR JONAS
>
>
> > Bernie,
> >
> > No, I have never applied this patch. I just checked the referenced
> > bytes and they are {3,0,10}. Should this patch be applied to exw.exe
> > AND pdexw.exe?
> >
> > Thanks for the tip!
> >
> > Jonas
> > Bernie Ryan wrote:
> > > Jonas:
> > >
> > >
> > > I don't know if you read my last post so I'll try again.
> > >
> > > I can't seem to post using the web interface.
> > >
> > > Are you sure that your public domain exw.exe file that
> > > you are binding to is patched to run win32 programs above
> > > version 4.00. If you search the old messages in the archive
> > > you find out more about this problem. You may be running your
> > > program with a newer version of the interpreter and
> > > binding with an older version of the public domain interpreter.
> > >
> >
4. RE: EuGrid - was Runs w/I FOR JONAS
THIS IS DRIVING ME ABSOLUTELY MAD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This is no way to code.............
> After I posted my question about running the patch against exw.exe and
> pdexw.exe I read through the documentation on bind. When you bind a
> program it uses pdexw.exe instead of exw.exe (that is, if you have the
> complete edition). I applied the patch to pdexw.exe only. I then
> rebound the program and am still getting the same error. :(
5. RE: EuGrid - was Runs w/I FOR JONAS
Hi Jonas,
I have tried binding an app which uses EuGrid 1.1 - no problems on
Win98. It did get me thinking about the memory allocation I am using
though. At the moment I am using the tk_mem functions acquire_mem() and
release_mem() but I changed these to use acquire() and free() and the
grid seems to work just as well. If you would like I will send you this
version and you can see if it helps. If it works I will release this as
a patch to EuGrid so you won't be running a custom version.
Let me know your email address if you want to give this a try.
Regards,
Phil
Jonas Temple wrote:
> THIS IS DRIVING ME ABSOLUTELY MAD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
> This is no way to code.............
>
> > After I posted my question about running the patch against exw.exe and
> > pdexw.exe I read through the documentation on bind. When you bind a
> > program it uses pdexw.exe instead of exw.exe (that is, if you have the
> > complete edition). I applied the patch to pdexw.exe only. I then
> > rebound the program and am still getting the same error. :(
>
>
6. RE: EuGrid - was Runs w/I FOR JONAS
Phil,
Sure, I'll try anything at this point.....
Send it to jktemple at yhti.net
Thanks!
Jonas
Phil Russell wrote:
> Hi Jonas,
>
> I have tried binding an app which uses EuGrid 1.1 - no problems on
> Win98. It did get me thinking about the memory allocation I am using
> though. At the moment I am using the tk_mem functions acquire_mem() and
>
> release_mem() but I changed these to use acquire() and free() and the
> grid seems to work just as well. If you would like I will send you this
>
> version and you can see if it helps. If it works I will release this as
>
> a patch to EuGrid so you won't be running a custom version.
>
> Let me know your email address if you want to give this a try.
>
> Regards,
>
> Phil
>
7. RE: EuGrid - was Runs w/I FOR JONAS
Hi Derek,
I intended no innuendo, honest! I was working from Jonas' statement that
<snip>
And yes, I did try using safe.e in place of machine.e. Of course the
problem you run into when using win32lib is that tk_mem uses the Windows
memory management routines so when a routine in tk_mem does a peek or
poke against that memory safe.e shows an error, which is not true. My
solution was to create a version of tk_mem that uses Euphoria's allocate
and free routines instead (I also had to use register_block in other
places in my code as well). Of course the bound program ran fine
then...
</snip>
Which, although not in anyway conclusive, suggests to me that this is,
at heart, a memory allocation problem of some sort. What I am
suggesting is to see whether or not this problem is arising as some sort
of interaction *between* tk_mem and EuGrid in bound programs.
Memory allocation is a fairly minor part of EuGrid and it seems to be to
be worth trying a modification to a) see if it fixes the problem and b)
stop Jonas from having to use a modified version of a standard Eu lib.
Regards,
Phil
Derek Parnell wrote:
> ----- Original Message -----
> From: "Phil Russell" <pg_russell at lineone.net>
> To: "EUforum" <EUforum at topica.com>
> Sent: Tuesday, December 03, 2002 9:04 PM
> Subject: RE: EuGrid - was Runs w/I FOR JONAS
>
>
> I have to add that there is no evidence that the tk_mem routines are
> causing
> this or any other memory related issues.
>
> The tk_mem routines are still a better alternative to the standard Eu
> routines in a Windows environment.
>
> I innuendo is that the tk_mem routines are in some way suspect. There
> has
> been evidence to suggest that they are not harmful.
>
> I also maintain that the RDS provided routines are also not harmful. The
> primary difference is that with the tk_mem routines, released memory is
> made
> available to other processes where as the RDS free'd memory is still
> held by
> the Eu process that allocated it.
>
> ----------------
> cheers,
> Derek Parnell
>
>
8. RE: EuGrid - was Runs w/I FOR JONAS
Derek/Phil,
No innuendo on my part either. My statement of "tk_mem does a peek or
poke against that memory safe.e shows an error, which is not true" has
to deal with the fact that safe.e will show a read/write error if the
memory was not allocated directly with allocate(). In tk_mem since
memory is allocated through Windows functions and then peeked/poked with
Euphoria routines safe.e thinks it's an error, which in actuality it is
not.
My latest angle on finding the bug has been to open a text file and
write something to it at certain points in the program. I was thinking
that since puts(1,"test") sends the output to the screen that if I could
avoid screen i/o it would still bomb. It proved me wrong! Adding code
to open/write/close a text file got the program working. Maybe I should
just leave it in there :)
Jonas
Phil Russell wrote:
> Hi Derek,
>
> I intended no innuendo, honest! I was working from Jonas' statement that
>
> <snip>
> And yes, I did try using safe.e in place of machine.e. Of course the
> problem you run into when using win32lib is that tk_mem uses the Windows
>
>
> memory management routines so when a routine in tk_mem does a peek or
> poke against that memory safe.e shows an error, which is not true. My
> solution was to create a version of tk_mem that uses Euphoria's allocate
>
>
> and free routines instead (I also had to use register_block in other
> places in my code as well). Of course the bound program ran fine
> then...
> </snip>
>
> Which, although not in anyway conclusive, suggests to me that this is,
> at heart, a memory allocation problem of some sort. What I am
> suggesting is to see whether or not this problem is arising as some sort
>
> of interaction *between* tk_mem and EuGrid in bound programs.
>
> Memory allocation is a fairly minor part of EuGrid and it seems to be to
>
> be worth trying a modification to a) see if it fixes the problem and b)
> stop Jonas from having to use a modified version of a standard Eu lib.
>
> Regards,
>
> Phil
9. RE: EuGrid - was Runs w/I FOR JONAS
Phil,
Just tried the allocate/free version of EuGrid and got the same results.
I'm gonna explore some other possibilities....
Thanks!
Jonas
Phil Russell wrote:
> Hi Jonas,
>
> If you would like I will send you this
> version and you can see if it helps. If it works I will release this as
>
> a patch to EuGrid so you won't be running a custom version.
>
> Let me know your email address if you want to give this a try.
>
> Regards,
>
> Phil
>
> Jonas Temple wrote:
> > THIS IS DRIVING ME ABSOLUTELY MAD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> >
> > This is no way to code.............
> >
> > > After I posted my question about running the patch against exw.exe and
> > > pdexw.exe I read through the documentation on bind. When you bind a
> > > program it uses pdexw.exe instead of exw.exe (that is, if you have the
> > > complete edition). I applied the patch to pdexw.exe only. I then
> > > rebound the program and am still getting the same error. :(
> >
> >
10. RE: EuGrid - was Runs w/I FOR JONAS
Jonas,
Oh well. Another beautiful theory slain by an ugly fact...
Phil
Jonas Temple wrote:
> Phil,
>
> Just tried the allocate/free version of EuGrid and got the same results.
>
> I'm gonna explore some other possibilities....
>
> Thanks!
>
> Jonas
> Phil Russell wrote:
> > Hi Jonas,
> >
> > If you would like I will send you this
> > version and you can see if it helps. If it works I will release this
as
> >
> >
> > a patch to EuGrid so you won't be running a custom version.
> >
> > Let me know your email address if you want to give this a try.
> >
> > Regards,
> >
> > Phil
> >
> > Jonas Temple wrote:
> > > THIS IS DRIVING ME ABSOLUTELY MAD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> > >
> > > This is no way to code.............
> > >
> > > > After I posted my question about running the patch against exw.exe
and
> > > > pdexw.exe I read through the documentation on bind. When you bind
a
> > > > program it uses pdexw.exe instead of exw.exe (that is, if you have
the
> > > > complete edition). I applied the patch to pdexw.exe only. I then
> > > > rebound the program and am still getting the same error. :(
> > >
> > >
