Season's Greetings,
Well, today, I finally removed my CDC 9" SMD disk drive from the
living room; getting it down the basement steps was fun. Anyway, now
it's only a few feet away from my 11/73 and 11/44. The 11/73, running
RT-11 and RSX-11, already has two, much smaller, 8" Fujitsu SMD drives
in it.
Now then, I've got an RL02 pack labeled RSX-11M, which I'm hoping
contains a complete RSX-11M distribution. If I can get an RL02
controller board for the 11/73, will there be any problem with just
connecting one of the SMD cables to the CDC drive and copying RSX-11M
onto it? Should I be able to boot this from any PDP-11? One note:
this CDC drive appears to be configured for drive select 1, not
0... does anyone know where I can get one of those little square
buttons used to select drive 0?
When I get the intermittent CPU problem on the 11/44 fixed, and find a
UNIBUS SMD controller, can I just attach the CDC drive to the 11/44 and
have it boot and go, or will I need to reconfigure something?
Thanks for any info. that anyone can provide about this!
--
Copyright (C) 2000 R. D. Davis "The best way to gain a true understanding of
All Rights Reserved Wile E. Coyote on the Roadrunner cartoons is to
rdd(a)perqlogic.com 410-744-4900 fly, head-first, off a horse into something like
http://www.perqlogic.com/rdd a fence or a tree; trust me, this works." --RDD
Hi all
>From: John Lawson <jpl15(a)panix.com>
>
> I have a Pentium I wintel box which I've had for nearly five years.
>It's 1.9 GB HD has been slowly developing bearing whine for the last
>several months. It is getting noticibly louder now and I'm sure this
>faithful old HD is nearing the end of it's earthly sojourn.
>to move the data.
I just did this to a Windoze 95 box. Firstly, I put in the new hard drive
and installed Windoze on it. Meanwhile, I stuck the old drive in a Linux
box and made a big tarball. Then, I restored the tarball on to the
new hard drive.
Reasoning: the tarball gets all the files, except the bootfiles, and those
get sorted out by the new install.
Won't work (yet) for NTFS, tho.
W
I've updated my "House of VAX" pages at
<http://www.mcmanis.com/chuck/computers/vaxen>
Check it out, especially the 'panels' section that talks about console
bulkheads.
--Chuck
>I recently picked up a Fujitsu M2266SA HDD. This is a 1M SCSI
5 1/2 " drive with a black bezel like the IBM-PC MFM drives and
Ah thats 10mb if memory serves.
>will fit in the same space. The vendor said it was SCSI-1 but
TheRef says it is SCSI-2 and Fujitsu doesn't say.
Difference is max data rate and some higher level commands
added. SCSI-II is backward compatable.
>I have a heavily modified PC(5150) with an Intel 386 Onboard card
as Allison has on her Leading Edge 8086 (BTW, I have a lead
>ajp < to someone that has the mem-expander daughter card)
It's an Inboard386... a meg or memory for that would be great
if possible.
>However I have no info on whether it would be possible to add a
SCSI card to an IBM-PC. I have an Adaptec 1522A ISA SCSI card
and likely others in my card box. Was there a SCSI card for the
PC ? If so, would this possibly, with this configuration, allow you to
It's doable, the only reason SCSI was not commonplace in PCs
the was the significantly greater cost at the time. Also back then
PCs could barely enjoy the potential performance advantage.
Allison
In a message dated 12/29/2000 9:13:20 PM Eastern Standard Time,
mikeford(a)socal.rr.com writes:
> Like I said, not really a call for help, just a this is what I did and
> where it got me, so be carefull with memtest86.
I downloaded and ran Memtest86 on my Cel 500 w/144 MB SDRAM. The memory
passed and the machine suffered no harm.
As Sellam and Wizard suggested, it was probably just a coincidence that your
hdd croaked after running this program.
Also, your mention that it took you 3 attempts to create the bootable disk
suggests that your download may have been faulty. If the code was damaged
during transmission then it's possible that running the program could have
caused trash to be written to the hdd. Or maybe your fdd is flaky and the
boot disk wasn't right.
A bummer, at any rate :>(
Glen
0/0
On Dec 29, 15:46, David Gesswein wrote:
> >From: pete(a)dunnington.u-net.com (Pete Turnbull)
> >> 40 pin connector is numbered
> >>
> >> 1 (A) 39 (UU)
> >> 2 (B) 40 (VV)
> >
> >ObNitpick: That's the reverse of the conventional numbering; Berg
> >connectors with letters have the red stripe at the A end, which is on
the
> >left of the pin header (looking into the pins) while all other headers
> >which are numbered have pin 1 on the right.
>
> Yup, how about
> Looking into pins of 40 pin male connector numbering is
>
> 2 (A) 40 (UU)
> 1 (B) 39 (VU)
>
> I think both the numbers are letters were otherwise correct, just the
> summary diagram was wrong.
That wasn't what I meant. Berg label the connector pins starting from the
opposite end of the connector from the rest of the world, so what I meant
was that on actual connectors, the pins are:
39 (B) ... 1 (VV)
40 (A) ... 2 (UU)
or more completely:
39B 37D 35F 33J 31L 29N 27R 25T 23V 21X 19Z 17BB 15DD 13FF 11JJ 9LL 7NN
5RR 3TT 1VV
40A 38C 36E 34H 32K 30M 28P 26S 24U 22W 20Y 18AA 16CC 14EE 12HH 10KK 8MM
6PP 4SS 2UU
Thus on a cable with a Berg connector, the stripe corresponds to pin A and
goes on the left (as you look into the male connector), and on any other
similar connector (3M, T&B Ansley, ITT, Amphenol, Fujitsu, Molex, etc pin
headers but not D-connectors, for example) the stripe corresponds to pin 1
but goes on the right. That's one of the reasons so many DEC cables have a
"THIS WAY UP" sticker.
Of course, if you use the conventional numbering above, you need to change
your table as well (I've put the numbers in brackets, since it IS a Berg
connector, after all):
DB25 40 pin header
1 C (38)
14 D (37)
2 H (34)
15 J (33)
3 M (30)
16 N (29)
4 S (26)
17 T (25)
5 W (22)
18 X (21)
6 AA (18)
19 BB (17)
7 EE (14)
20 FF (13)
8 KK (10)
21 LL (9)
9 PP (6)
22 RR (5)
10 SS (4)
23 TT (3)
11 UU (2)
24 VV (1)
I've put AA where you had CC -- both are ground on the M7744, but it seems
more logical to pair AA and BB, rather than BB and CC.
--
Pete Peter Turnbull
Network Manager
Dept. of Computer Science
University of York
I've got a DEC monitor labelled VRT13-DA, it has a 9 pin color input. Does
anyone have the specs for this monitor? Can it do 1280 x 1024 or is it 1024
x 768? Does anyone know the pinout for it?
--Chuck
I'm looking for some accessory items related indirectly to my computer
collecting/repairing - can't seem to find them, so thought I'd ask here:
I love my HP 1631D logic analyzer, but it takes up way too much real estate
on my bench. I'd like to get a mobil cart for it, but virtually all the
scopecarts I've seen (like the tek 200) are for small scopes & such... the
1631D analyzer is 16.5 inches across the middle, and 17 inches across the
front (the bezel sticks out a bit on each side). Would anyone have a scope
cart (like a tek 212 or similar) that is for wider instruments that is
excess and would consider selling/trading?
Second, I'm looking for various disassemblers for the 1631D... these came on
3.5 floppy, but I'm not sure what all disassemblers were available for it.
Anyone got this software laying around?
If anyone can help, contact me off-list at west(a)tseinc.com
Thanks!
Jay West
From: Tony Duell <ard(a)p850ug1.demon.co.uk>
>Oh, they're no worse (for HV) than any other mains-powered SMPSU. We've
>had this discussion before, but I still maintain that the most dangerous
>voltage in a monitor is the rectified (and maybe doubled) mains -- 400V
This one uses only direct mains (160V). That bothers me less as it
can't reach out abnd get me.
>at essentially unlimited current. And it's on bare PCB tracks. A lot
more
>likely to do you harm than the low-current 25kV EHT supply that's
>impossible to touch by accident.
There is insulation breakdown, I've been nailed once.
I have experience with HV and High Power as well as big RF so I know
how to avoid getting wacked. I just generally dislike working on
TV/monitors.
>As you doubtless realise, you've got a SMPSU that's shutting down
because
>it thinks it's overloaded.
>From testing that woudl be the case.
>The most likely cause of a real overload is a shorted HOT (Horizontal
>Output Transistor), possibly damaged because of shorted turns in the
>flyback transformer. So testing that transistor (on a heatsink near the
>flyback) is a good first move.
Testing is that it's ok.
>The other thing that monitors suffer from is dried-up electrolytics,
>which therefore have a high ESR. These can cause all sorts of faults,
the test was to bridge the likely candidates.. no joy.
>including a PSU that keeps on shutting down. I'd test all such
capacitors
>in the PSU area. This might even be the cause of the long warm-up time.
Would seem that way but that was before, not it does not power up.
Since it's SVGA and prints for it are unlikely and some of the parts are
oddball enough to not warrent digging too deep.
Allison
The subject (I think) is on topic, the hardware to which I'm refering is
a little too new for us, but I'm gonna ask anyway.
I have a Pentium I wintel box which I've had for nearly five years.
It's 1.9 GB HD has been slowly developing bearing whine for the last
several months. It is getting noticibly louder now and I'm sure this
faithful old HD is nearing the end of it's earthly sojourn.
My fantasy is that I can buy another IDE drive (of somewhat larger
capacity) and just somehow copy the whole thing on the original down to
the new one, without having to go thru the backup/restore/re-auth all the
programs I've got on it. I have 8mm streaming tape backups of the system,
but that's a pain.
I'm living in southern India so 'just pop in to Fry's and get a package
like DriveCopy III' is not an option. :)
Any advice/how-to/magic formulae?
Cheers and Happy NuYeer
John
