Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Release of v1.15.6

Browse source 
Some FDC tweaks, a CPU emulation fix, and some Debugger message improvements
This commit is contained in:
Jeff Parsons 2014-10-23 20:01:29 -07:00 • committed by jeffpar
commit 326cfbb42c
146 changed files with 6798 additions and 859 deletions
Download patch file Download diff file Expand all files Collapse all files

6
blog/2014/09/30/README.md
View file

@ -5,7 +5,7 @@ Here are a few highlights of the (evolving) JavaScript coding conventions used i
### Tabs vs. Spaces
I've configured my IDE ([PhpStorm](http://www.jetbrains.com/phpstorm/)) to NEVER use tab characters in .js files
I've configured my IDE ([WebStorm](http://www.jetbrains.com/webstorm/)) to NEVER use tab characters in .js files
(spaces only) and to ALWAYS use tab characters in almost every other type of text file. This is largely because
when a web browser displays a JavaScript file (either in the main window or in the Developer Tools window), tabs
usually screw up the formatting, which I find annoying when I'm debugging. XML files, on the other hand,
@ -198,7 +198,7 @@ it a couple of years ago.
I've adopted a zero-tolerance policy for warnings: nothing gets checked in if the Closure Compiler generates even
a single warning.
And finally, speaking of warnings, I've had to tell [PhpStorm](http://www.jetbrains.com/phpstorm/) to "shut up"
And finally, speaking of warnings, I've had to tell [WebStorm](http://www.jetbrains.com/webstorm/) to "shut up"
about a few:
- Unfiltered for…in loop
@ -219,4 +219,4 @@ because it's a useful warning, but I don't like being penalized for functions th
way but can't always be implemented exactly as prototyped.
*[@jeffpar](http://twitter.com/jeffpar)*
*September 30, 2014*
*September 30, 2014*

19
blog/2014/10/23/README.md Normal file
View file

@ -0,0 +1,19 @@
Release of PCjs v1.15.6
---
This is a fairly minor update that fixes a few Floppy Disk Controller (FDC) issues and one CPU emulation bug
that prevented PC-DOS 7.00 from working properly.
There are also some Debugger improvements; for example, if you turn on "fdc" and "int" messages in the
Debugger using the "m fdc on" and "m int on" commands, all FDC (INT 0x13) software interrupts will be logged,
including descriptions and register values.
PC-DOS 7.00 still can't be setup from its non-standard 1.84Mb [XDF](http://www.os2museum.com/wp/the-xdf-diskette-format/)
distribution disk images, "PC-DOS 7.00 (SETUP Disk 2)" through "PC-DOS 7.00 (SETUP Disk 5)", so your best bet is to boot
from the 1.44Mb "PC-DOS 7.00 (Boot Disk)".
Note that you must use a fairly new 80286 machine configuration, like this [8Mhz IBM PC AT](/configs/pc/machines/5170/ega/1152kb/rev3/),
in order to use 1.44Mb diskette images; previous models did not support 3.5-inch diskette drives, unless they had been retrofitted
with a newer [BIOS](/devices/pc/bios/5170/).
*[@jeffpar](http://twitter.com/jeffpar)*
*October 23, 2014*