Moderators: simonsunnyboy, Mug UK, ICS, Doctor Bob Gordon, Moderator Team
ijor wrote:I'm not sure you understand my point. All I'm saying is to change the term "dump" for "release", because otherwise it might imply that the problem is specific to the dump and not to the disk/software/release.
Still get the scum of earth message though.ijor wrote:Marakatti wrote:Ok, please tell me how to put it and i'll update the text. I'm not a coder or know nothing about disk protections so i don't know anything about what's happening "inside the disk".
If i write it requires TOS 1.0 i get reports that it works even though people won't play it enough to understand the protection gets activated with TOS 1.2 and greater.
I'm not sure you understand my point. All I'm saying is to change the term "dump" for "release", because otherwise it might imply that the problem is specific to the dump and not to the disk/software/release.
Currently the record claims: "Dump only works correctly with TOS 1.0 due to a copy protection".
I suggest to change it to something like this: "The original release only works correctly with TOS 1.0 due to a copy protection".I also wonder if the Mastertronic release is different...
It seems so according to a dump I have. And it looks like you have, or had, a Mastertronic dump. Did you read the other message I posted above? viewtopic.php?f=4&t=32007#p324104
Stefan jL wrote:pic from Mastertronic release playing in Steem SSE TOS 1.0.
Stefan jL wrote:Now i have tried my Mastertronic release with two of my ST's... one with TOS 1.02 (or 1.04?) and one with 1.0 and it still crashes when defeatingt an enemy and shows 4 bombs.
Worth mentioning might be that both ST's use 1mb of RAM in case that causes problem with the program?
Steven Seagal wrote:There's a bug in Steem SSE, I'll fix it soon so that the game doesn't call you names.
And some images may be wrong.
Steven Seagal wrote:Wrong WD1772 status register after command $D0, CRC bit wasn't cleared, so it did the same in TOS 1.0 as in later TOS.
In fact it's surprising that the bug didn't break more games.
Steven Seagal wrote:Wrong WD1772 status register after command $D0, CRC bit wasn't cleared, so it did the same in TOS 1.0 as in later TOS.
In fact it's surprising that the bug didn't break more games.
Fixed now in the dev build.
rogue_ok.png
At least I wasn't called 'scum of the earth'.
Steem's 'ghost disk' feature also seems to work with this game for the writes.
Keep it safe ijor wrote:Marko, in my (perhaps, very personal) opinion. The dump of the Mastertronic release should be restored at Atarimania. The dump is good. It works as good and as bad as the actual disk on real hardware. Of course, some note describing the issue should be posted. At the very least, the text should be changed to mention that the version itself doesn't seem to work.
And if you want to play the game just use the Epyx dump or Atarizoll's HD version. ijor wrote:More technical details about the Mastertronic release
The disk seems to be mastered and duplicated in two different devices. The regular tracks (0-78) on one hand seem professionally duplicated. While the copy protected track, track 79, seems to be done separately. This track is not a faithful reproduction of the original copy protected in the Epyx release, but a manually crafted track that emulates the protection yielding almost the same result.
I'm not sure why it was done like this. May be they used cheap duplicators that couldn't handle the protection. May be they didn't have the original master to make the protection. Btw, this was quite common in the later generation of budget releases. We know they even sometimes used cracked versions. But it unusual, to say the least, on a Mastertronic release that shouldn't be that late.
The original protection is based on a couple of overlapped sectors (one sector embedded in the other) in such a way, because of their content, that it can't reproduced exactly with the standard FDC on the ST. In this case, in this budget release, this was replaced with two separate, non overlapped, sectors. And then this can be written and created with a plain ST. In addition, and because this take more space, they shortened the two first sectors. As you can see, a manually crafted track that when is read by the game it reads almost the same as the original. But they made a small mistake when crafting the track and the data is actually not identical as the original, so the protection test fails.
It is possible that this protection adaptation was made by Mastertronic, or somebody they hired. It is also possible they simply used a non original copy, a pirated copy that copied the original release with a software copier like Procopy. The latter might make more sense when you consider that the disk has a deleted saved game. But even then, it still seems that duplication of this track was performed separately.
In addition to this, when the game checks if the protection test failed, it crashes. That's at the point where on the original release it just makes more difficult to beat the enemies. I don't know exactly why it crashes and as I said, I'm not very motivated to investigate it. It doesn't seem to be related to the protection test fail. The point is that the protection test fails, even with TOS 1.0. And, in addition it crashes. The actual program was altered, so may be there was an attempt to crack it or at least modify it.
dlfrsilver wrote:With a second owner dumping his original it could be confirmed or infirmed.
Users browsing this forum: No registered users and 5 guests
