Home > Archive > Clarion > January 2006 > Crashes in Windows XP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Crashes in Windows XP
|
|
|
| I have few applications developed in CLARION 5.5b using legacy
templates. I am facing a lot of abrupt crashes. Here are few
scenarios,
1. If the application is not used for some time and if you suddenly
click on the window it crashes.
2. Switching between applications sometimes causes the system to
crash.
3. Frequent Crashes are observed on WINDOWS XP.
4. Third Party OCXs are used.
Has anyone faced similar issues and has any solution to any of the
above problems.
OR
If you know some known crashes already.
Ajay
| |
| Paul S. Person 2006-01-21, 6:55 pm |
| On 21 Jan 2006 02:36:49 -0800, "AB" <ajayb@labinformationsystem.com>
wrote:
>I have few applications developed in CLARION 5.5b using legacy
>templates. I am facing a lot of abrupt crashes. Here are few
>scenarios,
>
>1. If the application is not used for some time and if you suddenly
>click on the window it crashes.
>2. Switching between applications sometimes causes the system to
>crash.
>3. Frequent Crashes are observed on WINDOWS XP.
>4. Third Party OCXs are used.
>
>Has anyone faced similar issues and has any solution to any of the
>above problems.
>
>OR
>
>If you know some known crashes already.
This is probably not relevant or useful, but I will mention it anyway:
Using Clarion for Windows Standard Edition 2.0 ("the best $50 I ever
spent") to generate a 32-bit executable, I have noticed that it is
noticeably less stable than the 16-bit version was. A few notes:
a) Windows XP Pro SP2 with as many "recommended" patches as Microsoft
has put out through Windows (or Microsoft) Update.
b) The only templates available to me are what I believe are now
referred to as "legacy templates".
c) Recompiling as a 32-bit executable was part of a more extensive
change which I believe is now complete but which may have left an
undiscovered problem (eg, the key used to sort a dependent table
changed but the button calling it is still using a field from the from
the key used formerly, which, of course, is immediately apparent when
seen but I can't guarantee I have seen every single dependent table to
verify that it is invoked correctly) which is destabilizing it.
Still, it does show these two strange behaviors, even with procedures
whose appearance is correct:
a) looping on the locator field, followed by several "gpf:main"
message windows; or
b) apparently random (at least, I don't know how to reproduce them)
crashes, also marked by one or more "gpf:main" message windows.
A "gpf:main" message window, of course, is a small modal dialogue
stating that "main" has caused a problem and must close.
And it does sometimes seem as if switching to the program and pressing
a key is the last thing I did before the crash.
--
"I begin to envy Petronius."
"I have envied him long since."
| |
| Earl R Coker 2006-01-21, 6:55 pm |
| Hi Ajay,
A possible suggestion is to migrate up to Clarion 5.5h Version. I have had
a couple of customers report that kind of a problem you describe but I have
never had that problem here on my development PC or other PC's on my 4 PC
peer-to-peer network. Those customers all had Intel P4 "hyper-threading"
processors and once they did "something or other" (they never did report
back to me what they did to get rid of their problem - too embarrased I
guess cause they were in the computer business e.g. computer store) their
problem "went away". All my PC's have AMD processors. <g>
I also believe your problem might possibly be due to a corrupted XP install.
I had the corrupted XP install problem myself not long after XP was released
but it primarily caused "boot-up" problems and not my apps crashing and a
"repair install" from the install CD took care of the problem.
Every time I did have the type of problem you are describing, it was usually
my embed code that caused it and once I (usually quickly) found the "bad
code" the problem went away. BTW, I use ABC. <g>
FWIW
--
Best Regards,
Earl R Coker
ksasales AT machlink DOT com
kwiksys AT kwiksystems DOT net
www.kwiksystems.net
www.kwiksystems.com
www.kwiksystems.net/appshell/index.htm
www.kwiksystems.com/clarion.htm (BigTamer(tm) Templates)
"AB" <ajayb@labinformationsystem.com> wrote in message
news:1137839809.703515.60560@f14g2000cwb.googlegroups.com...
>I have few applications developed in CLARION 5.5b using legacy
> templates. I am facing a lot of abrupt crashes. Here are few
> scenarios,
>
> 1. If the application is not used for some time and if you suddenly
> click on the window it crashes.
> 2. Switching between applications sometimes causes the system to
> crash.
> 3. Frequent Crashes are observed on WINDOWS XP.
> 4. Third Party OCXs are used.
>
> Has anyone faced similar issues and has any solution to any of the
> above problems.
>
> OR
>
> If you know some known crashes already.
>
> Ajay
>
| |
|
| the best what you can do . .is create the same application from
scratch..
also install clarion newly
for sure it will work, if it's not the ocx's what is the problem
|
|
|
|
|