How to add command line arguments to command line arguments in Windows shortcut?

Question

I know I can add a command line argument/option to a shortcut this way; for example:

"C:\Program Files\Internet Explorer\iexplore.exe" www.a.com

So IE will connect to a.com when it starts up. What I would like to do is to get IE connecting to a.com when I call it through another program like the following:

C:\Windows\SysWOW64\ForceBindIP.exe 192.168.1.151 "C:\Program Files\Internet Explorer\iexplore.exe" www.a.com

This does not work. IE starts up but doesn't go to a.com. It seems like the argument is either ignored or is understood as an argument of ForceBindIP instead (I'm not sure).

What I am trying to do is to create 2 IE shortcuts such each of them binds one IE window to one NIC and one particular website. So adding the www.a.com etc in its startup list won't help. OS is Windows 8.

Apologize if this has been asked and answered before. Please suggest keywords for searching if that's the case.

score 2 · Accepted Answer · answered Dec 17 '12 at 22:34

Create a batch file (called, say, foo.bat) that says

"C:\Program Files\Internet Explorer\iexplore.exe" www.a.com

and then change the shortcut to say

C:\Windows\SysWOW64\ForceBindIP.exe 192.168.1.151 foo.bat

This lets you work within ForceBindIP’s apparent restriction of handling only

ForceBindIP.exe IP address full path to app

on its command line (without accepting any parameters for the app), while also providing parameter(s) for Internet Explorer. (You’ll note that their web page shows only the above usage, although they don’t spell out the restriction.)

score 1 · Answer 2 · answered Aug 21 '13 at 20:10

1

For some reason ForceBindIP is ignoring first parameter, so do it like:

C:\Windows\SysWOW64\ForceBindIP.exe 192.168.1.151 "C:\Program Files\Internet Explorer\iexplore.exe" foo www.a.com

answered Aug 21 '13 at 20:10

user247422

11

score -1 · Answer 3 · edited Jul 28 '14 at 19:10

ForceBindIp takes 3 arguments for itself and searches them for IP/Interface, the program to start and the "-i" switch, which delays the injection of forcebind until the message queue is loaded (whatever this means).

So even when the 2 mandatory arguments ip and program are there but the third, optional -i switch is missing, it is discarding the third parameter (since it is none of the 3 known).

From the fourth parameter on, it parses every argument to the program. So something like ForceBindIp ÌP FULLPATH garbage ARGUMENT1 ARGUMENT2 works.

How to add command line arguments to command line arguments in Windows shortcut?

3 Answers3