Topic - the problem with the drive to the Scorpion ZS 256.

               T E M A I I



(C) SERGIUS PUZZLER



        Problem Scorpion ZS 256?


   Now I will tell you a story of my communication with my 
computer. If you, the reader, after reading this material, any 
thoughts or have infa, about what it is or how to deal with it,

I'll be very grateful and endlessly
glad if you write me a letter, or even
article on the topic for entu ZX-Pilot'a.

   There is a suspicion that this problem is related to the 
Scorpion, and perhaps with the old its development (the card).


   Let's begin.

   I have a Scorpion ZS-256 and all. Well, of course, with the 
shadow Monitor (TM) MOA (C) 1993, 94 v2.5c 15 jan 94. Of 
course, this does not nove, but it works fine. I bought it

with hands, which, in turn, also took
with other hand. I do not know where it came from a
Kovrov, from St. Petersburg or any pirates concocted.

   In short, no problems, okromya
those who are already inherently in Scorpio. I will not list 
them all their already know.


   But once again, be slowed by TM
text from one of the programs I've encountered
with the following: TM can not be written on
disk - error. Checking RDS'koy floppy, convinced that the drive 
is in order. But TM stubbornly does not want to work with him.


   Looking disk parameters and drive in
Menu TM Disk Utility, find out what TM said that the disc - One 
Side'ovy. Obviously a glitch. The rest of the program ADS, RDS, 
FUT, and the rest give to know that the drive - Double Sided. 

   Restornuv floppy RDS'koy persuaded HM
that the disc is double sided. Searched and found several more 
disks on which had a similar reaction TM. Naturally,

all their zarestoril.

   And they live happily ever after, and the good ever after. 
But then came another problem, as well, quickly open the gates. 

   That's right, this story was continued.

   I'm a no, but the encoder. I sit myself
somehow, sit in Alasm_4.1, nobody
touch. Kodyu means to develop new
the possibilities of this naikruteyshego and naiudobneyshego 
assembler. Decided to somehow load the drive with "B" 
alasmovsky file. Hear overwrought initialized

drive, see the message "B>", I press "W". Choose the file, 
trying to pressure "Enter". FIG there, rather than file. 
Unreadable! Thought Totals kreshing s drive. Checked RDS'koy - 
o.k!, Know bad sektors. Repeated reading from disk "B" from

Alasm'a, you still can not read.

   And there came a vision, and I realized that all
it already was, but in a past life. And I do not
Deja Vu Do I? Yeah like I would not read
him yesterday nanoparticles? Or read it?

   But nevertheless, I'm leaving in STS_6.2, here
he home, go out to the address # 5CC8 and ofigevayu:


          drive A # 5CC8 1983

          drive B # 5CC9 1980

          drive C # 5CCA FF

          drive D # 5CCB FF


   Unscramble:


    # 83 -% 10000011

                     80 as 80

                     2 sided

                     80 tracks


    # 80 -% 10000000

                     80 as 40 (1)

                     One sided (2)

                     80 tracks


   The program decided that the one-sided disc (2), but in 
addition more and 40-track (1)!


   Probably, I'm starting to wander?. You have to manually put 
the variables of STS'a TR-DOS'a! Where have you seen, tell me

for mercy, please! Similarly, no or I
in delirium.

   Of all the above stated arises
question:


     Who is buggy? Alasm, TM or TR-DOS?


   I went to Vel'u. Checked Alasm
his Pentagon, everything is fine.


               TM or TR-DOS?


   But why then the rest of the program
define the data disk drive correctly,
if the case is in the TR-DOS'e? Can cause a disk controller 
architecture Scorpio? The silence, the room is silent ...


   The question remains open.

   We are not local people, help who than
can. Amen.


                                    SP.WH!