HDRIVE1.DAT from ilper/giesselink not readable in pyILPER

82160A

HDRIVE1.DAT from ilper/giesselink not readable in pyILPER

Postby floppy_stuttgart » Sun Feb 06, 2022 6:13 pm

Hello,
I have a file HDRIVE1.DAT from ilper here https://hp.giesselink.com/hpil.htm (on a raspberry pi4, ARM, 32bits, ext4 file system, ilper started in a box86&wine environment) and it is not readable from pyILPER (in a Debian 11, x86 64bits, ext4 file system).
Same in the other direction: I have a file I created few months ago and used with pyILPER and it cannot be read with ilper (I cannot remember where the original HDRIVE1.DAT used with pyILPER came from; I can only remember the first try with an HDRIVE1.DAT was not successfull and I had to find a working one).
It means for me, I cannot put the HDRIVE1.DAT on an usb stick and use it whatever on PC 32/64bits or ARM board for communicating via pilbox to the HP41.
Has anybody experienced incompatibilities of HDRIVE1.DAT between ilper under windows and pyilper under MacOS/Linux/Windows?
floppy_stuttgart
.........
.........
 
Posts: 99
Joined: Mon Mar 29, 2021 2:36 pm

Re: HDRIVE1.DAT from ilper/giesselink not readable in pyILPE

Postby jeffcalc » Sun Feb 13, 2022 9:31 am

I'm not a raspberry/Linux/Mac user and rarely used pyILPer but if you can post a HDRIVE1.DAT disc image that can't be read in ILPer then we could have a look and maybe give some indications.

J-F
User avatar
jeffcalc
......
......
 
Posts: 25
Joined: Fri Aug 28, 2009 8:57 pm

Re: HDRIVE1.DAT from ilper/giesselink not readable in pyILPE

Postby floppy_stuttgart » Sun Feb 13, 2022 4:38 pm

File was sent via mail since the .DAT extension cannot be uploaded here.
floppy_stuttgart
.........
.........
 
Posts: 99
Joined: Mon Mar 29, 2021 2:36 pm

Re: HDRIVE1.DAT from ilper/giesselink not readable in pyILPE

Postby floppy_stuttgart » Sat Feb 19, 2022 1:56 pm

As per J-F suggestion, I created/formatted a new HRIVE1.DAT with the HP41 connected to a virtual drive HDRIVE1.DAT by pilbix/pyilper by giving "XEQ NEWM" then "447" as per requested entry.
For now, I have 2 files HRIVE1.DAT and HDRIVE3.DAT. Is there any possibility to move program files from HDRIVE3.DAT into HDRIVE1.DAT by command line or other?
Loading files into the HP41 from HDRIVE3.DAT then moving into the HDRIVE1.DAT with pyilper/pilbox is well known but perhaps a quicker solution with hpdir or other exists?
Then with the new formatted refilled file, I will further dig into my original issue.
floppy_stuttgart
.........
.........
 
Posts: 99
Joined: Mon Mar 29, 2021 2:36 pm

Re: HDRIVE1.DAT from ilper/giesselink not readable in pyILPE

Postby jeffcalc » Sun Feb 20, 2022 4:01 pm

floppy_stuttgart wrote:For now, I have 2 files HRIVE1.DAT and HDRIVE3.DAT. Is there any possibility to move program files from HDRIVE3.DAT into HDRIVE1.DAT by command line or other?
Loading files into the HP41 from HDRIVE3.DAT then moving into the HDRIVE1.DAT with pyilper/pilbox is well known but perhaps a quicker solution with hpdir or other exists?

Well, the Extended I/O ROM provides a MCOPY command to copy the whole medium, but it will not help there since it would also duplicate the LIF structure anomalies.
Otherwise, you can write a short program, using other commands from the X-I/O ROM, to do a file per file copy.

Here is the principle;
select source drive with SELECT
set index=1
repeat
{
read the catalog entry number index with DIRX
if the catalog entry is empty, then it's done.
copy that file from source to target drive with COPYFL
index++
}

It seems I already posted such program, can't remember right now where,.

J-F
User avatar
jeffcalc
......
......
 
Posts: 25
Joined: Fri Aug 28, 2009 8:57 pm

Re: HDRIVE1.DAT from ilper/giesselink not readable in pyILPE

Postby floppy_stuttgart » Thu Mar 17, 2022 6:14 pm

Lets come back to the original subject of that thread.
I found out that the lifutils linux 64bits which has to be installed in parallel to pyilper dont list the programs present in the the "giesselink" DAT file =
Code: Select all
/usr/bin/lifdir /home/user/programming/hp41/HDRIVE1.DAT
Volume : , formatted : 10/04/16 09:53:05
Tracks: 125 Surfaces: 8 Blocks/Track: 64 Total size: 64000 Blocks, 16384000 Bytes
0 files (640 max), last block used: 0 of 64000

