• Please review our updated Terms and Rules here

New Datapoint 2200 owner.

That is sort of how it works. The 1100 bootrom is loaded serially as if it is a cassette. I simply made it a cassette-image by prepending and appending a proper TAP header. So the first attach is just to get it to load the bootstrap into memory. The second attach is for the actual floppy.

Of course one can add some kind of 1100 mode which auto-attaches a virtual cassette and loads it at startup. But for now this is all manual.
 
Last edited:
Regarding the debugger: It do start but there are a feature in the RAM-based screen card I haven't figured how to implement in curses. There is a function to do a reverse scroll of one line. If anyone has an idea how to do that in ncurses pleae tell me!

This issue together with the font issue, the RA-based screen card has downloadable fonts, makes me think I should perhaps have an option to popup a graphics window that is the screen output of the machine. I was thinking X-windows window, but I have very little experience programming in X. The is that compatible with Macos? I simply don't know.

So, yes, the debugger do start if you have the DISPLAY button pressed (F6 toggles display button) but I am not sure how to use it and it does look very strange.
 
The MacOS curs_scroll man page has this to say:
For positive n, the scrl and wscrl routines scroll the window up n lines (line i+n becomes i); otherwise scroll
the window down n lines. This involves moving the lines in the window character image structure. The current
cursor position is not changed.
It isn't very clear but perhaps you specify a negative integer? It's been a long time since I programmed something using ncurses.
 
Did nor realize you already xferred the monitor code into a tap-file. I agree the debugger looks strange & spartanic, but it does work well in the real hardware. Might be a worthwhile hardware project, to recreate a cassette reader / boot prom combo card.

For my Emulith Lilith emulator I started out with X, which worked well enough. But then switched to the FLTK graphics package which allows easy porting to Windows, OS-X and Linux.
Bur probaly too much work, for now we should indeed see to recover as much existing software first.
 
The MacOS curs_scroll man page has this to say:

It isn't very clear but perhaps you specify a negative integer? It's been a long time since I programmed something using ncurses.

That looks promising. Need to re-investigate this. Thanks!

For my Emulith Lilith emulator I started out with X, which worked well enough. But then switched to the FLTK graphics package which allows easy porting to Windows, OS-X and Linux.
Bur probaly too much work, for now we should indeed see to recover as much existing software first.

Probably too much work for now. I don't think that much simple software programmed a font that was completely different from the standard font. Agree that we should try to recover as much old software as possible. I have pointers two one or two sets of "100 cassettes". Not sure this in fact is the same set but it would be great to get those imaged.

I made a quick implementation of the "LocalPrinter" and can now list the files of floppies to a virtual printer:

PAGE 1 DRIVE 0 011.IMD


APP /CMD (260)
AUTO /CMD (300)
AUTOKEY /CMD (320)
BACKUP /CMD (100)
BLOKEDIT/CMD (340)
BOOTMAKE/CMD (020) D
BUILD /CMD (360)
CAT /CMD (040) D
CHAIN /CMD (021)
CHAIN /OV1 (041)
CHANGE /CMD (061)
COPY /CMD (101)
COPYFILE/OVC (120)
DOS /EPT (121)
DOSGEN /CMD (140)
DR2 /OV1 (222)
DUMP /CMD (141)
DUMP9380/CMD (160)
EBCDIC /SEQ (161)
EDIT /CMD (201)
FILES /CMD (221)
FIX /CMD (241)
FREE /CMD (261)
INDEX /CMD (301)
KILL /CMD (321)
LIST /CMD (341)
MANUAL /CMD (361)
MASSACRE/CMD (022)
MIN /CMD (060) D
MOUT /CMD (042)
NAME /CMD (200)
OVERLAYS/SYS (220)
REFORMAT/CMD (062)
REPAIR /CMD (240)
REWIND /CMD (102)
SAPP /CMD (122)
SCRATCH /TXT (262)
SORT /CMD (142)
SORT /OV1 (162)
SUR /CMD (202)
SYSTEM0 /SYS (000) DW
SYSTEM1 /SYS (001) DW
SYSTEM2 /SYS (002) DW
SYSTEM3 /SYS (003) DW
SYSTEM4 /SYS (004) DW
SYSTEM5 /SYS (005) DW
SYSTEM6 /SYS (006) DW
SYSTEM7 /SYS (007) D

