Table of Contents
Why I often receive Database or Index Corruption hosted in NT Server PCs (most probably caused by Opportunistic Locking) ?
Why I often receive Redirector error in Win95 PCs ?
Why I cannot debug in Win9x machine with Symantec products ?
How can I solve DOS Error 4 in Windows NT, 2000, or ME ?
Why I often receive Database or Index Corruption hosted in NT Server PCs (most probably caused by Opportunistic Locking) ?
To solve this, you should do the following:
1. Run RegEdt32.exe
2. Goto HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
3. Click Edit - Add Value menu
- Value Name: EnableOplocks
Data Type: REG_DWORD
Data: 0
- Value Name: CachedOpenLimit
Data Type: REG_DWORD
Data: 0
- Value Name: AutoDisconnect
Data Type: REG_DWORD
Data: FFFFFFFF
4. Restart NT Server
Read the Microsoft Knowledge Base articles in:
http://support.microsoft.com/support/kb/articles/Q219/0/22.ASP?LN=EN-US&SD=gn&FR=0
Go Top
Why I often receive Redirector error in Win95 PCs ?
To solve this, you should ensure all Win95 PCs are already updated to the latest vredir.vxd patch 4.00.1116. Download file vrdrupdr.exe
from Microsoft site, but I'll check whether it is allowed to published it publicly. Please be carefull, ignoring this error will cause
serious database corruption.
Read the Microsoft Knowledge Base articles in:
http://support.microsoft.com/support/kb/articles/Q174/3/71.asp
http://support.microsoft.com/support/kb/articles/Q148/3/67.asp
Go Top
Why I cannot debug in Win9x machine with Symantec products ?
Well, I observed several postings for trouble in running Clipper 5.x Debugger after installing a Symantec product in a Win9x PC.
To solve this problem, please do the following:
1. Run RegEdit
2. Delete key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\Symevent
3. Restart Windows
Go Top
How can I solve DOS Error 4 in Windows NT, 2000, or ME ?
Yes, DOS Error 4 means there is not enough file handles for your applications. The solutions are simple, increase your FILES= setting
in CONFIG.SYS and increase the number in Clipper environment variable SET CLIPPER=Fnnn or if you have Blinker, you can simply burn in
the setting in the executable itself, using BLINKER EXECUTABLE CLIPPER //F:nnn. Read your Blinker manual for further information.
Things become more complicated if you are using Windows NT, 2000, or Millennium Edition (ME); where CONFIG.SYS is not functioning at all.
If you use NT or 2000, set the FILES= in %systemroot%\system32\config.nt; i.e. C:\WINNT\SYSTEM32\CONFIG.NT
But if you use ME version, you should edit C:\WINDOWS\SYSTEM.INI in
[386Enh]
PerVMFiles=nnn
Note: Please replace all references of "nnn" with the maximum number of files you estimate. Remember, DOS reserves 5 file handles for
its own usage.
Go Top