EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Pages: [1]   Go Down

Author Topic: Dir2Dat new feature req.  (Read 193 times)

CCT

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 3
  • OS:
  • Windows NT 6.3 Windows NT 6.3
  • Browser:
  • Mozilla compatible Mozilla compatible
    • View Profile
Dir2Dat new feature req.
« on: 13 July 2019, 06:18 »

It would be useful to add an automatic (optional) CHD format recognition to Dir2Dat.

For example, Dir2Dat output for kinst CHD folder is:
rom ( name kinst.chd size 93887853 crc 35d59b6f sha1 12184e135cab2a6372c65843f823478b213bbfa0 )
CHD size and crc are useless and file sha1 is not documented anywhere.

Correct Dir2Dat output should be:
disk ( name kinst sha1 81d833236e994528d1482979261401b198d1ca53 )
Logged


Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 77
  • Offline Offline
  • Posts: 2608
  • OS:
  • Mac OS X Mac OS X
  • Browser:
  • Safari 10.0 Safari 10.0
    • View Profile
Re: Dir2Dat new feature req.
« Reply #1 on: 13 July 2019, 08:36 »

yes would make perfect sense. I put it on the list
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 77
  • Offline Offline
  • Posts: 2608
  • OS:
  • Windows NT 10.0 Windows NT 10.0
  • Browser:
  • Chrome 75.0.3770.142 Chrome 75.0.3770.142
    • View Profile
Re: Dir2Dat new feature req.
« Reply #2 on: 16 July 2019, 18:58 »

I guess it's enough to only check files with .chd extension to be added as chds, isn't it? (And then the name will be without the extension to match MAME style).
Or should each file be checked for a chd header?
Or should the disk creation only be added optionally (checkbox)....is there anyone who needs chds as "plain files"?
Logged
Pages: [1]   Go Up
 

Page created in 0.078 seconds with 20 queries.