EXTERNAL:Re: [omniORB] OmniORB on a Win 64 machine.

[Obermaier, Stephen J (IS)]

Thanks, I'll give this a shot.  FYI one of the things I did discover is that Win64 machines have parallel registry keys, one set for x64 applications, and one set for x32 applications.  So when you install the 32-bit omniORB on a x64 machine, the sample registry file must be modified so that HKEY_LOCAL_MACHINE\SOFTWARE\omniORB registry keys are also migrated to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\omniORB or the 32-bit ORB won't see them.  So with this fix, I can at least get the correct NS Initref, but there are still some issues passing objects around that I need to track down.

Steve O.

Northrop Grumman
Mission Systems

-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org] 
Sent: Wednesday, September 29, 2010 5:56 AM
To: Obermaier, Stephen J (IS)
Cc: omniorb-list at omniorb-support.com
Subject: EXTERNAL:Re: [omniORB] OmniORB on a Win 64 machine.

On Fri, 2010-09-24 at 15:07 -0500, Obermaier, Stephen J (IS) wrote:

> When I run omniNames on a Windows Server 2003 box (x64 version), the
> names server seems to run just fine, but I cannot resolve the Names
> IOR when running a local application on the same machine.

Run your client with -ORBtraceLevel 25 -ORBtraceInvocations 1. That will
show what it's doing and where it fails.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --