Shortcut for Windows Fax and Scan

[mvuille]

Trying to add a shortcut for Windows Fax and Scan to my dock (in Windows 8.1)

The shortcut works fine from the Desktop, but if I add it to the dock, it doesn't
do anything. Tried both Copy Shortcut Properties and Link to Shortcut, to no
avail.

Any thoughts? I've likely overlooked something obvious.

MV

[mouser]

Link to shortcut should always work.. Could you attach a screenshot of the node configured in that way?

[mvuille]

Attached



MV

[mouser]

can't really see anything wrong with that.
when you launch that button does anything happen at all?

can anyone else try this?

just for fun, maybe you could try making a copy of the shortcut on your desktop that has no spaces in the filename, and try creating a link to that one from LBC?

[mvuille]

That's right, nothing at all happens.

Tried removing the blanks in the name of the shortcut,
made no difference.

It's very strange!
MV

[mouser]

Ok i'm going to have to try to reproduce this on a virtual machine.  If anyone else can report their experiences with launching this and other control panel shortcuts let me know.

[mvuille]

Since you mention Control Panel shortcut, and just so there's no
misunderstanding, the non-working shortcut points to "%windir%\system32\WFS.exe".

I also tried manually creating a command node that points directly
at the executable in "C:\Windows\system32\WFS.exe" and that
didn't work either.

MV

[mouser]

well now thats plain weird.
let me ask, does that file actually exist (WFS)?

i wonder if this is one of those cases where windows is doing some trickery with virtual directory shadowing type stuff, pretending the file is one place when it's not..  or if it's some kind of permission system..

[mvuille]

Explorer shows a file named WFS.exe in C:\Windows\System32, but that
doesn't eliminate the possibility of some special Windows trickery.

MV

[Ath]

Explorer shows a file named WFS.exe in C:\Windows\System32, but that
doesn't eliminate the possibility of some special Windows trickery.

MV

-mvuille (April 04, 2014, 05:37 AM)

But an executable by that name is not in C:\Windows\SysWOW64, where the 32 bit LBC will try to find it...

[Ath]

This link might be useful: https://community.or...ead/2465844?tstart=0 (Starting a 64 bit (-only) executable from a 32 bit process)

[mvuille]

Thank you Ath!

Changed the command node target to "C:\Windows\Sysnative\WFS.exe"
and it works now.

MV

[Vurbal]

well now thats plain weird.
let me ask, does that file actually exist (WFS)?

i wonder if this is one of those cases where windows is doing some trickery with virtual directory shadowing type stuff, pretending the file is one place when it's not..  or if it's some kind of permission system..

-mouser (April 03, 2014, 11:04 PM)

Looks like it's exactly the opposite of that. LBC can't even see wfc.exe because it doesn't redirect to a 32-bit program like most of the programs in System32.

I'll have to remember that trick. Thanks Ath!