Miroirs/mame
1
0
Fork 0
mirror of https://github.com/mamedev/mame.git synced 2024-11-16 07:48:32 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mame/hash/dragon_flex.xml

327 lines
11 KiB
XML
Raw Normal View History

New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
<?xml version="1.0"?>
<!DOCTYPE softwarelist SYSTEM "softwarelist.dtd">
(nw) More license shuffling Get rid of a couple of copies of the CC0 text. Add header comment to CC0 files to remind people editing them what the terms are. Also add some missing XML headers. The header comments in layouts won't bloat the binary - they get stripped out before compressing, same as any other comments.
2020-03-07 12:02:56 +01:00
<!--
housekeeping: Use proper SPDX ID for CC0 license.
2022-12-22 16:49:34 +01:00
license:CC0-1.0
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
(nw) More license shuffling Get rid of a couple of copies of the CC0 text. Add header comment to CC0 files to remind people editing them what the terms are. Also add some missing XML headers. The header comments in layouts won't bloat the binary - they get stripped out before compressing, same as any other comments.
2020-03-07 12:02:56 +01:00
Dragon 64 FLEX floppy disks
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
(nw) More license shuffling Get rid of a couple of copies of the CC0 text. Add header comment to CC0 files to remind people editing them what the terms are. Also add some missing XML headers. The header comments in layouts won't bloat the binary - they get stripped out before compressing, same as any other comments.
2020-03-07 12:02:56 +01:00
Loading Instructions:
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
Load a FLEX system disk using:
BOOT
-->
<!-- This list was compiled from the archive at http://archive.worldofdragon.org/archive/index.php?dir=Disks/Dragon/Flex/ as of 26/03/2017. -->
<softwarelist name="dragon_flex" description="Dragon FLEX diskettes">
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
<software name="chatplus">
<description>Chatplus V1.0.2</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Chatplus v1.0.2 (1985)(Compusense Ltd)[FLEX].vdk" size="184332" crc="19ccacf0" sha1="5ada16ed7ffedb779fee6217c429a5d0eab607e8"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
<software name="dbasica" cloneof="dbasic">
<description>DBASIC (Alt)</description>
<year>1984</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="89612">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="DBASIC (1984)(Compusense Ltd)[a][FLEX].vdk" size="89612" crc="8d0c7af0" sha1="8804954ab2a5ff0694f1f5d85d660ea1c5fd325c"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
<software name="dbasic">
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
<description>DBASIC</description>
<year>1984</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="89612">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="DBASIC (1984)(Compusense Ltd)[FLEX].vdk" size="89612" crc="9e442c96" sha1="59e219fe8fc419acb607e09376a0ffcabc803b01"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
<software name="dbasic10">
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
<description>DBASIC v1.0</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184343">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - DBASIC v1.0.vdk" size="184343" crc="6d45b2a2" sha1="5f3bf42dad7a4d06dac0f106f4e57d124eb130d6"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
<software name="diag">
<description>Diagnostics</description>
<year>198?</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Diagnostics (198x)(Compusense Ltd)[FLEX].vdk" size="184332" crc="a7dc4a6d" sha1="3805b18f612ca0556555d5318fe71f9edd2fdd2c"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
<software name="bargain2">
<description>Dragon Bargain Pack 2</description>
<year>1986</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184343">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - Dragon Bargain Pack 2.vdk" size="184343" crc="b0fa9ade" sha1="f427cfc7fe8e6af6695c245a27dcc73c4bfaed1d"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
<software name="dplusupdt">
<description>DragonPlus Updates</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="DragonPlus Updates (1985)(Compusense Ltd)[FLEX].vdk" size="184332" crc="43b47717" sha1="89791522e0eb633c61021d16a463b32f7dccd1a5"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
<software name="dynacalc">
<description>Dynacalc</description>
<year>1986</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184345">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Dynacalc (198x)(Compusense Ltd)[FLEX].vdk" size="184345" crc="9ddcb3cd" sha1="c0b187571f7e01ba43a8a0d8a1f42afa736f1791"/>
New working software list additions ----------------------------------- bbc_rom: BBC Teletext 2.38, BBC Teletext 2.50, ATS+ 1.00, ATS+ 2.00, DMON A1.03, HyperDriver 1.11, The Informant, Logotron LOGO (Cymru), Open LOGO, QFS 1.01, Romit 1.00, Super-Forth 1.5, StarBASE 2.11, STL Clock & Desk 1.10, SupaStore 1.5, Techno-Font, Acorn TFS 1.00, Acorn TFS 1.02, Acorn TFS 1.03, ViewSheet 1.0, Wapping Support 1.21, Wordwise Plus 2.04, WYSIWYG Plus 1.22 dragon_flop: Dunjunz z88_cart: Code Count, Z88 Data Organiser, EP-Copy, Event Control System, PC-Link II, Stop Watch, Toll Tracker v2.0 (Demo) New NOT_WORKING software list additions --------------------------------------- bbc_rom: Barry-Box, CUBE BeebFlex, BeebScan, Eprom Programmer 1.03, Eprom Programmer 1.06, Eprom Programmer V2 2.01, Eprom Programmer V2 2.02, Eprom Programmer V2 2.03, EURO-Beeb Terminal 1, EURO-Beeb Terminal 4.13, FIT Test Station, PMS Genie 1.02, Hobbit OS 1.8, Prestel 1.0, Ramamp Video 2.40, Ramamp Video 2.50 Software list items promoted to working --------------------------------------- bbc_rom: AMX Design
2019-06-08 22:17:01 +02:00
</dataarea>
</part>
</software>
<software name="dynafast">
<description>DynaFast v1.5.0</description>
<year>1984</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="102412">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Dynafast v1.5 (1984)(Compusense Ltd)[FLEX].vdk" size="102412" crc="6f57191a" sha1="4b86a6a7128efe98eb3b99fa66adb7b2d44b2358"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
<software name="editassm">
<description>Editor &amp; Assembler</description>
<year>1984</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Editor &amp; Assembler (1984)(Compusense Ltd)[FLEX].vdk" size="184332" crc="fbd982fc" sha1="0d61de42dac45f2177691483f2246d8613562611"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
<software name="editassmdp">
<description>Editor &amp; Assembler (DragonPlus)</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Editor &amp; Assembler (1985)(Compusense Ltd)[FLEX][DPLUS].vdk" size="184332" crc="2401fb97" sha1="ac068e6b33f46c50a06a48f16dff2d5c7a2cb8cb"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
<software name="extbasic">
<description>Extended Basic</description>
<year>198?</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Extended Basic (198x)(Compusense Ltd)[FLEX].vdk" size="184332" crc="c18a8f61" sha1="24b5d8add1bf1159d7687956c95967085ecfe597"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
<software name="pascal">
<description>Lucidata Pascal Compiler</description>
<year>1986</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - Pascal.vdk" size="184332" crc="ef6ff3b9" sha1="f211bc7e74ecce4822a8f78a1d517efe8a211362"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
<software name="rms">
<description>RMS</description>
<year>1986</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184343">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - RMS.vdk" size="184343" crc="ddbf10b8" sha1="cb5fce70af4625df820a52df4989564728d292d3"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
<software name="spedit">
<description>SP-Edit</description>
<year>1985</year>
<publisher>Compusense</publisher>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="SP-Edit (1985)(Compusense Ltd)[FLEX].vdk" size="184332" crc="f33017a8" sha1="ec48253caaa782e259c2b9055bc726b3f96f429c"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
<software name="speditdp">
<description>SP-Edit (DragonPlus)</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="SP-Edit (1985)(Compusense Ltd)[FLEX][DPLUS].vdk" size="184332" crc="6e225972" sha1="744205c3603d2c043861b11e73d1b8a80abc35be"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
<software name="spedit108">
<description>SP-Edit v1.0.8</description>
<year>1985</year>
<publisher>Compusense</publisher>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - SPEdit v1.0.8.vdk" size="184332" crc="087807c8" sha1="fadcc929925f9b492e62c8b87c665b8cd179dba6"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
<software name="ssleuth">
<description>Super Sleuth Disassembler</description>
<year>198?</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Super Sleuth Disassembler (198x)(Compusense Ltd)[FLEX].vdk" size="184332" crc="75e73de8" sha1="e5498f4a8eee30bd1cfd94fed4edb3519f5ed334"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
<software name="system120">
<description>System v1.2.0</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - System v1.2.0.vdk" size="184332" crc="ab8603ba" sha1="3410b3d1373b1a11e6fe2a7878dac47209380179"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
<software name="system131">
<description>System v1.3.1</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184336">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - System v1.3.1.vdk" size="184336" crc="2ecb2f2b" sha1="eeae2edf20697a2f919cf9a22d87c2c623d5d859"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
<software name="system132c">
<description>System v1.3.2/Crunch Cobol v1.1</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184338">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - System v1.3.2 plus Crunch Cobol v1.1.vdk" size="184338" crc="47574ec3" sha1="8f1f829632442e9e56046de345a09028c80afdee"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
<software name="system132">
<description>System v1.3.2</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184336">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - System v1.3.2.vdk" size="184336" crc="b1660797" sha1="c812587dd4b5718d73f4b798f797c47c7f042d44"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
<software name="system200c">
<description>System v2.0.0/Crunch Cobol v1.1/DBASIC v1.5 (DragonPlus)</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184339">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - System v2.0.0 plus Crunch Cobol v1.1 - DBASIC v1.5 - DragonPlus Only.vdk" size="184339" crc="116eb4ab" sha1="363fb5c10f33a7d14a48e1aca53a9fc898403cbc"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
<software name="system200d">
<description>System v2.0.0/DBASIC v1.7 (DragonPlus Update)</description>
<year>1985</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184347">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - DragonPlus Update - Flex System v2.0.0 - DBASIC v1.7.vdk" size="184347" crc="d925a559" sha1="3b88f299e01cf6979921048d3ec6dfdab354f9a4"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
<software name="various">
<description>Various (Debug v1.5 - DynaFast v1.5.0)</description>
<year>198?</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) d,e*.xml : removed offset=0
2019-05-16 05:47:26 +02:00
<rom name="Compusense - Flex - Various (Debug v1.5 - DynaFast 1.5.0 etc).vdk" size="184332" crc="66367a4c" sha1="d5fc033232c3d09cb56d70cd1dca60c4d47d6bd1"/>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</dataarea>
</part>
</software>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
<software name="textproc">
<description>Text Processing System</description>
<year>198?</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Text Processing System (198x)(Compusense Ltd)[FLEX].vdk" size="184332" crc="567ec37b" sha1="e88197c2961696eb2efc95e6fc1cd24ec3cc1e02"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
<software name="utilsa" cloneof="utils">
<description>Utilities (Alt)</description>
<year>198?</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="184332">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Utilities (198x)(Compusense Ltd)[a][FLEX].vdk" size="184332" crc="87a482da" sha1="f910800793020845f26f10aa46fdcc22ea75d686"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
<software name="utils">
<description>Utilities</description>
<year>198?</year>
<publisher>Compusense</publisher>
<part name="flop1" interface="floppy_5_25">
<dataarea name="flop" size="89612">
(nw) softlist_dev.cpp: validate ROM labels The free-for-all on labels in software lists is not working. There's no consistency, labels are getting excessively long, people are starting to use non-ASCII characters in labels making it harder for others to type them when manipulating files on the command line, and there's too much markup being put in labels. The length limit is 127 characters, same as for labels in MAME itself. This should be long enough to be descriptive. Remember that the Win32 path limit is 260 characters, and many applications and frameworks have issues with longer paths, including Windows Explorer and the .NET framework. Labels are used as filenames, so concessions need to be made for this. I have not abbreviated excessively long labels myself - they're currently causing 135 validity errors. Someone else can fix them. Printable ASCII characters are allowed, with a few exceptions. The exceptions are limited to characters most likely to cause issues for interactive shells and scripts: * ! - csh event substitution (very difficult to escape properly) * $ - sh varibale expansion * % - csh job control, cmd variable expansion * / - UNIX directory separator * : - sh path separator, Windows drive qualifier * \ - sh escape, Windows directory separator Most of the labels that had to be edited were using ! for markup, or using ! and % for titles in labels. Strangely, titles in labels are often forced to lower case, despite this never being enforced for software lists. There are also various other edits to titles used for labels, such as moving articles to the end (with or without a comma), or replacing spaces with underscores. As I already said, there's no consistency at all. There is far too much markup in labels. They're even being used for notes in some cases (e.g. at least one case where a dumper's name is in the label). The XML schema supports metadata - use it. For example, you can use part_id for an unrestricted display name for a software part. You can also use XML comments for notes. And while on the topic of metadata, vgmplay.xml is putting the same thing in the part_id as well as the label. The part_id should have the actual title, not the title mangled to make it more suitable for use as a filename. Addressing this would be a lot of work, given how large the file is. For now, empty data areas in software lists cause a verbose message rather than a validation warning. There are thousands of software lists using empty data areas to indicate the size/width of cartridge RAM/EEPROM/etc.
2020-04-15 21:05:16 +02:00
<rom name="Utilities (198x)(Compusense Ltd)[FLEX].vdk" size="89612" crc="f36b61da" sha1="ed84f92d53b123e939a6f40c3eceb2a00019c3ef"/>
New WORKING software list additions ----------------------------------- dragon_cart: Sound Extension, and non-working EPROM Programmer, Speech Synthesis, Ultra Drive dragon_cass: Hang It! dragon_flex: Chatplus, Diagnostics, Editor and Assembler, Utilities, etc. dragon_flop: Various releases from PSE, Dragonfire, N.D.U.G., etc. dragon_os9: Cash and VAT, DragonPlus OS9 Drivers, Stock Control
2017-06-15 19:41:02 +02:00
</dataarea>
</part>
</software>
New working software list additions ----------------------------------- coco_cart: Added Super LOGO and removed all Dragon cartridges dragon_cart: Moved all Dragon cartridges from coco_cart dragon_cass: All known cassette dumps dragon_flop: All known floppy dumps dragon_flex: FLEX System and other Compusense FLEX releases dragon_os9: OS-9, BASIC09, C, Dynacalc, Pascal, RMS, Stylograph dgnalpha_flop: OS-9, NitrOS9, C, Dynacalc, Pascal, RMS, Stylograph, etc.
2017-04-17 17:50:43 +02:00
</softwarelist>
Reference in a new issue Copy permalink