ZX ASM 3- help
 

Dear friends,

this weekend my friend showed me ZX ASM 3 assembler in emulator on JHCON Czech speccy party and I must say I am completely enthusiastic about it.

I know, today, there may be better assemblers, but I am thinking to rework its disk operations for MB02+, because I want to run ZX ASM 3 on my speccy with MB02+ disk interface. I have not Betadisk. And also all disk oparetions in ZXASM 3 are called in a standart way (CALL h3D13), so it should be not very complicated to write new disk operations.

Is here somebody, who could redirect me onto some document on the internet where I could find system info about ZX ASM 3? Source code, at best...

I mean informations, that would help me to convert disk operations for MB02+. I am looking into the code, but some things are still not very clear to me. TRDOS CALL h3D13 I found 24 times in the code. I am trying to find out principles of disk operations of ZXASM3.

Or do you know, if the author is still on the scene or do you have a contact to him? (authors in the ReadMe file are: Oleg Chochlov, Konstantin Afendikov and Vladimir Rubcov).

Thanks, guys

Hood

Добавлено через 21 минуту
I forgot to ask you about one thing. Could someone send me a source code for ZXASM 3??? I mean a long code with includes or sub-includes. I would work with it and discover what TRDOS calls are implemented.

my mail is hood@znojman.cz


Thanks a lot

Hood

The answer to your question can find here:
http://zx.pk.ru/showthread.php?t=215
http://zasm.by.ru/index.html

You can even ask Rubts0FF - http://zx.pk.ru/member.php?u=201, for example through E-mail.

Author - http://zx.pk.ru/member.php?u=201

Thanks everyone for help. I tried to contact the author, hopefully he will be able to answer.

Thanks for links, I found исходные тексты ZASM 3.10, ZASM 2.5, but unfortunatelly not 3.0:(((

Really, nobody has them?? I hope the author will be so kind and contact me.

Thanks again

Hood

3.10 is better & bugfixed version of 3.0, why not try to use it?

Hello Shadow Maker,

I know 3.10 is better and improved, but it uses overlays and more complicated TRDOS disk operations, I think. 3.10 is more bound to Betadisk and I guess it would be much harder to rework disk operations in 3.10 than 3.00.

Or, could you tell me, if in 3.10 standart TRDOS calls are used only? or some "dirty" calls are used?? maybe also memory organisation is more sophisticated. Is 3.10 able to use 128k machine only? We in the Czech Republic use only 128k machines, and no clones with extra memory. If standart calls are used and if 3.10 works with 128k memory, I could try to rework 3.10 version.

Thanks for answer

Hood

3.10 uses direct tr-dos programming, if I remember well. Also 3.10 works with 128k memory too, so there should be no problem. All you have to do is to locate the subroutine, which does all the load/save procedures and reprogramm it. But I never saw the sources, so my guesses may be wrong :) Author can tell you more detailed info, i believe.

Try to use Unreal Speccy emulator for investigations. It has very flexible breakpoint mechanism ( conditional breakpoints ). This will make your life easier :)

Try to answer questions. I apologize for translation, using translate.google.com.
ZXASM version 3.10 is based on 3.0, and uses the same standard point of call for disk operations 3D13, IMHO. An alternative point of call for disk operations (3D2F) does not make sense to use, it is necessary for operations fast format discs and work with non-TR-DOS disks. System calls TR-DOS quite simple - to register C placed command code, in the other registers command parameters (track, sector, address RAM), and executed CALL #3D13.
ZXASM 3.10 requires a computer with a minimum of 128kb, but can be longer.

...what I have discovered in 3.0...
 

Hi guys,

so, I have investigated version 3.0. Most of TRDOS 3d13 calls or jumps I have discovered (with service number in brackets):

MERGE, LOAD 85e5(eh)
SAVE, SAVE SETUP, SAVE BLOCK 84cb(12h), 84d6(bh)
SAVE OBJ 8541(8h),8564(12h)
CAT c6c4(5h), c734(5h) (page 14h)
LOAD FONT ca19(eh) (page 14h)
LOAD STS 8d1b(eh)
DRIVE CHANGE cbf2(1h), cbb1(18) (page 14h)
INCLUDE, INSERT 66a3(ah), 66ae(8h), 6718(5h)
MAKE 65b2(12h), 65b9(8), 6664(9h), 6676(9h)



however there remained several ones, that I do not know to whihch functions of ZASM they are linked:

661a
859a
c851
c876
c8c6

I also, did not found a TRDOS call for function ERASE FILE.

I found, that the pool begins on c012 in page 13h. That is probably the reason, why maximum size of pool is 16128 and not 16384. But, could you tell me one thing? It is clear, that the bigger the pool size is, the quicker is assembly function. BUT, what advantage does it bring to the user, he lowers pool size for example to 256 bytes? That is what I do not know.

I also suppose, that the maximum length of source code file is from about 31515 (do not know the exact adress form my head) till 65535. Is this right??

Yes, I forgot an important question. Do you have any ideas where I could safely place my new disk routines in the memory??? Is there any free RAM which I can use?

Could someone look into code and answer all my questions, please???


Thanks a lot


Hood