test-drb October 2001

test-drb@ccmp.vtda.org

259 participants
770 discussions

TU81+ spooks (was: Re: first step getting VAX 6000-400 booted ...)

by Antonio.Carlini＠riverstonenet.com

> Gunther Schadow wrote: >I did try MUB0 (because that's how VMS calls it for me), but >that doesn't work. I just like VMS calls my disk DUA0 but to >boot from it I have to call it just DU0. So MU0 it should be. >The CSA1 is weird, because it's really MUC6 for VMS, and it >should be another MU. The console's idea of a device name and VMS's idea of a device name will not always agree. For MSCP SDI disks (like your RA90) the device name will usually be DUAn:, where n: is the unit number you have given it. OpenVMS will sort out how to get from that unit number to a specific path to the device (possibly hanging off a CI rather than on your local machine!) The console usually does not bother with such shenanigans. It wants you to tell it how to find the device. For example, on a VAX 82x0/83x0 box you would boot as: B DUsn: where s is something like the VAXBI slot number in hex, and n is the unit number (also in hex IIRC). Of course if you put your KDB50 in slot ten then you can do: B DUAn: but that just hides the difference :-) Once VMS boots you can do: $ MC SYSGEN A A /L (that's AUTOCONFIGURE ALL /LOG) and it will go off and find most things. Then SHOW DEVICE D will list the disks (really any device that starts with D) and SHOW DEV M will show the Magtapes. The Console Storage device (CS) is generally not visible without being explicitly made so via SYSGEN, so it will generally not show up. >Yes, that would be the crucial question? Can you even boot from >TU81+. Given the rest of the orthogonal DEC design, I would be >highly surprized if one could not. Also, I'm pretty sure that >BSD used to be distributed on 9-track, bootable, presumably. But >I would appreciate a confirmation of this. If someone could test >copying a bootable TK to TU and then try TU booting? I don't know whether the VAX 6000 can cope with booting from TU81+, nor do I know what, if any, controller support it expects for a device to be bootable. (I don't know how much of a boot driver is implemented in the console and how much needs to be provided by the controller). If you do want to backup your system disk, the steps are as follows: 1. Install standalone backup on the system disk. $ @SYS$UPDATE:STABACKIT SYS$SYSDEVICE: This *should* (if I've remembered it correctly) create a standalone backup in root SYSE (i.e. $ DIR SYS$SYSDEVICE:[SYSE] should now have something in it ... don't mess or delete any of this though, most of it is effectively symlinks to stuff that matters!) 2. Boot as normal but with R5's top byte set to E, typically /R5:E0000000 should do this for you. 3. Standalone Backup should come up in a few minutes rather than a few hours! 4. $ BACKUP/IMAGE/VERIFY/IGNORE=LABEL SYS$SYSDEVICE: mua0:SYSTEM.BCK /SAVE mua0: is whatever the tape device wants to be called (MUB0:, MUB1: CSA1:, whatever). SYSTEM.BCK is just the saveset filename /IGNORE=LABEL means "I don't care how valuable that tape is, I know what I'm doing so wipe it!!" /VERIFY means it will take twice as long but there is a possibility that you may be able to restore the data one day :-) It's been a while, so this probably won't work first time. Antonio

24 years

[OT] New toy...

by dhquebbeman＠theestopinalgroup.com

> > In no time somebody is bound to post the URL to some master list. > > INTSIBTPTUTSML SETMBRWHAA (someday, even the most banal remarks will have an abbreviation)! -dq

24 years

Do we have a VAX organization?

by mhstein＠usa.net

