Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unknown Internal Operating System Error

0 views
Skip to first unread message

Ernie DeVries

unread,
May 7, 1999, 3:00:00 AM5/7/99
to
I have a Windows95 PC that shares Paradox data with other PCs on the
network. The files reside on an NT4 server (which has had the
opportunistic locking & write-behind caching disabled). The PCs are
all running Pdox8 with SP1 installed.

Only one PC is having a problem, which is: if the user is viewing a
table after some variable amount of time he will receive an "unknown
internal operating system error" from Paradox & the application will
crash.

It makes no difference whether the user is in view or edit mode. The
only reference I've been able to find on this is at Borland.Com & is
related to a corrupt language driver in the BDE. I've upgraded to BDE
to 5.01, but this has not changed the behavior.

I'm at a real loss to explain this. I've previously swapped out every
hardware component in the system & the problem went away for a long time
after replacing the hard drive, but now it's back. Has anyone had any
similar experiences?


Mike Irwin [CTech]

unread,
May 7, 1999, 3:00:00 AM5/7/99
to
Ernie,

after some time a Windows system will disgard any locks that are over a
certain age and which have not been used, on the grounds that the app
is probably dead (<cynicism>and because Microsoft have a deal with the
network makers to try to force up net usage and thus user demand for
higher bandwidth</cynicism>). Then if the application tries to use the
lock, it's gone !

Alter the rate at which Paradox checks for changes on the net.
--
Mike Irwin
[Volunteer CTech Sysop, not a Corel employee
Please post enquiries and responses to the Corel newsgroups
(cnews.corel.ca).]


Ernie DeVries

unread,
May 10, 1999, 3:00:00 AM5/10/99
to
Thanks Mike. As I mentioned, this is actually a reoccurance of this
problem. The last time I fought with it I could get it to happen after
only 4 or 5 seconds of having the table in view. We eventually changed out
the hard drive (we were desperate since it was the only component we hadn't
changed) and the problem went away for several weeks.

Doing a search through DejaNews I've found some threads that indicate that
this may be a network problem so I'm going to explore that with my
networking team to see if we can isolate it. This seems likely since there
are 3 other PCs in this group that can have tables in view all day long
with no problem, but only this workstation displays this behavior. I've
tried to implement your suggestion, but I can't find a place to set this in
the BDE configuration program. Can you point me to it? I've checked the
help & can't find anything there either.


ewi...@my-dejanews.com

unread,
May 10, 1999, 3:00:00 AM5/10/99
to
I have had these same problems with network crashing Pdox with the data
on an NT4 server. This happens to me daily. I have to recode,
restructure, etc. many times a day. I have to kick out 4 or 5 users to
do this. It happens during queries, regular programming, etc. It is
one of the most frustrating things about using paradox. Nothing can be
as rewarding as Unknown Error fffffff. I think I finally understand
what the f's stand for.


--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---

Mike Irwin [CTech]

unread,
May 14, 1999, 3:00:00 AM5/14/99
to
it isn't in the BDE, but in the Preferences | Settings or Paradox
itself, under the Databases tab.

I'm looking for the registry entry, but I have to go resurrect a Win95
machine to do it ...

Kate Atkins

unread,
May 21, 1999, 3:00:00 AM5/21/99
to
We had a machine running Win98 on an NT4 network receiving the
"unknown internal operating system error" msg several times a day.
We reformatted the hard drive and swapped out cables & cards with a
'good' machine & finally narrowed it down to a connector on the
network cable.

We also added 128MB of RAM to our server, which was running on 96MB,
supporting 20 users at peak season. (ridiculous, i know)

David Ehle

unread,
May 26, 1999, 3:00:00 AM5/26/99
to
Ditto on network problems causing this. We had a hub that was going
out... machines would randomly disappear from network neighborhood, and
if someone had a file open (via peer-to-peer) on the machine that went
away, they would get this error. Replacing the hub fixed the problem on
all of the machines.

HTH
David

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
David A. Ehle
Director of Student Programs and
Field Course Coordinator
Gifted Education Resource Institute
Purdue University
1446 Liberal Arts and Education Building
West Lafayette, Indiana 47907-1446
eh...@purdue.edu
www.soe.purdue.edu/geri
(765) 494-7243
(765) 496-2706 (fax)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

0 new messages