From: Mark Schupsky (mark.d.schupsky@lmco.com)
Date: Mon Feb 24 2003 - 12:37:45 EST
> Mark Schupsky wrote:
>
>>
>> I attached a bunch of replies to my original query to the list. Looks like we need
>> to find
>> a small box device to attach to the chain of the keyboard/mouse. It would seem to me
>> that if that
>> device is lost, we are stuck. Lots of good advice. Thanks to:
>
> Roger McNulty
> Marc Godbout
> Kevin Davisson
> Jinu Suresh
> ryan green
> rick jones
> Wolf-Dietrich Schmook
> Jim McDonald
> Volker T. Mueller
>
>> --
>> Mark Schupsky mark.d.schupsky@lmco.com
>> EIS UNIX SysAdmin Lockheed Martin CSS Newtown, PA
>> --
>>
>> ----------------------------------------------------------------------------
>>
>> Has anyone ever heard of a /dev/hil1 device? We have an ancient 715 running HPUX
>> 9.x that someone is trying
>> to ressurect to retrieve some old drawings from an application called ME10. Would
>> this be a hardware device used to
>> control application licensing?
>>
>> when I try to start this as root it gives me an error:
>> # /etc/MEls
>> Restart using device /dev/hil1
>> /dev/hil1: Device busy
>>
>> TIA, Mark
>> -----------------------------------------------------------------------------
>>
>> Mark,
>>
>>
>> This was a bit before my time, but I was once told a bit about
>> HIL and what parts could be attached to the bus. One is a so
>> called ID module. It is of the size of, well, a pack of cigarettes
>> (more or less).
>>
>> Once attached to the bus, a software can issue calls to see if a
>> certain ID number is there. The cool side is that one could work
>> virtually anywhere, provided you had the module with you.
>>
>> hth,
>> vt
>>
>> *********************
>> Hi
>> >From http://groups.google.com/groups?q=/dev/hil1&start=10&hl=en&lr
>> =&ie=UTF-8&selm=1080029%40hpfcmr.HP.COM&rnum=12
>>
>> By searching Google on "Groups" - more info than this available
>>
>> Windows/9000 expects a locator device, such as an HP-HIL mouse, to be
>> specified by the device file /dev/locator (by default). This device file
>> needs to be a character device file with the HP-HIL major number (24);
>> the minor number refers to the "address" of the device.
>> HP-HIL (HP Human Interface Link) is a proprietary interface which allows up
>> to seven devices to be connected. At boot time each connected device is
>> automatically given an address from 1 to 7. The device closest to the SPU
>> is address one. Passive devices (such as the 46081A Extender) do not
>> consume
>> an address. Some devices consume more than one (the knob box takes three).
>> A standard HP-UX installation will provide device files for all possible
>> HIL devices (/dev/hil1 through /dev/hil7). The recommended way
>> to get a correct device file for /dev/locator is to link the appropriate
>> hil[1234567] device file to /dev/locator. For example, if you have
>> a security module (HP46084A), a keyboard, and then the mouse,
>> # ln /dev/hil3 /dev/locator (as superuser)
>>
>> Regards
>> Jim McDonald
>> *************************
>>
>>
>> Hi Mark,
>>
>> ME10 did use a "dongle" like box, which was connected to the HIL bus,
>> together with mouse and keyboard. Mouse and keyboard were #0 and #2,
>> IIRC, so #1 could easily have been the "dongle"...
>>
>> Don't remember wether "ioscan" was available under HP-UX9.x, but give
>> it a try, anyway.
>>
>> HIL used two different connections, in and out. Check for the labels/symbols
>> on the cabels and the jacks (one dot and two dots).
>>
>> FWIW,
>> Wodisch
>> **************************
>> Hi -
>>
>> HIL - Human Interface Loop - think USB, but years earlier. Connected,
>> keyboards, mice, tablets, and ID modules - the latter being small boxes
>> roughly the size of a soft cigarette pack that would contain a unique ID
>> that licensing software could use.
>>
>> rick jones
>> ***********************
>> The /dev/hil1 refers to the HIL, human interface loop, that the 715 and
>> many other older HP workstations in the 300 and 700 series used.
>>
>> There will be one connector on the back of the unit that the keyboard
>> plugs into. That is the HIL I/F. Typical workstations would have a
>> keyboard and a mouse daisy chained. Other devices such as track balls,
>> tablets and ID modules could be attached.
>>
>> I know nothing about ME other than it's a CAD package. By default, the
>> /dev/hil1 device for ME was set as the ID module. I think that the
>> license may have been tied to the ID module. So if it is looking for the
>> ID module at position one, either it's missing, it's in the wrong
>> position, or it's bad.
>>
>> CPU ------ ID_module ----- keyboard ------ mouse (normally last device)
>>
>> The ID module is a small box the color of the workstation. About 1 inch
>> thick and then (very roughly) 2.5 or so by 3 inches on the sides. It has
>> two connectors, one to the keyboard and one to the CPU.
>>
>> Also, you may notice the "." and the ".." on the cables/connectors. Make
>> sure that you line these up correctly. The "." to the "." and the ".."
>> to the "..".
>>
>> ryan green
>> ***************************
>> Dear Mark,
>>
>> This is a old type of keyboard and mouse device.IT is called Human
>> Interface Line or some thing of that sort.
>>
>> regards
>> JS
>> ***************************
>> Mark,
>> We've been running ME10 here for a dozen years. The license server now runs on the
>> L2000 (from a serial dongle),
>> but at one time the dongle attached to the HIL chain. HIL was HP's proprietary bus
>> that they used to daisy chain the
>> keyboard, mouse, and other devices (like the ME10 license module). If you find the
>> module, make sure you make it
>> the first device in the chain (if the wires go from the 715 to the module to the
>> keyboard to the mouse, the module
>> is /dev/hil1, keyboard is /dev/hil2, etc...)
>>
>> Good luck
>> Kevin
>> *****************************
>>
>> Mark,
>>
>> Kevin Davisson offers sound advice in his reply (below). Some additional
>> thoughts that may be helpful to someone new to MEls:
>>
>> 1. Hewlett-Packard's HIL acronym stands for Human Interface Link.
>>
>> 2. HP is no longer in the mechanical CAD business. The 2D ME10 and its
>> sister 3D solid modeling apps are sold and supported by CoCreate Software
>> Inc., www.cocreate.com <http://www.cocreate.com> .
>>
>> 3. The complete command to start the ME License Server is "MEls -d /dev/hil1
>> -c /etc/MEls.conf". The "d" signifies "device", and the "c" signifies
>> "configuration file". MEls.conf is the text file that contains all of your
>> HP/CoCreate license codes.
>>
>> 4. It's essential that the HIL (/dev/hil1) device connected to your 715 be
>> the one that was used to register the license codes found in MEls.conf. If a
>> different HIL device is connected the licenses will not start.
>>
>> 5. The CoCreate user community has a website that is an excellent source of
>> free information. It includes forums on which you can post questions.
>> www.cocreateusers.org <http://www.cocreateusers.org> .
>>
>> 6. Attached is a copy of a recent MEls manual.
>>
>> Best regards,
>>
>> Marc Godbout
>> MCAD System Manager
>> *********************************
>>
>> Mark,
>>
>> What it is looking for is a HP-HIL ID Module they are usually numbered like
>> this 46084A xxxxXxxxxx. The /dev/hil device is a little box that is linked through
>> the
>> keyboard. This is used to link the ME10 licenses to a machine. That machine is used
>> as a license server for the ME10 licenses. The newer licenses are tied to a lan cards
>>
>> MAC address. They can still be tied to a security device but usually its tied to a MAC
>> address.
>>
>> If I can be of more help let me know.
>> Roger McNulty - Applications Analyst
>>
>
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:26 EDT