Maybe not just for VAXes? >From another perspective: A friend and I were both selling & supporting Cromemcos in the 80's and early 90's and, although neither of us is a "collector," as time went on and they became obsolete, we took them all back & hung on to them, first for parts and then because we didn't have the heart to throw them out. A few years ago we decided it was time to clear out the space and get rid of them, but could not find anyone seriously interested locally or on the 'Net at that time (mind you, being in Canada does make shipping a little expensive), so we hung on to them a little longer. Recently we both needed space again; he decided that it wasn't worth the time and trouble to find a good home for them and tossed most of his into the dumpster, while I thought that surely there'd be lots of people who'd give their eye teeth (and maybe even a couple of bucks) for this stuff. I did get a few inquiries for a card or two, and several people wished that I were in California or Minnesota (or that they were in Toronto, although, at least for the Californians, that's less attractive as winter approaches :). And yes, I was contacted by a couple of local collectors who will probably take a few of the systems. But on the whole, so far it has indeed not been worth the time and trouble, especially since (unlike HP & DEC) there's not much of a user community (knowledge base) out there and people prefer them to be assembled & working instead of a pile of chassis and boxes of manuals & untested cards. All this to say that it sure would have been nice if there'd been a central place with the organization & resources to arrange and/or pay for shipping the whole lot and a few bucks on top, and then dole them out to interested individuals. As it is, unless someone local actually wants it all, most of it will have to be scrapped. Thanks for the tip about the value of scrap, BTW; believe these boards & connectors were still goldplated... mike

24 years

Apple II SCSI Card Questions

by r_beaudry＠hotmail.com

Hello all, I just today received an Apple II SCSI card (NO docs), and I have some questions... First, a description of the card: Typical sized Apple II card, has a ribbon cable with one connector soldered to the card, and the other terminating in a female 25-pin "D" shape connector. There is a 40-pin chip labeled "NCR/5380" on one line, followed by "C476217", "6-1082073", and "8810S" on separate lines. There is also a 27128 EPROM, labeled "341-0437-A, (c) Apple '87". Aside from some glue logic, there are also two PALs, an 8-position jumper block, and a 6264 SRAM chip. The card is silk-screened "607-0291-B (c) 1986 Apple II SCSI Card", and carries the FCC ID "BC66DSA2B2087". Questions: 1) Is this the High-Speed SCSI card I hear about every so often? 2) Will this card work in a IIgs? 3) Are there any limitations to what SCSI devices I can attach? Ideally, I'd like to add an external hard drive and CD-ROM (Or maybe a Zip drive). Could I do this from this card? 4) Does anyone have docs they could copy and send to me? I'd gladly pay postage. 5) Are there updates to the EPROMs available somewhere? Not that I suspect problems, but if Apple released updates, I'd like to make sure I have the latest code... 6) Does anyone have drivers (if needed) that they could copy and send to me? Again, I'll pay postage. Thanks! Rich B. P.S. I get the digest, so if you could CC: me privately in your replies, I'd appreciate it. I'm a bit anxious to know what I've got here... "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Ben Franklin

24 years

How to disassemble an HSC90?

by DAW＠yalepress3.unipress.yale.edu

Are the sdies getting stuck on wheel brackets that stick out too far? A DEC rack I have for a tape drive had that problem. The brackets by the two back wheels stick out about 1/8". Enough to stop the side panel from lifting neatly up... --- David A Woyciesjes --- C & IS Support Specialist --- Yale University Press --- mailto:david.woyciesjes@yale.edu --- (203) 432-0953 --- ICQ # - 905818 ! -----Original Message----- ! From: Gunther Schadow [mailto:gunther@aurora.regenstrief.org] ! Sent: Friday, October 26, 2001 11:11 PM ! To: classiccmp(a)classiccmp.org ! Subject: How to disassemble an HSC90? ! ! ! Hi, ! ! has anyone of you ever disassembled an HSC cabinet? I am looking ! pretty stupid right now. It's not the first piece of DEC iron ! equipment that I have moved in pieces, I did two VAX6000 and one ! TU81+. But this one is different. While being half-height like the ! TU81, it's quite a bit deeper. The side-walls appear to be just ! locked at the bottom and then hooked such that one can lift it ! up and off, like the TU81's side walls. However, they do not move ! no matter how hard I try. I don't find any screws holding them, ! though. And with the sidewalls on, I cannot remove the top-cover ! either. ! ! So, I was hoping I could at least take it into two pieces by ! moving the whole core out in one piece. Apparently that central ! unit is just screwed on the front, like a rack-mount device. ! Indeed I can move it out quite far. But then it stops at a ! protruding piece of the backplane circuit board! There seems ! to be no way to move that core all the way out other than by ! removing the backplane circuite board. And I'm not going to do ! that. ! ! Other DEC equipment was quite straight forward to disassemble, ! but this one beats the auto-assembies in difficulty level. ! I appreciate every advice. My suspicion is that the sidewalls ! are indeed removable, but mine are just stuck. Someone seen ! it? ! ! regards ! -Gunther ! ! -- ! Gunther Schadow, M.D., Ph.D. ! gschadow(a)regenstrief.org ! Medical Information Scientist Regenstrief Institute for ! Health Care ! Adjunct Assistant Professor Indiana University School ! of Medicine ! tel:1(317)630-7960 http://aurora.regenstrief.org

