Author Topic: Entries without MD5  (Read 78 times)

Offline doomwarrior

  • Newbie
  • *
  • Posts: 7
    • Email
Entries without MD5
« on: April 16, 2022, 10:49:12 AM »
Hi,

because I'm unhappy with the tooling is started to write a little program to use TOSEC DAT files to move stuff around as I like it. A few amount  of entries don't have a MD5 value. The Logiqx dat file does not require to have a md5 entry. But i found it odd, because it is only missing on the following files. What is the policy here?

Code: [Select]
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Texas Instruments TI-83 - Applications (TOSEC-v2014-06-30_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {Word v1.0 (2001)(Diepeveen, Jordie)}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Texas Instruments TI-82 - Applications (TOSEC-v2014-06-30_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {HexEditor v1.2 (1998)(Milewski, Greg)[req Ash][with source code]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model 4 - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {Faultless Foto Payroll v3.1 (1987)(Robert Doerr)[BAS]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model I - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {HAM QSL Information System (19xx)(-)[BAS]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model I - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {S & P Portfolio Management System (1981)(S&P)[BAS]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model I - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {Subscription Chopping System v0.01 (19xx)(-)[BAS]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model I - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {Wheel of Fortune (19xx)(Byron Brower)[BAS]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model III - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {Fantastic Realms (19xx)(-)[BAS]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model III - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {GenSystems (1981)(Maurice L Dyer)[BAS]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model III - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {Leland Stock Control (1985)(-)[BAS][Program Disk]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model III - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {MicroFiles v3.0 (1979)(Rober Kleigus)[CMD]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model III - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {Profile III+ v1.0 (1981)(Small Computer Company)[CMD]}
ERROR:root:TOSEC DAT file {My Games/ROM/TOSEC/Tandy Radio Shack TRS-80 Model III - Various (TOSEC-v2014-06-27_CM).dat} parser error. Entry skipped because: no {datafile/game/rom{md5}} found for game {Store Operating System Initialization v3.5 (1982)(Tandy)[CMD]}
« Last Edit: April 16, 2022, 11:24:06 AM by doomwarrior »



Offline mictlantecuhtle

  • Global Moderator
  • Full Member
  • *****
  • Posts: 128
Re: Entries without MD5
« Reply #1 on: April 17, 2022, 03:50:04 PM »
Thanks for this, it's a strange one for sure. As far as I'm concerned, all files should have all three hashes. Looking at the dates, those haven't been touched in a while so presumably just a small historic oversight.

I'll take a look at them and update those DATs with MD5 values for the files.

Thanks for flagging this up, really appreciate it!