Happy to add information, I ll reply separately, but yes it does run under Windows, Linux/Debian and FreeBSD. Paul Koning is, I think, on this list, so he can tell you about his Python router.
Regards
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens Sent: 08 March 2015 12:47 To: hecnet at Update.UU.SE Subject: Re: [HECnet] DEC Legacy 2015, Windermere UK, April 11/12th is just around the corner!
Hi Rob
Maybe you can add some info on your router at some point in the presentation?
BTW I meant to ask does it work under Windows?
I don't know about the python version - can you give me any more details please?
I've update the Alpha/MIPS section
Thanks, Mark.
On 8 March 2015 at 00:30, Robert Jarratt <robert.jarratt at ntlworld.com> wrote:
Hello Mark,
The programme is looking really amazing, I am so impressed with the work you put into this part. In your talk on HECnet, it would be nice if you mentioned my user mode router, and you may also like to mention Paul Koning s Python version!
Just a small correction to the exhibits. The DECstation and DECsystem I am thinking of bringing are MIPS, not Alpha.
Regards
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens Sent: 07 March 2015 21:54 To: cctalk at classiccmp.org; hecnet at Update.UU.SE; DEC discussion list. Subject: [HECnet] DEC Legacy 2015, Windermere UK, April 11/12th is just around the corner!
Sincere Greetings
This is a quick email to remind you that DEC Legacy 2015 is just around the corner!
I've recently updated the web page with some exciting presentations and demonstrations including the following topics:
VAX MP - Simulating a SMP VAX
Mark Wickens, DEC Legacy Organiser
Unearthing an important historical computer at the computer sheds museum
Jim Austin, The Jim Austin Computer Collection
Video Presentation
Bernd 'vaxman' Ulmann
An Update from the Living Computer Museum
Rich Alderson, Senior System Engineer
The MCPRINT Utility, 30 years in the making
Malcolm Blunden, retired VMS Systems Manager
The Future of VMS
Sue Skonetski, VP of Customer Engagement, VMS Software
Getting the DEC experience on modern hardware
Peter Allan, ex VAX system manager and VMS programmer
HECnet - A worldwide DECnet network
Mark Wickens, DEC Legacy Organiser
... and there will be more yet to come.
We also now have quite an impressive list of exhibits which I expect to continue to grow throughout the next month. Whatever your favourite era of DEC kit you are sure to find something of interest.
The registration page allows registration for a single day or the whole weekend.
Please come, join in and experience the best computing equipment from the best manufacturer!
Kind regards,
Mark Wickens
Event Organiser
p.s. please forward this email to anyone else you think might be interested in attending!
Hi Rob
Maybe you can add some info on your router at some point in the presentation?
BTW I meant to ask does it work under Windows?
I don't know about the python version - can you give me any more details please?
I've update the Alpha/MIPS section
Thanks, Mark.
On 8 March 2015 at 00:30, Robert Jarratt <robert.jarratt at ntlworld.com> wrote:
Hello Mark,
The programme is looking really amazing, I am so impressed with the work you put into this part. In your talk on HECnet, it would be nice if you mentioned my user mode router, and you may also like to mention Paul Koning s Python version!
Just a small correction to the exhibits. The DECstation and DECsystem I am thinking of bringing are MIPS, not Alpha.
Regards
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens Sent: 07 March 2015 21:54 To: cctalk at classiccmp.org; hecnet at Update.UU.SE; DEC discussion list. Subject: [HECnet] DEC Legacy 2015, Windermere UK, April 11/12th is just around the corner!
Sincere Greetings
This is a quick email to remind you that DEC Legacy 2015 is just around the corner!
I've recently updated the web page with some exciting presentations and demonstrations including the following topics:
VAX MP - Simulating a SMP VAX
Mark Wickens, DEC Legacy Organiser
Unearthing an important historical computer at the computer sheds museum
Jim Austin, The Jim Austin Computer Collection
Video Presentation
Bernd 'vaxman' Ulmann
An Update from the Living Computer Museum
Rich Alderson, Senior System Engineer
The MCPRINT Utility, 30 years in the making
Malcolm Blunden, retired VMS Systems Manager
The Future of VMS
Sue Skonetski, VP of Customer Engagement, VMS Software
Getting the DEC experience on modern hardware
Peter Allan, ex VAX system manager and VMS programmer
HECnet - A worldwide DECnet network
Mark Wickens, DEC Legacy Organiser
... and there will be more yet to come.
We also now have quite an impressive list of exhibits which I expect to continue to grow throughout the next month. Whatever your favourite era of DEC kit you are sure to find something of interest.
The registration page allows registration for a single day or the whole weekend.
Please come, join in and experience the best computing equipment from the best manufacturer!
Kind regards,
Mark Wickens
Event Organiser
p.s. please forward this email to anyone else you think might be interested in attending!
DECheads,
Just heard about the UK event, so I thought posting about a VCF East is also a good idea. :)
This year's vintage Computer Festival East is April 17-19 at the InfoAge Science Center in Wall, New Jersey.
The schedule is as follows:
- Friday all day: technical classes.
- Saturday/Sunday morning: keynotes (Wes Clark, Bob Frankston)
- Saturday/Sunday all day after keynotes: exhibit hall, museum tours, consignment/vendors
There's a special PDP-8 presentation Friday at lunchtime, and there's a PDP-8 pavilion in the exhibit hall Saturday and Sunday. The pavilion features 7 of our event's 36 exhibitors. Those 7 are all showing various models of the PDP-8 in honor of its 50th anniversary. David Gesswein, who you all probably know, will exhibit our club's Straight-8. It will go on display in our museum (same venue as where the show is) after the event.
Full details, online ticketing, social media links, etc. are at http://www.vintage.org/2015/east/.
- Evan Koblentz
VCF East producer
Hello Mark,
The programme is looking really amazing, I am so impressed with the work you put into this part. In your talk on HECnet, it would be nice if you mentioned my user mode router, and you may also like to mention Paul Koning s Python version!
Just a small correction to the exhibits. The DECstation and DECsystem I am thinking of bringing are MIPS, not Alpha.
Regards
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens Sent: 07 March 2015 21:54 To: cctalk at classiccmp.org; hecnet at Update.UU.SE; DEC discussion list. Subject: [HECnet] DEC Legacy 2015, Windermere UK, April 11/12th is just around the corner!
Sincere Greetings
This is a quick email to remind you that DEC Legacy 2015 is just around the corner!
I've recently updated the web page with some exciting presentations and demonstrations including the following topics:
VAX MP - Simulating a SMP VAX
Mark Wickens, DEC Legacy Organiser
Unearthing an important historical computer at the computer sheds museum
Jim Austin, The Jim Austin Computer Collection
Video Presentation
Bernd 'vaxman' Ulmann
An Update from the Living Computer Museum
Rich Alderson, Senior System Engineer
The MCPRINT Utility, 30 years in the making
Malcolm Blunden, retired VMS Systems Manager
The Future of VMS
Sue Skonetski, VP of Customer Engagement, VMS Software
Getting the DEC experience on modern hardware
Peter Allan, ex VAX system manager and VMS programmer
HECnet - A worldwide DECnet network
Mark Wickens, DEC Legacy Organiser
... and there will be more yet to come.
We also now have quite an impressive list of exhibits which I expect to continue to grow throughout the next month. Whatever your favourite era of DEC kit you are sure to find something of interest.
The registration page allows registration for a single day or the whole weekend.
Please come, join in and experience the best computing equipment from the best manufacturer!
Kind regards,
Mark Wickens
Event Organiser
p.s. please forward this email to anyone else you think might be interested in attending!
Hello!
Good to know.
However a week later or so from your special event is ours, that's
when VCF East is held at the InfoAge center in Wall Township.
Want to be there Mark?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Sat, Mar 7, 2015 at 4:54 PM, Mark Wickens <mark at wickensonline.co.uk> wrote:
Sincere Greetings
This is a quick email to remind you that DEC Legacy 2015 is just around the
corner!
I've recently updated the web page with some exciting presentations and
demonstrations including the following topics:
VAX MP - Simulating a SMP VAX
Mark Wickens, DEC Legacy Organiser
Unearthing an important historical computer at the computer sheds museum
Jim Austin, The Jim Austin Computer Collection
Video Presentation
Bernd 'vaxman' Ulmann
An Update from the Living Computer Museum
Rich Alderson, Senior System Engineer
The MCPRINT Utility, 30 years in the making
Malcolm Blunden, retired VMS Systems Manager
The Future of VMS
Sue Skonetski, VP of Customer Engagement, VMS Software
Getting the DEC experience on modern hardware
Peter Allan, ex VAX system manager and VMS programmer
HECnet - A worldwide DECnet network
Mark Wickens, DEC Legacy Organiser
... and there will be more yet to come.
We also now have quite an impressive list of exhibits which I expect to
continue to grow throughout the next month. Whatever your favourite era of
DEC kit you are sure to find something of interest.
The registration page allows registration for a single day or the whole
weekend.
Please come, join in and experience the best computing equipment from the
best manufacturer!
Kind regards,
Mark Wickens
Event Organiser
p.s. please forward this email to anyone else you think might be interested
in attending!
Sincere Greetings
This is a quick email to remind you that DEC Legacy 2015 is just around the corner!
I've recently updated the web page with some exciting presentations and demonstrations including the following topics:
VAX MP - Simulating a SMP VAX
Mark Wickens, DEC Legacy Organiser
Unearthing an important historical computer at the computer sheds museum
Jim Austin, The Jim Austin Computer Collection
Video Presentation
Bernd 'vaxman' Ulmann
An Update from the Living Computer Museum
Rich Alderson, Senior System Engineer
The MCPRINT Utility, 30 years in the making
Malcolm Blunden, retired VMS Systems Manager
The Future of VMS
Sue Skonetski, VP of Customer Engagement, VMS Software
Getting the DEC experience on modern hardware
Peter Allan, ex VAX system manager and VMS programmer
HECnet - A worldwide DECnet network
Mark Wickens, DEC Legacy Organiser
... and there will be more yet to come.
We also now have quite an impressive list of exhibits which I expect to continue to grow throughout the next month. Whatever your favourite era of DEC kit you are sure to find something of interest.
The registration page allows registration for a single day or the whole weekend.
Please come, join in and experience the best computing equipment from the best manufacturer!
Kind regards,
Mark Wickens
Event Organiser
p.s. please forward this email to anyone else you think might be interested in attending!
Could it still be, like that manual suggests in section 2.2.1 on page
2-5, that it is indeed "BRUSYS Standalone Copy System and Layered
Product Corrections"?
I don't think so. Sounds more like someone did a backup of a just installed/booted system on tape...
Oh, still haven't had much time to look at Kermit :(
I'm not sure what tape image are you trying to install. Just did a quick test using this one:
http://www.mirrorservice.org/sites/www.bitsavers.org/bits/DEC/pdp11/magtape…
which seems to be the same you are using:
$ ./pdp11
PDP-11 simulator V4.0-0 Beta git commit id: a67afa4a
Disabling XQ
sim> att tq BB-J0830-01.M01_RSX11M+_V4.6_1999.tap
sim> b tq
RSX-11M/RSX-11M-PLUS STANDALONE COPY SYSTEM V4.8
RSX-11M/RSX-11M-PLUS Standalone Configuration and Disk Sizing Program
Valid switches are:
/CSR=nnnnnn to change the default device CSR
/VEC=nnn to change the default device vector
/FOR=n to change the default magtape formatter number
/DEV to list all default device CSR and vectors
Enter first device: /DEV
Device CSR Vector CSR Status
------ ------ ------ ----------
DB 176700 254 Present
DK 177404 220 Present
DL 174400 160 Present
DM 177440 210 Present
DP 176714 300 Present
DR 176300 150 Not Present
DU 172150 154 Present
MM FOR=0 172440 330 Not Present
MS 172522 224 Not Present
MT 160000 320 Not Present
MU 174500 260 Present
Enter first device: MU0:
Enter second device: U\U\FU\UF\DU0:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
RUN BAD
BAD>DU0:
BAD -- DU0: Total bad blocks= 0.
BAD>^Z
Run BRU
BRU>
Simulation stopped, PC: 001344 (CLRB (R1)+)
sim> att tq0 BB-J0830-01.L01_RSX11M+_V4.6_BRU_1999.tap
sim> c
From:
BRU -- *FATAL* -- Syntax error
BRU>/INIT MU0: DU0:
BRU - Starting Tape 1 on MU0:
BRU - End of Tape 1 on MU0:
BRU - Completed
BRU>
Simulation stopped, PC: 001344 (CLRB (R1)+)
sim> b rq
RSX-11M-PLUS V4.6 BL87 1024.KW System:"Baseline"
RED DU:=SY:
RED DU:=LB:
(...)
I have stopped here, but I have got a baseline system that I should be able to SYSGEN.
The SIMH configuration I have used is quite simple:
$ cat pdp11.ini
set cpu 11/70
set cpu 2M
att rq0 RD54.000
set tm disable
Those are MSCP disks and tapes, visibles from RSX as MU: and DU: The emulated tape drive is a TK50, and the disk is a RRD54.
I have been replying-to-sender instead of replying-to-list to some mails in this thread. :(
Inici del missatge reenviat:
Data: 3 de mar de 2015 23:40:47 CET
De: Johnny Billquist <bqt at softjar.se>
Per a: simh at trailing-edge.com
Tema: Re: [Simh] Getting rsxs to run on the pdp11 emulator
On 2015-03-03 23:32, Al Kossow wrote:
the smaller bootable tape is for an rl02
RSXMPRL02
Ah! It's the RSX-11M-PLUS PREGEN system, I suspect.
For people who don't know. The RSX distribution tape holds several savesets.
RSX11MPBL87 is the standard baseline system.
MPBL87SRC holds the sources. (Normally installed during the initial sysgen)
Then comes a bunch of patches to layered products.
Final saveset is RSXMPRL02, which is a pregenned system for RL02. This is especially useful if your system disk is an RL02, as you do not have enough room to run a SYSGEN on that disk, but it also saves some space and speed, since you can basically install that and start using the system without any more work. It can be customized somewhat.
I have no idea what someone have gone to the effort of splitting the distribution tape up the way you people have found things.
Johnny
_______________________________________________
Simh mailing list
Simh at trailing-edge.comhttp://mailman.trailing-edge.com/mailman/listinfo/simh
On Mar 2, 2015, at 10:27 AM, <Paul_Koning at Dell.com> <Paul_Koning at Dell.com> wrote:
On Mar 1, 2015, at 5:50 PM, Hans Vlems <hvlems at zonnet.nl> wrote:
Paul, so if more decnet routers are heard of on the land, what happens with:
A) the list that gets transmitted is truncated, the 32 most recent routers and the transmitting host itself are on it?
B) the locally maintained list, is that also limited to 33 entries?
Almost (A) but not quite. If more than the max routers show up on the Ethernet (whatever that limit is it can be set to less than 33), the excess are dropped first based on router priority, and if it s a tie then by address (higher address wins). See section 9.1.1 in the DNA Routing spec. The adjacency that s rejected as a result is logged event 4.16, with no reason code because the Netman spec forgot to define a specific reason code for this particular case.
And yes, the locally maintained list is also limited. That s critical; distributed routing protocols require that all routers agree on the routing data (after transient differences due to changes propagating have settled out). Otherwise you end up with persistent loops. So the information that s transmitted to other routers and the information used for local computation must be the same.
An analogous issue appears in link state routing (Phase V and other link state protocols derived from it, like OSPF). There, it is necessary for all routers to store the same link state the same map of the area. If some don t have enough memory to do that, some serious magic is required to ensure they are handled specially, since they can t calculate correct routes if they can t store all the inputs. This is why Phase V has special rules for overloaded routers. I remember when that issue was first raised, and the brainstorming that resulted in an attempt to arrive at a solution. The current one is due to Mike Shand, as I recall, and is incredibly simple; before that one, some much more complicated approaches were concocted by other members of the team.
paul
On Mar 1, 2015, at 5:50 PM, Hans Vlems <hvlems at zonnet.nl> wrote:
Paul, so if more decnet routers are heard of on the land, what happens with:
A) the list that gets transmitted is truncated, the 32 most recent routers and the transmitting host itself are on it?
B) the locally maintained list, is that also limited to 33 entries?
Almost (A) but not quite. If more than the max routers show up on the Ethernet (whatever that limit is it can be set to less than 33), the excess are dropped first based on router priority, and if it s a tie then by address (higher address wins). See section 9.1.1 in the DNA Routing spec. The adjacency that s rejected as a result is logged event 4.16, with no reason code because the Netman spec forgot to define a specific reason code for this particular case.
paul
El 01/03/15 a les 23:35, Paul_Koning at Dell.com ha escrit:
Interestingly enough, the DECnet network management architecture spec says the limit is 255. 33 is correct, actually; the reason is that an Ethernet router hello message contains a list of the other routers heard by this router, and the encoding of the packet limits the length of that list to 33 entries. paul
I was afraid the users of Johnny's bridge could be over that limit, since all the connected networks are -from DECNET point of view- part of the same ethernet (all the nodes are adjacent). I have taken a look at the HELLO messages I'm getting and I see just 10 routers, so we are still far away from the absolute limit, but just at the recommended maximum.
Paul, so if more decnet routers are heard of on the land, what happens with:
A) the list that gets transmitted is truncated, the 32 most recent routers and the transmitting host itself are on it?
B) the locally maintained list, is that also limited to 33 entries?
Hans
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Paul_Koning at Dell.com
Verzonden: zondag 1 maart 2015 23:35
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
On Feb 28, 2015, at 3:00 PM, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
...
Use the SET CIRCUIT command with the MAXIMUM ROUTERS parameter to set the maximum number of routers permitted on a particular Ethernet or FDDI circuit. The largest number of routers allowed on a LAN is 33, which is the default value of the MAXIMUM ROUTERS parameter.
Interestingly enough, the DECnet network management architecture spec says the limit is 255. 33 is correct, actually; the reason is that an Ethernet router hello message contains a list of the other routers heard by this router, and the encoding of the packet limits the length of that list to 33 entries.
paul
On Feb 28, 2015, at 3:00 PM, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
...
Use the SET CIRCUIT command with the MAXIMUM ROUTERS parameter to set the maximum number of routers permitted on a particular Ethernet or FDDI circuit. The largest number of routers allowed on a LAN is 33, which is the default value of the MAXIMUM ROUTERS parameter.
Interestingly enough, the DECnet network management architecture spec says the limit is 255. 33 is correct, actually; the reason is that an Ethernet router hello message contains a list of the other routers heard by this router, and the encoding of the packet limits the length of that list to 33 entries.
paul
There are three h4000's.
The first had an elaborated tap, which was a pain to install. The second generation used a simple hand drill. We (fuji) used only Dec gear, no problems. The problems for us started when thin wire repeaters were introduced.
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Clement T. Cole
Verzonden: zondag 1 maart 2015 05:32
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
No - this was pre-thinnet. As I recall Cabletron and interlan were selling repeaters as well as DEC. Johnny's right the h4000 was dec's stringer tap transceiver. 3com had a transceiver where you had to cut the cable (or get it pre-made). Mixing manufacturers could be a crapshoot. Repeaters were needed for long segments in larger buildings and thus we sometimes got forced into using them. The number of hours we spent debugging issues I do not want to think about. I was running the data comm group at Masscomp by then and I pretty sure out field service guys tried really hard to tell people to keep the transceivers to a single brand because we saw so many issues in the field. The h4000 I remember being particularly troublesome.
I have memories of the Masscomp field service guys (who were all ex-DEC) getting a large customer to toss out the h4000 for their Vaxen to solve a number of issues when we trying to make customers talk to our gear. I also recall that The interlan stinger tap was the best of the original stinger taps, although the 3com (cable cut style) worked the best of the early ones and I remember that was the one we recommended for thick-net installations for a long time. A couple of years into it, we did finally find a 3rd party tap that worked really well - but I do not remember the brand. We had a lab with a couple of coils of thick-net in 250 meter segments so we test things. I still have a couple maybe 3 of the strange one we switched too in a box in the basement. Unfortunately, I'm traveling so I can not go downstairs to check the brand. But they were a number years into thick-net so people were finally getting the analog electronics right.
As for repeaters, I have forgotten which one we tested, but I do remember that that it was one of the dec repeaters worked significantly better than any others; but we generally suggested to not use repeaters but instead multi-home a couple of systems and route as needed. Even with all of routers issues, it worked better than big segments.
I used to have one old dec repeater in my cache but I'm pretty sure it finally went to the electronics recycler about 3 years ago since I was not using at at home and never going too and my wife was working on getting me to purge excess stuff. I felt it, a couple of old pc's, some Mac-2, and the like that had been powered up in over 10 years had reached there end of life and had no value to anyone more.
Clem
Sent from my iPad
On Feb 28, 2015, at 7:57 PM, Johnny Billquist <bqt at softjar.se> wrote:
I might be totally confused now, but I have a strong recollection that the H4000 is a tickwire transciever, and if so, I can't make sense of a sentence that talks about it in the context of thinwire ethernet.
Johnny
On 2015-03-01 00:13, Hans Vlems wrote:
That is probably a story when the first thin wire repeaters were introduced. The h4000-aa wouldn't play nice when connected to a dempr or despr. The h4000-ba fixed that, or you could cut a capacitor (?) on the -aa and save money. A transceiver was 1200 guilders at the time.
Dec's thick wire repeaters (derep-ab and -rd) worked for me. One is still in use today...
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Clement T. Cole
Verzonden: zaterdag 28 februari 2015 23:00
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
Right. And many of the repeaters tended to not work well.
DEC had wholes name I forget - that was pretty much the only one that worked reliably. I have bad memories of repeater created issues where host A one seg1 just would not talk to host b on seg2 but c & d could talk to both and each other
Sent from my iPad
On Feb 28, 2015, at 2:28 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-02-28 21:21, Hans Vlems wrote:
Yeah of course you can have more than one L2 router in an area, didn't think of it :)
:-)
About the 10base5 segment, that was limited in length to 500 meters. Transceivers must be at least 2.5 meters apart, hence the 200 nodes. This was before a DELNI was invented. If my failing memory doesn't fail me that 200 node limit remained the same with Delni's.
But you were allowed to bridge several segments (using repeaters). I think the maximum distance, including hops, between any two nodes had to be within 1000m, but you could also do stars... You were not allowed to have more than two repeaters I also seem to remember.
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Johnny Billquist
Verzonden: zaterdag 28 februari 2015 20:55
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
On 2015-02-28 20:51, Hans Vlems wrote:
64:-)?
You can definitely have more than one L2 router per area... :-)
I don't know for sure, as you probably have guessed...
There is an ncp executor parameter called maximum broadcast routers, default value 32 iirc.
Is there an architectural limit, depends on what you mean by ethernet segment. A 10base5 segment was limited to 200 nodes. 64 L2 routers might put a hefty broadcast load on it. On an extended ethernet LAN there is likely no technical limit.
Really? I have some vague memory of some limit of an ethernet segment,
but I can't recall any details now. Why 200?
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jordi Guillaumes i Pons
Verzonden: zaterdag 28 februari 2015 20:37
Aan: HECnet Mailing List
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Maximum number of L2 routers?
Hello, list,
I'm trying to remember what is the maximum number of area routers allowed in a DECNET Phase IV ethernet segment. Anyone of you have that information at hand?
On other news, the old macbook I was using as home server has died, after years of service beyond the call of duty. I'm setting up my stuff using several smallish ARM computers. To be specific, now I'm running a cubietruck and and Odroid-C1 (and a raspberry Pi as router/firewall). I'm having trouble with the net connectivity, so some yo-yo disconnects from area 7 should be expected. Not so hard as last sunday, but I'm still doing quite a lot of reboots.
BTW, the SG1 multinet link seems to be down again (unless it is a problem in my side, which is completely possible).
--
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
Thin wire repeaters had an AUI port too. That way they could connect to existing backbones. With h4000's
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Johnny Billquist
Verzonden: zondag 1 maart 2015 02:56
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
I might be totally confused now, but I have a strong recollection that
the H4000 is a tickwire transciever, and if so, I can't make sense of a
sentence that talks about it in the context of thinwire ethernet.
Johnny
On 2015-03-01 00:13, Hans Vlems wrote:
That is probably a story when the first thin wire repeaters were introduced. The h4000-aa wouldn't play nice when connected to a dempr or despr. The h4000-ba fixed that, or you could cut a capacitor (?) on the -aa and save money. A transceiver was 1200 guilders at the time.
Dec's thick wire repeaters (derep-ab and -rd) worked for me. One is still in use today...
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Clement T. Cole
Verzonden: zaterdag 28 februari 2015 23:00
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
Right. And many of the repeaters tended to not work well.
DEC had wholes name I forget - that was pretty much the only one that worked reliably. I have bad memories of repeater created issues where host A one seg1 just would not talk to host b on seg2 but c & d could talk to both and each other
Sent from my iPad
On Feb 28, 2015, at 2:28 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-02-28 21:21, Hans Vlems wrote:
Yeah of course you can have more than one L2 router in an area, didn't think of it :)
:-)
About the 10base5 segment, that was limited in length to 500 meters. Transceivers must be at least 2.5 meters apart, hence the 200 nodes. This was before a DELNI was invented. If my failing memory doesn't fail me that 200 node limit remained the same with Delni's.
But you were allowed to bridge several segments (using repeaters). I think the maximum distance, including hops, between any two nodes had to be within 1000m, but you could also do stars... You were not allowed to have more than two repeaters I also seem to remember.
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Johnny Billquist
Verzonden: zaterdag 28 februari 2015 20:55
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
On 2015-02-28 20:51, Hans Vlems wrote:
64:-)?
You can definitely have more than one L2 router per area... :-)
I don't know for sure, as you probably have guessed...
There is an ncp executor parameter called maximum broadcast routers, default value 32 iirc.
Is there an architectural limit, depends on what you mean by ethernet segment. A 10base5 segment was limited to 200 nodes. 64 L2 routers might put a hefty broadcast load on it. On an extended ethernet LAN there is likely no technical limit.
Really? I have some vague memory of some limit of an ethernet segment,
but I can't recall any details now. Why 200?
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jordi Guillaumes i Pons
Verzonden: zaterdag 28 februari 2015 20:37
Aan: HECnet Mailing List
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Maximum number of L2 routers?
Hello, list,
I'm trying to remember what is the maximum number of area routers allowed in a DECNET Phase IV ethernet segment. Anyone of you have that information at hand?
On other news, the old macbook I was using as home server has died, after years of service beyond the call of duty. I'm setting up my stuff using several smallish ARM computers. To be specific, now I'm running a cubietruck and and Odroid-C1 (and a raspberry Pi as router/firewall). I'm having trouble with the net connectivity, so some yo-yo disconnects from area 7 should be expected. Not so hard as last sunday, but I'm still doing quite a lot of reboots.
BTW, the SG1 multinet link seems to be down again (unless it is a problem in my side, which is completely possible).
--
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
No - this was pre-thinnet. As I recall Cabletron and interlan were selling repeaters as well as DEC. Johnny's right the h4000 was dec's stringer tap transceiver. 3com had a transceiver where you had to cut the cable (or get it pre-made). Mixing manufacturers could be a crapshoot. Repeaters were needed for long segments in larger buildings and thus we sometimes got forced into using them. The number of hours we spent debugging issues I do not want to think about. I was running the data comm group at Masscomp by then and I pretty sure out field service guys tried really hard to tell people to keep the transceivers to a single brand because we saw so many issues in the field. The h4000 I remember being particularly troublesome.
I have memories of the Masscomp field service guys (who were all ex-DEC) getting a large customer to toss out the h4000 for their Vaxen to solve a number of issues when we trying to make customers talk to our gear. I also recall that The interlan stinger tap was the best of the original stinger taps, although the 3com (cable cut style) worked the best of the early ones and I remember that was the one we recommended for thick-net installations for a long time. A couple of years into it, we did finally find a 3rd party tap that worked really well - but I do not remember the brand. We had a lab with a couple of coils of thick-net in 250 meter segments so we test things. I still have a couple maybe 3 of the strange one we switched too in a box in the basement. Unfortunately, I'm traveling so I can not go downstairs to check the brand. But they were a number years into thick-net so people were finally getting the analog electronics right.
As for repeaters, I have forgotten which one we tested, but I do remember that that it was one of the dec repeaters worked significantly better than any others; but we generally suggested to not use repeaters but instead multi-home a couple of systems and route as needed. Even with all of routers issues, it worked better than big segments.
I used to have one old dec repeater in my cache but I'm pretty sure it finally went to the electronics recycler about 3 years ago since I was not using at at home and never going too and my wife was working on getting me to purge excess stuff. I felt it, a couple of old pc's, some Mac-2, and the like that had been powered up in over 10 years had reached there end of life and had no value to anyone more.
Clem
Sent from my iPad
On Feb 28, 2015, at 7:57 PM, Johnny Billquist <bqt at softjar.se> wrote:
I might be totally confused now, but I have a strong recollection that the H4000 is a tickwire transciever, and if so, I can't make sense of a sentence that talks about it in the context of thinwire ethernet.
Johnny
On 2015-03-01 00:13, Hans Vlems wrote:
That is probably a story when the first thin wire repeaters were introduced. The h4000-aa wouldn't play nice when connected to a dempr or despr. The h4000-ba fixed that, or you could cut a capacitor (?) on the -aa and save money. A transceiver was 1200 guilders at the time.
Dec's thick wire repeaters (derep-ab and -rd) worked for me. One is still in use today...
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Clement T. Cole
Verzonden: zaterdag 28 februari 2015 23:00
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
Right. And many of the repeaters tended to not work well.
DEC had wholes name I forget - that was pretty much the only one that worked reliably. I have bad memories of repeater created issues where host A one seg1 just would not talk to host b on seg2 but c & d could talk to both and each other
Sent from my iPad
On Feb 28, 2015, at 2:28 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-02-28 21:21, Hans Vlems wrote:
Yeah of course you can have more than one L2 router in an area, didn't think of it :)
:-)
About the 10base5 segment, that was limited in length to 500 meters. Transceivers must be at least 2.5 meters apart, hence the 200 nodes. This was before a DELNI was invented. If my failing memory doesn't fail me that 200 node limit remained the same with Delni's.
But you were allowed to bridge several segments (using repeaters). I think the maximum distance, including hops, between any two nodes had to be within 1000m, but you could also do stars... You were not allowed to have more than two repeaters I also seem to remember.
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Johnny Billquist
Verzonden: zaterdag 28 februari 2015 20:55
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
On 2015-02-28 20:51, Hans Vlems wrote:
64:-)?
You can definitely have more than one L2 router per area... :-)
I don't know for sure, as you probably have guessed...
There is an ncp executor parameter called maximum broadcast routers, default value 32 iirc.
Is there an architectural limit, depends on what you mean by ethernet segment. A 10base5 segment was limited to 200 nodes. 64 L2 routers might put a hefty broadcast load on it. On an extended ethernet LAN there is likely no technical limit.
Really? I have some vague memory of some limit of an ethernet segment,
but I can't recall any details now. Why 200?
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jordi Guillaumes i Pons
Verzonden: zaterdag 28 februari 2015 20:37
Aan: HECnet Mailing List
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Maximum number of L2 routers?
Hello, list,
I'm trying to remember what is the maximum number of area routers allowed in a DECNET Phase IV ethernet segment. Anyone of you have that information at hand?
On other news, the old macbook I was using as home server has died, after years of service beyond the call of duty. I'm setting up my stuff using several smallish ARM computers. To be specific, now I'm running a cubietruck and and Odroid-C1 (and a raspberry Pi as router/firewall). I'm having trouble with the net connectivity, so some yo-yo disconnects from area 7 should be expected. Not so hard as last sunday, but I'm still doing quite a lot of reboots.
BTW, the SG1 multinet link seems to be down again (unless it is a problem in my side, which is completely possible).
--
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
Right
Sent from my iPad
On Feb 28, 2015, at 7:54 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-02-28 23:13, Clement T. Cole wrote:
I should have added when Stan and I wrote the original IP/TCP for VMS @ Tektronix did not have routing in it (nor mail support). We gave to CMU who enhanced it and I assume added routing. DEC did not support an IP stack until much later - Johnny probably remembers when it became available. I had stopped having to hacking on VMS when I left Tektronix in '81.
I don't know, actually.
However, it should be pointed out that routing is not the same as bridging...
Johnny
Sent from my iPad
On Feb 28, 2015, at 3:24 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Sat, 28 Feb 2015, Johnny Billquist wrote:
Not sure what you mean with a star configuration. The first (proprietary) glass fiber repeaters were star designs, was that what you meant?
Not all ethernet segments have to be in one line. But since the maximum number of repeaters between any two nodes were two, you could (obviously) have repeaters in configurations that just made sure not more than two were involved in any given path, but there could be more than two totally.
The simplest such configuration would be a star.
How are you doing more than one line without bridges or repeaters? Have I misread?
(Not counting routing)
But my memory is fuzzy enough at this point that I should probably go read the docs instead of continuing to ramble here...
DEC also sold remote bridges and repeaters. A glass fiber trunc connected either two remote repeaters or bridges or one of each. I forgot how long a fiber segment could be, 2500 m IIRC. That gave you some room to plan on a large site. Two remote repeaters counted as one in the two repeater rule.
Expensive stuff though. A Lanbridge 100 was 30.000 guilders in 1988. A remote bridge was even more expensive.
Yeah.
But the ethernet was older than those devices. If my memory serves me right, the original repeater (from DEC) was the DEREP. Probably even more expensive back in the day. :-) And there were no bridges back then.
Hmmmm, when did VMS/BSD get software bridging capabilities?
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
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
I might be totally confused now, but I have a strong recollection that the H4000 is a tickwire transciever, and if so, I can't make sense of a sentence that talks about it in the context of thinwire ethernet.
Johnny
On 2015-03-01 00:13, Hans Vlems wrote:
That is probably a story when the first thin wire repeaters were introduced. The h4000-aa wouldn't play nice when connected to a dempr or despr. The h4000-ba fixed that, or you could cut a capacitor (?) on the -aa and save money. A transceiver was 1200 guilders at the time.
Dec's thick wire repeaters (derep-ab and -rd) worked for me. One is still in use today...
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Clement T. Cole
Verzonden: zaterdag 28 februari 2015 23:00
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
Right. And many of the repeaters tended to not work well.
DEC had wholes name I forget - that was pretty much the only one that worked reliably. I have bad memories of repeater created issues where host A one seg1 just would not talk to host b on seg2 but c & d could talk to both and each other
Sent from my iPad
On Feb 28, 2015, at 2:28 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-02-28 21:21, Hans Vlems wrote:
Yeah of course you can have more than one L2 router in an area, didn't think of it :)
:-)
About the 10base5 segment, that was limited in length to 500 meters. Transceivers must be at least 2.5 meters apart, hence the 200 nodes. This was before a DELNI was invented. If my failing memory doesn't fail me that 200 node limit remained the same with Delni's.
But you were allowed to bridge several segments (using repeaters). I think the maximum distance, including hops, between any two nodes had to be within 1000m, but you could also do stars... You were not allowed to have more than two repeaters I also seem to remember.
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Johnny Billquist
Verzonden: zaterdag 28 februari 2015 20:55
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
On 2015-02-28 20:51, Hans Vlems wrote:
64:-)?
You can definitely have more than one L2 router per area... :-)
I don't know for sure, as you probably have guessed...
There is an ncp executor parameter called maximum broadcast routers, default value 32 iirc.
Is there an architectural limit, depends on what you mean by ethernet segment. A 10base5 segment was limited to 200 nodes. 64 L2 routers might put a hefty broadcast load on it. On an extended ethernet LAN there is likely no technical limit.
Really? I have some vague memory of some limit of an ethernet segment,
but I can't recall any details now. Why 200?
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jordi Guillaumes i Pons
Verzonden: zaterdag 28 februari 2015 20:37
Aan: HECnet Mailing List
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Maximum number of L2 routers?
Hello, list,
I'm trying to remember what is the maximum number of area routers allowed in a DECNET Phase IV ethernet segment. Anyone of you have that information at hand?
On other news, the old macbook I was using as home server has died, after years of service beyond the call of duty. I'm setting up my stuff using several smallish ARM computers. To be specific, now I'm running a cubietruck and and Odroid-C1 (and a raspberry Pi as router/firewall). I'm having trouble with the net connectivity, so some yo-yo disconnects from area 7 should be expected. Not so hard as last sunday, but I'm still doing quite a lot of reboots.
BTW, the SG1 multinet link seems to be down again (unless it is a problem in my side, which is completely possible).
--
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 2015-02-28 23:13, Clement T. Cole wrote:
I should have added when Stan and I wrote the original IP/TCP for VMS @ Tektronix did not have routing in it (nor mail support). We gave to CMU who enhanced it and I assume added routing. DEC did not support an IP stack until much later - Johnny probably remembers when it became available. I had stopped having to hacking on VMS when I left Tektronix in '81.
I don't know, actually.
However, it should be pointed out that routing is not the same as bridging...
Johnny
Sent from my iPad
On Feb 28, 2015, at 3:24 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Sat, 28 Feb 2015, Johnny Billquist wrote:
Not sure what you mean with a star configuration. The first (proprietary) glass fiber repeaters were star designs, was that what you meant?
Not all ethernet segments have to be in one line. But since the maximum number of repeaters between any two nodes were two, you could (obviously) have repeaters in configurations that just made sure not more than two were involved in any given path, but there could be more than two totally.
The simplest such configuration would be a star.
How are you doing more than one line without bridges or repeaters? Have I misread?
(Not counting routing)
But my memory is fuzzy enough at this point that I should probably go read the docs instead of continuing to ramble here...
DEC also sold remote bridges and repeaters. A glass fiber trunc connected either two remote repeaters or bridges or one of each. I forgot how long a fiber segment could be, 2500 m IIRC. That gave you some room to plan on a large site. Two remote repeaters counted as one in the two repeater rule.
Expensive stuff though. A Lanbridge 100 was 30.000 guilders in 1988. A remote bridge was even more expensive.
Yeah.
But the ethernet was older than those devices. If my memory serves me right, the original repeater (from DEC) was the DEREP. Probably even more expensive back in the day. :-) And there were no bridges back then.
Hmmmm, when did VMS/BSD get software bridging capabilities?
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
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
That is probably a story when the first thin wire repeaters were introduced. The h4000-aa wouldn't play nice when connected to a dempr or despr. The h4000-ba fixed that, or you could cut a capacitor (?) on the -aa and save money. A transceiver was 1200 guilders at the time.
Dec's thick wire repeaters (derep-ab and -rd) worked for me. One is still in use today...
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Clement T. Cole
Verzonden: zaterdag 28 februari 2015 23:00
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
Right. And many of the repeaters tended to not work well.
DEC had wholes name I forget - that was pretty much the only one that worked reliably. I have bad memories of repeater created issues where host A one seg1 just would not talk to host b on seg2 but c & d could talk to both and each other
Sent from my iPad
On Feb 28, 2015, at 2:28 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-02-28 21:21, Hans Vlems wrote:
Yeah of course you can have more than one L2 router in an area, didn't think of it :)
:-)
About the 10base5 segment, that was limited in length to 500 meters. Transceivers must be at least 2.5 meters apart, hence the 200 nodes. This was before a DELNI was invented. If my failing memory doesn't fail me that 200 node limit remained the same with Delni's.
But you were allowed to bridge several segments (using repeaters). I think the maximum distance, including hops, between any two nodes had to be within 1000m, but you could also do stars... You were not allowed to have more than two repeaters I also seem to remember.
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Johnny Billquist
Verzonden: zaterdag 28 februari 2015 20:55
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Maximum number of L2 routers?
On 2015-02-28 20:51, Hans Vlems wrote:
64:-)?
You can definitely have more than one L2 router per area... :-)
I don't know for sure, as you probably have guessed...
There is an ncp executor parameter called maximum broadcast routers, default value 32 iirc.
Is there an architectural limit, depends on what you mean by ethernet segment. A 10base5 segment was limited to 200 nodes. 64 L2 routers might put a hefty broadcast load on it. On an extended ethernet LAN there is likely no technical limit.
Really? I have some vague memory of some limit of an ethernet segment,
but I can't recall any details now. Why 200?
Johnny
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jordi Guillaumes i Pons
Verzonden: zaterdag 28 februari 2015 20:37
Aan: HECnet Mailing List
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Maximum number of L2 routers?
Hello, list,
I'm trying to remember what is the maximum number of area routers allowed in a DECNET Phase IV ethernet segment. Anyone of you have that information at hand?
On other news, the old macbook I was using as home server has died, after years of service beyond the call of duty. I'm setting up my stuff using several smallish ARM computers. To be specific, now I'm running a cubietruck and and Odroid-C1 (and a raspberry Pi as router/firewall). I'm having trouble with the net connectivity, so some yo-yo disconnects from area 7 should be expected. Not so hard as last sunday, but I'm still doing quite a lot of reboots.
BTW, the SG1 multinet link seems to be down again (unless it is a problem in my side, which is completely possible).
--
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 Sat, 28 Feb 2015, Robert Jarratt wrote:
It might be worth just checking that it isn't the disk that is the problem.
Does the power keep cycling with the disk removed? What about if you put a
different disk in?
I've had the main drive spin down before randomly and several other issues indicating a PSU issue.
Regards
Rob
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
It might be worth just checking that it isn't the disk that is the problem.
Does the power keep cycling with the disk removed? What about if you put a
different disk in?
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Cory Smelosky
Sent: 28 February 2015 21:41
To: dectec at dectec.info
Cc: hecnet at Update.UU.SE
Subject: [HECnet] VAXStation 4000/60 PSU info
Afternoon all,
Anyone have schematics for the 4000/60 PSU? Mine's acting funny again.
THinking I should probably just recap it.
Harddrive kept spinning down, then back up...then right back down.
Powered the entire thing off, attempted to turn back on to no avail. Let
sit for
several minutes and it powered right back up. Drive seems to remain
spinning
now.
Any other specific components I should test and replace while in there for
the
recap?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
I should have added when Stan and I wrote the original IP/TCP for VMS @ Tektronix did not have routing in it (nor mail support). We gave to CMU who enhanced it and I assume added routing. DEC did not support an IP stack until much later - Johnny probably remembers when it became available. I had stopped having to hacking on VMS when I left Tektronix in '81.
Sent from my iPad
On Feb 28, 2015, at 3:24 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Sat, 28 Feb 2015, Johnny Billquist wrote:
Not sure what you mean with a star configuration. The first (proprietary) glass fiber repeaters were star designs, was that what you meant?
Not all ethernet segments have to be in one line. But since the maximum number of repeaters between any two nodes were two, you could (obviously) have repeaters in configurations that just made sure not more than two were involved in any given path, but there could be more than two totally.
The simplest such configuration would be a star.
How are you doing more than one line without bridges or repeaters? Have I misread?
(Not counting routing)
But my memory is fuzzy enough at this point that I should probably go read the docs instead of continuing to ramble here...
DEC also sold remote bridges and repeaters. A glass fiber trunc connected either two remote repeaters or bridges or one of each. I forgot how long a fiber segment could be, 2500 m IIRC. That gave you some room to plan on a large site. Two remote repeaters counted as one in the two repeater rule.
Expensive stuff though. A Lanbridge 100 was 30.000 guilders in 1988. A remote bridge was even more expensive.
Yeah.
But the ethernet was older than those devices. If my memory serves me right, the original repeater (from DEC) was the DEREP. Probably even more expensive back in the day. :-) And there were no bridges back then.
Hmmmm, when did VMS/BSD get software bridging capabilities?
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Unix certainly could bridge and route with 4.1a after Sam wrote the routed stuff which he will tell you was ripped off from a Xerox routing protocol. My memory is hazy here. I think he started that work with BBN stack which a couple of us ran on 4.1 before joy created sockets. I have memories of debugging that with Eric cooper and Sam because they were in Evans and I ran the link in Cory in the CAD group at the time as one of our 3 780s was on both the Cory LAN and the other end of a link to Evans [3meg Ethernet not even 3com or interlan he in those days]. My memory is that the other end of that Evans link was the system KIM which was on the Evans internal LAN and the link between the buildings.
Sent from my iPad
On Feb 28, 2015, at 3:24 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Sat, 28 Feb 2015, Johnny Billquist wrote:
Not sure what you mean with a star configuration. The first (proprietary) glass fiber repeaters were star designs, was that what you meant?
Not all ethernet segments have to be in one line. But since the maximum number of repeaters between any two nodes were two, you could (obviously) have repeaters in configurations that just made sure not more than two were involved in any given path, but there could be more than two totally.
The simplest such configuration would be a star.
How are you doing more than one line without bridges or repeaters? Have I misread?
(Not counting routing)
But my memory is fuzzy enough at this point that I should probably go read the docs instead of continuing to ramble here...
DEC also sold remote bridges and repeaters. A glass fiber trunc connected either two remote repeaters or bridges or one of each. I forgot how long a fiber segment could be, 2500 m IIRC. That gave you some room to plan on a large site. Two remote repeaters counted as one in the two repeater rule.
Expensive stuff though. A Lanbridge 100 was 30.000 guilders in 1988. A remote bridge was even more expensive.
Yeah.
But the ethernet was older than those devices. If my memory serves me right, the original repeater (from DEC) was the DEREP. Probably even more expensive back in the day. :-) And there were no bridges back then.
Hmmmm, when did VMS/BSD get software bridging capabilities?
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects