hiderun /w RamDisk.cmd B: NTFS 4 64 50 % ImDisk /c
hiderun.exe /w cmd /c md "B:\Documents and Settings\Default User\Local Settings\Temp"
hiderun /w cmd.exe /C hiderunEX /w ModelRam -oB: -y
hiderun /w reg import cplfix.reg
hiderun.exe /w BroadcastEnvChange.exe /broadcast
Also, Besides it is distributed with different namings (hiderunEx_x64.exe , hiderunEx_x86.exe) Guru wants us to use same file name of his utilities on PE (
hiderun.exe, BroadcastEnvChange.exe ....) on different architectures.
ps: @psc: maybe better to put exe files inside folders in the zip packages (hiderunEx.zip\x86\hiderun.exe , hiderunEx.zip\x64\hiderun.exe) or maybe different zip packages in order not to cause misusage.
Edit: fixed, after sometime on a pm traffic with guru, I notice guru wants hiredun.exe on target (PE) not hiderunEx.
May i ask x64 versions of your utilities. (
, SetPageFile, RunScanner, HwPnp, ......)
I prefer having same name for executable (like you did in RamStatus.7z - ramstatus.exe), only minor cosmetic, can we have x86 and x64 folder name usage to make script writing easier. (ex: RamStatus.7z\x86\ramstatus.exe , RamStatus.7z\x64\ramstatus.exe)
after JonF's following post. I just copy/paste quickly to give examples without checking