Nss volumes and clipper 16bit application

[Tim Heywood (NSC Sysop)]

I have a number of Clipper (5.2) apps that work fine with NSS. What seems to be
your problem?

Are your DB files VERY big (100mb+)?

Tim

On Mon, 29 Sep 2003 06:38:18 GMT, "Darko Martinoviæ" <darko.ma...@irata.hr>
wrote:

>Hi,
>
>Does anyone know how to setup nss volumes on which clipper application work?
>On traditional volumes everything was fine with clipper apps. On nss volumes
>somethin strange happens. What seems to be the trouble? Thanks in advance.
>D.
>

No Direct e-Mail Please!
--
****************
Tim Heywood
Independent Consultant
Scotland
(God's Country)
Novell Support Connection SYSOP
****************

In theory, practice and theory are the same,
In practice they are different!

[Darko Martinovic]

Hi,
I noticed very strange behavior. System sloooow down extremely.
What seems to be the trouble? NW6 ( small business ) sp3, client 4.9. Do you
apply some parametars for nss?
What is your nss configuration? Please send me, what do you change in server
parametars? Do dbf is up to 10MB.
Thanks in advance
"Tim Heywood (NSC Sysop)" <t...@iqx.co.uk> wrote in message
news:5nsfnv852hsr8dsen...@4ax.com...

[Tim Heywood (NSC Sysop)]

Post SP3 I change the TCPIP stack to TCP607k.exe I also run Purge_NW.exe (both
of these are downloads from support.novell.com)

On the server make sure that "Set client file caching enabled=off" This should
be the first line in the Autoexec.ncf

Try these and then we can expand from there.

Tim

On Mon, 29 Sep 2003 10:15:19 GMT, "Darko Martinovic" <darko.ma...@irata.hr>
wrote:

[Darko Martinovic]

Ok, I'm using purge daily as a schedule job, I'm using set client file
caching=off.
tcp/ip patch I did not apply until now. Please, tell me more. Regs. D.

"Tim Heywood (NSC Sysop)" <t...@iqx.co.uk> wrote in message

news:m15gnvs4jot510lt5...@4ax.com...

[Tim Heywood (NSC Sysop)]

On the workstations change Client32 and set True Commit to On.

Beginning with the NWFS.SYS dated 2Jan2002, the Novell Client for Windows
NT/2000/XP corrects performance problems caused by delays in attempting to
locate non-findable resources. This is accomplished by adding a bad server name
cache. This functionality is controlled via "Bad Server Name Cache Enabled" and
"Bad Server Name Cache Timeout" which are settable from the Advanced Settings
tab of the Novell Client Configuration properties page (via the red "N" system
tray icon).

The corresponding registry entries are:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetwareWorkstation\Parameters]
"Bad Name Cache Enabled"=dword:00000001
"Bad Name Cache Timeout"=dword:0000012c

"Bad Name Cache Enabled" can have a value of 0 or 1. 0 is off and 1 is on.

"Bad Name Cache Timeout" is how long the name will stay in the cache. This
value is in seconds and the default is 300 seconds (5 minutes). Enter this value
as the number of seconds, in hexadecimal.

The NWFS.SYS cache is able to remember bad names even if they appear to be valid
UNCs (ie \\.\Display3).

Note that there will be a delay the first time the client tries to locate a
resource, but subsequent tries will be fast, thanks to the bad name cache. To
eliminate the initial delay, it is also possible to pre-populate the bad server
name cache. This is done by editing the registry (no user interface is currently
available)

The name of the registry value is "BadServer" which is a multiple string value.
Server names added to this value will never timeout. For example, if you have a
NT4 server that you connect to, you can put its name in the "BadServer" value
and the Novell Client will never try to resolve that name.

How to add server named to the BadServer value:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide
problems that may require you to reinstall Windows NT to correct them.

1. Run Registry Editor (REGEDT32.EXE).

2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:

\SYSTEM\CurrentControlSet\Services\NetwareWorkstation\Parameters]

3. From the Edit menu, select Add Value.

4. Add the following (using Server1, Server2, and Server3 as examples):

Value Name: BadServer
Data Type: REG_MULTI_SZ
Data: Server1<CR>Server2<CR>Server3

NOTE: <CR> Indicates you should hit Enter on the keyboard

5. Choose OK and quit Registry Editor.

6. Shut down and restart Windows NT.

And if that doesn't work...

<G>

Tim

On Mon, 29 Sep 2003 13:24:31 GMT, "Darko Martinovic" <darko.ma...@irata.hr>

[Darko Martinoviæ]

I do not know what to say.
First thank you, but
True commit iz property of win95/98 wks, not nt/xp/w2k wks. I only have
nt/xp/w2k wks.
Second I have latest client version which means correct version on nwfs.sys.
Client finds server(s) resources through slp or?
Regs D.

"Darko Martinoviæ" <darko.ma...@irata.hr> wrote in message
news:urQdb.535$681...@prv-forum3.provo.novell.com...

[Tim Heywood (NSC Sysop)]

I beg to differ

Look in the client properties, advanced settings... File Commit. By default
this is off.

Tim

On Tue, 30 Sep 2003 08:37:01 GMT, "Darko Martinoviæ" <darko.ma...@irata.hr>
wrote:

>I do not know what to say.