Name: akai11 Date: October 30, 2004 at 12:07:25 Pacific Subject: NT 3.51 version after shell update OS: NT3.51?? CPU/Ram: P133
Comment:
I'm a hobbyist w/ NT 3.51 + Service Pack 5 installed on an older computer. Just installed the Shell Technology update from the 3.51 Resource Kit (couldn't find a clear answer to this question in the book). When I go to the System applet in Control Panel, it, as usual, lists all the familiar environmental values (OS is NT 3.51, %windir% is, etc.) However, when the system boots, the blue screen states that it's NT 4.0 w/ Service Pack 5. So which is it? With the shell installed, can this system be treated as an NT 4.0 system and can all of the relevant 4.0 SP's be installed? Just curious. Sorry is this is a stupid question.
the boot loader version doesn't mean its the running OS version. In other words I can use the XP loader to start Windows 2000[newer can mount older but not visa versa]
No you can't load the service packs for NT4 into 3.51. They shouldn't let you anyway with a message like wrong OS version.
But an interesting question would be does this mean that more NT 4.0 programs can be installed because perhaps the the installer is fooled into thinking it is NT 4.0 instead of NT 3.51? Not only is the boot loader upgraded but the NT 4 interface is too which is something that many NT programs check for.
as a matter of fact, prior to installing the Shell Update, I tried installing ArcView GIS 3.2a & was returned the error message that "this program cannot be run on an NT3.51 operating system." Or words to that effect. However, after the shell update, I was able to install & use the software without a hitch. Interesting.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE