Brakes on the Sprinter's chart?
ZXNet echo conference «zx.spectrum»
May you have eighty-three bags of hryvnia, Andrew!
Once upon a time, specifically Sunday January 25, 1998 at 01:15 Andrew
Savichev wrote All:
>> maximum 500 tons from a good program in 4 months, this is for programmers.
AS> Software will be paid for as sales go (100% protection from
AS> copying - guarantee of the general director! ) Where did you get 500 rubles from
AS> the ceiling? ;)
We've already heard about 100%, 120%, 200% copy protection... Everything was broken.
Something is easier, something more difficult, but absolutely everything can be broken.
Can you give a detailed description of the principle on which “100% copy protection” is based?
Besides, those who will now (?) write programs for it will receive the maximum amount of money in the first year
200 (at best!) computers sold. This is not
much and is unlikely to please the authors, especially since if the program is cheap,
the author will get almost nothing, and if it’s expensive, they will hack it, and even less
they won’t get anything.
>> word... the memory works at 7 MHz, the maximum theoretical
>> accelerator performance is 3,500,000 bytes per second or 70,000 bytes
>> in one int (frame)
AS> Are you planning on redrawing _the entire_ screen _every frame_?
What about toys like rally games, where you have to scroll the entire screen? Or is
hardware scrolling implemented?
AS> A anddon't do it! in 256x192/256 mode everything is ok! definitely
AS> I saw with my own eyes!!!
And how about forgetting mpeg once and for all?
AS> Windows and other primitives, by the way, will work much faster
AS> due to hardware filling! So, write ZX-Windows, gentlemen!
And who will pay for it and how much?
AS> Who cares, and secondly, there are 10 million pussies in Russia (?), and all over the world
AS> 600 million (?), and there are still 10 Sprinters in the whole world!
AS> Why are you like these same ones...a baby in a cradle...and you his to a brothel
AS> house? Eh...fathers,....
I don’t understand the meaning. I still don’t understand why they do it? Who will buy it? And
they haven’t convinced me yet that it’s worth the money they’re asking for it.
With respect, Tim. [Team Aries - Rulez Forever]
Get Msg, Andrew!
25 Jan 98 01:15, Andrew Savichev reported All about {Slowness on the graphics of
Sprinter?}:
AS> And modes with high resolution on the entire screen for now for photos and “background
AS> in games will be normal.
I wonder how? This is not Dandy. If the foreground heroes are displayed in a lower resolution, and the background of the game is in a higher resolution, then again there will be a “squareness of colors” ((c) Denis Parinov:), only this time a special one - sprinter-like. IMHO, different resolutions can be made separately, for example
for the toy display window and for the control panel/frame. And “mixing” them
in the display window itself is difficult (IMHO).
Warm greetings, Slava!
You can also get by using memory (after all, (256)512k video memory and
4Mb main). Those. keep a lot of
individual states for each high-resolution sprite, slip them into backup screens, and they are “reselected”
at a breakneck speed (but still there are not 60 of them? :( ), although it is still better to
redraw only the sprites and, due to their relatively small sizes,
get out of it (but they should be very small so as not to slow down ;) )
Hmm... well, of course... hmm ;)
>
>
> Warm greetings, Slava!
Sincerely, Andrey Savichev / CGS
░▒▓██ I am glad to welcome you, Tim! ██▓▒░
█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░
█ Once upon a time, Monday January 26 1998 18:03, Tim Yunaev
█ wrote for Andrew Savichev:
TY> We have already heard about 100%, 120%, 200% copy protection... Everything
TY> broke. Some things are easier, some things are more difficult, but absolutely everything is breakable. Can you provide a detailed description of the principle on which "100%
TY> copy protection is based"?
Detailed - not possible. This is program protection - that means secret. And the principle is simple.
Changing hardware for a specific program. The change is known only to the author
of the program. Hacking the ALTRA firmware will cost a couple of million dollars. Next
to understand the circuit, the addressing of ports, data, commands, unknown commands embedded in the PLM.... Such a hack is UNREAL, because... will cost more than the profit from
it.
░▒▓██ I am glad to welcome you, Paul! ██▓▒░
█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░ ░▒▓█▓▒░
█ Once upon a time, Sunday January 26 1997 00:00, Paul Falcon
█ wrote for Andrew Savichev:
...
PF> see above, I’m not going to shit on the sprinter, but what was
PF> agreed back in May has still not been done and is not even planned.
What hasn’t been done?
Ivan is that you?
...why were you telling Tim Yunaev about the Brakes on the Sprinter chart? ?
IM> commands, in unknown commands built into the PLM.... Such a hack is UNREAL,
IM> because. will cost more than the profit from it.
Hacker's rule: If the protection cannot be broken, then it needs to
be copied (well, stupid hacker, stupid ;)))
And you do not have 100% copy protection. Yes, and no one has.
IM> Yes! Hardware scrolling of all and parts of the screen. For example, half the screen
IM> can be scrolled up, a quarter down, and the other quarter to the left plus
IM> redraw something on it...
Is it possible to scroll some small piece? Or strictly
in halves? What about free form? Or just
rectangles? ;)
Good Luck...
... THE way to accelerate Windows is THROUGH one!
Get Msg, Max!
29 Jan 98 11:28, Max Romanoff reported to Ivan Mak about {Slowness on the graphics
Sprinter-a?}:
MR> Hacker's rule: If the protection cannot be broken, then it needs to be
MR> copied (well, stupid hacker, stupid ;)))
Worse - if the program is copied, there is no need to break it...
Warm greetings, Slava!
VM> Worse - if the program is copied, there is no need to break it...
It is often more difficult to copy than to break it. Not to mention the fact that pirates need not just copy one floppy disk for an hour or two, but multiply them in batches. The latest
tendency among hackers is to break it exactly to such a state that it can be copied with
hurray.
VM> Warm greetings,
VM> Slava!
Sincerely, Dmitry (OLDMAN).
ZXNet: 095/100.1
old...@i-connect.ru
May you have eighty-three bags of hryvnia, Ivan!
Once upon a time, specifically Wednesday January 28, 1998 at 07:37 Ivan Mak
wrote by Tim Yunaev:
IM> Detailed - impossible. This is protection of programs - that means it is secret.
So by this you want to say that as soon as the principle becomes known,
the protection will become easy to hack?
This is _not_ unbreakable protection.
IM> And the principle is simple. Changing hardware for a specific program. The change
IM> is known only to the author of the program.
Not only. Also for anyone who hacks this program.
IM> Hacking the firmware for ALTRA will cost a couple of million dollars.
Will the firmware altera be supplied with the program? Or will the firmware be
modified by the program itself?
Two ways - either analyzing the code of the program itself (troublesome, but 100% reliable), or
a good logic analyzer/computer with fast ports on the Z80 legs, then analyzing
the state of the legs... well, you get the idea :)
IM> Next, understand the circuit, the addressing of ports, data, commands, etc. IM> unknown commands built into the PLM.... Such a hack is UNREAL, because
IM> will cost more than the profit from it.
Any hack is real, alas.
MR> And you don’t have 100% copy protection. And no one has.
If you copy a disk atom by atom, of course, there will be no protection. So, there is
no protection against this and cannot be.
If there is a way to make a disk unique, add to it a unique data decryption scheme, you will get pretty good protection.
...
MR> Is it possible to scroll some small piece? Or purely
MR> in halves? What about free form? Or just
MR> rectangles? ;)
Rectangles 8 by 8 points can be moved from one familiarity to another
by rewriting two bytes.
All other pieces are made up of 8x8.
VM>> Worse - if the program is copied, there is no need to break it...
DG> It is often more difficult to copy than to break it. Not to mention the fact that pirates
DG> need not just copy one floppy disk for an hour or two, but multiply them in batches.
The latest
DG> tendency among hackers is to break exactly to such a state that it is copied
to
DG> cheers.
Dima, they are pirates, pirates, there is no smell of hackers here...
▌▌║▌█▐│▌▌▐▐ WiTh The BeST wIsheS fROM CREATOR product
▌812/03.00▐ Powered by Cyrix 6x86L 200+/16DIMM/S3TrV2 2MB/1.6GB
... the glitch is not a sparrow , flew out - kill !
-+- SMM version 1.05
DG>> pirates need not just copy one floppy disk for an hour or two, but multiply
DG>> them in batches. The latest trend among hackers is to break it exactly to such a state that it can be copied with a bang. But by and large - they are goats, and let them remember this (or remember). Just don't point at me. Sinful, but sincerely
repented... and he didn’t do much harm ;)
PF> ▌▌║▌█▐│▌▌▐▐ WiTh The BeST wIsheS fROM CREATOR product
TY> Will the flashed altera be supplied with the program?
TY> Or will the firmware be modified by the program itself?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is !
TY> Two ways - either analyzing the code itself programs (troublesome, but 100%
TY> reliable), or a good logic analyzer/computer with fast
TY> ports on the Z80 legs, then analysis of the legs... well, you get the idea :)
Okay. Let's break it down.
1st. The program overloads 16 kilobytes of rubbish.
2nd. A hardware reset of the processor occurs, to which an unknown circuit is connected and work begins. Not only the processor, but also the coprocessor inside the PLM. Pulses on the legs of the PLM with a resolution of 12ns.
How will we break it?
We will buy a super analyzer for $2 million, as mentioned above.
Get Msg, Ivan!
12 Feb 98 05:43, Ivan Mak reported to Tim Yunaev about {Slowdowns on the
Sprinter chart?}:
IM> 1st. The program loads up 16 kilobytes of rubbish.
IM> How are we going to break it?
Let’s write a program that copies this rubbish (that is, break not the program, but the
distribution)
Warm greetings, Slava!
Somehow a long time ago, specifically Thursday February 12, 1998 at 05:43 Ivan Mak
wrote by Tim Yunaev:
TY>> So, by this you want to say that as soon as the principle
TY>> becomes known, the protection will become easy to hack? This is _not_ unbreakable
TY>> protection.
IM> Interesting movie. And where _in_principle_ can there be such protection that it
IM> cannot be broken if everything is known about it?
Not necessarily everything. Remember - protection using the R register was also quite complex until they learned to emulate it. After the algorithm
increase became known, the protective effect of it became zero and leads only
to a small loss of time.
And there are a lot of algorithms, for example RSA. Even if you know the algorithm and have a set of
digits before and after encryption, you will not be able to find the secret key.
The “hardware” plugs are keys like Sentinel with a _competent_ API (and not what
the manufacturer slips in). The essence is an unknown function, hardwired into the key (there are no ways to get it out of there, like a class). Receives two 32bit
numbers in parameters and returns one 32bit. You can store a complete file of values for each
number with the result, but it will take up a lot of space.
And even then, this does not provide 100% protection.
Ivan is that you?
...why were you telling Tim Yunaev about the Brakes on the Sprinter chart? ?
IM> Interesting movie. And where _in_principle_ can there be such a protection that it cannot
IM> be broken if everything is known about it?
if the protection is more difficult to break than to copy, they will copy.
IM> Only if the author tells someone about it, as you ask above.
we are just trying to find out what is it based on in order to dispel your
bright hopes for 100% protection.
IM> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is !
so what? And the program must load first. This is where they
break it.
IM> Good. Let's break it.
IM> 1st. The program loads 16 kilobytes of rubbish onto your forehead.
question: who will do this? I mean the firmware? Spectrum programmer? How?
IM> 2nd. A hardware reset of the processor occurs, to which an unknown circuit is connected
IM> and work begins. Not only the processor, but also
IM> the coprocessor inside the PLM. Impulses on the legs of the PLM with a resolution of 12ns.
IM> How will we break it?
hint: the percentage is the same! -> we break it down in order.
IM> Who will do something that has no (monetary) meaning?
how not? for the purpose of pirated copying and sale. there is a benefit.
Good Luck...
... C:\dos C:\DOS\RUN C:\DOS\RUN\WINDOWSC:\DOS\RUN\SLOW
IM>> can’t it be broken if everything is known about it?
MR> if the protection is more difficult to break than to copy, they will copy.
Somehow, I’ll make a floppy disk and give it to you for you to copy. Can you do it?
MR> We are just trying to find out what the basis is in order to dispel your
MR> bright hopes for 100% protection.
We will not create an unnecessary argument. I just don’t want to give away what is being discussed under the sign:
┌─────────────────────┐
│ Top Secret │
└─────────────────────┘
[killed by uncle with AK-74 and grenade launcher]
Ivan
Ivan is that you?
...why did you tell me about Soft Protection?
IM> Somehow, I’ll make a floppy disk and give it to you so you can copy it.
IM> Can you do it?
yes, but on the condition that it will be real protection, which NORMAL
will work on computers, and not just like that.
IM> Let’s not start an unnecessary argument. I just don’t want to give away what is being discussed under the sign:
IM> ┌─────────────────────┐
IM> │ Top Secret │
IM> └─────────────────────┘
most likely it only seems 100% to you protection, because in fact
it's the other way around...
Good Luck...
... Hollow chocolate bunnies have no calories.
IM> Let's not start an unnecessary argument. I just don’t want to give away what is being discussed
IM> under the sign: ┌─────────────────────┐ │ Top Secret
Why? He can tell you a lot of sensible things about the copyability/non-copyability of floppy disks... For example, confirm/refute the non-copyability of 1.44
disks on the Amiga.
Warm greetings, Slava!
Hello Vyacheslav.
Wed Feb 25 1998 00:34, Vyacheslav Mednonogov wrote to Ivan Mak:
IM>> Let’s not start an unnecessary argument...
VM> Why? He can tell you a lot about the copyability/non-copyability of floppy disks
VM>... For example, confirm/refute
VM> the non-copyability of 1.44 disks on the Amiga.
Max has already answered me. :)
1.44 disks on the Amiga are copied if you install the appropriate drive.
Track to track, as I believe.
Ivan
Get Msg, Ivan!
26 Feb 98 02:44, Ivan Mak reported to Vyacheslav Mednonogov about {Soft Protection}:
IM> Max has already answered me. :)
IM> 1.44 disks on the Amiga are copied if you install the appropriate disk drive.
That's why they are all on the 720 :) You can also copy them on the Spectrum, if
you install the appropriate disk drive and controller ;))))
Warm greetings, Slava!
VM> That's why they all sit on the 720 :) So you can copy them on the Spectrum
VM> if you install the appropriate drive and controller ;))))
Not all of them. Many people use HD drives, and in order to copy
a disc, a lot of people can buy HD 5.25 for 50 rubles.
Regards, Alex from FFC COMPUTERS.
>e-mail: as...@usa.net
Ivan is that you?
...why did you tell Vyacheslav Mednonogov about Soft Protection?
IM> Good track, as I think.
yes. But why do you need an Amiga if you will protect these discs on a sprinter? A sprinter is taken and a pile driver is written for this purpose. cheap
and cheerful. and most importantly - quickly.
Good Luck...
... 24 hours in a day...24 beers in a case...coincidence?
Vyacheslav is that you?
...why did you tell Ivan Mak about Soft Protection?
VM> Why? Regarding the copyability/non-copyability of floppy disks, he can tell you a lot
VM>... For example, confirm/refute
VM> the non-copyability of 1.44 disks on the Amiga.
the Amiga may have nothing to do with it if these disks are written on the
Spectrum.
Good Luck...
... Madness takes it toll. Exact change, please.
VM> That's why they all sit on the 720 :) So on the Spectrum you can copy them
880.
VM> if you install the appropriate drive and controller ;))))
about that and the market.
Good Luck...
... PC User? Line On The Left, One Cross Each.
Hello Max.
Wed Mar 04 1998 00:47, Max Romanoff wrote to Ivan Mak:
MR> yes. But why do you need an Amiga if you will protect these discs on a
MR> sprinter? A sprinter is taken and a pile driver is written for this purpose. cheap
MR> and cheerful. and most importantly - quickly.
Quick copying will not work. The program will not know the structure of the track, and simply reading the entire track will not copy it. (This is how the track is arranged on a
protected floppy disk.)
Ivan
Ivan is that you?
...why did you tell me about Soft Protection?
IM> It won’t work to copy quickly. The program will not know the track structure,
good. the program will not know the first time. then they tune it
UNDER A SPECIFIC floppy disk-original, and the whole thing begins to be copied at such
speed that snot will fly.
IM> but by simply reading the entire track it will not be copied. (This is how the track
IM> is arranged on a protected floppy disk.)
Is this how the track is made on the sprinter? on the sprinter and copied.
You don’t even need an Amiga.
Good Luck...
... Double your disk capacity: DELETE WINDOWS!
Hello Max.
Sat Mar 07 1998 21:29, Max Romanoff wrote to Ivan Mak:
MR> Is that how the track is made on the sprinter? on the sprinter and it will be copied.
MR> You won’t even need an Amiga.
To do this you will have to hack the hardware. And even a crowbar will not help with this. The disc is read
entirely only from the program, which is recorded on the same floppy disk. And there
first of all, the hardware changes and after that hacking will be more expensive than gold.
Ivan
IM> To do this you will have to hack the hardware. And even a crowbar won’t help with this. Disk
why hardware? You have a VE-Gashka in it, right?
IM> is read in full only from the program, which is recorded on the same floppy disk and
IM>. And there, first of all, the hardware changes and after that hacking
IM> will turn out to be more expensive than gold.
pf... back to what was printed: breaking the firmware is a couple of
trifles. after all, from the beginning the program must be launched from the STANDARD
FORMAT -> at the very beginning it is DEFENSELESS.
Good Luck...
... MS-DOS Causes deafness and hair loss when used by laboratory rats.
IM>> floppy disk and recorded. And there, first of all, the hardware changes and after
IM>> this hacking will turn out to be more expensive than gold.
MR> pf... back to what was printed: breaking the firmware is a couple
MR> of trifles. after all, from the very beginning, the program must start from the STANDARD
MR> FORMAT -> at the very beginning it is SECURITY-LESS.
_How_to_break_the_firmware_?
Take a block from an unprotected program and load it from another. Then everything comes up,
because after changing the firmware, you also need a _changed_ one, i.e. coded
program. The code itself is in the firmware file in such a form that it is impossible to pull it out from there. The program is written in this code. So no disassembly will help to crack it. And after rebooting the firmware with this program, it
starts and there is no internal device for hacking in it.
Ivan
IM> It's worth checking. What's next?
hehe, that means HA ANYONE and copy it. Is the idea clear?
IM> _How_to_break_the firmware_?
and how to load it? so break it.
IM> Take a block from an unprotected program and load it from another. Then everything
IM> comes to a standstill, because after changing the firmware, you also need a _changed_ i.e.
IM> encoded program. The code itself is located in the firmware file in such a form that it is impossible to pull it out from there. This code contains
what code is in the firmware file? Is he corrupting the memory using cunning
algorithms before giving it to the processor, right?
IM> program. So no disassembler will help you crack it. And after
IM> rebooting the firmware with this program, it starts and there is no
IM> internal device for hacking in it.
You are chasing something. and it looks like I'm confused in this...
Good Luck...
... Friends don't let friends use MS-DOS.
IM>> Then everything stops, because after changing the firmware you need and
IM>> _changed_ i.e. encoded program. The code itself is located in
IM>> the firmware file in such a form that it is impossible to pull it out from there.
IM>> In this code is written
MR> what code is in the firmware file? Is he corrupting the memory using cunning
MR> algorithms before giving it to the processor, right?
He is corrupting the memory using cunning algorithms. And breaks it back. But it is impossible to extract the code itself from the firmware file. The code is not for the processor, but for the PLM. It is
three-dimensional, if not more.
IM> I’m probably an idiot, but the idea is not clear.
I explain:
If the protection is done using VG93, then using Vg93 it is
copied.
IM> It is loaded simply. 16k code block, inside of which there is a mishmash of bits
IM> understandable only to PLM.
who loads it?
IM> It corrupts memory using cunning algorithms. And it opens up back. And it is impossible to extract the code itself
IM> from the firmware file. The code is not for the process, but for
IM> PLM It is three-dimensional there, if not more.
a.... understandable... this is already more interesting... but still, read the beginning
of the letter... there is no point in doing any kind of bells and whistles in iron-clad protection,
if the media will be copied anywhere.
IM> No I'm confused, and you don't understand. You are loading an encoded program block,
you just didn’t talk about it. Now, when I clarified whether it is corrupting the memory, everything became clear.
IM> which will be decoded only after rebooting the circuit. The encoding
IM> of the program is unknown to you. And you don’t have a coded debugger. And therefore
IM> therefore, after loading a new circuit, there is nothing in memory except the
IM> program being launched. Is the idea clear? (c) MR
now yes.
p.s. This means they won’t break it, but copy it. it's easier.
Good Luck...
... RAM disk is not an installation procedure.
Greetings, Max!
є─────────────────────────── ──────────────────────── MR> I explain: [about PLM firmware] MR> now yes. Ivan, with Big Greetings. ZX-Spectrum is #10 years old!
║ On
╙────────────────
MR> If protection is done using VG93, then with the help of Vg93 it
MR> is copied.
Here you need to use all known (and unknown) methods of protecting floppy disks. For this purpose, Sprinter has some trick. Discs are recorded using a different circuit. Which is not in the program itself.
MR> who loads it?
Anyone. From anywhere. You need to throw 16k into a certain bank of RAM and
reset the machine. (Software reset.) Then a simple program runs in the ROM
which loads the firmware.
I will add that if the protection is done using the 8272, then with its help it is
copied.
As a last resort, there are ready-made software and hardware systems for
copying floppy disks, which can be used to copy any floppy disk that is not physically damaged.
There is indeed one type of protection that is copied poorly (out of 5 copies, two are functional). And the second disadvantage is that these complexes usually copy very slowly
(floppy disk per hour), which is not very convenient for mass replication.
IM> Here you need to use all known (and unknown) methods of protecting
IM> floppy disks. For this purpose, Sprinter has some trick. Recording
IM> discs is done using a different scheme. Which is not in the program
IM> itself.
So, it will be possible to record the same floppy disk on another Sprinter, do you agree?
P.S. imho, the dispute is reaching a dead end.
With respect, Tim. tyu...@usa.net [team Aries are Rulez Forever]
IM> Here you need to use all known (and unknown) methods of protecting floppy disks.
IM> To do this, Sprinter has some trick.
IM> discs are written using a different scheme. Which is not in the program itself.
damn it, so what? writes VG93, right? or again, MFM xorim?
Good Luck...
... Friends don't let friends use Windows.
Greetings, Tim!
є─────────────────────────── ──────────────────────── TY> May you have eighty-three bags of hryvnia, Ivan! TY> P.S. imho, the dispute is reaching a dead end.
║ On
╙────────────────
It won’t be enough. :)
It seems like that. The problem of protecting software on floppy disks is a universal one. If there were a simple solution, this protection would have existed long ago. The sprinter simply gives a few more
opportunities for developing this defense. And with the help of “complexes”
any defense can be unraveled.
TY> P.S. imho, the debate is reaching a dead end.
Vano is just hiding the facts.
Good Luck...
... TRUE PeeCee Multitasking = 3 PCs and a chair with wheels.
IM>> floppy disks. There is a trick for this in Sprinter. Recording
IM>> discs is performed using a different scheme. Which is not in the
IM>> program itself.
MR> damn it, so what? writes VG93, right? or again, MFM xorim?
The VG93's harness is on the PLM. The recording program changes the scheme and the sequence of pulses written to the disk changes. When reading, the scheme changes,
but differently. So that the program cannot be written back. In the program itself there is no
opportunity to record using an encoded method. Just straight.
P.S. How to xorize MFM?
IM> P.S. MFM xoring, what is it like?
and so, since you have it wrong, it means it is copied.
Good Luck...
... Ever stop to think, and forget to start again?
May you have eighty-three bags of hryvnias, Max!
Once upon a time, specifically Thursday April 09, 1998 at 02:15 Max Romanoff
wrote by Tim Yunaev:
MR> well, since yours is wrong, it means it’s being copied.
We need to finish the topic. When I have time (and I will definitely have time for this), I’ll make a floppy disk and give it to you so you can copy it. We'll see there. :)
TY> Do they exist?
but after much torment, I finally pulled out from it that the firmware
can corrupt the processor data. maybe there's something here? although, I think there
there is nothing there... if there is MFM, we will copy it.
Good Luck...
... Be nice to moderators. They HATE that!
IM> We need to finish the topic. When I have time (and for this I will definitely
IM> have time), I’ll make a floppy disk and give it to you so you can copy it. We'll see there
IM>. :)
come on. soon :)
Greetings, Max!
є─────────────────────────── ──────────────────────── MR> but after much torment, I finally pulled out of it that the firmware And if you copy RLL?
║ On the day
╙────────────────
MR> can corrupt process data. maybe there's something here? although, I think, there
MR> there is nothing... if there is MFM, we will copy.
Or MFM, but with a non-standard frequency?
IM> What if you copy the RLL?
ELEMENTARY. But how do you record it through VG93?
IM> Or MFM, but with a non-standard frequency?
with what non-standard frequency? in principle, you can copy all formats.
exceptions - scratched (checked) and jumping length
(checked)...
Good Luck...
... Microsoft, does that mean small and limp?
MR> with which non-standard one? in principle, you can copy all formats.
Well, let's just say that the unformatted volume on a track is not 5Kb or 10Kb, but 7,
for example ?
Ivan, with Big Greetings.
IM> Is the noise (digital noise) signal on the floppy disk also copied?
Any digit from the media is copied. it turns out a complete bitwise copy
of the track.
IM> Well, let's say that the unformatted volume on the track is not 5Kb or 10Kb,
IM> but 7, for example ?
see above.
Good Luck...
... Ethernet (n): something used to catch the etherbunny
IM>> not 10Kb, but 7, for example ?
MR> see above.
If everything is so, then protection without mechanical defects on the disk is impossible.
Ivan, with Big Greetings.