The actual idea was to create or assist with the creation of a completely
"free" (GNU?) implementation of VMS that "looks and feels" just like the
original.
The next step was to port this version of FreeVMS to i386, VAX, and AXP.
I've seen a few projects that have started or have stopped that attempt to
achieve similar goals.
- Matt
At 07:46 PM 1/3/2002 -0500, you wrote:
>Why not just get a VAX (or two or three?)
>
>Peace... Sridhar
>
>On Thu, 3 Jan 2002, Ron Hudson wrote:
>
> > Date: Thu, 03 Jan 2002 09:51:27 -0800
> > From: Ron Hudson <rhudson(a)cnonline.net>
> > Reply-To: classiccmp(a)classiccmp.org
> > To: classiccmp(a)classiccmp.org
> > Subject: Re: FreeVMS
> >
> > I for one, would LOVE to run a VMS look alike on my
> > i386 machine (or at least one of my spare machines...)
> > It would bring back younger days when I was an op on several
> > vaxen. (also some dg and some apollo)
> >
> > please please please!!! : ^ )
> >
> >
> >
> > Matthew Sell wrote:
> >
> > >
> > >
> > > I know I'm going to open up a can of worms on this post, but my
> > > curiosity is killing me....
> > >
> > >
> > > Now that I have OpenVMS 6.1 running on my VAX 4000, I'm curious about
> > > the status of the various "FreeVMS" projects that are in progress (or so
> > > it would seem....).
> > >
> > > Are any of these projects really in active development? Which projects
> > > have the greatest potential for operation? I checked several sites
> > > related to "FreeVMS", which actually seems to be a common name for
> > > several different projects with different goals.
> > >
> > > I'd love to "cut my teeth" with kernel development after working with
> > > Linux for several years. I personally think it would be neat to have an
> > > accurate version of FreeVMS that would work on VAX, AXP, and i386
> > > (gulp!). When I say accurate, I mean that FreeVMS would respond the same
> > > as VMS would for the various commands and peripherals.
> > >
> > > Some of you probably think it would be silly to take an i386 version of
> > > FreeVMS and port it "back" to VAX and AXP, but it would be a neat way to
> > > use FreeVMS, especially if the OpenVMS hobbyist program (or OpenVMS)
> > > were to go away.
> > >
> > > Nuts? Probably. Neat? Yes!
> > >
> > > Here are links to the various FreeVMS projects I have visited:
> > >
> > > http://www.panix.com/~kingdon/free-vms.html
> > > http://www.freevms.org/
> > > http://www.djesys.com/vms/freevms/
> > >
> > >
> > > - Matt
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Matthew Sell
> > > Programmer
> > > On Time Support, Inc.
> > > www.ontimesupport.com
> > > (281) 296-6066
> > >
> > > Join the Metrology Software discussion group METLIST!
> > > http://www.ontimesupport.com/cgi-bin/mojo/mojo.cgi
> > >
> > >
> > > "One World, One Web, One Program" - Microsoft Promotional Ad
> > > "Ein Volk, Ein Reich, Ein Fuhrer" - Adolf Hitler
> > >
> > > Many thanks for this tagline to a fellow RGVAC'er...
> >
> >
Matthew Sell
Programmer
On Time Support, Inc.
www.ontimesupport.com
(281) 296-6066
Join the Metrology Software discussion group METLIST!
http://www.ontimesupport.com/cgi-bin/mojo/mojo.cgi
"One World, One Web, One Program" - Microsoft Promotional Ad
"Ein Volk, Ein Reich, Ein Fuhrer" - Adolf Hitler
Many thanks for this tagline to a fellow RGVAC'er...
Hello. About the probes with the DILOG DQ614 over one PDP-11/23 PLUS
with one MFM hard disk using the diagnostics program for these board,
I have some matters to speak about:
* Somebody spoke about a possible modification of the U55 chip.
I have the reference of the chip mounted. It's the 55U-91358.
In fact, the order number of some chips of the board is:
25U-91353
69U-91354A
64U-91355
21U-91356
22U-91357
55U-91358
The question is: Could be used some XXDP diagnostic to determine
the possible problem of the board that I told in my previous message
about it ?
* I want to use another hard disk, one IBM MFM full height of 44 Mb.
Is one Type 31 (for the IBM PC) disk. Somebody has the complete
geometry of it ? I don't have it actually available in the BIOS of my PCs,
but I suppose that one 486 or 386 could have it.
Thanks and Greetings
Sergio
On Jan 5, 23:41, The Wanderer wrote:
> Pete Turnbull wrote:
> I swapped the Unibus map and the cache control board, and the machine
> behaves
> apparently much better.
Hmm.. Lots of DEC CPU backplanes have dedicated slots for various things,
and the position/order of the boards is very important. I don't know if
the 11/70 is like that, but I'd not be at all surprised if it were. Have
you checked that everything is in exactly the right place? If you've
removed any optional boards, have you checked in case any jumpers need
replaced?
> After pressing the bootstrap key (someone made a
> small
> switch between tabs 1 & 2 of the M9312) and it goes into a sort of loop
> after
> a second or so.
Do you mean that someone swapped the wires from their normal places, or
that someone added a switch that wouldn't normally be there?
> When pressing halt, the address display ends in 344,
> while the
> data display shows 116.
>
> Also memory location 400000 through 477777 are accessible via the
> console and
> I can dump data and read from it.
That's an unusual address, and it's only 32K bytes (16KW). You said you
had two 64KW boards. What type are they? They probably have switches to
set their base addresses. Are these set correctly? It would be worth
trying just one, set to address zero, and see if that improves things.
Start with the minimum in the system, and build it up as you get things
working.
> > That sounds encouraging. At least it seems to be running the
diagnostic
> > code. I think, though, that the address it halts at is what tells you
what
> > (if anything) failed the test. If you can tell where it halted, it may
be
> > able to look that up.
> At 344 (addr) and 116 in the data display. No idea if this a valid value
> though...
It's an odd sort of address. I'd expect it to stop at an address in the
ROM. If you had to halt it manually, it must have been running in a loop.
Why that address, I have no idea, because according to the M9312 manual,
it only runs code from ROM until it has booted some device. According to
the M9312 manual, it runs various CPU instruction tests, then tests memory
>from 1000 to as high as it can go (up to 28KW), then tests the cache. It
will halt if it gets an error in any of the memory or cache tests, but you
can press CONTINUE to ignore the fault and carry on.
> > Do you have the manual for the M9312? There are several ROMs that
might
> Yes, the 9312 has the 233 type rom (11/70 diagnostic, so this is ok).
All DEC ROM numbers begin 23-<something>. All DEC diagnostic PROM numbers
end in F1. The correct bootstrap for a M9312 in an 11/70 is 23-616F1. If
that's not what you've got, it's unlikely to work correctly.
> Has the location of the available ram in my case anything to do with the
> high address
> limit register? According to the usermanual it is the high imit of the
> memory, not
> it starting address?
Well, you ought to set it to the correct value, obviously, but I've no idea
what would happen if you set it too high or too low. Yes, it's the high
limit.
> On the other hand, the starting address of 400000 can maybe also the
> result of some
> initial values in the unibus map registers?
I think the bus init is supposed to set them to zeros. Of course, the map
may be faulty. Normally each memory board has a switch pack to set its
starting address. What type of board(s) do you have?
--
Pete Peter Turnbull
Network Manager
University of York
i think you and i are saying the same thing.
except i am putting more emphasis on the bot being self controlled
with outside help. you are putting more emphasis on remote control
with eventual self-control.
the thing is; the brain is the easiest part. the brain of the bot will
be self learning so each bot will learn as it goes as opposed to me
having to do a lot of designing.
Follow nature for ideas
for example a little child has just enough knowledge to ask about what
he or she doesnt know about.
so each bot will know just enough to refer to the master os on whatever it
doesnt
know until it learns.
it will be set up to sort , retain, recall various information.
joee
Hello, does anyone know of a copy of the DECStation 3100 hardware guide
(or whatever it is called) available online? Also, does anyone have a
handle on a URL for a piccie of the backside of one of these beasts?
Thanks for listening
Alex
--
melt
meltlet(a)fastmail.fm
I too had a Digicomp, which was more of a calculator than computer. Goto www.incolor.inetnebr.com/bill_r/computer_simulators.htm to see examples of other classic computers built virtually instead of replicating the entire kit with plastic and wire ;)
On Jan 5, 16:34, Tom Leffingwell wrote:
> On Sat, 5 Jan 2002, Pete Turnbull wrote:
> I did find on the MSV11-L
> that X was connected to U. I'm not sure what U is for, but seemed to be
> grounded, so I removed it, which I assume set the address back to 0. At
> that point it started working.
Yes, U is the ground for V...Z (K is the ground for L...P). X-U (with all
other bank pins disconnected) gives a start address of 00100000 (32K,
decimal).
> How do I know whether or not I need to enable or disable I/O page
> setting? I haven't tried to enable it on the MSV11-L, although it was
> enabled on the MSV11-D before I removed it. What symptoms occur if its
> set wrong?
If you have any devices in the lower 2KW of the I/O page, you should
disable memory access to that area. If you don't, you'll get a conflict
when both the I/O device and the memory try to respond to the same address.
However, not many small QBus systems have I/O devices in that address
range (160000-167777). It's normal to leave the whole I/O page for I/O
devices, and disable memory in that area, though.
> > And that's the second thing. The MSV11-L doesn't use BBS7 for
everything
> > it decodes, so you have to set it according to whether it's in a 22-bit
> > system or an 18-bit system. If there's a jumper from R-T, it's set for
a
> > 2MW system. Remove it for 128KW systems.
>
> I did find out that I have the 22-bit KDF11-A, although I haven't checked
> the backplane yet. If the backplane is 22-bit, should put the R-T jumper
> in the M8059? Does it matter if I only have 128KW of memory?
I don't know; try it and see :-) I suspect if you set it to 18-bit mode
and use it in a 22-bit system, it will respond to multiple addresses. If
you set it to 22-bit mode and use it in an 18-bit system with no
termination on the upper 4 lines, it may respond to noise on those lines
and not turn on when it should. The bus signals are active low, so if
there's no signal they should float high and read as zeros -- but life and
bus systems are not always so predictable.
OTOH, if you have a 22-bit processor, it's easy to upgrade the backplane by
soldering four pieces of wire-wrap wire to bus the extra 4 address bits
(and upgrade the BDV11 if necessaary).
--
Pete Peter Turnbull
Network Manager
University of York
> From: Chris <mythtech(a)Mac.com>
> Ugh.. try reading William Faulkner (I am pretty sure that is who it
> was)... he has 3 page run on sentences... worst reading my poor dyslexic
> brain ever had to deal with.
Faulkner was an amateur. Try picking up "The Ticket That Exploded," "The
Soft Machine," "The Job" or a number of other books by William S.
Burroughs, and you'll find run-on sentences as long as 10 pages.
(Yes, he's related to the Burroughs calculator and computer firms -- his
grandfather invented the hydraulic piston which made the adding machine
possible.)
Glen
0/0
