Help Required

On 1/17/2021 at 4:17 PM, Edward850 said:

These seemingly aren't corrupted files, but rather completely mislabelled files. They may have the WAD file extension but they aren't WAD files, their contents are something else entirely.

• Drawing map.wad is some kind of mix between a text document and binary data. Looks like HTML and CSS in some places. Unable to determine its true nature.
• hellish escape.wad is entirely encoded/encrypted binary. No headers or any markers.
• New re map thing.wad is actually a fully intact JPEG of some kind of Fallout Shelter image, maybe a video thumbnail? However it also has an OGG stapled on the end, not sure what it contains.
• noneuclidean.wad is an OGG Vorbis file. Some kind of swinging sound effect.
• NUTS3.WAD is some kind of meta data file referring to sound effects, such as "data\sound\dialog\combat\bugger\dth_slnt\h3_4_25.aif".
• portsal thing.wad is another binary chunk file with an XML header. This appears to be a VTF file, or at least contains one.
• Project Incident.wad is another binary chunk file. Starts with the bytes bvc, unknown.
• remap thing.wad is another binary chunk file. Unknown.
• TempFile.wad is another binary chunk file. Unknown.
• The Armorments.wad is another binary chunk file. Unknown. Seems to have UTF-16 text mixed with raw images of some kind in the mix. Unknown.  

 

At no point could this data have ever have been WAD files or Doom maps of any kind.

Okay, NOW im interested, that info is really interesting, like that blew my mind. especially the fallout image you said about, cause im not that sophisticated with mapping, so how that appeared there, i have no clue, but uh, thanks anyway! like, actual thanks for explaining each file

19 hours ago, 2009XboxLiveKid said:

.....
it says there's no maps in the WAD, can anyone help with this?.....

Whatever happened to these pwads did a good job at obfuscation. Checking them with a HEX editor, there are no ASCII strings left. No PWAD header no MAP or other lump information.

These seemingly aren't corrupted files, but rather completely mislabelled files. They may have the WAD file extension but they aren't WAD files, their contents are something else entirely.

• Drawing map.wad is some kind of mix between a text document and binary data. Looks like HTML and CSS in some places. Unable to determine its true nature.
• hellish escape.wad is entirely encoded/encrypted binary. No headers or any markers.
• New re map thing.wad is actually a fully intact JPEG of some kind of Fallout Shelter image, maybe a video thumbnail? However it also has an OGG stapled on the end, not sure what it contains.
• noneuclidean.wad is an OGG Vorbis file. Some kind of swinging sound effect.
• NUTS3.WAD is some kind of meta data file referring to sound effects, such as "data\sound\dialog\combat\bugger\dth_slnt\h3_4_25.aif".
• portsal thing.wad is another binary chunk file with an XML header. This appears to be a VTF file, or at least contains one.
• Project Incident.wad is another binary chunk file. Starts with the bytes bvc, unknown.
• remap thing.wad is another binary chunk file. Unknown.
• TempFile.wad is another binary chunk file. Unknown.
• The Armorments.wad is another binary chunk file. Unknown. Seems to have UTF-16 text mixed with raw images of some kind in the mix. Unknown.  

At no point could this data have ever have been WAD files or Doom maps of any kind.

15 hours ago, Kappes Buur said:

 

Whatever happened to these pwads did a good job at obfuscation. Checking them with a HEX editor, there are no ASCII strings left. No PWAD header no MAP or other lump information.

so in other words, yeah, these are comepletly fucked?

1 hour ago, 2009XboxLiveKid said:

so in other words, yeah, these are completely fucked?

Unfortunately yes.

There is still a lot of information in those wad files, but reconstructing them from the information left would be like a miracle.

@Edward850 Can I ask how you determined that certain files are actually OGG Vorbis files or JPEGs? Was it just opening up the file in a hex editor and looking for headers?

26 minutes ago, xvertigox said:

@Edward850 Can I ask how you determined that certain files are actually OGG Vorbis files or JPEGs? Was it just opening up the file in a hex editor and looking for headers?

Pretty much. Parts of my job have involved identifying what files actually are while ignoring file extensions (sometimes because they don't even have one). OGG containers and JPEG JFIF headers stick out like a sore thumb.