Minor 5170 config tweaks
This commit is contained in:
parent
9b8c00ce8b
commit
02a7eb22fc
4 changed files with 23 additions and 15 deletions
|
|
@ -1,33 +1,41 @@
|
|||
OS/2 1.0
|
||||
---
|
||||
Exciting news for OS/2 fans: PCjs (v1.16.1) is now able to run OS/2 1.0 on selected IBM PC AT (80286) machine
|
||||
configurations.
|
||||
Exciting news for OS/2 fans: PCjs (v1.16.1) is now able to run OS/2 1.0 on IBM PC AT (80286) machine configurations.
|
||||
|
||||
To test it out, go to [IBM PC Machine Configurations](/devices/pc/machine/), scroll down to the Model 5170 machines,
|
||||
and choose one. For drive A:, select "OS/2 1.0 Debug Boot Disk", click "Download", and then click the "Run"
|
||||
and choose one. For drive A:, select "OS/2 1.0 Debugger Boot Disk", click "Download", and then click the "Run"
|
||||
button.
|
||||
|
||||
In a few seconds, you'll see a very rudimentary OS/2 shell (a slimmed-down verion of the OS/2 "Program Selector")
|
||||
In a few seconds, you'll see a very rudimentary OS/2 shell (a slimmed-down version of the OS/2 Program Selector)
|
||||
that allows you to start the protected-mode command interpreter ("Start a Program") or the real-mode command
|
||||
interpreter ("command.com").
|
||||
|
||||

|
||||
|
||||
As an added bonus, these Model 5170 PCjs machines feature two serial ports, with COM1 connected to a simulated
|
||||
serial mouse and COM2 connected to the **Control Panel** output window.
|
||||
As an added bonus, the Model 5170 machines feature two serial ports, with COM1 connected to a simulated serial
|
||||
mouse and COM2 connected to the **Control Panel** output window.
|
||||
|
||||
So, once you've booted the "OS/2 1.0 Debug Boot Disk" from our assortment of [OS/2 Miscellaneous Disks](/disks/pc/os2/misc/),
|
||||
Once you've booted the "OS/2 1.0 Debugger Boot Disk" from the assortment of [OS/2 Miscellaneous Disks](/disks/pc/os2/misc/),
|
||||
you can click on the **Control Panel** output window, press Ctrl-C, and find yourself magically transported
|
||||
to the OS/2 Kernel Debugger. The **Control Panel** display is functioning as both the output window for all PCjs
|
||||
into the OS/2 Kernel Debugger. The **Control Panel** display is functioning as both the output window for all PCjs
|
||||
messages and PCjs Debugger commands, as well as a serial input/output device (aka "Dumb Terminal") for any software
|
||||
running inside the machine, such as the OS/2 Kernel Debugger.
|
||||
inside the machine communicating via COM2: in this case, the OS/2 Kernel Debugger.
|
||||
|
||||
> SIDEBAR: You can perform similar tricks with DOS in these machines. Boot any DOS disk (version 2.00 and up)
|
||||
and type "CTTY COM2" at the DOS prompt. All DOS input/output will now be routed to the **Control Panel** display.
|
||||
To restore control to the the machine's keyboard and video display, type "CTTY CON".
|
||||
|
||||
Type "?" for a list of all OS/2 Kernel Debugger commands. Type "g" to continue running OS/2. Make sure you type all
|
||||
OS/2 Kernel Debugger commands into the **Control Panel** output window. Commands typed into the input box *beneath*
|
||||
the output window are only processed by the PCjs Debugger, which retains ultimate control over the entire machine.
|
||||
the output window are processed only by the PCjs Debugger.
|
||||
|
||||
There are still a number of known issues with OS/2. For example, when attempting to install OS/2 1.0 from the
|
||||
installation diskettes onto a virtual hard disk, OS/2 successfully formats the hard disk and copies the files from
|
||||
When a fault occurs, OS/2 normally displays a "TRAP" message; however, when the Kernel Debugger is running, it
|
||||
intercepts the fault and displays the faulting instruction. But the PCjs Debugger has ultimate control: using
|
||||
the "m fault on" and "m halt on" commands, the PCjs Debugger will display and halt on any fault first. If you want
|
||||
PCjs to deliver the fault to OS/2, single-step over the faulting instruction and then continue.
|
||||
|
||||
There are still a number of known issues running OS/2. For example, when attempting to install OS/2 1.0 from the
|
||||
installation diskette images onto a hard disk image, OS/2 successfully formats the hard disk and copies the files from
|
||||
the first two diskettes, but usually while copying files from either the second or third diskette, the process stops.
|
||||
There's no crash -- it simply stops copying files and never finishes. My best guess at this point is that some
|
||||
interrupts are being dropped.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
<rom id="romBIOS" addr="0xf0000" size="0x10000" alias="0xff0000" file="/devices/pc/bios/5170/1984-01-10.json"/>
|
||||
<video ref="/devices/pc/video/video-ega-128kb-lock.xml"/>
|
||||
<keyboard ref="/devices/pc/keyboard/keyboard-minimal-functions.xml"/>
|
||||
<debugger id="debugger" messages="" commands=""/>
|
||||
<debugger id="debugger" messages="fault" commands=""/>
|
||||
<panel ref="/devices/pc/panel/wide.xml"/>
|
||||
<fdc ref="/disks/pc/library.xml" width="320px" 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"}}'/>
|
||||
<hdc id="hdcAT" type="at" drives='[{name:"20Mb Hard Disk",type:2}]'/>
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
<rom id="romBIOS" addr="0xf0000" size="0x10000" alias="0xff0000" file="/devices/pc/bios/5170/1985-11-15.json"/>
|
||||
<video ref="/devices/pc/video/video-ega-128kb-lock.xml"/>
|
||||
<keyboard ref="/devices/pc/keyboard/keyboard-minimal-functions.xml"/>
|
||||
<debugger id="debugger" messages="" commands=""/>
|
||||
<debugger id="debugger" messages="fault" commands=""/>
|
||||
<panel ref="/devices/pc/panel/wide.xml"/>
|
||||
<fdc ref="/disks/pc/library.xml" width="320px" automount='{A: {name: "PC-DOS 3.20 (Disk 1)", path: "/disks/pc/dos/ibm/3.20/PCDOS320-DISK1.json"}, B: {name: "PC-DOS 3.20 (Disk 2)", path: "/disks/pc/dos/ibm/3.20/PCDOS320-DISK2.json"}}'/>
|
||||
<hdc id="hdcAT" type="at" drives='[{name:"20Mb Hard Disk",type:2}]'/>
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
<rom id="romBIOS" addr="0xf0000" size="0x10000" alias="0xff0000" file="/devices/pc/bios/5170/1984-01-10.json"/>
|
||||
<video ref="/devices/pc/video/video-ega-128kb-lock.xml"/>
|
||||
<keyboard ref="/devices/pc/keyboard/keyboard-minimal-functions.xml"/>
|
||||
<debugger id="debugger" messages="" commands=""/>
|
||||
<debugger id="debugger" messages="fault" commands=""/>
|
||||
<panel ref="/devices/pc/panel/wide.xml"/>
|
||||
<fdc ref="/disks/pc/library.xml" width="320px" 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"}}'/>
|
||||
<chipset id="chipset" model="5170" floppies="[1200,1200]"/>
|
||||
|
|
|
|||
Loading…
Reference in a new issue