lifutils came from there https://github.com/bug400/lifutils/rele ... _amd64.deb
I am still searching the reason for non compatibility.
floppy_stuttgart
.........
.........
 
Posts: 99
Joined: Mon Mar 29, 2021 2:36 pm

Re: HDRIVE1.DAT from ilper/giesselink not readable in pyILPE

Postby rprosperi » Thu Mar 17, 2022 8:15 pm

Email me the exact HDRIVE.DAT LIF file you are having trouble with and I verify if the windows version of lifdir will read the file and produce the listing.
rprosperi
.........
.........
 
Posts: 64
Joined: Sat Apr 11, 2015 1:03 pm

Re: HDRIVE1.DAT from ilper/giesselink not readable in pyILPE

Postby floppy_stuttgart » Fri Mar 25, 2022 1:31 pm

The windows and linux lifutils programs from pyilper github can read the content of virtual drive HDRIVEP.DAT created with pyilper (both commands; see below; made on a linux 64bits PC).
In fact, nothing really new, it show only that the GUI pyilper and the command line programs works as it must be.

Code: Select all
wine '/home/user/.wine/drive_c/Program Files (x86)/HP-Emulators/LIFUTILS/lifdir.exe' '/home/user/programming/hp41/HDRIVEP.DAT'

Volume : , formatted : 25/03/22 13:00:00
Tracks: 125 Surfaces: 4 Blocks/Track: 64 Total size: 32000 Blocks, 8192000 Bytes
BATTEST PGM41 50/256
1 files (2000 max), last block used: 252 of 32000

Code: Select all
lifdir '/home/user/programming/hp41/HDRIVEP.DAT'

Volume : , formatted : 25/03/22 13:00:00
Tracks: 125 Surfaces: 4 Blocks/Track: 64 Total size: 32000 Blocks, 8192000 Bytes
BATTEST PGM41 50/256
1 files (2000 max), last block used: 252 of 32000

A virtual DAT file from ilper (Giesselink) cannot be read on a Linux 64bits PC with the lifutils codes from pyilper. Nothing new, just an evidence the command lines work as the GUI. However, no error comes up, just no file is listed.
Code: Select all
lifdir '/home/user/programming/hp41/IIL1.DAT'

Volume : , formatted : 10/04/16 09:53:05
Tracks: 125 Surfaces: 8 Blocks/Track: 64 Total size: 64000 Blocks, 16384000 Bytes
0 files (640 max), last block used: 0 of 64000
Code: Select all
wine '/home/user/.wine/drive_c/Program Files (x86)/HP-Emulators/LIFUTILS/lifdir.exe' '/home/user/programming/hp41/IIL1.DAT'

Volume : , formatted : 10/04/16 09:53:05
Tracks: 125 Surfaces: 8 Blocks/Track: 64 Total size: 64000 Blocks, 16384000 Bytes
0 files (640 max), last block used: 0 of 64000

ilper started on the linux64bits pc with
Code: Select all
/usr/bin/wine 'C:\\windows\\command\\start.exe' /unix '/home/user/.wine/drive_c/Program Files (x86)/HP-Emulators/ILPER/ilper.exe'

can read the content of a virtual file from ilper sources which is
NAME TYPE REGS
CHIL1 PR 3
BATTEST PR 7

Summary:
- pyilper and ilper cannot access the same virtual drive on linux64bits
- ilper access to a file created/readable by pyilper show the error "MEDM ERR" on linux64bits (ilper started with "wine")
- since,
a) there is no pyilper for ARM 32/64bits linux (raspberry PI)
b) it is possible to install ilper on raspberry PI raspbian,
it makes ilper the first choice in case only a single virtual drive want to be used (= a virtual drive on a USB storage can be used on a linux64bits and raspberry PI "raspbian" and
connected to a V41 or an HP41 via "ilper")
- = 2 different virtual drives has to be used for linux64 bits (pyilper) and ARM (ilper) raspbian
- windows PCs dont show any issue so far (result of JF and Rob testing)
- travel package; setup in picture
raspberry PI4 "raspbian" with its own 220V connection via USB-C
booting direct in USB3-SSD
Micro SD port is free
USB-Memory attached on USB3 (virtual drive on that memory)
pilbox to an HP41CX (via an USB hub with separated 220V connection because its usual too much USBs connected to a raspberry PI make it functionality unstable)
ilper/V41 seen on a touchscreen
optional USB mouse or USB board (not everyone likes touchscreens which ia accessed via a touchpen)
LAN-Network cable can be connected to the raspberry PI for writing here in that forum
Attachments
IMG_0166(1).JPG
floppy_stuttgart
.........
.........
 
Posts: 99
Joined: Mon Mar 29, 2021 2:36 pm


Return to HP-IL

Who is online

Users browsing this forum: No registered users and 1 guest