Promotion - Soft from Kharkov: PiFormat,

                                         
          -PIFORMAT-           
                                         
(C) 1999 PIcon/Last Masters              
-------------------------------------------------------
 From the editor.               
     I didn't publish "just another format-
rover", but really very useful
program that will help you format
Rotate your “dead” disks. Description given
There is no point in making a new program. I re-
I wanted to limit myself to only describing the differences
this program from its own kind. With this
I addressed the question directly to
the author of the program.                        
                                         
      Answers to some questions      
                                         
    This versionPIFORMAT`a allows
get around some scratches, which ones and how
I’ll tell you exactly now. Usually use
The format of the track you select is not always available
correct and correct.Вот пример одного из них:               
+---------------------------------------+
| #4Е - 5Oшт. Последний пробел ??       |
| #00 - 12шт.                  ??       |
| #F6 -  Зшт. Поле #С2         ??       |
| #FC -  1шт. Индексная метка  ??       |
| #4Е - 22шт. Первый пробел    ?? 50 шт.|
| #00 - 12шт. |
| #F5 -  Зшт. Поле A1                   |
| #FE -  1шт. Адресная метка заголовка  |
|  XX -  1шт. Номер дорожки             |
|  XX -  1шт. Номер стороны             |
|  XX -  1шт. Номер сектора             |
|  XX -  1шт. Длина сектора             |
| #F7 -  1шт. Контрольный код заголовка |
| #4Е - 22шт. Второй пробел|
| #00 - 12шт.                           |
| #F5 -  Зшт. Поле A1                   |
| #FB -  1шт. Адресная метка данных     |
|  XX - 25бшт. Данные                   |
| #F7 -  1шт. Контрольный код данных    |
| #4Е - 22шт. Третий пробел             |
+---------------------------------------+
                                         
    И  так повторяется для всех 16 секто-
ров начиная с 1-го пробела по контрольный
код данных, а в конце остаток дорожки за-
полняют  пробелами #4Е, чтобы размер всейtracks was approximately 6.5 KB. 
                                         
#4E - XX pcs. Trailing space.            
                                         
    On different drives the value is 6.5 KB
ranges from -20 to +20 bytes,
but even on the same drive it
unstable. Therefore, to greatly overestimate the sec-
torus is not possible.  Marked with "??" places are
those that some programmers do
thrown away, although this should not be done.   
                                         
    In my FORMATERe I use this
track formatting type:              
+---------------------------------------+
| #00 - 12 pcs.   !! |
| #4E - 8Opcs. Last space  !! |
| #00 - 12 pcs.   !! |
| #F6 -  Зшт. Поле С2                !! |
| #FC -  1шт. Индексная метка        !! |
| #F7 -  1шт. Контр. код индекса     !! |
| #4Е - 5Oшт. Первый пробел          !! |
| #00 - 12шт. синхронули                |
| #F5 -  Зшт. Поле A1                   |
| #FE -  1шт. Адресная метка заголовка  |
|  XX -  1шт. Номер дорожки             |
|  XX -  1шт. Номер стороны             |
|  XX -  1шт. Номер сектора             |
|  XX -  1шт. Длина сектора             |
| #F7 -  1шт. Контрольный код заголовка |
| #4Е - 22шт. Второй пробел             |
| #00 - 12шт. Синхронули                |
| #F5 -  Зшт. Поле A1                   |
| #FB -  1 pc. Data address label |
| XX - 25 pcs. Data |
| #F7 -  1 pc. Data control code |
| #4E - 22 pcs. Third space |
+---------------------------------------+
                                         
    This is repeated for all 16 sectors,
starting from the 1st space through the control code
data, and at the end the rest of the track is filled
use spaces #4E to make the entire size
horns was approximately 6.5 KB.   
                                         
#4E - XX pcs. Trailing space.            
                                         
    Marked "!!" places are those that
ry differ from some of the used
our standards. Ifdepict graphically
What method can you use to get around scratches?
on the disk or other damage will become
it is clear that this is accomplished by increasing
eliminating or reducing the length of spaces.    
                                         
            Normal            





                                         
 
 
 
 
 
 
 
                                         
          Changed           





                                         
    As we see in the second figure, that
by increasing the first and second spaces, we re-
moved the address label and data field from
there are scratches, and there are scratches in the margins of the spaces
pins have almost no effect on the quality of reading from
disk. In principle, this approach is somewhat
In some cases it is justified, but not always. If
The first space can be increased and decreased
range from 32 to 90 characters, then
in this case, of course, the last space
will be reduced in proportion to the first. Well
2, 3, ..., 16 spaces that are
between the address mark and the data, they must
must be equal and their length cannot be changed
I recommend. If their lengths are different, then reading
the next sector can only happen
for the second approach, which affects the speed
reading and often TURBO LOADER reads them
even slower than normal reading. Except
there is no guarantee that such a form
the mat will provide the required recording quality and
reading.                                  
                                         
    In my version of the format, it is partially pro-
there is a shift from the beginning of the track, but everything is
except for the first and last, standard
us. Spaces added before first field
synchro pulse field,which everyone has
formats of IBM-compatible computers and I
I recommend it for use on the Spectrum. And
If you look closely at the picture, then
it is clear that the scratches have disappeared from the information
fields:                                   
                                         
            Normal            





 PIFORMAT            





                                         
         
                                         
    So, as in the first option, so
and in mine we avoided some scratches, but
without losing quality and speed
when reading and writing a disk.There is also a second way to bypass the king-
pin and bad sectors. It is based on
that these places are formatted like regular ones
sector, but the number of the bad sector is done
non-standard or with the same as in front
him. However, these sectors are not read.  
                                         
             Example one:              
     +----------------------------+      
     |#01 #02 #03 #F7 #04 .... #10|      
     +----------------------------+      
             Example two:              
     +----------------------------+      
     |#01 #02 #03 #03 #04 .... #10|      
     +----------------------------+      
                                         
    In the first case, TR-DOS is no different
melts, but in the second it will miss, because he already
considered #03.                              
                                         
    But this is not always the case if the program
uses its own bootloader and at the same time it
reads, for example, 20 sectors in a row, then
None of these methods will help. Cro-
However, there is a limit on the quantity
sectors on one track, depending
It varies depending on the length of the fields. In addition to these ways
You can also use some other dogs
There are many ways, but they require their own
militarybootloader or duplication on
the second side, as is done in the program
frame"Black Raven".                    
                                         
  Well, that's probably all. If you have
your methods of working with disks, as well as you
If you want to share with them, then write. I them
I will consider them and if they are effective, I will accept them
take into account.                             
                                         
From the editor:I did not rewrite the math
rial in accordance with his views and
convictions on this matter, but decided simply
comment on it. Indeed, according to
You can use spaces to bypass damage to
disk, but here we need to do more seriously -
analysis of the track to find and
way to work around the defect. Time to work
it will take a lot of such a plan, but we are half-
There is a 98% probability of a successful result.
You can determine damage on a disk by
in this way: format the track with code #4E
and then scan into the buffer, where there will be
track times. This is so as not to clog up the RAM yet
one buffer. So, when scanning bi-
you space fields can “move out” in the buffer as well
there may be other codes.  To be error-free
It’s hard to define this code, you need to compare
several consecutive bytes. From observation
for the consequences of scanning, I recommend
I recommend starting the search not from the beginning of the buffer, but
by skipping the first 20 bytes.           
   After you have determined the code, you need to
the same indentation from the beginning of the "probe" buffer
huddle" around the entire buffer, checking the codes.  Then
the place where the other byte will be encountered is
bad place. Identify more defects for
this place, it seems difficult
nom, because the bits can move out again and the code
in the buffer may be different.  Or maybe not
will change. Decide on these situations -
we can with the help of numerous experi-
riments.                                
   After detecting damage, you should
carry out calculations to determine
step between sectors to bypass defects
disk. The step between sectors (spaces) can be
but also change between sectors. I checked this
I had problems with glitches when reading or writing
encountered! If in this case there is no
what is the opportunity to bypass the faulty area,
then offer in your program the most beautiful
as bright a window as you can
depict that "The user should
I can't fucking throw this bullshit disc
to shake one's head and one's people!"  ;-)))      
   Newance: the spaces fields are made to
so that the controller synchronizes. I
I recommend shifting sectors along the track like this:
so that the scratches fall on the beginning of the test
fishing Otherwise there will bethe situation is like in a hundred
good old times when we enjoyed
cassettes - the short piloton makes it difficult
reading file.  The same goes for sectors -
the controller will not have time to synchronize and
the sector header may be lost. Also
I don’t recommend putting a sync space between
the sector header and its data are strongly
different from the standard - is fraught with pos-
consequences: poor quality recording on this
sector and as a result - again masturbation with
PIFORMAT`om...                           
                                         
   And one more thing: somehow I happened to somewhere chi-
