[0/3] NAMv0.24.$B
ZXNet echo conference «real.speccy»
Just replace your previous version with subj and that's it. :) Settings from v0.23
will be easily swallowed - I didn't fix anything there.
Added:
- exit to tr-dos after the end of the last session and start boot on the current
disk
- if when the HangUp message appears (after the last session) you press Caps
Shift, then the computer will simply reset (as with a reset)
that's all. :)
Tim Kelly allowed posting.
ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/
September 18, 2001 at 21:33:31
Sergey Zotov wrote to All on the topic "[0/3] NAMv0.24.$B":
SZ> Just replace your previous version with subj and that's it. :) Settings from v0.23
SZ> will be easily swallowed - I didn't fix anything there.
SZ> Added:
SZ> - exit to tr-dos after completing the last session and launch boot on
SZ> the current
SZ> disk
SZ> - if you press Caps
SZ> when the HangUp message appears (after the last session) Shift, then the computer will simply reset (as with reset)
SZ> that's all. :)
SZ> Tim Kelly allowed posting.
And Disa??? :)
Well, that’s all, Sergey, for now.
Alexander Grokholsky was with you on September 19, 2001
[I ZX] Spawn/Last Masters Group/X-Project Association 12:33:31
... E-Mail: spaw...@mail.ru - FidoNet: 2:461/16.23 - ZXNet: 500:572/16.23
ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/
Tue 25 Sep 2001, at 21:17:24 Sergey Zotov told Alexander Groholsky about [0/3]
NAMv0.24.$B.
SZ> And if he doesn’t respond, I’ll disassemble the subj and do the work
SZ> with
SZ> time via SMUC. Here! Because I'm tired of the first (night) boss
SZ> break
SZ> skipping! And no Disa will forbid me. It seems to me that he again scored on
SZ> subj as well as on Melon.
Listen, don’t break off those whose watches were assembled according to Gluck’s scheme. Make
at least an external clock driver, like in Lara Croft, up to 256 bytes long at
address #5b00.
Bye, Sergey.
WBR, Vivid^Brainwave.
AM>’s scheme. Make
AM> at least an external clock driver, like in Lara Croft
AM> with a length of up to 256 bytes at
AM> address #5b00.
By the way, the printer buffer sits at this address, and Scorpio uses this area
for himself. For me, looking at the 7th screen (although this rarely happens) is not very pleasant... And this is the most common misuse of this area. But I'll think about it...
AM>> diagram assembled. At least make the clock driver external, like in
AM>> Lara Croft with a length of up to 256 bytes at address #5b00.
SZ> By the way, the printer buffer sits at this address, and Scorpio
SZ> uses this area for itself. For me, looking at the 7th screen (although this rarely happens) is not very pleasant...
To recognize 5/7 of the screen, Scorp uses only one bit of cell
#5b5c; it is enough that the driver at this address contains a value in which bit d3 is equal to zero. In principle, you can simply monitor the contents of the 3rd (3-2-1-0) digit of this cell when writing a driver. This is exactly how I
made firewood for Lara: when there was any heresy at address #5b5c, I
simply shifted the code by 1-2-3 bytes, filling it with zeros.
SZ> And this is the most common misuse of this area. But I
SZ> I'll think about it...
It will be steering.
Why does Nam have a watch?
SZ> ZXNet: 500:8462/1 ~/ <~ http://zs80.chat.ru/
SZ> Fido: 2:5057/21.93 /_ _> ftp://zx-museum.org.ru/zs/
Sergey, Пака! WbW, i┌i└/4D.
SZ> By the way, the printer buffer sits at this address, and Scorpio uses this
SZ> area
SZ> for himself. For me, looking at the 7th screen (although this rarely happens) is not very pleasant... And this is the most common misuse of this area. But
SZ> I
SZ> will think about it...
This address was given as an example. You can at least post #bd00. Tell what the
driver should return and what it has as input. The people will write under their own hardware.
Bye, Sergey.
WBR, Vivid^Brainwave.
Sat 29 Sep 2001, at 11:43:20 Ilya Vinogradov told Sergey Zotov about [0/3]
NAMv0.24.$B.
IV> Why does Nam have a clock?
So that if there are several bosses, he can call where necessary and when
needed automatically.
Bye, Ilya.
WBR, Vivid^Brainwave.
SZ>> of this area. But I'll think about it...
AM> This address was given as an example. You can at least post it on #bd00
AM>. Tell what
AM> the driver should return and what it has as input. The people under
AM> will write their own hardware.
As soon as I get ready, I’ll write here right away. Because I was already getting nervous before pressing Break. ;) In addition, my driver for Larka takes 56 bytes and does not
reach the painful variable responsible for the screen. :)