> On Aug 19, 2015, at 3:33 PM, d...@mitton.com wrote:
>
> From: Paul Koning
>
>>> ...
>
>> Ok. RSTS does indeed check for duplicate vectors. It also checks for devices
>> interrupting at too high a priority.
>
>> It’s pretty neat code. Back in 1977 or so when that came out, it may have
>> b
From: Paul Koning
...
Ok. RSTS does indeed check for duplicate vectors. It also checks for
devices interrupting at too high a priority.
It?s pretty neat code. Back in 1977 or so when that came out, it may
have been one of the first autoconfig systems, at least in DEC. It
could probe almo
On 2015-08-19 04:27, Jon Elson wrote:
On 08/18/2015 01:00 PM, Johnny Billquist wrote:
The floating address space was pretty much there from the start for
the Unibus, even before you had "large" systems. For most controllers,
only the first one has a fixed address, and all others were assigned
f
On 08/18/2015 01:00 PM, Johnny Billquist wrote:
The floating address space was pretty much there from the
start for the Unibus, even before you had "large" systems.
For most controllers, only the first one has a fixed
address, and all others were assigned from the floating
space. Makes sense
Paul Koning skrev: (18 augusti 2015 21:55:23 CEST)
>
>> On Aug 18, 2015, at 3:48 PM, Johnny Billquist
>wrote:
>>
>> On 2015-08-18 21:29, Paul Koning wrote:
>>>
On Aug 18, 2015, at 2:00 PM, Johnny Billquist
>wrote:
On 2015-08-18 19:05, Jon Elson wrote:
...
> Most like
> On Aug 18, 2015, at 3:48 PM, Johnny Billquist wrote:
>
> On 2015-08-18 21:29, Paul Koning wrote:
>>
>>> On Aug 18, 2015, at 2:00 PM, Johnny Billquist wrote:
>>>
>>> On 2015-08-18 19:05, Jon Elson wrote:
>>> ...
Most likely, some board was added or removed from the system before you
>>>
On 2015-08-18 21:29, Paul Koning wrote:
On Aug 18, 2015, at 2:00 PM, Johnny Billquist wrote:
On 2015-08-18 19:05, Jon Elson wrote:
...
Most likely, some board was added or removed from the system before you
got it, and it caused the vector to now be wrong.
The vector is usually not the fir
> On Aug 18, 2015, at 2:00 PM, Johnny Billquist wrote:
>
> On 2015-08-18 19:05, Jon Elson wrote:
> ...
>> Most likely, some board was added or removed from the system before you
>> got it, and it caused the vector to now be wrong.
>
> The vector is usually not the first victim. The CSR address
On 2015-08-18 19:05, Jon Elson wrote:
On 08/18/2015 10:48 AM, Holm Tiffe wrote:
Understand my quandary: I have changed not a single bit on the
hardware while cleaning and repairing it and besides that DHU11-DHV11
Switch the board was in the published factory setting!
DEC went to this floating a
On 08/18/2015 10:48 AM, Holm Tiffe wrote:
Understand my quandary: I have changed not a single bit on
the hardware while cleaning and repairing it and besides
that DHU11-DHV11 Switch the board was in the published
factory setting!
DEC went to this floating address/vector scheme back in the
PDP-
On 2015-08-18 17:48, Holm Tiffe wrote:
Johnny Billquist wrote:
On 2015-08-18 14:17, Holm Tiffe wrote:
What makes me wonder is that I've wrote that the vector of the card schould
be 300...but:
What makes you say the card should have vector 300?
That exactly is the question...
The thing is
Johnny Billquist wrote:
> On 2015-08-18 14:17, Holm Tiffe wrote:
> >What makes me wonder is that I've wrote that the vector of the card schould
> >be 300...but:
>
> What makes you say the card should have vector 300?
That exactly is the question...
>
> >$ mcr sysgen
> >SYSGEN> SH/CONF
> >
> >
On 2015-08-18 14:17, Holm Tiffe wrote:
What makes me wonder is that I've wrote that the vector of the card schould
be 300...but:
What makes you say the card should have vector 300?
$ mcr sysgen
SYSGEN> SH/CONF
System CSR and Vectors on 18-AUG-2015 14:11:12.81
Name: PAA Units: 1
Holm Tiffe wrote:
[snip]
>
> The additional VT420 is connected to txa3: and I haven't changed the term
> parameters since reboot:
>
> $ sh term txa3:
> Terminal: _TXA3: Device_Type: Unknown Owner: No Owner
>
>Input:9600 LFfill: 0 Width: 80 Parity: None
>O
Holm Tiffe wrote:
> Holm Tiffe wrote:
>
> > Johnny Billquist wrote:
> >
> > > On 2015-08-18 11:31, Holm Tiffe wrote:
> > > >Jerry Weiss wrote:
> > > >
> > > >>Sorry if some of the suggestions aren?t appropriate, was just throwing
> > > >>a
> > > >>few things out.
> > > >>
> > > >>
> > > >>$ana
Holm Tiffe wrote:
> Johnny Billquist wrote:
>
> > On 2015-08-18 11:31, Holm Tiffe wrote:
> > >Jerry Weiss wrote:
> > >
> > >>Sorry if some of the suggestions aren?t appropriate, was just throwing a
> > >>few things out.
> > >>
> > >>
> > >>$analyze/error/since=today/full/include=tx
> > >>
> > >>
Johnny Billquist wrote:
> On 2015-08-18 11:31, Holm Tiffe wrote:
> >Jerry Weiss wrote:
> >
> >>Sorry if some of the suggestions aren?t appropriate, was just throwing a
> >>few things out.
> >>
> >>
> >>$analyze/error/since=today/full/include=tx
> >>
> >>Can you post a sample of the output for one
Holm Tiffe wrote:
> Jerry Weiss wrote:
>
> > Sorry if some of the suggestions aren?t appropriate, was just throwing a
> > few things out.
> >
> >
> > $analyze/error/since=today/full/include=tx
> >
> > Can you post a sample of the output for one of the lines that has an error?
> >
> > Regar
On 2015-08-18 11:31, Holm Tiffe wrote:
Jerry Weiss wrote:
Sorry if some of the suggestions aren?t appropriate, was just throwing a few
things out.
$analyze/error/since=today/full/include=tx
Can you post a sample of the output for one of the lines that has an error?
Regards,
Jerry
Hmm...
Jerry Weiss wrote:
> Sorry if some of the suggestions aren?t appropriate, was just throwing a few
> things out.
>
>
> $analyze/error/since=today/full/include=tx
>
> Can you post a sample of the output for one of the lines that has an error?
>
> Regards,
> Jerry
>
Hmm...
$analyze/error/s
Guys. Slow down. It is not a cable error. It is not a terminal error. If the
system also had the card already installed before it is also not an
installation error. It is also probably not an interrupt error.
I can go into more details behind the reasoning for this if people are
interested.
Hol
Holm Tiffe wrote:
>
> Please give me a hint how exactly I should setup a line, no problem for me
> on unix with stty ..but I don't know much about VMS...
>
I've never seen this particular arrangement so I am just guessing here, based
on experience with other VAX terminal setups. The terminal set
Sorry if some of the suggestions aren’t appropriate, was just throwing a few
things out.
$analyze/error/since=today/full/include=tx
Can you post a sample of the output for one of the lines that has an error?
Regards,
Jerry
> On Aug 17, 2015, at 4:11 PM, Holm Tiffe wrote:
>
> Jerry Weiss
Jay Jaeger wrote:
> On 8/17/2015 1:18 PM, Holm Tiffe wrote:
>
> > Johnny Billquist wrote:
> >
> > [..]
> >>>
> >>> Since I'm a total VMS Noob I now have some Questions:
> >>>
> >>> .. have I missed something?
> >>> .. is the CXY08 bad?
> >>> .. what could I try next?
> >>> ...is there some diagn
Jerry Weiss wrote:
> A few quick thoughts:
>
> 1) Bad non-name USB/Serial converter. I have one that won?t speak to a MVII
> console or certain non-DEC DLV11J cards
...sorry, USB in a DEC VT420 _and_ an Bull Compuprint 970?
(http://www.computer-makarow.de/images/product_images/popup_images/431
On 8/17/2015 1:18 PM, Holm Tiffe wrote:
> Johnny Billquist wrote:
>
> [..]
>>>
>>> Since I'm a total VMS Noob I now have some Questions:
>>>
>>> .. have I missed something?
>>> .. is the CXY08 bad?
>>> .. what could I try next?
>>> ...is there some diagnosting software for the CXY08 existing for
A few quick thoughts:
1) Bad non-name USB/Serial converter. I have one that won’t speak to a MVII
console or certain non-DEC DLV11J cards
2) LED Analyzer is pulling too much current on the lines
3) Bad +-15 volt converter on board.Do you see any activity on control
signals or send line? T
Glen Slick wrote:
> You don't say so asking just to be sure, are you using standard BC19N four
> port breakout cables with the CXY08?
Yes, BC19N-12 is the label..
Regards,
Holm
--
Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe,
Freiberger Straße 42, 09600 Oberschöna, USt
You don't say so asking just to be sure, are you using standard BC19N four
port breakout cables with the CXY08?
Sean Caron wrote:
> Have you tried just a "quick-n-dirty" serial cable with only TXD, RXD and
> GND wired? Sometimes trying to accommodate all those modem control lines
> will just lead you down the rabbit hole ... Just a thought.
>
> Best,
>
> Sean
>
>
Yes, tried this with XON/XOFF setting o
Have you tried just a "quick-n-dirty" serial cable with only TXD, RXD and
GND wired? Sometimes trying to accommodate all those modem control lines
will just lead you down the rabbit hole ... Just a thought.
Best,
Sean
On Mon, Aug 17, 2015 at 1:40 PM, Johnny Billquist wrote:
> On 2015-08-17 19
Johnny Billquist wrote:
[..]
> >
> >Since I'm a total VMS Noob I now have some Questions:
> >
> >.. have I missed something?
> >.. is the CXY08 bad?
> >.. what could I try next?
> >...is there some diagnosting software for the CXY08 existing for VMS
> >and if yes, where can I get it?
> >
> >Th
On 2015-08-17 19:33, Holm Tiffe wrote:
Hi guys,
I'm fiddeling around for hours now to get an M3119-YA CXY08
Multiplexer to work in my VAX4000/300 on VMS7.3.
The Card is properly detected it seems..
Device Device Error
Name Status Count
Hi guys,
I'm fiddeling around for hours now to get an M3119-YA CXY08
Multiplexer to work in my VAX4000/300 on VMS7.3.
The Card is properly detected it seems..
Device Device Error
Name Status Count
FTA0: Offline
34 matches
Mail list logo
