OpsConsol setup and Win XP 64

42 views
Skip to first unread message

danverde

unread,
Sep 10, 2009, 3:51:08 PM9/10/09
to IADS
I am trying to setup our ops console on windows xp 64. All the client
machines are also Win XP 64. Everything seems to be working
correctly, except for the ops console doesn't know how to start the
real time clients. It reports each client machine as yellow and not
having a client startup file. The ops console thinks the clients are
in the 'c:\Program Files\IADS' directory, instead of the 'C:\Program
Files (x86)\IADS' where they really are. Right clicking on the
client, it shows that iads.exe is under c:\progra~1, this needs to be
c:\progra~2. Can I tell the ops console where each client exec is?
The ExeLocation parameter is set to c:\progra~2 in the Global section
but it doesn't seem to be helping.

Thanks,
Dan Green


Michael Jones

unread,
Sep 10, 2009, 4:38:19 PM9/10/09
to IADS
Hiya Dan,

Unfortunately, you have discovered the hard way that x64 OSs are not
yet supported in a realtime environment unless you run everything by
hand. There are a long list of fixes for this slated for 7.0 (Though
many will start showing up much sooner then that)

What version of IADS are you running? I might be able to provide you
some version specific workarounds.

danverde

unread,
Sep 11, 2009, 7:21:35 AM9/11/09
to IADS
We are using 6.2

Michael Jones

unread,
Sep 11, 2009, 5:59:49 PM9/11/09
to IADS
Hello again Dan,

Unfortunately, this turns out to be a bug for all Client Objects in
the OpConsole - its alredy fixed for the next release.
There isn't a solid workaround that I can come up with. Currently
Clients must exist at C:\Progra~1\IADS\ClientWorkstation\

I tried moving both of the folders for Program Files to a new
subdirectory but the OS kept protecting itself and would let me move
things like Wordpad.exe

Vista has a commandline tool available called fsutil.exe. You can use
it to change the mangled name of file and folders, but I get access
denied on the Program Files folders. If you can find a way todo it
early enough on boot it might have promise.
Usage : fsutil file setshortname <filename> <shortname>
Eg : fsutil file setshortname "C:\Program Files" PROGRA~9

In theory, you could use a Linux Boot CD to move the contents around
and then back such that "Program Files (x86)" = "C:\Progra~1" instead
of 2


My apologies, thanks for catching it and pointing out the error
> > > Dan Green- Hide quoted text -
>
> - Show quoted text -

Michael Jones

unread,
Sep 11, 2009, 6:38:14 PM9/11/09
to IADS
Ugh, there are additional hurdles....Tons of stuff in the registry
explicitly uses the mangled shortnames. Even if you reorder the
folders to get the desired names, it would neccessitate scouring the
registry and modifying thousands of entries.
> > - Show quoted text -- Hide quoted text -

Patrick Mattingly

unread,
Sep 17, 2009, 10:33:04 AM9/17/09
to IADS
Hi Dan,

Can you tell me more about your environment? Are you testing Winx64
with IADS for compatibility or is this a must have or perhaps you
don't have a choice of which OS to use.
Reply all
Reply to author
Forward
0 new messages