test-drb October 2001

test-drb@ccmp.vtda.org

259 participants
770 discussions

by dittman＠dittman.net

> Shoot..... I've wanted a VLB SCSI card! The Adaptec would have been > perfect. Tell me, is the 2842 wide or narrow? Both of them were narrow. There wasn't a wide 2842. -- Eric Dittman dittman(a)dittman.net Check out the DEC Enthusiasts Club at http://www.dittman.net/

22 years, 8 months

Reading non-PC format floppies

by mtapley＠swri.edu

Tony, with characteristic modesty, said: >I've written programs, sure, but I don't think they're particularly >well-written or elegant programs. They just do the job I need to do. Tony: MICROS~ has what they call "programmers" and they don't get that far. Do I have to win the Indy 500 before I get to be called a "driver", or is it enough if I just make it to the grocery store and back? I'd go ahead and claim credit, were I you. You might say "...not a professional programmer" or "...don't have a formal degree in programming" or even "...not a serious programmer". But if you're able to read kernel sources in order to learn how to successfully use FDRAWCMD, I'd call you a programmer. Sellam: I humbly suggest that more exact forms of expression, at least in international public forums, might avert misunderstandings. - Mark

22 years, 8 months

What people "should" know

by ajp166＠bellatlantic.net

Here here! One-shots are fine for pule shortening or stretching so long as it's non-critical. Worst abuse, Altair 8800 front pannel. One of the best designs that use a oneshot was the PERCOM Cassette board, it was a digitial oneshot and predictable. Allison -----Original Message----- From: Richard Erlacher <edick(a)idcomm.com> To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org> Date: Wednesday, October 24, 2001 9:12 PM Subject: Re: What people "should" know >That's why it's been common practice to fire anyone who uses one-shots >(monostables) for anything. I personally believe it should go beyond that, in >that the perpetartor of such a heinous crim should be barred from asserting his >credentials as a circuit designer for a short period, of, say, 10 decades.

22 years, 8 months

Reading non-PC format floppies

by jdonogh1＠prodigy.net

Any tools for reading non-PC 5 1/4" HD floppies out there? Tried reading them with DOS DEBUG, get 'Data Error'.

22 years, 8 months

first step getting VAX 6000-400 booted ...

by ajp166＠bellatlantic.net

