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 |
|
Jeff Parsons
|
34bb5f2d28
|
Updated the Closure Compiler and bumped the project version number
|
2017-08-25 09:58:26 -07:00 |
|
Jeff Parsons
|
159588623a
|
Fixed PCx86 "Save Machine" functionality (broken by the inclusion of source maps at the end of the compiled scripts)
|
2017-08-16 20:52:15 -07:00 |
|
Jeff Parsons
|
eb79d0e87e
|
Working on version 1.36.1
|
2017-08-07 19:33:26 -07:00 |
|
Jeff Parsons
|
9e149dda6a
|
Added support for a new "flicker" PCx86 Video property that simulates good old-fashioned CGA flicker -- don't leave home without it!
|
2017-07-12 16:22:26 -07:00 |
|
Jeff Parsons
|
0ec54f6da4
|
Started work on v1.35.2
|
2017-06-27 12:01:19 -07:00 |
|
Jeff Parsons
|
9626fed7c2
|
Got rid of more app-specific demo machines (eg, DONKEY and WIN101); demos like that are more properly located in either the /apps or /disks folders (not /devices)
|
2017-06-22 12:03:52 -07:00 |
|
Jeff Parsons
|
6fd2a3bcb6
|
Started work on v1.35.1
|
2017-06-21 11:18:02 -07:00 |
|
Jeff Parsons
|
37e0e660c9
|
Bumped next release version to 1.35.0
|
2017-06-01 15:35:25 -07:00 |
|
Jeff
|
40c588a069
|
Starting work on v1.34.3
|
2017-03-21 14:32:50 -07:00 |
|
Jeff
|
3508b1050e
|
Started work on v1.34.2: More PDP-10 opcode handlers
|
2017-03-01 12:26:57 -08:00 |
|
Jeff Parsons
|
ce3479c422
|
Promoted version to 1.34.1
|
2017-02-28 16:35:16 -08:00 |
|
Jeff Parsons
|
65bd1348dc
|
Starting work on v1.34.0
|
2017-02-04 17:27:25 -08:00 |
|
Jeff Parsons
|
8f0b808b1e
|
Switching to machine XML files that use a machine 'type' attribute rather than 'class'; 'class' can still be used to specify the machine type if 'type' is omitted, but going forward, it should only be used to specify an alternate CSS class
|
2017-01-31 22:05:04 -08:00 |
|
Jeff Parsons
|
323a42be37
|
Converted the rest of the PCjs machines to ES6
|
2017-01-31 11:44:33 -08:00 |
|
Jeff Parsons
|
c59dd06914
|
Start work on v1.32.2
|
2017-01-08 23:15:14 -08:00 |
|
Jeff Parsons
|
23cfefa971
|
Bumped version to 1.32.1, since there is an interface change (addition) to support sticky machines
|
2017-01-03 17:34:31 -08:00 |
|
Jeff Parsons
|
f87161f5d6
|
v1.32.0: The New Year Release
|
2016-12-30 15:56:01 -08:00 |
|
Jeff Parsons
|
28f47a3424
|
Starting on v1.31.1
|
2016-12-27 16:33:00 -08:00 |
|
Jeff Parsons
|
f4f6181923
|
v1.31.0 marks our first transition to ES6 classes, but only for PDPjs initially (which is why there must be both /lib and /es6 files in the shared folder for now)
|
2016-12-18 11:31:55 -08:00 |
|
Jeff Parsons
|
d8f0e64329
|
Merge the last set of changes from the gh-pages branch
|
2016-12-04 11:31:03 -08:00 |
|
Jeff Parsons
|
b54253acf9
|
Numerous changes to make paper tape configurations more consistent with disk configurations. This allows all devices to share the machine-wide "autoMount" configuration object, now that the PC11 has a proper device name ("PTR"), making its properties distinguishable from those for RK11 and RL11 drives (eg, "RK0", "RL0", etc). And all the tape/disk components now use "Load" functions to connect a tape or disk to a device ("Attach" is deprecated). And finally, all tape/disk components now support operations to deposit their media directly into memory -- although in this case, the names of the operations are necessarily different: "Read" for tape images, "Boot" for disk images. The difference is partly historical convention but also reflects the fact that a "Boot" operation is more limited: paper tapes were designed to be completely loaded into memory, whereas bootable disks are designed for only the first sector to be loaded and executed. Also, paper tape images are now flagged as non-auto-starting, because they often require some user action (eg, loading another tape, setting some switches, etc), whereas disk boot sectors are flagged as auto-starting (see the fStart parameter of the loadImage() interface in the RAM component).
|
2016-12-03 14:49:51 -08:00 |
|
Jeff Parsons
|
aa2aebd89a
|
Working on v1.30.6 now
|
2016-12-03 09:04:34 -08:00 |
|
Jeff Parsons
|
be02b5780b
|
Starting next phase of PDP-11 support (whatever that turns out to be)
|
2016-11-27 11:15:29 -08:00 |
|
Jeff Parsons
|
a29ee56a5d
|
Starting work on 1.30.4 and some additional PDP-11 hardware support
|
2016-11-21 13:16:38 -08:00 |
|
Jeff
|
56bdd84e1a
|
Promoted the working version to 1.30.3
|
2016-11-03 16:24:56 -07:00 |
|
Jeff Parsons
|
fa87224856
|
Minor machine description tweaks
|
2016-10-23 08:54:35 -07:00 |
|
Jeff Parsons
|
89dc2660f1
|
Added more PDP-11 paper tape resources
|
2016-10-22 21:57:45 -07:00 |
|
Jeff Parsons
|
5d5629c27b
|
More README updates, particularly in regard to DEC's Absolute Loader
|
2016-10-22 14:21:33 -07:00 |
|
Jeff Parsons
|
181229833e
|
Synced with website updates
|
2016-10-22 10:31:44 -07:00 |
|
Jeff Parsons
|
2274c97215
|
Starting work on v1.30.2
|
2016-10-22 00:23:55 -07:00 |
|
Jeff Parsons
|
ed59b61013
|
Fixed the autoMount setting the PC11 demo config, and updated some the demo READMEs
|
2016-10-21 22:42:52 -07:00 |
|
Jeff Parsons
|
7beaf7ca7b
|
More README updates
|
2016-10-20 15:32:37 -07:00 |
|
Jeff Parsons
|
21d91cbcfa
|
Fixed the components.xsl for PDPjs machines, and added more instructions, resource links, etc, for the PDP-11 demo machines
|
2016-10-20 15:16:22 -07:00 |
|
Jeff Parsons
|
80741b98d0
|
XML layout tweaks
|
2016-10-19 15:45:33 -07:00 |
|
Jeff Parsons
|
aa131d5413
|
Changed name of tape demo configuration
|
2016-10-17 15:29:59 -07:00 |
|
Jeff Parsons
|
ed24094683
|
Lots of tweaks in advance of PDPjs support for loading tape files
|
2016-10-17 15:19:01 -07:00 |
|
Jeff Parsons
|
980c2ac5ab
|
Updated PC8080 and PDPjs to support RAM images, eliminating the need for the old "writable ROM" kludge; RAM images can include their own load and exec addresses as part of the JSON file, but the RAM component can provide explicit overrides (if no load address is specified either way, the default load address is the starting RAM address)
|
2016-10-17 11:01:32 -07:00 |
|