Исходники TR-DOS для SjASMPlus

[Keeper]

Where can I find code for return from trdos ?

x2869       LD      A,(HL)      ;берем код команды
            CP      C           ;он совпал с требуемым?
            JR      NZ,x287F    ;если нет, то берем код следующей команды
            POP     AF          ;восстановление AF
            INC     HL          ;берем адрес, по которому находится адрес подпрограммы
            LD      E,(HL)      ;берем адрес подпрограммы
            INC     HL
            LD      D,(HL)
            LD      HL,YOUR_EXTRA_CODE_ADDR
            PUSH    HL          ;кладем его на стек
            PUSH    DE          ;кладем на стек адрес подпрограммы
            LD      HL,(#5D02)  ;восстановление HL и DE
            LD      DE,(#5D04)
            RET                 ;переход к подпрограмме
x287F       CP      #FF         ;достигнут конец таблицы?
            JR      NZ,x2887    ;если нет, то берем адрес номера следующей подпрограммы
            POP     AF          ;снятие AF со стека (этого можно было не делать)
            JP      YOUR_EXTRA_CODE_ADDR
x2887       INC     HL          ;пропуск двух байтов адреса подпрограммы
            INC     HL
            INC     HL
            JR      x2869       ;повтор

;SOMEWHERE IN TRDOS FREE SPACE
YOUR_EXTRA_CODE_ADDR
            DI              ;Do what you need here...
            HALT
            JP      x01D3

[Keeper]

Основано на исходниках версии 6.11E

Что сделано:
- Компилируемый исходник
- Удален конфигуратор
- Отключена работа с резидентами
- Размер рам-диска 896Кб

По сравнению с версией 6.11Е эта версия компилируется со следующими настройками:

DEFINE RUN_BOOT_B_ON_DOS_START - Выполнять комманду RUN "BOOT.B" при входе в TR-DOS с адреса 0x0000
DEFINE RAM_DISK_SIZE_896K - 896К

Бут по команде 8 пришлось удалить т.к. WDC 1.3 не влазил бы в ПЗУ...

[VELESOFT]

- Размер рам-диска 896Кб

Why is supported too long ramdisc ?
Ideal ramdisc size is 648kB (82 tracks) for compatibility with original FDD format = possibility always use export/import image from/to fdd. If ramdisc is longer than 648kB then is unusable on real FDD and must be converted..

If PHOENIX contain 2048kB memory then best way is move ramdisc position to second 1MB memory and size can be up to 1024kB. First 1024kB of 2MB memory is often used by software. First 128kB must be always for ZX software, next 128kB is used in WILD PLAYER (detect and use extended memory). Next pages up to 512kB can be used for some GAMEs or assemblers (ALASM).

If ramdisc is in first 1MB memory then ideal memory layout is:

a) 128kB ZX ram, 384kB reserved (for software using extra memory up to 512kB), 512kB ramdisc.
+ better compatibility with software for 512kB ram
- small ramdisc

b) 128kB ZX ram, 256kB reserved (for software using extra memory up to 384kB), 640kB ramdisc.
+ compatibility with software for 256kB ram (max. 384kB)
+ full ramdisc size compatible with original FDD image.

[Keeper]

Why is supported too long ramdisc ?

RAM-DISK is not some kind of RAM space that should be formatted in some special way to be a RAM-DISK. Its logical structure is very simple:

1. It is organized like a stack, so "virtual track 0" will be placed in the RAM page with the highest number, there will be placed tracks 1,2,3 too. For example, in Pentagon 1024 we have 64 RAM pages, then track 0 of RAM-DISK will be placed in page 63.

2. As I mentioned before, RAM-DISK is not a "special" structure in RAM pages, it is simple mapping of TR-DOS disk structure in RAM, in other words it is a per-sector copy of TR-DOS disk. So, if you will import standart TR-DOS disk (640Kb) into RAM-DISK you won`t corrupt "lower" RAM pages that won`t be occupied by some RAM-DISK data. Also you can configure its size by changing "FREE SECTORS" param in sector 8 of track 0.

If PHOENIX contain 2048kB memory then best way is move ramdisc position to second 1MB memory and size can be up to 1024kB.

In my version of TR-DOS for ZXM-Phoenix RAM-DISK is always placed in second megabyte, even if there are no second megabyte of RAM But some bug(s) is(are) still there, that makes me angry... May be I had too long break in asm programming for speccy...

[char]

trдоs.ru освободился.

[DimkaM]

trдоs.ru освободился.

tr-dos.ru наверно правильней будет

[Advertiser]

[VELESOFT]

RAM-DISK is not some kind of RAM space that should be formatted in some special way to be a RAM-DISK. Its logical structure is very simple:

1. It is organized like a stack, so "virtual track 0" will be placed in the RAM page with the highest number, there will be placed tracks 1,2,3 too. For example, in Pentagon 1024 we have 64 RAM pages, then track 0 of RAM-DISK will be placed in page 63.

I know detailed structure or ramdisc/TRD file in ram. Some different TR-DOS versions use different position in memory. Only last versions of TR-DOS 6.0x support same layout:
TRD image is divided to 16kB pages and placed from last memory page 63. This is best way. But possibility use 896 kB ramdisc as default value is bad This ramdisc size is dangerous for data placed/loaded to high memory pages on software for Pentagon 256/512kB.....

2. As I mentioned before, RAM-DISK is not a "special" structure in RAM pages, it is simple mapping of TR-DOS disk structure in RAM, in other words it is a per-sector copy of TR-DOS disk. So, if you will import standart TR-DOS disk (640Kb) into RAM-DISK you won`t corrupt "lower" RAM pages that won`t be occupied by some RAM-DISK data. Also you can configure its size by changing "FREE SECTORS" param in sector 8 of track 0.

I know. I use PENTAGON 1024 without real FDD, only RAMDISC mapped to drive "A". Default size of ramdisc is 640kB. User can't rewrite pages 8-23. This can be used with ALASM, WILD PLAYER,...

In my version of TR-DOS for ZXM-Phoenix RAM-DISK is always placed in second megabyte, even if there are no second megabyte of RAM But some bug(s) is(are) still there, that makes me angry... May be I had too long break in asm programming for speccy...

Can you please write also version for ZX PROFI or other clones ? This is only different memory paging code....

[SoftFelix]

Keeper, А можно всё-такИ попросить внести в исходник 6.11е на постоянной основе fix от VELESOFT'а?

[Alex_NEMO]

Keeper, подскажи, пожалуйста, как RAM-диск на С: переназначить, вместо D:? Хочу под КАЙ переделать...

[Дмитрий]

Alex_NEMO, а чем тебя каевская родная не устраивает? Ведь с этой тырдосиной не будет работать ни переназначение рам-диска на другие буквы, ни Ресет-сервис каевский...