OK, the default boot device (a SET option) is either dead or not found. Allison -----Original Message----- From: Gunther Schadow <gunther(a)aurora.regenstrief.org> To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org> Date: Wednesday, October 24, 2001 12:19 PM Subject: Re: first step getting VAX 6000-400 booted ... >Geoff Roberts wrote: > >> Hmm, Unit 0 has an excellent chance of being a system disk, but possible it >> was >> initialised prior to being retired. What's the exact error msg (console dump >> is good) > >I don't have the console dump on that, but the only error message >I recollect was: > >?3 Device I/O Error (or something very similar.) > >Would that be the appropriate response on an RA90 drive with >wiped-out media? My drive completed all tests, including the >spun-down and the spun-up tests (the latter includes disk >access tests.) > >> Tapes are probably sus. TK70's are the least reliable component of a 6000, >> but are still pretty reliable compared to the TK50. > >yack! > >> > I also have a TU81+ and VMS bootable tape on 9-track, maybe that's more >> reliable? >> >> Very likely, do you have the companion card for the TU81+ (KLESI-B) to go in >> the Vax? >> They TU81+ is not SDI, so it won't even plug in to the KDB50. If all else >> fails I can probably whip >> up a tape for you on ours. > >Instructions on how to write an Ultrix tape from VMS would >be cool. I'm sure I can get VMS up. What is the least >amount of knowledge that I need to get a VMS system up >in single user mode and try a couple of SDI accesses, >try reading a TK and writing to a TU? > > >> Not very familiar with Ultrix though I gather it's also possible to mop boot >> an ultrix box from a vms one, though I don't think it will do vice versa. > >It definitely is as the source code says. I'll use my FreeBSD >laptop as the boot host. Monitoring with tcpdump is a good way >of debugging network booting. > >Attached below you'll find annotated console dumps from my >yesterday's attempts (thanks to xterm :-) > >My comments are lines starting with "GS>" > >GS> I have swapped in another TK70 drive (one that may be less worn) >GS> and now I turn on the machine: > >#123456789 0123456789 0123456789 01234567# > >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # > A A . A M M M M P P P P P P >TYP > o o . + + + + + + + + + + + >STF > . . . . . . . . E E E E E B >BPD > . . . . . . . . + + + + + + >ETF > . . . . . . . . E E E E E B >BPD > > >. . . . . . . . . + . . + + + . XBI D >+ >. . . . . . . . . + + . + . + . XBI E >+ > > . . . . A4 A3 A2 A1 . . . . . . >ILV > . . . . 128 128 128 128 . . . . . . 512 >Mb > >ROM0 = V4.00 ROM1 = V4.00 EEPROM = 2.03/4.02 SN = AG94408887 > > >>>> SHOW ALL > Type Rev > 1+ KA64A (8082) 000D > 2+ KA64A (8082) 000D > 3+ KA64A (8082) 000D > 4+ KA64A (8082) 000D > 5+ KA64A (8082) 000D > 6+ KA64A (8082) 000D > 7+ MS65A (4001) 0084 > 8+ MS65A (4001) 0084 > 9+ MS65A (4001) 0084 > A+ MS65A (4001) 0084 > B+ KDM70 (0C22) 2811 > D+ DWMBA/A (2001) 0002 > E+ DWMBA/A (2001) 0002 > > XBI D > 1+ DWMBA/B (2107) 000A > 2+ KLESI-B (0103) 0006 > 3+ KDB50 (010E) 142C > 6+ DEBNI (0118) 0400 > > XBI E > 1+ DWMBA/B (2107) 000A > 3+ DMB32 (0109) 0004 > 5+ CIBCA-B (0108) 41C2 > 6+ TBK70 (410B) 0307 > Current Primary: 1 > /NOENABLED- > /NOVECTOR_ENABLED- > /NOPRIMARY- >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # > . . . . A4 A3 A2 A1 . . . . . . >ILV > . . . . 128 128 128 128 . . . . . . 512 >Mb > /INTERLEAVE:DEFAULT > /SCOPE /SPEED: 9600 /BREAK > English > XMI:D BI:6 08-00-2B-34-A5-CA > DEFAULT /XMI:E /BI:6 CSA1 > TAPE /XMI:E /BI:6 CSA1 > ETH0 /XMI:D /BI:6 ET0 >SHOW DSSI is not yet implemented > >GS> Now I have loaded the VMS 6.1 stand alone backup TK70 and go: > >>>> BOOT /XMI:E /BI:6 CSA1 >Initializing system. > >#123456789 0123456789 0123456789 01234567# > >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # > A A . A M M M M P P P P P P >TYP > o o . + + + + + + + + + + + >STF > . . . . . . . . E E E E E B >BPD > . . . . . . . . + + + + + + >ETF > . . . . . . . . E E E E E B >BPD > > >. . . . . . . . . + . . + + + . XBI D >+ >. . . . . . . . . + + . + . + . XBI E >+ > > . . . . A4 A3 A2 A1 . . . . . . >ILV > . . . . 128 128 128 128 . . . . . . 512 >Mb > >ROM0 = V4.00 ROM1 = V4.00 EEPROM = 2.03/4.02 SN = AG94408887 > > >Loading system software. > > OpenVMS VAX Version V6.1 Major version id = 1 Minor version id = >0c >PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 23-OCT-2001 > >Configuring devices . . . > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > >%PAA0, Port is Reinitializing ( 49 Retries Left). Check the Error Log. > >GS> oops, what is %PAA0? Something is bad, but what? >GS> as you might expect, it gives above error message for each >GS> retry 48, 47, 46, ... will not show those here. But there >GS> is also other stuff, as if I'm already running multi-tasked. > >Now configuring HSC, RF, and MSCP-served devices . . . > >GS> and on with the %PAA0 reinitializations down to 24 > >%PAA0, Port is Reinitializing ( 24 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > >Please check the names of the devices which have been configured, >to make sure that ALL remote devices which you intend to use have >been configured. > >If any device does not show up, please take action now to make it >available. > >GS> in a hurry I power up the RA90 hooked to the KDB50 and >spin it up > >Available device MUC6: device type TK70 >%PAA0, Port is Reinitializing ( 23 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > >GS> ... > >%PAA0, Port is Reinitializing ( 9 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 8 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 7 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 6 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 5 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 4 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 3 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 2 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 1 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is Reinitializing ( 0 Retries Left). Check the Error Log. > >%PAA0, Port Error Bit(s) Set - CNF/PMC/PSR 00000000/00000020/00008280 > > >Enter "YES" when all needed devices are available: >%PAA0, Port is going Offline. > > >Enter "YES" when all needed devices are available: yes >%BACKUP-I-IDENT, Stand-alone BACKUP V6.1; the date is 23-OCT-2001 >00:03:52.13 >$ > >GS> yea! a prompt! we made it. But what's next? > >$ help >%CLI-W-IVVERB, unrecognized command verb - check validity and spelling > \HELP\ > >GS> ah I give up, I want to see Ultrix up, may be that new >GS> drive did it? Hit the reset button, system initializes >GS> same as above, swap in the Ultrix TK and go: > >>>> BOOT /XMI:E /BI:6 CSA1 >Initializing system. > >#123456789 0123456789 0123456789 01234567# > >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # > A A . A M M M M P P P P P P >TYP > o o . + + + + + + + + + + + >STF > . . . . . . . . E E E E E B >BPD > . . . . . . . . + + + + + + >ETF > . . . . . . . . E E E E E B >BPD > > >. . . . . . . . . + . . + + + . XBI D >+ >. . . . . . . . . + + . + . + . XBI E >+ > > > . . . . A4 A3 A2 A1 . . . . . . >ILV > . . . . 128 128 128 128 . . . . . . 512 >Mb > >ROM0 = V4.00 ROM1 = V4.00 EEPROM = 2.03/4.02 SN = AG94408887 > > >Loading system software. >%BOOT-F-Insufficient memory for CI >?06 Halt instruction executed in kernel mode. > PC = 0000040Fc > SAVPSL = 041F0600 > ISP = 00000200 > >Bootstrap failed due to previous error. >>>> > > >GS> this is that CI problem. Now I turn off machine again and >GS> remove CI cards. I do have HSC90s to go with it and I definitely >GS> want to run CI, but for now I'll start easy. So, power up >GS> again. Wait for one initialization again, then: > >>>> BOOT /XMI:E /BI:6 CSA1 >Initializing system. > >#123456789 0123456789 0123456789 01234567# > >F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE # > A A . A M M M M P P P P P P >TYP > o o . + + + + + + + + + + + >STF > . . . . . . . . E E E E E B >BPD > . . . . . . . . + + + + + + >ETF > . . . . . . . . E E E E E B >BPD > > >. . . . . . . . . + . . + . + . XBI D >+ >. . . . . . . . . + . . + + + . XBI E >+ > > . . . . A4 A3 A2 A1 . . . . . . >ILV > . . . . 128 128 128 128 . . . . . . 512 >Mb > >ROM0 = V4.00 ROM1 = V4.00 EEPROM = 2.03/4.02 SN = AG94408887 > > >Loading system software. > >?06 Halt instruction executed in kernel mode. > PC = 00280200c > SAVPSL = 041F0600 > ISP = 00280000 > >Bootstrap failed due to previous error. >>>> > >GS> here ends my console dump. > >If it weren't for the many heavy items I still have to >shuffle, disassemble, lift and reassemble, I could go mad >about the Ultrix folks who have neglected to put >some explanatory printf into the boot code before >the halt call. It could be so much easier if we knew what >the problem is. > >thanks, >-Gunther > >-- >Gunther_Schadow-------------------------------http://aurora.rg.iupui.edu >Regenstrief Institute for Health Care >1050 Wishard Blvd., Indianapolis IN 46202, Phone: (317) 630 7960 >schadow(a)aurora.rg.iupui.edu------------------#include <usual/disclaimer>

22 years, 8 months

MacOS DHCP Server?

by dhquebbeman＠theestopinalgroup.com

> >At one time, you could download trial versions of the package. > >Additionally, if you hunt around, you'll find the magix needed > >to make the evaluation period last a very, very long time. ;-) > > Although, lots of people use and love Vicom's SoftRouter (I think that is > the name it is going by now)... I would like to point out that last I > knew, it uses its own TCP/IP stack, and not Apple's OpenTransport. The > Vicom stack has been known to provide incompatibility with some software > that wants to use OpenTransport. I have also heard that Vicom's is more > unstable in general (but I guess that might be dependant on what version > of OpenTransport you compare it to, as early versions of OT were very > unstable in their own right). This might have changed by now, but I would > confirm it before buying. Yes, it does use it's own TCP/IP stack, but one which co-exists peacefully with Open Transport... it's not like you've got to drop back down to Classic Networking... We never had any stability problems. However, it does not pass GRE(47) packets, so you can't form a VPN connection through one. > And then just to give a plug to Sustainable Softworks... their > IPNetRouter product does everything Vicom's does (and more I believe), > and is priced pretty much the same ($49 for 68k only, $79 for PPC and > 68k). I don't have any connection with Sustainable Softworks, I am just a > VERY VERY satisfied customer (I put them as the #1 best company I have > ever had to deal with). Nice price, Chris; I'd say, David, go with it! -dq

22 years, 8 months

More free ISA/VME cards

by pcw＠mesanet.com

Maybe someone would like these for shipping charges. Hate to just toss em. ISA Q DESC 2 D-A cards 2X 12 bit analog out ? 1 D-A ADC card 2x12 bit D-A + maybe 8 chan 12 bit A-D ? 1 localtalk card ? 1 SCSI adapter Adaptec 1522A 2 SCSI adapter Adaptec 1540C 1 SCSI adapter Adaptec 1540B 1 SCSI adapter Adaptec 1542CF VME Q DESC 2 AB Creonics MCC 2 axis servo motor controller 1 Data translation DA -- ADC 12 bit DT1408 1 Teckint opto-isolated I/O card TVM 744 Misc Q DESC 6 OMTI SCSI/MFM disk controller model 310x 1 Columbia Data Products looks like MFM HDC has Z80 + 64K RAM + MFM disk interface PN 10805-D Peter Wallace

22 years, 8 months

first step getting VAX 6000-400 booted ...

by Antonio.Carlini＠riverstonenet.com

>Among all the fanning and blowing and spinning, the disk >seek can be pretty faint. No, I did not hear the disk >seeking and it all went suspiciously quick. I may My recollection of RA9x drives is that when you transition them to RUN (either by hitting the button or as a result of host action) they is a clear "thunk". >not have proper connection between KDB50 and disk. The >disk shows both ports A and B enabled, and I'm connected >only to A. Is there any ordering of the 4 ports on the >KDB50 bulkhead that I need to know to get it right? The order of the 4 KDB50 connections is essentially meaningless. It certainly does not determine device naming or whatever. The A/B port stuff also matters very little. If your KDB50 is connected to port A, then port A needs to be enabled and B is irrelevant. Or vice versa. Antonio

22 years, 8 months

Adventure in Ersatz-11

by ajp166＠bellatlantic.net

If I'd seem the message I'd have told you most of the PDP-11 games that eat memory run under the RT-11 SJ monitor. Advent is definately one. Allison -----Original Message----- From: Gooijen H <GOOI(a)oce.nl> To: 'classiccmp(a)classiccmp.org' <classiccmp(a)classiccmp.org> Date: Wednesday, October 24, 2001 11:32 AM Subject: RE: Adventure in Ersatz-11 >Stupid that I did not think of trying SJ. >With SJ entering .R ADVENT starts Adventure also! >I assumed that VBG was for Virtual BackGround, so >nice to be comfirmed on that. >Indeed, I have E11 running on an 486DX2/66, but I >cannot give an idea of how fast it runs, compared >to a PDP-11. Although E11 can be set to an 11/70, >I have set it to /35-40 because that is also the >*real* hardware I have. Never set it to /34(A) or >to /44. Both those systems I also have running. >Next time that I start the 11/35 I will run ADVENT >on both of them and measure the time until the >welcome message appears on the screen. > >For the "blinkenlights" check out my webpage. >http://home.hetnet.nl/~tshaj/pdpsite/pdpstartpage.html > >then click in the left pane on the link Homebrew 'PDP-11'. >At this moment only the LEDs of the data bus blink. >I hope to add a piece of hardware that 'talks' to Ersatz-11 >so that the address bus LEDs are also active *and* that the >switches function as on the real thing. The goal is that >the hardware design can facilitate *any* real PDP-11 console >that has switches and lights, from an 11/10 to an 11/70. >Of course, this project needs the cooperation of John Wilson, >and I had already some preliminary contacts with him. >He also likes the option to connect a real console to the >demo(!) version of Ersatz-11. > >-Henk. > >> -----Original Message----- >> From: Jerome Fine [mailto:jhfine@idirect.com] >> Sent: woensdag 24 oktober 2001 0:41 >> To: classiccmp(a)classiccmp.org >> Subject: Re: Adventure in Ersatz-11 >> >> >> >Gooijen H wrote: >> >> > Yes !! >> >> Jerome Fine replies: >> >> Thank you for the feed back. I was not sure how much memory >> ADVENT requires. You might also try: >> BOOT RT11SJ >> if you wish. >> >> > Thanks very much, Jerome. >> > Booting RT-11FB and then running ADVENT still produces >> > the "Insufficient memory" fatal error. >> > However, VBGEXE works fine ! >> > After the "Welcome to Adventure!! Would you like instructions?" >> > and entering 'YES", it goes: Somewhere nearby is Colossal Cave, >> > etc. >> > This means that I am now going to play Adventure. This has a >> > serious drawback on the expansion of my website ... >> > I am playing it on my "homebrew-PDP" with the BLINKENLIGHTS on!! >> > On my website this project (early phase) has a separate link. >> > BTW. What is VBGEXE, what do the letters stand for? >> > Thanks again, >> > Henk. >> >> "EXEcute Virtual BackGround program" is how I think of the letters >> with the understanding that the word EXEcute is then switched >> to the end. >> >> A few points worth noting. >> >> (a) If FOO.SAV requires any arguments as in: >> "RUN DEV:FOO.SAV arguments" or replace RUN with VBGEXE, >> then they must be on the same line. The alternative is the >> put all three >> parts of the command on separate lines. Otherwise, with just >> "VBGEXE DEV:FOO.SAV" on the first line, somehow the request >> for information expects the arguments to already be there and if not, >> just exits. Entering: >> VBGEXE >> DEV:FOO.SAV >> arguments >> on three separate lines works as well. >> >> (b) The command: >> SRUN VBGEXE.SAV/TERMINAL:n/LEVEL:m/NAME:utility >> also works very well when you want to run a system job at a >> higher priority. >> TERMINAL is only useful with a system that has multi-terminal support >> LEVEL specifies the system job number ( 1=>6 ) >> NAME can be used to automatically select an executable file >> called SY:utility.SAV >> One minor problem is that if name is omitted, then only ONE >> instance of >> VBGEXE can be invoked as a system job since the high memory >> GRCBs (Global >> Region Control Blocks) must all have different names. I have >> a small patch >> with allows the user to do the command: >> SRUN VBGEXE.SAV/TERMINAL:n/LEVEL:m/NAME:VBGEXm >> If that is done, each GRCB is given the name VBGEXm making them all >> different. This means that no program can have the name VBGEX(1=>6), >> a restriction that I assume can be lived with. >> >> I also remember that modifying TECO to be named VMUNG so that >> "VBGEXE VMUNG arguments" >> would work the same as >> "MUNG arguments" >> but use the full 64 KBytes allowed by VBGEXE. >> >> By the way, I assume that you are using E11 on a PC. Which hardware >> and how fast do you find that the code runs compared to any >> real PDP-11 >> hardware. Plus, I can't remember about the "BLINKENLIGHTS" - what >> did you do to have those available? >> >> Sincerely yours, >> >> Jerome Fine >> >> > >

22 years, 8 months

value of classic DEC machines?

by ajp166＠bellatlantic.net

My understand of PDP-1s is that if there are 10 left it's a lot. the only two I know of was the BCM Machine and one up in Whitehorse {or was it Yellowknife} running Log/wood mill accounting system. Allison -----Original Message----- From: John Allain <allain(a)panix.com> To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org> Date: Wednesday, October 24, 2001 10:16 AM Subject: Re: value of classic DEC machines? >>> Now a PDP-1 would certainly be worth 100KUS$, > >>..to a collector who had US$100K to throw away and >> absolutely HAS to have the first PDP-1... > >Worth, Costs, Is Valued at... all highly relativistic concepts >don't you think? > >What about history? My book says that only 50 PDP-1's >were produced. Almost certainly 50%++ were scrapped. >Anybody know where all the PDP-1's are? I'd like to see >one (or more). > >John A. > > >BTW, on thread. A good clean runnung PDP-11 with SW >and docs can fetch over $4K, to the original question. > >John A. > >

22 years, 8 months

← Newer
1
...
18
19
20
21
22
23
24
...
77
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

test-drb October 2001