CDC 1700 emulator added to SIMH

For those of us, who have never heard of the CD 1700, there is a brief page on wikipedia:

https://en.wikipedia.org/wiki/CDC_1700

And from the announcement on the SIMH mailing list:

For the past couple of years or so, I have been working on a SIMH-based
simulator for the CDC1700 series, a 16-bit system from the mid-1960’s, using
the documentation and software available at bitsavers. It has now sufficiently
stable to allow others to make use ot the software. The base system implements:

  • a 1714 CPU with:
    • 1705 multi-level interrupts and direct storage access bus
    • up to 32KW of memory
    • memory protect system
    • Optional 64KW support
  • 1711-A teletypewriter
  • 1721-A paper tape reader
  • 1723-A paper tape punch
  • 1740 or 1742-30 line printer
  • 1738-B disk pack controller with up to 2 disk packs:
    (853 disk pack – 1.5MW)
    (854 disk pack – 3.0MW)
  • 1733-2 cartridge disk controller with up to 4 drives:
    Each drive has 1 fixed disk and 1 removeable disk:
    (856-2 CDD – 1.13MW per disk)
    (856-4 CDD – 2.25MW per disk)
  • 1732-A or 1732-3 magtape controller with 4 transports

The simulator is able to boot the diagnostic tape (SYSTEM17_SMM_DIAGS.TAP at
bitsavers.org) and successfully execute tests for each of the above
components. Some test sections fail due to various reasons; lack of
documentation, timing issues, feature not implemented etc.

The simulator is also able to boot and install MSOS 5 from an installation
tape (MSOS5_SL136.tap at bitsavers.org) onto a 1733-2 cartridge drive. This
is a copy of a distribution tape provided by CDC to run on a 64KW system at
Exxon.

I would like to thank Doug Gwyn for answering questions about the system
architecture and providing details about specific diagnostics tests and
Al Kossow for for peripheral documentation so that I could get MSOS 5
installed.

Spent some more time messing with NetHack 1.3d revived

1.3d revived and reloaded

1.3d revived and reloaded

And now it runs on Windows 10 (probably lots of Windows NT as well) thanks to EMX+RSXNT.

I put a Windows binary build on sourceforge, with the needed termcap and rsxnt.dll to run.  It works best if installed into the root of a drive, but it doesn’t matter which drive letter (I suppose you could even use subst).  I was patching around the stock NetHack 1.3d, but considering the weird issues I was having with it ‘mostly’ working, it was easier to just lean on the NetHack 1.3d revived project.  I should also say this is what I also used to get NetHack 1.3d running on the x68000.

I’ve been able to save, restore and go up, down and even die without it crashing so it seems OK to me.

It’s kind of cool to build it with GCC 1.40 on Windows 10, and get a native executable.  Maybe pointless in the golden age of emulation / virtualization as you could just as easily build stock 1.3d on a 4.2 BSD VAX, or even 386BSD 0.1 system.

Maybe I’ll finish the work to see if I can get it running on OS/2 or MS-DOS via EMX, but for now the project stuff is on sourceforge.net

 

Nintendo Classic Mini

11/11/2016

11/11/2016

Just saw mention of this, the Nintendo Classic Mini

It includes a USB controller, HDMI, and you have to bring your own USB +5v power supply. It’ll come with 30 pack in games, but no mention of any additional games.

The only thing that stuck out to me is that Mike Tyson’s Punch-Out!!,  is reverted back to the original Japanese Mr Dream.  Kind of lame, but I guess that is licensing for you.

There is more information at the Nintendo page, with a shipping date of November 11th, 2016 for the UK.

Microsoft starting to reduce One Drive storage

5GB..?

5GB..?

I suppose I should have managed it better.  I don’t even know what is there, but I shelled out the $18 HKD to at least keep it for now.

I know Microsoft has long dreamed of being SaaS, instead of being a traditional software vendor.  Is there hope for buy it and own it software as we approach 2020’s?

Either way, if you have onedrive, migrate, fix it, or pay for it.

MS-DOS 5.0 DPMI

MSDOS 5.00A BOOT

MS-DOS 5.00A booting on Neko Project 21

While I’m waiting for my real PC-9821 to arrive, I’ve been playing with various software.  One fun thing was the old DJGPP, as the version 1.x had a customized version of go32 to support the PC-98 hardware.  This is cool, but I’d love to perhaps start down the road of porting something to the PC-98.  There is no VGA adapter, and the I/O is mapped differently so naturally this is why they are only loosely compatible.  So while I was looking for any kind of source code using DJGPP, I found the FCE: Family Computer Emulator (NES).  It includes source code, which is great but it builds against DJGPP 2.x What makes it more interesting is that it has DPMI hooks in place, unlike the old DJGPP 1.x’s DOS extender which is DPMI incompatible.  So how do you magically get a DPMI environment for MS-DOS?  Well one way is to run it under Windows 3.0 or higher.  And certainly with MS-DOS 3.30 that is an option.  However lurking in the disk images of MS-DOS 5.00A was a fun program DPMI.EXE .  Well now that is interesting!

MSDOS 5.00A native memory

MSDOS 5.00A native memory

Using a generic config.sys I have 600kb of low RAM available, and 7MB of extended RAM.

Now the real interesting part is DPMI.INI

[386Enh]
ebios=
display=dddn.386
keyboard=*vkd
network=*vnetbios, *dosnet
device=*vpicd
device=*vtd
device=*vdmad
device=*vsd
device=*vsound
device=d86mgrn.386
device=*pageswap
device=*dosmgr
device=*vmpoll
device=*wshell
device=*vfd
device=*vscsid
device=dpdn.386
device=*parity
device=*biosxlat
device=dmcpd.386
device=*vhd
device=*vcd
device=*combuff
device=*resume
device=*la20hma
device=dpfd.386
Paging=Yes

As you can see this is pretty much the 386 enhanced portion of Windows 3.0!  So you get all of the DPMI services offered by Windows as part of the OS.

MSDOS 5.00A DPMI activated

MSDOS 5.00A DPMI activated

As you can see, with DPMI running I have access to EMS, and XMS memory now available.  Additionally with paging you can even over commit memory.

My only question, is why was DPMI not an added in feature of the English versions of MS-DOS?  Granted there was a LOT of OEM bundling with new machines so you were forced to purchase a copy of Windows along with MS-DOS on all new computers, regardless of what you were going to do with them, and this would have been a bit more interesting.

This kind of environment was extensively documented in the “Unauthorized Windows 95“, by Andrew Schulman that showed how DOSX.EXE could chain load Win386 + command.com achieving the same thing.  The DPMI environment from MS-DOS 5.00A is dated 11/11/1992, I wonder if he knew about this going into the Windows 95 book.  It’s been too long since I’ve read it to remember, but I don’t recall any details about Japanese PC-98 releases of MS-DOS.  There was also a ‘MSDPMI’ environment created for the beta versions of Microsoft C 7.0, but I’ve been unable to find one to verify.  MSC 7.0 was released in 1992, so it fits in the same timeframe, but the shipping products used QEMM’s DPMI server instead.