HECnet

hecnet@lists.dfupdate.se

6 participants
15595 discussions

by gregg.drwho8＠gmail.com

On Sat, Feb 9, 2013 at 5:11 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 02/09/2013 04:31 PM, Jordi Guillaumes i Pons wrote: El 09/02/2013, a les 7:44, Dave McGuire <mcguire at neurotica.com> va escriure: I bought *new* ones from Mouser as recently as two years ago. I've heard nothing about any of them being discontinued. Right now if you search for DS1287A in their web you get nothing. Well then that one may have been discontinued. I bet there are still quite a few of them around, though. (one can readily buy brand new 7400-series TTL, for example...and I'm not talking 74LS! -Dave -- Dave McGuire, AK4HZ New Kensington, PA Hello! I agree to the TTL one. And its slowly driving some of my contemporaries crazy by the amount I recall concerning TTL logic. Now Dave stop feeding those ewoks they are expected home within the day. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

13 years, 1 month

VS4000/90: Up and running!

by clemc＠ccc.com

Yup. sorry if you thought i was suggesting that it was 100% compatible, as you point out its not and i was mot trying to imply that. since you are performing surgery on the board, my point is there is a chance you can make it work electrically since in this case the chip is supposed to be software compatible ie since ds1287a are not to be found the 1687 might be able to be pressed into service. On Feb 9, 2013, at 5:58 PM, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote: El 09/02/2013, a les 23:49, Clem Cole <clemc at ccc.com> va escriure: eeds to check any timing differences and the name of the RW/WR pin is different - but they >>might<< work the same way (might also need to be inverted). In the 1287 that pin is named R/W when the chip uses motorola style timing (MOT connected to Vcc) and WR when it uses intel style (MOT connected to GND). Check the DC1287A datasheet for the gory details. Now the MOT pin is not there in the 1267 (it is used to signal a "wake up" condition), so it doesn't look to be completely compatible with the 1287. Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES

13 years, 1 month

DFS kit for VAX-VMS 7.3

by b4＠gewt.net

On 9 Feb 2013, at 21:11, Cory Smelosky <b4 at gewt.net> wrote: On 9 Feb 2013, at 13:57, "Steve Davidson" <jeep at scshome.net> wrote: -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Saturday, February 09, 2013 13:53 To: hecnet at Update.UU.SE Subject: Re: [HECnet] DFS kit for VAX-VMS 7.3 On 9 Feb 2013, at 13:51, "Steve Davidson" <jeep at scshome.net> wrote: -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Saturday, February 09, 2013 13:49 To: hecnet at Update.UU.SE Subject: Re: [HECnet] DFS kit for VAX-VMS 7.3 On 9 Feb 2013, at 13:47, "Steve Davidson" <jeep at scshome.net> wrote: Does anyone have a DFS kit for VAX-VMS 7.3? Thanks! I think I found it in the layered products disc I was looking through -Steve -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. If you can copy it to your default DECnet directory I can pick it up from there. -Steve GEWT::B4$ dir Directory DUA2:[000000.DECDFS_0231] DOCUMENTATION.DIR;1 KIT.DIR;1 Total of 2 files. I'll copy DECDFS_0231.DIR over. It'll be on GEWT:: -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. And if you have it... DQS for VAX-VMS 7.3. Thanks! GEWT:: is back up my states table got a bit cluttered and the GRE tunnels got borked. I'll go see if I have DQS ad copy it over. Looks like I don't have DQS at the moment. I'll need to go grab the layered products CD from the FTP site. -Steve -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.

13 years, 1 month

DFS kit for VAX-VMS 7.3

by b4＠gewt.net

On 9 Feb 2013, at 13:57, "Steve Davidson" <jeep at scshome.net> wrote: -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Saturday, February 09, 2013 13:53 To: hecnet at Update.UU.SE Subject: Re: [HECnet] DFS kit for VAX-VMS 7.3 On 9 Feb 2013, at 13:51, "Steve Davidson" <jeep at scshome.net> wrote: -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Saturday, February 09, 2013 13:49 To: hecnet at Update.UU.SE Subject: Re: [HECnet] DFS kit for VAX-VMS 7.3 On 9 Feb 2013, at 13:47, "Steve Davidson" <jeep at scshome.net> wrote: Does anyone have a DFS kit for VAX-VMS 7.3? Thanks! I think I found it in the layered products disc I was looking through -Steve -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. If you can copy it to your default DECnet directory I can pick it up from there. -Steve GEWT::B4$ dir Directory DUA2:[000000.DECDFS_0231] DOCUMENTATION.DIR;1 KIT.DIR;1 Total of 2 files. I'll copy DECDFS_0231.DIR over. It'll be on GEWT:: -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. And if you have it... DQS for VAX-VMS 7.3. Thanks! GEWT:: is back up my states table got a bit cluttered and the GRE tunnels got borked. I'll go see if I have DQS ad copy it over. -Steve -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.

13 years, 1 month

Mulita issue

