> -----Original Message-----
> From: Dan Wright [mailto:dtwright@uiuc.edu]
> hmmm...I'd only need the latter :) anyone have any idea where I could
find
> it? might the drivers come with AIX 4.3.2? I sort of doubt it, but you
never
> know...
I know of somebody who's got some RS/6000 machines which he believes might
contain the drivers on their internal disks. He hasn't started any of them
up yet, though, AFAIK. He's promised me a copy of the drivers if he has
them, but as to when he'll get around to checking, your guess is as good as
mine.
I have heard (please let me know if you find out differently) that they
weren't part of any AIX distribution media, but were separate.
Regards,
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
For me:
I like to find systems with a National Semi 32000 series chip, esp. NS32532.
Not rare, per se, but very uncommon.
For really rare, I'd think:
A Lilith or a Ceres
An Ampere APL machine
Anything iAPX-432
Ken
> -----Original Message-----
> From: r. 'bear' stricklin [mailto:red@bears.org]
> IRIX only runs on MIPS. Some other SVR3ish software I can't
> remember the
> name of ran on the m68k boxes.
I talked to the guy who handles the IRIS 2000/3000 FAQ, and he seemed to
think that it was "IRIX." I would be interested if you find out more
details.
Regards,
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
>From: Warren Toomey <wkt(a)minnie.tuhs.org>
>To: The Unix Heritage Society <tuhs(a)tuhs.org>
>Reply-To: wkt(a)tuhs.org
>X-Mailer: ELM [version 2.4ME+ PL68 (25)]
>Subject: [TUHS] Anybody want 3B2 or 6300+ software/documentation/hardware?
>Date: Wed, 19 Dec 2001 08:49:30 +1100 (EST)
>
>All,
> Aharon Robbins just passed this on to me. Maybe some
>of you are interested in this.
> Warren
>
>----- Forwarded message from Aharon Robbins -----
>
> From: Aharon Robbins <arnold(a)skeeve.com>
> To: wkt(a)tuhs.org
> Subject: would any of this be useful to TUHS?
>
>I am cleaning out my attic. What does that mean?? It means a lot of
>AT&T documentation and software needs to find a home to avoid ending
>in the dumpster. I have documentation and sfotware for the 6300+ and the
>3B2. Some of it still in the original shrink-wrap.
>
>And yes, this is on topic. I also have quite a bit of software and
>documentation for the Unix-PC as well. Much of this still in the
>original packaging. OS, Development sets, utilities. everything must
>go. I also have three complete Unix-PC's and two without disks or
>heads but with functional motherboards. At least all of this stuff
>was functional the last time I actually turned any of them on. I have
>one that I just fired up (that's already been claimed) to test it and
>it works fine, so i assume the same is true of the others. I would
>probably be willing to let all of them go at this point. Nice machines,
>but my PDP's and VAXen need the room.
>
>Now the only string. I will not ship any of this. it is located in
>NEPA in the Scranton/Wilkes-Barre area and must be collected. And it
>must be soon.
>
>One person can claim it all and then ship it to others if they wish,
>or people can email me asking for particular packages. First come,
>first served. If you know of any other places where there might be
>interest in the 3B2 or 6300+ stuff feel free to forward this message.
>
>All the best.
>bill
>----- End of forwarded message from Aharon Robbins -----
>_______________________________________________
>TUHS mailing list
>TUHS(a)minnie.tuhs.org
>http://minnie.tuhs.org/mailman/listinfo/tuhs
So... down a path I've not gone in a while.
Just got a system for my business (it's classic too, I'll ramble on that
later) and part of it is a Wyse 386 box running SCO System V Xenix.
That's the good part...
Now, the bad... while cleaning it up (about 6 lbs of dust in the box) and
getting ready to image off the hard drive (backups are always a good
thing, no?), either I fumble fingered something or my drive test/backup
program was having a 'bad hair day', cause it nuked the boot record on the
drive! (AARGH!)
'Course... just to add insult to injury, it then went happily ahead and
ran off the image of the hard drive just like I wanted in the first place,
minus a valid boot record of course. B^{
So... would anyone perhaps have an appropriate boot disk on a 3.5HD
floppy that I could get, and any convienient hints on how to regenerate
the boot for this thing?
Many thanks;
-jim
---
jimw(a)agora.rdrop.com
The Computer Garage - http://www.rdrop.com/~jimw
Note: the 'computergarage.org' domain is currently offline. The original
'Garage' site (URL above) is still out there and is currently being updated.
> On Tue, 18 Dec 2001, Russ Blakeman wrote:
>
> > How in the hell did this list get into racial slang anyway?
>
> The same way it gets into cats, food, cars, guns, <insert other
> inappropriate topic here>...
>
> A lot of folks here need to get out more often.
<sigh> If only there were someplace to get out *to*... maybe
Bubba and Billy Joe are slugging it out again at the Silver
Dollar... that's always a good show.
We used to have some very cool, dark, smoky blues clubs
around in the 80s... then blues got popular with Gen-X-ers
and it all moved downtown to clean, glitzy, neon-infested
juke joints...
I might point out that some off-topic threads have gone
private and ended up being the beginning of more than one
new friendship...
-dq
From: Ben Franchuk <bfranchuk(a)jetnet.ab.ca>
>What I wanted was a 12/24 bit CPU. Other than the 6100 cpu ( over
>priced? )
>by DEC nobody has ever put a octal machine 24:12 or 18:9 or 36:18:9 on a
>chip.
>(Ignoring PDP-10 stuff) to my knowledge.
Right on very few if any! Most went to byte wide or multiples of byte
wide...
give a guess why? I've always felt that 24bvits was a good starting point
for a clean slate machine or a stretched PDP-8. By Stretched 8 I mean
just add 12 bits to the right and extend everything else the same amount,
gives you a 500k page address and a 16mb machine address. So what
if the instruction set is thin if done with modern FPGAs an easy 100ns
(12x faster) instruction cycle time would be fine.
>I have yet to see a nice micro-code example. All the micro-code
>I have done ( on paper ) needed 32+ bits for a 2901 design.
>Also about 2K of ROM. TTL controller. It got messy after you added
>a MAR, In/out registers, and stuff like opcode decoding.
At 48 bits it gets better as then your not horozontal encoding.
Also if you use a prom to do the opcode to microaddress translation
it looks nicer and cuts a lot out. Also using the 2901 registers for
the PC and all saves a bit too. Still, as you noticed a lof of storage
bits for managing traffic are incurred. A combinational state machine
is simpler in some respects but far less flexible when it comes to
fixing a bent opcode.
>> Now that's depressing. ;)
>You tell me how I can make $$$ and I will not move to seattle.
I can't but, some things still taste bad. ;)
Allison
From: Fred Cisin (XenoSoft) <cisin(a)xenosoft.com>
>Ah, Allison, where have you been all of my life?
Ah, right here.
>If you would have told me that 15+ years ago, you would have saved me LOTS
>of time and effort putting tape over index holes, making cables with
>switches to interrupt the index signal, etc.
;) and if you havd called NEC during the '79 to '83 time frame you might
have gotten me there. One trick for the short index or late index problem
of most 1793 formats is solved by using a oneshot that is a delay of index
around 98% of rotation time, once it fired the resulting pulse looks earlier
and the index window now has the right time. That makes it easy to wind out
the VCO sync delay in the 765.
>With a 765, if I want to read a sector from the second side of most Kaypro
>disks, I need to feed it a value that matches the WRONG value that's in
>the sector header for the H field. With WD, that field can be ignored.
Ah yep. I did a two sided to match an oddball that had sectors 1 to 18
on the top and 19 thru 36 on the bottom. no problem.
>Raw v formatted track read has advantges and disadvantages. The 765
>approach is very handy for reading a bunch of "normal" sectors. The WD
>approach makes it possible to read MFM that does not follow
>"normal" sector header standards, such as Amiga, or some TRS-80 address
>marks.
Yep, then again depends on what your doing too. If you building a data
recovery machine a 1793 may be it. Then again you'll need a 1771 too
as there were 1771 formats that were unreadable by the DD 1793. If you
building a virgin CP/M machine that needs to read a smaller subset of
media... 37c65 or later is far cheaper and easier.
>Personally, I would have preferred the "raw" approach of the WD, but I
>make no claims to be representative of the marketplace.
It's only useful for the special cases. For everything else you wnat a
track
or cylinder without the junk.
Allison
Marked in black felt-pen on the drive: "Amstrad PCW 8256." Cable is
attached. Unit is untested and is yours for postage from Orlando FL.
Any interest?
Glen
0/0
At 03:46 PM 12/14/01 -0500, you wrote:
>Allways wanted an SGI INDIGO.
>Allways wanted an Atari 1450xld and:
>an Atari 815 disk drive
>A trak disk drive
-snip-
I want a CRAY.
--------------------------------------------------------------
Carlos E. Murillo-Sanchez carlos_murillo(a)nospammers.ieee.org