OpenEuphoria

Re: poke4 won't accept my 32bit values

• Posted by Igor Kachan <kinz at peterlink.ru> Mar 22, 2001
• 501 views

------=_NextPart_000_01C0B300.97F101A0

Chris Bensler wrote:

> Thank you Robert,
>   I fixed that bug..
> instead of poking all four bytes, I changed it to only poke the first 
> two bytes from int_to_bytes.. This works with Safe.e
> But like you said, after this fix, the system hangs on Safe.e
> When I run the fixed demo with Machine.e, I get the same error..
> poke4 is limited to 32-bit numbers
> I think what you found was just ANOTHER bug, not the one I'm trying to 
> solve..

On my favourite 386-25 8M RAM  Win95 machine,
win32lib.ew v0.45r works wery well.

But v 0.50c++ can not open comctl32.dll,
if I run both standard machine.e or save.e.
In this case, error message appeas in the
Win's crash message box without ex.err file(!),
and, in this box, text is
"Win32lib Error
Common controls could not be initialized!"

I think for day and night - Why not ?
My mainframe-386?

But, if I use machine.e then v 0.55.1 crashes
whith the next message:

"Win32lib App Window - Fatal Error
         Error code 498
Common controls could not be initialized!
       Win32lib v 0.55.1"

And if I run v 0.55.1 with save.e then
save.e says me about incorrect *poke*
and gives ex.err before this message above
as well (See attachment).

Then I begin to understand that 
8M RAM of my mainframe may be full
of starting win32lib.

And I think - what about virtual memory?

Note, I run pure win32lib.ew whithout
any app, without just one button.

And again I love very much the simplest
solution - 386+Eu_DOS32.

Can you say me what RAM I need to
have 500 buttons (at all) in 5
windows on Win32 ?
Just interesting to know
without programming :::---)))

Regards,
Igor Kachan
kinz at peterlink.ru

------=_NextPart_000_01C0B300.97F101A0
Content-Description: Ex-55-1.err (ERR )