Anonymous_User Absent Member.
Absent Member.
2353 views

Which Novell client for DOS database application on XP box [IP-only]?

Hi,

With legacy MS-DOS (Clipper) database multi-user application running in the
Windows XP desktop & Netware 6 file server environment and IP protocol only,
which Novell client proves to provide the most stability and the less speed
degradation?

TIA, Eugene


Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Which Novell client for DOS database application on XP box [IP-only]?

Hi Eugene

> With legacy MS-DOS (Clipper) database multi-user application running in
> the
> Windows XP desktop & Netware 6 file server environment and IP protocol
> only,
> which Novell client proves to provide the most stability and the less
> speed
> degradation?


This is an answer in an earlier thread. Maybe it apllies to clipper too:
With credits to Kevin

> We're are going to be running a (Windows and DOS) FoxPro 2.6a apps in
> parallel with its replacement, a VFP app for a while on a WinXP / NW 6.5
> environment.
> Have you encountered any problem or any performance issue with NSS

volumes?
> Any advice?
>
> Thank you.
>
> Eric.


Hi Eric,

No real problems to report. I have several tips you may be able to use,
though. We haven't run 2.6a apps in a long time, so I don't know how
those will play with 6.5's NSS - but we are currently running VFP5, 6,
7, 8, and soon to be 9 apps. YMMV, but here's what we are doing to keep
us running day-to-day;

1. Novell NetWare 6.5 - Disable file caching and oplocking. If you
aren't already doing this, do it now. Don't wait another minute.
Although Novell works very hard on this problem, and they will tell you
that it's fixed, they've been telling us for years that "it's fixed". (
Reference this TID http://tinyurl.com/dk7yf ) In this rare case, don't
believe them - it's never really been fixed in our environment.
Performance is fine for us without caching or oplocking enabled anyway.

To disable; At the server load monitor.nlm, under Server parameters set
NCP and Set Client File Caching = Off, and set Level 2 OpLocks Enabled =
Off and reboot the server. Do this as soon as you possibly can as
neither is disabled until the server is rebooted.

2. Novell NetWare 6.5 - Purge your volumes consistently and don't bother
with the old TFS set statements. If possible, enable purge immediate on
the volumes or folders your database will be in. If you don't do this,
at least set up a nightly or weekly purge using cron, task master or
Hamish Speirs' great Autopurge utility ( it can be found here;
http://www.caledonia.net/autopurg.html ). Also, with NetWare TFS,
typical FoxPro users used to have to set the maximum record locks and
file locks per connection much higher than the defaults. With NSS, the
default set statements have worked fine for us with no manual
adjustments. (Reference TID http://tinyurl.com/cdaky ).

3. Novell NetWare 6.5 - Stay current with support packs, but test! NW
6.5 SP2 has worked excellent for us, and we are waiting for SP3'A' to be
released once the memory issues others have experienced are resolved
(although I know of several companies running SP3 with no issues at all
- test it for yourself). Try to test support packs on a test server with
a recent copy of your database and a test workstation first. It's *very*
cheap to setup a test network today with new or used equipment - I
highly recommend that you do it if you haven't already.

4. Novell Clients - Use the latest, disable caching and NMAS. Do not use
the Microsoft Client for NetWare - whatever you have heard or read. Use
the latest Novell Clients for your OS (or possibly Native File Access).
Update your Novell Clients to the most current available for your
operating systems. Disable File Caching in the clients as well - we have
seen strange activity if it is not disabled on both the client and the
server. Be vigilant about testing the latest clients and patches as they
are released. Roll the latest clients out consistently across your
environment using one of the client update methods. Mixed Novell Client
versions can cause you problems, and not just with FoxPro apps. FWIW, we
are evaluating Native File Access, and while it looks promising, we are
a not ready to use this in production. Also, we have seen NMAS cause
some strange problems when enabled on the clients as well (with VFP and
MS Office). Disable NMAS on your servers and your clients if you don't
need it (on the client choose Advanced Login tab, NMAS Authentication
setting, set to OFF).

5. Microsoft Visual FoxPro. Stay current VFP runtime files on the
clients - but always test them on your test network and/or a few
machines first. If possible, shutdown your databases completely for your
backup window. We have never had great luck restoring VFP databases with
any of the open file managers. We have had much better results when
scheduling a forced shutdown of our primary databases and backing up the
traditional way. If you use an open file manager - be sure to try a real
life disaster recovery on any "bare metal box" using the open file
manager files and your backup tapes.

Hope this helps! Most of it you are probably already doing if you have
been running NetWare for any length of time with VFP. We have not had
the time to test Novell SuSE Enterprise Server or OES Linux Kernel and
VFP yet - but we eventually will do this as well. If you are coding from
scratch, you might want to evaluate MySQL on NetWare - it's free and
enterprise proven. We are looking at it for some web projects we have
coming up. Feel free to post in here or e-mail me direct if you ever
need additional information. Just remove the NO SPAM from the address in
the header if you use e-mail.

Regards,

Kevin Salisbury


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Which Novell client for DOS database application on XP box [IP-only]?

Peter,

While the message you're quoting does raise some interesting (mostly
well-known) points, it does not address IPX vs. IP issue.

Plus it suggests to use the latest client. I'm not sure it's such a
good idea for legacy DOS applications, especially in IPA-only
environments.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Which Novell client for DOS database application on XP box [IP-only]?


> Plus it suggests to use the latest client. I'm not sure it's such a
> good idea for legacy DOS applications, especially in IPA-only
> environments.


Eugene,

Agreed, but the same goes for running legacy DOS on XP...
If it were up to me I would give all users VMware Workstation and let them
work from a REAL dos 6.22 box with client 2.71 installed 🙂
This TID states which minimum versions to use with Clipper:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10069108.htm

We have no problem with our DOS database application (not Clipper) with
4.90sp2 basic and filecaching turned off. On the other hand, this version
causes problems with Access databases. Looks like we can't have it both
ways.
One patch will fix database access, the next one will break it again.

Peter


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.