HP-71 Compu-LS module

[Dave Frederickson]

(03-26-2017 11:51 AM)twa14 Wrote:  I see that you are using a COMPU.TXT file and not a COMPU.DAT File.

What is COMPU.DAT?

It's important to keep track of and to define the various file types. .DAT is the file type found is the LIF disc archives. The SWAP archive contains LIF files that have been extracted from the disc archives. The tool that extracted the files leaves the 32-byte LIF file header prepended to the data and file extensions have been defined for those file types:
http://ftp.ftp.hpmuseum.org/lif/swap/0readme
However, the tool converted the LIF1 text files to DOS text files and removed the file header, so the *.t71 files are really DOS text, as if it wasn't confusing enough.

Is COMPU.DAT the LIF disc image you created using HPDir? That's how I started. Notice I copied the file into the 71 from :2, the first emulated mass storage device.

Dave

[rprosperi]

(03-26-2017 11:51 AM)twa14 Wrote:  Its working !!!, I followed Bob's advice in his email to me. I did get an "error syntax" following the transform but the basic program is in EMU71\win memory. I have no idea what I did wrong the first and second times. Anyway thanks again to both of you for all your help. The text file is 46848 bytes and the Basic file 32670 bytes

Great news, glad it's working.

Did you make some changes to the program? I ask because your resulting program size is slightly different than what Dave and I both got, and I'd expect the BASIC file to be the exact same if there were no changes, even though the '71 Text file size could vary as explained earlier.

[twa14]

Dave\Bob

I made no changes so its still a bit of a mystery, I am going to go back over the whole process from the beginning to put together a NOOBS method for using the PIL-BOX. I still have to make the COMPU_LS examples scan, you will get it next week

Dave asked what COMPU.DAT file was, that was the file produced by the alihdr32 program

[floppy]

(03-23-2017 12:32 AM)Christoph Giesselink Wrote:  Execute "ALIFHDR FOO.TXT FOO.DAT /T". This converts the ASCII file FOO.TXT into a LIF1 file FOO.DAT.

Is there any linux command for this?

For any reason I cannot reproduce the use of alifhdr with wine.

The file I want to transfer to the HP71B has 43 lines. Perhaps there is a limitation in the number of lines?

in a terminal

env WINEPREFIX="/home/user/.wine" wine-stable C:\\\\windows\\\\command\\\\start.exe /Unix "/home/user/.wine/drive_c/Program Files (x86)/HP-Emulators/alifhdr32/alifhdr.exe" "H:\\programming\hp71b\SNAKE\SNAKE.SRC" "H:\\programming\hp71b\SNAKE\SNAKE.DAT /T"
00a2:err:seh:setup_exception_record stack overflow 816 bytes in thread 00a2 eip 7bc5731e esp 00221000 stack 0x220000-0x221000-0x320000

[Dave Frederickson]

(10-16-2023 01:50 PM)floppy Wrote:  

(03-23-2017 12:32 AM)Christoph Giesselink Wrote:  Execute "ALIFHDR FOO.TXT FOO.DAT /T". This converts the ASCII file FOO.TXT into a LIF1 file FOO.DAT.

Is there any linux command for this?

Joachim's LIFUTILS run under linux.
https://github.com/bug400/lifutils

pyILPER can be used as a "front end" for LIFTUILS which I find very convenient.

[floppy]

+1

Code:

unix2dos -v SNAKE.SRC
unix2dos -v H71B1.SRC

Code:

textlif SNAKE <SNAKE.SRC > SNAKE.lif

Code:

lifput /media/user/ILPERSTO/HDRIVE16.DAT SNAKE.lif

Code:

lifdir /media/user/ILPERSTO/HDRIVE16.DAT

Volume : , formatted : 19/04/23 17:00:00
Tracks: 125 Surfaces: 8 Blocks/Track: 64 Total size: 64000 Blocks, 16384000 Bytes
PERE12 TEXT 768/768 31/05/23 12:58:35
SNAKE TEXT 1792/1792 16/10/23 19:39:54
H71B1 TEXT 768/768 16/10/23 19:40:45
3 files (160 max), last block used: 34 of 64000

looks better. In EMU71 connected with ILPER i see :

>(Basic prompt)

Code:

CAT :HDRIVE1

NAME S TYPE LEN DATE TIME
PERE12 TEXT 768 05/31/23 12:58
SNAKE TEXT 1792 10/16/23 19:39
H71B1 TEXT 768 10/16/23 19:40
(when scrolling with the down key).

Probably it worked: H71B1 is there and was uploaded with

Code:

cat H71B1.SRC | textlif H71B1 | lifput /media/user/ILPERSTO/HDRIVE16.DAT

but I did not scroll with the down key therefore all files were not showned.

[hesc]

Dear all,

I used Christoph's method to transfer a simple basic textfile tsthenk.txt (basic language) into a dat.file tsthenk.dat and imported it into the HP71. The result was indeed a textile tsthenk.text. However, I would like to transfer it into a basic file tsthenk.basic to RUN.
Can someone help me how to do this?

Many thanks,

Henk

[rprosperi]

If the file TSTHENK is a text file on the 71B, and it is correct 71B syntax, this command will change it into a normal BASIC file.

TRANSFORM TSTHENK INTO BASIC

Could not be simpler...

[hesc]

Dear Bob,

Thank you for your suggestion. However, it does not seem that simple to me:
When I execute TRANSFORM TSTHENK INTO BASIC I get an error: Excess Chars Execution of TRANSFORM TSTHENK.TEXT INTO BASIC gives an error: HPIL error Device not found (???)
Do you have an idea?

Thanks,
Henk

[rprosperi]

You cannot use a file type 'extension' as in FILE.EXT. The 71B filename encodes the file type in some bits that are not directly accessible to the user to change. When you specify "TSTHENK.TEXT", the 71B is interpreting the ".TEXT" portion as meaning a mass storage device, hence the confusing error message about HP-IL.

If you do a CAT on file TSTHENK, what file type does it show, it should be TEXT.

Do you know if the syntax of the Basic program is fully compatible with 71B BASIC? The "Excess characters" error could be because of incompatible commands?

Also, do you know what the line terminating characters of your source text file are?
CR-LF pair?
LF only?
CR only?

[hesc]

Dear Bob,

Thanks for the reply.
It is a *.TEXT file.
The file content is:

FOR I=1 TO 10 DO
DISP I;I*I;I*I*I
NEXT I
END

The terminating characters are: CR-LF
What should the terminating characters be?

Kind regards,
Henk

[Dave Frederickson]

Try removing "DO".

" ... it is correct 71B syntax ..."

And you need to add line numbers.

[hesc]

Thank you, Bob and Dave,

The problem was indeed in the syntax. The conversion now works!

Best regards,

Henk

[rprosperi]

Great, glad you have solved the problem and now have a workable process.

And thanks Dave!