The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: downing.nick@gmail.com (Nick Downing)
Subject: [pups] PDP-11 (SIMH), Seventh Edition UNIX
Date: Wed, 29 Sep 2010 10:22:54 +1000	[thread overview]
Message-ID: <AANLkTikmPvJxM14HCtZBYTOKPNn5oWwWnWCAy2P9RPyB@mail.gmail.com> (raw)
In-Reply-To: <4C9E234D.4020705@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4886 bytes --]

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 at gmail.com> wrote:
> Hi everyone, this is my first message, after being on the mailing list for
> the best part of three years :)
>
> I've a couple of [hopefully] simple questions about running Seventh Edition
> UNIX on SIMH.
>
> The first question is: how can I get the C compiler to work properly? When
> I've tried to compile programs, I get 'cannot create temp' - here's a full
> list of what's on the screen:
>
> @boot
> New Boot, known devices are hp ht rk rl rp tm vt
> : rl(0,0)rl2unix
> mem = 177856
> # Thu Sep 22 07:50:47 EDT 1988
>
> login: mark
> $ ed
> a
> main() {
>   printf("  Hello.\n");
>   return; }
>
> .
> w a.c
> 46
> q
> $ cc a.c
> cc: cannot create temp
> $
>
> Also, how can I get the backspace key to erase? I've done stty erase '^H'
> but I have to actually type <CTRL>+H to erase.
>
> The other thing I want to ask about is: can I compile SIMH on DOS, so it
> doesn't display any messages except those of the simulated software, and so
> it ignores ^E?
>
> I'm asking because I want v7 on an ancient laptop I've got lying around - a
> 486 with 24M of core. v7x86 won't work on it, and I don't really fancy
> putting Slack 3 back on it - if I'm going to go outdated, I might as well go
> the whole hog and go really outdated.
>
> Though I might consider 2.11BSD, if that'll work on a machine with 24M of
> core, and if the escapes will display properly, because
>
> [24;1H[?1h=[;H[2J
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~
>                  ~[H
>
> is a little bit difficult to work with when I'm wanting to edit source code.
>
> Thanks very much. Mark Tuson.
>
> _______________________________________________
> PUPS mailing list
> PUPS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/pups
>
>



  reply	other threads:[~2010-09-29  0:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25 16:29 Mark Tuson
2010-09-29  0:22 ` Nick Downing [this message]
2010-09-29  1:03 ` Frank Wortner
     [not found]   ` <Pine.BSI.4.64.1009291120060.4063@dave.horsfall.org>
2010-09-29 11:49     ` Frank Wortner
2010-09-29 11:56       ` Bob Eager
2010-09-30  0:54         ` Jay Jaeger
2010-09-29  9:24 ` Johnny Billquist
2010-09-29 14:02   ` Bill Pechter
     [not found] ` <AANLkTik5Ni7SARxa4x9-_2M6UxYaD18OR2t_Y2Z4JeSf@mail.gmail.c om>
2010-09-30  0:48   ` Jay Jaeger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikmPvJxM14HCtZBYTOKPNn5oWwWnWCAy2P9RPyB@mail.gmail.com \
    --to=downing.nick@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).