I will check list the contents for all the Datapoint .IMD files on bitsavers. Useful to have IMHO.
 
Getting ARC simulated could be interesting, but as Al wrote, we need the software that could use it. There is very little software around right now.

There is a description for the FRIL adapter that would work for 5500 I/O bus. But I doubt there ever were any software for the 2200 to use the FRIL interface, unfortunately. I would very much like to network my real old 2200...

Nice T-shirts by the way!
 
Last edited:
Easiest way to add some IO to a DP2200 would be to partially reconstruct the 9462 modem box : it is basically not much more than 8 UART's ( AY-5-1013) coupled to the normal IO connector. The small packages just above the IDC connectors are the interface to the IO bus.
9462_modem.jpg

9462_pcb..jpg
 
I have been contemplating the idea to create a board that simulates disks, printer, async and sync IO. All in the same. I have a Diablo HyType II aka servo printer that should be quite easy to connect. A simple STM32 or raspi pico could probably handle quite a lot of serial ports and possibly also act as sync serial controller. I think disk on an SD card should be quite easy as well.
 
Mattis, this is just perfect timing. I have been working with and for Datapoint since 1978 for about 10 years incl. writing lots of DATABUS code.

i am looking forward to any further version, this is fun to use and acts like a time machine.

keep up the good work!
 
Mattis, this is just perfect timing. I have been working with and for Datapoint since 1978 for about 10 years incl. writing lots of DATABUS code.

i am looking forward to any further version, this is fun to use and acts like a time machine.

keep up the good work!

Thanks!

I just added some convenience-functions; command history and better command line editing.

I also have recovered a set of tapes which contained DOS.D (thanks Jos for the wav-files) so now I am working on adding support for the 9350 and 9370 disk drives. That would allow me to at least get a bit further on the booting DOS.D. Possibly I need to add support for 5500 instructions and memory mapping as well. We'll see.

What kind of functions do you want to put on the wish-list for the simulator?

Do you have any software left on tapes or disks from your time working with Datapoint? It is very little software that has been saved for Datapoint so anything would be interesting. There is nothing for DOS.A or DOS.B for example. Cassettes with those operating systems would be interesting.

Any software that involves ARC network would be interesting. But also any documentation for the early ARC network adapters.
 
Hi Mattis,

ARCNet was mainly uaed to map remote drives s far as I remember. There were no applictions per se using ArcNet natively. there was a Videoconferencing device named MINX using networking. Networking was more prominent with the successor of DOS - RMS.

If I would wish, gettng a 5500/6600 emulation would be nice, also R/W mode for disks, that would allow to compile and run Databus software. There is lots more but hey,XMAS is over.

There is a FPGA based emulation kit called Mr. FPGA ,which may also be a nice home for a 22/55/6600… https://mister-devel.github.io/MkDocs_MiSTer/
 
BTW: I have no media from these days. Really most of it was custom written software in DATABUS. Later with RMS there was also COBOL compilers. Never touched RPG though.

the real power was DATASHARE, which allowed to run terminals with application software.
 
ARCNet was mainly uaed to map remote drives s far as I remember. There were no applictions per se using ArcNet natively. there was a Videoconferencing device named MINX using networking. Networking was more prominent with the successor of DOS - RMS.
OK. I see. So standard DOS supported sharing a disk that one node had with other nodes in the network? There wasn't any special config needed to make drives visible to other nodes or so?
If I know there is a possibility to have ARC net running with the software we currently have on bitsavers then I will look into creating a simulation for the interface module. Isn't there some kind of driver required for BAIL/PAIL/FRIL/RIM or whatever the name is for the ARC interface module: http://www.bitsavers.org/pdf/datapoint/arcnet/FRIL_Adapter_Feb77.pdf