by dibi58＠gmail.com

i had a problem with mine stuck in arc console, another based on the noname, same thing, for whatever reason all the arc failed around the same time, but i care less of running windoze our days take the power cable off and on the motherboard, or the ram out and in, afterwards it should come up in srm on the serial console, after that set console graphic and it should go back to usual, but don't try to go to arc or it will do the same thing again, if the problem is the same as mine i find the arc thing suspicious because it happened at the same time on a miata, a noname and a multia, probably a calendar bug ? i have not tried to flash the firmware, no time, but from srm everything works, as said except windoze cheers, daniel ;-) On 2/9/13, Michael Holmes <mholmes10 at hotmail.com> wrote: Forgive me if this is off topic, but I was reading about the fixes to the VAXStation 4000 regarding chips. I bought a multia several years back and I think it sucommed to being moved to and from Germany and the States too many times. I had it booting as a satelite off a DEC 3000 just fine, until this last move. I thought the battery had died and replaced it. (dead battery prevents the bios from coming up) I get the SRM console and i'd get MOP load message on the DEC 3000 but the MULTIA just hangs after message about bootstrapping. I heard something about an I/O chip that can go bad on the MB and was wondering if anyone had any ideas that could be used to fix the MULTIA. thanks Mike

13 years, 1 month

Easiest way to do 'sed' type search and replace on VMS...

by bqt＠softjar.se

