The machine *may* also need to have the amount of physical RAM increased. It's *likely* that increasing the amount of free conventional memory will resolve the problem. If the machine is using VSHARE and the problem still occurs, then there are two known solutions:ġ) The available system memory must be increased. VSHARE should dynamically allocate the space for files and locks, so you should never run into this error unless you are running DOS's SHARE simultaneously. To use VSHARE, ensure that the following line is in the section of the system.ini file: Problems will occur if the machine is configured with both SHARE and VSHARE. Under Windows 3.1x, use VSHARE in the system.ini instead of SHARE. If the machine is configured to use SHARE, then its parameters should be increased.Īfter increasing SHARE's parameters in the config.sys or autoexec.bat file, the machine must be rebooted for the changes to take effect. The error indicates that that the share buffer has been exceeded at the operating system level. If the user exits VP/5 and immediately re-executes VP/5, the error goes away. It's possible to receive an Error 0 with a TCB(10)=-36 or -32 when OPENing a file using Visual PRO/5 on a Windows for Workgroups machine. Error 0, TCB(10)=-36 or -32, when OPENing a file under Windows for Workgroups Description:
0 kommentar(er)
