71B/EMU71 + 9114B error



#10

I am testing a 9114B post-repair and get the following error after a successful copy of a specific file (MATHROM.LEX):

HPIL ERR:Not LIF Format
Once I get this error I cannot read the disk again until I power cycle the drive or initialize the diskette.

I am using EMU71 with an HP-IL ISA adapter and a 9114B.

Session:

>INITIALIZE :HP9114B
>COPY MATHROM:HDRIVE2 TO :HP9114B (:HDRIVE2 = lexfl1.lif)
>COPY JPCLEX:HDRIVE2 TO :HP9114B (:HDRIVE2 = lexfl1.lif)
>COPY WB71:HDRIVE2 TO :HP9114B (:HDRIVE2 = lexfl1.lif)
>COPY NIBBLEX:HDRIVE2 TO :HP9114B (:HDRIVE2 = lexfl1.lif)
>COPY LEXOFF:HDRIVE2 TO :HP9114B (:HDRIVE2 = lexfl1.lif)
>CAT :HP9114B

NAME S TYPE LEN DATE TIME
MATHROM LEX 32745 05/02/07 00:56
JPCLEX LEX 11173 05/02/07 01:00
WB71 ROM 32768 05/02/07 01:04
NIBBLEX LEX 329 05/02/07 01:05
LEXOFF LEX 152 05/02/07 01:05

>INITIALIZE :HDRIVE1
>COPY JPCLEX:HP9114B TO :HDRIVE1
>COPY WB71:HP9114B TO :HDRIVE1
>COPY NIBBLEX:HP9114B TO :HDRIVE1
>COPY LEXOFF:HP9114B TO :HDRIVE1
>COPY MATHROM:HP9114B TO :HDRIVE1

HPIL ERR:Not LIF Format (huh?)

>CAT :HDRIVE1 (file did get copied. I verified with lifget/md5sum, all bits are there)

NAME S TYPE LEN DATE TIME
JPCLEX LEX 11173 05/02/07 01:07
WB71 ROM 32768 05/02/07 01:08
NIBBLEX LEX 329 05/02/07 01:09
LEXOFF LEX 152 05/02/07 01:09
MATHROM LEX 32745 05/02/07 01:09

>CAT :HP9114B (cannot read drive)

HPIL ERR:Not LIF Format

Power cycle or initialize and all is well again.

What is special about MATHROM.LEX?

Could this be isolated to EMU71?

Is there any other way to reset the 9114B remotely?

Thanks.


#11

Quote:
Is there any other way to reset the 9114B remotely?

There are several things you can try. Here's what I can think of, in no particular order.

  • If flag -21 is clear (the default) a real 71 attempts to power off all devices on the loop when it is powered off itself. I assume the equivalent operation would be to stop and restart EMU71.

  • You could try RESTORE IO, which will readdress the loop, and reset talker/listener status for all devices.

  • CLEAR :HP9114B might work. That is supposed to reset the internal state of the addressed device, without touching its interface, i.e. not doing anything RESTORE IO does.

  • In case the problem is with EMU71's HPIL state, you can RESET HPIL/RESTORE IO. RESET HPIL does a cold boot and self test of the HP-IL interface. RESTORE IO will recall the PRINTER IS and DISPLAY IS devices, in addition to readdressing the loop. The readdressing will happen before the next I/O operation in any case.

  • Finally, you might look up what the HP/IL message sequence is for power down, and send that to the drive. This might work better if you were programming this stuff, instead of sitting with EMU71 or a real 71 in front of you.
That is mighty weird about MATHROM.LEX. I assume you get that result no matter in what sequence you copy the files back from the 9114?

Regards,

Howard


#12

Quote:
That is mighty weird about MATHROM.LEX. I assume you get that result no matter in what sequence you copy the files back from the 9114?

Order does not matter. Tried multiple disks as well.
#13

Hi Egan,

Strange. I tried the same procedure using Emu71 and the 2 internal drives, without errros.

It would be interesting to know if this behavior happens using a real HP-71B as controller, doing "CONTROL OFF" on Emu71 side.

I can't do it by myself, my HP9114 battery is out of order, and it's a HP9114A version with a probably older firmware version.

I'm not sure CLEAR :HP9114 can reset the fault condition. Maybe ejecting and inserting the floppy disc again can fix it, just it can't be done remotely...

J-F


Edited: 28 May 2007, 7:26 a.m.


#14

Quote:
I'm not sure CLEAR :HP9114 can reset the fault condition. Maybe ejecting and inserting the floppy disc again can fix it, just it can't be done remotely...

Power cycle only, or re init the diskette.
#15

More info. I repaired another two 9114Bs. Neither unit exhibits the same behavior.


#16

Interesting. I wonder if the firmware levels differ. I have no idea how you could tell.

Regards,
Howard

#17

Update. I swaped system boards. The problem follows the drive. I cleaned it and the problem went away. Well sort of...

I cannot reproduce the problem with a 71B, only with EMU71. EMU71 will read it once without error, the 2nd read of only MATHROM (no other file) yeilds a "New Medium" error after the copy. The copies are complete.

Edited: 28 May 2007, 2:39 p.m.


#18

Huh.

Assuming there are no firmware bits outside the main board, then there must be a physical flaw/quirk that copying the MATHROM sets up. It's probably independent of head position, unless the file ends up in the same sectors each time. So it has to be in the electromagnetic state of the system. That seems bizarre, but I can't think of another angle. The particular bit patterns in the deadly file must set up magnetic flux that jiggers the read mechanism somehow.

Anyone have a less UFO-like explanation?

Regards,
Howard


Possibly Related Threads...
Thread Author Replies Views Last Post
  How to copy files from 9114B to hard drive via PIL-box? Joe Horn 23 6,757 12-14-2013, 11:57 PM
Last Post: Geoff Quickfall
  MS advert shows spreadsheet with obvious error BruceH 3 1,477 11-14-2013, 09:50 AM
Last Post: Bill (Smithville, NJ)
  HP Prime: Rounding error in determinant Stephan Matthys 3 1,114 10-25-2013, 09:29 PM
Last Post: Walter B
  Prime Error or Mine? toml_12953 12 2,446 10-22-2013, 10:35 AM
Last Post: toml_12953
  Explaination on How to Reset Caculator in Users guie: error Harold A Climer 5 1,684 10-15-2013, 02:11 AM
Last Post: cyrille de Brébisson
  Repair of HP-34C - Error 0 and Error 9 Jeff Kearns 3 1,176 10-11-2013, 12:29 PM
Last Post: Randy
  Update of Emu71 to v1.05 Christoph Giesselink 0 684 09-24-2013, 04:22 PM
Last Post: Christoph Giesselink
  Do You Think a Listing Error Was Made? Jim Johnson 13 2,682 09-04-2013, 09:23 AM
Last Post: Eddie W. Shore
  HP Prime: Error reports : Here Patrice 111 14,239 07-24-2013, 05:52 PM
Last Post: Thomas Klemm
  EMU71 on a web page! hugh steers 13 2,678 07-14-2013, 12:47 PM
Last Post: Namir

Forum Jump: