Safe to install some DirectX and NET 1.1 files??? 2

[Bocaire]

I downloaded a file from NASA to install their "World_Wind software "World_Wind_1.3.5_Full.exe". This is software to handle their high-resolution maps which have been promoted as being much better than Google Earth.

When I went to install it, several messages came up stating that they have to install "NET 1.1" and "Managed DirectX October 2005 update". So I temporarily cancelled the install

I did a quick search on Google, and it appears that both these items are MS items that may well be needed to run the NASA 3-D hi-res maps that they have available.

But before I allow this "stuff" to be installed, I want to make sure that I'm not compromising/messing up anything on my system.

I'm running a high end system with Windows XP Pro, with all the updates that MS has been sending out. My CPU is an AMD 64 4400 X2 Athlon chip. I have about 2 Terabytes of HD space, 2 GB of RAM, and an EVGA 7800GT 256 MB video card.

I seem to recall reading in the past that some DirectX stuff caused someone some problems. Am I running any possible risks in letting this NASA software install what it wants, as noted above?

Thanks for any help or suggestions -

Bocaire

 

[Rick998]

I can't think of any problems installing these two items. As you have discovered, they are both from MS. I would suggest you do a manual 'Windows Update' afterwards so they are both updated, if necessary, with the latest patches.

Hope this helps...

 

[Bocaire]

Hi Rick,

Thanks for the info.

The NASA World_Wind software displayed quite a 3D type display during the opening stages of the install. I'm using a DELL 2407 widescreen monitor, and if the follow-on hi res images fall into the same display category, that should be one great software display from NASA.

Bocaire

 

[eyec]

if you want really hi-res graphics check out

http://www.interfacelift.com.

your monitor should do them justice.

p.s. before you do any updates set a restore point in case NASA is running and requires an older version of Direct X or specifically NET 1.1

 

[Bocaire]

Thanks for the info. And yes, I always set a restore point prior to activities like this. It is cheap insurance.

Bocaire

 

[bcastner]

.NET and DirectX are inclusive and cumulative.

You should be fine in terms of function by just using the latest version of each.

Software that does a version check, however, may not understand / be satisfied by this approach.

The Microsoft Installer software can handle this issue. Download and install all the versions. This will make certain you have the registry entries that your software installer is checking.

My preference would be to do this oldest-to-newest versions as downloads and installs, although it should not matter.



____________________________
Users Helping Users

 

[Bocaire]

bcastner,

I've not yet installed the NASA software, which does offer to install the necessary DirectX and NET 1.1 files.

Presumably they will be installing the ones necessary to work with their main software package, but possibly not the latest ones that MS offers.

I'm presently using MS's auto updates for XP Pro. Whenever I attempt to look over the update files available, it's not straightforward to figure out which to download and run. So, I've stayed with letting MS do things automatically.

Assuming that what the NASA software installs is not the latest update, will my auto update arrangement for XP pick up what I've added, and automatically update those files, at an appropriate time in the near future?

If not, what would be the best route for me to call for an update manually immediately?

Bocaire

 

[bcastner]

The issue fundamentally is what the software installer looks for, rather than how technicly up-to-date your workstation may be.

It is not considered "fair" for a software installer to poll the registry for a specific version of NET or DIREXTX; but rather the poll should be the hightest version now installed.

This is just sloppy programming. The disk space required by installing subsequent issue releases of DirectX and .NET are not onerous, and once installed (they will install under Program Files to seperate directories) you could just delete the folders if you wish, as the important registry entries would remain.

But I suspect an application that is weak on identifying base sofvtware resources such as .NET might in fact make direct calls to the folder for the software. Again, the storage requirements are quite modest.

Give it what it wants. It is often a better choice than yelling at the darned computer.

Best.
Bill Castner


____________________________
Users Helping Users

 

[Bocaire]

The actual operation went well. Accepting the NASA software's invitiation for NET 1.1 brought me to the appropriate MS page where the available files were listed. So I downloaded NET 1.1, and also SP1 for NET 1.1. I ran both, and it was installed and updated.

Then I restarted the NASA software, and I was not questioned again re NET 1.1. I was queried about DirectX later on, and when I accepted that invitation, it appeared that MS took over again, and retreived the necessary files (apparently from my hard drive).

The installaton went well, and everything was up and running very shortly.

Thanks again for your help.

Bocaire