Visual Basic - Setup program run on NT?

Author

Setup program run on NT?

Damon

2004-05-27, 10:30 am

Hi,

I have written my VB app on my Windows XP machine, I have also created a
setup program on my XP machine, however when running the setup on a Windows
NT machine it mentions that there are some system files which are out of
date on the system and do I want the system to update these files. When I
say yes it says that I must re-boot the machine but when I do I get a blue
screen with a memory dump error message. Has anyone come across this
before? What system files could be out of date? and what are they linked
to. I thought it may have been MDAC so I installed the same version of MDAC
onto the NT machine but with the same result. Would appreciate the help on
this one.

Thanks

Damon

Bob O`Bob

2004-05-27, 3:30 pm

Damon wrote:

> I have written my VB app on my Windows XP machine, I have also created a
> setup program on my XP machine, however when running the setup on a Windows
> NT machine it mentions that there are some system files which are out of
> date on the system and do I want the system to update these files. When I
> say yes it says that I must re-boot the machine but when I do I get a blue
> screen with a memory dump error message. Has anyone come across this
> before? What system files could be out of date? and what are they linked
> to. I thought it may have been MDAC so I installed the same version of MDAC
> onto the NT machine but with the same result. Would appreciate the help on
> this one.

Those would be system files, on the NT machine, just as it warned you.

The files you brought, it should be obvious, came from an XP machine, and
therefore installing them on NT may actually destabilize the whole system.

There is a concept known as "backward compatibility" which is fairly well
respected in Windows. When new platforms are created, there are some allowances
made for the ways in which older applications were written. Programs created
on NT should run on XP. But it's not possible to insure "forward compatibility"
without having advance knowledge of the future.

All in all, you've quite possibly screwed up the NT system itself,
not just the program you attempted to install.

If you want to create programs which work on multiple platforms, then you
should do your production compiles, and build all your installation sets,
on the OLDEST of the platforms you intend to support. You can safely
package older system libraries in your installer, and when installing on
a newer platform it won't bother to copy those. Going the other way fails
too often to be worth the effort.

Bob

Ralph

2004-05-28, 2:30 pm

"Damon" <damon@nospam.co.uk> wrote in message
news:9Emtc.55$0e2.14@newsfe4-gui...
> Hi,
>
> I have written my VB app on my Windows XP machine, I have also created a
> setup program on my XP machine, however when running the setup on a
Windows
> NT machine it mentions that there are some system files which are out of
> date on the system and do I want the system to update these files. When I
> say yes it says that I must re-boot the machine but when I do I get a blue
> screen with a memory dump error message. Has anyone come across this
> before? What system files could be out of date? and what are they linked
> to. I thought it may have been MDAC so I installed the same version of
MDAC
> onto the NT machine but with the same result. Would appreciate the help
on
> this one.
>
> Thanks
>
> Damon
>

To amplify on Bob's sage advice - It is very very seldom that you need to
include "system" files with your setup. While such files often show up as a
"dependancy", the application will usually work with the comparable or
equivalent "system files" of the target platform.

Simply remove any "system files" from your setup.

In those cases where you are using some advance or new feature of the newer
platform - you are likely SOL.

-ralph

Sponsored Links