Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
pcjs/devices/pcx86/machine
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Jeff Parsons 22728fb7e9 v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process
2017-09-24 18:11:44 -07:00
..
5150 v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process 2017-09-24 18:11:44 -07:00
5160 v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process 2017-09-24 18:11:44 -07:00
5170 v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process 2017-09-24 18:11:44 -07:00
att v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process 2017-09-24 18:11:44 -07:00
cdp v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process 2017-09-24 18:11:44 -07:00
compaq v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process 2017-09-24 18:11:44 -07:00
custom v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process 2017-09-24 18:11:44 -07:00
zenith v1.37.1: Fixed a CPU bug wherein resetting a running CPU could result in multiple runCPU() timeout handlers being created (there should never be more than one outstanding runCPU() setTimeout request); also modified the Keyboard component to use a CPU-driven timer instead of setTimeout() for keystroke injection, so that stopping/starting the CPU won't interfere with the injection process 2017-09-24 18:11:44 -07:00
README.md The PCSIG08 README needed to use a "raw" link rather than a Markdown link, so that it could set the "download" attribute on the link, preventing the page's "onbeforeunload" handler from firing (which would otherwise shutdown any machines on the page) 2017-07-19 14:13:29 -07:00

README.md

layout title permalink redirect_from
page IBM PC Machine Configurations /devices/pcx86/machine/
/configs/pc/machines/
/devices/pc/machine/

IBM PC Machine Configurations

PCjs supports these early IBM PC Machines:

PCjs also supports IBM PC-compatibles such as:

Ready-To-Run App Demos

Machines from our IBM PC Application Archive:

Ready-To-Boot Disk Demos

Selected machines from our IBM PC Disk Library:

IBM PC Machines

Shortcuts to most of the preconfigured IBM PC machines in the project are listed below. Some of them include a predefined state, which automatically restores the machine and the specified application to an initial state, while others include a hard disk with preinstalled software.

However, most simply boot an early version of DOS, and the hard disk, if any, will generally be unformatted. From there, you can load other disks from the Disk Library (or mount your own disks) and install other software.

IBM PC 5150 Machines

IBM PC XT 5160 Machines

IBM PC AT 5170 Machines