Re: Same form, but one system GPFs...?

#41

Kenneth,

Quote:

"The exception generated was c0000005 at address 4CE1036B
(OsLdMBRisCJKKana)"

That c0000005 error is a fairly common one, and sometimes difficult to
identify exactly, and, therefore, to eradicate. I've seen it!

I suggest some coffee... and Google on it...

See how MEMTEST goes, but, I've seen cases with memory that passed
MEMTEST, but was not suitable for the motherboard, and failed randomly
during normal (stressful) use of the PC. Cause: the RAM sticks were
"buffered", and the MB was designed for non-buffered. With high
activity, the actual buffering ICs heated, and caused nasty problems.

Any chance you have "identical" PCs, whereby you could swap around the
memory sticks?

Try killing all unwanted services before running the PDox app, in case
some other "app" is conflicting with your form.

Check that all updates have been applied to the OS itself.

What about local disk-space?. I think c0000005 sometime triggers on low
free-space.

Can't think of anythin' else right now!

- Mike

#42

Kenneth,

Quote:

"The exception generated was c0000005 at address 4CE1036B
(OsLdMBRisCJKKana)"

That c0000005 error is a fairly common one, and sometimes difficult to
identify exactly, and, therefore, to eradicate. I've seen it!

I suggest some coffee... and Google on it...

See how MEMTEST goes, but, I've seen cases with memory that passed
MEMTEST, but was not suitable for the motherboard, and failed randomly
during normal (stressful) use of the PC. Cause: the RAM sticks were
"buffered", and the MB was designed for non-buffered. With high
activity, the actual buffering ICs heated, and caused nasty problems.

Any chance you have "identical" PCs, whereby you could swap around the
memory sticks?

Try killing all unwanted services before running the PDox app, in case
some other "app" is conflicting with your form.

Check that all updates have been applied to the OS itself.

What about local disk-space?. I think c0000005 sometime triggers on low
free-space.

Can't think of anythin' else right now!

- Mike

#43

Kenneth,

Since you went back to a system-image of a time when all worked fine,
you should not be dealing with a paradox, bde or windows problem. The
logical conclusion would be, that you are either dealing with a hardware
problem in either the PC itself or it's connection to the network.

But a problem in that area, that only influences 1 form seems rather
unlikely. Unless there is something special about that form, that makes
it trigger the problem, where the others don't. So is there anything
specific about that form, that really makes it stand out from the
others? Does it access local- and/or network files or tables, that the
other forms don't? Does it access a larger number of tables; is it much
larger in size; does it use libraries, that the others don't; etc.

If such things are not the case, then a hardware problem remains rather
unlikely. Then the next best place to look, would be the server or
networksettings; could there be anything on there, that restrict this
specific PC in a way that the other PC's are not restricted?

Kind regards
Jan Stegehuis

Kenneth schreef:

Quote:

Hi Tony,

Please see my responses inline below...

On Tue, 12 Feb 2008 20:43:57 -0700, "Tony McGuire"
png.paradoxcommunity@com> wrote:

P9...

Full or Runtime?

Full version.

What minor version, and is the version the exact same for both
systems?

I will have that in the morning, but I am quite certain that
the versions are exactly the same on all boxes.

"All of a sudden" usually points to a Windows update, in my
experience.

Or to a software install that should be totally innocuous, but which
kills something within Paradox.

There were no modifications of the faulty system (in either
sense you describe.) Also, we image these systems frequently
and have returned to an image that was created when the
system had a clean installation of Windows about two months
ago. That image ran the Paradox form perfectly for those
many weeks. Now, having gone back to that image, we have the
problem.

Or even a new printer installed on the problem system.

Nope... Nothing new on the hardware side.
Does the operator of the problem system play games on the computer?

No games at all.

I think you said the form resides on the server. Does it (the form)
USE libraries or any other file type that are local to each computer?

The BDE configuration is local...

