Visual Basic - Backward compatibility with Win98

Author

Backward compatibility with Win98

Tom_OM

2005-08-28, 9:55 pm

I compiled a VB project and made a setup with my setup tool, but the
program doesn't run right under Windows 98. I get the following
error:

"The MSVCRT.dll file linked to missing export NTDLL.dll-
RtlGetNtVersionNumbers"

I searched this news group's archives and learned that I need to
compile my project and create its setup file under Windows 98. Turns
out the MSVCRT.dl file from XP isn't backward compatible with the one
with Win 98, if it existed then. (Links to what I read about this
issue are at the end of this post if you're interested.) I have an
old Win 98 machine, so the compiling work under that OS is no problem.

I still have some questions that were not answered by the archive
posts.

1. My Win 98 machine is an old HP Pentium III that came with a restore
disk rather than a Microsoft Win 98 install disk. Once I've let the
restore disk run and thus have Win 98 up and running, do I need to go
online and update Win 98 with Microsoft's latest Win 98 patches? Or
does it really matter? I would need to install my Internet software
on the old machine to update it, but I'll skip this step if it doesn't
really matter.

2. Should I create both Win 98/ME and Win XP/2K versions of the
program? I'm wondering if my version compiled and set up under XP
will run better under XP (and Win 2K) than the one I'll do for Win
98. (The XP compiled one ran fine under Win 2K.)

I appreciate any insight offered. Thank you.

Links to the archive posts:
http://groups.google.com/group/micr...9c09cc1d6634426

http://groups.google.com/group/micr...3ef32083b8cd252

Kevin Provance

2005-08-29, 3:55 am

In a nutshell, installing OLE runtimes from XP on (9x machines will blow up,
as you've seen). :(

It's not really necessary to create two setup files. The standard advice
given to is to compile your EXE and install on the oldest OS you intend to
support and use version checking in your setup to check for newer files
before installing.

For me, it's a real PITA to do everything on a Win 98 system, so when
creating my setups, I use the files in the REDIST folder in the VB folder
which versionally speaking will work on 95 and up. The version checking
will prevent overwriting of the newer files on 2000/XP systems and then
everything should work more smoothly.

I know this is kind of vague...if you want something more in depth, let me
know and I'll help where I can. :)

- Kev

"Tom_OM" <dontspamme@nojunkmail.com> wrote in message
news:csr4h1ptc10p4bh53d3ai059u6k562d4ee@
4ax.com...
>I compiled a VB project and made a setup with my setup tool, but the
> program doesn't run right under Windows 98. I get the following
> error:
>
> "The MSVCRT.dll file linked to missing export NTDLL.dll-
> RtlGetNtVersionNumbers"
>
> I searched this news group's archives and learned that I need to
> compile my project and create its setup file under Windows 98. Turns
> out the MSVCRT.dl file from XP isn't backward compatible with the one
> with Win 98, if it existed then. (Links to what I read about this
> issue are at the end of this post if you're interested.) I have an
> old Win 98 machine, so the compiling work under that OS is no problem.
>
> I still have some questions that were not answered by the archive
> posts.
>
> 1. My Win 98 machine is an old HP Pentium III that came with a restore
> disk rather than a Microsoft Win 98 install disk. Once I've let the
> restore disk run and thus have Win 98 up and running, do I need to go
> online and update Win 98 with Microsoft's latest Win 98 patches? Or
> does it really matter? I would need to install my Internet software
> on the old machine to update it, but I'll skip this step if it doesn't
> really matter.
>
> 2. Should I create both Win 98/ME and Win XP/2K versions of the
> program? I'm wondering if my version compiled and set up under XP
> will run better under XP (and Win 2K) than the one I'll do for Win
> 98. (The XP compiled one ran fine under Win 2K.)
>
> I appreciate any insight offered. Thank you.
>
>
> Links to the archive posts:
> http://groups.google.com/group/micr...9c09cc1d6634426
>
> http://groups.google.com/group/micr...3ef32083b8cd252

Ted

2005-08-29, 3:55 am

>"The MSVCRT.dll file linked to missing export NTDLL.dll-
>RtlGetNtVersionNumbers"

Lucky it just gave an error, normally it crashes Win 98.

You need either compile in Win 98, or purchase an installation
software such as Setup Factory.
With it you can include both MSVCRT.dll versions in the setup
and assign which OS it goes to.
Same with Comcat.dll, certain versions are not compatible with
Win NT.
Compiling in Win 98 and older VB run files, insures you are not
over writing these crucial files unless they are very old.

"Tom_OM" <dontspamme@nojunkmail.com> wrote in message
news:csr4h1ptc10p4bh53d3ai059u6k562d4ee@
4ax.com...
>I compiled a VB project and made a setup with my setup tool, but the
> program doesn't run right under Windows 98. I get the following
> error:
>
> "The MSVCRT.dll file linked to missing export NTDLL.dll-
> RtlGetNtVersionNumbers"
>
> I searched this news group's archives and learned that I need to
> compile my project and create its setup file under Windows 98. Turns
> out the MSVCRT.dl file from XP isn't backward compatible with the one
> with Win 98, if it existed then. (Links to what I read about this
> issue are at the end of this post if you're interested.) I have an
> old Win 98 machine, so the compiling work under that OS is no problem.
>
> I still have some questions that were not answered by the archive
> posts.
>
> 1. My Win 98 machine is an old HP Pentium III that came with a restore
> disk rather than a Microsoft Win 98 install disk. Once I've let the
> restore disk run and thus have Win 98 up and running, do I need to go
> online and update Win 98 with Microsoft's latest Win 98 patches? Or
> does it really matter? I would need to install my Internet software
> on the old machine to update it, but I'll skip this step if it doesn't
> really matter.
>
> 2. Should I create both Win 98/ME and Win XP/2K versions of the
> program? I'm wondering if my version compiled and set up under XP
> will run better under XP (and Win 2K) than the one I'll do for Win
> 98. (The XP compiled one ran fine under Win 2K.)
>
> I appreciate any insight offered. Thank you.
>
>
> Links to the archive posts:
> http://groups.google.com/group/micr...9c09cc1d6634426
>
> http://groups.google.com/group/micr...3ef32083b8cd252

Tom_OM

2005-08-29, 6:55 pm

On Sun, 28 Aug 2005 21:18:47 -0700, "Ted" <2000@xxxmsn.com> wrote:

>
>Lucky it just gave an error, normally it crashes Win 98.
>
>You need either compile in Win 98, or purchase an installation
>software such as Setup Factory.
>With it you can include both MSVCRT.dll versions in the setup
>and assign which OS it goes to.
>Same with Comcat.dll, certain versions are not compatible with
>Win NT.
>Compiling in Win 98 and older VB run files, insures you are not
>over writing these crucial files unless they are very old.

That's perfect. I have the Setup Factory 6 and will do it that way.

Many thanks to everyone for the help offered.

Sponsored Links