avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Wednesday June 16, 2021, 7:06 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - lordmuzer [ switch to compact view ]

Pages: [1]
and the last problem with "Program Files"|"Program Files (x86)" folders:

by default windows 7 x64 has 2 shortcut for Internet Explorer:
"Internet Explorer.lnk" = "C:\Program Files (x86)\Internet Explorer\iexplore.exe"
"Internet Explorer (64-bit).lnk" = "C:\Program Files\Internet Explorer\iexplore.exe"

but FARR always execute "C:\Program Files (x86)\Internet Explorer\iexplore.exe"

but another problem: on x64 OS FARR cannot start any .lnk (from %MYSTARTMENU%|%COMMONSTARTMENU%)
for build-in/system Windows application from "%windir%\System32\" that doesnt have corresponding x32 analog in "%windir%\SysWOW64\"

on windows 7 x64 you cannot execute:
"Sound Recorder", "Snipping Tool" and other.

maybe FARR, when resolve *.lnk target to %windir%\system32\* can try to find it in %windir%\sysnative too ?

yes, i can confirm.
i type in FARR "C:\Windows\System32\regedit.exe", but instead "C:\Windows\SysWOW64\regedit.exe"  will start.
my os is windows 7 x64

Microsoft say at http://msdn.microsof...384187(v=VS.85).aspx:

Applications can control the WOW64 file system redirector using the Wow64DisableWow64FsRedirection, Wow64EnableWow64FsRedirection, and Wow64RevertWow64FsRedirection functions. Disabling file system redirection affects all file operations performed by the calling thread, so it should be disabled only when necessary for a single CreateFile call and re-enabled again immediately after the function returns. Disabling file system redirection for longer periods can prevent 32-bit applications from loading system DLLs, causing the applications to fail.

and as temporary fix:

32-bit applications can access the native system directory by substituting %windir%\Sysnative for %windir%\System32. WOW64 recognizes Sysnative as a special alias used to indicate that the file system should not redirect the access. This mechanism is flexible and easy to use, therefore, it is the recommended mechanism to bypass file system redirection. Note that 64-bit applications cannot use the Sysnative alias as it is a virtual directory not a real one.


I have 2 small problems
Here is a screenshot:

1. FARR get icon direct from .exe file, not .lnk. But if .exe has no icon and .lnk has it, can FARR take it from .lnk? on screenshot "windows update.lnk" has icon, but FARR does not show it

2. After first 9 item in history list with predicate with "* - ", other items has strange space before.

and last, i confirm that
3. When a list of results is displayed, right-click an item and click Properties. Result: nothing happens. No error, no message, just nothing  The Shell Context Menu command works, though.
reproduce in windows 7 x64

sorry for my bad english, its not my native lang


Pages: [1]