Vista 64 and WinGMM

[Joe]

I am having a problem running WinGMM on a Vista machine.
My OS is Vista Home, 64 bit.
My user account has administrator privileges.
I am running WinGMM in compatibility mode for Windows XP (Service Pack
2)

The software installs OK, but when I run wg.exe, I get the following
error message:

Run-time error '339':
Component 'comctl32.ocx' or one of its dependencies not correctly
registered: a file is missing or invalid

The file 'comctl32.ocx' is located in directory c:\windows\SysWOW64
on
my machine.

When I register comctl32.ocx I get the message “DIIRegesterServer in
c:\Windows\SysWOW64\Comdlg32.ocx succeeded”. However, when I run
WinGMM, I get the same error message stated above.


I have been searching the INTERNET, and have found a kajillion forums
dealing with this problem, but I cant find a solution.
One Site:
http://social.msdn.microsoft.com/Forums/en-US/vbgeneral/thread/4f315164-3148-4adf-843d-87479e984870
says to unregister the OCX files, but I can't figure out how to do
that. I tried the command “unregsvr32” but this is not a recognized
command.

I am running a dual boot (VISTA/XP) so I am able to use GMM, but it is
a pain in the butt. I'd much rather run GMM from VISTA.

Any ideas will be greatly appreciated. Also, how do you unregister an
OCX file????

Joe S.

[Mil]

BLM's latest catch 22.

We don't do software and the leading GIS software developer doesn't do
surveying. At least not our flavor.

Still jump ball.

[David Grainger]

Have you tried searching the registry for 'comctl32.ocx' to see if and
where it is getting registered?

On Oct 6, 2:40 pm, Joe <jschm...@cnsp.com> wrote:
> I am having a problem running WinGMM on a Vista machine.
> My OS is Vista Home, 64 bit.
> My user account has administrator privileges.
> I am running WinGMM in compatibility mode for Windows XP (Service Pack
> 2)
>
> The software installs OK, but when I run wg.exe, I get the following
> error message:
>
>    Run-time error '339':
>    Component 'comctl32.ocx' or one of its dependencies not correctly
> registered: a file is missing or invalid
>
> The file 'comctl32.ocx' is located in directory  c:\windows\SysWOW64
> on
> my machine.
>
> When I register  comctl32.ocx I get the message “DIIRegesterServer in
> c:\Windows\SysWOW64\Comdlg32.ocx succeeded”.  However, when I run
> WinGMM, I get the same error message stated above.
>
> I have been searching the INTERNET, and have found a kajillion forums
> dealing with this problem, but I cant find a solution.

> One Site:http://social.msdn.microsoft.com/Forums/en-US/vbgeneral/thread/4f3151...

[Joe]

I opened Registry Editor and did a search on conctl32.ocx. It found
the file right where I knew it was: c:\windows\syswow64\conctl32.ocx.

I'm not sure where to check to see if and where it is getting
registered.

I guess the question to ask is;
Is this a VISTA problem or is it a 64 VS 32 bit OS problem? Does
WinGMM need to be re-compiled to run on any 64 bit system?


Joe

[Kurt B. Wurm]

It could be so Joe, but unfortunately that is impossible without support.

Beyond that, WinCMM and WinGMM need to be upgraded to the .NET framework,
which provides many new possibilities (and problems). This would be an
extensive effort -- one that I'm willing to take on, but only with support.
For example -- gmm dataset could be migrated to an XML implementation,
something that NILS promised but I don't believe ever delivered. Other
issues is that all file I/O from the interface needs to be rewritten, I
think the fortran code could be made static, but that puts additional
functionality into the interface to perform the translations.

NMSU is in preliminary stages of development of a graduate program, this
type of project would be very beneficial to us as well as the profession as
a whole.

[David Grainger]

Your original meesae said that the error message was:

Run-time error '339':
Component 'comctl32.ocx' or one of its dependencies not correctly
registered: a file is missing or invalid

So why not look for the same OCX why look for a different one? Or
was that just a typo in this post?

Also, did you not say that your PC is dual boot, XP/VISTA? So would
it not be 64 bit under either OS? Seems to me it would indicate there
is Vista configuration problem.

[David Grainger]

It would be sweet to be able to do the things you suggest. Perhaps
with the demise if NILS someone will be willing to fund such and
effort. But then that would make sense ......

> Joe- Hide quoted text -
>
> - Show quoted text -

[Kurt B. Wurm]

Maybe....just maybe, this problem will go away after Joe upgrades to
Windows 7 !!!

-----Original Message-----
From: win...@googlegroups.com [mailto:win...@googlegroups.com] On Behalf Of
David Grainger
Sent: Friday, October 30, 2009 1:45 PM
To: Measurement Management BBS
Subject: Re: Vista 64 and WinGMM

[Joe]

Yea, Kurt, I know its all funding based., I was just trying to figure
out what the actual problem is.
So, Windows 7 might be the cure-all. I think I'll wait and let
someone else do all the testing.
Actually I think my son has a copy on his laptop. Maybe I'll install
Wingmm and see what happens.

Dave, It was a fat finger on my response; I meant to say
'comctl32.ocx'.
Also, my dual boot is to 32 bit XP, so that's how I get Wingmm to
work.

I was thinking the same thing that you were Dave, since the
government isn't sinking a lot of money into NILS, maybe a re-visit ti
GMM (and CMM) might be appropriate. But like you said, that makes too
much sense.

Oh well. Thanks for the ideas.

[jlwahl]

I just installed W7 for the second time. (I upgraded my hardware) and
wingmm installed and seems to work. Of course I haven't tested
everything *AND* I installed the 32 bit version.

FYI - jerry

[Milby]

I have been fielding some questions on NILS and GCDB recently so
called Mary Hartel to get an update on the team she is on looking at
options. As usual, limits to what she could say but indications are
good progress has been made on identification of options capable of
performing all functionality intended of NILS and more. She also said
Interior and OMB have been in the loop so hopefully, it won't be *too*
much longer before we hear something.