Software Deployment

You don't really specify what you mean by registering. If you're trying to register the OCX use the SelfReg table. That will register it silently. Also, try it with the /qn switch and see if that works for you. If there's something in the OCX which creates this dialog, then it's an app problem and not something you can correct with the MSI.

Thanks for your reply.

The OCX is set to self register. The issue is that some of the filetypes it wants to "handle" (for example .tif) are already registered to other applications (Microsoft Picture and Fax Viewer). Instead of just overwriting the exisiting values, I'm being prompted by a message box asking if this is what I want to do.

I'll try the qn switch but I doubt that it will help ...

I need a fix for this, even if its a registry hack ... my last resort option will be to delete the offending registry keys, but I'd just rather silently overwrite

Regards

ORIGINAL: kymdyer

Thanks for your reply.

The OCX is set to self register. The issue is that some of the filetypes it wants to "handle" (for example .tif) are already registered to other applications (Microsoft Picture and Fax Viewer). Instead of just overwriting the exisiting values, I'm being prompted by a message box asking if this is what I want to do.

I'll try the qn switch but I doubt that it will help ...

I need a fix for this, even if its a registry hack ... my last resort option will be to delete the offending registry keys, but I'd just rather silently overwrite

Regards


Kym, if it's something that can be suppressed in the MSI then /qn should do it. That means absolutely no user inteface. /qb- means minimal user interface. If you use this in conjunction with logging /l*v "path to log file" then the log file should show you whether it was successful in registering it.

If it's a badly behaved OCX see what other options are available to register it. Regsvr32.exe is used to manually register files, /s is the silent switch for that OS command.