Registering 16 bit OCX

[JXBURNS]

This may be a non-starter but I have a 16 bit application that is required to run under XP. It includes several 1 bit OCX which need to be self-registered. I appreciate they are not 32bit Activex so cannot be registered using REGSVR32 (or SUF7) but without having to develop a 16 bit installer (such as in VB4), does anyone know how these can be registered?

I do have the CLSID registry keys captured using a 3rd party application and it may well be the only choice is for SUF7 to write those registry keys but there are 100's of them and not available in a .REG format for easy import.

The suppliers only answer is they may be migrating to 32 bit later this year which does me no good at all...

Thanks - John

[Adam]

Setup Factory 4.0 from back in the day supports 16 bit files. I am not sure if it will register 16 bit ocx files but you could try. Contact Support (http://support.indigorose.com) and I'll see what I can do to help.

Adam Kapilik

[JXBURNS]

Adam,

Since posting I have been trawling back through my archive disks for a copy of SUF4 as also realised that was probably the solution although could not remember whether it was 4 or 5 that dropped 16 bit support. At the moment I can find my old bought copies of SUF5 & 6 but not 4. I probably did the best thing at the time & dumped it thinking I would never have a need for it post millenium. But then I do still have my old Z80 systems running CP/M from the late 70's so perhaps its true what my son calls me (a sad old .....):lol

I'll drop you a line through support.

Thanks - John

[Adam]

I think that SUF 5.0 might support 16 bit files but you would need to verify that.

Adam

[JXBURNS]

OK I'll retrieve SUF5 from my backups and try that first although vague recollections make me think it was the first 32 bit only version.

Its so annoying when this is an upgrade of a system we have just purchased and find half is still 16 bit and other is 32 bit... Trouble is software is for loading of tankers which do not change much structurally over 25 year lifetime so there is little incentive to update the core software.

Thanks - John

[Dan Ullman]

Trouble is software is for loading of tankers which do not change much structurally over 25 year lifetime so there is little incentive to update the core software.

Thanks - John

My, that's not reassuring... (grin)

[Brett]

John,

I would suggest that you just make the necessary Registry changes using the Registry actions. You can download the registry monitor program from Sysinternals and watch what Registry keys that the OCX accesses. Or you can reverese engineer it if you know the ProgID, Typelib GUID or Class GUID.