I have a potential client who sells a VB3 app, for which he lost the source code. It does not run on Windows 7 64-bit because the app is 16-bit. Only 32- and 64-bit programs will run on 64-bit Windows. (Well the 16-bit app would run in XP mode, but the end users will not accept that)
In order to accomplish this I would have to:
- Find a copy of Visual 3.0 (full) (perhaps from http://www.emsps.com/oldtools/msvb.htm#vb3)
- Find a USB floppy drive so I can install it
- Use the so-called Visual Basic v3.0 Decompiler - from DoDi from http://www.woodmann.com/crackz/Tools.htm to decompile it, with no guarantee of success, with the result being code that would be very difficult to modify in any way
- Find a copy of Visual Basic 4.0 (full or upgrade) (perhaps from http://www.emsps.com/oldtools/msvb.htm#vb4)
- Upgrade the (mostly non-understandable) code
- Compile it in 32-bit mode
- Make an installer
- Profit!! :)
I see this as a project with significant risk of failure, with step 3 being especially high risk. What do you think my chances of success? Should I turn it down or go for it? If it's a go, what precautions should I take?
EDIT: GrandmasterB (below) brings up a huge "monkey wrench". Indeed the app uses several .VBX's. Although this doesn't make the project impossible per se... perhaps I would be able to track down 32-bit upgraded versions of these extensions (.OCX's?)... but this issue, combined with the fact that I would have to get it working with decompiled source code just seems like too much of an uphill battle.