Have you narrowed it down to what is happening when the GPFs occur?

Is Paradox patched to sp3?

Have you checked to ensure that none of the printer names exceed 32
characters?

First guesses based on a new installation.


--
------------------------------
Tony McGuire

Did you correctly change the network card settings after reinstalling
W2K? It could be that those settings are messing things up. The blank
screen sounds like a network issue where Paradox can't refresh the data
for some reason. Just guessing here...

Zal

On 27-11-2007 11:31 Kenneth wrote the following email:

Might there be any files with non-Paradox extensions in the :work: or
riv: of that machine?
(Although I would expect you'd see issues on more than one form, if
that were the case.)

Have you tried copying that form from a machine without issues to the
one with issues?

And any libraries that form uses, as well.

Are you using other than 100% zoom on that form?

Does the form (or library, if used) use any external DLL calls or
ActiveX controls?

Have you tried using a delivered version of the form, or do you use
source version of the form? If source, try the delivered version
only.

Finally, have you tried updating the VIDEO driver on that machine? Do
you have a spare video card you could try?

Other than these, I'm about out of idears. Maybe someone else can
step up....


--
------------------------------
Tony McGuire

Kenneth

As this is a new installation of Paradox and the BDE:

1) Have you changed the default settings for MinBufSize and MaxBufSize in
BDE Admin? The default settings are too low IMO. And at least in the first
versions of Paradox for Windows, they were a cause of GPVs.

2) As you are using P9, corrupted toolbar files can cause GPVs.



--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Kenneth" <usenet (AT) soleSPAMLESSassociates (DOT) com> skrev i meddelandet
news:v5sok3pmfuhifts6q2s1ekvmc31morg9aj (AT) 4ax (DOT) com...

I think what was meant was that by default Windows has 'Allow OS to
put this device to sleep' checked; ostensibly to save power.

Shouldn't be specific to just one form, though.

YOu should still look to see the state of this setting, however.


--
------------------------------
Tony McGuire

If I had a dollar for every time that was stated here, but not checked
until later...

Again, though, creating issues specific to one form...not likely.

------------------------------
Tony McGuire

Kenneth wrote:
Well, thank you for thinking of ChimneySweep, but when you have a repeatable
and isolatable issue you can be pretty sure that you are not dealing with a
case of file-corruption.

The first thing I would do is to look at the Event Viewer -- a system tool
that you may need to be an Administrator to use. Look at all of the logs,
to see what might be recorded there.

Next, I would ponder exactly what FURTHER pattern might exist behind those
GPFs. Set up some experiments: particular tables? Particular operations?
Also, is the application-instability isolated or general?

When you say "entering data on a particular form on a particular
machine ..." I consider what might be the most-likely culprit. I don't
look at service-pack levels, because Paradox is pretty darned robust and
stable. (That's why we all love it so...) And it can't be the form
because we know that same network-resident form works fine elsewhere. In
fact because it DOES "work fine elsewhere," we are pushed again and again
toward something much more fundamental than what has been bantered-around
so far. I wish that I could conclude this paragraph with a grand
pronouncement of what that is: unfortunately, all I can say is that I feel
my "red herring" intuition going-off.

So let's do things. Log-off as user X and try logging-on as User-Y. Look
at those darned event-logs again. Look also at the server logs of the
file-server! Act on the working-assumption that we've all been barking up
the wrong tree somehow. Look for the "'DOH!' problem." Not because any of
us, including yourself, are in any way silly, but because we've all slapped
our foreheads with great force in situations just like this. "Screwball
problems..."


----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com

Kenneth

MinBufSize=8192 and maxBufSize=16384.

MinBufSize should be at least 1024, that's the old saying from the days when
you had to have 4 MB RAM to run Paradox for Windows. MaxBufSize should be
twice the size of MinBufSize.

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Kenneth" <usenet (AT) soleSPAMLESSassociates (DOT) com> skrev i meddelandet
news:drtqk3dt78928h9coqd59pphe3h69vscv5 (AT) 4ax (DOT) com...

Kenneth ,

What is the Private directory set to? You can have problems in queries (and
reports?) if the file name ends up too long.

HTH,
Jim Moseley