Shalaev emulator

People! Well, how can I read native TR-DOS disks in the subject?
I'm stuck, they can't read them in the emulator, on SPECCY - formatted in
the emulator - DISK ERROR.
Both computers have HD 3.5" (by the way, working with SPECCY is a pleasure
).
Maybe Mr. Shalaev will finally finish his emulator to compatibility
with "PROFI+".
P.S. Please do not suggest dragging and dropping disks using a method like:
copying the image file of the TR-DOS disk (fortunately PROFI has enough memory for
this) to the MSDOS disk, because firstly the question is not
in this, and secondly, it arises not only for me.

Bye.
Max.

It was like this: Maxim_Gorkov 09 Nov 97 at 15:06 was pushing speeches to All.
Well, I wrote it.

M> People! Well, how can I read native TR-DOS disks in the subject?
M> I'm stuck, they can't be read in the emulator, on SPECCY - formatted in
M> the emulator - DISK ERROR.
M> Both computers have HD 3.5" (by the way, working with SPECCY is a pleasure
M>).
Well, if 2 are 3.5" then try to restore the disk from a file in the subject, and then use Specki to erase(!) all the files, write down new ones that need to be transferred, and
again, make a disk image in the subject. It works for me.
M> Maybe Mr. Shalaev will finally finish his emulator to be compatible
M> with "PROFI+".
There's nothing to finish there, the disks just can't be read, IMHO, because of the wrong
distance between sectors, which turns out, IMHO, because of all sorts of bells and whistles,
like Fast Disk, etc.
M> P.S. Please do not suggest dragging and dropping disks using a method like:
M> copying the image file of the TR-DOS disk (fortunately PROFI has enough memory for
M> this is enough) to the MSDOS disk, because firstly, the question is not
M> in this, and secondly, I am not the only one who has it. rOOleZZZZ]
╚══─══─═─═─── ── ─ ─ ─

Sunday November 09 1997 15:06, Maxim_Gorkov ─── All:

MG> People! Well, how can I read native TR-DOS disks in the subject?
MG> I'm tired, they can't be read in the emulator, on SPECCY - formatted in the
MG> emulator - DISK ERROR.
MG> Both computers have HD 3.5" (by the way, working with SPECCY is a pleasure
MG>).
Aren't the flops installed crookedly? Are the holes sealed? Are the adjustments on the flops the same? ;))
MG> Maybe Mr. Shalaev will finally make his emulator compatible
MG> with "PROFI+".
Why not scorp? :))
MG> P.S. Please do not suggest dragging and dropping disks using the method like:
MG> copying a disk image file TR-DOS (fortunately PROFI has enough memory for
MG>) to the MSDOS disk,
But the mulator doesn’t work with live disks, only with images on MS-DOS
disks ;))
MG> because, firstly, that’s not the question, and secondly, it’s not just me
MG>.
What about the screw?

Good luck ! Evgeny.

■ The night is shorter than the day... The day will kill me... The world of illusions is burning in it (C) Aria.

Tuesday November 11 1997 20:25, Alex Kovrigin ─── Max Lanskih:

ML>> There’s nothing to finish there, the disks just can’t be read, IMHO, because of
ML>> the wrong distance between sectors, which turns out, IMHO, because of
ML>> all sorts of bells and whistles, like Fast Disk, etc.

AK> FastDisk has nothing to do with it, you just need to format disks on real speccy
AK> not in TR-DOS, but with all sorts of fancy FUT, DCU, etc.
Well, almost, almost... Max said almost correctly - the synchro
series between sectors are too small. And the DCU in Fast Disk mode creates exactly this,
but in Ordinary mode (or whatever? I forgot already), the distance is acceptable for
IBM.

EM> Well, almost, almost... Max said almost correctly - too small
EM> synchro series between sectors. And the DCU in the Fast Disk mode just
EM> creates something similar, but in the Ordinary mode (or whatever? I forgot already),
EM> the distance is acceptable for the IBM.

It is immediately clear that the person did not climb inside...

The Fast and Ordinary modes differ only in one thing:
Fast - the sectors on the track are in a row - 0, 1, 2, 3...
Ordinary - 0, 8, 1, 9, 2, 10... That is, Interleave 1:2.

As practice has shown, the Speck controller is quite capable of raking the data,
which is why Fast appeared, which allows you to count the entire track in one revolution of the disk, and
not
in two, like normal...
(and such a thing as ADS can make a shift between the sides and cylinders)

Now about compatibility with PC.
VG93 does not have the “Format track” command, but it has the “Record
track” command. Actually, Spec formats the track by recording its “blank” onto a cylinder. The whole problem of incompatibility is that from the index marker AKA
a hole
in the disk to the beginning of the first sector there is some distance, scientifically - GAP.
Standard formatting of Speck leaves not enough space - the VG93 has time to
“catch” on the data, but the PC does not. Accordingly, there is no hindrance to increase
the first GAP, which was done in later versions of DCU &FUT.
(Aw! Who threw TRDOS 6.06? What about you with the first GAP???)

Here. If anyone from the public wants to say that I'm wrong, don't bother writing soap. I will not read it, much less respond. The answer is already
ready - RTFM.

PS: For those who didn’t believe it, format a bunch of disks, whatever you can, and then
try the ADS format (a cool thing - thanks to the author!).

PS: At that time, I created a TRDOS disk formatter for... DVK/RT11
(for the MY controller).
Disks wrapped with it were readable without any problems and on PC, and on ZX...

