512*192

Once, on 20 Jan 99, someone Oleg Pritula wrote to All,
on the topic '512*192'...

OP> This is required to write a driver that supports the operation of these programs
in
OP> extended screen Pro mode.
OP> A driver for you to use in your programs as you write it,
OP> if there are any such wishes, you will expelled.

What does Pro have to do with it? This mode is not compatible on Pro...

Regards, Evgeniy aka EVP.

EP> What does Pro have to do with it? On Pro, this mode is not compatible...

Not compatible with what?
The structure of the extended screen of Pro is approximately the same as that of the subject. A driver
is needed to organize output not only to the subject screen but also to the extended
Profi.
Determining which one to use is most likely done using autodetect.
Although the LC option is also possible - installation in the setup.

Yes, by the way, is the subject monochrome? If you can go into more detail to connect with the pros.

2Viktor Kuzmin: At least he would respond. Or is the attitude towards this completely
negative?

\\|// ╟─┤asta la vista !!!
o(@ @)o -=POWer/WDG=-
-----ooO-(_)-Ooo-----

As far as I remember, the addresses are the same (#4000 and #6000), but the columns are in reverse,
i.e. the zero column sits with #6000, the first with #4000, the second with #6001, etc.
(this is for b/w Pro, for Pro+ there is still a palette somewhere), but the height
of the Pro screen is four “thirds”, i.e. The screen structure is the same, but 256 pixels in
height.

ps: I'm not sure about address #6000, because... I checked it a long time ago.

With the best, Eudgine!

... I’ll buy a moonshine still. intermediary phone number 02.

OP> Not compatible with what?

On Pro, after all, 512*240...

OP> The structure of the extended screen of Pro is approximately the same as that of the subject.

On Pentagon and Scorpia, here like this:
┌────┬────┬────┬────┬────┬────┬ ┬────┬────┐
│4000│6000│4001│6001│4002│6002│. ..│401F│601F│
└────┴────┴────┴────┴────┴────┴ ┴────┴────┘
And similarly, the second screen in the 7th bank at addresses #C000/#E000...

OP> Yes, by the way, is the subject monochrome?

The subject is _only_ monochrome - after all, its implementation is such that every
second pixel is read instead attribute...
Although on Scorp you can change the color of the entire screen via the #FE port - there
the color of the subject = the color of the border...

Once on 23 Jan 99, at 02:13:23, Oleg Pritula wrote to Eudgine Palenock on the topic
'512*192', let me think, I'll write a few lines, and wrote the following:

OP> Although the LC option is also possible - installation in the setup.

This is preferable than homing.

OP> Yes, by the way, is the subject monochrome? If you can go into more detail to link it with the
pro.

I don’t know how to do it in Pro, but I know about the details on Scorp:

===cut from the subject diagram in Scorp===

" The advanced mode is turned on by setting the 1st bit (counting from
0th) of port #EFF7. In the advanced mode, the color of the screen is determined by the color of the border, and the color of the set points 0 or 7 depending on the 2nd bit of the border color (counting from 0). If the color of the border is within 0..3 then the color of the set points will be white, otherwise - black.

Half of the image is located at address #C000 and occupies
#1800 bytes. The other half is located at address #E000. may be in the 5th or 7th banks depending on the 3rd
bit of the #7FFD port. The characters on the screen alternate - one in one
half, and the other in the next."
===cut===

1. when the subject is turned on, the #FE port is blocked, i.e. You can write into it, but
the border, naturally, and the color of the monochrome will not change until you turn
off/on.subject.
2. after recording the border color (to set the color of the future monochrome),
you need to take a short pause (HALT, or 512 times DJNZ $-2), and only
then click the second bit on #EFF7.
3.give the opportunity to select a border in the setup.
example:

; enable the subject with the monochrome color in accordance with user setup

ld a,(setup_border)
out (#fe),a
halt ;or any delay
call on_subj
ret

;switch color

call off_subj
ld a,(new_border)
out (#fe),a
halt
call on_subj
ret

Bye, Oleg Pritula. SY, Klim Gromov!!!

Night. The time is 06:31. And only Eudgine tried to tell Oleg something.

EP> On Pro it’s 512*240...
just a few additional lines

OP>> The structure of the extended screen of Pro is about the same as that of the subject.
absolutely the same structure, only on Pro The black screen is in other pages

EP> On the Pentagon and Scorpia like this:
EP> ┌────┬────┬────┬────┬────┬────┬ ┬────┬────┐
EP> │4000│6000│4001│6001│4002│6002│...│401F│601F│
EP> └────┴────┴────┴────┴────┴────┴ ┴────┴────┘
EP> And similarly, the second screen in the 7th bank at addresses #C000/#E000...
everything is correct, but if you set bit 4 of the 7FFD port you will get:
6000|4000|6001:4001:...:601F:401F

OP>> Yes, by the way, is the subject monochrome?

EP> The subject is _only_ monochrome - after all, its implementation is such that every
EP> second pixel is read instead of an attribute...
I didn’t like one thing in this scheme: it is in yincreases the frequency, i.e. fits all 512 pixels into the previous 256 pixels. IMHO it was better done on a pro...
Magnificent Max.

-!- GoldED/386 3.00.Beta5+
! Origin: If you're drunk, it won't seem like that!.. (2:5010/141.10)

The time was 24 Jan 99 and the day was 20:47:04. Fearing a bloodthirsty moderator
Klim Gromov wrote Oleg Pritula on the topic 512*192

KG> 1. when the subject is turned on, the #FE port blocks, i.e. You can write into it, but
KG> the border, naturally, and the color of the monochrome will not change until
KG> you turn it off/on. subject.
KG> 2. after recording the border color (to set the color of the future monochrome),
KG> you need to take a short pause (HALT, or 512 times DJNZ $-2), and only
KG> then click the second bit on #EFF7.

:-( ) I don’t have this. The border can be changed at any time and the color
of the entire screen will also change, and if something is blocked
then it means everything is buggy.

With best wishes, Kirill Frolov.

Once on 25 Jan 99, at 12:41:11, Maxim Bazarov wrote to Eudgine Palenock on the topic
'Re: 512*192', let me think, I'll write a few lines, and wrote the following:

MB> I didn't like one thing in this circuit: it increases the frequency, i.e. it fits
MB> into the previous 256 pixels all 512. IMHO it’s better done on the Pro...

Of course, if you plugged the terminal under hayes for the Pro, using all its
hardware advantages, it would be great, but on the other hand, when you’re stuck somewhere on the bard and looking at a full-fledged screen from Ansi, especially I don’t care how it
everything works.;)
╔═─────────═╗
[GIVTS GKS RF] :-Q
╚═─────────═╝
Bye, Maxim Bazarov. SY, Klim Gromov!!!

Night. Time 02:00. And only Klim tried to tell Maxim something.

KG> Of course, if you plugged the terminal under hayes for the Pro, using all its
KG> hardware advantages, it would be nice, but on the other hand, when
KG> you hang around somewhere on the bard and watch a full screen from ansi, especially
KG> don’t give a damn how it all works.;)
if I understand sausages correctly, then a full-fledged ansi comes with
color. You can do this on a pro, but on the rest?

Magnificent Max.