So, if I'm not using Novell, but only the Windows standard network setup (peer to peer, using a Workgroup network), are my reg hacks correct?

I'm surprised that this wouldn't be a Microsoft knowledge base entry, as well.
Allen

>Hi,
>The reg hacks you mentioned are for Windows Networking only, for a Novell environment do the following:-
>
>Use the latest Client
>
>ON THE SERVER
>
>Add SET CLIENT FILE CACHING ENABLED = OFF to the AUTOEXEC.NCF and reboot the server.
>
>ON THE WORKSTATION
>
>In Control Panel/Networking go into the Properties for the NIC, and in the properties section of the Novell Client disable the following options
>
>1. Opportunistic Locking Off
>
>2. Packet Burst Mode Off
>
>3. Server caches writes Off
>(this may be described differently)
>
>4. Large internet Packets Off (Optional)
>
>The following setting is Optional, if you have continuing problems (may slow the system down considerably)
>
>5. TrueCommit Off
>
>-Or- this link contains all the reg hacks in the advanced section, it is a good read as has a lot of info relevant to a Novell environment http://www.novell.com/coolsolutions/appnote/620.html
>
>
>
>>>Hi,
>>>Have disabled client file caching on the server.
>>>Also check this link out http://www.superbase.com/services_tech_support_net_fact_sheet.htm
>>>
>>>>I am just beginning work for a new client. This client wanted a VFP5 app upgraded to VFP9..they're using Novell (lastest version). After the conversion (very little changes needed to be made), they started getting file and memo corruption errors as well as indexing errors.
>>>>
>>>>I took a copy of the data and tried a recopy using SCATTER MEMO MEMVAR to a new fresh data file (using GATHER MEMO MEMVAR) in VFP90. I got the same errors. (Running XP Professsional)
>>>>
>>>>So, just to be sure (my version of VFP9 is new), I tried the same thing on VFP8. NO ERRORS! Then I took the new data file (8.0) and ran it through the same program only this time now in VFP9 and NO ERRORS.
>>>>
>>>>I don't understand why VFP version 9.0 would give me this problem.
>>>>
>>>>Since I converted my regular customers to VFP90 on another app, there have only been occasional memo corruption and numerous indexing errors on Novell networks only.
>>>>
>>>>This new customer is also running Novell.
>>>>
>>>>Is there some incompatability between Novell and VFP90?
>>>>
>>>>Thanks in advance.
>>
>>
>>After reading the article you linked, I'm considering making the recommended changes, but would like to get a confirmation of what I'm about to do:
>>(Note: All my computers are Windows XP)
>>
>>1. On the computer that is acting as the data server (database residing computer)... enter a registry entry of: EnableOplocks value(REG_DWORD): 0
>> (under the key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
>>\Services\LanmanServer\Parameters)
>>
>>2. On the client computers (and on the server, if it's also acting as a client of itself, correct?)... enter a registry entry of: UseLockReadUnlock value(REG_DWORD): 0
>>(under the key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
>>Services\LanmanWorkstation\Parameters)
>>
>>3. On the client computers (and on the server, if it's also acting as a client of itself, correct?)... enter a registry entry of: UtilizeNtCaching
>> value(REG_DWORD): 0
>>(under the key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
>>Services\LanmanWorkstation\Parameters)
>>
>>4. On the client computers (and on the server, if it's also acting as a client of itself, correct?)... enter a registry entry of: OplocksDisabled
>> value(REG_DWORD): 1
>>(under the key:HKEY_LOCAL_MACHINE\System\CurrentControlSet\
>>Services\MRXSmb\Parameters)
>>
>>So that's what I've understood the article's instructions to be. Did I get that correct? And, is this really what many of you, who use VFP databases (as opposed to Sql Server) are doing?
>>
>>Thanks for the help.
>>Allen