test-drb April 2002

test-drb@ccmp.vtda.org

280 participants
1162 discussions

by cdl＠proxima.ucsd.edu

> From: ard(a)p850ug1.demon.co.uk (Tony Duell) > Subject: Re: More 11/750 PSU Qs > To: classiccmp(a)classiccmp.org > Date: Tue, 16 Apr 2002 03:01:23 +0100 (BST) > In-Reply-To: <20020415200927.52402.qmail(a)web10301.mail.yahoo.com> from "Ethan Dicks" at Apr 15, 2 01:09:27 pm > Sender: owner-classiccmp(a)classiccmp.org > Reply-To: classiccmp(a)classiccmp.org > > > > > > NO!. SMPSUs do not like being run in parallel (unless designed to be > > > > > used like that). One PSU will end up attempting to supply all the > > > > > current and the other PSUs may not like having voltages applied to > > > > > their outputs. > > > > > > > > And once the first one drops dead, the next > > > > most "powerful" one repeats the process. > > > > Proof by "induction" left as an exercise :-) > > > > > > > *giggle* OK, ok, thought it was best to ask.... *laughs manically* > > > > Presumably, if one could a) tolerate the voltage drops and b) find massive > > diodes (many amps for the intended application in an 11/750), it could be > > done safely. Please feel free to correct me if I'm wrong. > > Well, that would prevent one PSU from supplying a voltage to the outputs > of another (something that can really confuse the regulation circuitry!), > but it won't help with the current distribution problem. The PSU who's > output after the diode drop is the highest voltage will end up sourcing > all the current. Not what you really want. Aren't there some power supplies that can be run in constant-current or "current-limited" mode? I think I used to do that with a PDP8-E, when the power drain of the add-in boards exceeded the original 1/2 Amp per slot. A booster supply to provide more current. carl -- carl lowenstein marine physical lab u.c. san diego clowenstein(a)ucsd.edu

22 years, 8 months

Champaign trip (aka DEC Galore)

by csmith＠amdocs.com

> -----Original Message----- > From: Doc [mailto:doc@mdrconsult.com] > [xdmcp] > Enable=1 Did that -- no dice. I haven't gotten much further. I hear that you can put a Port=177 (is that the number?) in there to make sure it uses the right port, and I haven't done that yet. Chris Christopher Smith, Perl Developer Amdocs - Champaign, IL /usr/bin/perl -e ' print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n"); '

22 years, 8 months

It's alive!

by vcf＠siconic.com

We've managed to get the Apple-1 being auctioned working. We can enter commands into the monitor and get expected responses. We're going to get a cassette drive hooked up to it and attempt to load BASIC next. -- Sellam Ismail Vintage Computer Festival ------------------------------------------------------------------------------ International Man of Intrigue and Danger http://www.vintage.org * Old computing resources for business and academia at www.VintageTech.com *

22 years, 8 months

OT Letting it go (was Re: The CommodoreOne is near!)

by mcguire＠neurotica.com

On April 17, Christopher Smith wrote: > > That's because we want to be *right.* It took me a long time > > to learn that > > I'd rather be happy than right. > > I'd rather be corrected than right. ;) No matter how much it > bruises the ego, it generally saves lots of time and energy > later. And you can learn something in the process! -Dave -- Dave McGuire "Mmmm. Big." St. Petersburg, FL -Den

22 years, 8 months

NeXTStation: How to fix NetInfo

by csmith＠amdocs.com

Ok, R. -- chime in here any time ;) Now that I can see the NeXTStation's display better, I've booted it again, and changed the local password with 'passwd'. That got me in again. It seems that some netinfo stuff is dying on bootup. Lots of the NeXTAdmin apps will complain about not being able to contact the NetInfo server and die. The NetInfo server, as far as I can tell is nibindd, is that right? What is lookupd? It starts right after it, and seems to possibly have something to do with NetInfo too, but I can't tell what. Anyway, lookupd likes to exit without doing much, and nibindd seems to be dumping core, which I assume isn't good at all ;) ... so how does one go about straightening this mess out? Chris Christopher Smith, Perl Developer Amdocs - Champaign, IL /usr/bin/perl -e ' print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n"); '

22 years, 8 months

Emulex MD21

by dquebbeman＠acm.org

