Peter maked a short video about demonstrating the Zzzip, now it is in the EP TV!
And there is the original mpg

It's great!

I wish I had a real Enterprise.....

A few days ago sold one in the eBay.
But if you realy want it, I will search one for you!

We got some new Zzziped games from Peter. The Routes is writed by Peter, the others is only zipped by Peter.

The Routes is a great puzzle game, the Crib is a Enterprise version of Cribbage card game. Reversi is a new version for the well-know game. And the Rock is the "Scissors Paper Stone" game.

Thanks Peter!

Áh, ismeretlen EP programok. Nem hittem hogy még léteznek ilyenek.

Endi: "Wow, unknown EP programs. I didn't believe there still existed any."

Using a different EXOS version and additional ROM configs, may the same basic program result a slightly different compiled file? I mean, I compiled a basic program with EXOS 2.1 and EXDOS for the first time, and years later I compiled the same basic program with EXOS 2.3, IVIEW.ROM and without any EXDOS. May the result be different? (Moreover, for the first time I used a real Enterprise computer, and later the EP128emu.)

When the compiled program call any ROM routines use a any direct address, or use the standrad RST routines?

Some difficult questions about Zzzip and EXOS, but one easy question about English, which I will answer first.

We can use the word "mirror" to mean "reflect", although for a list of commands, such as in your program, we would simply say "mirror" rather than "mirroring".  However I think we would nornally use a different word.  I often edit photos with Adobe Photoshop, and that program has a number of rotate commands, two of which are Flip Vertical and Flip Horizontal.  (Not very good English really, as Vertical and Horizontal are adjectives  -  after a verb it would be better to use the adverbs Vertically and Horizontally).  Anyway these commands are identical to the functions in your program.  Because it is not so obvious in your program that the commands are meant to rotate the image, I would suggest that you use the commands "Flip Image Vertically" and "Flip Image Horizontally".

I will have to do some more work to try and answer the difficult questions.

Well, I have investigated the two compiled versions of the Basic program.  First of all I compared them (using my COMP program) and found that they are almost exactly the same.  There is just one byte that is different between them and I believe that in the case of the version compiled using EXOS 23 (Hungarian)  the byte is simply an error.  I can not see any reason why EXOS would have any effect on the byte value written by ZZZip at this particular point and therefore I think it just one of those unexplained glitches.  In fact I think if you compiled the program again (under the same conditions) it would come out correctly this next time.

Also I looked at how calls are made to ROM routines (the question asked by Zozo).  Actually there are three questions that need to be answered. 

The first question is "How does Zzzip access EXOS routines while it is compiling a Basic program?" and the answer is that Zzzip always uses RST 30H.  The functions used by Zzzip are:
1   Open channel
2   Create channel
3   Close channel
5   Read character
6   Read block
8   Write block
9   Channel read status
11  Special function  (Zzzip only uses VIDEO  -  Display page)
24  Allocate segment
25  Free segment
26  Scan System Segments  (I think this is just used to exit to BASIC but I would need to check more carefully to be sure)
28  Explain Error Code

The second question is how compiled programs access EXOS routines.  I feel certain that the only method used is RST 30H.  However I am not sure which EXOS functions are used by compiled programs, and it is not very easy to find out.  Unfortunately I did not keep good records of the code used in compiled programs and the only way I can see this code is to disassemble a compiled program.  Then of course one example program will not contain all the Basic functions, so I will not know that all possible EXOS functions have been covered  -  unless of course I write a special Basic program that is nonsense but does contain all possible types of Basic statement.

The third question is how compiled programs access the Basic ROM.  I do not know the answer exactly and some of the code in compiled programs is so complex that I can not easily understand it.  However I seem to remember that for some functions the compiled program presents a standard Basic statement (or part of a statement) to the Basic ROM, to be interpreted and processed.  This is a question that I would need to investigate further.

I remember that one of the most difficult areas was Exception Handling  -  this is not surprising because it is only required when something has gone wrong! I noticed that in the Basic program written by Szipucsu there are several Handler routines and I would be interested to know whether these routines work correctly in a compiled program.