This
is the Tips & Tricks section for Intel Itanium2 world, including Linux and
Windows 64bit O.S., open source and commercial products problems.
O.S. |
Product or component | Tips
& Tricks |
Linux RHES3
and 4 WIndows 2003 SP1 | MQ4CPP | A
message oriented middleware working on Itanium2. See
there. |
Linux RHES3
and 4 WIndows 2003 SP1 | True3D*Shell | A
new concept of 3D desktop working on Itanium2. See
there. |
| Linux RH AS
2.1 | BEA JRockit 8.1 | Interoperability problems
with SUN JRE 1.4.1 64bit |
| Windows
2003 | BEA JRockit 8.1 | Works fine. |
| Windows
2003 | ORACLE 9i | Installation problems with
more 4 nodes using Real Application Cluster. Need configure each node by hand.
After installation ORACLE works fine. Use 32bit version of ORACLE client to manage
server. |
| Windows 2003 | SQL
Server 2000 | In the installation CD is missing the Enterprise
Manager. Use instead 32bit version of SQLServer 2000 installation CD with SP3.
|
| Windows 2003 | Analysis
Services (SQLServer2000) | Use SP3a for Analysis
Services and security patch KB815495. Problem of server registration if
more DB instances are present : workaround registering only the server name without
DB name. Problem with restore of cube archive (.cab): workaround with command
line 'msmdarch' executable. |
| Windows
2003 | Ascential Datastage | The product
woks fine in emulation mode. When you define datasource be aware to define the
same entry in 32 and 64 bit ODBC Administrator. You find 64bit odbcad32.exe
in \Windows\system32 folder. You find 32bit odbcad32.exe in \Windows\SysWOW64
folder. |
| Windows 2003 | Lotus
Domino | The product works fine in emulation mode. |
| Windows
2003 | Citrix Metaframe | The product doesn't
work in emulation mode. |
| Linux RH
AS 2.1 | ORACLE 9i | The product works
fine with Real Application Cluster. Tested also with Intel iANS for network failover. |
| Windows
2003 | BEA Weblogic 8.1 | Workshop GUI doesn't
run. I think there is an incompatibility between JRE 64bit and Workshop DLL's
called via JNI. |
| Windows 2003 | .NET
Framework 2.0 | The installation fail. You need to install
before Microsoft Windows 2003 Service Pack 1 Beta Pre-release for IA64 (ask to
Microsoft) and then Microsoft .NET Framework 2.0 Beta 1 Release for IA64. |
| Windows
2003 | DLL compatibility | WOW64 launches
and runs 32-bit applications seamlessly. The system isolates 32-bit applications
from 64-bit applications, which includes preventing file and registry collisions.
Console, GUI, and service applications are supported. The system provides interoperability
across the 32/64 boundary for scenarios such as cut and paste and COM. However,
32-bit processes cannot load 64-bit DLLs, and 64-bit processes cannot load 32-bit
DLLs....... Click
here to read the article.
|
| Windows
2003 | DLL compatibility | To use a 32bit
DLL from a 64bit executable (for example an .ASP form on IIS calling a service)
you have to register it using 'Component Services' utility. This wrap your DLL
in a COM object decouling 64bit client from 32bit service. |
| Windows
2003 | Microsoft SDK | Debugger DbgW64.exe
crashes on File/Open. |
| Windows 2003
| Microsoft SDK | cl.exe compliler give lot
of warning using C++ std libraries. Streams (cout, fstream, ...) aren't thread
safe. |
| Windows 2003 | Opera | This
product works fine in emulation mode. |
| Windows
2003 | WinZip | This product works fine in
emulation mode. |
| Windows 2003 | Adobe
Acrobat | This product works fine in emulation mode. |
Windows
2003 Linux RH AS 2.1 | EFI | It
is not possible define a dual boot for Linux and Windows. Each O.S. redefine the
EFI partition during O.S. installation. |
| Windows
2003 | UltraVNC | This product works fine
but use too much CPU resources. |
| Windows
2003 | Eclipse | The product doesn't work
in emulation mode. I think there is an incompatibility between JRE 64bit and Eclipse
DLL's called via JNI. |
| Linux RH
AS 2.1 | Hercules System/370, ESA/390, and z/Architecture Emulator | This
product compile and works fine on IA64. Click
here for details about Hercules emulator. |
| Windows
2003 | DDK WinDbg | There's
a problem with Win32 OutputDebugString / TRACE statements running under the debugger
near synchronization conditions. The problem is documented roughly in the article
'PRB: Synchronization Failure When Debugging' on MSDN.
As I understand it, it's more of a limitation of the Win32 debug environment
rather than any specific debugger.
The solution unfortunately is to
remove the TRACE / OutputDebugString calls from around the code making SetEvent
/ WaitForSingleObject (or other synchronization routines). |
| Windows
2003 | ORACLE 9.2 Client | Some 32bit
executable need OCI.DLL to connect to ORACLE database via SQL*Net. If your application
is installed in IA32 emulation mode under:
C:\Program Files (x86)\...
you should receive the error: ORA-6413 "CONNECTION NOT
OPEN". This is because in the connection string SQL*Net add a section
like this: ( CID = C:\Program Files (x86)\...\your_exec.exe ) causing
a parsing error. A workaround is to install your application directly under C:\
. |
