Glitch in RC 1.9

Finally, I found a glitch in the subject! Or rather, not me, but my brother.
Honestly, it’s so nice.

Specially for REAL: if you open the RAM disk, then create a left file there
with a length of 255 sectors, and then change the starting sector in the doctor to some thread
#3C for example, then by viewing the file you can look at the RC and edit
it to your liking (for example Replace REAL with ....).

People, tell me, how can such nonsense be allowed to happen? Any sane person
will definitely check sector>15.

With the best of these... well, of course, !mPeR!0/PHG [imper...@mail.ru]

Pavel Demchuk ==========> All:

PD> Finally, I found a glitch in the subject! Or rather, not me, but my brother.
PD> Honestly, it’s so nice.

:)

PD> Specially for REAL: if you open the RAM disk, then create there
PD> a left file with a length of 255 sectors, and then change in the doctor
PD> the starting sector to some #3C thread, for example, then by viewing the file you can
PD> and RC take a look and edit it to your liking (for example, replace REAL
PD> with ....).

PD> People, tell me, how can such nonsense be allowed to happen? Any sane
PD> person will definitely check sector>15.

Of course, checking for the sector number when going to a file in Doctor
is not difficult to do. Well, what if you come across a file written to a non-standard sector number for protection purposes? Maybe there still
makes sense not to kill this glitch?

Bye!
Pawel_...@mail.ru [ZX] [Real Software]

07 June 2000 10:30, Pavel Demchuk wrote to All:

PD> Specially for REAL: if you open the RAM disk, then create there
PD> a left file with a length of 255 sectors, and then change in Doctor
PD> the starting sector to some thread #3C For example, by viewing the file you can look at
PD> and RC and edit it to your liking (for example, replace REAL
PD> with ....).

This is not the first program that allows modification of itself.
In c-dos you can definitely do it through view go through memory and change
everything you need for everything you don’t need ;)

In fact, it’s a good feature, you can fix bugs in real time :)

I was with you 500:95/462.17@ZXNet
Ars^FTL mailto:ars...@nival.com

PK> :)
I just got into the habit of looking for glitches in your programs, and, you know,
at first it was very disappointing that there was nothing in RC 1.95... but then...
PK> Of course, checking for the sector number when going to a file in Doctor
PK> is not difficult to do. Well, what if you come across a file recorded on
PK> with a non-standard sector number for protection purposes? Maybe there still
PK> makes sense not to kill this glitch?
How can a non-standard sector number appear on a ram disk?
As for killing, I think it’s worth killing :( it’s still a glitch.

Original was from to .
AA> This is not the first program that allows modification of itself.
AA> In c-dos you can definitely go through the view through memory and change
AA> everything you need for everything you don’t need ;)
for example .... to .... ;)
AA> Actually, it’s good feature, you can fix bugs in real time :)
yep, I once changed one byte in RC, so it sent me a disk.

PK>> to a non-standard sector number for security purposes? Maybe after all
PK>> it makes sense not to kill this glitch?
PD> how can a non-standard sector number appear on a ram disk?

And what does RamDisk have to do with it? The glitch is in the procedure of switching to a
file in Doctor, there is no check of the number of the first sector of the file for >15.

PD> As for killing, I think it’s worth killing :( still a glitch.

PK> What does RamDisk have to do with it? The glitch is in the procedure for switching to a
PK> file in Doctor, there is no check of the number of the first sector of the file for >15.
just check on the ram disk for sector >15