Editing POS (Pong Consoles) CPUs and Other Chips

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 37: Line 37:
 
|[[DOSBox]]<br/>[[DOSBox#Forks|and forks]]
 
|[[DOSBox]]<br/>[[DOSBox#Forks|and forks]]
 
|align=left|{{Icon|Windows|Linux|macOS|FreeBSD}}
 
|align=left|{{Icon|Windows|Linux|macOS|FreeBSD}}
|[https://github.com/joncampbell123/dosbox-x/releases {{DOSBox-XVer}}] (DOSBox-X)<br/>[https://dosbox-staging.github.io {{DOSBoxStagingVer}}] (DOSBox Staging)<br/>[https://github.com/schellingb/dosbox-pure/releases {{DOSBox PureVer}}] (DOSBox Pure)<br/>[https://github.com/realnc/dosbox-core git] (DOSBox-core)<br/><small>''<abbr title="We recommend DOSBox forks instead of DOSBox for advanced users or those seeking specific functionalities, more feature support and modern
+
|[https://github.com/joncampbell123/dosbox-x/releases {{DOSBox-XVer}}] (DOSBox-X)<br/>[https://dosbox-staging.github.io {{DOSBoxStagingVer}}] (DOSBox Staging)<br/>[https://github.com/schellingb/dosbox-pure/releases 0.9.9] (DOSBox Pure)<br/>[https://github.com/realnc/dosbox-core git] (DOSBox-core)<br/><small>[http://www.dosbox.com/download.php?main=1 0.74-3] (DOSBox)</small>
enhancements.">[http://www.dosbox.com/download.php?main=1 0.74-3] (DOSBox)</abbr>''</small>
+
|{{~}} ||{{~}} ||{{✓}} ||{{~}}<ref group=N>[[DOSBox#Forks|DOSBox-X]], [[DOSBox#Forks|DOSBox Staging]], [[DOSBox#Forks|DOSBox Pure]] and [[DOSBox#Forks|DOSBox-core]] forks are still active.</ref> ||{{~}}
|{{~}} ||{{~}} ||{{✓}} ||{{~}}<ref group=N>[[DOSBox#Forks|DOSBox-X]], [[DOSBox#Forks|DOSBox Staging]], [[DOSBox#Forks|DOSBox Pure]] and [[DOSBox#Forks|DOSBox-core]] forks are still active.</ref> ||{{}}
 
 
|-
 
|-
 
|[[DREAMM]]
 
|[[DREAMM]]
Line 48: Line 47:
 
|[https://github.com/dbalsom/martypc MartyPC]
 
|[https://github.com/dbalsom/martypc MartyPC]
 
|align=left|{{Icon|Windows}}<br/>{{Icon|Linux|macOS}}<abbr title="It should build on Linux and MacOS (Including M1) but no release builds for these platforms at the moment.">*</abbr>
 
|align=left|{{Icon|Windows}}<br/>{{Icon|Linux|macOS}}<abbr title="It should build on Linux and MacOS (Including M1) but no release builds for these platforms at the moment.">*</abbr>
|[https://github.com/dbalsom/martypc/releases {{MartyPCVer}}]
+
|[https://github.com/dbalsom/martypc/releases 0.1.3]
 
|{{?}} ||{{~}} ||{{✓}} ||{{✓}} ||{{~}}
 
|{{?}} ||{{~}} ||{{✓}} ||{{✓}} ||{{~}}
 
|-
 
|-
Line 64: Line 63:
 
|align=left|{{Icon|Windows|Linux|macOS|FreeBSD}}
 
|align=left|{{Icon|Windows|Linux|macOS|FreeBSD}}
 
|<abbr title="Latest development version">git artifacts</abbr><ref group=N>[https://nightly.link/mamedev/mame/workflows/ci-windows/master CI-Windows] [https://nightly.link/mamedev/mame/workflows/ci-linux/master CI-Linux] [https://nightly.link/mamedev/mame/workflows/ci-macos/master CI-Macos]</ref></br>[http://www.mamedev.org/release.html {{MAMEVer}}]<br/>[https://buildbot.libretro.com/nightly/ libretro core]
 
|<abbr title="Latest development version">git artifacts</abbr><ref group=N>[https://nightly.link/mamedev/mame/workflows/ci-windows/master CI-Windows] [https://nightly.link/mamedev/mame/workflows/ci-linux/master CI-Linux] [https://nightly.link/mamedev/mame/workflows/ci-macos/master CI-Macos]</ref></br>[http://www.mamedev.org/release.html {{MAMEVer}}]<br/>[https://buildbot.libretro.com/nightly/ libretro core]
|{{~}} ||{{~}} ||{{✓}} ||{{✓}} ||{{~}}
+
|{{~}} ||{{~}} ||{{✓}} ||{{✓}} ||{{~}}[https://github.com/mamedev/mame/blob/master/src/devices/cpu/i386/i386.cpp#L8 *]
 
|-
 
|-
 
|[https://www.pcjs.org/ PCjs]
 
|[https://www.pcjs.org/ PCjs]
Line 141: Line 140:
 
:: One aspect commonly used to compare PCem and 86Box is the emulation performance. PCem v15 introduced a rewritten dynamic recompiler, which was primarily aimed at improving emulation performance in games; however, it also caused minor to severe performance regressions in other applications. 86Box uses the previous recompiler from PCem versions before v15, with optimizations performed by devs, as they have determined that the new one causes too many regressions to be adopted as a sensible default. There is a way for you to try out the new recompiler on 86Box, though. PCem’s emulation of some core system components, such as the Programmable Interval Timer (PIT), takes a few shortcuts to improve performance. These shortcuts are perfectly fine for games, which is what PCem targets; although, they have caused issues with the software preservation side of things. In addition to taking fewer shortcuts, 86Box also tries to follow the specifications of these components, rather than implement the minimum viable feature set, which is - once again - good enough for games, but not good enough for some other applications. Generally speaking, the more accurate a component’s emulation is made, the more host CPU horsepower it will require. In addition to taking fewer shortcuts, 86Box also tries to follow the specifications of these components, rather than implement the minimum viable feature set, which is - once again - good enough for games, but not good enough for some other applications. [https://86box.net/2022/01/07/pcem-migration-guide.html See this guide for more information].
 
:: One aspect commonly used to compare PCem and 86Box is the emulation performance. PCem v15 introduced a rewritten dynamic recompiler, which was primarily aimed at improving emulation performance in games; however, it also caused minor to severe performance regressions in other applications. 86Box uses the previous recompiler from PCem versions before v15, with optimizations performed by devs, as they have determined that the new one causes too many regressions to be adopted as a sensible default. There is a way for you to try out the new recompiler on 86Box, though. PCem’s emulation of some core system components, such as the Programmable Interval Timer (PIT), takes a few shortcuts to improve performance. These shortcuts are perfectly fine for games, which is what PCem targets; although, they have caused issues with the software preservation side of things. In addition to taking fewer shortcuts, 86Box also tries to follow the specifications of these components, rather than implement the minimum viable feature set, which is - once again - good enough for games, but not good enough for some other applications. Generally speaking, the more accurate a component’s emulation is made, the more host CPU horsepower it will require. In addition to taking fewer shortcuts, 86Box also tries to follow the specifications of these components, rather than implement the minimum viable feature set, which is - once again - good enough for games, but not good enough for some other applications. [https://86box.net/2022/01/07/pcem-migration-guide.html See this guide for more information].
 
|-
 
|-
|[https://dosbox-x.com/ DOSBox-X]/[https://docs.libretro.com/library/dosbox_pure/ DOSBox Pure]/[https://github.com/realnc/dosbox-core DOSBox-core]/[https://dosbox-staging.github.io/ DOSBox Staging]:
+
|[https://dosbox-x.com/ DOSBox-X]/[https://docs.libretro.com/library/dosbox_pure/ DOSBox Pure]/[https://dosbox-staging.github.io/ DOSBox Staging]:
 
:[[DOSBox]] is another option for emulating many older computer games specially for pretty good performance with low-end computers but compatibility, accuracy and [[#Hardware_features_and_peripherals|hardware support]] aren't as good as [[PCem]] or [[86Box]]. [[DOSBox]] is no longer updated but it has many "DOSBox forks" over the years. Windows 95/98/ME can be installed in "DOSBox forks" and also supports 3DFX Voodoo emulation. Even more forks are listed in the [https://github.com/dosbox-staging/dosbox-staging/wiki/DOSBox-forks "DOSBox forks" page of DOSBox Staging's GitHub wiki] or [[DOSBox#Forks|here]].
 
:[[DOSBox]] is another option for emulating many older computer games specially for pretty good performance with low-end computers but compatibility, accuracy and [[#Hardware_features_and_peripherals|hardware support]] aren't as good as [[PCem]] or [[86Box]]. [[DOSBox]] is no longer updated but it has many "DOSBox forks" over the years. Windows 95/98/ME can be installed in "DOSBox forks" and also supports 3DFX Voodoo emulation. Even more forks are listed in the [https://github.com/dosbox-staging/dosbox-staging/wiki/DOSBox-forks "DOSBox forks" page of DOSBox Staging's GitHub wiki] or [[DOSBox#Forks|here]].
 
::'''[https://dosbox-x.com/ DOSBox-X]''' is vastly different from other "DOSBox forks" in that it aims to be a complete emulation package that covers all pre-2000 DOS and Windows 9x based hardware scenarios. It features more flexibility by way of config options and an accompanying frontend to customize the DOS VM further, and beyond games it also supports standard software for DOS, as well as DOS-based Windows including Windows 3.x and 9x/ME with 3D acceleration via 3dfx emulation. The project also has its own [https://dosbox-x.com/wiki wiki] which contains extensive documentation on DOSBox-X, and a summary of notable added features can be seen [https://dosbox-x.com/wiki/DOSBox%E2%80%90X%E2%80%99s-Feature-Highlights here]. While DOSBox-X currently supports emulation of [[#Intel_CPUs|IBM PC/XT/AT]], Toshiba AX/J3100, IBM PCjr/Tandy, and [https://emulation.gametechwiki.com/index.php/NEC_PC-9800_series NEC PC-9800 series] architecture, the maintainer, Jonathan Campbell, does not plan to add any other MS-DOS system. This limitation is mainly done to prevent bloating of the codebase, keeping it at a manageable level for himself while also staying organized. However, the codebase does contain stubbed source files for [https://emulation.gametechwiki.com/index.php/FM_Towns_emulators FM Towns] emulation in the event that other programmers want to add that functionality.<br/>
 
::'''[https://dosbox-x.com/ DOSBox-X]''' is vastly different from other "DOSBox forks" in that it aims to be a complete emulation package that covers all pre-2000 DOS and Windows 9x based hardware scenarios. It features more flexibility by way of config options and an accompanying frontend to customize the DOS VM further, and beyond games it also supports standard software for DOS, as well as DOS-based Windows including Windows 3.x and 9x/ME with 3D acceleration via 3dfx emulation. The project also has its own [https://dosbox-x.com/wiki wiki] which contains extensive documentation on DOSBox-X, and a summary of notable added features can be seen [https://dosbox-x.com/wiki/DOSBox%E2%80%90X%E2%80%99s-Feature-Highlights here]. While DOSBox-X currently supports emulation of [[#Intel_CPUs|IBM PC/XT/AT]], Toshiba AX/J3100, IBM PCjr/Tandy, and [https://emulation.gametechwiki.com/index.php/NEC_PC-9800_series NEC PC-9800 series] architecture, the maintainer, Jonathan Campbell, does not plan to add any other MS-DOS system. This limitation is mainly done to prevent bloating of the codebase, keeping it at a manageable level for himself while also staying organized. However, the codebase does contain stubbed source files for [https://emulation.gametechwiki.com/index.php/FM_Towns_emulators FM Towns] emulation in the event that other programmers want to add that functionality.<br/>
::'''[https://docs.libretro.com/library/dosbox_pure/ DOSBox Pure]''' is a new DOSBox fork specifically built for RetroArch/Libretro. According to its project description it aims for simplicity and ease of use just like DOSBox Staging. On top of that it has an advantage over other "DOSBox forks" because of libretro features ([https://www.youtube.com/watch?v=W8zCEf9prmQ EmuVR support], [[Shader_Presets#RetroArch.2FLibretro|Shader presets/Overlays]] and configs etc). Some of the other advantages are save-states, wider platform support (including Switch and Vita) and input auto-configuration fetched from the game database. It's good for users who want to experience their DOS games without too much hassle with settings, in a simple way akin to how console emulators deal with ROMs.
+
::'''[https://docs.libretro.com/library/dosbox_pure/ DOSBox Pure]''' is a new DOSBox fork specifically built for RetroArch/Libretro. According to its project description it aims for simplicity and ease of use just like DOSBox Staging. On top of that it has an advantage over other "DOSBox forks" because of libretro features ([https://www.youtube.com/watch?v=W8zCEf9prmQ EmuVR support], [[Shader_Presets#RetroArch.2FLibretro|Shader presets/Overlays]] and configs etc).
 
:::[https://www.youtube.com/watch?v=fA5SaT9uDa4 0.9.5 version] brings 3dfx emulation support.
 
:::[https://www.youtube.com/watch?v=fA5SaT9uDa4 0.9.5 version] brings 3dfx emulation support.
 
:::[https://old.reddit.com/r/emulation/comments/18ctij3/dosbox_pure_098_released/ 0.9.8 version] brings further improvements to the ATAPI CD-ROM emulation for Windows 9x games with CD copy protection, add support for uncompressed CHD version 5 CD images and [https://www.libretro.com/index.php/retroarch-1-17-new-netplay-features/ add netplay] for multiplayer games that used IPX, Ethernet or a modem over the internet.
 
:::[https://old.reddit.com/r/emulation/comments/18ctij3/dosbox_pure_098_released/ 0.9.8 version] brings further improvements to the ATAPI CD-ROM emulation for Windows 9x games with CD copy protection, add support for uncompressed CHD version 5 CD images and [https://www.libretro.com/index.php/retroarch-1-17-new-netplay-features/ add netplay] for multiplayer games that used IPX, Ethernet or a modem over the internet.
::'''[https://github.com/realnc/dosbox-core DOSBox-core]''' is an alternative core for RetroArch/Libretro, which focuses on being as close in use as upstream DOSBox. Its advantages include using .conf files to run games, ability to use external MIDI synths (like the Roland Sound Canvas VA, the Yamaha S-YXG50, or whatever else) so that you can get much higher quality MIDI music in dosbox-core, and has more configuration options befitting more advanced users. Its disadvantages are slightly worse input lag (like half a frame), lack of save-states and runs on less platforms (Windows, Linux, macOS and Android; consoles like Vita and Switch are unavailable)
 
 
::'''[https://dosbox-staging.github.io/ DOSBox Staging]''' is a DOSBox fork that focuses on ease of use, modern technology and best practices. [https://github.com/dosbox-staging/dosbox-staging/issues/339 3dfx emulation is supported] with the latest releases.
 
::'''[https://dosbox-staging.github.io/ DOSBox Staging]''' is a DOSBox fork that focuses on ease of use, modern technology and best practices. [https://github.com/dosbox-staging/dosbox-staging/issues/339 3dfx emulation is supported] with the latest releases.
 
|-
 
|-
Line 176: Line 174:
 
|-
 
|-
 
|[[QEMU]]
 
|[[QEMU]]
Similar to Bochs, QEMU may not be the perfect x86 emulator, but its versatility, [[Hypervisors|hypervisor]] capabilities, and vast platform support make it a powerful tool for anyone interested in exploring the world of [[Hypervisors|virtualization]]. Its commitment to open-source development and its vibrant community ensure its continued evolution and relevance in the ever-changing world of computing. While QEMU is versatile and great for [[Hypervisors|virtualization/VMs]], if your focus is precise, reasonable and compatible x86 emulation, '''use alternatives like 86Box, PCem or even DOSBox forks'''.
+
Similar to Bochs, QEMU may not be the perfect x86 emulator, but its versatility, [[Hypervisors|hypervisor]] capabilities, and vast platform support make it a powerful tool for anyone interested in exploring the world of virtualization. Its commitment to open-source development and its vibrant community ensure its continued evolution and relevance in the ever-changing world of computing. While QEMU is versatile and great for virtualization/VMs, if your focus is precise, reasonable and compatible x86 emulation, use alternatives like 86Box, PCem or even DOSBox forks.
 
|}
 
|}
  
Line 190: Line 188:
 
:[[Wikipedia:PowerPC]]
 
:[[Wikipedia:PowerPC]]
 
See [[:Category:PowerPC-based]] page for PPC-based systems software emulation.
 
See [[:Category:PowerPC-based]] page for PPC-based systems software emulation.
 
=ARM CPUs=
 
:[[Wikipedia:ARM_architecture_family]]
 
See [[:Category:ARM-based]] page for ARM-based systems software emulation.
 
  
 
=MIPS CPUs=
 
=MIPS CPUs=
Line 1,015: Line 1,009:
 
----
 
----
 
{{NEL}}
 
{{NEL}}
 +
[[Category:Hardware]]
 
[[Category:Computer emulators]]
 
[[Category:Computer emulators]]
 
[[Category:X86-based|*]]
 
[[Category:X86-based|*]]
[[Category:Various Emulation]]
 
[[Category:Microcontrollers|*]]
 
 
{{Consoles}}
 
{{Consoles}}

Please note that all contributions to Emulation General Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Emulation General Wiki:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)