With best wishes - Andrey Khristov (ha...@robin.alt.ru)

[Team Horse Aviation] [Team beer, girls & sofa]
[Team For Garage] [Team Khasansky border guards]

All my spec drives are formatted in DCU as Fast. And everything is readable.
I tried to format it in bare TR-DOS - they are not readable.

P.S. I don’t understand how this interval value can affect the size of the synchro series.

__ With cre...@online.nsk.su
__/// Best 39:245/1.0@amiganet
\XX/ Regards 2:5000/28.19@fidonet

Greetings, dear Andrey!

One day, namely Friday November 14, 1997 21:58, a certain humanoid calling himself
Andrey Khristov wrote something intelligible to the name Evgeny Milun:

AK> Ay! Who threw TRDOS 6.06?
AK> What about you with the first GAP???)
Tnx !
I discovered problems with Shalayev, consider it fixed today and I’ll inform the developer
(before this the whole problem was in temporary absence programmer, now
the program is functioning successfully, although another problem has appeared...)

With respect, Andrey Mihaylow

AK> It is immediately clear that the person did not climb inside...
He did, but a very, very long time ago - in the year 92-93. ;)))
AK> The Fast and Ordinary modes differ only in one thing:
AK> Fast - sectors on the track are in a row - 0, 1, 2, 3...
AK> Ordinary - 0, 8, 1, 9, 2, 10... That is, Interleave 1:2.
I just forgot... :(( In addition, he uses TR-DOS a procedure, to
the input of which only the sector number is transmitted.

AK> As practice has shown, the Speck controller is quite capable of raking data,
AK> which is why Fast appeared, which allows you to count the entire track in one revolution of the disk,
AK> and not in two, like normal... (and such a thing as ADS can make a shift
AK> between the sides and cylinders)
We know that. :))

AK> Now about compatibility with PC.
AK> VG93 does not have the "Format track" command, but it has the "record
AK> track" command. Actually, Spec formats the track by recording its “blank” onto the
AK> cylinder. The whole problem of incompatibility is that from the index marker AKA
AK> hole
AK> in the disk to the beginning of the first sector there is some distance, scientifically - GAP.
AK> The standard formatting of Speck leaves not enough space - the VG93 manages
AK> to “catch” on the data, but the PC does not.
Well, I said almost the same thing. :)
AK> Accordingly, nono hindrance
AK> to increase the first GAP, which was done in later versions of DCU & FUT. (Ay!
AK> Who threw TRDOS 6.06? What about you with the first GAP???)

AK> Here. If anyone from the public wants to say that I'm wrong, don't
AK> bother writing soap. I won't read it, much less -
AK> answer. The answer is already ready - RTFM.
Why do you think so about people?

AK> PS: For those who didn’t believe it, format a bunch of disks, whatever you can, and then
AK> try the ADS format (a cool thing - thanks to the author!).
AK> PS: In those days, I created a TRDOS disk formatter for... DVK/RT11
AK> (for MY controller).
So what? And back in 1994 I wrote a program that heals disks. ;))
AK> The disks spun by it were readable on both the PC and the ZX without any problems...
This means that the length of the sync pulses was successfully selected. For example, take a disk
formatted in Scorpio Shadow...

AK> All my Spec disks are formatted in DCU as Fast. And they are all readable.
I got a little confused. :((
AK> I tried to format it in bare TR-DOS - it’s not readable.
But this is strange - the DCU almost exactly calls the TR-DOS
procedure.
AK> P.S. I don’t understand how this interval value can affect the size of
AK> synchro-series.
Exactly... The whole joke is that the DCU format differs from the naked Dos format only in interliving.

EM> So the length of the synchronization pulses was chosen successfully. For example, take
EM> a disk formatted in Scorpio's shadow...

You'll laugh, but I didn't select anything.
I simply passed all the parameters needed for formatting to the controller.

AK> You will laugh, but I didn’t select anything.
AK> I simply passed all the parameters that were needed for formatting to the controller.
Well, it’s clear that “I just passed it to the controller.” But, in what way did he format - create an image of the track, and then give the formatting command and call the procedure for sending bytes to the controller? Or called TR-DOS
procedure, passing it a pointer to the interleaving table? If it's 1st, then that's what I'm saying - the image of the path was successfully chosen. And if it’s 2nd, then everything should
work like that.

__ With cre...@online.nsk.su
__/// Best 39:245/1.0@amiganet
\XX/ Regards 2:5000/28.19@fidonet

AK>> formatting.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

EM> Well, it’s clear that “just passed controller". But in what
EM> way did he format - create an image of the track, and then give the
EM> formatting command and call the procedure for sending bytes to the controller? Or
EM> called the TR-DOS procedure, passing it a pointer to the interliving table
EM>? If it’s 1st, then I’m saying that the image of the path was successfully chosen. And
EM> if the 2nd, then everything should work like that.

If you really have such a cool memory, you probably forgot the beginning of the conversation.
So: on a DCK, a disk is formatted in only one way: by sending the controller
the “Format Track” command with an array of sector descriptions. The controller generates all GAPs itself, without my help.

EM>> Well, it’s clear that “I just passed it on to the controller.” But in what way did you format it - create an image of the track, and then give the formatting command and call the procedure for sending bytes to the controller? Or
EM>> called the TR-DOS procedure, passing it a pointer to the interliving table
EM>>? If it’s 1st, then I’m saying that the image of the path was successfully chosen. A
EM>> if it’s 2nd, then everything should work like that.