1. RE: Prog crashes when closing (sometimes)
I tired it, seems to work fine..
Maybe you can give more details to what they are doing to cause it to
crash..
Is there something specific they are tryin to access in the program?
I tried loading the example file and click every button, nothing wrong..
Maybe it's the OS they are using.. or amount of Memory/Diskspace they
have.
I am running WIN98, on a 600Mhz PIII, with 64MB RAM and loads of
harddrive space..
Chris
Tony Steward wrote:
> Hi all,
> I have written a prog in EU. Both before and after binding it it runs
> and closes fine on my computer. I have been told by others who have
> downloaded the bound version that every time they close the program they
> get program performed illegal operation. Can someone download it from my
> web site and try it for me.
>
> location http://www.nlc.net.au/~figjam/Downloads/Keytrack.exe
>
> Thanks
> Tony Steward
>
> Come Visit Me At www.locksdownunder.com
>
>
2. RE: Prog crashes when closing (sometimes)
On a side note..
I got an error trying to access the help file..
Couldn't tell you what it is though, It's in Korean..
something about..
...:MK: at MSTIStore:..(PATH)../Keytrack.chm
Chris
Tony Steward wrote:
> Hi all,
> I have written a prog in EU. Both before and after binding it it runs
> and closes fine on my computer. I have been told by others who have
> downloaded the bound version that every time they close the program they
> get program performed illegal operation. Can someone download it from my
> web site and try it for me.
>
> location http://www.nlc.net.au/~figjam/Downloads/Keytrack.exe
>
> Thanks
> Tony Steward
>
> Come Visit Me At www.locksdownunder.com
>
>
3. RE: Prog crashes when closing (sometimes)
- Posted by leviathan at uswest.net
Mar 19, 2001
To tony:
> I tired it, seems to work fine..
> Maybe you can give more details to what they are doing to cause it to
> crash..
> Is there something specific they are tryin to access in the program?
>
> I tried loading the example file and click every button, nothing wrong..
>
> Maybe it's the OS they are using.. or amount of Memory/Diskspace they
> have.
>
> I am running WIN98, on a 600Mhz PIII, with 64MB RAM and loads of
> harddrive space..
>
> Chris
>
Where I, Win95B/466/96, crashed, the crash going on in the comctl
dll.
Perhaps the controls are being destroyed improperly? Or
something?
HTH,
--"LEVIATHAN"
4. RE: Prog crashes when closing (sometimes)
G'day all
Tony, I got the same as Leviathan, but only sometimes... strange...
I've got a P166 running Win ME (not a happy combination, but that's
another story...) 32Mb RAM, <400Mb free HD
leviathan at uswest.net wrote:
> To tony:
>
> > I tired it, seems to work fine..
> > Maybe you can give more details to what they are doing to cause it to
> > crash..
> > Is there something specific they are tryin to access in the program?
> >
> > I tried loading the example file and click every button, nothing wrong..
> >
> > Maybe it's the OS they are using.. or amount of Memory/Diskspace they
> > have.
> >
> > I am running WIN98, on a 600Mhz PIII, with 64MB RAM and loads of
> > harddrive space..
> >
> > Chris
> >
>
> Where I, Win95B/466/96, crashed, the crash going on in the comctl
> dll.
>
> Perhaps the controls are being destroyed improperly? Or
> something?
>
> HTH,
>
> --"LEVIATHAN"
>
>
Regards
Tony
5. RE: Prog crashes when closing (sometimes)
-----Original Message-----
From: Tony Steward [mailto:figjam at nlc.net.au]
>I have written a prog in EU. Both before and after binding it it runs and
closes fine on my >computer. I have been told by others who have downloaded
the bound version that every time they >close the program they get program
performed illegal operation. Can someone download it from my >web site and
try it for me.
This could be another manifestation of the ReleaseHeap problem mentioned
here last week (I believe you're using Win32Lib, right?).
Matt Lewis
6. RE: Prog crashes when closing (sometimes)
> From: Tony Steward [mailto:figjam at nlc.net.au]
>
> >I have written a prog in EU. Both before and after binding it it runs and
> closes fine on my >computer. I have been told by others who have downloaded
> the bound version that every time they >close the program they get program
> performed illegal operation. Can someone download it from my >web site and
> try it for me.
Nicely designed program!
I think the problem may be that it is using up resources.
After running it for a while, and getting ready to quit, I found that all the
file menu items (new,open, exit) were greyed out.
I can't reproduce the problem, unfortunately.
That would account for why it quits on some computers, but not others,
which may have more free resources.
Regards,
Irv
7. RE: Prog crashes when closing (sometimes)
> -----Original Message-----
> From: Matthew Lewis [mailto:matthewwalkerlewis at YAHOO.COM]
> -----Original Message-----
> From: Tony Steward [mailto:figjam at nlc.net.au]
>
> >I have written a prog in EU. Both before and after binding
> it it runs and
> closes fine on my >computer. I have been told by others who
> have downloaded
> the bound version that every time they >close the program
> they get program
> performed illegal operation. Can someone download it from my
> >web site and
> try it for me.
>
> This could be another manifestation of the ReleaseHeap
> problem mentioned
> here last week (I believe you're using Win32Lib, right?).
I take that back--now that I've actually looked at your program. :)
It looks like it's the problem of ListViews as children of TabControls.
Here's what I wrote last week:
"...I located the point at which I've had GPF trouble (once again, on
closing).
I tracked it down to SubProc. The crash happens when a TabControl gets a
WM_NOTIFY with an LVN_DELETEALLITEMS notification. This happens when the
app is closed, and when there is a ListView with a TabControl as parent. I
added this code to SubProc right above the call to xCallWindowProc:
if window_type[id] = TabControl and iMsg = WM_NOTIFY then
VOID = fetch( lParam, NMHDR_code )
if VOID = LVN_DELETEALLITEMS then
return popSelf()
end if
end if
For some reason, the tab control can't handle this message, but this
prevents a GPF."
Try modifying your copy of win32lib and the error should go away. I get the
error (PII300, W98) when I run your program, same as my program did until I
fixed Win32Lib. Perhaps MS fixed this bug in ME/2000.
Matt Lewis
