Doom9's Forum - View Single Post - CallCmd v1.04 - x86 & x64 -Execute command

StainlessS · 21st October 2012, 17:56

CallCmd waits for the process to both start and end (as Call did), I guess I could add an arg to return immediately,
It might well be the CMD.Exe that is slow to start though, I know it checks eg AutoRun type entries
in the registry and probably an amount of other startup stuff. (CMD /D disables AutoRun).
I'll add the arg soon.

EDIT: RAMDISK dont seem to be beneficial, guess that the ScriptClip single tif version is hitting the disk cache
all of the time and therefore gives better performance.

21st October 2012, 17:56	#4 \| Link
StainlessS HeartlessS Usurer Join Date: Dec 2009 Location: Over the rainbow Posts: 10,980	CallCmd waits for the process to both start and end (as Call did), I guess I could add an arg to return immediately, It might well be the CMD.Exe that is slow to start though, I know it checks eg AutoRun type entries in the registry and probably an amount of other startup stuff. (CMD /D disables AutoRun). I'll add the arg soon. EDIT: RAMDISK dont seem to be beneficial, guess that the ScriptClip single tif version is hitting the disk cache all of the time and therefore gives better performance. __________________ I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? Last edited by StainlessS; 21st October 2012 at 17:59.