Jump to content

CACHE386.EXE: Difference between revisions

From EDM2
Ak120 (talk | contribs)
Created page with "Enables the cache for HPFS386. Only valid for the OS/2 Warp Server Advanced otherwise CACHE386.EXE is started by the following command: CALL=C:\OS2\CMD.EXE /Q /C C:\IBM386FS\..."
 
Ak120 (talk | contribs)
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:


options for CACHE386 (x is an optional drive letter):
options for CACHE386 (x is an optional drive letter):
 
* /OPTIONS[:x] - Display current configuration
* /OPTIONS[:x]  
* /STATS[:C|:D] - Display, clear, or dynamically display statistics
Display current configuration
* /LAZY[:x][:ON|:OFF] - Enable or disable lazy writing
 
* /MAXAGE[:x]:n - Change msDataAge to n milliseconds
* /STATS[:C|:D]  
* /BUFFERIDLE[:x]:n - Change msIdleBuf to n milliseconds
Display, clear, or dynamically display statistics
*:If no drive (x) is given, the option will apply to all HPFS drives.
 
* /LAZY[:x][:ON|:OFF]  
Enable or disable lazy writing
 
* /MAXAGE[:x]:n  
Change msDataAge to n milliseconds
 
* /BUFFERIDLE[:x]:n  
Change msIdleBuf to n milliseconds
 
If no drive (x) is given, the option will apply to all HPFS drives.
 
Each option may be abbreviated to a single letter, for example:
Each option may be abbreviated to a single letter, for example:
  CACHE386 /B:D:1000 (sets BufferIdle to 1000 for drive D)
  CACHE386 /B:D:1000 (sets BufferIdle to 1000 for drive D)
'''ATTENTION:''' This entry has to be done manually. If this statement is not added you'll get the following error 'Net 3091: the Cache386.exe is not running. The server cannot be started.
;ATTENTION: This entry has to be done manually. If this statement is not added you'll get the following error 'Net 3091: the Cache386.exe is not running. The server cannot be started.


Adding the parameter /STATS will display the statistic usage cache usage. This will help you to size the cache to a size where the minimum sized cache achieves the maximum hit rate.
Adding the parameter /STATS will display the statistic usage cache usage. This will help you to size the cache to a size where the minimum sized cache achieves the maximum hit rate.
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


[[Category:RUN Statements]]
[[Category:RUN Statements]]

Latest revision as of 04:46, 7 July 2020

Enables the cache for HPFS386. Only valid for the OS/2 Warp Server Advanced otherwise CACHE386.EXE is started by the following command:

CALL=C:\OS2\CMD.EXE /Q /C C:\IBM386FS\CACHE386.EXE >NUL

Call to the cache program for HPFS386

options for CACHE386 (x is an optional drive letter):

  • /OPTIONS[:x] - Display current configuration
  • /STATS[:C|:D] - Display, clear, or dynamically display statistics
  • /LAZY[:x][:ON|:OFF] - Enable or disable lazy writing
  • /MAXAGE[:x]:n - Change msDataAge to n milliseconds
  • /BUFFERIDLE[:x]:n - Change msIdleBuf to n milliseconds
    If no drive (x) is given, the option will apply to all HPFS drives.

Each option may be abbreviated to a single letter, for example:

CACHE386 /B:D:1000 (sets BufferIdle to 1000 for drive D)
ATTENTION
This entry has to be done manually. If this statement is not added you'll get the following error 'Net 3091: the Cache386.exe is not running. The server cannot be started.

Adding the parameter /STATS will display the statistic usage cache usage. This will help you to size the cache to a size where the minimum sized cache achieves the maximum hit rate.