Windows

1. The Windows platform does not support character oriented programs. So any program which is using FORMs, Softkeys etc. needs to be converted to Dialogs.
   Change: Character mode is supplied by A.06.20.

2. QUERY and other utilitiy programs such as CFORM, MFORM and PFORM require character I/O which is not available on Windows.
   Change: Character mode is supplied by A.06.20.

3. The Eloquence servers can not be run on Windows 95/98.

4. The Intel processors have a different byte order than PA-RISC processors. This may affect you when you access a packed buffer (eg. DBINFO or DBGET) because Eloquence builds them in the order which is native to the underlying system (PACK/UNPACK USING and IN DATA SET takes care of it). However if you unpack buffers manually, you have to take care of the different byte order.

   This may also affect you, when unpacking the DBINFO 202 result buffer. The number of records and data set cpapcity must be unpacked as a 32 bit value (DINTEGER) instead of two 16 bit values.

5. On HP-UX, the HP-Roman8 character set encoding is usually used (and Eloquence internally uses it for backards compatibility). Please be aware, that with Windows the ISO8859-1 character set encoding is usually used. Files written by Eloquence may need to be converted if used outside Eloquence.

6. Windows does not include POSIX commandline utilities. So any program which depends on the availability of a shell or other tools needs to be converted.

Linux Platform

1. The eloq program (providing virtual terminals - "TASKS") is currently not available on Linux. The Linux kernel does not support the ioctl() functions we use to communicate with ptys.
   Change: The eloq program is available as of A.06.30.

2. There is no Motif Dialog Driver available on Linux. The Linux version is currently limited to forms and ASCII dlg. However, you can use Linux as a server for Windows PCs using graphical dialogs.

3. The Intel processors have a different byte order than PA-RISC processors. This may affect you when you access a packed buffer (eg. DBINFO or DBGET) because Eloquence builds them in the order which is native to the underlying system (PACK/UNPACK USING and IN DATA SET takes care of it). However if you unpack buffers manually, you have to take care of the different byte order.

   This may also affect you, when unpacking the DBINFO 202 result buffer. The number of records and data set cpapcity must be unpacked as a 32 bit value (DINTEGER) instead of two 16 bit values.

4. On HP-UX, the HP-Roman8 character set encoding is usually used (and Eloquence internally uses it for backards compatibility). Please be aware, that with Linux the ISO8859-1 character set encoding is usually used. Files written by Eloquence may need to be converted if used outside Eloquence. You can use GNU recode to convert character set encoding of files.

5. The Linux utilities are a different from HP-UX. For example: Linux uses the BSD printing system (lpr) instead of the SYSV one (lp). So any program which uses lp or lpstat directly needs some minor adaption. In addition all modifications which were made to printer interface files must be adapted to lpr filters.

6. The Eloquence terminal adaption of the Linux console does not support underline. This is a limitation of the Linux console driver.

   The following X11 based terminal emulators have been tried:

   • rxvt (version 2.18) works with TERM=dtterm
   • dtterm (part of the CDE product which is available for Linux from either RedHat/TriTeal or Xig).
   The X11 emulator windows currently dont provide a replacement for the "HP Special" keys like Clear-to-End-of-Line or Clear-to-End-of-Display, Insert-Line, Delete-Line.

   Change: Please refer to the A.06.30 release notes for updated information.