A client has purchased a 64 bit server - IBM XSERIES_3400 running Server 2003 R@ 64bit service pack 1

They have no PCs connected yet, so I wanted to test that OI 7.2.1 works on the server.

I Copied my OI system to the server and ran oinsight.exe and nothing happened.

I installed a UD3 service and put LH3.LOG in the OI dir.

Nothing in log.

Questions:

Should OI have run (and the UD service)

Can it ONLY run in compatibilty mode (Engineer said can do this)

If compatibilty mode, how does that affect the service.

The engineer said that the DEP was hardware, so I assume I will have a DEP problem as well.

Will OI8 have the DEP problem fixed.

Will OI8 be 64bit compatible.

If OI cant run directly on the server, what about when *remote terminal* is running on the server will OI still run.

I know a lot of these questions depend on other answers, but I wanted to cover all bases.

TIA

-Barry

(RIP - Billy Thorpe)

Barry,

I can't speak specifically and I have not tested 64 bit yet. But, generally speaking there are compatibility issues with 32 bit programs on 64 bit OS. Basically, the 32 bit applications have to run under an emulator WOW32? similar to how XP32 handled 16bit/DOS programs with Wowexec. And as you know with any emulation there are bound to be problems. That being said, there is nothing that forces you to run a 64 bit OS on 64 bit hardware. The 32 bit OS will work just fine. In reality, whenever you purchase new technology as different as 32bit to 64bit, it should be tested and not assumed that it will work.

The DEP issue is a whole other subject regardless of number of bits in your OS.

HTH,

John

Barry,

We are running OI here on a 64-bit setup almost exactly the same as yours, so in my mind it is not an issue of the 64-bit OS. If you see in the registry, OI, the UD and OECGI will be in the Wow6432Node key in the registry. When installing OI on the 64-bit Server, we did nothing special to allow it to run in 64-bit. It has now been running in production for over a year now with no show-stopping issues.

So if my vast assumption is correct, that leaves, DEP. Probably the easiest way to confirm it is a DEP problem is to reboot the Server. If upon reboot you get a number of Microsoft Errors about OpenInsight not working, then it points to DEP.

The ways to get around the DEP issue for now are in other postings. Once you get past that problem, test OI thoroughly to confirm that you aren't running into problems with OI on the 64-bit platform.

Hope it helps.

Is the DEP issue with OI going to be fixed

Barry-

It's on our list of things to fix. It seems to occur with rcl4.dll. To fix that, we need to change a version of a library we use to make nearly all of our dlls. However, there are enough differences between the original and current version of this library that we can't just plug and play; we need to modify the code in many, many of our routines. So, we're treading lightly right now. It is scheduled to be attacked right after the 8.0 release.

Hope this helps-

Mike

I ran up OI 7.22 on a 64 OS and - after sorting DEP issues - found it ran fine. The problem eventual came down to not all other business critical software is good for OS x64.

After further investigation I concluded that effectively MS Windows Server x64 is a white elephant (or a sandbox for the x64 experience - which ever way you want to think). That is, not all key software is good to go AND how wants to run WOW enabled sessions AND the new server edition - Longhorn - is due out in Nov 2007. Longhorn will be available in both flavours but will be the last to offer x86.

In a server farm with lots of alternative platforms, OS 64 has its place but in a small shop - say a couple of server boxes - it doesnt make that much sense at present due to potential software compatability issues.

Richard Bright

]]rcl4.dll

Which is the universal driver 3..correct.

As I have a number of files that were create under this, and can only be *read* by UD3, how can i *convert* these files back to "all networks 2.1*

G'day Barry,

This is what you have to do to convert UD3.0 files to the traditional format.

1. Change your network driver using NETDRV.EXE to the All Networks Driver V2.1.

2. Create a new subdirectory on your computer. Login to OI with the All Networks driver V2.1 set and then create a new file for each UD3.0 file you want to create in the new subdirectory. Make the name of each file different to the ud3.0 filename. You will need to have both the UD3.0 files and the new files attached at the same time in the next step.

3. Logout of OI and change the network driver back to UD3.0 using netdrv.exe. Log back into OI, attached the new subdirectory, then record copy the contents of each UD3.0 file to the newly created 2.1 files.

4. Detach the UD3.0 files and rename the v2.1 files to the UD3.0 filenames. Now you should have your data in files that work with v2.1 all networks driver.

Dave G

Cool, thanks

View this thread on the Works forum...