avatar image

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

Login with username, password and session length
  • Wednesday October 21, 2020, 5:33 pm
  • 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 - chok [ switch to compact view ]

Pages: [1]
Well, bummer.  As long as I find the file and launch it and don't use any shortcuts that have system32 in them, I'll be OK.  Although it may be a lot of work, I still think a 64-bit FARR would solve all of this.

I think lordmuzer should get a gold star on his chart for today!  Wow!  I just added %windir%\sysnative to my search folders and unchecked %windir%\system32 and I can launch all these neat 64-bit programs instead of the 32-bit versions.  I think this is just a good as a 64-bit FARR.  Thanks lordmuzer.

I cannot add an alias, because the 32-bit FARR cannot find the 64-bit cmd.exe.  When it looks at system32, it is actually seeing the sysWOW64 directory instead.

I can copy the 64-bit cmd.exe to another directory and FARR can find it and run it just fine.  But there are quite a few programs that are missing.  Defrag, dnscmd, mrt, msconfig, telnet, and tftp are a few that I have noticed.  Also, most of these have some language-specific files in %windir%\system32\en-US (on my machine), which have to be copied to a corresponding subdirectory of wherever the executable is.

There is also just a philosophical issue of running the 32-bit versions of everything instead of the new 64-bit versions.  Practically, though, it probably makes no difference.

It is much easier just to work around this issue by launching cmd with the Windows key.

I do think that sooner or later you will be wanting to start offering a 64-bit build.  It will probably be a long time before 32-bit support is phased out, but 16-bit programs stopped working with the first 64-bit Windows (

Find And Run Robot / Request for 64-bit build of FARR
« on: November 18, 2010, 08:56 AM »
I know some discussion about launching 64-bit programs has taken place.  I don't see any discussion about finding and launching 64-bit programs in the system32 directory.  As you know, a 32-bit program sees the sysWOW64 directory as the system32 directory.  I first noticed this problem when launching cmd.exe from FARR.  It finds the 32-bit cmd.exe in the sysWOW64 directory and runs it.  Then when I type something like nbtstat in that command prompt window, it cannot find it, because there is not a 32-bit nbtstat.exe in the sysWOW64 directory, only a 64-bit one in the real system32 directory.  I think what we need is a 64-bit build of FARR.

Pages: [1]