24 years

unknown SRAM chips

by mhstein＠usa.net

This IS your lucky day! Since nobody at all replied to my post offering several boxes of data books, I tossed 'em all out; HOWEVER, it turns out that I'd overlooked one box under a chair and guess what, it contained a 1986 Toshiba MOS memory book. The TMM2068 is a TTL compatible 4x4 NMOS SRAM: 1-A7 20-Vcc 2-A6 19-A8 3-A5 18-A9 4-A4 17-A10 5-A3 16-A11 6-A2 15-I/O1 7-A1 14-I/O2 8-A0 13-I/O3 9-/CS 12-I/O4 10-GND 11-/WE I think someone else already gave you the info on the HM6147 -------------Original Message-------------- Date: Sun, 28 Oct 2001 13:32:54 -0500 From: Jim Donoghue <jdonogh1(a)prodigy.net> Subject: unknown SRAM chips Anybody have pinouts for these ICs - I think they are some kind of SRAM. Thanks. TMM2068AP-45 HM6147HP-35

24 years

OT: Playstation 2 opinion?

by technos＠nerdland.org

I dunno. I'm doing just fine as far as games go on a K6-450 and VooDoo 2 SLI. Jim On Monday, October 29, 2001 12:49 PM, Zane H. Healy [SMTP:healyzh@aracnet.com] wrote: > >My recommendation is to forget the console, and put together a gaming PC. > >Better intelligence to the games, and immensely greater selection and > >usefullness. > > With the PS2 he'll be able to play new games for how many years without > upgrading the hardware? OTOH, how often do you need to upgrade a gaming PC > to play the latest stuff? I decided consoles were the way to go a few > years ago. > > Zane > -- > | Zane H. Healy | UNIX Systems Administrator | > | healyzh(a)aracnet.com (primary) | OpenVMS Enthusiast | > | | Classic Computer Collector | > +----------------------------------+----------------------------+ > | Empire of the Petal Throne and Traveller Role Playing, | > | PDP-10 Emulation and Zane's Computer Museum. | > | http://www.aracnet.com/~healyzh/ |

24 years

Price guide for vintage computers

by DAW＠yalepress3.unipress.yale.edu

! Instead of a price guide, how bout a spotting/indentification ! guide with info ! on identifying computers and components and options without ! any pricing info? ! ! -Bob This would be most helpful. Similar to these hardware references on NetBSD's site... http://www.netbsd.org/Documentation/Hardware/Machines/DEC/vax/ http://www.netbsd.org/Ports/vax/models.html --- David A Woyciesjes --- C & IS Support Specialist --- Yale University Press --- mailto:david.woyciesjes@yale.edu --- (203) 432-0953 --- ICQ # - 905818

24 years

VAX6460: VMS 5.4 how to move on?

by gunther＠aurora.regenstrief.org

