931
Setup & Installation / Re: RAM disk and temp folders...what else?
« on: April 20, 2018, 04:49:25 pm »
Hi Lars,
OK, step by step explanation:
Only using HPFS386 partitions. The only other IFSs deployed are: FAT32 & CDFS, but the CDFS is a standard these days and FAT32 is specific to just using memory cards/thumb drives.
Yes, G: is my boot drive, I am copying various sized files from G: to ramdisk, which is drive Y:
Ramdisk is drive Y:
Issuing 'cache386' @CLI shows the following:
So, to turn on the cache (lazy write really as per the option listing, but it appears to actually behave as if that controls the CACHE function) you issue 'cache386 /l:y:on', which can then be checked by issuing the following 'cache386 /o:y':
As best as I can tell issuing 'cache386 /l:y:off' disables or enables the HPFS386 cache:
Therefore, the previously reported results are specific to the above method of turning on the HPFS386 cache (lazy write) for the ramdisk drive 'Y:'.
As far as I can tell there is nothing else in the HPFS386 module which allows one to explicitly control the cache function, instead I believe it is the 'LAZY write' control that actually does this.
OK, step by step explanation:
1) do you ONLY have HPFS386 partitions on your HD ? Or do you also have JFS partitions ?
Only using HPFS386 partitions. The only other IFSs deployed are: FAT32 & CDFS, but the CDFS is a standard these days and FAT32 is specific to just using memory cards/thumb drives.
Quote
2) have you been copying from G: to ramdisk ?
Yes, G: is my boot drive, I am copying various sized files from G: to ramdisk, which is drive Y:
Quote
3) What driveletter does your ramdisk have ? It seems that it is neither F: nor G: so what is it ?
Ramdisk is drive Y:
Quote
4) What is the switch to cache386 to explicitely turn on/off caching for a specific drive letter ?
Issuing 'cache386' @CLI shows the following:
Code: [Select]
[G:\]cache386
Valid 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)
So, to turn on the cache (lazy write really as per the option listing, but it appears to actually behave as if that controls the CACHE function) you issue 'cache386 /l:y:on', which can then be checked by issuing the following 'cache386 /o:y':
Code: [Select]
[G:\]cache386 /o:y
CACHE386 options
Cache Size 65536 KB
Drive Y:
Lazy write: ON MaxAge: 15000 msec
BufferIdle: 5000 msec
As best as I can tell issuing 'cache386 /l:y:off' disables or enables the HPFS386 cache:
Code: [Select]
[G:\]cache386 /o:y
CACHE386 options
Cache Size 65536 KB
Drive Y:
Lazy write: OFF
Therefore, the previously reported results are specific to the above method of turning on the HPFS386 cache (lazy write) for the ramdisk drive 'Y:'.
As far as I can tell there is nothing else in the HPFS386 module which allows one to explicitly control the cache function, instead I believe it is the 'LAZY write' control that actually does this.