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

5170 and Enhanced DEBUG updates

Browse source
This commit is contained in:
Jeff Parsons 2016-04-11 18:19:53 -07:00
commit b55e6ba2c4
30 changed files with 720 additions and 62 deletions
Download patch file Download diff file Expand all files Collapse all files

6
devices/pc/machine/5150/README.md
View file

@ -1,15 +1,15 @@
---
layout: page
title: IBM PC Machines (Model 5150)
title: IBM PC (Model 5150) Machines
permalink: /devices/pc/machine/5150/
redirect_from:
- /configs/pc/machines/5150/
---
IBM PC Machines (Model 5150)
IBM PC (Model 5150) Machines
---
All our Model 5150 configurations of the IBM PC are located here, including:
All our IBM PC (Model 5150) configurations are located here, including:
* [IBM PC with Monochrome Display](/devices/pc/machine/5150/mda/)
* [IBM PC with Color Display](/devices/pc/machine/5150/cga/)

6
devices/pc/machine/5160/README.md
View file

@ -1,13 +1,13 @@
---
layout: page
title: IBM PC XT (Model 5160)
title: IBM PC XT (Model 5160) Machines
permalink: /devices/pc/machine/5160/
---
IBM PC XT Machines (Model 5160)
IBM PC XT (Model 5160) Machines
---
All our Model 5160, aka IBM PC XT, configurations are located here, including:
All our IBM PC XT (Model 5160) configurations are located here, including:
* [IBM PC XT with Monochrome Display](/devices/pc/machine/5160/mda/)
* [IBM PC XT with Color Display](/devices/pc/machine/5160/cga/)

447
devices/pc/machine/5170/README.md
View file