ooh-ahh about the fact that 8OOKb
The disk cannot be properly formatted,
so as not to screw up the last sector.  Nonsense
all this! It’s possible, as much as possible! Enough
trim whitespace fields by 20 bytes each
and everything will work out without any problems! Quality of work
bots with disk will not change. This is what I tried
shaft in full on the disc with our game
"Black Raven. New Missions".            
                                         
   Well, Picon, do you implement this in practice?
tick?  Considering that in recent years
there is a shortage of new or high-quality
new used floppy disks for5.25", work sometimes
occurs on “dead” disks and without yours
We can't do without programs!  We are waiting for a new one
versions...                                
                                         
                  -----                  
                                         
   Beeper protection system    
           v1.0 beta           
                                         
(C) Mg.Beeper                            
-------------------------------------------------------
 This program is very useful in
when it is necessary to protect the disk
role or code from arbitrary viewing
ra.  After protecting the disk with this program
it is impossible to view what files are there
on disk or run some program
gram. After loading the program, the screen
will not appear on the monitor, a menu consisting of
the following inscriptions:                     
                                         
           1. Setting protection           
            2. Removing protection             
             3. Types of protection              
              4. Information              
               5. Output                  
                                         
       Setting protection        
  After selecting this item, you will be offered
You must enter a password of up to 10 characters,
including numbers and punctuation marks. If
the disk already has protection, the corresponding
current message.                      
                                         
         Removing protection         
  This item will allow you to remove protection,
if the disk is protected.                       
                                         
          Types of protection          
  This item is not implemented in this version.
van.                                     
                                         
          Information           
  After selecting this item you will find outsome information about the program.        
                                         
             Output             
  After selecting this item,
checking for presence in memoryReal Coman-
der`a and, if it is present in memory, then
starts.  Otherwise done
reboot TR-DOS.                     
 In the next version, first of all there will be
the item"types of protection" is implementedusing
which it will be possible to choose a variety
the number of ways to protect a disk or
file.  Complete interception of disk errors.
Increase the number of characters entered for
password. Improved protection.