@RetroBunny,

Added, but file_id.diz is bad news here, especially the DCNT11-1.ZIP / DCNT11-2.ZIP part. This is typical for scene / warez releases, which weren't originally distributed on floppies but via BBS, FTP etc. Someone must've faked these images. Also, you can type the filenames in a search engine and see what I mean. Anyhow, we can keep this set just in case.

@

I've found an eBay auction from someone selling it? Wasn't very expensive. Or what do you mean? ... And yes, I immediately put the write protection switches into "readonly" - thanks for reminding me ^^.




Well, it is a Shareware version, so yeah... mmmh...

I understand the concept of shareware, I'm only saying it doesn't look like it came directly from the floppies whose scans you provided. I admit I was probably wrong about scene / warez though, these archives must've come from a soft / demo CD.

@flyers80,

Added:

International Tennis (3113): Fixes ID 2657. Verified.

Hi guys!

Golden Axe:

We have 3 "verified" sets: 958 (2x360), 2184 (1x720) and 2185 (2x360).

A couple of days ago I found and read this document: http://www.reteam.org/papers/e76.pdf

As I didn't know that Golden Axe apparently shipped with that bug that makes the duel mode impossible to finish (quite a severe bug if you ask me to go unnoticed) I started some detective work to see a bit more about the versions we have as verified.

Here's what I've found:

Sets 958 and 2184 are identical except for one detail, set 954 has 1 extra file called DRIVERS but it is an empty file, I don't know why it's there or where it comes from. The unpacked AXE.DAT file is identical in both sets and apparently bugged (has the 20 and 24 hex values at F90B and F90D).

