<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: X Windows in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985689#M923261</link>
    <description>your font path is a little &lt;BR /&gt;messy too, but as pointed &lt;BR /&gt;out the problem is the mouse &lt;BR /&gt;device file.&lt;BR /&gt;&lt;BR /&gt;This is sometimes defined in &lt;BR /&gt;the BCH (power up prompt / &lt;BR /&gt;bios equivalent).  Make sure &lt;BR /&gt;it's defined correctly.  &lt;BR /&gt;&lt;BR /&gt;Also, ioscan -fnk should show &lt;BR /&gt;a CLAIMED mouse device.. &lt;BR /&gt;check this and it will give &lt;BR /&gt;your the HW path, device file &lt;BR /&gt;and state.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I'm guessing it should be hil &lt;BR /&gt;and not hid.. but that's a &lt;BR /&gt;guess!&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
    <pubDate>Mon, 02 Jun 2003 08:44:22 GMT</pubDate>
    <dc:creator>Bill McNAMARA_1</dc:creator>
    <dc:date>2003-06-02T08:44:22Z</dc:date>
    <item>
      <title>X Windows</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985686#M923258</link>
      <description />
      <pubDate>Sat, 31 May 2003 09:12:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985686#M923258</guid>
      <dc:creator>Sriharimohan</dc:creator>
      <dc:date>2003-05-31T09:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: X Windows</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985687#M923259</link>
      <description>It is complaining that it can't open the mouse device file.&lt;BR /&gt;You could run lsdev to see if there is an hid device driver in the kernel.  If it is missing you should add it from sam.&lt;BR /&gt;You could check that there is a /dev/hid/mouse_000 file.  You can create or recreate that file with 'insf -e'.&lt;BR /&gt;You should also check that you have a working mouse plugged in. ;-)&lt;BR /&gt;</description>
      <pubDate>Sat, 31 May 2003 19:17:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985687#M923259</guid>
      <dc:creator>Mike Stroyan</dc:creator>
      <dc:date>2003-05-31T19:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: X Windows</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985688#M923260</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt; Actually I need to start the X-windows daemon and comfigure in my IFP HP.11.23 Server. I m not using it directly. i m accessing the 11.23 X-windows from my Windows-XP Machine using X-Manager.&lt;BR /&gt;&lt;BR /&gt; The X-Windows daemon is not configured in the IPF Hp-11.23 Server, how to do that.&lt;BR /&gt;In HP-UX 11.11 or 11.22 they are automatically configured and working fine...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;rgds,&lt;BR /&gt;Hari</description>
      <pubDate>Mon, 02 Jun 2003 08:38:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985688#M923260</guid>
      <dc:creator>Sriharimohan</dc:creator>
      <dc:date>2003-06-02T08:38:18Z</dc:date>
    </item>
    <item>
      <title>Re: X Windows</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985689#M923261</link>
      <description>your font path is a little &lt;BR /&gt;messy too, but as pointed &lt;BR /&gt;out the problem is the mouse &lt;BR /&gt;device file.&lt;BR /&gt;&lt;BR /&gt;This is sometimes defined in &lt;BR /&gt;the BCH (power up prompt / &lt;BR /&gt;bios equivalent).  Make sure &lt;BR /&gt;it's defined correctly.  &lt;BR /&gt;&lt;BR /&gt;Also, ioscan -fnk should show &lt;BR /&gt;a CLAIMED mouse device.. &lt;BR /&gt;check this and it will give &lt;BR /&gt;your the HW path, device file &lt;BR /&gt;and state.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I'm guessing it should be hil &lt;BR /&gt;and not hid.. but that's a &lt;BR /&gt;guess!&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Mon, 02 Jun 2003 08:44:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985689#M923261</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2003-06-02T08:44:22Z</dc:date>
    </item>
    <item>
      <title>Re: X Windows</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985690#M923262</link>
      <description>You don't want x11start.  That is trying to start an X server.&lt;BR /&gt;&lt;BR /&gt;Remote logins from a PC X server will depend on dtlogin.  It may already be running.  You can run "/usr/dt/bin/dtconfig -e" to  enable the startup of dtlogin each time you go to init 3 run-level.  If the system is already at init 3 you could use "/sbin/init.d/dtlogin.rc start" to start dtlogin.  If the system has been configured with a custom /etc/dt/config/Xaccess you may need to edit it to allow your system to connect to dtlogin.</description>
      <pubDate>Mon, 02 Jun 2003 14:59:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/x-windows/m-p/2985690#M923262</guid>
      <dc:creator>Mike Stroyan</dc:creator>
      <dc:date>2003-06-02T14:59:37Z</dc:date>
    </item>
  </channel>
</rss>

