Windows 7 x86 Error 1904

First of all, can you check if the DLL and OCX files you are working with are 32 bit?
Windows 7 does not support 16 bit at all, so if these resources are 16 bit, you may need to start experimenting with the Windows XP compatibility add-on to Windows 7.

I am not sure. I doubt it. Can you guide me to a tool for determine if a ocx is 16 bit or not?

Thanks :)

I would recommend searching the internet (eg Google) on the filenames of your various OCX files - if you can identify the author of the OCX you can no doubt find out whether the OCX is 16 bit.
I'm not a programmer, but I would imagine there are ways of checking what type of DLL or OCX you are working with.

Thanks for the reply :)

I believe my ocx'es are 32bit, since they are ActiveX, thus being 32bit. right?

So, what now? How to make my MSI work? :)

...then perhaps the DLL and OCX files causing the kernel error are incompatible with Windows 7.

Since you are referring to an "ageing" VB6 environment, have you looked for any "modern" equivalents of the OCX's you are using?
Clearly if you are just copying the OCX manually to a folder on the Windows 7 machine, and trying to register it with REGSVR32.exe, then a Kernel error signifies an issue with the OCX, and cannot be a problem with the installer, as the installer is not involved when you do anything manually.

I tried googling on RichViewEditX.ocx, and only got this thread as a result. Is this the correct name for the OCX, and if so, where did it come from?  It's odd that there are no other hits in google.

Thanks for the reply :)

The ActiveX is an specially brewed component based on the TRichView component, www.trichview.com/features/. We had to make a VB6 component of TRichView, because it shipped only in Delphi or C++ Builder.

No wonder Google gave no hits :)

We are currently working on an upgrade. But we also have to others who produce the same error messages. It may be that the OCX's are too old. I did not check dependency on all three of the ocx's, only one of them. But it produced the same error message, anyway.

When I register csXImage (which was upgraded to the newest ocx) it failed. I also spoke to Chestysoft (the makers of csXImage) and they told me they got it registered just fine. I obviously used cmd elevated as administrator.

Does anybody have a clue about this problem? The component is developed using Delphi, so is the two other which fails during registering. I believe there is a connection here, but not sure how to deal with the problem.

Regards,
Greendaale

Since the problem appears when you attempt a manual registration, the issue would appear to be with your Windows 7 RC installation.
The RTM is now available from MSDN and Technet, so perhaps you should get hold of the latest release and test on that instead. If it still gives problems then you need to go back to Chestysoft.
Remember to test on a bare metal install before any apps are added, and then test again once you have installed any other apps such as antivirus programs.

I have seen some similar problems with registering files. The files registered fine on the developer machines, because they contain everything necessary. Use Dependency Walker to check if there are some missing files that makes it impossible to register the file on your machine.

It would be helpful to know which manufacturer(s) machines you experienced this on, as it may impact the installs of other users too.