Testing QL environment on the Vampire V4 Stand alone

[guibrush]

As ignited in the thread about the Q40 board, I'm doing some testing on the V4 SA (Vampire 4 Stand Alone, it's the complete computer sold by Apollo computers), respectively on the Icedrake (this is an accelerator board for that Amiga 1200 based on the V4 Stand Alone, same hardware) to test the compatibility degree.

What I managed to do:
. install QDOS4Amiga from Aminet. (https://aminet.net/search?query=qdos)
- install the XFS filesystem from Aminet, that is required to read and write QL formatted floppy disk (https://aminet.net/package/disk/misc/xfs)

Basically, the Amiga is capable to handle almost every disk format that fit on a regular 3.5" floppy disk thanks to his versatile floppy controller, the xfs filesystem allow the amiga to understand the floppy disk format of the QL.

- use the transfert program in the QDOS4amiga package to write the content of the support disk on a floppy readable by the QL

- boot the floppy disk

- create a second floppy disk on the Amiga side with some provided commands by xfs

- copy the content of the dhrystone zip file pointed by Peter in the other thread (https://dilwyn.theqlforum.com/benchmrk/index.html)

- list the content of this disk

Now, I try to launch the C68dhrystone program from this disk. I tried lrun flp1_c68dhrystone, but this is not this.

then I tried EXEC flp1_c68dhrystone, it's a no too:

What is the right command to type to execute it?

EDIT: precision on the names added

[Pr0f]

The bad parameter could be because the unzip was not done on the QL side - non QL unzip will kill the all essential lead part of the executable file - and you get the bad parameter error

[guibrush]

this is what I feared. But on the other side, the way used to create the floppy disk is done via a specific program for this purpose. And I can create the boot disk using the same procedure.

[Peter]

Thanks for attempting to test and for opening a specific topic. At first you need the QL-side unzip program itself to have the right executable header.
So this doesn't become a chicken-and-egg problem, here is a self-extracting binary that you can start without executing:
https://dilwyn.theqlforum.com/arch/unzip541xq.bin
You can LRESPR this file and follow the on-screen prompts.

Two side notes:

• Terms like "V4 SA" or "Icedrake" mean nothing to me and probably most QLers. That's no problem for our current test goal, as long as it means "some hardware containing the Apollo68080 FPGA core". However, if we need to know something specific about these, please be a bit more comprehensive.
• Instead of QDOS4amiga, it would be better to use QDOS Classic, because it is still maintained. You can get it here:
  https://dilwyn.theqlforum.com/emu/index.html
  Or from a site where Mark Swift is hosting it. It used to be on "pages.unisonfree.net/mswift/ql/index.html", but that one seems down at the moment.

[Peter]

If you still struggle with the executable headers, but want a first rough speed comparison, you could just do:

LRUN QSBB_BAS

QDOS Classic (or QDOS4Amiga) basically provide the same OS with the same BASIC interpreter code on Q60 and Amiga, so it should be meaningful. At least if the timer runs correctly. Which you can verify by checking if QSBB_BAS takes exactly 1 minute. Under QDOS, the Q60 delivers:

Printing 52320
Functions 106300
Strings 177980

Note: The Q60 does not use the 68060 to it's full potential, since it is an ancient EDO RAM design.

[guibrush]

Thanks for attempting to test and for opening a specific topic. At first you need the QL-side unzip program itself to have the right executable header.
So this doesn't become a chicken-and-egg problem, here is a self-extracting binary that you can start without executing:
https://dilwyn.theqlforum.com/arch/unzip541xq.bin
You can LRESPR this file and follow the on-screen prompts.

Two side notes:

• Terms like "V4 SA" or "Icedrake" mean nothing to me and probably most QLers. That's no problem for our current test goal, as long as it means "some hardware containing the Apollo68080 FPGA core". However, if we need to know something specific about these, please be a bit more comprehensive.
• Instead of QDOS4amiga, it would be better to use QDOS Classic, because it is still maintained. You can get it here:
  https://dilwyn.theqlforum.com/emu/index.html
  Or from a site where Mark Swift is hosting it. It used to be on "pages.unisonfree.net/mswift/ql/index.html", but that one seems down at the moment.

Ok, I give a try to the other emulator and will report back. It make take some days, I'm really busy at work those days.

I precised in my most what the V4 SA is (Vampire 4 Stand Alone). I already precised what the Icedrake is, I did it now a little bit more precise.

As you know, I'm from the Amiga world, so what you say here is basically what I wanted to explain the last time when you gave me words like "LRESPR" or "WSTAT", it's was equally Klingon to me. I'm sure that we can find a way to understand us

[pjw]

<>
Ok, I give a try to the other emulator and will report back. It make take some days, I'm really busy at work those days.

I precised in my most what the V4 SA is (Vampire 4 Stand Alone). I already precised what the Icedrake is, I did it now a little bit more precise.

As you know, I'm from the Amiga world, so what you say here is basically what I wanted to explain the last time when you gave me words like "LRESPR" or "WSTAT", it's was equally Klingon to me. I'm sure that we can find a way to understand us

Since youre on the team you could perhaps suggest to BigGun that to boost its credentials that the 68080 "CPU is the most compatible processor with the whole Motorola 68000 family range.." it must also pass the "QL test". Let him sort it!

While QLers probably wont add much to his sales, there is a market out there for 68k CPUs.

[Mark Swift]

Hi

A little background info on why the QDOS4amiga is able to create the QL boot disk without having issues with QL executables.

Here is an Amiga CLI output from LIST FD0:

Code: Select all

Directory "fd0:" on Sunday 01-Dec-24
CLONE                       1862 ----rw-d 06-Nov-24 16:19:28
------BOOT------            1170 ----rw-d 06-Nov-24 16:19:30
BOOT                        3106 ----rw-d 06-Nov-24 16:19:32
SYSINFO_bas                 1464 ----rw-d 06-Nov-24 16:19:33
-------TK-------            1170 ----rw-d 06-Nov-24 16:19:35
PDTK_readme                 7183 ----rw-d 06-Nov-24 16:19:37
PDTK_rext                   3420 ----rw-d 06-Nov-24 16:19:39
PDTK_asm                   31215 ----rw-d 06-Nov-24 16:19:45
QDOS_inc                   41479 ----rw-d 06-Nov-24 16:19:53
TURBO_TK_readme             6955 ----rw-d 06-Nov-24 16:19:55
Turbo_TK_CODE               7594 ----rw-d 06-Nov-24 16:19:58
D68K_readme                 3000 ----rw-d 06-Nov-24 16:19:59
D68K_rext                   4472 ----rw-d 06-Nov-24 16:20:00
QLIB_readme                  415 ----rw-d 06-Nov-24 16:20:03
QLIB_runtimes              10552 ----rw-d 06-Nov-24 16:20:06
RAMDISC_readme               351 ----rw-d 06-Nov-24 16:20:07
RAMDISC_cde                 2000 ----rw-d 06-Nov-24 16:20:09
------TK2-------           empty ----rw-d 06-Nov-24 16:20:11
TK2_README_txt                79 ----rw-d 06-Nov-24 16:20:13
TK2_TK236_bin              19104 ----rw-d 06-Nov-24 16:20:17
TK2_TK236_rom              16384 ----rw-d 06-Nov-24 16:20:21
---UTIL-TIME----           empty ----rw-d 06-Nov-24 16:20:22
SETDATE_readme               562 ----rw-d 06-Nov-24 16:20:24
SETDATE_task               10982 ----rwed 06-Nov-24 16:20:27
: QL_TASK:040600001000
SETDATE_bas                 2999 ----rw-d 06-Nov-24 16:20:29
---UTIL-INFO----           empty ----rw-d 06-Nov-24 16:20:30
MEMORYMAP_readme             582 ----rw-d 06-Nov-24 16:20:32
MEMORYMAP_bas               1369 ----rw-d 06-Nov-24 16:20:33
KEYROW_readme              empty ----rw-d 06-Nov-24 16:20:35
KEYROW_bas                  1427 ----rw-d 06-Nov-24 16:20:37
-UTIL-COMPRESS--           empty ----rw-d 06-Nov-24 16:20:38
UNZIP_readme                 549 ----rw-d 06-Nov-24 16:20:40
UNZIP                     101666 ----rwed 06-Nov-24 16:20:56
: QL_TASK:04060000C93E
ZIP                        86212 ----rwed 06-Nov-24 16:21:09
: QL_TASK:04060004B9B6
-UTIL-ASSEMBLER-           empty ----rw-d 06-Nov-24 16:21:10
CONFIG                      5510 ----rwed 06-Nov-24 16:21:13
: QL_TASK:040600000700
MACRO_lib                  19768 ----rw-d 06-Nov-24 16:21:18
Notes_txt                   5522 ----rw-d 06-Nov-24 16:21:21
QED_doc                    39795 ----rw-d 06-Nov-24 16:21:27
QED_exe                     7900 ----rwed 06-Nov-24 16:21:30
: QL_TASK:040600000600
QED_help                    2109 ----rw-d 06-Nov-24 16:21:33
QLINK                      22560 ----rwed 06-Nov-24 16:21:38
: QL_TASK:040600001000
QMAC                       34452 ----rwed 06-Nov-24 16:21:45
: QL_TASK:040600001000
Updates_txt                 8189 ----rw-d 06-Nov-24 16:21:48
WINDOW_MGR                 15440 ----rwed 06-Nov-24 16:21:52
: QL_TASK:040600002000
-----SPEED------           empty ----rw-d 06-Nov-24 16:21:53
GladTimings_bas            12482 ----rw-d 06-Nov-24 16:21:57

As you can see XFS presents QL executable info as a filenote beginning with "QL_TASK:"

The boot disk creator makes use of this to preserves QL executable info via file notes in the LHA archive.
It made sense to store filesystem extended attributes in a file note, as these can be easily preserved by archive programs from system to system.

Unfortunately standard QL zip archives don't represent QL executable info this way.
So you need to unzip a standard QL zip archive from within QDOS itself rather than on any other system.

There is a BASIC program here that will create an unzip executable for QDOS that may be of help (by Dilwyn I think).

[Derek_Stewart]

HI,

The programme is by Jonathan Hudson, which can be used systems that forget the QDOS file header, like the Qubide partition copying.

[Mark Swift]

Hi,

The programme is by Jonathan Hudson, which can be used systems that forget the QDOS file header, like the Qubide partition copying.

Thanks Derek, I wasn't sure.

Having just read my post I now realise that on the Amiga, the easiest way to get the file info back onto the unzipped executable is to set the file comment appropriately.