<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Using ... </TITLE>
</HEAD>
<BODY BGCOLOR="#efefef" TEXT="black" LINK="blue" VLINK="#551A8B" ALINK="red">

<A HREF="isc.html"><EM> Information for ISC Users</EM></A>
 <b>:</b> <EM>Using ... </EM><BR>
<b>Previous:</b> <A HREF="isc9.html"><EM>Installation </EM></A><BR>
<b>Next:</b> <A HREF="isc11.html"><EM>Acknowledgements </EM></A>


<HR NOSHADE>
  <H2><A NAME="16"></A>10. Using ... </H2>

<p>
<ul>
<li>Xprt:<p>The new Xprint Server is configured to use lpr as its print helper
so you have to install and configure lpr to use Xprt.</p>


</li>
<li>Keyboard:<p>You don't need any modmap-File to get your keyboard
working with any iso-8859-1 Font. Simply enable </p>
<p>
<ul>
<li>LeftAlt  Meta
</li>
<li>RightAlt ModeShift
</li>
<li>RightCtl Compose</li>
</ul>
</p>
<p>in your XF86Config - Section "Keyboard"</p>

</li>
<li>xpcterm: <p>if you want to get the German 'Umlaut' inside your ISC X11R4 client
xpcterm when you are using the ega/vga font. Set up the
user's .Xdefaults to contain:
<pre>
         XEga*AT386.Translations: #override \
                   Shift&lt;Key&gt;odiaeresis: string(0x99) \n\
                        &lt;Key&gt;odiaeresis: string(0x94) \n\
                   Shift&lt;Key&gt;adiaeresis: string(0x8e) \n\
                        &lt;Key&gt;adiaeresis: string(0x84) \n\
                   Shift&lt;Key&gt;udiaeresis: string(0x9a) \n\
                        &lt;Key&gt;udiaeresis: string(0x81) \n\
                   Shift&lt;Key&gt;ssharp: string(0x3f) \n\
                    Meta&lt;Key&gt;ssharp: string(0x5c)  \n\
                        &lt;Key&gt;ssharp: string(0xe1)
         
</pre>
</p>
<p>The only disadvantage is that you have to use <code>Alt</code> instead of
<code>AltGr</code> to get the <code>\</code> Backslash (on a German
Keyboard)</p>
<p>You have to call your xpcterm with the option 
<code>-name XEga -fn ega</code></p>

</li>
<li>Switching between X11R5 and X11R6 configuration<p>to compile X11-Clients as either R6 or R5 clients,
should be as easy as you only switch the PATH components
so that either <code>/usr/X11R6/bin/xmkmf</code> or 
<code>/usr/X386/bin/xmkmf</code> would make the new Makefile.</p>

</li>
<li>ISC Streams Pipes <p>The old path to the pipes on ISC's R4 <code>/tmp/.X11-unix</code>
has changed to <code>/dev/X/ISCCONN</code>. For compatibility 
reasons on ISC, the pipes in the new directory will be
linked to a file inside the old. 
This will normally be a hard link, so it can't go across
filesystems. On ISC Version 4.x this is now allowed. But
you should use the new S5L on both filesystems.
ISC30 systems should take care that the two directories
are on the same FS. Else if you are using a ISC40 compiled
binary, the Server could maybe abort due to a SIGSYS.
We tried to catch this signal, so if it dumps please send
me a note.</p>

</li>
<li>Warnings you may see: <p>
<ul>
<li>Since 3.2A, you could see a warning from pre X11R6.3 clients.<p>
<pre>
           Warning: Unable to load any usable fontset
           
</pre>

The case are the new gzipped fonts, but the Warning isn't serious.</p>

</li>
<li>If you start a server you may see the following message:<p>
<pre>
        _XSERVTransOpen: transport open failed for named/enigma:0
        _XSERVTransMakeAllCOTSServerListeners: failed to open listener for named
           
</pre>

This message either isn't critical. Interactive doesn't support this
kind of connection.</p>

</li>
</ul>
</p>

</li>
</ul>
</p>


 <HR NOSHADE>
<A HREF="isc.html"><EM> Information for ISC Users</EM></A>
 <b>:</b> <EM>Using ... </EM><BR>
<b>Previous:</b> <A HREF="isc9.html"><EM>Installation </EM></A><BR>
<b>Next:</b> <A HREF="isc11.html"><EM>Acknowledgements </EM></A>



</BODY>
</HTML>
