Clipper 5.3b/Blinker 5.1 and Windows
I have seen this happen when there was a certain type of index or database
corruption. It's apparently caused by a stray pointer that accidentally
grabs INT 5 (print screen) recursively - which is never supposed to happen
either.
Almost always this was fixable by rebuilding indices; sometimes you may need
to repair the dbf as well. If I recall correctly, having many index keys
with the same value made this problem worse. If you're using Clipper 5.2x
with SIx or DBFCDX you also need to pay attention to the stack size -
Blinker Procedure Depth must be over 80 (I generally use 110)
Quote:
> On the PC's that have the problem, the problem doesn't occur always (only
> sometimes).
> On whitch code-line it starts to print printscreens with "Loading ...", we
> do not know. Between the displaying of "Loading..." on the screen and
> blanking the screen out to display something other, these things are done:
> some SET ... ON/OFF commands, then declaring some public variables and
> opening some files.
> I think the problem only occurs with Blinker.
> > > On some PC's we have a strange problem.
> > > When starting our Clipper-program (linked with Blinker 5.1), we
display
> > > "Loading..." while some files are opened. Suddenly the printer (lpt1)
> > > starts to print print screens (countinuously) en the program is
> blocked.
> > > Does anyone have a solution for this ??
> > First you need to say what your code is actually doing at the time the
> > problem occurs. The description you give here is vague at best.
> > --
> > Dave Pearson | OSLib - Timeslice release
> functions.
> > http://www.davep.org/ | eg - Norton Guide reader for
> Linux.
> > http://www.davep.org/clipper/ | weg - Norton Guide reader for
> Windows.
> > http://www.davep.org/norton-guides/ | dgscan - DGROUP scanner for
Clipper.
