Hi folks,
Seems like my webserver was hacked on xmas eve by someone who managed to
install a 'nice' little script called c99shell; fortunately they left their
IP address kicking around and it resolves to a company called Staminus
Communications in Fullerton, CA. Since the majority of this list is US based
can anyone tell me if it's worth flinging them a message to abuse@ giving
the culprit's IP address? I've already told my ISP over here but I doubt
anything will happen.
Message me off list if possible please, Jay, apols for the off-topic noise!
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
Jobs has announced a name change:
"SAN FRANCISCO (AP) - Apple Computer CEO Steve Jobs on Tuesday made the
company's long-awaited jump into the mobile phone business and renamed the
company to just "Apple Inc.," reflecting its increasing focus on consumer
electronics.
He said the name change is meant to reflect the fact that Apple has matured
>from a computer manufacturer to a full-fledged consumer electronics
company."
I wonder if "devolved" or "degraded" might better describe the change than
"matured".
Bob
_________________________________________________________________
Get live scores and news about your team: Add the Live.com Football Page
www.live.com/?addtemplate=football&icid=T001MSN30A0701
On 1/10/07, Brad Pritts <bpritts at pritts.com> wrote:
> Well, we used lots of PDP-10's in the timesharing... business in
> the '70's and '80's. By the late '80's this business was dying fast. But it was fun.
Indeed.
> Yes, Compuserve was a big player...
There are still 36-bit machines (Systems Concepts SC-40s, IIRC)
running in Columbus at what _used_ to be called CompuServe
Headquarters (now just another AOL campus :-/ ) They got rid of the
DEC-manufactured machines well over 10 years ago, but still run their
endlessly hacked version of TOPS-10 on real (not emulated) 36-bit
hardware.
I haven't seen them since 2003, but at that time, there were more SC
machines at the WorldCom data center in Hilliard, OH (at what was
_going to be_ CompuServe Headquarters before the company was bought
and divided). I was told that WorldCom had to keep them running for
some obscure billing app that was written in FORTRAN and couldn't be
ported (or at least had been the subject of several failed attempts to
port). Given the history of things, I would think it was full of
CompuServe extensions, perhaps what they called XF4, perhaps something
descended from that.
So in Central Ohio, at least, 36-bits survived into the 21st Century
for commercial usage. Personally, the last "productive" thing I did
was to run Zork under the Panda distro of klh10/TOPS-20. I used to
have a 36-bit account when I worked at CompuServe, but they'd cleaned
all the old "service" menus and items off before I started there - it
was an empty shell of its former glory by 2001.
-ethan
It just dawned on me something that might be helpful... a quick list of the
most relevant documents to look at first when you get your first HP 21xx
box. Fortunately, Al at bitsavers has made a concerted effort to put up docs
for these boxes, there's a lot of good info there - probably everything
you'd ever need. Here are the manuals I'd suggest getting first....
For the hardware.....
If you read nothing else, here's the one to read even for folks just curious
what these boxes are. Very short (50 pages), quick read, but informative:
Whoops... wow, apparently there's no 21MX E or 21MX F short user guide on
bitsavers. Wierd! So there's no step by step tutorial on how to use the
front panel, etc. My best suggestion - skim the 2100A user guide. The front
panel is much different, but the instruction set (a subset), I/O
architecture, etc. is pretty much the same. The main difference to keep in
mind... the MX's have a store button. Use it :) 2100's autostore if you incM
or decM or select a different register (select the register you're already
viewing to revert contents). The 2100 doesn't have loader roms cause it's
core (so MX's have a IBL button to load a given rom into upper ram). I need
to get Al a 21MX E or F short user guide to put up on bitsavers, that's a
big omission. The 2100 variant is here:
http://bitsavers.vt100.net/hp/21xx/02100-90001_2100refManDec71.pdf this will
get you the basics of your machine.
Next essential reading to learn about setting up & configuring your
machine...
http://bitsavers.vt100.net/hp/1000/12992-90001_loaderRomsApr86.pdf describes
what loader roms are, what they do, how to install them, including source
code listings. Essential for learning all about booting your machine.
http://bitsavers.vt100.net/hp/1000/12791-90001_fwInstRef_Feb86.pdf describes
what firmware exists, what boards exist for you to install firmware in to,
and how to do so. Includes not just firmware options, but base set firmware
as well. You'll need this, it's the second thing to check if your machine
doesn't boot.
http://bitsavers.vt100.net/hp/1000/5955-4310_stdPerfMem_Apr79.pdf describes
the different memory boards & controllers & accesories, how to
configure/jumper them and how to install them. Standard Performance memory
only. One of the first things to check and change.
http://bitsavers.vt100.net/hp/1000/5955-4311_highPerfMem_Dec83.pdf same as
above, but for High Performance memory.
For any interface boards in the rear of the computer, see the manuals here:
http://bitsavers.vt100.net/hp/21xx/interfaces/
Now... the heavy duty everything you could possibly need in the future
definitive reference....
http://bitsavers.vt100.net/hp/1000/1000_MEF_EngrRef/
For diagnostics:
http://bitsavers.vt100.net/hp/1000/Diagnostics/02100-90157_Oct-1980.pdf This
is the diagnostic configurator manual. It's the program used to load all
other diagnostics. Learn this one well. Note - older diagnostics exist that
are standalone. Some (not all) standalones CAN run under the diagnostic
configurator. I'd suggest just learning the configurator and sticking to the
diagnostics which run under it (all are available).
http://bitsavers.vt100.net/hp/1000/Diagnostics/ is the main directory of
diagnostic manuals. Each diagnostic has it's own manual.
Note: HP diagnostics are (apparently) unlike DEC diagnostics for the 11/45
(my own experience, not neccessarily universal fact). The HP diagnostics
work, and work well/right/AsDocumented. They are extremely thorough. They
ARE the best and recommended test for if a given card is working properly
before proceeding to attempt running anything else. If a card doesn't pass
diags, DONT bother trying to use an OS/application to test it. If the card
doesn't seem to work with the application, the diags ARE the best way to
troubleshoot. They often tell you what section (or chip) on a card is
suspect. The diag manuals on bitsavers aren't the complete set, nor the
latest set. I have been working for some time on putting together a CD that
contains the entire latest (last) diagnostic library for HP1000 stuff,
including all manuals, source code, object code, and assembler output
listings (with memory addresses). That will fix the above lack of info :)
Once you have general 2100/21MX knowledge under your belt from the above, if
there is just one manual you should keep handy... it's the ce handbook. It's
a quick-reference cheat sheet on most of the above manuals. At least in the
CE handbooks I have, little attempt is made to explain anything. It's just
quick reference for jumpers, installation, etc. Note that it also includes
quick reference information for many operating systems & software. The link
is:
http://bitsavers.vt100.net/hp/1000/5950-3767_M-E-F_CEhbk_Jul84.pdf
For operating systems:
TSB:
http://bitsavers.vt100.net/hp/2000TSB/ contains the starting point for the
documentation you'll need/want.
RTE:
http://bitsavers.vt100.net/hp/1000/RTE-IV/http://bitsavers.vt100.net/hp/1000/RTE-IVB/http://bitsavers.vt100.net/hp/1000/RTE-6VM/
HP-IPL/OS:
http://www.infionline.net/~wtnewton/oldcomp/hp2100/
Hope this all helps!
Jay West
From: Scott Quinn <compoobah at valleyimplants.com>
>Pat wrote:
>
> On Tuesday 09 January 2007 21:16, Richard wrote:
>> In article <2c9905e7a0917a23c18369f94e997689 at valleyimplants.com>,
>>> Especially interesting given the scorn that the DEC-VAX agreement
>>> from the '70s had.
>>
>> Come again? That reads like a total non sequitur to me.
>
> He's probably referring to the agreement that DEC had with the company
> that makes VAX vacuum cleaners, for both of them to be able to use
> the "VAX" name for their respective products, in each other's country.
>
>As I understand it, DEC agreed not to make consumer goods, and VAX
>agreed not to make computers. To an adolescent mind back in the mid
>'90s it seemed a bit absurd and a waste of time, but maybe not so much
>anymore.
See: Apple Computer v Apple Corp
I'm looking for the cable that goes from a KLESI-UA card (M8739) to the I/O
bulkhead on the back of an 11X44. In the absence of that, would anyone know
for sure the part number for said cable? I would think it would be in the
KLESI manual, but I don't seem to see one on bitsavers (other than prints
for the Qbus version).
Thanks in advance!
Jay West
> From: Richard <legalize at xmission.com>
>
> Ah, so the mystery of who this "marvin" guy is, is finally solved! :-)
>
> Seriously.
>
> I have looked at a *lot* of your adds on vintage computer marketplace :)
Thanks! If everything that I sold or tried to sell on VCM, VCF, Ebay sold, it
wouldn't make a dent ... at least that I would be able to see :).
I could put up several thousand items, and that *might* start to make a dent.
The problem there is listing and packing time. I would *really* like to play
with some of this stuff, but it is just too much stuff right now.
Marvin