A cursory examination shows that only unix compilers are supported (see makefile) and Win32 (see build_mingw*.bat). There is no reason in principle why you couldn't compile it with djgpp http://www.delorie.com/djgpp/ however. This would probably be the easiest thing because djgpp is a version of gcc and the code is known to compile under gcc on the unix platforms. As you won't be running in a Windows DOS box, you must provide a DOS extender (or more correctly a DPMI server), a free one is PMODE/W http://www.sid6581.net/pmodew/ which has worked for me in the past. Another option would be to compile with the free Watcom C/C++ compilers which I believe come bundled with DOS/4GW (Rational Systems, now Tenberry Software) as the DOS extender. More of a problem is the devices, you realize that the more basic your system the more trouble you are going to have getting information in? If you only want to run the editor and C compiler for experimentation then you will get bored very quickly, I remember as a student we had access to unix terminals via a serial link and since I didn't understand telnet or ftp and didn't have any internet access and no way to put a file on or off the system it was totally useless to me. With SIMH you can transfer stuff via simulated tapes (basically tar files) but since you want to disable ^E you won't be able to do that. I would suggest you use 2.11BSD because it has networking features so you can easily transfer your source code/etc on and off the system. However that leads to a nasty problem, which is that you will have to obtain a DOS packet driver for your laptop http://www.brutman.com/Dos_Networking/packet_drivers.html and implement a simulated network device for SIMH, I did something like this a while ago and it isn't trivial. (Another option would be to get a FOSSIL driver http://pcmicro.com/bnu/ and implement a simulated serial device for SIMH, you could then make a SLIP connection to a Linux or Windows machine). All things considered I believe your best option is to restore Slackware 3 (or some other linux) and then run SIMH under that, with the TUN/TAP device or whatever to allow an ethernet connection. Somewhere I have a set of floppy disk images, I think it was Slackware 4, which you could write out to floppy and install on the box. cheers, Nick On Sun, Sep 26, 2010 at 2:29 AM, Mark Tuson <markfptuson(a)gmail.com> wrote:

Mark Tuson wrote: Oh joy! :-) As others have mentioned, it could be problems with /tmp protection, as well as checking if there actually is any free space there. You need to know what code the key you call "backspace" actually sends. I suspect it is not sending a backspace, but a DEL (DEL is actually the traditional character used to delete, BS is a modern perversion). For the messages, I'm not sure what you are thinking of. Is it the ones before boot time, or is there some other messages that you see? As for the ^E, that is configured in simh when running. :-) 2.11BSD won't make a difference. You'll see the same result. This is a problem because you are running under DOS. It is the DOS screen handler that needs to understand whatever codes are output by the programs running inside simh. In this case, the program inside simh thinks it is connected to a VT100 (or xterm, or something similar), and sends escape codes based on that. I don't know why it thinks so, but I suspect you told the system by setting the TERM variable. Please set it to something that matches reality, or else fix reality. :-) Johnny