Re: CarnEvil - Unplayable? Correct Mouse Support?

* MCR Wrote in alt.games.mame:

> SINNER wrote:
>> * MCR wrote in alt.games.mame:
>>
>>>Roman wrote:
>>>
>>>>Your reply is totally out of scope and gives zero sense to the
>>>>discussion. I gave a concrete answer to his question while my
>>>>'speech' was totally ok and there was no discussion about
>>>>missing files nor a question about roms themselves either.
>>
>>
>>>The reply you gave was the standard MAME.NET one. The guy wants
>>>to know how to get his game working. Your answer about dumping
>>>from the original machine! (Something BTW that is illegal).
>>
>>
>> Not illegal to dump for the purpose of backup. Personal use of
>> the image without the original equipment is illegal but ONLY if
>> that hardware is still readily available, at least thats the way
>> it works in the US.
>>
>> The latter part of that statement is a recent addition to the
>> DMCA.
>
> The DMCA also states that it does not oveerturn/change any
> previous rulings.
>
> "The practice of dumping the videogame cartridges of a home
> videogame system by the average user is not justified under the
> backup proviso of copyright law (Atari v. JS&A Group, 1983) and
> this restriction also covers arcade videogames and any other
> ROM-derived formats as well (Tandy v. Personal Micro Computer,
> 1981). The one exception for ROM dumping is granted solely to
> bona fide developers and their associates (Sega v. Accolade and
> Nintendo v. Atari, 1992)".
>
> Fair use and 'backup' are not applicable to ROMs. Also, we are
> not all covered by the DMCA :)

Fair use is not, backup is. It is specifically mentioned that use for
repair is legal. THe RTOM may not be 'used' without the original
hardware. Regarding the DMCA it was ruled that IF the hardware for a
platform is no longer available that reverse engineering is no longer
an issue.

Small quote:

Thirdly, in addition to being able to make copies of damaged,
deteriorating, lost, or stolen items, eligible libraries and archives
may now make copies of digital material in obsolete formats. A format
is considered obsolete if the machine or device necessary to render
perceptible a work stored in that formatis no longer manufactured or
is no longer reasonably available in the commercial market-place. The
law recognizes that hardware or software obsolescence is in itself a
form of loss and has made it legallypossible to transfer files to
newer media or file formats.


http://cidc.library.cornell.edu/Pub_files/DMCA_Final.pdf


--
David
.

Relevant Pages

  • Re: CarnEvil - Unplayable? Correct Mouse Support?
    ... Regarding the DMCA it was ruled that IF the hardware for a platform is no longer available that reverse engineering is no longer an issue. ... The DMCA specifically refers IIRC to obsolete hardware, however, you would have a tough time in the court with Nintendo explaining that you own a Mario Bros Board, and you were playing it in MAME because you have the original. ... Thirdly, in addition to being able to make copies of damaged, deteriorating, lost, or stolen items, eligible libraries and archives may now make copies of digital material in obsolete formats. ...
    (alt.games.mame)
  • Re: Microform developments
    ... backup from one electronic format to the next ... ... The internet is now ubiquitous. ... We are no longer at the mercy of undocumented file formats, ... As a typical home user I don't want to know and don't need to ...
    (soc.genealogy.britain)
  • Re: Hard drive format compatibility - what am I missing?
    ... XP can handle all File Formats: Me cannot handle formats above FAT32. ... Try these 2 Options [if you have Norton Ghost]. ... Create the Ghost start disk and accomodate USB device support during the ... If so create your backup of the Me System. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Microform developments
    ... backup from one electronic format to the next ... ... The internet is now ubiquitous. ... We are no longer at the mercy of undocumented file formats, ...
    (soc.genealogy.britain)
  • Re: Old broken COBOL programs from the 70s and 80s
    ... It has since been supplemented by an Extended TOD hardware value with higher resolution and longer cycle for the rare cases where raw TOD values are used for a time stamp, which is typically only within IBM code and system data structures, very rarely in application code or application defined data fields. ... Some of the MVS date formats at the time that had abbreviated years values had to be left that way for compatibility with earlier hardware and operating systems. ... Once you have conventional date formats flying around, you open up the same opportunity for abbreviated year fields and potentially ambiguous dates in user interfaces, application code, and files - so having an internal hardware/system date-time representation that minimizes ambiguity is unfortunately no guarantee that applications on that system would be immune from date ambiguity issues. ... having less robust hardware/system time stamp support doesn't prevent an intelligent application design that avoids date ambiguity problems. ...
    (comp.lang.cobol)