Click to See Complete Forum and Search --> : 16 bit to 32 bit conversion


JOE V
April 7th, 1999, 03:32 PM
I have been asked to convert a piece of code that was part of a larger application from a 16 bit compatible format to a 32 bit compatible format. In doing my reading, I have discovered the wonderful and intriguing world of the Windows Registry. I have been told that in addition to producing the executable, I must also provide an install routing and an executable that will update the Windows registry. Any suggestions as to how I can go about this or any suggestions on sources of information to help me solve this problem.

Thanks in advance

Rob Wainwright
April 8th, 1999, 06:19 PM
The easiest way is to use one of the third party tools which write custom installation programs for you. I've used Install Shield in the past and it allows you to make entries into the registry. (It isn't so hot with COM components).

If you have to do it yourself with C++ code, there is a fairly large API set, all prefixed "Reg" including RegOpenKey. There are at least three helper classes submitted within CodeGURU.

There is a Microsoft book "Inside the Windows Registry" which is fairly detailed.

JOE V
April 9th, 1999, 02:33 PM
Hey Rob

Thanks for your advice. I found the Windows 95 book and am currently going through it. (Definitely not a page turner but seems very thorough :-)) Also found Installshield on web and have evaluation copy, so I will play around and see if I can get anywhere.

Thanks Again

Joe V

Alvaro
April 9th, 1999, 07:05 PM
Joe,

I recommend that you try Installer VISE from MindVision (www.mindvision.com). I found it much simpler than InstallShield (no scripts) and yet quite powerful. I should buy stock in the company, the way I keep promoting it :-).

Best of luck!


Alvaro

Vasko
April 13th, 1999, 01:26 AM
BE very careful before buying install programs lkie Install Sheild, VISE, WISE Install, etc.
MICROSOFT IS CHANGING the Install technology.
If you want your program to have "Designed For Windows 98/NT 5" logo it should use "Microsoft Installer Technology". I have not engough time to spare on it, but I suppose that in some little future most of the programs will use it. Most probably Microsoft is triying to get the installer market as well as many others - remember what they did to Netscape(Netscape Communicator), Borland(Borland C,Delphi) and IBM (OS2).
Now installers are the targets.