TRD version of GAMES with kempston mouse support

Цитата:

---

Сообщение от Shadow Maker

Сделаю Bloodwych. Но я делаю медленно, поэтому пока играйте в тапку.

VELESOFT, а чем отличается версия Bloodwych 2006 и Bloodwych 2008?

---

Bloodwych 2006 use special mouse driver designed for second mouse support with old firmware of CPLD (K-MOUSE INTERFACE version 2006). Use software switching of master and slave mouse.

And K-MOUSE 2008 is modern version of K-MOUSE INTERFACE and slave mouse use different ports only...

---------- Post added at 18:41 ---------- Previous post was at 18:37 ----------

Цитата:

---

Сообщение от TomCaT

Что происходит в мышь-версии R-TYPE по ссылке из первого сообщения темы? Версия явно 128к, из 48к не грузится, после загрузки из 128к или по 'Tape Loader' сбрасывается сразу после вывода меню. Но - если после этого сброса ее снова с ленты загрузить - все работает нормально. Unreal 0.352b2, модель памяти PENTAGON 128. Unreal.ini и дампы ПЗУ - по требованию.

---

This is 128kB remix of R-TYPE with fixed 8th level. Game must be loaded in USR 0 mode (from 48rom with enable 128kB paging)

Цитата:

---

Сообщение от VELESOFT

This is 128kB remix of R-TYPE with fixed 8th level. Game must be loaded in USR 0 mode (from 48rom with enable 128kB paging)

---

It's strange, for my TRDOS-ed verison of this mouse R-TYPE 128 remix doesn't need USR 0. I advise you to put OUT ... , 16 before loading the first 49152,16384 file, just like you do with the followin pages.

Цитата:

---

Сообщение от TomCaT

It's strange, for my TRDOS-ed verison of this mouse R-TYPE 128 remix doesn't need USR 0. I advise you to put OUT ... , 16 before loading the first 49152,16384 file, just like you do with the followin pages.

---

For loading files in 128 basic must be add POKE 23388,page.

OUT 32765, can't use values in range 16-23:
- original code in this game use paging via LD A,#5x + OUT (#FD),A. On Pentagon 512 this code access to high memory then I must also load all blocks on basic to this extra pages !!!

But can be patchen game code for correct memory paging using out 7FFD via BC register and use only values in range 16-23....

(your TRD conversion crash on pentagon's with extra memory)

2 Velesoft: R-TYPE tape version with mouse support, from your site, uses OUT 32765, and values 16-23 . Does it mean the tape version from your site also crashes on pentagons with extra memory?

If so, I can't understand what the problem is - my DOS version uses the same loading as yours TAPE version. And if the game requires #5x values on Pentagon 512 and crashes with #1x values, it is Pentagon 512 compatibility problem, not my problem.

And if you say the game with values #5x will work well both at Pentagon 128 and Pentagon 512, then, of course, I will change the values.

Кто-то может объяснить, что это за крахи на Пентагоне 512, если страницы выбираются значениями #1x а не #5x ? По идее, в Пентагоне 128 этот бит 6 незадействован, так что можно все и под 5x переделать, но интересно все-таки, почему нет совместимости...

Цитата:

---

Сообщение от TomCaT

2 Velesoft: R-TYPE tape version with mouse support, from your site, uses OUT 32765, and values 16-23 . Does it mean the tape version from your site also crashes on pentagons with extra memory?

---

??? This is screenshot of basic loader on my TAP version:

http://velesoft.speccy.cz/other/r-type-basic.png

Цитата:

---

And if you say the game with values #5x will work well both at Pentagon 128 and Pentagon 512, then, of course, I will change the values.

Кто-то может объяснить, что это за крахи на Пентагоне 512, если страницы выбираются значениями #1x а не #5x ? По идее, в Пентагоне 128 этот бит 6 незадействован, так что можно все и под 5x переделать, но интересно все-таки, почему нет совместимости...

---

This is problem on all russian Pentagon machines with extra memory bigger than 128kB. If port 7FFD on Pentagon machine is used for select extended memory pages, then original software for ZX128 will often crash and must be rewrited paging code in game !!!

Some original games use two different ways for memory paging:
1) LD BC,7FFD + LD A,XX + OUT (C),X (7 bytes and rewrite registers BC+A):v2_mad:

