William Dove
December 9th 03, 12:12 PM
This is a long shot and I apologise if I have posted this
in the wrong forum.
Is there a compatibility problem with installation files
created using the Visual Basic 4.0 SetupWizard and
Windows XP (Home Edition)? When installing an exe file
using files created with Visual Basic 4.0 SetupWizard, I
have twice seen an Overflow error message once the
installation button (on the Install to chosen directory
screen) has been activated.
As soon as the Overflow error message is displayed
program installation is aborted.
These installation files work perfectly on machines
running Windows 95/98/ME/NT operating systems and we have
been using these files - and variants thereof -
successfully for over six years now. Occasionally during
installation warning messages appear connected with some
DLL or OCX controls but these have so far not presented
any problems. I managed to solve the problem in one
instance by installing Visual Basic 4.0 on the particular
Windows XP computer before using the installation files
created for our exe file, but why should this be
necessary?
It is important to me that I find out both the cause of
the Overflow error message and a more suitable way to fix
it as clearly installing Visual Basic 4.0 on every
Windows XP equipped machine is not a viable solution.
Thanks for reading this: any replies would be greatly
appreciated.
in the wrong forum.
Is there a compatibility problem with installation files
created using the Visual Basic 4.0 SetupWizard and
Windows XP (Home Edition)? When installing an exe file
using files created with Visual Basic 4.0 SetupWizard, I
have twice seen an Overflow error message once the
installation button (on the Install to chosen directory
screen) has been activated.
As soon as the Overflow error message is displayed
program installation is aborted.
These installation files work perfectly on machines
running Windows 95/98/ME/NT operating systems and we have
been using these files - and variants thereof -
successfully for over six years now. Occasionally during
installation warning messages appear connected with some
DLL or OCX controls but these have so far not presented
any problems. I managed to solve the problem in one
instance by installing Visual Basic 4.0 on the particular
Windows XP computer before using the installation files
created for our exe file, but why should this be
necessary?
It is important to me that I find out both the cause of
the Overflow error message and a more suitable way to fix
it as clearly installing Visual Basic 4.0 on every
Windows XP equipped machine is not a viable solution.
Thanks for reading this: any replies would be greatly
appreciated.