On 2013-01-06 20:56, Steve Davidson wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Sunday, January 06, 2013 14:51
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] DU11 vs. DUV11
On 2013-01-06 18:13, Lee Gleason wrote:
.IF DF L$$SI1
MOVB @(R5)+,-(SP) ;;; COPY CHARACTER FOR WORD MOVE
MOV (SP)+,(R4) ;;; (SAVES 85 USECS ON PDT-11)
.IFF ; DF L$$SI1
MOVB @(R5)+,(R4) ;;; OUTPUT A CHARACTER
.ENDC ; DF L$$SI1
OK, I'll bite. Why is moving a character in the deferred
location in
R5 to the stack and then, from the stack to the address in
R4 faster
than just going from the deferred R5 location to the R4 address?
--
I'm even more curious what a PDT-11 optimization is doing
in an RSX
driver...was there at one time an RSX product product
planned for the
PDT family?
I'm not at all surprised to learn that RSX ran on the PDT-11.
RSX can run on pretty much any PDP-11, as long as you have
atleast around 50K of ram. That's about the lower limit, I'd
guess. No other hardware frills or features required.
PDT-11's, I want to say 30KB of RAM. May 28K, it has been too long...
The PDT-11/150 came in three configurations.
16K, 32K or 60K (bytes).
Johnny
-Steve
I'm curious if the PDT-11 supported booting over the DUV-11.
That would have made it a pretty nice netbooted, diskless RSX
machine. Otherwise I'd suspect the most common use was just
11S booted from whatever locally. But an unmapped 11M system
is a possibility, I guess.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-01-06 20:35, Steve Davidson wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of John Wilson
Sent: Sunday, January 06, 2013 14:29
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] DU11 vs. DUV11
From: "Lee Gleason" <lee.gleason at comcast.net>
I'm even more curious what a PDT-11 optimization is doing in an RSX
driver...was there at one time an RSX product product
planned for the
PDT family?
I've never met a PDT-11/110 in person. The docs say they
were downline-load-only -- so what DID they run? MRRT11?
RSX11S would certainly make sense. Also, DEC dumped a lot of
the PDTs to their own employees, so maybe someone made a few
tweaks to the RSX code for their own evil purposes at home.
John Wilson
D Bit
The main target for the PDT-11 was RT-11. It was slow. The floppies
spent a great deal of time seeking. They were the size of a small
microwave oven. In software services we would use it to test patches to
RT-11 and some of the layered products. I had one for a time that I
used at home over a 300 baud connection. Tough to say whether the
dial-up or the floppies were slower... :-)
You must be talking of the PDT-11/150 then. The /110 and /130 sat inside a VT100 shell. Extremely similar to a VT103 (I actually never figured out what the difference between a VT103 and a PDT-11/130 is.)
But I figure RSX-11S would fit those machines perfectly. After boot, you wouldn't even care about how slow the floppy was. :-)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Sunday, January 06, 2013 14:51
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] DU11 vs. DUV11
On 2013-01-06 18:13, Lee Gleason wrote:
.IF DF L$$SI1
MOVB @(R5)+,-(SP) ;;; COPY CHARACTER FOR WORD MOVE
MOV (SP)+,(R4) ;;; (SAVES 85 USECS ON PDT-11)
.IFF ; DF L$$SI1
MOVB @(R5)+,(R4) ;;; OUTPUT A CHARACTER
.ENDC ; DF L$$SI1
OK, I'll bite. Why is moving a character in the deferred
location in
R5 to the stack and then, from the stack to the address in
R4 faster
than just going from the deferred R5 location to the R4 address?
--
I'm even more curious what a PDT-11 optimization is doing
in an RSX
driver...was there at one time an RSX product product
planned for the
PDT family?
I'm not at all surprised to learn that RSX ran on the PDT-11.
RSX can run on pretty much any PDP-11, as long as you have
atleast around 50K of ram. That's about the lower limit, I'd
guess. No other hardware frills or features required.
PDT-11's, I want to say 30KB of RAM. May 28K, it has been too long...
-Steve
I'm curious if the PDT-11 supported booting over the DUV-11.
That would have made it a pretty nice netbooted, diskless RSX
machine. Otherwise I'd suspect the most common use was just
11S booted from whatever locally. But an unmapped 11M system
is a possibility, I guess.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-01-06 20:29, John Wilson wrote:
From: "Lee Gleason" <lee.gleason at comcast.net>
I'm even more curious what a PDT-11 optimization is doing in an RSX
driver...was there at one time an RSX product product planned for the PDT
family?
I've never met a PDT-11/110 in person. The docs say they were
downline-load-only -- so what DID they run? MRRT11? RSX11S would
certainly make sense. Also, DEC dumped a lot of the PDTs to their
own employees, so maybe someone made a few tweaks to the RSX code
for their own evil purposes at home.
I'd suspect 11S should work right out of the box. But both the /110 and /130 was Qbus, so I'd suspect them to be pretty straight forward. The one I was thinking of was the /150, which is the one I assumed you were talking about when you talked about the serial chip and DUV-11 emulation, John...
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-01-06 19:41, Gregg Levine wrote:
On Sun, Jan 6, 2013 at 1:20 PM, Bill Pechter <pechter at gmail.com> wrote:
perhaps rsx11s was planned for the pdt11 series.
On Jan 6, 2013 12:14 PM, "Lee Gleason" <lee.gleason at comcast.net> wrote:
.IF DF L$$SI1
MOVB @(R5)+,-(SP) ;;; COPY CHARACTER FOR WORD MOVE
MOV (SP)+,(R4) ;;; (SAVES 85 USECS ON PDT-11)
.IFF ; DF L$$SI1
MOVB @(R5)+,(R4) ;;; OUTPUT A CHARACTER
.ENDC ; DF L$$SI1
OK, I'll bite. Why is moving a character in the deferred location in
R5 to the stack and then, from the stack to the address in R4 faster
than just going from the deferred R5 location to the R4 address?
--
I'm even more curious what a PDT-11 optimization is doing in an RSX
driver...was there at one time an RSX product product planned for the PDT
family?
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
Hello!
I'm even more curious just what finally happened to that family
member. (And this week I'm not interested in finding one or two.)
11S is just as up to date and supported as 11M and M-PLUS...
Not that uncommon for it to even be netbooted and totally diskless.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2013-01-06 18:13, Lee Gleason wrote:
.IF DF L$$SI1
MOVB @(R5)+,-(SP) ;;; COPY CHARACTER FOR WORD MOVE
MOV (SP)+,(R4) ;;; (SAVES 85 USECS ON PDT-11)
.IFF ; DF L$$SI1
MOVB @(R5)+,(R4) ;;; OUTPUT A CHARACTER
.ENDC ; DF L$$SI1
OK, I'll bite. Why is moving a character in the deferred location in
R5 to the stack and then, from the stack to the address in R4 faster
than just going from the deferred R5 location to the R4 address?
--
I'm even more curious what a PDT-11 optimization is doing in an RSX
driver...was there at one time an RSX product product planned for the
PDT family?
I'm not at all surprised to learn that RSX ran on the PDT-11.
RSX can run on pretty much any PDP-11, as long as you have atleast around 50K of ram. That's about the lower limit, I'd guess. No other hardware frills or features required.
I'm curious if the PDT-11 supported booting over the DUV-11. That would have made it a pretty nice netbooted, diskless RSX machine. Otherwise I'd suspect the most common use was just 11S booted from whatever locally. But an unmapped 11M system is a possibility, I guess.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of John Wilson
Sent: Sunday, January 06, 2013 14:29
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] DU11 vs. DUV11
From: "Lee Gleason" <lee.gleason at comcast.net>
I'm even more curious what a PDT-11 optimization is doing in an RSX
driver...was there at one time an RSX product product
planned for the
PDT family?
I've never met a PDT-11/110 in person. The docs say they
were downline-load-only -- so what DID they run? MRRT11?
RSX11S would certainly make sense. Also, DEC dumped a lot of
the PDTs to their own employees, so maybe someone made a few
tweaks to the RSX code for their own evil purposes at home.
John Wilson
D Bit
The main target for the PDT-11 was RT-11. It was slow. The floppies
spent a great deal of time seeking. They were the size of a small
microwave oven. In software services we would use it to test patches to
RT-11 and some of the layered products. I had one for a time that I
used at home over a 300 baud connection. Tough to say whether the
dial-up or the floppies were slower... :-)
-Steve
From: "Lee Gleason" <lee.gleason at comcast.net>
I'm even more curious what a PDT-11 optimization is doing in an RSX
driver...was there at one time an RSX product product planned for the PDT
family?
I've never met a PDT-11/110 in person. The docs say they were
downline-load-only -- so what DID they run? MRRT11? RSX11S would
certainly make sense. Also, DEC dumped a lot of the PDTs to their
own employees, so maybe someone made a few tweaks to the RSX code
for their own evil purposes at home.
John Wilson
D Bit
On Sun, Jan 6, 2013 at 1:20 PM, Bill Pechter <pechter at gmail.com> wrote:
perhaps rsx11s was planned for the pdt11 series.
On Jan 6, 2013 12:14 PM, "Lee Gleason" <lee.gleason at comcast.net> wrote:
.IF DF L$$SI1
MOVB @(R5)+,-(SP) ;;; COPY CHARACTER FOR WORD MOVE
MOV (SP)+,(R4) ;;; (SAVES 85 USECS ON PDT-11)
.IFF ; DF L$$SI1
MOVB @(R5)+,(R4) ;;; OUTPUT A CHARACTER
.ENDC ; DF L$$SI1
OK, I'll bite. Why is moving a character in the deferred location in
R5 to the stack and then, from the stack to the address in R4 faster
than just going from the deferred R5 location to the R4 address?
--
I'm even more curious what a PDT-11 optimization is doing in an RSX
driver...was there at one time an RSX product product planned for the PDT
family?
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
Hello!
I'm even more curious just what finally happened to that family
member. (And this week I'm not interested in finding one or two.)
--
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
perhaps rsx11s was planned for the pdt11 series.
On Jan 6, 2013 12:14 PM, "Lee Gleason" <lee.gleason at comcast.net> wrote:
.IF DF L$$SI1
MOVB @(R5)+,-(SP) ;;; COPY CHARACTER FOR WORD MOVE
MOV (SP)+,(R4) ;;; (SAVES 85 USECS ON PDT-11)
.IFF ; DF L$$SI1
MOVB @(R5)+,(R4) ;;; OUTPUT A CHARACTER
.ENDC ; DF L$$SI1
OK, I'll bite. Why is moving a character in the deferred location in
R5 to the stack and then, from the stack to the address in R4 faster
than just going from the deferred R5 location to the R4 address?
--
I'm even more curious what a PDT-11 optimization is doing in an RSX driver...was there at one time an RSX product product planned for the PDT family?
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
