Files from CT/MRI

I have a couple of CDs containing images and supporting software.

However, I cannot get the program to run.

There's a file called start.hta. Double-clicking on it brings up a
window with three buttons: view images, no results available and exit.
It also says "Powered by pacsgear".

There is a large exe file called GEARview.exe.

Clicking "View Images" does nothing. "No results" is grayed out and
"Exit" terminates the program.

I attemptedÂ* to execute GEARview.exe directly and got a pop-up:

GearviewBasic.exe - .NET Framework Initialization Error.
Please set registry key
HKLM\Software\Microsoft\.NETFramework\InstallRoot to point to the .NET
Framework install location.

I found .Net Framework at

C:\Windows\INF\.NETFramework
C:\Windows\System32\Tasks\Microsoft\Windows\.NET Framework
C:\Windows\System32\Tasks_Migrated\Microsoft\Windo ws\.NET Framework

The registry key is set to
C:\Windows\Microsoft.NET\Framework64\

WhatÂ* do I do now?

Thank you.

In article , Alek
wrote:

I have a couple of CDs containing images and supporting software.

ignore the supporting software.

medical images are normally dicom, which can be read any of a variety
of apps.

https://www.dicomstandard.org/using/cds/
https://medevel.com/free-dicom-viewers-for-windows/

Alek wrote:
I have a couple of CDs containing images and supporting software.

However, I cannot get the program to run.

There's a file called start.hta. Double-clicking on it brings up a
window with three buttons: view images, no results available and exit.
It also says "Powered by pacsgear".

There is a large exe file called GEARview.exe.

Clicking "View Images" does nothing. "No results" is grayed out and
"Exit" terminates the program.

I attempted to execute GEARview.exe directly and got a pop-up:

GearviewBasic.exe - .NET Framework Initialization Error.
Please set registry key
HKLM\Software\Microsoft\.NETFramework\InstallRoot to point to the .NET
Framework install location.

I found .Net Framework at

C:\Windows\INF\.NETFramework
C:\Windows\System32\Tasks\Microsoft\Windows\.NET Framework
C:\Windows\System32\Tasks_Migrated\Microsoft\Windo ws\.NET Framework

The registry key is set to
C:\Windows\Microsoft.NET\Framework64\

What do I do now?

Thank you.


You can see here, that the .hta is used to reduce the
level of interaction required with the user.

https://devblogs.microsoft.com/scrip...n-from-an-hta/

Your "program" GearView is probably built on .NET.
It uses a .NET runtime library, which needs to be
on the machine in advance.

Good developers "sniff" for .NET before invoking it,
then the developer prints instructions on the screen,
detailing what the user needs to do. I find very few
commercial applications have any sort of "handler"
for this issue. A number programs come back with
"mscoree blah blah blah", leaving it to the user
to deduce that mscoree has something to do with .NET
and the latest version of .NET might be missing or
something.

https://docs.microsoft.com/en-us/dot...ser-experience

Versions of Windows now, have a "primary" version of
..NET, which is packaged with the OS. Say, for example,
Windows 10 uses .NET 4.0 . Well, the Windows Firewall
is coded in .NET, and if for some reason .NET 4.0 is
not working, the Firewall code won't load and the
Windows networking stack will not come up! A disaster.

In Control Panels : Programs and Features : Windows Feature
you may see

Tick .NET Framework 3.5
Box

When you see that, you know that:

1) The OS has its own private, unremovable .NET 4.0
So that's not what GearView is looking for.
If .NET 4.0 is ever broken, the usual repair techniques
cannot be used to fix it (will likely need a Repair Install).

2) The offer of a tick box for .NET 3.5, gives you
.NET 2.0, .NET 3.0, .NET 3.5. These all have the
same "CLR" version number. By ticking the one box,
you're actually getting code to handle *three* messes.
Once ticked, you might need to reboot when requested
to do so. NGEN really shouldn't need to run when an older
version is added like that, but with .NET I usually
reboot for the hell of it.

Now, it's back to "trying your CD again". Open the
C:\Program Files (x86)\Internet Explorer or similar,
where you will find a 32-bit version of "iexplore.exe".
That's the old Internet Explorer 11. Drop the "start.hta"
onto the EXE icon, and see if that works. If that fails,
you can test on C:\Program Files\Internet Explorer\iexplore.exe
which is the 64-bit version. Now that you've ticked
..NET 3.5, there really isn't an excuse for it not to
work.

There are still a few executables compiled with .NET 1.1
or .NET 1.0. Those libraries can be installed separately
if and when you need them. That would require a download.

But at the moment, check
Control Panels : Programs and Features : Windows Feature
and ensure .NET 3.5 is enabled.

To reach control panels, right click Start and use the Run
box. Type "control" without the double-quotes into the
Run box and run it. This will open Control Panels. Right
click the taskbar icon and select "Pin to Taskbar" so you
will have a permanent Control Panels icon for future usage.

Paul