HP-41: Has anyone used the Laitram rom?



#15

If so, what do you think about this takeover rom?


#16

Hi, Geir;

right after building the MLDL2000 and adding a NoVRAM and a NoV32 to the 'troup', I had the change to get to know about the so many modules that existed for the HP41. I can tell I am one of the 'newest' users of these extensions amongst the 'older' worshipers of the HP41 system, though...

About the Laitran: I read about it, took a look at the manual but I was actually a lot interested on HEPAX, CCD-family, AECROM, FORTH ROM, Advantage, amongst some others. I must confess I never give it a try because it seemed to me that the proposed functionality was not something I was seeking for.

I'll get closer to it and let you know.

Cheers.

Luiz (Brazil)


#17

I actually got one on eBay (at a very affordable price) and sold it later on - that should give you an indication of my appreciation for it... all that ado for nothing much, in my opinion.

#18

Yes, I have one buried away in a box along with its special touchpad overlay. In my estimation it was a solution in search of a problem.

J.M. LaPeyre (I think that's the spelling) made his fortune in shrimp processing (Bubba Gump?) and a special staggered tread industrial stair/ladder (called the LaPeyre Stair), and he hired Dave Conklin and co. for the project. J.M. himself demonstrated the product at the 1985 users conference in Atlanta, and if memory serves Dave was there.


#19

Can someone explain, in a few words, what this ROM is about?


#20

AFAIR all possible functions are accessible with a few key strokes.

HTH

Raymond


#21

Correct. It's a takeover rom where 16 keys are active and with combinations of keys, all HP-41 functions are available with very few keystrokes (2?).


#22

... Sinclair´s keyboard conception. If the idea was to reduce keystrokes while entering (large) programs, maybe it is a solution. I´m addicted to [XEQ][ALPHA] spell [ALPHA] or the [USER] shortcut, though.

Luiz (Brazil)

Edited: 14 Jan 2010, 2:37 p.m.


#23

Quote:
... Sinclair´s keyboard conception. If the idea was to reduce keystrokes while entering (large) programs, maybe it is a solution. I´m addicted to [XEQ][ALPHA] spell [ALPHA] or the [USER] shortcut, though.
Maybe one of you MCODE experts could write something that allows multiple KEYS files, so USER keyboards could be swapped out quickly like on the 71. Without it, I think you would have to run a program with lots of PASN's and it would be slow and take more memory. I haven't reviewed this recently so I may be forgetting something.

#24

Hi, garth;

Ángel´s first 4K 41Z had a programmable, complex-addressed USER keyboard through a single MCODE function. Anyway, any pair of consecutive USER assignment (or after packing the existing ones) will ocupy a main RAM register, as we know.

For me, the best cost-benefit relation is the use of sofkeys (HP19, HP28, HP42S, HP48-series and so), and in some applications, like the ones in the HP41 Advantage Pack, such feature is simulated (not the softkeys themselves, something close to). The HP32S also takes advantage of the ALPHA keyboard with the addition of the small arrows pointing to the active keys.

The main issue of the USER keyboard is to remember what is assigned to which key, and I believe the [NULL] feature in the HP41 was one of the solutions to help the user to 'check before using' a particular key in user mode. If we have a set of USER keyboards, I guess the user would have to retain more information, though.

Please, these are just my own considerations about the subject. I neither have an answer, nor a solution to propose, but I really would like to have another possibility for the multiple user defined keyboards.

Cheers.

Luiz (Brazil)


#25

Right. When I program FOCAL I do as the Advantage module (this I advice in the FOCAL coding standard).

The Laitram keyboard overlay is some crazy piece of thingymawiz

#26

Quote:
Ángel´s first 4K 41Z had a programmable, complex-addressed USER keyboard through a single MCODE function. Anyway, any pair of consecutive USER assignment (or after packing the existing ones) will ocupy a main RAM register, as we know.
I am looking forward to using 41Z after I get one of the modules that can hold such images. But as for the RAM space taken by key assignments, I'm thinking of KEYS files in extended memory or one of the newer plug-in modules with more RAM file space. Then only the active assignments take any of main RAM.

Quote:
For me, the best cost-benefit relation is the use of sofkeys (HP19, HP28, HP42S, HP48-series and so), and in some applications, like the ones in the HP41 Advantage Pack, such feature is simulated (not the softkeys themselves, something close to). The HP32S also takes advantage of the ALPHA keyboard with the addition of the small arrows pointing to the active keys.
I do this on the 41 with local alpha labels as well as with GEYKEY and GEYKEYX. Useful functions, although not the same thing.

Quote:
The main issue of the USER keyboard is to remember what is assigned to which key, and I believe the [NULL] feature in the HP41 was one of the solutions to help the user to 'check before using' a particular key in user mode. If we have a set of USER keyboards, I guess the user would have to retain more information, though.
For this reason, I frequently change key overlays on the 71. I only have one for the 41 that I could write on (I should have bought a bunch when they were available), plus the special-use ones that came with the 41 and its modules. The guide for the text editor is on the back.

Edited: 15 Jan 2010, 2:21 a.m.

#27

Both the 41Z and the SandMath modules have their own "USER function files" - very comparable to Garth's example with the 71B.

On the 41Z (either 4k or 8k version) it's called ZKEYS; on the SandMath it's called MHKEYS. Either one will remap the User keyboard to a pre-assigned function set, pertinent to the module in question.

As much as this is a good approach, I find this technique a little taxing on the user: because there are that many functions, there's a lot of toggling the USER mode on and off to also access the native 41C functions (or else lot of XEQ-Spelling). It also uses up a chunk of main memory with the key assignments "buffer" .

That's why I wrote the Complex Keyboard function (ZKBRD) on the 41Z (8k version). It provides access to many more functions than available on the basic layout, it does NOT conflict with the native or the user assignments, and it doesn't take any memory register. A charm, if you ask me. The cost of course is a lot of programming behind the scenes to make it happen.

Take it for a spin and you'll see what I mean.

Cheers,
"AM

#28

Sounds rather like the eG0BEEP functions.


Possibly Related Threads...
Thread Author Replies Views Last Post
  HP-41(CL): The easiest way to transfer FOCAL programs from a Linux PC to the HP-41 Geir Isene 13 1,125 12-05-2013, 02:40 AM
Last Post: Hans Brueggemann
  HP85 Programmable ROM cardtridge 82929A-service ROM not working- inaki 2 370 04-25-2013, 08:08 AM
Last Post: inaki
  HP71B to HP 41 Translator ROM Manual Michael Lopez 5 427 04-25-2013, 03:51 AM
Last Post: Mike (Stgt)
  HP-41 ROM Polling Point at FF5 Dan Grelinger 2 267 01-11-2013, 06:00 PM
Last Post: Monte Dalrymple
  shelf life time of a ROM, EEPROM, EPROM vs Mask Rom Guido (Canada) 6 536 01-11-2013, 04:09 PM
Last Post: Thomas Falk
  Big ROM - 41 System DEMO ROM Ángel Martin 5 520 10-16-2012, 05:28 AM
Last Post: Ángel Martin
  HP-41 takeover ROM with Clonix-D Sylvain Cote 1 228 10-15-2012, 02:37 PM
Last Post: Diego Diaz
  New 41 model to use rom of "big" program Olivier De Smet 4 341 10-03-2012, 07:35 PM
Last Post: Brian Walsh
  HP-41 Quiz: How to pack 100k in ROM? (on-line) Ángel Martin 10 651 09-02-2012, 10:35 PM
Last Post: Luiz C. Vieira (Brazil)
  HP 41 CL ROM List Gerry Schultz 2 223 05-23-2012, 12:51 AM
Last Post: Ángel Martin

Forum Jump: