1. Error while using Win32Lib

I've been getting an error while using Win32Lib, starting from version .014.
It only happens about every 4th or 5th time I run 2 different programs I've
been writing.  First I get an application error for EXW.EXE:

"The instruction at bff64e46 referenced memory at ffffffff
The memory could not be read from"

Then when I click to close the application, I get 2 concecutive errors which
make my hard drive sound like a machine gun and say "This program has
performed an illegal operation and will be shut down."  The Details for the 2
errors are:

EXW has caused an invalid page fault in module USER32.DLL at 0137:bff64e46

EXW has caused an invalid page fault in module KERNEL32.DLL at 01237:bff858cd

Does anyone have an idea on why I'm getting these errors?  I'm at a loss to
explain them.

Vincent Gonzales

new topic     » topic index » view message » categorize

2. Re: Error while using Win32Lib

On Mon, 7 Dec 1998 15:45:55 EST, Vincent Gonzales  wrote:

>"The instruction at bff64e46 referenced memory at ffffffff
>The memory could not be read from"

I get this a lot when using puts or printf (like debugging information)
My fix is not to use these for debugging. Win32lib, I guess, is not handling
the console window properly (This is just a guess)

>Then when I click to close the application, I get 2 concecutive errors which
>make my hard drive sound like a machine gun and say "This program has
>performed an illegal operation and will be shut down."  The Details for the 2
>errors are:
>
>EXW has caused an invalid page fault in module USER32.DLL at 0137:bff64e46
>
>EXW has caused an invalid page fault in module KERNEL32.DLL at 01237:bff858cd

Maybe be related to the above?

Greg Harris
HHS

new topic     » goto parent     » topic index » view message » categorize

3. Re: Error while using Win32Lib

>On Mon, 7 Dec 1998 15:45:55 EST, Vincent Gonzales  wrote:
>
>>"The instruction at bff64e46 referenced memory at ffffffff
>>The memory could not be read from"
>
>I get this a lot when using puts or printf (like debugging information)
>My fix is not to use these for debugging. Win32lib, I guess, is not
handling the console window properly (This is just a guess)

It freezes my system sometimes without win32lib even loaded running under
exw. However I was assuming this was more or less a configuration/win98
fault. Anyways, I dont think this so-called 'console'-output should use a
dos-screen, why even bother all the risk to problems not to mention
performance. Lets open a *real* log screen!

Ralf

new topic     » goto parent     » topic index » view message » categorize

4. Re: Error while using Win32Lib

> I've been getting an error while using Win32Lib, starting from version
> .014. It only happens about every 4th or 5th time I run 2 different
> programs I've been writing.  First I get an application error for
> EXW.EXE:

> "The instruction at bff64e46 referenced memory at ffffffff
> The memory could not be read from"

I get a similar message box whenever I launch exw.exe with/without
win32lib or any exw program for that matter:

Application Error: C:\EUPHORIA\BIN\EXW.EXE
The instruction at 00000009 referenced memory at 70046517
The memory could not be written

> Then when I click to close the application, I get 2 concecutive errors
> which make my hard drive sound like a machine gun and say "This program has
> performed an illegal operation and will be shut down."  The Details for
> the 2 errors are:
<snip>

Similarly, I get two consecutive errors (but my hard drive is silent)

EXW caused an invalid page fault in
module <unknown> at 0000:00000009.
Registers:
EAX=00000001 CS=015f EIP=00000009 EFLGS=00010202
EBX=0041d924 SS=0167 ESP=0056fd0c EBP=0056fe2c
ECX=04000000 DS=0167 ESI=005802e8 FS=454f
EDX=0000003c ES=0167 EDI=00000000 GS=0000
Bytes at CS:EIP:
00 a0 16 65 04 70 00 65 04 70 00 54 ff 00 f0 79
Stack dump:
00000167 0040101a 0040511d 816dab9c 00000002 00000000 004002d3 00000022
0041681b 00400000 00000000 005802d2 0000000a 00560000 00000000 00000000

EXW caused an invalid page fault in
module KERNEL32.DLL at 015f:bff766ae.
Registers:
EAX=00000000 CS=015f EIP=bff766ae EFLGS=00010246
EBX=bff87fc0 SS=0167 ESP=00560000 EBP=00560000
ECX=00560100 DS=0167 ESI=816f97f8 FS=454f
EDX=0056015c ES=0167 EDI=00560018 GS=0000
Bytes at CS:EIP:
50 8b 45 08 c7 00 ff ff ff ff 50 6a 00 68 14 00
Stack dump:
005600e8 bff76737 00560018 005600e8 00000004 00560184 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000


> Does anyone have an idea on why I'm getting these errors?  I'm at a loss
> to explain them.

I don't know what causes them either.  I only know they started after my
2nd clean install of windows 98 4.10.1998 on an AMD-K6 3D processor with
128.0MB RAM.  I'm hoping it will work if I reinstall win98 again, or when
RDS releases version 2.1.

 _______  ______  _______  ______
[    _  \[    _ ][ _   _ ][    _ ]
[/| [_] |[/| [_\][/ | | \][/| [_\]
  |  ___/  |  _]    | |     |  _]
[\| [/]  [\| [_/] [\| |/] [\| [_/]
[_____]  [______] [_____] [______]
xseal at harborside.com  ICQ:13466657
http://www.harborside.com/home/x/xseal/euphoria/

new topic     » goto parent     » topic index » view message » categorize

5. Error while using Win32Lib

Vincent Gonzalves writes:

>>I've been getting an error while using Win32Lib, starting from version
.014.
It only happens about every 4th or 5th time I run 2 different programs I've
been writing.  First I get an application error for EXW.EXE:

"The instruction at bff64e46 referenced memory at ffffffff
The memory could not be read from"

Then when I click to close the application, I get 2 concecutive errors
which
make my hard drive sound like a machine gun and say "This program has
performed an illegal operation and will be shut down."  The Details for the
2
errors are:

EXW has caused an invalid page fault in module USER32.DLL at 0137:bff64e46

EXW has caused an invalid page fault in module KERNEL32.DLL at
01237:bff858cd

Does anyone have an idea on why I'm getting these errors?  I'm at a loss to
explain them.

Vincent Gonzales<<
Are you using v 0.15a? I thought these errors would be gone. There was a
bug in some allocation routines, when using lists and combo boxes. But
version 15 should be a fix to that.
David and/or Robert can explain things further.

Ad

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu