>
>Incidentally, do you know if the PX4, PX8, PF10 and HX20 all use the same
>adapter?
>
>
Both HX-20 and PX-8 came with some variation of the HOOAA? Adapter
(HOOAAG for 220V, HOOAAU-A for 240V, ...)
Not sure about the PX-4, which has smaller cells, but charges ok with
the adapter mentioned above.
You can replace the old C-type NiCd cells with modern NiMh penlights.
The capacity is similar and so is charging (using the primitive way
Epson implemented it). And these are considerable cheaper.
I did make a small page containing the information I have on the PF-10:
http://www.xs4all.nl/~fjkraan/comp/px8/pf10/.
Important to know is that the unit is not designed to be used from the
mains adapter. This is only for charging. Charging and operation should
not be done at the same time.
>-tony
>
>
>
Fred Jan
Hey folks!
I have set up a mirror of bitsavers.org at
http://bitsavers.hachti.de
It is up to date (today) and I will try to keep it available and up to
date as long as my server's hdd space is not needed and the isp doesn't
decapitate me.....
The server is connected with great bandwidth so use it.....
Best regards,
Philipp :-)
Why isn't there a hint on bitsavers - like a cgi which calls "du
-h"....? I didn't know that the archive is around 40GB when I started
mirroring it......
This post will serve 2 purposes:
(a) Let anyone who keeps track note that my e-mail address has changed.
(b) My progress in calculating high precision numbers:
Background: I want to calculate li(x) for Prime Numbers for
2 <= x <= 10 ** n accurate to at least 20 decimal places to
the right of the decimal point. This will require numbers using
REAL * 128 = Unsigned INTEGER * 64 / FRACTION * 64
in order to calculate the natural logarithm, log(10 ** n),
accurate to about 120 decimal places or 400 bits when n = 100,
although initially I will limit the calculation to n = 38.
If anyone is interested, I have finally produced 2 FORTRAN 77
(and many MACRO-11 support) subroutines which calculate:
(i) The reciprocal of an Unsigned INTEGER * 2 to 128, 256 and 512
bits of accuracy
(ii) The natural logarithm of log(p+1)-log(p) where p is an
Unsigned INTEGER * 2 also to 128, 256 and 512 bits of accuracy
I have also calculated log(2), log(10) and log(log(10)) to
128, 256 and 512 bits of accuracy (well the 512 is probably
only 500 bits) so that the values for li(x) can now be done
for 10 <= x <= 10 ** n when n is an INTEGER from 1 to 100.
At the moment, year end housekeeping tasks will occupy my
time for about a month, but I hope to complete li(x) up
to 10 ** 100 by around June.
The final step with be to calculate the value of log(x) for
any INTEGER value of x which also requires the reciprocal
of 1 <= x <= 3 (which should be only a bit more difficult
than 1/3) followed by modifications to the code to increase
the speed of the calculation. I might also be able to write
some NEW instructions for the PDP-11 which will execute under
E11. Probably the most useful would be an Unsigned INTEGER
multiply instruction, especially if it could handle 32 or
perhaps 64 or even 128 bit operands. E11 allows this to be
done in C and X86 assembler. One possible method might be
to use the floating point registers of 64 bits * 64 bits to
produce the 128 bit product. That might increase multiplication
speed by a factor of 10 (reduce multiplications by a factor of 16).
While the subroutines execute under RT-11, there is NO actual
RT-11 dependent code and the code can easily execute under RSX-11
and RSTS/E. If there is any general interest, I can provide
additional details. While there has been a bit of actual
testing using a PDP-11/73, most of the work has been done under
E11 on a 750 MHz Pentium III under Windows 98 SE. This provides
speeds about 15 times a PDP-11/93 (or about 25 times the speed
of the PDP-11/73 for both CPU and disk I/O). I hope to switch
to a Pentium 4 sometime this year.
Any questions?
Sincerely yours,
Jerome Fine
--
If you attempted to send a reply and the original e-mail
address has been discontinued due a high volume of junk
e-mail, then the semi-permanent e-mail address can be
obtained by replacing the four characters preceding the
'at' with the four digits of the current year.
On Jan 2 2006, 14:15, Charles wrote:
> So I flipped the restart switch on the CPU, answered "Y" to
> "Start?" and got a message "Please boot from system disk". I have
> one other disk pack that is known to have come from a PDP-11, so I
> put it in the drive - lo and behold, "Booting up XXDP-XM Extended
> Monitor" followed by ... "V2.4, Rev. E1, booted from DL0, 124Kw
> memory, Non-Unibus system, restart address 152000, type H for
> help".
>
> Looks like I now have a working PDP-11 :)
>
> The pack has 727 files on it whose names are meaningless (to me
> anyway). XXDPXM.SYS etc. is obvious but there are hundreds of
> files from A to Z with names like "VKMHA0.BIN", "ZAFAC0.BIC" and
> some .LIB and .OBJ files too.
>
> What on earth do I have here? Is it something that anyone would be
> interested in copying?
You have the diagnostics. Several places have listings of individual
programs, Henk's site being a good example, and you'll find a set of
documents explaining XXDP on my site, at
http://www.dunnington.u-net.com/public/PDP-11/XXDP.pdfhttp://www.dunnington.u-net.com/public/PDP-11/XXDP.ps is the same
document in its original PostScript form.
--
Pete Peter Turnbull
Network Manager
University of York
Does anyone know of a good on-line reference to VMS internals.
I'm not looking for anything too in-depth. At the moment, I'm
mostly looking for something along the lines of "here are the
major components and how they fit together." I've got most
of an orange wall and a copy of the old software handbook,
but I'm not finding anything like that there. I know about
the VMS Internals and Data Structures book and if I have to
I'll find a copy, but I'm not really looking for something
that detailed anyway.
Thanks in advance,
Brian L. Stuart
>From: "William Maddox" <wmaddox at pacbell.net>
>
>Dwight Elvey wrote:
>
>> Hi
>> Some types of foam don't last long. I wonder if one
>> could make some with closed cell foam instead. It
>> last much longer but is a little stiffer than the
>> foam that they seem to be using.
>> If it is a capacitive you should be able to make
>> new capacitors with some aluminum foil and clear
>> tape.
>
>Aluminized mylar is easy to come by in the form of mylar punched-tape
>stock. It is quite expensive these days, but a single roll would go a
>long way. Also, aluminized mylar is widely used in balloons and novelty
>items, which could be harvested for material. I have no idea if the
>thickness is critical, but this sort of material would likely be much
>more conformant than aluminum foil.
>
>--Bill
Hi Bill
Using the mylar from the balloons seems like the best of ideas.
It is very thin and would most likely work the best.
One could get a hole punch from an auto parts store ( used
for making gaskets ) and make new pads. I have closed cell
foam that is over 20 years old and still fine, unlike the
normal foam used elsewhere that ozone and time have turned
to a gooey mess.
I would say that this makes the keyboards repairable for
someone that want to take the time.
Dwight
--------------Original Message-------------
>Date: Sun, 1 Jan 2006 18:09:45 -0800
>From: Alan Perry <alanp at snowmoose.com>
>Subject: Re: Burroughs L-series
>
>> From: M H Stein <dm561 at torfree.net>
>>
>> A couple of years ago I met a couple of people on here that had
>> Burroughs L-series computers, but lost track of them in the meantime.
>> (I think there's an L5000 at Bletchley, but they probably don't need
>> or want anything).
>>
>> I'm about to toss out the last remnants of my L stuff (programming
>> manuals, memory cards, tape drive, TD-700 display, etc.)
>>
>> If there's anyone out there still interested, send me an email off-list
>> before they go into landfill.
>>
>
>What are the Burroughs L-series computers? I started working for
>Burroughs just before the Sperry merger and I guess I missed the
>L-series.
>
>I collect B1000 stuff (or, I would collect it if I could find anything)
>and acquired a bunch of B20 systems a couple of years ago, so I collect
>them now.
>
>Other than a museum that asked me if I ever found a B1000, I haven't
>found any other collectors of Burroughs stuff.
>
>alan
-------------Reply-------------
Ah, another ex-BBM/Unisys type; hi!
Frank McConnell very kindly directed me to: news:comp.sys.unisys
Don't know how many people on there are collectors, but they're certainly
interested in Burroughs & Unisys stuff.
What are L's? Glad you asked:
The L series was a type of computer that's largely ignored by the
historical community, often written off as _just_ an accounting machine.
First there was the F series which, along with Monroe and NCR
equivalents, could be found in pretty well every small bank back in
the 50s & 60s. Completely electro-mechanical, they were basically
multi-total adding machines with a wide carriage for ledger cards
and journal paper rolls. If you think a Selectric is a complicated
system of levers & springs, you've never seen the insides of one of
these babies; they were "programmed" with different length metal
pins inserted in specific locations in a program panel running the
width of the machine. Printing was done with type bars for the
numeric data and a type box for alpha (if an alpha model).
They were superseded by the E series, which replaced the levers
and springs with discrete transistor logic and core memory (and
an interesting device called a "magnetic core counter"). They also
added the capability to read data off a magnetic stripe on the back
of the ledger cards which stored constant data (client name etc.)
and running totals, and PPT I/O.
The replacement L series started out (L 2000 to L5000) with mechanical
keyboards and a Selectric ball printer, a small fixed hard disk for RAM,
and IC logic. The L6000 replaced the keyboard with an electronic version,
the L8000 replaced the memory with IC's (2102?), and the L9000 replaced
the Selectric ball with a dot matrix printhead. They were programmed
in assembler, Cobol or a Report Generator (usually cross-compiled
on a larger system, although there was an on-board assembler available).
They all had an integrated PPT reader (mechanical or electronic) for
loading firmware, and also programs if there was no cassette or
mag stripe reader. The IC RAM models also had a battery-powered
DC300 tape drive for saving & restoring memory in case of a power
failure.
Optional peripherals included PPT I/O (Tape and cards), up to four digital
cassette drives, a separate batch mag stripe reader and datacomm
(TC series). One interesting feature was the two independent form
tractors on the printer, essentially giving you two (three, if you count
the ledger cards) separate printers, side by side, with only one printhead.
Not all models used ledger cards and, especially with four tape drives,
they made a pretty good all-purpose computer; one of my installations
generated BOMs for an aluminum window manufacturer, for example.
The last models of this type (AFAIK) were the B80 & B90, which added
8" floppy disks, 14" 5MB hard disk cartridges and a video display
(either a Panaplex or a CRT). Aside from the one thing all these
models had in common, the integrated keyboard and wide carriage
console, they had essentially become "normal" mainstream micros
and were superseded by B20s etc.
mike
Anybody have, or know where I can get, a datasheet for these chips I have
some of that are marked "74S409" and "DP8409"? I haven't had much luck
finding one so far...
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, a critter that can
be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin
I had hoped to use the holiday to think this over, however I continue to
receive private email badgering me about the ImageDisk source code.
I received one this evening from a list member who states that I have caused
harm by my development of the program, and apparently I am also being
held responsible for at least one pile of "hard to find" disks that will not be
preserved because of my efforts.
I've had enough, and I don't need this crap.
Effective immediately, I have cancled the ImageDisk project. My offer to
make the source code available by request is hereby withdrawn. I have
removed the images section from my site. If you have copies of any of this
material, I would respectfully ask you to please delete them, or at least not
make my material available. I want this program to have never existed.
--
dave04a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools: www.dunfield.com
com Collector of vintage computing equipment:
http://www.parse.com/~ddunfield/museum/index.html
Hi
Silcon rubber would work but you'd need to press it
to get the lumps out and have a smooth surface.
Dwight
>From: "J.C. Wren" <jcwren at jcwren.com>
>
> I wonder if one could take a thin stiff plastic (perhaps for
>overhead transparencies?), glue it to the foam, and glue that to the
>mylar, then start punching discs. I don't know about the gasket cutter,
>but I have a tool from years ago that was part of a grommetting kit.
>It's a sharp edged steel tool for cutting holes in canvas or rubber, and
>is smacked with a hammer to do the cutting.
>
> You'd need an adhesive that wasn't thick and wouldn't eat the foam.
>Perhaps something like "artists adhesive". I think it's used for
>mounting photos and such, and comes in a spray can. I do remember it's
>fairly thin. I don't know if it would remain sticky enough over time.
>
> --jc
>
>Dwight Elvey wrote:
>
>>
>>Hi Bill
>> Using the mylar from the balloons seems like the best of ideas.
>>It is very thin and would most likely work the best.
>>One could get a hole punch from an auto parts store ( used
>>for making gaskets ) and make new pads. I have closed cell
>>foam that is over 20 years old and still fine, unlike the
>>normal foam used elsewhere that ozone and time have turned
>>to a gooey mess.
>> I would say that this makes the keyboards repairable for
>>someone that want to take the time.
>>Dwight
>>
