Ok, I had some initial success with a quick and dirty hack.
- apply the attached patch to your simh tree and rebuild pdp11
and copy it into your tools directory.
- maps the TTIX device into the DC11 space
- forces the CSR to return the carry-detect bit as always on
- edit build/init.s and uncomment some or all of the ttys
build it and place it on your drive:
$ vi build/init.s
$ tools/as build/init.s
$ cp b.out build/root/etc/init
$ tools/mkfs -p fs/Readme build/root rf0.dsk rf
- copy your simh.cfg to simh2.cfg and add these lines before
the "go" line:
set ttix en
set ttix lines=8
att ttix 5555
- run "./simh2.cfg"
at this point you can telnet to port 5555 and enjoy a multi user
unix system. This lacks a lot of polish and needs a bit of work
yet, but its quick and dirty.
You'll have to revert to the old init if you want to use the normal
simh.cfg since the kernel will panic when opening the other ttys
if the DC11 hardware isnt attached.
Tim Newsham
http://www.thenewsh.com/~newsham/
> We need to recreate enough of the boot chain to make self-support possible.
> James Markevitch I think was working on this; James, can you give us a
> status report?
It's up and running. It requires the KE11 fix that Brad made (so that
switch registers work). I tested against that and can boot without
pre-loading core with anything other than the 32W bootstrap. It pulls
the bootstrap (bos) and operating system from the high portion of the
RF11 image.
I'll upload this this evening.
James Markevitch
Wednesday I got V1 running on my Mac. Great fun!
The level of sophistication impressed people here.
Do you folks think we can move the sources for
the kernel into it and have it be self supporting?
Hi
I have a few xt computers and would like to put some old unix OS on,
what unix would you guys recommend for it ? most of the unix that i have
tried to search for are for machines that are older than xt.
Regards,
Angus
I've just written a Readme to describe how to build the kernel and filesystems,
and to run 1st Edition UNIX. Can a few people who haven't actually used the
system please have a go and give me feedback on the Readme.
To fetch the repository:
svn checkout http://unix-jun72.googlecode.com/svn/trunk/ unix72
Then go into the new unix72/ and read the Readme.
Thanks,
Warren
I'm still working on the last1120 C compiler, so I've added the original code
to svn. Right now, the compiler executes fine under Apout (enough to recompile
itself), but not on V1 with the 0407 patch. I can compile simple C programs,
and execute the resulting 0407 binary on V1. I'm running this program to get a
memory dump of the process while it is running:
main()
{
char c[];
int i;
printf("Hello world\n");
c= main;
while (c != 0) {
i= *c & 0277;
printf("%o %o\n", c, i);
c++;
}
}
so I can compare the Apout memory environment with the V1 memory environment.
But it's very sloooow. I wonder why; V7 on simh is much faster than V1.
Cheers,
Warren
P.S The C compiler doesn't have for loops :-)
In the svn repository, patches/upcase.patch now fixes the kernel so
that CR is converted into LF. This means that you don't have to type ^J
in any more.
Warren
I removed some older tools from the svn. If you're still using them
and want to hold on to them, you might want to back up your copy
before updating, or pull old versions from svn (feel free to send
me questions if you are unsure how).
Assemv7 and assem went away as did dumpaout.py.
Tim Newsham
http://www.thenewsh.com/~newsham/
Would people mind if I imported apout src code into svn under tools/?
It's 35 files, 280K. I've fixed one small bug, and as we use it a lot it
might be good that you can get the latest version.
Warren
