Clarion for DOS 2.1 on Windows network

Hi,
we use Clarion for DOS 2.1 in Windows network. 5 Dos windows we can
open from Windows PC´s on network and we can access to one Clarion
dbs. Very often we receive error messages, that keys are defected (it
is not exactly translation from our language). Clarion is able to
repair defected files with keys, but for
our business application (POS in shop)is not acceptable to get this
problem 1 or 2 times per day. Our local vendor of application software
for POS is not able to give us any solution to avoid problems.

By my expierence it is not network traffic problem ( last error
receive in 1AM)or bad network (we have certified structured cabling
level5, 100Mbs).

My technical feeling is some inconsistency in files with keys (*.k00,
*.k01, ..).

What I would receive:
- Any recomendation what to check or how to start
- Is possible to get any logs information about the cause of problems
? Exist any debuging tools?

Thank you in advice for any help

Jaroslav

Hi Jarda,


Here are 2 web sites that I have found very useful in regards to windows
networking issues. Take a look and see if they help you.

http://www.cardbox.co.uk/ntserver.htm

http://www.granitebear.com/network.htm

The opportunistic file locking information is very important when working
with ISAM databases.

--
Best Regards,
Earl R Coker
ksasales AT machlink DOT com
kwiksys AT kwiksystems DOT net
www.kwiksystems.net
www.kwiksystems.com
www.kwiksystems.com/clarion.htm (BigTamer(tm) Templates)



"Jarda" <jaroslav.pulda@albiostyl.cz> wrote in message
news:254c3a3c.0403101848.7366c608@posting.google.com...
> Hi,
> we use Clarion for DOS 2.1 in Windows network. 5 Dos windows we can
> open from Windows PC´s on network and we can access to one Clarion
> dbs. Very often we receive error messages, that keys are defected (it
> is not exactly translation from our language). Clarion is able to
> repair defected files with keys, but for
> our business application (POS in shop)is not acceptable to get this
> problem 1 or 2 times per day. Our local vendor of application software
> for POS is not able to give us any solution to avoid problems.
>
> By my expierence it is not network traffic problem ( last error
> receive in 1AM)or bad network (we have certified structured cabling
> level5, 100Mbs).
>
> My technical feeling is some inconsistency in files with keys (*.k00,
> *.k01, ..).
>
> What I would receive:
> - Any recomendation what to check or how to start
> - Is possible to get any logs information about the cause of problems
> ? Exist any debuging tools?
>
> Thank you in advice for any help
>
> Jaroslav

Hi Jarda,
We have many sites with networks running 2.1 files. Most key corruption has
ceased since we insisted that clients use NT based O/S. My opinion is that
keys are held in RAM and are not written back as consistently as .dat files
particularly on Win98. We refuse to support 95, 98 or ME.
Despite the above, corruption still occurs and can usually be traced back to
faulty network cards, cabling, and incorrect settings for Oplocks. The sites
that Earl has mentioned are a good start.
Regards
Neville Wright
neville@myesk.ws



"Jarda" <jaroslav.pulda@albiostyl.cz> wrote in message
news:254c3a3c.0403101848.7366c608@posting.google.com...
> Hi,
> we use Clarion for DOS 2.1 in Windows network. 5 Dos windows we can
> open from Windows PC´s on network and we can access to one Clarion
> dbs. Very often we receive error messages, that keys are defected (it
> is not exactly translation from our language). Clarion is able to
> repair defected files with keys, but for
> our business application (POS in shop)is not acceptable to get this
> problem 1 or 2 times per day. Our local vendor of application software
> for POS is not able to give us any solution to avoid problems.
>
> By my expierence it is not network traffic problem ( last error
> receive in 1AM)or bad network (we have certified structured cabling
> level5, 100Mbs).
>
> My technical feeling is some inconsistency in files with keys (*.k00,
> *.k01, ..).
>
> What I would receive:
> - Any recomendation what to check or how to start
> - Is possible to get any logs information about the cause of problems
> ? Exist any debuging tools?
>
> Thank you in advice for any help
>
> Jaroslav