> From: shadoooo
> I'm scanning at 600dpi grayscale, lossless compression.
I've been scanning a few things too, and I found that 600dpi grayscale
produced absolutely enormous files (many, many MB's per page, for prints), no
matter what I tried to do, compression-wise.
600dpi black and white, followed by saving as TIFF's with CCITT Group 4
compression, produced immensely smaller files (small 100's of KB's for the
same pages), and they are quite readable (even the fine letter seems to be
readable - b/6 is quite distinguishable, etc).
Al, I hope that's acceptable for BitSavers - I have a number of things that
are missing, and I was planning on scanning them in, and sending them along.
Noel
> From: Brent Hilpert
> Core rope ROM has one magnetic core per the word-width of the memory.
> That is, a memory of (say) 1024 16-bit words would have 16 cores.
Not always (although your basic point, that in core ROM, a single core is
often/usually used for more than one bit, is a very key point to note); the
Apollo rope ROM had one core per 192 bits, or 12 words of 16 bits each,
"thousands of ... cores" per memory rope. See:
http://web.mit.edu/digitalapollo/Digital%20Apollo%20Annotated.doc
and there's a picture of one here:
http://klabs.org/mapld04/presentations/session_g/g1007_hall_s.ppt
(see slide #15).
Those notes do contain an interesting aside: "rearrange the program's
fixed-memory allocations to avoid cases where such sets of 12 words contained
too many ones to fit in their cores", which implies that the cores were
fairly small, physically (since a one involved running the wire _through_ the
core, not around it).
I don't know why they didn't make the cores larger, and have fewer of them;
my suspicion is that in manufacturing terms, it was easier to have more of
them, with less wires through each one. (I can't think of an _electrical_
reason to do so; unlike with RAM cores, where smaller cores are faster to
switch, and take less power to do so.)
Noel
I picked up a (known-faulty) 5160 a few weeks back, just because it had a
keyboard with an intact decal, and the one on my otherwise-perfect system
is missing.
The machine came with a CGA card, which I've tested as working in my other
5160.
Symptoms of the fault are one long beep and two short beeps at power-on,
with 1024 characters of garbage displayed on-screen (typically either a
solid block or a space, but with a handful of other random chars) - i.e. 12
rows of 80 and then a row of 64.
Following this on screen, at location 13,64, the memory count occurs, and
then it'll drop to ROM BASIC (no hard disk, and for the purposes of testing
I've not bothered with a boot floppy), with the BASIC startup text starting
at row 14 and all offset by 64 characters from the left margin. However,
the function key reference on the bottom line of the display is OK,
starting at position 25,1.
I can issue BASIC commands, and each new line is offset by 64 characters,
until I hit the bottom of the screen, at which point text appears at
position 1 (but still offset from the top of the screen by 13 lines).
Issuing a 'cls' doesn't remove the garbage from the display, and typing
then resumes from location 13,64. Throughout all of this the cursor seems
to appear where I'd expect it on the screen, however - I'm assuming it's
done via hardware entirely within the CGA card.
I've tried pulling all other cards, leaving just the CGA board, and the
problem persists. One long and two short beeps seems to be 'video failure',
but as mentioned I've verified that the card works in my other 5160.
Does anyone have any ideas what might be going on? It doesn't quite seem
like a memory fault - possibly some sort of address decoding error? It's
almost like the video board is pulling display data from the wrong part of
memory, but I'm not sure that makes sense given that the board has its own
local RAM rather than relying on RAM on the system board.
cheers
Jules
Hello Al Kossow,
I'm scanning a bunch of documents. Many of them aren't not listed on
Manx, and shouldn't be already loaded on bitsavers.
I'm scanning at 600dpi grayscale, lossless compression.
I could upload the documents somewhere in original RAW format, or
already deskewed, converted to TIFF BW bitmap.
I would contribute to Bitsavers, please contact me offlist for details
of upload.
Unfortunately I don't have a server, and the raw documents are heavy.
Thanks
Andrea
Hiya,
I have posted this in the past but I hate selling things but really that
is selfish on my part and some of my interests have shifted.
I need to move some items from the "Dust" and into the light from my
collection. Its all stored in my climate controlled clean basement.
I have mostly Dec gear although there are sprinkles of other stuff such
as Kaypro's , Osbournes etc ...
No blinken lights machines but some PDP's such as the 11/23 etc along
with some Vaxstations and Alphas.
The prices will be cheap and geared towards putting this into hands that
can use them over people wanting a quick flip.
I will not ship although anyone who wants to work with someone to pick
up a pile and ship it is more than welcome.
I am in the mid atlantic area and can be contacted via my gmail address
ladylinux4u at gmail dot com.
Thanks!!
Fran
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
I'm working over at the Living Computer Museum in Seattle and we're attempting to revive a PDP-11/44 for use in a project. At some point, someone stripped the power distribution panel from the 44's H7140 power supply (this is a small PCB that connects to the power supply terminals and provides molex power connectors for standard UNIBUS backplanes (or other backplanes).
Anyone happen to have one of these distribution panels (or failing that, a complete supply) going spare?
Thanks!
Josh
Sr. Vintage Software Engineer
Living Computer Museum
www.livingcomputermuseum.org<http://www.livingcomputermuseum.org>
(206) 342-2537<tel:%28206%29%20342-2537>
Once I get home, I could probably cross reference with a pantone color for you.
> On Apr 23, 2015, at 2:38 PM, Bill Sudbrink <wh.sudbrink at verizon.net> wrote:
>
> I remember a conversation about this subject from many
> years ago that never came to any conclusion. Has anyone
> discovered any "paint codes" or other definitive descriptions
> for the finish on the upper case of an IMSAI? I'm thinking
> of having my worst case (multiple scrapes and scratches,
> several permanent stains) refinished.
>
> Bill S.
>
>