On 2013-02-10 00:20, mike young wrote: Ahhhhh, TECO, first editor I ever used, some 35 years ago. Far and away the most powerful, too. A few mistyped characters can wreak such havoc! Thanks, Johnny, for the memories. You are welcome. I still find it surprisingly easy and efficient to do some types of editing in TECO, compared to anything else. I guess the closes for other people nowadays are sed, awk, perl, and similar tools. But they are all just doing parts of the work, so you often see people use several of them, and they are so heavyweight compared to TECO. But yes, you need to keep your letters in order, or things quickly get out of hand. :-) TECO have been referred to as a write-only language. I can sortof understand that one... ;-) Writing something like EMACS in TECO, however, is rather trivial. Johnny --Mike On 2/9/2013 11:54 AM, Johnny Billquist wrote: On 2013-02-09 15:23, G. wrote: On Sat, 09 Feb 2013 02:21:21 +0100, you wrote: <fs($(<a href="hecnetinfo.com?q=$;.UAS)$-CQA,.XAI">$GAI</a>$>EX$$ Clear as a spring rain. Let me know if you want me to explain it... ;-) Yes please, do! :) Like I said, clear as spring rain... Ok, here we go. Written somewhat more "structured": Anything between exclamation points are comments in TECO (well, technically, they are labels, but what is really the difference between a label and a comment anyway... :-) < ! Start of loop ! FS($(<a href="hecnetinfo.com?q=$; ! Search for ( and replace it with all that other crap. The trailing ; after the second escape means that if the search and replace fails we'll exit the loop ! .UA ! Save current position in Q-register A ! S)$ ! Search for ) ! -C ! Backup one char ! QA,.XA ! Copy text between position in Q-register A and current position into Q-register A ! I">$ ! Insert the text "> ! GA ! Insert the text from Q-register A ! I</a>$ ! Insert </a> ! > ! End of loop ! EX$$ ! Exit ! Now, the good tricks to know: In TECO you have Q-registers. Think of them as variables that can store a number and a string (at the same time). TECO always have a current position in the buffer. That is denoted by ".". Functions takes arguments. So, a thing like the search and replace is FSstr1$str2$, which searches for str1, and if found, replaces it with str2. So the first like is just searching for the next opening paren, and inserts a lot of cruft after the paren. Just plain text constant. At this point, the current position is just before the nodename. So, we store the position where the nodename starts. (.UA). The command is actually nUq, where n is any number. We just use "." as the number, which is the current position. q is what Q-register to store the value in. So, .UA stores the current position in Q-register A. S)$ should be very obvious. Just search for the closing paren. -C should also be pretty obvious. nC moves the position that many steps. If no argument is given, it defaults to 1. -C is just short for -1C. QA,.XA looks much worse than it is. The basic command is actually m,nXq, which stores the text between m and n in Q-register q. The the XA part should be obvious. Store the text in Q-register A. The stuff before the command is QA,. . At this point, you should realize that n in this case is ".", or the current position. QA is the function to read out the value from Q-register A (Qq to say the function in a general way). So we'll copy the text from the start of the nodename (stored in Q-register A) to the current position, which is right before the right paren, to Q-register A. That is, Q-register A will then hold the nodename. Also, at this point, the current point is after the nodename. So, we now want to finish the <a href= tag, so we insert a little more text: I">$, which does just that. Position is still right before the right paren, but now we have a full <a> tag in the buffer. GA gets the text from Q-register A, and inserts it into the buffer. That is the nodename again, now for displaying. I</a>$ then inserts a little more text, finishing the tagged text. > is the end of the loop. EX$$ exits. See. TECO is actually pretty easy. :-) 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

13 years, 1 month

Easiest way to do 'sed' type search and replace on VMS...

by young＠ecn.purdue.edu

Ahhhhh, TECO, first editor I ever used, some 35 years ago. Far and away the most powerful, too. A few mistyped characters can wreak such havoc! Thanks, Johnny, for the memories. --Mike On 2/9/2013 11:54 AM, Johnny Billquist wrote: On 2013-02-09 15:23, G. wrote: On Sat, 09 Feb 2013 02:21:21 +0100, you wrote: <fs($(<a href="hecnetinfo.com?q=$;.UAS)$-CQA,.XAI">$GAI</a>$>EX$$ Clear as a spring rain. Let me know if you want me to explain it... ;-) Yes please, do! :) Like I said, clear as spring rain... Ok, here we go. Written somewhat more "structured": Anything between exclamation points are comments in TECO (well, technically, they are labels, but what is really the difference between a label and a comment anyway... :-) < ! Start of loop ! FS($(<a href="hecnetinfo.com?q=$; ! Search for ( and replace it with all that other crap. The trailing ; after the second escape means that if the search and replace fails we'll exit the loop ! .UA ! Save current position in Q-register A ! S)$ ! Search for ) ! -C ! Backup one char ! QA,.XA ! Copy text between position in Q-register A and current position into Q-register A ! I">$ ! Insert the text "> ! GA ! Insert the text from Q-register A ! I</a>$ ! Insert </a> ! > ! End of loop ! EX$$ ! Exit ! Now, the good tricks to know: In TECO you have Q-registers. Think of them as variables that can store a number and a string (at the same time). TECO always have a current position in the buffer. That is denoted by ".". Functions takes arguments. So, a thing like the search and replace is FSstr1$str2$, which searches for str1, and if found, replaces it with str2. So the first like is just searching for the next opening paren, and inserts a lot of cruft after the paren. Just plain text constant. At this point, the current position is just before the nodename. So, we store the position where the nodename starts. (.UA). The command is actually nUq, where n is any number. We just use "." as the number, which is the current position. q is what Q-register to store the value in. So, .UA stores the current position in Q-register A. S)$ should be very obvious. Just search for the closing paren. -C should also be pretty obvious. nC moves the position that many steps. If no argument is given, it defaults to 1. -C is just short for -1C. QA,.XA looks much worse than it is. The basic command is actually m,nXq, which stores the text between m and n in Q-register q. The the XA part should be obvious. Store the text in Q-register A. The stuff before the command is QA,. . At this point, you should realize that n in this case is ".", or the current position. QA is the function to read out the value from Q-register A (Qq to say the function in a general way). So we'll copy the text from the start of the nodename (stored in Q-register A) to the current position, which is right before the right paren, to Q-register A. That is, Q-register A will then hold the nodename. Also, at this point, the current point is after the nodename. So, we now want to finish the <a href= tag, so we insert a little more text: I">$, which does just that. Position is still right before the right paren, but now we have a full <a> tag in the buffer. GA gets the text from Q-register A, and inserts it into the buffer. That is the nodename again, now for displaying. I</a>$ then inserts a little more text, finishing the tagged text. > is the end of the loop. EX$$ exits. See. TECO is actually pretty easy. :-) Johnny

13 years, 1 month

VS4000/90: Up and running!

by jg＠jordi.guillaumes.name

El 09/02/2013, a les 23:49, Clem Cole <clemc at ccc.com> va escriure: eeds to check any timing differences and the name of the RW/WR pin is different - but they >>might<< work the same way (might also need to be inverted). In the 1287 that pin is named R/W when the chip uses motorola style timing (MOT connected to Vcc) and WR when it uses intel style (MOT connected to GND). Check the DC1287A datasheet for the gory details. Now the MOT pin is not there in the 1267 (it is used to signal a "wake up" condition), so it doesn't look to be completely compatible with the 1287. Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES

13 years, 1 month

Mulita issue

by mholmes10＠hotmail.com

Forgive me if this is off topic, but I was reading about the fixes to the VAXStation 4000 regarding chips. I bought a multia several years back and I think it sucommed to being moved to and from Germany and the States too many times. I had it booting as a satelite off a DEC 3000 just fine, until this last move. I thought the battery had died and replaced it. (dead battery prevents the bios from coming up) I get the SRM console and i'd get MOP load message on the DEC 3000 but the MULTIA just hangs after message about bootstrapping. I heard something about an I/O chip that can go bad on the MB and was wondering if anyone had any ideas that could be used to fix the MULTIA. thanks Mike

13 years, 1 month

VS4000/90: Up and running!

by jg＠jordi.guillaumes.name

El 09/02/2013, a les 22:36, hvlems at zonnet.nl va escriure: In most VAX or VAXstations you can use an SCA drive together with a converter. There'e enough room inside the box. Yeah, I know. I'm using that thing in the 4000/60 Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES

13 years, 1 month

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet