On recent advice from this forum I've tried installing IQFeed 6.2 and I'm a little perplexed at what gets installed.
I get a link on the desktop to 'IQFeed Applications' - which links to a folder with shortcuts to the applications.
However there is no shortcut to the connection manager.

When I try to run the connection manager application directly the connect button is disabled.
Please advise how one is supposed to run the connection manager in 6.2?

What are you trying to do exactly? Typically, if you launch the iqfeed app first, the iqconnect manager will open for you to login as needed.

---

Sincerely,
Gary Stephen
DTN IQFeed Implementation Support Specialist

I used to start the connection manager and that was that. I'm doing auto-trading so I don't have any of the apps open. Which one do you mean by "the app"?

Any of the IQFeed client apps: Time & Sales, Snap Quote, Option Chains, etc.

---

Sincerely,
Gary Stephen
DTN IQFeed Implementation Support Specialist

People doing auto-trading might not want other applications running just for the sake of keeping the connection open, this might be something worth considering.

Anyway - I've lengthened the timeout in the registry and created and modified shortcut...

There seems to be some confusion here and I just want to make sure everything is clear (and for future readers).
We have always preferred that your software launch the feed directly instead of using a launching app.

Here is the documentation page for how to launch the feed directly from your app using your registered productID: https://www.iqfeed.net/dev/api/docs//InitializingTheFeed.cfm

In the long distant past, we required your app load a DLL which then launched the feed with a function call but it was still directly from the app connecting to the feed.

In this particular case, I checked the server logs and it appears that your software has been doing this incorrectly for a very long time. I believe the confusion comes from our, now designated as End Of Life, DDE server (iqlink). The DDE server used to have a launching app (iqlinklauncher) because it was designed to be used with Excel and Excel did not reliably launch the DDE server when invoked. The launching app was removed when we designated the DDE server as EOL (and because it was confusing to new customers).

If by "doing it incorrectly" you mean using the short cut installed by the 6.1 installer, then I guess I have.
Anyway - I understand the intended methodology now.