Re: Identifying which Windows version ...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"Steve Richfie1d" <Steve@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:43kn2sF1nc699U1@xxxxxxxxxxxxxxxxx
> First, thanks for all of the help with my prior problem. The suggested
> changes to chop the offending line up into several statements apparently
> solved the problem without ever identifying exactly what it was! Anyway, I
> can now have a 30K log.
>
> Now, I am running into problems interfacing with other products that have
> survived Windows Logo testing. The special problem here is that Logo
> requirements specify DIFFERENT places for files to go depending on which
> version of Windows they are running on, a sort of super mutual
> incompatibility feature that Microsoft invented! Sounds super stupid and
> non-productive to me, but Microsoft certainly isn't going to change
> because I don't like something. Anyway, after Logo testing, files now go

You got the last part right anyway.

> in one of 3 different places for different Windows versions in the
> following list:
>
> 98/ME, NT, 2K/XP

Yes. Different folders for different systems. This has nothing to do with
Logo testing.

>
> I Googled for ways of identifying which OS is running, but everything
> seemed to predate XP. Also, the functions that access this information are
> a little different in .net, which I am not presently using but which I am
> trying to avoid incompatibilities with as a hedge against the future.

You are off in the rough. These are installation issues and are largely
handles by the Windows Installer. Why do you care where the various DLL's
are installed at run time?

>
> Past posted methods seem to either use GetVersion and pick through the
> numbers it returns, or use the Environ function to see which environment
> variables exist and which don't, which changes with the version as they
> keep adding new environment variables over time.
>
> Of course I could just go looking for the files, but then I run a risk of
> stumbling onto some old obsolete files that were copied in from

What files exactly? Whatever they are, they are likely registered.

> another system, or were left over on the present system from before the
> system was upgraded. Searching in newer-to-older order would reduce but
> not completely eliminate this sort of risk, as users could roll back to
> older systems or applications.
>
> Anyway, I figured that you MVPs just HAD to have solved this one long

Don't count on that.

> ago to ever be able to properly install most products, so if you could
> just let me in on the solution, it would save me a LOT of work
> re-inventing the wheel.

First, what is the question?

>
> Thanks again for your continuing help.
>
> Steve Richfie1d


.

Relevant Pages