According to this document one has to type "ARC" on the host that is supposed to be file server. I am not sure if I have seen the command ARC on the tapes / disks this far. Then this document describe the use of the DISPDOS command to do the same thing. Perhaps the latter document is an earlier version? Anyway, I cannot remember that I have seen DISPDOS either.

Perhaps if I can get DOS.D installed from the tapes on to a 9370 disk then it gets clearer?

If I would wish, gettng a 5500/6600 emulation would be nice, also R/W mode for disks, that would allow to compile and run Databus software. There is lots more but hey,XMAS is over.

I think 5500 support is next up. I want to be able to run DOS.D somehow.

The 9380 floppy should support R/W. But I haven't tested it. Disks are mounted write protected as default. But it can be turned of when attaching the image.

Code:
attach file=011.IMD writeprotect=false writeback=true type=floppy drive=0

At least that is how it is supposed to work. Please test and give and me steps on how to reproduce the problem and I will have a look. What program do you use for writing to disks? I am not very familiar with the different programs that are available under DOS.


There is a FPGA based emulation kit called Mr. FPGA ,which may also be a nice home for a 22/55/6600… https://mister-devel.github.io/MkDocs_MiSTer/

I have been considering a VHDL implementation but it is a much bigger task. At least for me. Perhaps one day I will do it.


BTW: I have no media from these days. Really most of it was custom written software in DATABUS. Later with RMS there was also COBOL compilers. Never touched RPG though.

the real power was DATASHARE, which allowed to run terminals with application software.

Ahh. That's a pity. I hope the guys at SAMSAT in Texas can recover their over 100 cassettes they have around. I have been in contact with them but they suddenly stopped responding, unfortunately. Then perhaps Jos have leads on a some more.
 
Ahh. That's a pity. I hope the guys at SAMSAT in Texas can recover their over 100 cassettes they have around. I have been in contact with them but they suddenly stopped responding, unfortunately. Then perhaps Jos have leads on a some more.
I think the SAMSAT people are tired/busy with people asking about Datapoint
Gordon Patterson is the guy to talk to about all things DOS. I sent you the last
email adr I have for him. He wrote big parts of it.
 
Let me give you some context how Datapoint came to play and how it was used (at least from my experience):
Datapoint was mainly aiming to be used as cheap data entry systems, take a 2200, attach a few terminals, run data entry software, write a tape and carry it off to your mainframe.

Personally, I started with DP in late 1978 (me being 18 and knowing nothing about IT), the IT team was mostly mainframe educated, meaning could not think beyond 80 character file records (aka punch card). DP had some advantages, like record size limited by disk space only, pretty good ISAM, later very good AIMDEX. Databus as a language was easy and able to be used for processing business applications. I was later working for DP itself, and most of my customers ran business applications, written in house. Later I worked for a software house doing land- and airfreight software, also written in DATABUS and being very successful.

Nearly every company had their own dev people, so most software was custom built. Yes, you shared code between companies on good will (security was not that much of a topic). In my role, we used DP for processing the ordering system, warehouse analysis, banking applications etc. We still used a /360 for some other stuff.

To take away all romance: These were not the good old times. Software was buggy ,hardware failed often. I spent countless weekends, New Years Eve's and christmas days working around issues, repairing disks, salvaging data etc.

ARCnet really became prominent in later years, I believe around 1981/82. I used it mainly in a dev environment. Why? When the DP2200 was in DATASHARE mode, driving terminals, the console was occupied, no editing, no compiling. One had to "ROLLOUT" of DATASHARE which meant all terminals were suspended. This is why networking was important, the main computer was running terminals and you had cheaper computers like a 1500/1800 (not sure about the models) or later the 8000 series to edit and compile. Until then, I had written my own text editor so it could run under DATASHARE, leaving the compilation for night time.

There was also a WAN Arcnet thing, but I cannot remember details.
 
BTW: What really would ease the use to write and compile code is to be able to mount the disk images in MacOS, so one can edit on a better screen... The 2200 screen is quite uncomfortable to use.
 
The DOS.C images do not include Databus nor Datashare which is a pity… Does anyone have a link or a source where these may exist?
 
Back
Top