> Rats, I wanted to use an Emulex MD21 from a Sun external SXSI box to hook my > PDP11s Fuji M2246E ESDI drive (that connects to the QBUS via an Emulex QD21) > upto a PC to do an image dump. > > The MD21 works OK with a Sun drive (a Micropolis model 1558) & the PC can > verify each block on that, but with the Fuji M2246E hooked up, I get > "unexpected SCSI command failure" from the Adaptec AHA1540CF BIOS when trying > to verify the disk - > host adapter status : 00h - no host adaptor error > target status : 02h - check condition > sense key : 02h - not ready > +sense code : : 22h > +sense code qualifier : 00h > > mean anything to anyone? The Fuji 2246E is working happily in the PDP11/83 so > I don't believe the drive is faulty (yet!) > > I noticed the MS21 announce itself to the SCSI controller as an "Emulex > MD21/S2". I wonder if there is specific Sun firmware in it to talk to > only Sun approved ESDI drives?... Hmmm this sounds a little familiar, I've got a Micropolis drive at home that's got an Emulex rider board, it may be the same setup, although from a Prime, not a Sun... I'll try to go home at lunch and check... -dq

22 years, 8 months

OT Letting it go (was Re: The CommodoreOne is near!)

by csmith＠amdocs.com

> -----Original Message----- > From: Glen Goodwin [mailto:acme_ent@bellsouth.net] > That's because we want to be *right.* It took me a long time > to learn that > I'd rather be happy than right. I'd rather be corrected than right. ;) No matter how much it bruises the ego, it generally saves lots of time and energy later. Chris Christopher Smith, Perl Developer Amdocs - Champaign, IL /usr/bin/perl -e ' print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n"); '

22 years, 8 months

OT Women & computers (was Re: The CommodoreOne is near!)

by csmith＠amdocs.com

> -----Original Message----- > From: Glen Goodwin [mailto:acme_ent@bellsouth.net] > Woman: Don't give me that crap! Women don't know anything about > computers! > This sort of thing happened almost every day. I don't blame > Deb at all for > leaving the industry. Of course, we're in Florida, so you > have to expect > some redneck attitudes, but from a *woman*?? Well, I guess the whole point of this is that women in general have every bit of ability that men in general have. I suppose that includes the "ability" to be stupid. Chris Christopher Smith, Perl Developer Amdocs - Champaign, IL /usr/bin/perl -e ' print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n"); '

22 years, 8 months

Explain the NeXTStation "dim monitor" problem, etc...

by csmith＠amdocs.com

> -----Original Message----- > From: ard(a)p850ug1.demon.co.uk [mailto:ard@p850ug1.demon.co.uk] > Look for a pot marked 'screen' or 'g2' or something like > that. It's often > on the flyback transformer in small monitors, could be elsewhere on > larger/high end ones. For the record, it's "white level" on my monitor. :) It's also very hard to get at without a pot tweaker (have to get some of those one day...) > Turning this up might help. The cure might not be permanent > (in fact it > might casuse the CRT to fail sooner), but it's worth a try. We'll see -- it's ok for now. > Do take care when working inside a monitor. There are some nasty high > voltages in there. Although IMHO the CRT electrode voltages are less > likely to kill you than mains (simply because the CRT > electrode supplies > can't source much current), a shock from one of them can be > nasty, and > might cause you to jerk back and cut yourself, or break the CRT, or... Indeed. I know, but thanks for the warning anyway. FWIW, the Megapixel monitors are completely shielded even once you open the plastic. There's a cutout in the shielding for each pot, and looking in with a flashlight, I can't see much of a way to contact anything except the pots. In other words, this is probably pretty safe on one of these. > If you've not been inside a monitor or TV before, then there's a > reasonable set of safety precautions in the sci.electronics.repair FAQ I might look at that anyway. Chris Christopher Smith, Perl Developer Amdocs - Champaign, IL /usr/bin/perl -e ' print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n"); '

22 years, 8 months

OT email response format (was Re: TTL computing)

by csmith＠amdocs.com

> -----Original Message----- > From: Doc [mailto:doc@mdrconsult.com] > On Tue, 16 Apr 2002, Christopher Smith wrote: > > they really hate for people to put any software on their system > > (typical windows-using mindset, but let's not get into that :), > Umm, I had the misfortune to run a Windows9x network for a couple of > years. 30+ machines and 50+ belligerently clueless > archeologist users. > If I could have stopped those idiots from installing *every* browser > plugin that came along and $3 cut-out software, I'd have had half the > repairs to do. > That _is_ a Windows-admin mindset, borne of much painful experience. I was wondering whether I would get this reply, and I have just one thing to say to it: You're absolutely right. I wouldn't trust people to *breathe* on a windows machine, personally, because windows can't handle it. It was the "windows using" part that I really dislike. The mindset is just a symptom. ;) Now if you'd like to talk about people who think that this is a natural way for a computer to behave, that's something else entirely. Ok, that was at least two things, I guess... Chris Christopher Smith, Perl Developer Amdocs - Champaign, IL /usr/bin/perl -e ' print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n"); '

22 years, 8 months

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 April 2002