#37 closed enhancement (fixed)

Change config.sys call to run for cachef32

Reported by: abwillis Owned by:
Priority: major Milestone: Future
Component: IFS Version:
Severity: medium Keywords:
Cc:

Description

I am suggesting changing the call statement for the cachef32 in config.sys be changed to run.

Index: lib/fat32_010.wis =================================================================== --- lib/fat32_010.wis (revision 197) +++ lib/fat32_010.wis (working copy) @@ -148,7 +148,7 @@

SELECT NODESELECT CONFIGSYS="SET PATH=$(3);|ADDRIGHT"

  • CONFIGSYS="call=$(3)\cachef32.exe /f /p:2 /m:50000 /b:250 /d:5000 | UNIQUE(cachef32.exe) ADDAFTER(fat32.ifs)"

+ CONFIGSYS="run=$(3)\cachef32.exe /f /p:2 /m:50000 /b:250 /d:5000 | UNIQUE(cachef32.exe) ADDAFTER(fat32.ifs)"

</PCK>

Change History (7)

comment:1 Changed 22 months ago by abwillis

Index: lib/fat32_010.wis
===================================================================
--- lib/fat32_010.wis	(revision 197)
+++ lib/fat32_010.wis	(working copy)
@@ -148,7 +148,7 @@
   SELECT
   NODESELECT
   CONFIGSYS="SET PATH=$(3);|ADDRIGHT"
-  CONFIGSYS="call=$(3)\cachef32.exe /f /p:2 /m:50000 /b:250 /d:5000 | UNIQUE(cachef32.exe) ADDAFTER(fat32.ifs)"
+  CONFIGSYS="run=$(3)\cachef32.exe /f /p:2 /m:50000 /b:250 /d:5000 | UNIQUE(cachef32.exe) ADDAFTER(fat32.ifs)"
 >
 </PCK>
 

comment:2 Changed 22 months ago by valerius

No, cachef32.exe always started as call=, because it is run synchronously. It starts daemon in the background, then terminates, that is.

and why

CONFIGSYS="SET PATH=$(3);|ADDRIGHT"

? It does not need PATH....

Last edited 22 months ago by valerius (previous) (diff)

comment:3 Changed 22 months ago by valerius

hm, it was there originally -- strange

comment:4 Changed 22 months ago by abwillis

I do not think it needs to be in path. Call is only needed in config.sys if there is something that needs to complete before something else is run. Call waits for it to complete before config.sys processes. Run allows the config.sys to continue processing while the statement finishes its thing. Unless something else in the config.sys relies on cachef32 completing, config.sys processing can continue while it completes.

comment:5 Changed 22 months ago by valerius

It, possibly, needs to have FAT32 utilities on PATH, but d:\os2 is on PATH anyway. Right, cachef32.exe needs to be completed until config.sys processing continues. It starts lazy writer, loads unicode translate table, and starts itself as a background process, asynchronously. Then it terminates and config.sys continues. This is done in a very short time, so no need to change something.

comment:6 Changed 21 months ago by valerius

The call= statement is an intended way of running cachef32.exe, so no need to change it to run=. So, I close it.

comment:7 Changed 21 months ago by valerius

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.