@ -1,15 +1,456 @@
---
layout: page
title: IBM PC AT (Model 5170)
title: IBM PC AT (Model 5170) Machines
permalink: /devices/pc/machine/5170/
---
IBM PC AT Machines (Model 5170)
IBM PC AT (Model 5170) Machines
---
All our Model 5170, aka IBM PC AT, configurations are located here, including:
All our IBM PC AT (Model 5170) configurations are located here, including:
* [IBM PC AT with MDA Display](/devices/pc/machine/5170/mda/)
* [IBM PC AT with CGA Display](/devices/pc/machine/5170/cga/)
* [IBM PC AT with EGA Display](/devices/pc/machine/5170/ega/)
* [IBM PC AT with VGA Display](/devices/pc/machine/5170/vga/)
The IBM PC AT 5170 came in several different models over a 3-year period, as summarized below.
### 5170 Models 68 and 99
Models 68 and 99 were [introduced](#ibm-pc-at-5170-models-68-and-99-announcement) in August 1984:
* Model 68
- Type 1 motherboard
- 6 MHz CPU
- 256Kb RAM
- [Rev 1 BIOS](/devices/pc/rom/5170/#ibm-pc-at-rom-bios-rev-1) dated "01/10/84"
* Model 99
- All of the above
- 256Kb additional RAM (total of 512Kb)
- 20Mb Hard Drive
- 1 Serial/Parallel Adapter
### 5170 Model 239
Model 239 was introduced in October 1985:
* Model 239
- Type 2 motherboard
- 6 MHz CPU
- 512Kb RAM
- 30Mb Hard Drive
- 1 Serial/Parallel Adapter
- [Rev 2 BIOS](/devices/pc/rom/5170/#ibm-pc-at-rom-bios-rev-2) dated "06/10/85"
### 5170 Models 319 and 339
Models 319 and 339 were introduced in April 1986:
* Model 319
- Type 3 motherboard
- 8 MHz CPU
- 512Kb RAM
- 30MB hard drive
- 1 Serial/Parallel Adapter
- [Rev 3 BIOS](/devices/pc/rom/5170/#ibm-pc-at-rom-bios-rev-3) dated "11/15/85"
* Model 339
- All of the above
- Enhanced 101-key keyboard
IBM PC AT Configuration Options
---
The Model 5170 doesn't have DIP switches like previous models, but it still has a few switches and jumpers.
First and foremost, there is a **Display Switch** near the battery connector that must be pushed "toward the
front of your system unit" if you have a CGA that is your only (or primary) display adapter, or "toward the
back of your system unit" if you're using an MDA as your only (or primary) display.
In PCjs, the Model 5170 **Display Switch** is configured with the <[ChipSet](/docs/pcjs/chipset/)> *monitor*
property, which you can set to either "mono" (aka "mda") or "color" (aka "cga"). Unlike the Model 5150/5160 DIP
switches, there is no UI for this switch, so once the machine has been created, it cannot be changed by the user.
Also, there is the "keyboard inhibit switch"; it defaults to UNLOCKED and stays UNLOCKED, since no UI or
configuration property is currently provided.
Finally, there is a "manufacturing jumper" that can be installed, enabling additional diagnostic functions
in the ROM; it defaults to UNINSTALLED and stays UNINSTALLED, since no UI or configuration property is currently
provided.
The rest of a Model 5170 machine's configuration is normally handled through CMOS settings, such as the number and type
of floppy diskette drives, which can be configured with the <[ChipSet](/docs/pcjs/chipset/)> *floppies* property;
e.g.:
<chipset id="chipset" model="5170" floppies="[1200,1200]" monitor="color"/>
The number of elements in the array determines the number of drives, and the value of each element
determines the type of drive; the value corresponds to the maximum supported diskette size, in Kb:
+ 360
+ 720
+ 1200
+ 1440
However, for the 3.5-inch diskette capacities (720 and 1440) to work properly, the machine should also use a
["Rev 3"](/devices/pc/rom/5170/#ibm-pc-at-rom-bios-rev-3) IBM PC AT ROM BIOS and boot with DOS 3.20 or later.
Like the **Display Switch**, there is no UI for this or any other CMOS setting, so once the machine has been created,
it cannot be changed by the user.
---
IBM PC AT 5170 (Models 68 and 99) Announcement
---
The following details come from a [copy](http://www.minuszerodegrees.net/misc/IBM%20PC%20AT%205170%20announcement%20letter.txt)
of IBM's PC AT Announcement Letter, dated August 14, 1984.
> The IBM Personal Computer AT is designed for professional
applications, office environments, and increased personal
productivity. It includes many advanced technology features
previously not available in IBM Personal Computers: increased
performance, advanced microprocessor, high capacity diskette drives,
high capacity fixed disk drives, large memory capacity, and advanced
co-processor. The 5170 provides compatibility with existing hardware
and software products for the IBM Personal Computer family.
> ### HIGHLIGHTS
> * Performs more than two times faster than current members of the IBM Personal Computer family
> * Based on high-performance Intel 80286 microprocessor, compatible with the IBM Personal Computer family
> * Includes 1.2Mb high-capacity diskette drives
> * Allows 20Mb fixed disk drives
> * Contains a standard combination fixed disk and diskette adapter
> * Provides 512Kb memory capacity on the system board
> * Offers a combination Serial (Asynchronous)/Parallel (Printer) Adapter
> * Allows workstation growth with eight I/O expansion slots
> * Includes an improved keyboard
> * Includes a clock/calendar with battery backup
> * Provides improved security capability with a standard keylock
> ### DESCRIPTION
> The 5170 system unit/keyboard includes the following standard features:
> * Advanced high-performance Intel 80286 microprocessor
> * ROM based automatic power on self test of system components
> * ROM based BASIC language interpreter
> * 8086 compatible real address mode
> * Protected virtual address mode
> * 256Kb of memory (Model 68)
> * 512Kb of memory (Model 99)
> * 1.2Mb high capacity diskette drive
> * Diskette interface
> * 20Mb fixed disk drive (Model 99)
> * Fixed disk interface
> * Fixed disk-in-use indicator light (red)
> * Serial/parallel interface (Model 99)
> * System clock/calendar/system configuration storage with battery back-up
> * Sound system
> * Keylock
> * Bi-directional keyboard interface
> * Enhanced keyboard
> * Switchable worldwide power supply
> * Power-on indicator light (green)
> * Eight I/O expansion slots
> * Socket for 80287 math co-processor
> * 24-bit addressing
> * 16-bit data path
> * Seven-channel direct memory access (DMA)
> * 16-level interrupt
> * Three programmable timers
> Based on a high performance 16/24-bit Intel 80286 microprocessor,
both models of the 5170 are equipped with a high capacity (1.2Mb)
diskette drive, enhanced keyboard, ROM based BASIC language,
clock/calendar with battery backup, and keylock. Standard memory on
Model 68 is 256Kb and on Model 99 is 512Kb. In addition, Model 99 is
equipped with a 20Mb fixed disk drive and a serial
(asynchronous)/parallel (printer) adapter. Each system can be further
expanded through customer setup options. Model 68 memory may be
expanded to 512Kb by addition of pluggable memory modules on the
system board. Both models may be further expanded to 640Kb with the
128Kb memory option or up to 3Mb with 512Kb memory options.
> Additional direct access storage is available with a 20Mb
Fixed Disk Drive, a second 1.2Mb High Capacity Diskette Drive, and a
Dual-sided (320/360Kb) Diskette Drive. A maximum of two diskette
drives and one fixed disk drive, or one diskette drive and two fixed
disk drives can be attached to the system unit. These combinations
result in direct access storage capacity of up to 41.2Mb.
> DOS 3.0 supports the 20Mb Fixed Disk Drive and 1.2Mb High
Capacity Diskette Drive in the 5170 system. With DOS 3.0, the 1.2Mb
diskette drive will also read single- and dual-sided diskettes
formatted at 160/180Kb and 320/360Kb capacity, respectively. The
Dual-sided Diskette Drive (320/360Kb) option is available for
downward diskette portability with other IBM Personal Computer family
members.
> The IBM Personal Computer AT is also supported by two other
operating systems. Personal Computer Interactive Executive (PC/IX)
Version 1.1 will support the IBM Personal Computer AT in
compatibility, real address mode. PC/IX will be available in the
fourth quarter of 1984. The IBM Personal Computer XENIX* will support
the IBM Personal Computer AT in the 80286 protected address mode. IBM
Personal Computer XENIX will be available in the first quarter of
1985.
> The 5170 contains eight option (feature) slots that support
feature cards for additional devices, features, or memory. Six of the
slots support either the advanced 16-bit or 8-bit option cards. Two
support 8-bit option cards only. However, both models use one 16-bit
slot for the standard combination fixed disk and diskette drive
adapter. The Model 99 uses one 8-bit slot for the Serial/Parallel
Adapter. The result is seven available expansion slots on Model 68
and six on Model 99.
> Both models include a world-wide power supply and a
temperature-controlled variable speed cooling fan that significantly
reduces acoustical noise in most user environments. Both models also
include a security keylock, which, when locked by the user, prevents
removal of the 5170 cover, initialization of the system, and entry of
command/data from the keyboard.
> The keyboard is attached to the 5170 via a ten-foot coiled
cable, permitting a variety of workspace configurations. The enhanced
84-key keyboard, with an adjustable typing angle, offers commonly
used data and word processing functions along with separate
typewriter and numeric keypads. Key-location enhancements and mode
indicators (Cap Lock, Numeric Lock, Scroll Lock) improve keyboard
usability. Special symbols may be accessed with a combination of
keys. Depending on the application program, from 10 to 40 special
function keys may be supported.
> Exploring the IBM Personal Computer AT, a program on a
diskette, is supplied with the 5170. It will familiarize a new
computer user with the 5170. The program takes 1-1/2 to 2-1/2 hours
to complete. There are two versions of the program, monochrome and
color. The program is self-loading from the diskette. It contains
tutorial information on the keyboard, printer, and disk storage, as
well as DOS and text editing. It requires a 5170 with a minimum of
one diskette drive, 256Kb of storage, and one display adapter (either
monochrome or color).
> ### OPTIONAL FEATURES
> #### 256Kb Memory Module Kit (#0202)
> This option increases the 5170 Model 68 memory from 256Kb to
512Kb. The kit consists of 18 modules that are plugged into existing
sockets on the system board. A maximum of one kit may be installed on
Model 68 only. It is required on the Model 68 for installation
of #0209 and #0203.
> #### 512Kb Memory Expansion Option (#0203)
> This option adds memory above 1Mb, in 512Kb increments. Up to
five options may be plugged into the I/O expansion slots of the
system unit to provide a total of three megabytes of primary storage.
Performance characteristics are the same as other 5170 user memory.
> The system unit must have at least 512 Kb installed. This option
requires one 16-bit expansion slot. Note: This option may not be used
for address storage from 512Kb to 640Kb. The memory range from 640Kb
to 1Mb is reserved for system functions.
> #### 128Kb Memory Expansion Option (#0209)
> This option expands the memory from 512Kb to 640Kb.
Performance characteristics are the same as other 5170 user memory.
Only one 128Kb Memory Expansion Option may be installed on a 512Kb
system unit and it requires a 16-bit expansion slot.
> #### 20Mb Fixed Disk Drive (#0205)
> Two optional fixed disk drives may be installed on Model 68 or
one, as a second fixed disk drive, on Model 99, providing a total of
40Mb of fixed disk storage capacity. Space and power are provided in
the system unit for this drive(s). All fixed disk or diskette drives
use the standard combination fixed disk and diskette drive adapter in
the system unit. A dedicated landing zone for the read/write heads
is available to protect the file and its contents during shipping,
movement, or storage. Increased performance of 40 ms average access
time is possible from the quasi-closed loop servo positioning system
utilized in the drive. The number of fixed disk drives and diskette
drives must not exceed three. No more than two fixed disk drives can
be installed in a system unit.
> CHARACTERISTICS:
> * 20Mb of storage
> * 512 bytes per sector
> * 17 sectors per track
> * 615 tracks per surface (cylinders)
> * 40 ms average access time
> * four surfaces
> * 3573 RPM
> * 5M bit per second transfer rate
> * Dimensions:
> - Height 82.55 mm (3.25 inches)
> - Width 154.3 mm (6.1 inches)
> - Depth 203.2 mm (8.0 inches)
> - Weight 2.9 Kg (6.4 lbs.)
> #### High Capacity Diskette Drive (#0206)
> This is a half-high, 5-1/4-inch, dual-sided drive with 1.2Mb
storage capacity. Space and power have been provided in the system
unit for up to two drives. The drive is fully self-contained and
consists of a spindle drive system, a read positioning system and a
read/write/erase system.
> One of these drives is standard in both models. An optional
second drive (#0206) may be installed in the system unit directly
under the first if the space is not occupied by another disk or
diskette drive. Both drives use the standard fixed disk and diskette
drive adapter in the system unit.
> The drive uses the new 96-TPI, high density media. In
addition, it will read or write 48-TPI, single- or dual-sided media
written for the IBM PCjr, IBM Personal Computer, IBM Personal
Computer XT, and IBM Portable Personal Computer, giving a high level
of compatibility with existing applications. However, once the
48-TPI media has been written in this drive, it may only be readable
on a high capacity diskette drive.
> CHARACTERISTICS:
> * 1.2Mb storage
> * 512 bytes per sector
> * 15 sectors per track
> * 96 tracks per inch
> * Two sides
> * 80 tracks per side
> * 360 RPM
> * Supports 300 and 500 bits/sec data transfer rate
> * 94 ms average access time in 96-TPI mode
> * Dimensions:
> - Height 42.9 mm (1.7 inches)
> - Width 154.3 mm (6.1 inches)
> - Depth 203.2 mm (8.0 inches)
> - Weight: 1.6 Kg (3.5 lbs.)
> #### Dual-sided Diskette Drive (#0207)
> This diskette drive permits the exchange of 320/360Kb diskette
media between the Personal Computer AT, to the IBM Personal Computer,
the IBM Personal Computer XT, the IBM Portable Personal Computer, and
the IBM PCjr. It is a half-high, 5-1/4-inch, dual-sided drive with a
320/360Kb storage capacity. Space and power for one drive have been
provided in the system unit. The drive is fully self-contained and
consists of a spindle drive system, a read positioning system, and a
read/write/erase system.
> This drive is available for both 5170 models. It is installed
in the system unit directly under the standard high capacity diskette
drive if the space is not occupied by another fixed disk or diskette
drive. This drive uses the standard fixed disk and diskette drive
adapter in the system unit.
> CHARACTERISTICS:
> * 320/360Kb of storage
> * 512 bytes per sector
> * 8/9 sectors per track
> * Two sides
> * 91 ms average access time
> * 40 tracks per surface
> * 48 tracks per inch
> * 300 RPM
> * Transfer rate of 250K bits/second
> * Dimensions:
> - Height 42.9 mm (1.7 inches)
> - Width 154.3 mm (6.1 inches)
> - Depth 203.2 mm (8.0 inches)
> - Weight: 1.6 Kg (3.5 lbs.)
> #### Math Co-Processor (#0211)
> This option is a high performance numeric 80287 processor
extension with floating point, extended integer, and BCD data types,
compatible with the Intel 8087 Math Co-Processor. When installed,
the system fully conforms to the proposed IEEE Floating Point
Standard and is an excellent facility for high-performance numeric
processing. Only one 80287 can be installed in a system unit.
> #### Serial/Parallel Adapter (#0215)
> This option provides a serial port and a parallel port. It
occupies only one expansion slot of either type. The serial portion
is fully programmable and supports asynchronous communications from
50 to 9600 baud. The back of the adapter has a nine-pin D-shell
connector that is classified as an RS232-C port. When the optional
10-foot Serial Adapter Cable (#0217) or 10-inch Serial Adapter
Connector (#0242) is connected to the adapter, the 25-pin end of the
cable or connector has all the signals of a standard EIA RS232-C
interface. The parallel portion of the adapter provides the ability
to attach various devices that accept eight bits of parallel data.
The parallel port is provided by a 25-pin, D-shell connector. One or
two Serial/Parallel Adapters may be installed in either model. Note:
This adapter does not support current loop operation. The 5218
Printer is not supported.
> #### Prototype Adapter (#0220)
> This adapter is 4.8 inches high by 13.12 inches long and plugs
into any system unit expansion slot except 1 or 7. Two card edge
tabs, one 2 by 31 positions and one 2 by 18 positions, provide all
system control signals and voltages. No components are shipped with
this card.
> The adapter contains a voltage bus (+5 Vdc) and a ground bus
(0 Vdc). Each bus borders the adapter with the ground bus on the
component side and the voltage bus on on the pin side. A system
interface (wiring only) is also provided with a space for a jumper to
specify whether the device has an 8- or a 16-bit data bus. This
adapter also accommodates a D-shell connector from 9 to 37 positions.
A recommended system interface logic diagram is available along with
a list of recommended components to be used to interface custom logic
to the 5170. Up to five Prototype Adapters can be installed in a
system unit. Each requires a 16-bit expansion slot.
> #### Binary Synchronous Communications Adapter (#1204)
> The BSC Adapter provides an EIA RS232-C interface. It is
compatible with the IBM Personal Computer, the Portable Personal
Computer, and the Personal Computer XT. A maximum of two BSC Adapters
may be installed. Only one BSC Adapter may be installed if an SDLC
Adapter is installed.
> #### SDLC Communications Adapter (#1205)
> The SDLC Communications Adapter provides an EIA RS232-C
interface. It is compatible with the IBM Personal Computer, the
Portable Personal Computer, and the Personal Computer XT. Only one
SDLC Adapter may be installed.
> #### Floor Standing Enclosure (#0218)
> This optional enclosure is available to customers who desire
to remove their system unit from the work surface. With the system
unit mounted vertically in the floor standing enclosure, only the
essential parts of the system such as the display and keyboard need
to be on the work surface. The unit may be positioned left or right
of the workspace or under the workspace.
> #### Display Stand (#0216)
> The display stand is available for the IBM 5151 Monochrome
Display Model 1 and IBM 5153 Color Display Model 1. It can be placed
under the display to allow the customer to tilt and/or swivel the
display for comfortable viewing.
> ### PUBLICATIONS
> Each system will be shipped with three manuals:
> * IBM Personal Computer AT Installation and Setup Manual (#2491)
> * IBM Personal Computer AT Guide to Operations (#2241)
> * IBM Personal Computer Basic Reference Manual Version 3.0 (#1132)
> The following are available for purchase:
> * IBM Personal Computer AT Technical Reference Manual (#2243)
> * IBM Personal Computer AT Hardware Maintenance and Service Manual (#2242)

5
devices/pc/machine/5170/cga/640kb/rev3/debugger/machine.xml
View file

@ -6,7 +6,7 @@
<cpu id="cpu286" model="80286"/>
<ram id="ramLow" addr="0x00000" size="0xa0000"/>
<rom id="romBIOS" addr="0xf0000" size="0x10000" alias="0xff0000" file="/devices/pc/rom/5170/1985-11-15/ATBIOS-REV3.json"/>
<video ref="/devices/pc/video/ibm/mda/ibm-mda.xml"/>
<video ref="/devices/pc/video/ibm/cga/ibm-cga.xml"/>
<fdc ref="/disks/pc/compiled/library.xml" automount='{A: {name: "PC-DOS 3.00 (Disk 1)", path: "/disks/pc/dos/ibm/3.00/PCDOS300-DISK1.json"}, B: {name: "PC-DOS 3.00 (Disk 2)", path: "/disks/pc/dos/ibm/3.00/PCDOS300-DISK2.json"}}'/>
<keyboard ref="/devices/pc/keyboard/us84-buttons-functions.xml"/>
<debugger id="debugger" messages="fault" commands=""/>
@ -28,6 +28,9 @@
Finally, there is a "manufacturing jumper" that can be installed, enabling additional diagnostic functions
in the ROM; it defaults to UNINSTALLED and stays UNINSTALLED, since no UI or configuration property is currently
provided.
The rest of a 5170 machine's configuration is handled through CMOS settings, which PCjs configures automatically
based on other settings (eg, the chipset's *floppies* property).
</comment>
<chipset id="chipset" model="5170" floppies="[1200,1200]" monitor="color"/>
<serial id="com1" adapter="1"/>

3
devices/pc/machine/5170/mda/640kb/rev3/debugger/machine.xml
View file

@ -28,6 +28,9 @@
Finally, there is a "manufacturing jumper" that can be installed, enabling additional diagnostic functions
in the ROM; it defaults to UNINSTALLED and stays UNINSTALLED, since no UI or configuration property is currently
provided.
The rest of a 5170 machine's configuration is handled through CMOS settings, which PCjs configures automatically
based on other settings (eg, the chipset's *floppies* property).
</comment>
<chipset id="chipset" model="5170" floppies="[1200,1200]" monitor="mono"/>
<serial id="com1" adapter="1"/>

41
devices/pc/rom/5170/README.md
View file

@ -8,9 +8,25 @@ redirect_from:
- /devices/pc/rom/5170/bios/
---
IBM PC AT (Model 5170) BIOS
IBM PC AT (Model 5170) ROM Revisions
---
[ATBIOS-REV1.json](1984-01-10/ATBIOS-REV1.json) contains the original IBM PC AT BIOS.
There were three ROM BIOS revisions for the IBM PC AT, which we refer to as **[Rev 1](#ibm-pc-at-rom-bios-rev-1)**,
**[Rev 2](#ibm-pc-at-rom-bios-rev-2)**, and **[Rev 3](#ibm-pc-at-rom-bios-rev-3)**. Each revision was used with a
corresponding motherboard type (**Type 1**, **Type 2**, and **Type 3**, respectively), which in turn were used with
corresponding 5170 models ([Models 68 and 99](/devices/pc/machine/5170/#models-68-and-99),
[Model 239](/devices/pc/machine/5170/#model-239), and
[Models 319 and 339](/devices/pc/machine/5170/#models-319-and-339), respectively).
IBM PC AT ROM BIOS (Rev 1)
---
[ATBIOS-REV1.json](1984-01-10/ATBIOS-REV1.json) contains the original IBM PC AT BIOS, dated January 10, 1984
("01/10/84"). It was produced for [5170 Models 68 and 99](/devices/pc/machine/5170/#models-68-and-99),
announced August 14, 1984.
Do we really think this PC AT BIOS was "finalized" a full 7 months before the PC AT was even announced, let alone
available? I doubt it. I suspect the BIOS date string was simply never updated to reflect the date of the final
change(s).
From [http://minuszerodegrees.net/bios/BIOS_5170_10JAN84_6MHZ.zip](http://minuszerodegrees.net/bios/):
@ -48,10 +64,13 @@ either the *merge* option or the appending of MAP data. For the moment, the API
---
IBM PC AT (Model 5170) BIOS ("Rev 2")
IBM PC AT ROM BIOS (Rev 2)
---
[ATBIOS-REV2.json](1985-06-10/ATBIOS-REV2.json) contains the second IBM PC AT BIOS, dated June 10, 1985, which expanded hard disk
support from 15 to 23 drive types, fixed some bugs, and added support for 720Kb 3.5-inch floppy diskette drives.
[ATBIOS-REV2.json](1985-06-10/ATBIOS-REV2.json) contains the second IBM PC AT BIOS, dated June 10, 1985.
This BIOS was produced for [5170 Model 239](/devices/pc/machine/5170/#model-239), announced October 10,
1985. It increased the number of supported hard disk types from 15 to 23, fixed some bugs, and added support for 720Kb
3.5-inch floppy diskette drives.
From [http://minuszerodegrees.net/bios/BIOS_5170_10JUN85_6MHZ.zip](http://minuszerodegrees.net/bios/):
@ -78,10 +97,16 @@ The JSON-encoded ROM image that PCjs uses was created using the *FileDump* comma
---
IBM PC AT (Model 5170) BIOS ("Rev 3")
IBM PC AT ROM BIOS (Rev 3)
---
[ATBIOS-REV3.json](1985-11-15/ATBIOS-REV3.json) contains the third (and last) IBM PC AT BIOS, dated November 15, 1985,
which added support for 101-key keyboards and 1.44Mb floppy diskette drives.
[ATBIOS-REV3.json](1985-11-15/ATBIOS-REV3.json) contains the third (and last) IBM PC AT BIOS, dated November 15, 1985.
This BIOS was produced for [5170 Models 319 and 339](/devices/pc/machine/5170/#models-319-and-339),
announced April 2, 1986. It added support for 101-key keyboards and 1.44Mb 3.5-inch floppy diskette drives.
Note that, although minuszerodegrees.net says this revision was found in "type 2 motherboards running at 8 Mhz",
the [Vintage Computer Federation](http://www.vcfed.org/forum/showthread.php?26480) refers to the 8Mhz motherboards as
"Type 3".
From [http://minuszerodegrees.net/bios/BIOS_5170_15NOV85_8MHZ_VARIATION_2.zip](http://minuszerodegrees.net/bios/):

8
disks/pc/README.md
View file

@ -41,9 +41,13 @@ diagnostics, and more.
* [Lotus 1-2-3](apps/lotus/123/)
* [MicroPro WordStar](apps/micropro/wordstar/)
* [Microsoft Chart](apps/microsoft/chart/)
* [Microsoft Games](games/microsoft/)
* [Microsoft Word](apps/microsoft/word/)
* [Microsoft Word for Windows](apps/microsoft/winword/)
### [Games](games/)
* [id Software](games/id/)
* [Infocom](games/infocom/)
* [Microsoft](games/microsoft/)
### [Tools](tools/)

1
disks/pc/apps/microsoft/README.md
View file

@ -11,4 +11,3 @@ Information is available for these Microsoft applications:
* [Microsoft Chart](chart/)
* [Microsoft Word](word/)
* [Microsoft Word for Windows](winword/)

13
disks/pc/apps/microsoft/word/README.md
View file

@ -1,14 +1,21 @@
---
layout: page
title: Microsoft Word (for DOS)
title: Microsoft Word
permalink: /disks/pc/apps/microsoft/word/
---
Microsoft Word (for DOS)
Microsoft Word
---
Information is available for these versions of [Microsoft Word](https://en.wikipedia.org/wiki/Microsoft_Word) (for DOS):
Information is available for these versions of [Microsoft Word](https://en.wikipedia.org/wiki/Microsoft_Word):
* [Microsoft Word 3.0](3.0/)
* [Microsoft Word 3.1](3.1/)
* [Microsoft Word 5.0](5.0/)
Microsoft Word for Windows
---
Information is available for these versions of [Microsoft Word for Windows](../winword/):
* [Microsoft Word for Windows 2.0c](../winword/2.0c/)

4
disks/pc/compiled/library.xml
View file

@ -483,8 +483,10 @@
<disk path="/disks/pc/tools/microsoft/windows/sdk/3.00/WIN30SDK_DISK08.json">Windows SDK 3.00 (720K Disk 8)</disk>
<disk path="/disks/pc/tools/microsoft/windows/sdk/3.00/WIN30SDK_DISK09.json">Windows SDK 3.00 (720K Disk 9)</disk>
<disk path="/disks/pc/tools/microsoft/windows/sdk/3.00/WIN30SDK_DISK10.json">Windows SDK 3.00 (720K Disk 10)</disk>
<disk path="/disks/pc/tools/misc/debugx/1.32/DEBUGX-132.json">Enhanced DEBUG 1.32</disk>
<disk path="/disks/pc/games/id/wolf3d/1WOLF14.json">Wolfenstein 3D 1.4</disk>
<disk path="/disks/pc/games/microsoft/flightsim/1982/FLIGHTSIM-1982.json">MS Flight Simulator (1982)</disk>
<disk path="/disks/pc/games/microsoft/flightsim/1984/FLIGHTSIM-1984.json">MS Flight Simulator (1984)</disk>
<disk path="/disks/pc/games/id/wolf3d/1WOLF14.json">Wolfenstein 3D (v1.4)</disk>
<disk path="/apps/pc/1981/visicalc/disk.json">VisiCalc</disk>
<disk path="/apps/pc/1982/esuite/disk.json">Executive Suite (1982)</disk>
<disk path="/apps/pc/1985/rogue/disk.json">Rogue (1985)</disk>

1
disks/pc/games/README.md
View file

@ -7,5 +7,6 @@ permalink: /disks/pc/games/
PC Games
---
* [id Software](id/)
* [Infocom](infocom/)
* [Microsoft](microsoft/)

10
disks/pc/games/id/README.md Normal file
View file

@ -0,0 +1,10 @@
---
layout: page
title: id Software Games
permalink: /disks/pc/games/id/
---
id Software Games
---
* [Wolfenstein 3D](wolf3d/)

23
disks/pc/games/id/wolf3d/README.md Normal file
View file

@ -0,0 +1,23 @@
---
layout: page
title: "id Software: Wolfenstein 3D"
permalink: /disks/pc/games/id/wolf3d/
---
Wolfenstein 3D
---
### Directory of Wolfenstein 3D 1.4
Volume in drive A is 1WOLF14
Directory of A:\
FILE_ID DIZ 350 01-01-93 12:40p
INSTALL EXE 142181 01-01-93 12:40p
W3DSW14 SHR 790409 01-01-93 12:40p
3 file(s) 932940 bytes
Total files listed:
3 file(s) 932940 bytes
280576 bytes free

11
disks/pc/games/id/wolf3d/manifest.xml Normal file
View file

@ -0,0 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/versions/pcjs/1.21.6/manifest.xsl"?>
<manifest type="software">
<title>Wolfenstein 3D</title>
<disk id="disk01" size="1228800" chs="80:2:15" dir="archive/1WOLF14" href="/disks/pc/games/id/wolf3d/1WOLF14.json" md5="f834555a36cc2d99b100ca8bbb7309b0" md5json="2ba049953af759e891a285db38a143de">
<name>Wolfenstein 3D 1.4</name>
<file size="350" time="1993-01-01 12:40:00" attr="0x20" md5="01b4e263c6a41a9159aa4332e1cb8592">FILE_ID.DIZ</file>
<file size="142181" time="1993-01-01 12:40:00" attr="0x20" md5="341334d8dd43ffa9cb215bbc6504d8d3">INSTALL.EXE</file>
<file size="790409" time="1993-01-01 12:40:00" attr="0x20" md5="229402f7d893b91beb15c8794f2d6fdf">W3DSW14.SHR</file>
</disk>
</manifest>

2
disks/pc/games/infocom/README.md
View file

@ -9,6 +9,6 @@ Infocom Games
* [The Hitchhiker's Guide to the Galaxy](hhiker/)
* [Planetfall](planet/)
* [Zork I](zork1/)
* [Zork I](zork1/) ([Debugger](zork1/debugger/))
* [Zork II](zork2/)
* [Zork III](zork3/)

20
disks/pc/games/infocom/machine-debug.xml
View file

@ -1,20 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/versions/pcjs/1.21.6/machine.xsl"?>
<machine id="ibm5150-infocom" class="pc" border="1" width="980px" pos="center" background="#FAEBD7">
<name pos="center">IBM PC Model 5150 (CGA, 64K)</name>
<computer id="infocom-cga-64k" name="IBM PC" resume="1"/>
<cpu id="cpu8088" model="8088"/>
<ram id="ramLow" addr="0x00000" test="false"/>
<rom id="romBASIC" addr="0xf6000" size="0x8000" file="/devices/pc/rom/5150/basic/archive/BASIC100.rom"/>
<rom id="romBIOS" addr="0xfe000" size="0x2000" file="/devices/pc/rom/5150/archive/1981-04-24.rom"/>
<video ref="/devices/pc/video/ibm/cga/ibm-cga.xml"/>
<fdc ref="/disks/pc/games/infocom/disks.xml"/>
<keyboard id="keyboard" pos="left" padleft="8px" padbottom="8px">
<control type="button" binding="esc">ESC</control>
<control type="button" binding="ctrl-c">CTRL-C</control>
<control type="button" binding="ctrl-alt-del">CTRL-ALT-DEL</control>
</keyboard>
<debugger id="debugger"/>
<panel ref="/devices/pc/panel/wide.xml"/>
<chipset id="chipset" model="5150" sw1="01001001" sw2="11110000"/>
</machine>

1
disks/pc/games/infocom/zork1/debugger/machine.md
View file

@ -4,6 +4,7 @@ title: "IBM PC (Model 5150) running Zork I with Debugger"
permalink: /disks/pc/games/infocom/zork1/debugger/
machines:
- type: pc
debugger: true
id: ibm5150-zork1
---

4
disks/pc/games/microsoft/README.md
View file

@ -7,5 +7,5 @@ permalink: /disks/pc/games/microsoft/
Microsoft Games
---
* [Microsoft Adventure](adventure/)
* Microsoft Flight Simulator (1984)
* [Microsoft Adventure (1981)](adventure/)
* [Microsoft Flight Simulator (1984)](flightsim/)

2
disks/pc/games/microsoft/adventure/machine.md
View file

@ -1,6 +1,6 @@
---
layout: page
title: "IBM PC (Model 5150) running Microsoft Adventure"
title: "IBM PC (Model 5150) running Microsoft Adventure (1981)"
permalink: /disks/pc/games/microsoft/adventure/
machines:
- type: pc

1
disks/pc/games/microsoft/flightsim/1982/FLIGHTSIM-1982.json Normal file
View file

File diff suppressed because one or more lines are too long

13
disks/pc/games/microsoft/flightsim/1982/manifest.xml Normal file
View file

@ -0,0 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/versions/pcjs/1.21.6/manifest.xsl"?>
<manifest type="software">
<title>Microsoft Flight Simulator</title>
<version/>
<type>Game</type>
<category>Simulation</category>
<author>Microsoft</author>
<releaseDate>1982</releaseDate>
<disk id="disk01" size="163840" chs="40:1:8" img="1982/archive/FLIGHTSIM-1982.img" href="/disks/pc/games/microsoft/flightsim/1982/FLIGHTSIM-1982.json" md5="3f4df6bfc9a6490b81d60daeca5865fe" md5json="273d49724e6ba857de680f5c6bed49e9">
<name>MS Flight Simulator (1982)</name>
</disk>
</manifest>

2
disks/pc/games/microsoft/flightsim/1984/FLIGHTSIM-1984.json
View file

File diff suppressed because one or more lines are too long

2
disks/pc/games/microsoft/flightsim/manifest.xml → disks/pc/games/microsoft/flightsim/1984/manifest.xml
View file

@ -7,7 +7,7 @@
<category>Simulation</category>
<author>Microsoft</author>
<releaseDate>1984</releaseDate>
<disk id="disk01" dir="archive/" href="/disks/pc/games/microsoft/flightsim/1984/FLIGHTSIM-1984.json" md5="334d3894f0a3ee4d7e9983867f36dc7e" md5json="a9d4eb333180eb5709c2049114c7ad29">
<disk id="disk01" size="368640" chs="40:2:9" dir="archive" href="/disks/pc/games/microsoft/flightsim/1984/FLIGHTSIM-1984.json" md5="dc9d35deddfd1389d6cee16993469a16" md5json="14391960fab50856ec09286f26d84ad2">
<name>MS Flight Simulator (1984)</name>
<file size="6917" time="1987-06-22 17:33:00" attr="0x20" md5="3a7c32594f174ae943c17cc3b23a6c34">FS.EXE</file>
<file size="3840" time="1987-06-22 17:33:02" attr="0x20" md5="d94eea83259d1658bb73da1ca3f59c16">FS.HLP</file>

56
disks/pc/games/microsoft/flightsim/README.md Normal file
View file

@ -0,0 +1,56 @@
---
layout: page
title: Microsoft Flight Simulator
permalink: /disks/pc/games/microsoft/flightsim/
---
Microsoft Flight Simulator
---
### Directory of MS Flight Simulator (1984)
Volume in drive A is PRIVATE
Directory of A:\
FS EXE 6917 06-22-87 5:33p
FS HLP 3840 06-22-87 5:33p
FS001 DAT 39936 06-22-87 5:31p
FS002 DAT 8192 06-22-87 5:31p
FS003 DAT 8192 06-22-87 5:31p
FS004 DAT 6144 06-22-87 5:31p
FS005 DAT 1024 06-22-87 5:31p
FS006 DAT 1024 06-22-87 5:31p
FS007 DAT 7168 06-22-87 5:32p
FS008 DAT 2048 06-22-87 5:32p
FS009 DAT 2048 06-22-87 5:32p
FS010 DAT 2048 06-22-87 5:32p
FS011 DAT 7168 06-22-87 5:32p
FS012 DAT 6144 06-22-87 5:32p
FS013 DAT 2048 06-22-87 5:32p
FS014 DAT 1024 06-22-87 5:32p
FS015 DAT 1024 06-22-87 5:32p
FS016 DAT 6144 06-22-87 5:32p
FS017 DAT 6144 06-22-87 5:32p
FS018 DAT 1024 06-22-87 5:32p
FS019 DAT 2048 06-22-87 5:32p
FS020 DAT 4096 06-22-87 5:32p
FS021 DAT 6144 06-22-87 5:32p
FS022 DAT 1024 06-22-87 5:32p
FS023 DAT 1024 06-22-87 5:32p
FS024 DAT 6144 06-22-87 5:32p
FS025 DAT 6144 06-22-87 5:32p
FS026 DAT 2048 06-22-87 5:32p
FS027 DAT 1024 06-22-87 5:32p
FS028 DAT 2048 06-22-87 5:32p
FS029 DAT 2048 06-22-87 5:32p
FS030 DAT 7168 06-22-87 5:32p
FS031 DAT 2048 01-01-80 12:08a
FS032 DAT 1024 06-22-87 5:32p
FS033 DAT 3072 06-22-87 5:32p
FS034 DAT 6144 06-22-87 5:32p
36 file(s) 172549 bytes
Total files listed:
36 file(s) 172549 bytes
189440 bytes free

6
disks/pc/library.xml
View file

@ -91,8 +91,10 @@
<manifest ref="/disks/pc/tools/microsoft/windows/sdk/1.04/manifest.xml"/>
<manifest ref="/disks/pc/tools/microsoft/windows/sdk/2.03/manifest.xml"/>
<manifest ref="/disks/pc/tools/microsoft/windows/sdk/3.00/manifest.xml"/>
<manifest ref="/disks/pc/games/microsoft/flightsim/manifest.xml"/>
<disk path="/disks/pc/games/id/wolf3d/1WOLF14.json">Wolfenstein 3D (v1.4)</disk>
<manifest ref="/disks/pc/tools/misc/debugx/manifest.xml"/>
<manifest ref="/disks/pc/games/id/wolf3d/manifest.xml"/>
<manifest ref="/disks/pc/games/microsoft/flightsim/1982/manifest.xml"/>
<manifest ref="/disks/pc/games/microsoft/flightsim/1984/manifest.xml"/>
<manifest ref="/apps/pc/1981/visicalc/manifest.xml" disk="disk01"/>
<manifest ref="/apps/pc/1982/esuite/manifest.xml" disk="disk01"/>
<manifest ref="/apps/pc/1985/rogue/manifest.xml" disk="disk01"/>

41
disks/pc/tools/misc/debugx/README.md Normal file
View file

@ -0,0 +1,41 @@
---
layout: page
title: Enhanced DEBUG 1.32
permalink: /disks/pc/tools/misc/debugx/1.32/
---
Enhanced DEBUG for PC DOS and MS-DOS
---
The [PC DOS Retro](https://sites.google.com/site/pcdosretro/) website has documentation for
[Enhanced DEBUG](https://sites.google.com/site/pcdosretro/enhdebug).
### Directory of Enhanced DEBUG 1.32
Volume in drive A is DEBUGX
Directory of A:\
DEBUG ASM 230861 04-08-16 12:48p
DEBUG COM 20828 04-08-16 12:48p
DEBUG TXT 28082 04-10-16 4:25p
DEBUGTBL INC 51176 03-11-16 7:27p
DEBUGX COM 26250 04-08-16 12:48p
DPMICL32 ASM 3022 04-06-16 5:48p
DPMICL32 EXE 847 04-06-16 5:48p
FPTOSTR INC 7908 11-28-14 2:28p
HISTORY TXT 18369 04-08-16 12:30p
INSTR KEY 5740 03-10-14 11:09a
INSTR ORD 576 01-25-14 10:59a
INSTR SET 9309 03-11-16 7:21p
LICENSE 35141 04-03-16 1:52p
MAKE BAT 1320 02-04-14 7:26p
MAKEC BAT 335 01-20-14 2:34p
MKTABLES C 31542 02-26-14 1:50p
README TXT 7268 04-10-16 4:24p
README MD 48 04-03-16 1:52p
18 file(s) 478622 bytes
Total files listed:
18 file(s) 478622 bytes
242688 bytes free

27
disks/pc/tools/misc/debugx/manifest.xml Normal file
View file

@ -0,0 +1,27 @@
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/versions/pcjs/1.21.6/manifest.xsl"?>
<manifest type="software">
<title>Enhanced DEBUG</title>
<source href="https://sites.google.com/site/pcdosretro/enhdebug">PC DOS Retro: Enhanced DEBUG for PC DOS and MS-DOS</source>
<disk id="disk01" size="737280" chs="80:2:9" dir="archive" href="/disks/pc/tools/misc/debugx/1.32/DEBUGX-132.json" md5="0142cf358fc2fb52f1f03db165ffd843" md5json="bb9e4ddfa0572dfbd7f6cb060e70a19b">
<name>Enhanced DEBUG 1.32</name>
<file size="230861" time="2016-04-08 12:48:00" attr="0x20" md5="a265513aff6af2efb1562f04e39bff9c">DEBUG.ASM</file>
<file size="20828" time="2016-04-08 12:48:02" attr="0x20" md5="45bbc08a0e38a4ac30d7e2d676344250">DEBUG.COM</file>
<file size="28082" time="2016-04-10 16:25:38" attr="0x20" md5="a9878a290c698f64aecd4a98ea727d56">DEBUG.TXT</file>
<file size="51176" time="2016-03-11 19:27:38" attr="0x20" md5="92522064c892fbce579f435c53858210">DEBUGTBL.INC</file>
<file size="26250" time="2016-04-08 12:48:02" attr="0x20" md5="84f9e88cb0bc5d4b1c97666aadaaba46">DEBUGX.COM</file>
<file size="3022" time="2016-04-06 17:48:54" attr="0x20" md5="7b3af2e516b53e2c51a4d0ea3aebfb05">DPMICL32.ASM</file>
<file size="847" time="2016-04-06 17:48:56" attr="0x20" md5="c29dcd96a8cb1ea69e1c2660d6f3b8af">DPMICL32.EXE</file>
<file size="7908" time="2014-11-28 14:28:56" attr="0x20" md5="e082a5153ffa32bd99502bd72fa3d892">FPTOSTR.INC</file>
<file size="18369" time="2016-04-08 12:30:00" attr="0x20" md5="13e2972df976ef8e58b4b321251b11f4">HISTORY.TXT</file>
<file size="5740" time="2014-03-10 11:09:28" attr="0x20" md5="f72698d37aeb8d9d02e3f85f83b9eaa8">INSTR.KEY</file>
<file size="576" time="2014-01-25 10:59:50" attr="0x20" md5="f5d0dba9006b655d481f49f875a0bcf3">INSTR.ORD</file>
<file size="9309" time="2016-03-11 19:21:56" attr="0x20" md5="52286ecd1118ce06a9b745b09b8632a3">INSTR.SET</file>
<file size="35141" time="2016-04-03 13:52:33" attr="0x20" md5="84dcc94da3adb52b53ae4fa38fe49e5d">LICENSE</file>
<file size="1320" time="2014-02-04 19:26:56" attr="0x20" md5="4fbdcf8dac8140c70df90b440fa6fb1b">MAKE.BAT</file>
<file size="335" time="2014-01-20 14:34:58" attr="0x20" md5="cec3c20285c5adae18a601d6a339ec2a">MAKEC.BAT</file>
<file size="31542" time="2014-02-26 13:50:00" attr="0x20" md5="adbf4961a3e4ab7c8c4646e003cbb08b">MKTABLES.C</file>
<file size="7268" time="2016-04-10 16:24:42" attr="0x20" md5="762396d950b08bd9deb6f7313f575b83">README.TXT</file>
<file size="48" time="2016-04-03 13:52:33" attr="0x20" md5="3d312a3c98b11e32ec8293b2095fae02">README.MD</file>
</disk>
</manifest>

2
docs/pcjs/chipset/README.md
View file

@ -67,7 +67,7 @@ Attributes
* *floppies* (optional)
If no *sw1* setting is provided, *floppies* may be used to specify an array of floppy drive capacities;
eg, [360, 360] for two 360Kb drives; default is none.
eg, [360, 360] for two 360Kb drives; default is none. Valid values include: 360, 720, 1200, and 1440.
* *monitor* (optional)

22
modules/diskdump/lib/diskdump.js
View file

@ -345,6 +345,7 @@ function DiskDump(sDiskPath, asExclude, sFormat, fComments, sSize, sServerRoot,
this.fJSONComments = fComments;
this.sJSONWhitespace = (this.fJSONComments? " " : "");
this.fXDFSupport = (argv && argv['xdf']);
this.sLabel = (argv && argv['label']);
/*
* The dump operation itself doesn't care about sManifestFile, but we DO need some indication
@ -678,7 +679,7 @@ DiskDump.CLI = function()
/**
* API
*
* Client-side version of the server-side function HTTPAPI.processDumpAPI(req, res).
* Client-side version of the web-based server-side function HTTPAPI.processDumpAPI(req, res).
*
* @param {Object} aParms (analogous to req.query on the server)
*/
@ -715,9 +716,10 @@ DiskDump.API = function(aParms)
web.alertUser(err.message);
}
});
} else {
}
else if (aParms[DumpAPI.QUERY.DIR] || aParms[DumpAPI.QUERY.PATH] || aParms[DumpAPI.QUERY.FILE]) {
/*
* The client-side API currently supports DumpAPI.QUERY.DISK requests only (eg, not DumpAPI.QUERY.FILE).
* The web-based client-side API currently supports DISK requests only (eg, no DIR, PATH, or FILE requests).
*/
web.alertUser("Unsupported API request.");
}
@ -766,7 +768,7 @@ DiskDump.outputDisk = function(err, disk, sDiskPath, sOutputFile, fOverwrite, sM
md5JSON = crypto.createHash('md5').update(data).digest('hex');
}
if (disk.bufDisk) {
md5Disk = crypto.createHash('md5').update(disk.bufDisk).digest('hex');
md5Disk = crypto.createHash('md5').update(disk.bufDisk.buf || disk.bufDisk).digest('hex');
}
fUnchanged = DiskDump.updateManifest(disk, disk.sManifestFile, sDiskPath, sOutputFile, true, sManifestTitle, md5Disk, md5JSON);
}
@ -922,7 +924,11 @@ DiskDump.updateManifest = function(disk, sManifestFile, sDiskPath, sOutputFile,
sCHS = disk.dataDisk.length + ':' + disk.dataDisk[0].length + ':' + disk.dataDisk[0][0].length;
size = disk.dataDisk.length * disk.dataDisk[0].length * disk.dataDisk[0][0].length * disk.dataDisk[0][0][0].length;
}
var sXMLDisk = '\t<disk id="' + sIDDisk + '"' + (size? ' size="' + size + '"' : '') + (sCHS? ' chs="' + sCHS + '"' : '') + (sParm? ' ' + sParm + '="' + sDiskPath + '"' : '') + ' href="' + sOutputFile + '"' + (md5Disk? ' md5="' + md5Disk + '"' : '') + (md5JSON? ' md5json="' + md5JSON + '"' : '') + '>\n';
var sXMLDisk = '\t<disk id="' + sIDDisk + '"';
sXMLDisk += (size? ' size="' + size + '"' : '');
sXMLDisk += (sCHS? ' chs="' + sCHS + '"' : '');
sXMLDisk += (sParm? ' ' + sParm + '="' + sDiskPath + '"' : '');
sXMLDisk += ' href="' + sOutputFile + '"' + (md5Disk? ' md5="' + md5Disk + '"' : '') + (md5JSON? ' md5json="' + md5JSON + '"' : '') + '>\n';
var sName = "";
if (sMatchDisk && (match = sMatchDisk.match(/<name>([^>]*)<\/name>/))) {
@ -1527,9 +1533,11 @@ DiskDump.prototype.readDir = function(sDir, fRoot, done)
* Use the directory name as a candidate for a volume label as well, if it's upper-case and
* 11 characters or less (after we remove any numeric prefix that we may have added to indicate
* disk order, that is).
*
* From the command-line, you can override this by passing --label=<somelabel>.
*/
if (fRoot) {
fileInfo = this.buildVolLabel(sDir);
fileInfo = this.buildVolLabel(this.sLabel || sDir);
if (fileInfo) {
aFiles.push(fileInfo);
// this.addManifestInfo(fileInfo);
@ -2083,7 +2091,7 @@ DiskDump.prototype.buildClusters = function(aFiles, offDisk, cbCluster, iParentC
} else {
cbData = sData.length;
bufData = new BufferPF(sData);
if (this.sManifestFile) aFiles[iFile].FILE_MD5 = crypto.createHash('md5').update(bufData).digest('hex');
if (this.sManifestFile) aFiles[iFile].FILE_MD5 = crypto.createHash('md5').update(bufData.buf || bufData).digest('hex');
}
}
else if (cbData < 0) {

2
pubs/pc/magazines/msj/README.md
View file

@ -10,7 +10,7 @@ Microsoft Systems Journal
Microsoft provides a [1986-1994 Index](https://www.microsoft.com/msj/backissues86.aspx) of Microsoft Systems Journal issues.
Unfortunately, the only online issues they currently provide are from January 1993 (Vol. 8, No. 1) through December 1994 (Vol. 9, No. 12).
PCjs has two early Microsoft Systems Journal issues for your out-dated programming enjoyment: October 1986 (Vol. 1, No. 1)
We have two early Microsoft Systems Journal issues for your out-dated programming enjoyment: October 1986 (Vol. 1, No. 1)
and the OS/2 Issue from May 1987 (Vol. 2, No. 2).
[<img src="http://archive.pcjs.org/pubs/pc/magazines/msj/MSJ-1986-10/thumbs/MSJ-1986-10 1.jpeg" width="200" height="260" alt="Microsoft Systems Journal, Oct 1986"/>](MSJ-1986-10/)