2) LD A,value + OUT (FD),A (4 bytes and rewrite only register A) :v2_thumb:
This code is often used, is shorf, fast and use only register A. But for compatibility with ZX 128+2A/+3 must be set D6 of value in register A to log.1. (+2A/+3 use ports adressation: 01xxxxxx xxxxxx0x).
Example of code:
LD A,#50
OUT (#FD),A
Previous value of register A is used as high adress of 16bit port.
It's same as OUT #50FD,#50
(#50FD = BIN 01010000 11111101) and value #50 = BIN 01010000 (48rom+vram0+page0) - on Pentagon 256-1024 this is page 8

Software using #5x values on port #5xFD will use pages 8-15. Theoretically you can rewrite #5x value to #1x value, but this will work only on Pentagon 128 and ZX128 but crash on ZX128+2A/+3 and Pentagon 1024SL(use same adressation as ZX128+3)

All original 128kB games can be dangerous for using on Pentagon 1024SL if use ramdisk 896kB. Can be rewrite last 128kB of ramdisk pages (page 8-15). For correct work you must use maximum ramdisk size 768kB or switch Pentagon to 128kB mode via set bit D2 of port #EFF7. (but in 128kB mode will not work ramdisc support in trdos). Pentagon design is bad, big part of 128kB software must be patched for possibility use correct 128kB memory on Pentagon.

I start to understand. If the value #5x is used for the way 2) LD A,value + OUT (FD),A to make the high part of address of 16 bit port something like 01xxxxxx

- then for the way 1) LD BC,7FFD + LD A,XX + OUT (C),X the values #5x and 1x must work well on ZX128 and ZX128+2A/+3 . Or the OUT(C),A with values #1x crash the Pentagon 512 ?

VELESOFT, как-то не хочется делать две версии. Лучше брать 2008 или 2006? Какие интерфейсы больше востребованы?

Цитата:

---

Сообщение от Shadow Maker

VELESOFT, как-то не хочется делать две версии. Лучше брать 2008 или 2006? Какие интерфейсы больше востребованы?

---

only version 2008 !!!

Old version 2006 is not supported in emulators. 2008 is better

---------- Post added at 13:30 ---------- Previous post was at 13:23 ----------

Цитата:

---

Сообщение от TomCaT

I start to understand. If the value #5x is used for the way 2) LD A,value + OUT (FD),A to make the high part of address of 16 bit port something like 01xxxxxx

- then for the way 1) LD BC,7FFD + LD A,XX + OUT (C),X the values #5x and 1x must work well on ZX128 and ZX128+2A/+3 . Or the OUT(C),A with values #1x crash the Pentagon 512 ?

---

All paging codes (basic loader + game code) must use same values !!!
If you use #1x in basic and game code use #5x then will game crash . If you use in basic same values as in game code (#5x) then will game work on all machines, but on pentagon 512/1024 rewrite ram pages 8-15. If you rewrite values #5x in game code to #1x and rewrite values in basic to #1x then will game work on all ZX models/clones correct !!! :v2_thumb:

Oh, I understood now. The whole incompatibility started from partly 8-bit addressing, but on >128k the full addressing loader still can use the standart #10-#17 pages, while the game for some reasons uses #50-57, and the mixture could result in crash.

I changed the pages in my loader, and also added a #50 page selection after start at "25e3" address, for basic cheat menu returns the #10 value. Now it should work fine. I passed the first level well on Pentagon 512 model in Unreal Speccy.

Цитата:

---

Сообщение от TomCaT

Oh, I understood now. The whole incompatibility started from partly 8-bit addressing, but on >128k the full addressing loader still can use the standart #10-#17 pages, while the game for some reasons uses #50-57, and the mixture could result in crash.

I changed the pages in my loader, and also added a #50 page selection after start at "25e3" address, for basic cheat menu returns the #10 value. Now it should work fine. I passed the first level well on Pentagon 512 model in Unreal Speccy.

---

Yes, this version work correct. :v2_thumb: