Long last wanted: XEQ_Auto-Complete finally done
|
05-10-2017, 05:42 AM
Post: #21
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
Hi Angel
This “XEQ+” function is really fantastic...! Thank you for that. Perhaps one option? While browsing back through the functions with SHIFT + SST (->BST) It would be nice, when the SHIFT stays on (like in the CCD CAT functions…) Great “MCODE” work! Best regards Tobie |
|||
05-10-2017, 07:08 AM
Post: #22
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(05-10-2017 05:42 AM)charger73 Wrote: Perhaps one option? While browsing back through the functions with Greetings Tobie. I didn't leave SHIFT on due to a lack of space but the functionality is there: did you notice the TAN key also acts like a BST? It's the same approach used in the HEPAX' HEXEDIT. Best, ÁM "To live or die by your own sword one must first learn to wield it aptly." |
|||
05-10-2017, 10:39 AM
Post: #23
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
Oh - yes the [TAN] key is ok - of course :-)
Thank you |
|||
05-12-2017, 05:13 AM
Post: #24
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(05-08-2017 02:42 PM)rprosperi Wrote: [quote='Michael Fehlhammer' pid='73047' dateline='1494247974']It is up to date, being a 2015 publication. Yet I find it to be 'NEWs' in brief, I believe lists in brief with the colour graphic image-work used, are the way to get the point over. The lack of detail is my gripe, paragraph info' would guide the wobbly-knee programmer to much more certain results. Instead of the [REQUIRED] 'spend hours looking into minutia details' problem inherent in this kind of programming, the success rate would be nearer 0% errors, with just that extra mile of helpful, well thought out guidance. Don't forget that once Angel as a resource ends forum membership all will be lost. Along with future program development from such choice methods as: 'LASTFunction, Auxiliary FAT, auto-complete, shadow stack buffer for UNDO', etc. These added into most programs/ROMs could revolutionize them. DA. |
|||
05-12-2017, 06:41 PM
Post: #25
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
The details are in the source code. Luckily we have a decent amount of that for the HP-41, though not everything.
If you want to do get into MCODE programming, start with the Ken Emery's book, it is good. After that you need to read the source code, there is no way around it (an advanced book would not save you from it). You will learn a lot from studying the VASM listings, it is a very well written code base. Add the internal hardware documentation and various other documents and you should be able to find most (if not all) of what you are looking for. Lack of books and tools did not stop people in the past. Later we got the book, and today we have better hardware support (way more powerful host computers, MLDL2000, Clonix and NEWT) and better tools. We can even communicate over the globe in no time, think about how it was in the eighties. It has never been easier to enter and do MCODE programming than it is today. Håkan |
|||
05-13-2017, 01:42 AM
Post: #26
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done | |||
05-13-2017, 07:40 AM
Post: #27
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(05-13-2017 01:42 AM)RobertM Wrote:(05-12-2017 06:41 PM)hth Wrote: You will learn a lot from studying the VASM listings, it is a very well written code base. If they do I've never seen them - it'll be great to read about the implementation by their creators. I'm guessing HP never took the time to document it in the same way as the original OS - which is a shame, there are a few dark corners in that code that I for one would love some clarification about. "To live or die by your own sword one must first learn to wield it aptly." |
|||
07-03-2017, 01:27 PM
Post: #28
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
Hello Angel,
While I am waiting for 41CL update tests to finish, I am taking this free time to learn your new/updated modules. I took an updated 41CL (rom_files.zip 2017-06-28) and mapped the Toltal_Rekall "Warp_Core" edition. CLv4 setup : MMUDIS MMUCLR "YFNX" PLUGH MMUEN "4LIB 4" PPLUG "WARP 8" PPLUG First thing I have tried was: XEQ "XEQ+" and the answer was NONEXISTENT ? Then I did a CAT 2, then digging into "-WARP CORE2" entry, I see XEQ" (XEQ double-quotes) and not XEQ+ Is this normal? Do I have to use a different Library#4 ? Sylvain Reference: mem_ref.pdf (2017-06-28) Code: 0x120 LIBRARY4 4LIB -- Library-4 0xBF465233 05/16/17 |
|||
07-03-2017, 02:05 PM
Post: #29
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(07-03-2017 01:27 PM)Sylvain Cote Wrote: Hello Angel, Excellent way to spend that free time ! ;-) (07-03-2017 01:27 PM)Sylvain Cote Wrote: I took an updated 41CL (rom_files.zip 2017-06-28) and mapped the Toltal_Rekall "Warp_Core" edition. Sorry for the confusion. The function name is 'XEQ"', with double quotes and not a plus sign. I'm not sure this last-minute change made it to the manual or not, but that's the final name given to the function. You can or course change that to "XEQ+" if you prefer. It's actually a good idea to make the name spell-able - currently you need to use the ASSIGN or EXECUTE hot-keys within the OS/X module Catalog-2 to get it assigned or executed, not very user-friendly I admit it. I think I'll change the name back to XEQ+ in the next revision. Best, ÁM "To live or die by your own sword one must first learn to wield it aptly." |
|||
07-03-2017, 02:31 PM
(This post was last modified: 07-03-2017 02:38 PM by Sylvain Cote.)
Post: #30
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(07-03-2017 02:05 PM)Ángel Martin Wrote: Sorry for the confusion. The function name is 'XEQ"', with double quotes and not a plus sign. I'm not sure this last-minute change made it to the manual or not, but that's the final name given to the function.No problem, in the June 6, 2017 manual it is written as XEQ+ (07-03-2017 02:05 PM)Ángel Martin Wrote: You can or course change that to "XEQ+" if you prefer. It's actually a good idea to make the name spell-able - currently you need to use the ASSIGN or EXECUTE hot-keys within the OS/X module Catalog-2 to get it assigned or executed, not very user-friendly I admit it.You can also do it this way: "XEQ" 34 XTOA KeyCode PASN (07-03-2017 02:05 PM)Ángel Martin Wrote: I think I'll change the name back to XEQ+ in the next revision.IMHO I like it better as XEQ+ then as XEQ" Thanks! Best regards, Sylvain edit: typo |
|||
07-03-2017, 02:52 PM
Post: #31
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
Hi
Two question. 1. Is the XEQ+ in this rom, the same as you have added in the AMC OSX module? 2. How to load the DTCOMPARE.ROM in the go41cx? It seems to accept only mod files. Renaming .rom to .mod, did not help |
|||
07-03-2017, 03:37 PM
Post: #32
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(07-03-2017 02:52 PM)Jotne Wrote: Hi A simple rename won't do, you have to change format. You can use MODMakeWin.zip by Warren Furlow at TOS. (Please don't ask what TOS stands for... ;) ) Greetings, Massimo -+×÷ ↔ left is right and right is wrong |
|||
07-03-2017, 05:43 PM
(This post was last modified: 07-03-2017 05:43 PM by Ángel Martin.)
Post: #33
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(07-03-2017 02:52 PM)Jotne Wrote: 1. Is the XEQ+ in this rom, the same as you have added in the AMC OSX module? There's no "XEQ+" function in the AMC_OS/X module. It's only available in the Warp_Core. You need to use MOD files. I have attached to this post a zip with both MOD files, plus the latest Library#4 just to be extra sure. I have no idea how to install those on g041CX, sorry. "To live or die by your own sword one must first learn to wield it aptly." |
|||
07-03-2017, 06:22 PM
Post: #34
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
Thanks, found it at the org site.
|
|||
07-03-2017, 06:46 PM
Post: #35
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
Hello Ángel,
Me again I am playing with multiple setup involving: LIB4 R44 (4LIB), AMC OS/X (OSX3), HP-16C (16CS) & Total Rekall (WARP) In one of the simple test setup I have: 4LIB@4, YFNX@7 & OSX3@8 CAT 2 shows the modules entries, BFCAT & PGCAT works, so the module is seen and it can execute functions But when I do a "CAT _ " do not see the ' of the famous CCD extended "CAT' _", why ? Best, Sylvain Code: 0x00A YFNX-2C YFNX 15 41CL Extreme Functions -2C 0x99BDA28B 06/19/17 |
|||
07-03-2017, 06:52 PM
Post: #36
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(07-03-2017 06:46 PM)Sylvain Cote Wrote: In one of the simple test setup I have: 4LIB@4, YFNX@7 & OSX3@8 I have a similar config, but with YFNX in page 9 and it works fine. Try that if not too big a deal to move ROMs around. No idea if this helps or why, just sayin... --Bob Prosperi |
|||
07-03-2017, 08:27 PM
Post: #37
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(07-03-2017 06:52 PM)rprosperi Wrote: I have a similar config, but with YFNX in page 9 and it works fine. Try that if not too big a deal to move ROMs around. No idea if this helps or why, just sayin... Yep, that did it, I was sure that I tried it before posting, but to evidence I did not. I have not looked at the assembly code, but for some reason, YFNX is not passing along some of the polling point to OSX. Thanks! Sylvain |
|||
07-03-2017, 08:27 PM
Post: #38
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(07-03-2017 06:46 PM)Sylvain Cote Wrote: Hello Ángel, Hi Sylvain, this is a known issue and has to do with the polling points. To get it to work properly the OS/X module needs to be in an "earlier" position (i.e. lower page#) in the ROM bus than the YFNX (or YFNZ for that matter. Try either swapping their positions, or plugging the OS/X in pages #6 or #7 (assuming no HP-IL is needed, which i guess won't work for you). Cheers, ÁM "To live or die by your own sword one must first learn to wield it aptly." |
|||
07-03-2017, 08:34 PM
Post: #39
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
(07-03-2017 08:27 PM)Ángel Martin Wrote: Hi Sylvain, this is a known issue and has to do with the polling points. To get it to work properly the OS/X module needs to be in an "earlier" position (i.e. lower page#) in the ROM bus than the YFNX (or YFNZ for that matter. Try either swapping their positions, or plugging the OS/X in pages #6 or #7 (assuming no HP-IL is needed, which i guess won't work for you). Simultaneous posting This confirm what I was suspecting, moving YFNX from page 7 to 9 worked, thanks! Regards, Sylvain |
|||
07-23-2017, 12:59 AM
Post: #40
|
|||
|
|||
RE: Long last wanted: XEQ_Auto-Complete finally done
Hello Angel,
I am back to studying the Warp_Core module and I am seeing strange things. I am using a 41CL v4 updated to 2017-06-28 rom_files.zip & setup is: Code: Page:4 Bank:0 -> 0x120 LIBRARY4 4LIB -- Library-4 0xBF465233 05/16/17 First if I try to execute "Y<>" ST Z directly while the stack contains: X=5, Y=6, Z=7 & T=8 the result I have is X=5, Y=NNN, Z=6 & T=8 (NNN = Not Normalized Number or something similar to) My first reaction would be to think that I have a mismatched LIB4 but all rom images came with the rom_files.zip and the dates match. so I assume that they are compatible. Then if I try to call the "Y<>" function from XEQ"function [XEQ"] display {XEQ" A:Z} press [Y] display {XEQ" YRES} press [SST] display {XEQ" Y<>} press [XEQ] display {NONEXISTENT} (same things for all WARP functions) This seems like XEQ" is executing code from page 9 bank 1 and trying to call something in page 9 bank 0 without going to bank 0 before doing the call. Sylvain |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)