>
>Subject: S-100 power supply transformer
> From: "Andrew Lynch" <lynchaj at yahoo.com>
> Date: Sun, 17 May 2009 16:51:44 -0400
> To: <cctalk at classiccmp.org>
>
>Hi! Does anyone know of an available transformer suitable for making an
>S-100 power supply? I need 120VAC input and 10VAC output and +/- 18VAC
>outputs.
>
>The best I solution I can find is two separate 80VA transformers; one
>parallel 10VAC output and another 36VCT output which can be configured for
>+/-18VAC outputs.
Try closer to 8V RMS rectified that will be more depending on load.
Same to the other two. Look up the calulations and see. FYI you also
talking for the 8V line 60,000 to 150,000microfarads (at 15-25V) and
the other two more like 10,000 to 20,000 (at 30V min) microfarad
capacitors..
Also consider a 240 primary to 16V which on 120 will do 8V then.
However common (standard) voltages are 6.3, 12.6, 25.4 and 48 then there
are control transformers like 10V, 18V and 24 and sometimes 36.
>I would prefer a single transformer rather than dual transformers because
>they are the most expensive part of a linear power supply.
You will have better luck with two but you may get lucky. FYI the early
Altair used two.
>
>I know Northstar and Vector Graphic used similar dual output transformers
>but I cannot find anything like them after searching the usual vendors like
>Digikey, Mouser, Jameco, etc. Even transformer manufacturers don't seem to
>carry a stock product of this configuration although you can order custom
>units.
Thos are honking big and intended for the then loaded bus of more that a
few cards. We talking a +8V good for 25-35A. More practical systems
especially those osing newer 64K (on one card) memories tended to require
far less power.
Try digikey and mouser.
In this day and age those are not common and during the golden age of S100
they were still a bit oddball and not cheap.
Allison
>
>Thanks in advance for any help. Your ideas greatly appreciated.
>
>Thanks and have a nice day!
>
>Andrew Lynch
I'm trying to get an old M4 9905 tape drive running with my PDP-11/73's
Pertec interface and I'm not having a ton of luck. Currently attempting
to boot from known-good media spins the reels a bit and then gives me an
"Error 21 - Drive Error" from the 11.
I want to check that the drive is configured correctly. There are
evidently settings that can be tweaked by running internal diagnostic
programs from the front panel, but I don't know what the codes are. I
haven't had much luck finding a manual on the 'net (Bitsavers has
manuals for the 9914, which is similar but not similar enough that the
diagnostic programs are the same.)
Anyone have a manual or a diagnostic listing for this drive?
Thanks,
Josh
Ethan Disck Wrote:
> 35Y3D / Apr 1977 - 7 wires as previously described
> 35AF4A / Jan 1081 - 11 wires as previously described
Yes, there are a couple of different Touch Tone Pads floating around. The main difference between them is a couple of things. The ones with more wires are designed for use with SpeakerPhones ("List 3" and the like for those reading BSP's at home). The extra wires do a couple of things. One set mutes the speaker a bit (an extra set of contacts) when dialing so you won't get blasted with the tones on the speaker (normal use is to really send LOUD tones down to the central office). The other wires provide power to the oscillator when using it "hands free". Normal power is derived from the telephone line, but with speaker phones, it is a bit different.
Hopefully this will explain things.
My problem is that I have a couple of "solid state" (non-coil) pads (they use an IC) and they are only compatible with non speakerphone telephone sets. Here at my parents house, they have three 2565 sets, one which is with a speakerphone. I would like to replace the old single transistor L-C pads (they turn on tones a bit mushy) with more modern ones, but they don't have all the wires. One of these days I'll figure out how to make do. Ackk! another "project"...
>I'm interested in knowing what the "remote program" connector shown on
>the back of the display does.
>
I have the maintenance manual.
Pin 1,2 and 14 Optional connection for X axis signal input. Disconnect the
coaxial cable from the X axis BNC connector. Connect the center conductor
of the coaxial cable to pin 1 and the shild to pins 2 and 4 (I think the 4
is a type, should be 14).
Pin 3,15 and 16 Option connection for the Y axis signal input. Disconnect the
coaxial cable from the Y axis BNC connector. Connect the center conductor
of the coaxial cable to pin 15 and the shield to pins 3 and 16.
Pin 4,5, and 17 Optional connector for the Z axis signal input. Disconnect
the coaxial cable from the Z axis BNC connector. Connect the center conductor
to pin 4 and the shild to pins 5 and 17.
6 NON-STORE is a function which is forced by grounding pin 6 to pin 19
(except when using the TEST SPIRAL switch).
7 ERASE INTERVAL is a signal output that goes from +10V to +0.3V during the
interval of erasure.
8 WRITE THRU is accomplished by grounding pin 8 to pin 19 and exciting the
Z axis.
18 ERASE FUNCTION is obtained by grounding pin 18 to pin 19.
19 PROGRAM GND is the ground reference for remotely connected external
functions.
20 VIEW MODE is a function that is forced to exist as long as pin 20 is
grounded to pin 19.
Several people replied to me privately about my previous post on bitsavers,
and apparently got the impression that bandwidth was tight on the server. It
is not a case of bandwidth being tight at all, far from it. It's a matter of
fairness, the bandwidth is to be distributed among all the mirrors. If
you're not prepared to take some real bandwidth, you probably shouldn't be
mirroring it.
We've got truckloads of available bandwidth. In the past I had throttled
bitsavers down because I couldn't find a good fair way to share bandwidth
amongst the mirrors. Now that I have such a way, bandwidth restrictions have
been completely lifted. Enjoy :)
Jay
Tobias Russell <toby at coreware.co.uk> wrote:
> Thanks for the advice. I had already started by the time I ready your
> reply so I have images for now, although it would be easy to go the
> extra step by mounting my images and extracting the individual files. I
> might have a hunt to see if there are any linux/unix utilities out there
> so I can automate exracting the individual files from RT-11 images.
Count me as a voice against extracting the individual files. It's way
better to make copies of the whole floppies. You can easily do the
extraction afterwards if you have a program that understands the file
system. And it will preserve the actual floppies as well, which can then
be recreated by someone who don't have the tools either.
Also, if you have some bug in the extraction software, you still have
the original around to repeat the process if you want to.
Also, there are file systems that PUTR don't understand, not to mention
that there can be issues with preserving some kind of information when
extracting files to another type of file system.
>
> If anyone is interested, the fruits of my labours can be seen here:
>
> http://www.pdp11.co.uk/2009/05/17/rt-11-rx50-disk-images/
>
> Quite a few of the files probably already exist in other archives but
> some of the stuff is probably new. I've not had a chance yet to look
> through the disks in detail but will annotate up the contents when I get
> a chance.
Nice. Keep up the good work.
> I've just been given a set of microRSX 1.0 distribution RX50s so I will
> put those up next.
That's something you don't want to point PUTR towards...
Johnny
>
> Thanks,
> Toby
>
>
>
> On Sat, 2009-05-16 at 17:38 -0700, Lyle Bickley wrote:
>> > Toby,
>> >
>> > On Saturday 16 May 2009, Tobias Russell wrote:
>>> > > I have a large box of RX50 disks that I would like to archive onto
>>> > > modern media to ensure they are preserved. I've built up a machine with
>>> > > a 5.25" floppy drive and install DOS and PUTR.
>>> > >
>>> > > Is the best method to archive them to:
>>> > >
>>> > > MOUNT B: /FOREIGN /RX50
>>> > >
>>> > > followed by:
>>> > >
>>> > > COPY/DEV/FILE B: [filename]
>>> > >
>>> > > for each of the disks I insert?
>>> > >
>>> > > I was pondering whether I should use the /BINARY flag on the copy, but
>>> > > I've not seen this mentioned on other webpages I have read.
>> >
>> > Since PUTR "understands" multiple filetypes, I have found it is much better to
>> > save the contents of each floppy (RX50) to a separate directory - but NOT as an
>> > image file, but rather as individual files. That way you can later use PUTR to
>> > create logical media of any form - say RL02, RX01, etc. from the captured
>> > files.
>> >
>> > Assuming drive "B:" is your 5.25" drive, and the OS is RT11 you would do the
>> > following:
>> >
>> > MOUNT B: /RT11 /RX50
>> > then
>> > COPY B:*.* .
>> > and you will have captured the individual files that were on the RX50.
>> >
>> > When you reverse the process to recreate a diskette (RX50, RX23, RX01, etc.) be
>> > sure to use a SET B: type; i.e., SET B: RX23
>> > then
>> > FORMAT B: /RT11 /RX23 (or whatever)
>> > then
>> > COPY *.* B:
>> >
>> > NOTE: Be absolutely sure to SET COPY BINARY before you do anything. For some
>> > unknown reason, the PUTR default is ASCII. (I have a SET COPY BINARY in PUTR's
>> > initialization file - to be sure I never forget to do it ;-)
>> >
>> > Cheers,
>> > Lyle
>> > --
>> > Lyle Bickley
>> > Bickley Consulting West Inc.
>> > http://bickleywest.com
>> > "Black holes are were God is dividing by zero"
>> >
>
--
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
cctalk-request at classiccmp.org wrote:
> Message: 26
> Date: Sat, 16 May 2009 12:31:25 -0400
> From: Ethan Dicks <ethan.dicks at gmail.com>
> Subject: Re: DEC ST506 Interface Adapter Part No 54-17003-01
> To: "General Discussion: On-Topic and Off-Topic Posts"
> <cctalk at classiccmp.org>
> Message-ID:
> <f4eb766f0905160931veb8ff8ax6957d5c2abd0d432 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Thu, May 14, 2009 at 5:51 PM, Julian Skidmore
> <julianskidmore at yahoo.com> wrote:
>>> >> I thought it could only format "known" disk types, not arbitrary disks
>>> >> (a firmware limitation in the formatter application, not a hardware
>>> >> limitation).
>> >
>> > Surely, it's possible to hack an RQDX3 controller's ROM to support arbitrary geometries?
>
> The geometries aren't in the RQDXn ROMs - the formatter application
> writes them to the disk during the formatter process.
>
> There are three VAX formatters I know of - the ROMs on a VS/uV2000,
> the Customer Runnable Diagnostics (CRD) and the Field Service
> diagnostics.
>
> I know the CRD formatter only allows you to select known drives from a
> menu table and the Field Service formatter allows you to enter
> arbitrary values (i.e., has a menu plus a fill-in page). The
> ROM-based formatter on the VS/uV2000 was the one I appear to have
> mis-remembered the capabilities of.
>
> No hacking of the RQDX3 is required, just selection of the right
> formatter application.
However, all information is not just located on the disk either.
The RQDX1 and RQDX2 use a format that is incompatible with the RQDX3. In
order to use an RD52 (for instance) that has been formatted on a RQDX2
on a RQDX3, you need to reformat it...
Also, an RQDX1 or RQDX2 cannot control an RD54. No matter what
formatting program you use. You need the RQDX3 for that.
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
Has anyone ever dealt with Vintage Processors in Santa Cruz, CA? They
have an EBay store at http://stores.ebay.com/Vintage-Processors
I ask because some of the prices that are listed struck me as a bit
'over the top' (such as a DG Eclipse S/120 for $1000?).
Just curious...
Mark Davidson
mdavidson1963 at gmail.com
Hi! Although there hasn't been much interest here in my S-100 backplane
prototype project on CCTALK progress is continuing. Thankfully I have found
several brave volunteers to test these initial units and help share the cost
of the manufacturing run with me. I appreciate their help immensely.
Of the eight initial units, I've shipped six and one more is committed. I
still have one PCB left if there is anyone on CCTALK that would like to join
the project.
Much of the testing has already been done and some things have been improved
but the basic design is proving to be functional and everything basically
works. There are some improvements I am keeping track of such as better
labeling on the PCB silkscreen but nothing which yet warrants a "respin."
Drawings of the N8VEM S-100 backplane prototype are available on the wiki.
The N8VEM S-100 backplane prototype PCBs are $32 each plus $2 shipping in
the US. Shipping overseas is typically $5.
http://n8vem-sbc.pbworks.com/browse/#view=ViewFolder
<http://n8vem-sbc.pbworks.com/browse/#view=ViewFolder¶m=S100>
¶m=S100
In addition to the S-100 backplane prototype PCB there are drawings for the
N8VEM S-100 prototyping board which I am developing. There have been
several revisions and I am not done with it yet. If anyone is interested
please contact me off list. I do not have a firm estimate on the price of
the N8VEM S-100 prototyping board but I believe it will be in the mid $20
range probably around $25 each plus shipping.
Any comments, suggestions, or questions are welcome. Please be constructive
and postive! Thanks and have a nice day!
Andrew Lynch