Commit 88de0fd7 authored by Roger Sanders's avatar Roger Sanders

Added page content for the Sega System 1/2, Sega System 24, and Sega H1 arcade hardware pages.

parent cbefa852
Pipeline #24702525 passed with stage
in 1 minute and 3 seconds
---
layout: default
title: "Sega H1"
---
# Sega H1
![](ReferenceImage.png)
# Status
I have yet to acquire this hardware, or gather any real information on it.
# Overview
Refer to [SegaRetro](https://segaretro.org/Sega_System_24) for a general hardware overview and list of games. The only real information you'll find on this system is what's documented in the [MAME source](https://github.com/mamedev/mame/blob/master/src/mame/drivers/coolridr.cpp). About the only observation I have which appears to not be written down elsewhere is that the communication board appears to only have been present on Cool Riders, not Aqua Stage. If I can get my hands on the hardware, I'll do some work on this system. It seems likely that Sega had big plans for this system when it was designed, but ultimately the system was abandoned shortly after it was developed.
# Miscellaneous Photos
Here's a collection of images of this system that have been posted online from various sources: {% include folder title="Hardware Photos" target="Pictures" %}
---
layout: default
title: "Sega System 1/2"
---
# Sega System 1/2
![](ReferenceImage.png)
# Status
A system 2 board has been acquired in a working state for hardware testing and analysis. System 1 hardware is not currently possessed.
# Overview
Refer to [SegaRetro](https://segaretro.org/Sega_System_2) and [System16](http://www.system16.com/hardware.php?id=694) for a general hardware overview and list of games. I'm not very confident in the general information that's currently available from these sources however, as it seems confusing and in some cases contradictory. It appears there may have been significant hardware variations between System 1/2 games, with different main board layouts, and various extension boards being added to provide game-specific hardware extensions of various kinds. There appears to me to be insufficient information currently available from the various online sources to clearly identify which games were running on which board layouts, and what custom hardware (if any) was added for the various titles. I'm not convinced the System 1/2 were ever considered as formal general purpose hardware platforms, rather I think it's likely that one first game was produced with a game-specific main board. To save time and costs however, that board was then re-used for other games. In some cases the board was used in an identical form, but in other cases the main board was revised to produce a new distinct hardware layout and feature set, but still in a game-specific form. In other cases again, an existing main board was used, but with minor additions to the hardware performed by introducing daughter boards. The terms "System 1" and "System 2" seem entirely made up by the emulation community, with no markings on the boards themselves identifying them in this way, nor the game flyers or manuals, or the schematics.
# Documentation
Document | Author | Description | Source
--- | --- | --- | ---
{% include download title="Choplifter Schematics" target="Schematics/Choplifter.pdf" %} | Sega | Complete hardware schematics for Choplifter running on a 171-5303 main board. These are the original schematics from Sega. The schematics are clean, however slightly lower resolution than would be ideal. Some of the smaller labels are a bit hard to make out. | [www.jammarcade.net](http://www.jammarcade.net/schematics/)
{% include download title="StarJacker Service Manual with Schematics" target="Schematics/StarJacker.pdf" %} | Sega | Full service manual for StarJacker, including the board layout and schematics for the 834-5191 main board. | [www.jammarcade.net](http://www.jammarcade.net/schematics/)
# High Resolution Photos
##TODO##
# Miscellaneous Photos
Here's a collection of images of this system that have been posted online from various sources: {% include folder title="Hardware Photos" target="Pictures" %}
......@@ -13,8 +13,8 @@ After scouring the web for any instructions on how to re-create System 24 disks
# Backing up a disk to PC (.dsk file)
1. Download and install the [fdrawcmd.sys](http://simonowen.com/fdrawcmd) floppy filter driver ([direct](http://simonowen.com/fdrawcmd/FdInstall.exe), {% include download title="mirror" target="FdInstall.exe" %}). This gives low-level access to the floppy controller.
2. Download and extract [SAMdisk 3.8.10](http://simonowen.com/samdisk) ([direct](http://simonowen.com/samdisk/SAMdisk3810.zip), {% include download title="mirror" target="SAMdisk3810.zip" %}). Newer versions may work better, but this was the version tested.
1. Download and install the [fdrawcmd.sys](http://simonowen.com/fdrawcmd) floppy filter driver ([direct](http://simonowen.com/fdrawcmd/FdInstall.exe), {% include download title="mirror" target="Utilities/FdInstall.exe" %}). This gives low-level access to the floppy controller.
2. Download and extract [SAMdisk 3.8.10](http://simonowen.com/samdisk) ([direct](http://simonowen.com/samdisk/SAMdisk3810.zip), {% include download title="mirror" target="Utilities/SAMdisk3810.zip" %}). Newer versions may work better, but this was the version tested.
3. Run the following command:
```shell
samdisk.exe a: "[filename].dsk" -c80
......@@ -27,8 +27,8 @@ If you want to "overdump" the disk (IE, read any additional sectors that might b
Note that this image format is NOT directly compatible with MAME. It contains additional metadata to describe the sector format and other properties of the physical media. This is a good thing if you want a useful disk image for archival purposes. This format is more complete than the raw data dumps in MAME. If you want to convert these .dsk files into the raw .img sector dump format used in MAME though, read on. Instructions are given below.
# Creating a disk from PC backup (.dsk file)
1. Download and install the [fdrawcmd.sys](http://simonowen.com/fdrawcmd) floppy filter driver ([direct](http://simonowen.com/fdrawcmd/FdInstall.exe), {% include download title="mirror" target="FdInstall.exe" %}). This gives low-level access to the floppy controller.
2. Download and extract [SAMdisk 3.8.10](http://simonowen.com/samdisk) ([direct](http://simonowen.com/samdisk/SAMdisk3810.zip), {% include download title="mirror" target="SAMdisk3810.zip" %}). Newer versions may work better, but this was the version tested.
1. Download and install the [fdrawcmd.sys](http://simonowen.com/fdrawcmd) floppy filter driver ([direct](http://simonowen.com/fdrawcmd/FdInstall.exe), {% include download title="mirror" target="Utilities/FdInstall.exe" %}). This gives low-level access to the floppy controller.
2. Download and extract [SAMdisk 3.8.10](http://simonowen.com/samdisk) ([direct](http://simonowen.com/samdisk/SAMdisk3810.zip), {% include download title="mirror" target="Utilities/SAMdisk3810.zip" %}). Newer versions may work better, but this was the version tested.
3. Run the following command:
```shell
samdisk.exe "[filename].dsk" a:
......@@ -38,7 +38,7 @@ That's it! This will create a system 24 floppy disk from an image that was creat
# Converting a .dsk file to a MAME compatible .img file
1. Download and extract the [HxC Floppy Emulator software](http://hxc2001.com/download/floppy_drive_emulator) ([direct](http://hxc2001.com/download/floppy_drive_emulator/HxCFloppyEmulator_soft.zip), {% include download title="mirror" target="HxCFloppyEmulator_soft.zip" %}).
1. Download and extract the [HxC Floppy Emulator software](http://hxc2001.com/download/floppy_drive_emulator) ([direct](http://hxc2001.com/download/floppy_drive_emulator/HxCFloppyEmulator_soft.zip), {% include download title="mirror" target="Utilities/HxCFloppyEmulator_soft.zip" %}).
2. Run "HxCFloppyEmulator.exe"
3. Select "Floppy image->Load" from the menu, and select your .dsk file.
4. Select "Floppy image->Export disk/Save As" from the menu, change the "Save as type" to ".img", enter a filename, and press "Save".
......@@ -46,9 +46,9 @@ That's it! This will create a system 24 floppy disk from an image that was creat
You now have an .img file equivalent to what you would have obtained through "Anadisk", which is what was originally used to create the MAME images. If you want instructions for using Anadisk, read on, as they'll be given later.
# Creating a disk from MAME rom (.img file)
1. Download and install the [fdrawcmd.sys](http://simonowen.com/fdrawcmd) floppy filter driver ([direct](http://simonowen.com/fdrawcmd/FdInstall.exe), {% include download title="mirror" target="FdInstall.exe" %}). This gives low-level access to the floppy controller.
2. Download and extract [SAMdisk 3.8.10](http://simonowen.com/samdisk) ([direct](http://simonowen.com/samdisk/SAMdisk3810.zip), {% include download title="mirror" target="SAMdisk3810.zip" %}). Newer versions may work better, but this was the version tested.
3. Download and extract my InterleaveSystem24 tool ([binary](InterleaveSystem24.zip), [source](InterleaveSystem24Src.zip)).
1. Download and install the [fdrawcmd.sys](http://simonowen.com/fdrawcmd) floppy filter driver ([direct](http://simonowen.com/fdrawcmd/FdInstall.exe), {% include download title="mirror" target="Utilities/FdInstall.exe" %}). This gives low-level access to the floppy controller.
2. Download and extract [SAMdisk 3.8.10](http://simonowen.com/samdisk) ([direct](http://simonowen.com/samdisk/SAMdisk3810.zip), {% include download title="mirror" target="Utilities/SAMdisk3810.zip" %}). Newer versions may work better, but this was the version tested.
3. Download and extract my InterleaveSystem24 tool ([binary](Utilities/InterleaveSystem24.zip), [source](Utilities/InterleaveSystem24Src.zip)).
4. Obtain the MAME rom with the disk you want to create. In my case, it was "crkdownu.zip".
5. Extract the disk image from the MAME rom. In my case, it was "ds3-5000-04d.img".
6. Open a Windows command prompt
......@@ -76,7 +76,7 @@ That's it! You now have a working floppy for the Sega System 24.
# Creating a MAME-compatible disk image using Anadisk
The System 24 disk images in MAME were originally created in a DOS program called Anadisk. Naturally this is where I went first to see if I could write the images back, but surprisingly, you can't write disk images using Anadisk. You can format a disk, and you can specify the unusual sector layout the Sega System 24 uses to store the game data, but there's no option to load data into the formatted sectors. You'd have to type it out byte by byte in the sector editor. Although Sydex, the creators of Anadisk, made a variety of other disk utilities, none of them appear to be able to work with the non-uniform sector sizes used in System 24 disks. The Windows-based utilities above offer a better alternative to working with System 24 disks in every way, however for completeness, here are the steps to create a raw sector image of a System 24 disk in Anadisk:
1. Download Anadisk 2.07 ([direct](anadisk-207.zip)). Do NOT use 2.06. I discovered this version has a bug which resulted in sectors filled with 0xFF being read back incorrectly.
1. Download Anadisk 2.07 ([direct](Utilities/anadisk-207.zip)). Do NOT use 2.06. I discovered this version has a bug which resulted in sectors filled with 0xFF being read back incorrectly.
2. Load Anadisk onto a DOS-based PC with a 1.44MB FDD installed
3. Run anadisk.exe
4. Select "Dump" from the main menu
......
......@@ -2,3 +2,25 @@
layout: default
title: "Sega System 24"
---
# Sega System 24
![](ReferenceImage.png)
# Status
This system has been acquired in a working state for hardware testing and analysis, with both FDD and ROM board support. The 834-6510 I/O board has not currently been acquired.
# Overview
Refer to [SegaRetro](https://segaretro.org/Sega_System_24) and [System16](http://www.system16.com/hardware.php?id=708) for a general hardware overview and list of games.
# Documentation
Document | Author | Description | Source
--- | --- | --- | ---
{% include download title="Official Schematics" target="Schematics/System24.pdf" %} | Sega | Complete hardware schematics for the System 24 main board, FDD controller board, and 834-6510 I/O board. These are the original schematics from Sega. The ROM board is not included in these schematics, however the pinout to the connector used by the ROM board is included, and the ROM board is relatively simple to trace. The schematics are clean and fairly easy to read. | Unknown
{% include download title="834-6510 Schematic" target="Schematics/Capture3.JPG" %} | Apocalypse | Low-res schematic for a reproduction 834-6510 I/O board. As official schematics are available from Sega, look there first. | [arcadefixer.blogspot.com](http://arcadefixer.blogspot.com/2018/05/sega-834-6510-io-board-reproduction.html)<br>[www.arcade-projects.com](https://www.arcade-projects.com/forums/index.php?thread/5503-sega-834-6510-i-o-board-reproduction/)
# High Resolution Photos
##TODO##
# Miscellaneous Photos
Here's a collection of images of this system that have been posted online from various sources: {% include folder title="Hardware Photos" target="Pictures" %}
......@@ -4,6 +4,7 @@ contentsData:
- title: Arcade Info
childlist:
- title: Sega System 1/2
url: Arcade/SegaSystem1/
- title: Sega System 16A/16B
- title: Sega System 18
- title: Sega System 24
......@@ -15,6 +16,7 @@ contentsData:
- title: Sega X Board
- title: Sega Y Board
- title: Sega H1
url: Arcade/SegaH1/
- title: Sega System E
- title: Sega System C
- title: Sega Mega-Tech
......
This diff is collapsed.
{% assign downloadPathFirstChar = include.target | slice: 0 %}{% if downloadPathFirstChar == '/' %}{% assign downloadPath = include.target %}{% else %}{% assign pageBaseUrl = page.url | split: '/' | pop | join: '/' %}{% assign downloadPath = pageBaseUrl | append: '/' | append: include.target %}{% endif %}{% assign downloadEntry = site.data.externalDownloadLinks.externalFileList | where: "path", downloadPath | first %}{% assign linkText = include.title | default: include.target | split: '/' | last %}{% if downloadEntry %}[{{ linkText }}](https://drive.google.com/uc?export=download&id={{ downloadEntry.id }}){% else %}<span class="missingDownload">{{ linkText }}</span>{% endif %}
\ No newline at end of file
{% assign downloadPathFirstChar = include.target | slice: 0 %}{% if downloadPathFirstChar == '/' %}{% assign downloadPath = include.target %}{% else %}{% assign pageUrlLastChar = page.url | split: "" | reverse | first %}{% if pageUrlLastChar == '/' %}{% assign pageBaseUrl = page.url %}{% else %}{% assign pageBaseUrl = page.url | split: '/' | pop | join: '/' | append: '/' %}{% endif %}{% assign downloadPath = pageBaseUrl | append: include.target %}{% endif %}{% assign downloadEntry = site.data.externalDownloadLinks.externalFileList | where: "path", downloadPath | first %}{% assign linkText = include.title | default: include.target | split: '/' | last %}{% if downloadEntry %}[{{ linkText }}](https://drive.google.com/uc?export=download&id={{ downloadEntry.id }}){% else %}<span class="missingDownload">{{ linkText }}</span>{% endif %}
\ No newline at end of file
{% assign downloadPathFirstChar = include.target | slice: 0 %}{% if downloadPathFirstChar == '/' %}{% assign downloadPath = include.target %}{% else %}{% assign pageUrlLastChar = page.url | split: "" | reverse | first %}{% if pageUrlLastChar == '/' %}{% assign pageBaseUrl = page.url %}{% else %}{% assign pageBaseUrl = page.url | split: '/' | pop | join: '/' | append: '/' %}{% endif %}{% assign downloadPath = pageBaseUrl | append: include.target %}{% endif %}{% assign downloadEntry = site.data.externalDownloadLinks.externalFileList | where: "path", downloadPath | first %}{% assign linkText = include.title | default: include.target | split: '/' | last %}{% if downloadEntry %}[{{ linkText }}](https://drive.google.com/drive/u/3/folders/{{ downloadEntry.id }}){% else %}<span class="missingDownload">{{ linkText }}</span>{% endif %}
\ No newline at end of file
{% assign downloadPathFirstChar = include.target | slice: 0 %}{% if downloadPathFirstChar == '/' %}{% assign downloadPath = include.target %}{% else %}{% assign pageUrlLastChar = page.url | split: "" | reverse | first %}{% if pageUrlLastChar == '/' %}{% assign pageBaseUrl = page.url %}{% else %}{% assign pageBaseUrl = page.url | split: '/' | pop | join: '/' | append: '/' %}{% endif %}{% assign downloadPath = pageBaseUrl | append: include.target %}{% endif %}{% assign downloadEntry = site.data.externalDownloadLinks.externalFileList | where: "path", downloadPath | first %}{% assign linkText = include.title | default: include.target | split: '/' | last %}{% if downloadEntry %}![{{ linkText }}](https://drive.google.com/uc?id={{ downloadEntry.id }}){% else %}<span class="missingImage">{{ linkText }}</span>{% endif %}
\ No newline at end of file
......@@ -21,4 +21,4 @@ In addition to formal documentation from official sources, original research is
This site is not a wiki, however it is open for external contributions. The main site content is hosted in a public Git repo at <https://gitlab.com/ExodusWeb/TechDocs>, and is written in basic markdown. Large files are hosted externally, currently on [Google Drive](https://drive.google.com/drive/u/3/folders/1011Us5E-AvRVPPhTkg7gdDacz5CbqP-M). It is intended and encouraged for you to clone the entire site through these channels, so that you can use this site as an offline resource. If you want to contribute, fork the git repo and submit a merge request, with large files referenced externally.
The information hosted on this site in some cases may have originally been of a confidential nature, however in all such cases we believe the works have been legally obtained and stand as abandoned by their original owners, and we assert the sharing of that material for research and archival purposes here is exempt from copyright restrictions under the fair use category.
Please note that some documents and tools hosted on this site may have originally been of a confidential nature, however in all such cases we believe the works have been legally obtained. Additionally, we assert that copyrighted works hosted here stand as abandoned by their original owners, and consider the sharing of this material here for research and archival purposes as exempt from copyright restrictions under the fair use category.
\ No newline at end of file
......@@ -15,11 +15,31 @@ h2 {
font-size: 110%;
}
img {
max-width: 100%;
width:100%;
height:100%;
max-width:600px;
}
pre {
font-size: 100%;
}
table {
border-spacing: 0;
border-collapse: collapse;
}
table tr:nth-child(2n) {
background-color: #f6f8fa;
}
table tr {
border-top: 1px solid #c6cbd1;
}
table th, table td {
padding: 6px 13px;
border: 1px solid #dfe2e5;
}
table th {
background-color: #f6f8fa;
font-weight: 600;
}
.tocRoot {
list-style-type: none;
margin: 0;
......@@ -260,6 +280,10 @@ pre {
font-weight: bold;
color: Red;
}
.missingImage {
font-weight: bold;
color: Red;
}
.argumentName {
font-style:italic;
font-size: 110%;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment