Hi,
>I've seen references to VAXwindows. I know it predates VMS 5 but I am not
>sure if it was a layered product or not.
VAXwindows was a layered product (like just about everything DEC sold for
VMS). Without it a VAXstation of that era wouldn't be very user friendly,
but it would boot happily
Folks,
I found a few technical reference manuals (KA820/KA825 and VAX 6200 and 6600
series) through google search, etc.
I reviewed KA820/KA825 (VAX 82x0/83x0) tech docs and it does not use SRM
firmware like KA780/KA865 processors. It uses VAXBI interface for I/O
devices. I think that it
I've seen references to VAXwindows. I know it predates VMS 5 but I am not
sure if it was a layered product or not. There is also a very primitive
window system for P/OS on the DECPro called Synergy (which I would love to
find documentation for) that you could control with either the keyboard or
I've seen references to VAXwindows. I know it predates VMS 5 but I am not
sure if it was a layered product or not. There is also a very primitive
window system for P/OS on the DECPro called Synergy (which I would love to
find documentation for) that you could control with either the keyboard or
IIRC, someone successfully compiled simh on Android using the Termux shell.
I really don't want to root my tablet and will be without my computer for
a week or so, so I thought I would play around with some OS configurations,
brush up on my PDP-11 assembly etc. Anyways I am not good with Linux
The Qbus-based VAXen support the QVSS (black-n-white) video module cards, which
were the basis of the original VaxStation I and were also compatible with
VaxStation II's, III's, and 4000's. The SIMH QVSS uses SDL for visualization.
This is a native DecWindows interface.
To be honest, it's just
> On Mar 9, 2017, at 12:15 PM, Mark Pizzolato wrote:
>
> On Wednesday, March 8, 2017 at 11:50 PM, Johnny Billquist wrote:
>> ...
>
> When Matt Burke initially was working on this, I believe that we talked
> briefly
> about extending sim_ether to support packet delivery
On 2017-03-09 19:00, Paul Koning wrote:
On Mar 9, 2017, at 12:27 PM, Timothe Litt wrote:
..
With respect to an earlier question about CI emulation: The best approach may
be to emulate it as multicast ethernet. Setup a couple of groups for each star
coupler. Each coupler
On 2017-03-09 19:09, Clem Cole wrote:
It looks that way..., but I need some help from Bob or Mark on VH
history, That was developed at DEC during the period I was off doing
Masscomp/Stellar et al. During my time earlier time with PDP11 and
Vaxen, you used DEC DZ's or DEC DH's or Able
Clem...
On 2017-03-09 15:58, Clem Cole wrote:
Warren,
We can take this offline. The quick answer is as far as simh is
concerned leave everything as 8 bits.
I'll show you how to make the rest work properly. The logins will run 8
bits also, but will run with parity enabled which BSD will
> On Mar 9, 2017, at 1:23 PM, Timothe Litt wrote:
>
> I don't have time to dig up the details. But TOPS-10/20 definitely supported
> the CI.
Interesting. That sounds like a product-specific item rather than part of the
standard architecture.
paul
> On Mar 9, 2017, at 3:15 PM, dun...@caltech.edu wrote:
>
>> So ...If the DHV is supposed to the simh emulation of the combination of a
>> DEC DH11 and DM11 pair (the DM11 was the modem control option for the DH),
>> then this should "just work"
>
> The SIMH VH device is a simulation of the DEC
There were 3rd party Unibus to Qbus converters that would handle the signal
Mux/decus issues on the bus lines.
I never saw any on 11/780 class boxes.
Crappy UBA was slow. Most were used to
put Unibus peripherals on Qbus Vaxes.
Bill
-Original Message-
From: Clem Cole
I used DHV11s on Microvax II when they we're real hardware. Worked fine under
VMS. I imagine DH11 wasn't different enough for them to not work on unibus.
Sent from my Galaxy Tab® A
Original message From: Clem Cole Date: 3/9/17
12:13 PM (GMT-07:00) To: Mark
> So ...If the DHV is supposed to the simh emulation of the combination of a
> DEC DH11 and DM11 pair (the DM11 was the modem control option for the DH),
> then this should "just work"
The SIMH VH device is a simulation of the DEC DHQ device (M3107), a dual
height Qbus board, normally supporting
On Thu, Mar 9, 2017 at 2:16 PM, William Pechter wrote:
> Unibus DH/DM backplane s and boards were not supported by DEC on Unibus...
I assume you mean were not supported on the VAX UBA. And that would make
sense.
___
Simh mailing
On Thu, Mar 9, 2017 at 2:16 PM, William Pechter wrote:
> I did Field Service through 8650s and never saw them. DMF32s - IIRC had
> modem control capability on some lines or is my memory shot.
DMF32 and DZ had >>partial<< modem control. It was crock in both cases
and did
Quick question - I saw SDL graphics support mentioned somewhere and wondered
which emulators have graphics support? Do any of the VAX ones?
Can I run native DECWindows on any of them?
sampsa
___
Simh mailing list
Simh@trailing-edge.com
On Thu, Mar 9, 2017 at 2:18 PM, Cory Smelosky wrote:
> device dhu0at uba? csr 0160440 vector dhurint
>>
>> It's been years since, I did this stuff...
>>
>> 1. 0160400 is 0xE120 and 0160400 certainly looks right for the
>> Unibus address for a DH.
On 3/9/17 11:18 AM, Cory Smelosky wrote:
>> 3. I never saw a real DEC DH on a Vax because of power and space issues.
>> 4. That said, we used to mix DEC DH11s and Able DH11's on the PDP-11
>> all the time
>> 5. Able DH11's were the most used serial controllers in BSD UNIX land
>> for
Clem Cole wrote:
Mark... as an FYI if it is of any help..
VH address=2013E120-2013E15F*, vector=C0-DC*, BR4, lines=64, 4
units
VH0 attached to 8070, DHU mode, Modem
0 current connections
VH1 DHU mode
VH2 DHU mode
VH3 DHU mode
device dhu0at
Unibus DH/DM backplane s and boards were not supported by DEC on Unibus...
Does Simh support them.
I did Field Service through 8650s and never saw them. DMF32s - IIRC had
modem control capability on some lines or is my memory shot.
Bill
___
Simh
Mark... as an FYI if it is of any help..
VH address=2013E120-2013E15F*, vector=C0-DC*, BR4, lines=64, 4
units
VH0 attached to 8070, DHU mode, Modem
0 current connections
VH1 DHU mode
VH2 DHU mode
VH3 DHU mode
device dhu0at uba? csr 0160440
On Thu, Mar 9, 2017 at 1:33 PM, Mark Pizzolato wrote:
> You mean DHV, not DVH
yes
___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
On Thu, Mar 9, 2017, at 10:33, Mark Pizzolato wrote:
> You mean DHV, not DVH, right? DHV is a Qbus variant of some version
> of the DH11 device. A VAX 780, not having a Qbus, wouldn’t have such
> a device in its configuration.
>
> The addresses you see in the SHOW CONFIG output are
You mean DHV, not DVH, right? DHV is a Qbus variant of some version of the
DH11 device. A VAX 780, not having a Qbus, wouldn’t have such a device in its
configuration.
The addresses you see in the SHOW CONFIG output are where the simulator will
respond to I/O space references. Those
The simh VAX simulators will readily participate in LAVC clustering with
other simh simulators and/or real VAX systems as long as they're all present
on the same LAN.
How to configure and/or manage cluster systems is described in various
DEC documents with nothing special relevant to the
> On Mar 9, 2017, at 12:27 PM, Timothe Litt wrote:
>
> ..
> With respect to an earlier question about CI emulation: The best approach
> may be to emulate it as multicast ethernet. Setup a couple of groups for
> each star coupler. Each coupler supports up to 32 nodes. For
The CI interface is the KLIPA. Its a KL10-only device that sits in an
RH20 channel slot. It uses a port architecture similar to the CI780,
with queues and 36-bit pointers in physical memory. It's supported in 7.04.
With respect to an earlier question about CI emulation: The best
approach may
On Wednesday, March 8, 2017 at 11:50 PM, Johnny Billquist wrote:
> On 2017-03-09 02:26, Paul Koning wrote:
> >
> >> On Mar 8, 2017, at 7:44 PM, Johnny Billquist wrote:
> >>
> >> On 2017-03-08 22:15, Bob Supnik wrote:
> >>> The HSC family offered a superset of capabilities
On Thursday, March 9, 2017 at 4:04 AM, Warren Toomey wrote:
> Is there a way to set bind some (but not all) DZ lines to localhost port X,
> and some (but not all) DZ lines to any address port Y (or X, doesn't matter)?
> I want to make the uucp DZ TCP ports visible on the Internet, but set the
>
Warren,
We can take this offline. The quick answer is as far as simh is concerned
leave everything as 8 bits.
I'll show you how to make the rest work properly. The logins will run 8
bits also, but will run with parity enabled which BSD will handle just
peachy.
Also, as I mentioned
32 matches
Mail list logo