The form uses nothing that is local. All tables, libraries,
etc. are on the server. (This is, by the way, a "nominal"
server in that it also runs a non-server version of Windows
(I believe 2000 Pro) on our peer to peer lan of six boxes.
The "server" is not used as a workstation.

All that said, is there any chance that flaky memory on the
problem system could cause the problem I have described?

I am currently running Memtest+ and by morning it will have
about 15 hours on the clock, but at last check, it shows no
errors.

Thanks for any further help,

#44

Kenneth,

Since you went back to a system-image of a time when all worked fine,
you should not be dealing with a paradox, bde or windows problem. The
logical conclusion would be, that you are either dealing with a hardware
problem in either the PC itself or it's connection to the network.

But a problem in that area, that only influences 1 form seems rather
unlikely. Unless there is something special about that form, that makes
it trigger the problem, where the others don't. So is there anything
specific about that form, that really makes it stand out from the
others? Does it access local- and/or network files or tables, that the
other forms don't? Does it access a larger number of tables; is it much
larger in size; does it use libraries, that the others don't; etc.

If such things are not the case, then a hardware problem remains rather
unlikely. Then the next best place to look, would be the server or
networksettings; could there be anything on there, that restrict this
specific PC in a way that the other PC's are not restricted?

Kind regards
Jan Stegehuis

Kenneth schreef:

Quote:

Hi Tony,

Please see my responses inline below...

On Tue, 12 Feb 2008 20:43:57 -0700, "Tony McGuire"
png.paradoxcommunity@com> wrote:

P9...

Full or Runtime?

Full version.

What minor version, and is the version the exact same for both
systems?

I will have that in the morning, but I am quite certain that
the versions are exactly the same on all boxes.

"All of a sudden" usually points to a Windows update, in my
experience.

Or to a software install that should be totally innocuous, but which
kills something within Paradox.

There were no modifications of the faulty system (in either
sense you describe.) Also, we image these systems frequently
and have returned to an image that was created when the
system had a clean installation of Windows about two months
ago. That image ran the Paradox form perfectly for those
many weeks. Now, having gone back to that image, we have the
problem.

Or even a new printer installed on the problem system.

Nope... Nothing new on the hardware side.
Does the operator of the problem system play games on the computer?

No games at all.

I think you said the form resides on the server. Does it (the form)
USE libraries or any other file type that are local to each computer?

The BDE configuration is local...

The form uses nothing that is local. All tables, libraries,
etc. are on the server. (This is, by the way, a "nominal"
server in that it also runs a non-server version of Windows
(I believe 2000 Pro) on our peer to peer lan of six boxes.
The "server" is not used as a workstation.

All that said, is there any chance that flaky memory on the
problem system could cause the problem I have described?

I am currently running Memtest+ and by morning it will have
about 15 hours on the clock, but at last check, it shows no
errors.

Thanks for any further help,

#45

Kenneth,

Since you went back to a system-image of a time when all worked fine,
you should not be dealing with a paradox, bde or windows problem. The
logical conclusion would be, that you are either dealing with a hardware
problem in either the PC itself or it's connection to the network.

But a problem in that area, that only influences 1 form seems rather
unlikely. Unless there is something special about that form, that makes
it trigger the problem, where the others don't. So is there anything
specific about that form, that really makes it stand out from the
others? Does it access local- and/or network files or tables, that the
other forms don't? Does it access a larger number of tables; is it much
larger in size; does it use libraries, that the others don't; etc.

If such things are not the case, then a hardware problem remains rather
unlikely. Then the next best place to look, would be the server or
networksettings; could there be anything on there, that restrict this
specific PC in a way that the other PC's are not restricted?

Kind regards
Jan Stegehuis

Kenneth schreef:

Quote:

Hi Tony,

Please see my responses inline below...

On Tue, 12 Feb 2008 20:43:57 -0700, "Tony McGuire"
png.paradoxcommunity@com> wrote:

P9...

Full or Runtime?

Full version.

What minor version, and is the version the exact same for both
systems?

I will have that in the morning, but I am quite certain that
the versions are exactly the same on all boxes.

"All of a sudden" usually points to a Windows update, in my
experience.

Or to a software install that should be totally innocuous, but which
kills something within Paradox.

There were no modifications of the faulty system (in either
sense you describe.) Also, we image these systems frequently
and have returned to an image that was created when the
system had a clean installation of Windows about two months
ago. That image ran the Paradox form perfectly for those
many weeks. Now, having gone back to that image, we have the
problem.

Or even a new printer installed on the problem system.

Nope... Nothing new on the hardware side.
Does the operator of the problem system play games on the computer?

No games at all.

I think you said the form resides on the server. Does it (the form)
USE libraries or any other file type that are local to each computer?

The BDE configuration is local...

The form uses nothing that is local. All tables, libraries,
etc. are on the server. (This is, by the way, a "nominal"
server in that it also runs a non-server version of Windows
(I believe 2000 Pro) on our peer to peer lan of six boxes.
The "server" is not used as a workstation.

All that said, is there any chance that flaky memory on the
problem system could cause the problem I have described?

I am currently running Memtest+ and by morning it will have
about 15 hours on the clock, but at last check, it shows no
errors.

Thanks for any further help,

#46

Kenneth,

Since you went back to a system-image of a time when all worked fine,
you should not be dealing with a paradox, bde or windows problem. The
logical conclusion would be, that you are either dealing with a hardware
problem in either the PC itself or it's connection to the network.

But a problem in that area, that only influences 1 form seems rather
unlikely. Unless there is something special about that form, that makes
it trigger the problem, where the others don't. So is there anything
specific about that form, that really makes it stand out from the
others? Does it access local- and/or network files or tables, that the
other forms don't? Does it access a larger number of tables; is it much
larger in size; does it use libraries, that the others don't; etc.

If such things are not the case, then a hardware problem remains rather
unlikely. Then the next best place to look, would be the server or
networksettings; could there be anything on there, that restrict this
specific PC in a way that the other PC's are not restricted?

Kind regards
Jan Stegehuis

Kenneth schreef:

Quote:

Hi Tony,

Please see my responses inline below...

On Tue, 12 Feb 2008 20:43:57 -0700, "Tony McGuire"
png.paradoxcommunity@com> wrote:

P9...

Full or Runtime?

Full version.

What minor version, and is the version the exact same for both
systems?

I will have that in the morning, but I am quite certain that
the versions are exactly the same on all boxes.

"All of a sudden" usually points to a Windows update, in my
experience.

Or to a software install that should be totally innocuous, but which
kills something within Paradox.

There were no modifications of the faulty system (in either
sense you describe.) Also, we image these systems frequently
and have returned to an image that was created when the
system had a clean installation of Windows about two months
ago. That image ran the Paradox form perfectly for those
many weeks. Now, having gone back to that image, we have the
problem.

Or even a new printer installed on the problem system.

Nope... Nothing new on the hardware side.
Does the operator of the problem system play games on the computer?

No games at all.

I think you said the form resides on the server. Does it (the form)
USE libraries or any other file type that are local to each computer?

The BDE configuration is local...

The form uses nothing that is local. All tables, libraries,
etc. are on the server. (This is, by the way, a "nominal"
server in that it also runs a non-server version of Windows
(I believe 2000 Pro) on our peer to peer lan of six boxes.
The "server" is not used as a workstation.

All that said, is there any chance that flaky memory on the
problem system could cause the problem I have described?

I am currently running Memtest+ and by morning it will have
about 15 hours on the clock, but at last check, it shows no
errors.

Thanks for any further help,

#47

Kenneth,

Since you went back to a system-image of a time when all worked fine,
you should not be dealing with a paradox, bde or windows problem. The
logical conclusion would be, that you are either dealing with a hardware
problem in either the PC itself or it's connection to the network.

But a problem in that area, that only influences 1 form seems rather
unlikely. Unless there is something special about that form, that makes
it trigger the problem, where the others don't. So is there anything
specific about that form, that really makes it stand out from the
others? Does it access local- and/or network files or tables, that the
other forms don't? Does it access a larger number of tables; is it much
larger in size; does it use libraries, that the others don't; etc.

If such things are not the case, then a hardware problem remains rather
unlikely. Then the next best place to look, would be the server or
networksettings; could there be anything on there, that restrict this
specific PC in a way that the other PC's are not restricted?

Kind regards
Jan Stegehuis

Kenneth schreef:

Quote:

Hi Tony,

Please see my responses inline below...

On Tue, 12 Feb 2008 20:43:57 -0700, "Tony McGuire"
png.paradoxcommunity@com> wrote:

P9...

Full or Runtime?

Full version.

What minor version, and is the version the exact same for both
systems?

I will have that in the morning, but I am quite certain that
the versions are exactly the same on all boxes.

"All of a sudden" usually points to a Windows update, in my
experience.

Or to a software install that should be totally innocuous, but which
kills something within Paradox.

There were no modifications of the faulty system (in either
sense you describe.) Also, we image these systems frequently
and have returned to an image that was created when the
system had a clean installation of Windows about two months
ago. That image ran the Paradox form perfectly for those
many weeks. Now, having gone back to that image, we have the
problem.

Or even a new printer installed on the problem system.

Nope... Nothing new on the hardware side.
Does the operator of the problem system play games on the computer?

No games at all.

I think you said the form resides on the server. Does it (the form)
USE libraries or any other file type that are local to each computer?

The BDE configuration is local...

The form uses nothing that is local. All tables, libraries,
etc. are on the server. (This is, by the way, a "nominal"
server in that it also runs a non-server version of Windows
(I believe 2000 Pro) on our peer to peer lan of six boxes.
The "server" is not used as a workstation.

All that said, is there any chance that flaky memory on the
problem system could cause the problem I have described?

I am currently running Memtest+ and by morning it will have
about 15 hours on the clock, but at last check, it shows no
errors.

Thanks for any further help,

#48

Kenneth,

Since you went back to a system-image of a time when all worked fine,
you should not be dealing with a paradox, bde or windows problem. The
logical conclusion would be, that you are either dealing with a hardware
problem in either the PC itself or it's connection to the network.

But a problem in that area, that only influences 1 form seems rather
unlikely. Unless there is something special about that form, that makes
it trigger the problem, where the others don't. So is there anything
specific about that form, that really makes it stand out from the
others? Does it access local- and/or network files or tables, that the
other forms don't? Does it access a larger number of tables; is it much
larger in size; does it use libraries, that the others don't; etc.

If such things are not the case, then a hardware problem remains rather
unlikely. Then the next best place to look, would be the server or
networksettings; could there be anything on there, that restrict this
specific PC in a way that the other PC's are not restricted?

Kind regards
Jan Stegehuis

Kenneth schreef:

Quote:

Hi Tony,

Please see my responses inline below...

On Tue, 12 Feb 2008 20:43:57 -0700, "Tony McGuire"
png.paradoxcommunity@com> wrote:

P9...

Full or Runtime?

Full version.

What minor version, and is the version the exact same for both
systems?

I will have that in the morning, but I am quite certain that
the versions are exactly the same on all boxes.

"All of a sudden" usually points to a Windows update, in my
experience.

Or to a software install that should be totally innocuous, but which
kills something within Paradox.

There were no modifications of the faulty system (in either
sense you describe.) Also, we image these systems frequently
and have returned to an image that was created when the
system had a clean installation of Windows about two months
ago. That image ran the Paradox form perfectly for those
many weeks. Now, having gone back to that image, we have the
problem.

Or even a new printer installed on the problem system.

Nope... Nothing new on the hardware side.
Does the operator of the problem system play games on the computer?

No games at all.

I think you said the form resides on the server. Does it (the form)
USE libraries or any other file type that are local to each computer?

The BDE configuration is local...

The form uses nothing that is local. All tables, libraries,
etc. are on the server. (This is, by the way, a "nominal"
server in that it also runs a non-server version of Windows
(I believe 2000 Pro) on our peer to peer lan of six boxes.
The "server" is not used as a workstation.

All that said, is there any chance that flaky memory on the
problem system could cause the problem I have described?

I am currently running Memtest+ and by morning it will have
about 15 hours on the clock, but at last check, it shows no
errors.

Thanks for any further help,

#49

Kenneth,

Since you went back to a system-image of a time when all worked fine,
you should not be dealing with a paradox, bde or windows problem. The
logical conclusion would be, that you are either dealing with a hardware
problem in either the PC itself or it's connection to the network.

But a problem in that area, that only influences 1 form seems rather
unlikely. Unless there is something special about that form, that makes
it trigger the problem, where the others don't. So is there anything
specific about that form, that really makes it stand out from the
others? Does it access local- and/or network files or tables, that the
other forms don't? Does it access a larger number of tables; is it much
larger in size; does it use libraries, that the others don't; etc.

If such things are not the case, then a hardware problem remains rather
unlikely. Then the next best place to look, would be the server or
networksettings; could there be anything on there, that restrict this
specific PC in a way that the other PC's are not restricted?

Kind regards
Jan Stegehuis

Kenneth schreef:

Quote:

Hi Tony,

Please see my responses inline below...

On Tue, 12 Feb 2008 20:43:57 -0700, "Tony McGuire"
png.paradoxcommunity@com> wrote:

P9...

Full or Runtime?

Full version.

What minor version, and is the version the exact same for both
systems?

I will have that in the morning, but I am quite certain that
the versions are exactly the same on all boxes.

"All of a sudden" usually points to a Windows update, in my
experience.

Or to a software install that should be totally innocuous, but which
kills something within Paradox.

There were no modifications of the faulty system (in either
sense you describe.) Also, we image these systems frequently
and have returned to an image that was created when the
system had a clean installation of Windows about two months
ago. That image ran the Paradox form perfectly for those
many weeks. Now, having gone back to that image, we have the
problem.

Or even a new printer installed on the problem system.

Nope... Nothing new on the hardware side.
Does the operator of the problem system play games on the computer?

No games at all.

I think you said the form resides on the server. Does it (the form)
USE libraries or any other file type that are local to each computer?

The BDE configuration is local...

The form uses nothing that is local. All tables, libraries,
etc. are on the server. (This is, by the way, a "nominal"
server in that it also runs a non-server version of Windows
(I believe 2000 Pro) on our peer to peer lan of six boxes.
The "server" is not used as a workstation.

All that said, is there any chance that flaky memory on the
problem system could cause the problem I have described?

I am currently running Memtest+ and by morning it will have
about 15 hours on the clock, but at last check, it shows no
errors.

Thanks for any further help,

#50

On the offending system, are there ANY non-Paradox files in the
directory?

Or a directory with the same name as the table or form?

Really reaching, but...

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