Set 2185 is different. All the files are identical (and it also has that empty DRIVERS file), but the unpacked AXE.DAT is different. It is 16 bytes bigger and comparing it with a hex editor to the previous sets, it differs considerably. It also appears to have the bug, as those values of 20 and 24 are there, but at a different address: F91B and F91D (it's shifted 16 bytes, interestingly matching the 16 bytes bigger file, maybe a different header?).

I haven't got time to play-test the games and see if indeed all 3 are bugged, I'm curious to see if the 3rd and different set also has it or it has been fixed in a different way, or if it's cracked or a different version/release. I can't know the differences just by looking at the DAT file, but maybe some1 can?

It's a volume label, not a file. Looks pretty suspicious alright. But if all 3 sets are verified none of them can be modified or cracked. For all I know this game doesn't even have any copy protection. I really think those are just different versions.

Silly me, must have been 7zip that uncompressed the label as a file

has manual protection check

Oops.

Added:

Ballyhoo (3114)

Moonmist (3115)

Sorcerer (3116)

Suspended (3117)

Stocker (3118)

Trump Castle II (3119)

Haven't had a new one in a while. Actually I did get F-15 Strike Eagle 3 but the disks were very corrupt:(

Indycar Racing 3.5" x3

@AliensOfGold,



Sorry to hear that. At least you got the original boxing, manuals etc. and disks which can be still revived using healthy images.

Added:

IndyCar Racing (3120): v1.0

@Otaku,

Added:

Airborne Ranger (3121): v441.03 Manual & physical copy protection (?)

Amazon: Guardians of Eden (3122): 1st disk is 3.5" DD. Fixes ID 44.

Alone in the Dark 2 (3123): Spanish release. Modified RootDir (CT). Probably fake.

Blake Stone: Planet Strike (3124): v1.0. Modified RootDir (CT). Probably fake.

Blake Stone: Aliens of Gold (3125): v3.0

Space Quest 1: The Sarien Encounter (3126): v2.000 SCI / VGA. Fixed OEM ID and cleaned RootDir (AT).

Space Quest 4: Roger Wilco and the Time Rippers (3127): v1.060. Written / modified RESOURCE.CFG.

Tie Fighter Demo (3128): Bad WinImage dump.

Tie Fighter: Defender of the Empire (3129): Tie Fighter expansion. Cleaned RootDir (AT) and fixed file size of disk 1 and 2. Fixes ID 612.

Wolfenstein 3D (3130): v1.4 Commercial version (episodes 1-6). Fixed OEM ID and cleaned RootDir (CT & AT).

Wolfenstein 3D (3131): v1.4 (episodes 1-6). GT Interactive release. Fixed OEM ID on all disks.

Wolfenstein 3D (3132): v1.4e (1-6 episodes). GT Interactive release. Fixed OEM ID.

X-Wing (3133): 5.25" (1200kB) Fixed OEM ID and cleaned RootDir (AT) on all disks.

Not added:

Alone in the Dark 2: v1.0. Incorrect OEM ID / Serial. Modified RootDir (CT). Positively fake.

Alone in the Dark 2 (English): Corrupt boot sector on disk 8, otherwise the same as ID 1612.

Note: ID 1808 has modified RootDir (AT) on disk 8, otherwise the same as ID 1612, which is now Verified. Indeed, it is weird how all 3 sets have modified disk 8, but all in different ways.

Another World (French): Fake image.

Budokan: Modified OEM ID, RootDir (AT) and Data region, otherwise the same as ID 717, which is already verified.

Heretic: Self-made in WinImage.

Hexen: Self-made in WinImage.

Simon the Sorcerer 2: Self-made in WinImage.

[TD0] Space Quest 1: The Sarien Encounter: v1.1A / AGI 2.272 (went on FTP into your personal folder).

Tie Fighter: Modified OEM ID, RootDir and wrong filesize, otherwise the same as ID 2729.

Warcraft: Self-made with WinImage.

Wolfenstein 3D v1.1: Incorrect OEM ID / Serial, modified RootDir (CT). Positively fake.

Wolfenstein 3D v1.4: Mindscape release. Incorrect OEM ID / Serial, modified RootDir (CT). Positively fake.

Wolfenstein 3D v1.4d: GT Interactive release. Incorrect OEM ID / Serial, modified RootDir (CT). Positively fake.

Wolfenstein 3D v1.4g: Registered version. Self-made with WinImage.

Wolfenstein 3D: Super Upgrades: Same as ID 678.

X-Wing 3.5" (1.44kB): Modified OEM ID, modified RootDir (AT), wrong file size, otherwise the same as ID 110, which is already verified.

These may be stuffed, but I have two new ones.

Gunship 2000 3.5" x4 720K
F-19 Stealth Fighter 3.5" x 2 720K

Dumped using UltraISO and skipping bad sectors. Disk 1 (A) of F-19 had a few errors come up while reading and disk 4 (D) of Gunship 2000 the same.


Nope tried these on my 486 and Gunship 2000 disk D is definitely dead:(. F-19 installs without issue so maybe copy protection?

@AliensOfGold,

Not added:

F-19 Stealth Fighter: Disk 1 had a few damaged unused sectors, which could be copy protection, otherwise the same as ID 57. Could you please dump this using Teledisk?

Gunship 2000: Like you said, errors in the data region, otherwise the same as ID 884, which is verified. You can safely restore your disk D/4 using that set.

@flyers80,

Added:

Prehistorik 2 (3134): Unknown release, possibly pirated / cracked. Includes a Windows application called Sapristi.

Uploaded F-19 TD0 files. I hope I did it correctly, but I've never used that software before so I could have done something wrong.

Weirdly it didn't stop on any errors and just kept going to the end, but it did give me some feedback in the analysis window about sectors being moved or shifted or something.

@AliensOfGold,

Something's wrong with disk 1. I don't know why, but I can't even list its directory in PCE as it brings up an error. All I can tell is that this "corruption" stems from CP, which really is there (id 57 is missing CP tracks, info updated). I think Pheonix should take over from here.

Doesn't appear to have CP tracks either. Cleaned up an IMG file a bit and uploaded it, for comparison work. But even keeping the "non-existing" tracks in place, doesn't recognize it as a key disk. Appears to me to be a corrupted read. May be a bad disk.

Thanks, it's still a match to ID 57.



I find it very strange. Seems like everything is ok (almost) about it except the CP part. Either that region alone is damaged (sounds unlikely) or this particular type of CP cannot be parsed correctly by either Teledisk or the emulator, which leads to corrupt root directory. So, the question is, which of the two is the real problem. If the latter then I would assume it's a compression issue.

@AliensOfGold,

Try dumping disk 1 again, please. But this time, just in case: do not change the compression level (keep at default). I'm pretty sure that's what you did, but now that we are facing a weird situation I can only ask you to re-dump the disk and make sure you do it correctly. Personally, I very much doubt it's bad nor cannot be successfully dumped by Teledisk. The issue lies elsewhere.