Bug Tracker – Bug 907

Odamex Incorrectly Identifies FREEDOOM.WAD as a commercial wad and will refuse to download it.

Last modified: 2016-10-14 23:43:03 CDT
Bug 907 - (ARRAY(0x6074cc8)) Odamex Incorrectly Identifies FREEDOOM.WAD as a commercial wad and will refuse to download it.
(ARRAY(0x6074cc8))
Odamex Incorrectly Identifies FREEDOOM.WAD as a commercial wad and will refus...
Status: NEW
Product: Odamex
Classification: Unclassified
Component: Server & Client
0.6.x
All All
: P2 minor
: ARRAY(0x62e01a8) (view as bug list)
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2012-10-03 00:40:50 CDT by RedZTag
Modified: 2016-10-14 23:43 CDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RedZTag 2012-10-03 00:40:50 CDT
0﷓
As you can see, Odamex refuses to transfer.
Comment 1 Alexander Mayfield 2012-10-11 23:15:30 CDT
This is due to the fact that Odamex uses W_IsIWAD() to determine if the file is okay to download which will return true for all IWAD's, not just commercially available ones.

A robust solution would be to make that check more nuanced.  Instead of returning a simple true and false, it could perhaps return a pointer to the appropriate doomwadnames entry on success, or a null pointer on failure.  The doomwadnames array could then be expanded to have more robust information, such as if the IWAD should be downloadable.

I seem to also have some memory of the canonical Freedoom WAD names being the same as the commercial WAD names.  If that's the case, we should probably also handle that case properly.
Comment 2 RedZTag 2012-10-17 04:51:58 CDT
Freedoom does name itself doom2.wad, and I assume ultimate freedoom will also name itself doom.wad.
Comment 3 /usr/share 2012-12-03 18:06:28 CST
Probably the better way would be to check the wad against a checksum database of known commercial WADs (to check for different release versions of the WADs).
Comment 4 HeX_Vulture 2016-10-14 23:43:03 CDT
*** Bug 1165 has been marked as a duplicate of this bug. ***