Hi,

I'm working on a package where an driver is installed with. It is an "generic NULL modem" driver. The installation itself is no problem but the customer now demands to assign this driver to all avaiable COM ports right after installation.

The usual way to go is:
Control Panel > Phone and Modem options > Give Location Code > Select Modem Tab > Add > Select from List > Select "Generic NULL Modem" > All ports > Next > Finish

But the customer demand this action done programaticly and silent by the setup (from MSI) mostly because of an restricted environment where most user only have default user rights.

Is there any way to archive this?

I researched for the last few hours and stumbled upon DIFxApp. But the installation of my driver is no problem, it is only the configuration / assignment to COM ports.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Ouch...

Off the top of my head, the only way to do this would be via WMI. Even then, I'm struggling to work out how you'd do that. It may require a custom DLL. Have a Google for 'VBScript COM port' or 'WMI COM port' and see what pops up.
Answered 03/12/2010 by: VBScab
Red Belt

Please log in to comment
0
I've already searched for 'VBscript comport', 'WMI com port', *vbscript serial port', 'assign driver serial port' and so on ...

Seems you can only read status and attributes of com port via WMI, eventually disable an etablished com port. But there seems no way to assign an installed modem driver to avaiable com ports.

Then I tried to capture the changes made by assigning the com ports in control panel. There I got a regfile but it doesnt change anything if I merge it to the registry after cleaning the com ports.
Answered 03/15/2010 by: Jay Am
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity