I don't suppose anyone has this kicking around, or any pre-release vax
images of netbsd?
I did manage to get 1.2 installed on SIMH for what it's worth....
Jason
How much does an old pdp-11 type system cost these
days (ie. a pdp-11/40 with disks and terminal capable
of running something like 1st, 6th or 7th ed)?
How much power do they take up to power on?
Whats maintenance like on those things?
I've always been curious.
Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
I was wondering if anyone has ever been able to build and use BSD 1 on
Research Unix v7 (pdp-11)?
I've installed the Keith Bostic tape, and I've been fighting the floating
point and some other weird stuff....
I've configured my PDP-11 like this:
set cpu 11/70
set cpu 2M
set cpu idle
set rp0 rp06
att rp0 rp06-0.disk
att tm0 xx.tap
boot tm0
but I'm lost on the install guide, as it mentions for floating point...
Floating Point
UNIX only supports (and really expects to have) the
FP11-B/C floating point unit. For machines without this
hardware, there is a user subroutine available that will
catch illegal instruction traps and interpret floating point
operations. (See fptrap(3).) To install this subroutine in
the library, change to /usr/src/libfpsim and execute the
shell files
compall
mklib
The system as delivered does not have this code included in
any command, although the operating system adapts automati-
cally to the presence or absence of the FP11.
Next, a floating-point version of the C compiler in
/usr/src/cmd/c should be compiled using the commands:
cd /usr/src/cmd/c
make fc1
mv fc1 /lib/fc1
This allows programs with floating point constants to be
compiled. To compile floating point programs use the `-f'
flag to cc(1). This flag ensures that the floating point
interpreter is loaded with the program and that the floating
point version of `cc' is used.
The library doesn't actually build a libfpsim.a but rather it hooks into
libc? And the fc1 command won't build as there is no libfpsim....
Maybe I'm doing something obviously wrong?
Any hint would be appreciated.
Jason
Anyone have a scanned (or text) copy of the 4.3BSD License Agreement
from 1986 they can send me?
Much of the code shipped in 4.3BSD says ``The Berkeley software License
Agreement specifies the terms and conditions for redistribution.'' As
far as I can see, it is not included in the source, nor in the Univ. of
Wisconsin fork, and not in Tahoe release.
I do have the agreement between UC and AT&T and copies of some of their
letters during that period clarifying the licensing.
The Net1 release included the license agreement in the source files. But
does anyone have a separate license agreement for Net1 too? (The README
seems to imply there was a separate license agreement too.)
I am also looking for addendum for Tahoe and the addendum for Reno. And
was there any agreement to sign for those who chose to pay for statement
that Net2 was freely redistributal (I guess that wouldn't make sense)?
Warren:
I thought the BSTJ went into 1984, as I have some references to 1984 issues,
e,g, The Evolution of UNIX System Performance. Bell System Technical Journal,
63(8):1791b1814, October 1984.
=======
The journal's name changed at the end of 1983, from Bell System Technical
Journal to AT&T Bell Laboratories Technical Journal, to reflect
divestiture.
There was indeed a late-1984 all-UNIX-papers issue of the BLTJ, but
technically (and journally) it was the BLTJ then, not the BSTJ.
I don't know whether there are issues of copyright-ownership or
the like over the post-divestiture journal (does it belong to
Bell Labs, now owned by Alcatel, or to AT&T, now owned by
Southern Bell?) that interfere with releasing the latter-day
journal.
Norman Wilson
Toronto ON
(actually passing through Davis CA on a train, but
who cares?)
A friend sent this to me. Both of these mailing lists are likely
to find this of interest. I have a paper copy of the 1978 BSTJ,
either the '82 or '83 issues, whichever one was devoted to Unix. :-)
Arnold
> Date: Mon, 8 Nov 2010 17:42:14 -0700 (MST)
> From: "Nelson H. F. Beebe" <beebe(a)math.utah.edu>
> To: fslc(a)fslc.usu.edu
> Cc: beebe(a)math.utah.edu
> Subject: [fslc] historical papers on Unix now online
>
> The Bell System Technical Journal from 1922 to 1983 is now online at
>
> http://bstj.bell-labs.com/
>
> with free downloadable PDFs of all articles.
>
> I've downloaded all of the HTML files, and found that just three of
> them contain mention of Unix:
>
> BSTJ.1978.5706-2.html
> BSTJ.1982.6109.html
> BSTJ.1983.6206.html
>
> Some of those important early articles that document the development
> of Unix have also been reprinted in these books:
>
> @String{pub-PH = "Pren{\-}tice-Hall"}
> @String{pub-PH:adr = "Upper Saddle River, NJ 07458, USA"}
>
> @Book{ATT:AUS86-1,
> author = "AT{\&T}",
> key = "ATT",
> title = "{AT}{\&T UNIX} System Readings and Applications",
> volume = "I",
> publisher = pub-PH,
> address = pub-PH:adr,
> pages = "xiv + 397",
> year = "1986",
> ISBN = "0-13-938532-0",
> ISBN-13 = "978-0-13-938532-2",
> LCCN = "QA76.76.O63 U553 1986",
> bibdate = "Sat Oct 28 08:25:56 2000",
> }
>
> @Book{ATT:AUS86-2,
> author = "AT{\&T}",
> key = "ATT",
> title = "{AT}{\&T UNIX} System Readings and Applications",
> volume = "II",
> publisher = pub-PH,
> address = pub-PH:adr,
> pages = "xii + 324",
> year = "1986",
> ISBN = "0-13-939845-7",
> ISBN-13 = "978-0-13-939845-2",
> LCCN = "QA76.76.O63 U553 1986",
> bibdate = "Sat Oct 28 08:25:58 2000",
> }
>
> -------------------------------------------------------------------------------
> - Nelson H. F. Beebe Tel: +1 801 581 5254 -
> - University of Utah FAX: +1 801 581 4148 -
> - Department of Mathematics, 110 LCB Internet e-mail: beebe(a)math.utah.edu -
> - 155 S 1400 E RM 233 beebe(a)acm.org beebe(a)computer.org -
> - Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ -
> -------------------------------------------------------------------------------
>
I will be giving a lecture at NYCBSDCon on November 13 about my research
covering the history of Berkeley Unix and will highlight some of the
important events and key participants in BSD history.
http://www.nycbsdcon.org/2010/
I have done over 50 interviews with early participants, including during
the first Berkeley UNIX Software Tape, the Second Berkeley Software
Distribution, and vmunix period. (I still have many to do.)
On 10/20/10 04:00, Tim Newsham<newsham(a)lava.net> wrote:
> I'm playing with unix v6 right now. I don't see the "man"
> binary anywhere.. anyone know why?
>
> I have v6 installed from tape. The tape has images for three
> disks apparently, root, source and docs. The docs image has
> a man directory with the man pages in them. I don't see a
> man binary anywhere though, and I don't see the sources to
> man in the sources directory either.
>
> I checked the disk images available on the simh "kits" page.
> It has man pages in /mnt/man but no sources or binary.
> (by the way, this image is missing /usr/sys for some reason,
> which is why I am running an installation from tape).
>
> I also checked the
> PDP-11/Trees/V6 directory on TUHS and similarly dont see
> sources or binaries for man (though the man pages are present
> in /usr/man).
>
> There's even a /usr/man/man1/man.1, formatted online here:
> http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/I/man.html
>
> anyone know why the source and binary are missing from the
> distributions?
What "man" binary? You use cat... You have the man-pages, you have a
program (or several) to type files... Why would you need yet another
program to type files?
Johnny
I'm playing with unix v6 right now. I don't see the "man"
binary anywhere.. anyone know why?
I have v6 installed from tape. The tape has images for three
disks apparently, root, source and docs. The docs image has
a man directory with the man pages in them. I don't see a
man binary anywhere though, and I don't see the sources to
man in the sources directory either.
I checked the disk images available on the simh "kits" page.
It has man pages in /mnt/man but no sources or binary.
(by the way, this image is missing /usr/sys for some reason,
which is why I am running an installation from tape).
I also checked the
PDP-11/Trees/V6 directory on TUHS and similarly dont see
sources or binaries for man (though the man pages are present
in /usr/man).
There's even a /usr/man/man1/man.1, formatted online here:
http://wwwlehre.dhbw-stuttgart.de/~helbig/os/v6/doc/I/man.html
anyone know why the source and binary are missing from the
distributions?
Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
hi everyone,
Just to let you all know that a few years ago I adapted the 2.11BSD
source so that it could be built on a modern system and transferred
across to the PDP-11. The changes are:
1. The PDP-11 assembler was written in assembler so made a
line-by-line translation into C code.
2. The C compiler required access to PDP-11 math e.g. for constant
folding, so I inserted some code from Bob Supnik's emulator in those
places.
3. Basically everything that runs from a makefile (e.g. "sh", "make",
"yacc", etc) has been upgraded to a more modern coding style with non
portable code fixed up, independence on type sizes, prototypes added,
etc, and the build system now generates two versions where
appropriate, one for running locally (compiled with gcc or whatever
your local compiler is) and one for inclusion in the distribution
(compiled with the PDP-11 cross toolchain).
4. I also fixed a number of "just plain bugs" that obviously had
remained undiscovered under PDP-11 conditions.
I used conditional compilation and macros where appropriate so as not
to break the PDP-11's ability to run the toolchain locally. I used a
binary comparison between the locally compiled build and the cross
compiled build to weed out bugs, and it did seem to be pretty robust
as I left it. The only reason I didn't make this work available
generally (apart from laziness), was that there's quite a few
experimental changes in addition to points 1-4, for example:
5. A reworking of the (existing) system that extracts strings and puts
them in the code segment (necessary to get the PDP-11 to run large
executables such as nethack). I can't really remember why I did this,
probably just to clean things up, but I don't think it's all that
essential so perhaps could be removed for the sake of minimal change.
6. Some changes to how "make" works, and to the Makefiles, intended to
clean things up, which in retrospect weren't essential and should be
removed (except for those changes necessary for point 3 above, need to
untangle it somehow). I didn't get around to converting all Makefiles
so there's probably a bit of inconsistency there. I might have broken
some things like "make tags" and "make depend", not sure.
7. Fortran stuff had to be disabled as the Fortran compiler is written
in assembly language (IIRC) and would probably be difficult to convert
into C (but I don't think this is a big deal).
If anybody volunteers to sift through the changes and sort out the
good from the dross then I will happily send the whole thing.
cheers, Nick
You've bested me there -- by a little. I only had the Sixth Edition on an 11/45. Now I could probably emulate that system on this iPhone, and it would run faster than the actual hardware.
Oh well, time to stop wallowing in nostalgia. ;-)
Sent from my iPhone
On Sep 28, 2010, at 9:42 PM, Dave Horsfall <dave(a)horsfall.org> wrote:
> And besides, I've used V5 on a /40 :-)
>
> -- Dave, turning 58 next month
I do indeed.
At 10:02 AM 9/29/2010 -0400, Bill Pechter wrote:
>Anyone else here remember fansi-console's ansi emulator.
>
>Works great instead of ansi.sys and is a pretty good screen driver for dos.
>
>On Wed, Sep 29, 2010 at 5:24 AM, Johnny Billquist
><<mailto:bqt@softjar.se>bqt(a)softjar.se> wrote:
>Mark Tuson wrote:
>Hi everyone, this is my first message, after being on the mailing list for
>the best part of three years :)
>
>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.
>
>
>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
>
>
>
>Anyone else here remember fansi-console's ansi emulator.
>
>Works great instead of ansi.sys and is a pretty good screen driver for dos.
>
><http://www.highbeam.com/doc/1G1-11953307.html>http://www.highbeam.com/doc/1G1-11953307.html
>
>Bill
>
>--
> d|i|g|i|t|a|l had it THEN. Don't you wish you could still buy it now!
> <http://pechter-at-gmail.com>pechter-at-gmail.com
>_______________________________________________
>PUPS mailing list
>PUPS(a)minnie.tuhs.org
>https://minnie.tuhs.org/mailman/listinfo/pups
---
Jay R. Jaeger The Computer Collection
cube1(a)charter.net
> > There is close zero chance I'll ever use this stuff,
> > unless I retire
> > to teaching in which case I'll make people write
> > PDP-11 assembler.
>
> That seems a tad archaic. MIPS might be a better
> choice; it's 32-bit
> with 32 registers, and there are excellent simulators for
> it.
At my university there's a grad class that's ostensibly on reverse
engineering,but you can't really disassemble anything if you don't
learn assembler, so you learn it. The downside, I guess, is that
I've read a decent amount of x86 assembler, but written very little.
I don't think it's a bad way to learn, but of course, Larry was
talking about teaching a nice instruction set, and you
kind of lose that. But you get Windows DLL function calling
back as a booby prize.
John Finigan
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.
I see The Unix Tree has browsable "4.1c BSD". Where can I download this
(so I don't have to browse)?
Also where can I find downloads for 4.1BSD and 4.1aBSD and 4.1cBSD and
anything after 2BSD but before 2.79BSD?
Thanks
Jeremy C. Reed
Hello.
I have a working Data General Aviion AV5500.
I'm searching for DG/UX tape images, documents and software for it,
specially
development kits for C.
Anybody has a machine like this or some data?
Thanks
Andrea
I managed to get 2.11 installed on SIMH, and hacked the de driver to work
(pretty much the same thing I did for 4.2 BSD on the 11/780) and now I've
gotten it networking.
I'll admit I'm not all that swift on the pdp-11, but I get the impression
that the maximum exe size is 128kb with 64kb of instructions, and 64kb of
data? Isn't there something that can be done with overlays or some other
linker thing to act like an 8086/80286 with the large memory model (ie
multiple segments...?)
I've been trying to build ircII-4.4 and I can't figure out how to link
something that big... I've tried the -Z and -O flags to ld to no avail.
Clearly I'm doing either something wrong, or impossible or stupid.
FWIW, here is the size of the same program on the VAX
myname# ls -l irc-4.4
-rwxr-xr-x 1 root 413696 Jun 8 08:46 irc-4.4*
myname# size irc-4.4
text data bss dec hex
293888 67584 20784 382256 5d530
I have a feeling that 300kb of text, along with 67kb of data is just too
much...?
Any pointers would be appreciated!
Jason
Sorry to bother you all with my questions over this ancient machine
and my failing trials with it..
Trying to get a DGUX system (Intel based) to work, as is, on a 'regular' x86 PC.
Just a couple of things :
1. I did find out that that DG machine is looking for an Adaptec PCI
SCSI Controller, and so I got an AHA-2940UW PCI card, installed it in
an old PC, got a matching 9GB HDD and booted it up from my image I've
'DD'ed from the original DG machine.
Boot prompt came up and said it's trying to load
sd(apsc(pci(0),d,0,7),1,0)root:/dgux -3
it didn't, no error msg, just gave me back a "Boot command:" prompt.
Bootpath of the original machine is sd(apsc(pci(0),d,0,7),1,0)root:/dgux -3.
The disk drive parameters are correct, according to the docs, its -
dev(ctrl(pci[pci_num]),slot[,func_num[,ctrl_id]])[,dev_id[,LUN]]).
I've checked the PCI slot in which I installed the card, it's 3, and
so I've tried '3' instead of 'd' in the command above, just got the
boot prompt back again.
Also tried - sd(apsc(pci(),3),0)root:/dgux -3 which should also work
according to the docs (all other params are default).
Tried to play with it and tried tons of combinations, just for the
heck of it, still nothing. If I do type in some nonsense it does give
me an error msg : "Error: No device specifications found in the boot
command. Invalid boot command line".
According to the docs, once I get the correct syntax, the system should load up.
Anyone got any advice about that?
2. Anyone here a/was a DG/UX user/admin? you guys are very hard to find :)
Thanks,
D'
---------- Forwarded message ----------
From: Bruce Jones <probes(a)communication.ucsd.edu>
Date: Mon, Aug 23, 2010 at 2:41 PM
Subject: [Sysadmin-L] Historical materials
To: sysadmin-L(a)ucsd.edu
Anyone want the complete set for BSD/386 v 1.0?
Includes manual, CDR, and 3.3" diskettes.
Just the thing to add to your library of obsolete but historically
significant software.
Bruce Jones
Department of Communication
(858) 534-0417/4410 FAX (858) 534-7315
-=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=-
--
carl lowenstein marine physical lab u.c. san diego
clowenstein(a)ucsd.edu
The 'problem' is with the de driver...Basically SIMH flags something wrong
with all incoming packets, and the driver thinks they are all corrupt...
in the procedure derecv
if ((rp->r_flags &
(RFLG_ERRS|RFLG_FRAM|RFLG_OFLO|RFLG_CRC))||
(rp->r_flags&(RFLG_STP|RFLG_ENP)) !=
(RFLG_STP|RFLG_ENP) ||
(rp->r_lenerr & (RERR_BUFL|RERR_UBTO|RERR_NCHN)) ||
len < ETHERMIN || len > ETHERMTU) {
something here is being passed wrong.. I've just changed the statement to
if(1==2) to keep the logic flow...
Anyways the same issue cropped up with 4.2 BSD & the VAX 11/780
On my pdp-11 the ini I'm using is:
set cpu 11/94 4M
set cpu cis
set cpu idle
set xu ena
att xu slirp
;attach tm0 211bsd.tap
attach tm0 ircii-4.4.source.tap
set rp0 rp06
attach rp0 auto.dsk
set rq dis
set rk dis
set rl dis
set hk dis
set rx dis
set tq dis
set dz lines=8
att dz 1000
boot rp0
I'm also using a version of SIMH that I've replaced the libpcap with SLiRP
from Qemu.. It's basically a user mode ip stack to do NAT. The advantage is
that they always have the same ip address, and it doesn't
require escalated privileges to run.
On Wed, Aug 11, 2010 at 5:45 AM, Johnny Billquist <bqt(a)softjar.se> wrote:
> Jason Stevens <neozeed(a)gmail.com> wrote:
>
> I managed to get 2.11 installed on SIMH, and hacked the de driver to work
>> (pretty much the same thing I did for 4.2 BSD on the 11/780) and now I've
>> gotten it networking.
>>
>
> Huh? What did you hack with the qe driver? Was that in 2.11BSD? I didn't
> know there was any problems with it in the first place.
>
> Or is there some problem in simh that you fixed?
>
> I'll admit I'm not all that swift on the pdp-11, but I get the impression
>>
>> that the maximum exe size is 128kb with 64kb of instructions, and 64kb of
>> data? Isn't there something that can be done with overlays or some other
>> linker thing to act like an 8086/80286 with the large memory model (ie
>> multiple segments...?)
>>
>
> Yes and no. In principle, the maximum size of a program is 64K instruction
> and 64K data. That's as much as is directly addressable. With overloays you
> can extend that somewhat, but there are limitations and restrictions.
>
>
> I've been trying to build ircII-4.4 and I can't figure out how to link
>> something that big... I've tried the -Z and -O flags to ld to no avail.
>>
>> Clearly I'm doing either something wrong, or impossible or stupid.
>>
>> FWIW, here is the size of the same program on the VAX
>>
>> myname# ls -l irc-4.4
>> -rwxr-xr-x 1 root 413696 Jun 8 08:46 irc-4.4*
>> myname# size irc-4.4
>> text data bss dec hex
>> 293888 67584 20784 382256 5d530
>>
>> I have a feeling that 300kb of text, along with 67kb of data is just too
>> much...?
>>
>> Any pointers would be appreciated!
>>
>
> You'll need to trim some fat off.
>
> Points to remember:
> 64K data is the max. There is no way to use overlays to get more data
> space. Overlays can only extend the instruction space.
> Overlays and the main program share the same address space. That is, the
> size of the main code and the largest overlay segment together must not
> exceed 64K. So, overlays is just a way to move parts of the program in and
> out of your basic 64K address space.
> When you link a program, you'll be able to see the sizes of all segments as
> well as the main program.
>
> As an example, this is how tcsh looks like:
>
> Test:/# size /bin/tcsh
>
> text data bss dec hex
> 48960 14844 11986 75790 1280e total text: 140864
> overlays: 15424,16000,14144,14016,16256,16064
>
> Notice how text+max(sizeof overlays) is less than 64K.
>
> All that said, you can easily find IRC clients who are much smaller than
> that... :-)
>
> Johnny
>
> --
> Johnny Billquist || "I'm on a bus
> || on a psychedelic trip
> email: bqt(a)softjar.se || Reading murder books
> pdp is alive! || tryin' to stay hip" - B. Idol
>
Hi,friend
I find a good website which is www.dybers2.com It sells electronic
products. All of them are brand new and original and they all have
cheap price and high quality.The company also deal with the tariff for
us. One of my friends orders an Apple laptop. It only takes a week to
get it.
Let us enjoy the happiness of shopping. %--u
As you might remember from a previous post, I am trying to virtualize
/ emulate an old Data General UNIX system to a VM env'.
This is my progress so far (after a lot of reading, searching and
understanding who is who and what does it all mean) :
1. I've DD'ed an exact copy of the raw system disk as an image on my Linux box.
2. Loaded it up with most virtualization products out there - VMware,
VirtualBox, Xen/KVM/Qemu, Bochs and such.
They all work, ie, bootloader works and getting a DG/UX menu to
choose my proper kernel/system disk.
3. This is where they fail, as they cannot find the system's original
Adaptec PCI SCSI Controller (which is an AIC-7880 chip).
Most VM products only support LSI/BusLogic SCSI, and IDE of course.
As I see it, I have a few things I can do to make it work:
1. write an Adaptec driver for a VM product.
2. write an LSI/BusLogic driver for DG/UX or implement virtio drivers into it.
3. get IDE support working.
1st 2 options, as I understand from software eng' and other
professionals, are very difficult.
The 3rd option is interesting :
On one hand, I have an config file with all of DG/UX's supported
hardware, IDE is simply not there (would love for someone else to have
a look if possible. Just say so and I'll send you the file).
_and_ docs say "Data General has not tested or qualified the use of
IDE devices in AViiON AV 2100 systems".
_BUT_, on the other hand, BIOS seems to have plenty of IDE config
options and also docs say:
"IDE Interface - Disabled/Auto" , "OnBoard IDE Controller - enabled".
" The AV 2100 board set consists of a system board with six PCI
expansion slots, three ISA expansion slots, and several embedded
controller devices (PCI video, SCSI, Network, and IDE).
and "..A SCSI-III AIC-7880 controller for connecting up to seven 8-bit
narrow SCSI devices. You can also connect a mixture of fifteen 8-bit
narrow and 16-bit wide SCSI devices to the controller—maximum of seven
8-bit narrow SCSI devices. PCI-enhanced Integrated Drive Electronics
(IDE) hard disk interface that supports two hard disk drives"
Also " Since the lower bay contains a SCSI CD-ROM drive, only one
other SCSI device can be installed. You can install an IDE device in
the remaining bay. "
And much more. The question is, if I have an exact image of the
primary disk and I did try to load it via an IDE drive (in Qemu/
VirtualBox etc), didn't work out. Like last time, bootloader booted up
and then hang after trying to load the kernel.
Is there something I can try and do as a different config in my image file?
Anything else you can think of?
Please let me know if you need any file sent over.
Any help would be greatly appreciated.
Thanks,
Adam
Speaking of DG/UX, anybody know where to find this article?
M. H. Kelley. A look at the DG/UX file system.
Technical Report 3, Data General Corporation, 1990
I have a feeling DG was very early with journaling / crash resistant
filesystem tech but I've seen almost no detailed info, just a couple of
lines in a brochure.
John Finigan
asbesto(a)freaknet.org:
p.s. a copy of the operating system or a dump of the DISK/OS
will be appreciated, is very important to save this kind of
software, very hard to found today.
[...]
[ *I DELETE* EMAIL > 100K, ATTACHMENTS, HTML, M$-WORD DOC and SPAM ]
=======
I guess if I had a copy it would be unwise to e-mail it to you.
(I dislike using e-mail as a large-file-transfer service myself,
but I communicate with enough non-geeks that I consider the
battle lost.)
Norman Wilson
Toronto ON
Hi,
A big thanks to all who replied to my request for takers for the old
PDP-11 systems I have. I'm afraid I haven't been able to respond to
everyone yet as there's been a lot going on but I appreciate the
enlightenment on some of the aspects of the machines.
To be honest I really know very little about the PDP-11 and I had
hoped to learn more though these, so my MicroVAX II was a best guess
based on trying to match the hardware up to images on the web.
I will try and get back to all who expressed an interest with more
detailed information on the configuration and better pictures.
> Of course a PDP-11 is not a MicroVAX, and vice versa.
>
> Looking at the pictures, the only thing really worth saving would be
> the chassis shown with a keyboard next to it. One can see a floppy
> disk drive, and a hole where a hard disk drive probably was once. If
> there is a nameplate on the front, it is not readable in the picture.
> A picture of the rear panel would help in further identification, as
> well as a reading of any nameplate data on the rear panel.
--
Regards,
Kevin Phair