Hi, O.K. I am delighted! I did boot VMS 5.4 from that RA90 labeled as unit 0. I changed the system password and am now copying ULTRIX filed off the TK50 tape onto disk in order to write them on 9-track trying to boot from there. Of course I will have all sorts of grief because of the weird VMS blocked file formats. For instance, what I read from the tape should look like this on UNIX: -rw-r--r-- 1 operator 17408 May 12 03:44 file0 -rw-r--r-- 1 operator 2091208 May 12 03:45 file1 -rw-r--r-- 1 operator 6594560 May 12 03:47 file2 -rw-r--r-- 1 operator 727040 May 12 03:47 file3 -rw-r--r-- 1 operator 8826880 May 12 03:48 file4 -rw-r--r-- 1 operator 3143680 May 12 03:48 file5 -rw-r--r-- 1 operator 2007040 May 12 03:48 file6 -rw-r--r-- 1 operator 522240 May 12 03:48 file7 -rw-r--r-- 1 operator 665600 May 12 03:48 file8 -rw-r--r-- 1 operator 286720 May 12 03:48 file9 -rw-r--r-- 1 operator 2949120 May 12 03:45 file10 -rw-r--r-- 1 operator 2160640 May 12 03:45 file11 -rw-r--r-- 1 operator 1249280 May 12 03:45 file12 -rw-r--r-- 1 operator 1024000 May 12 03:45 file13 -rw-r--r-- 1 operator 1495040 May 12 03:45 file14 ... -rw-r--r-- 1 operator 276480 May 12 03:47 file38 and what I have copied from TK50 so far looks like this: $ dir /size Directory SYS$SYSROOT:[GUNTHER] FILE.000;1 0 FILE.001;1 0 FILE.002;1 12880 FILE.003;1 1420 FILE.004;1 17240 FILE.005;1 6140 FILE.006;1 3920 FILE.007;1 1020 Total of 8 files, 42620 blocks. O.K. seems like we have file sizes reported in 512 byte blocks. But file 1 didn't come up right. May be that was because of this read error that keeps the tape from booting? Anyway, before I go to bed I will have copied the first set of filed to disk and back to a tape. Either a TK70 or a 9-track and will try to boot. It looks like I'm making progress, finally. However, I ask myself what to do with that VMS 5.4 system disk. Should I keep it and get another drive downstairs for my Ultrix attempts? Should I rather keep this running 5.4 VMS or should I make a fresh install of a VMS 6.1 of which I have tapes? I am a curious person, so I could first dig in the disks for interesting stuff, but then, I rather want to get away from VMS and onto Ultrix and finally NetBSD. So how much are old filesystems worth keeping? I don't have enough tape to back it all up, and even if I had, how would I do this? How can I find UCX on this VMS 5.4 filesystem? It appears as absent. Is there something like find(1) on VMS? Did UCX not exist for VMS 5.4? Could I install it from a VMS 6.1 bin tape? Do I have any chance of using my ethernet for anything like file transfer or NFS without having UCX? thanks much for helping me accross the VMS river :-) regards -Gunther -- Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org Medical Information Scientist Regenstrief Institute for Health Care Adjunct Assistant Professor Indiana University School of Medicine tel:1(317)630-7960 http://aurora.regenstrief.org

24 years

Is Joe Around Here(info MDS225)

by techno＠dsuper.net

Hi there ... After reading Joes Intel MDS page I was intrigued. I have a MDS 225 Series III , but I have no OS or software. I need help in getting it going. It starts up O.K. into the diag ROM but thats it. Is there a way for me to get ISIS III for it? Also, what exactly CPM (GENERIC) will work on it? Yours truly.. Doug Taylor (Techno) Sysop of the "Dead On Arrival BBS" Telnet://doabbs.dynip.com http://www-mtl.look.ca/~techno techno(a)dsuper.net

24 years

← Newer
1
...
6
7
8
9
10
11
12
...
77
Older →

Jump to page:

2025

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