I may have missed it but I can't find a way to launch Microsoft Word using command line switches.

Without it, Word launches fine but as soon as I add something like /n, e.g. "C:\Program Files (x86)\Microsoft Office\Office14\winword.exe" /n I get a message that "Windows cannot find....."

Suggestions?

Thanks

Right click your Word icon and select Dock Entry Properties.

Entry Filename should only contain the path to winword.exe like this:
Filename: C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXE

Entry Arguments should be used for the command line switches like this:
Arguments: /n

That's what was originally there. It doesn't work which is when I tried adding the quotes.

As soon as I add a switch Nexus can't find the executable

Just to make sure you understand it right.

Right click your Word icon and select Dock Properties.

If you add the command line switch (/n) as in the following picture it will not work (you get the problem you described).
http://i39.tinypic.com/1zw0oi1.jpg

If you add the command line switch (/n) as in the following picture it will work (at least on my system).
http://i44.tinypic.com/zj6pfp.jpg

Thanks Henk.

I must need remedial reading classes as I had the arguments in with the command line and never realized it until I saw the screen shots.

Everything is working as expected. I appreciate the guidance.

I have a similar problem.

Program gets started, but command line switch (parameter "/n") is not executed.

It used to work until yesterday, didn't change a thing but now it has stopped working.





What could be wrong here?

I *think* you might just need the 'n', without the slash...

Thanks but nope, doesn't work like you suggest. Acrobat thinks the "n" is a document name then.

Actually, I just tried it with Acrobat Reader and the '/n' argument works as intended. Without it, when an instance of Reader is running, isn't doing anything; with it, it launches a new instance. So, I conclude that the argument is being passed on successfully.
Seeing that you're actually using Acrobat (the big application) and not Acrobat Reader, I must ask... are you sure that Acrobat actually supports that '/n' switch?

Yes, and it has always worked. It still works like that (opens a new instance) when I enter


in the Windows "Run" box.

But not anymore in Nexus

That's weird... what changed, then? Did it just stop working all of a sudden?
Did you try to create a new icon? Don't know why that would work, but... can't really think of a reason why the other one doesn't.

I met two occasions in which clicking the icon on the Nexus dock doesn't work:

1) The application is already running. Have a look in task manager and end the process or simply reboot and try again, to see if works then.
2) Right click the icon on the Nexus dock and select Run As Administrator. This sometimes works while, although I am already logged in as admin, normal clicking the icon on the Nexus dock does not work. Also checking the 'Als Administrator ausfuhren' box did not help in my case.

I do not have a solution to this (other than kill the running process or Run As Administrator), but if one of those two ways are also applicable in your case this could be regarded as a 'bug' in either Winstep or the app involved.

OK, it took me only a week to figure out that Nexus option setting No. 32,768/crypt/$EAF3$ actually was responsible for this behavior.

Ok, I changed the text so it says 'Do not launch multiple sessions of the same application'.

Couple of things though: that option is disabled by default, so you must have turned it on at some point. Second, the fact that Nexus has many options is what makes so powerful and flexible in comparison to other dock programs.

Since not everybody wants the same behavior, those options must exist *somewhere*. Of course, I do try to 'bury' the least used options in secondary dialogs.