therefore whats needed is a piece of ribbon cable or mort modern 3.5 only floppy cable, iow dual inline connectors at opposite ends, and a card edge in between?
------------------------------
On Sun, Oct 28, 2012 1:10 PM PDT Fred Cisin wrote:
>On Sat, 27 Oct 2012, Chris Tofu wrote:
>> mine is longer then any Ive seen on various sites. Probably older. Need
>> docs and s/w, though what Ive downloaded may be appropriate. Anyone ever
>> use their (discrete logic) version with 8 inch drives?
>
>I can tell you the contents of the docs that came with it!
>1) connect in inline in the cable between the disk controller and the
>drive. It originally came with with a short cable with a 34 pin card edge
>and 34 pin dual-inline connector. You could reverse that cable to connect
>to your FDC and either connector of the board. Then your existing drive
>cable connects to the other connector.
>"Do all connections and anstallation with the computer turned off!"
>Run the supplied software.
>
>Although much more verbose, that was all that the documentation said.
>
>It didn't even give the meaning of the jumper or switch that some models
>had, labelled "Compaq/Other"
>
>
>At one time, they permitted me access to a "secret" page of instructions
>on how to program it. Several parts of that page did not match what was
>done in their supplied software (disassembly). I have since seen that
>page show up in a few places on the web.
>
>
>--
>Grumpy Ol' Fred cisin at xenosoft.com
>
>
>
ok so what is your opinion on painting macs, FI black?
------------------------------
On Tue, Oct 30, 2012 4:02 AM PDT Joost van de Griek wrote:
>No.
>
>On 30 okt. 2012, at 11:17, Chris Tofu <rampaginggreenhulk at yahoo.com> wrote:
>
>> if not will they still w/great difficulty
>
>Of course.
>
>.tsooJ
>--
>Wherever you go, there you are.
>--
>Joost van de Griek
><http://www.jvdg.net/>
Hi all,
I'm decyphering an encoding scheme that was used to compress source
code decks. It's from an old obscure IBM 1130 program (CMXP, written by
Wil Baden, part of set of enhancements that let source code be stored,
edited, and compiled directly from disk. Radical! Visionary!)
The compressed format uses 6 bits to encode each character, but it's
not any of the standard IBM 6-bit EBCD schemes I've found through
Google. It *might* be unique to this compression/decompression program,
whose source I haven't found yet. (And if the source does turn up it'll
likely be compressed using this format -- so unless the character codes
are in the source as hex constants, the source may not help).
Here is what I've been able to map out so far, from a small fragment of
an encoded source deck:
Hex value
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
00 sp A B C D E F G H I . )
10 + J K L M N O P Q R *
20 - / S T U V W X Y Z , (
30 0 1 2 3 4 5 6 7 8 9 =
where "sp" is space. I am absolutely certain of the encoding of the
space, alphabet, digits, slash, comma, period, parentheses, and
asterisk. I'm pretty sure of the plus, minus, and equals. For the ones
I've left blank, I have no idea yet; either the codes aren't in the
sample I examined or I can't guess what the character is from the
context. If I read in more cards they might become clear.
I've found some CDC codes where / precedes S, but the row ordering is
different.
Does this encoding ring any bells for anyone? (Again, it might not
belong to any standard).
Thanks
Brian
I did this in the '80s and it worked very well, I used it as a kind of
software interrupt in a communications handler that had to handle both
input and output at the same time from the same terminal. Unfortunately
I
don't rememver exactly how I did it, and I no longer have access to the
source code.
But I did find this in the HP Pascal for OpenVMS User manual, section
5.1.4
on page 5-6:
Asynchronous system trap routines (ASTs) and RMS completion routines
must
have both the ASYNCHRONOUS and UNBOUND attributes. Because they
are asynchronous, such routines can access only volatile variables,
predeclared
routines, and other asynchronous routines.
The Language Reference mentions the User manual near the end in
conjunction
with volatile variables.
You might also need to declare the variable p as volatile somewhere.
The User manual is here:
http://h71000.www7.hp.com/doc/82final/6140/aa-pxsnd-tk.pdf
You would probably want to read chapter 5 in there.
Hope this helps.
/Jonas
I have a Seagate ST336706LC (10KRPM 36GB SCA-2) HD that quit working one day (doesn't light up, isn't detected, no humming or spinning). Was wondering if there is a fuse or something fixable on this drive (I kept my hardware drivers on it and not all of them are backed up). Mostly just want to get the data back before I toss it if possible.
Any ideas?
> From: jim s <jws at jwsss.com>
> Date: Mon, 29 Oct 2012 22:34:13 -0700
> Subject: B6700 story from Sharktank
>
> "It's 2 o'clock in the morning. Halloween. Suddenly, the two screens go blank. Then two closed eyes appear. Slowly open. Eyeballs look slowly to the left, then slowly to the right -- then slowly stare straight ahead. Then eyelids slowly close, the two displays blank, and go back to scrolling plain text.
>
> "Of course, nobody is going to believe the operator..."
A friend at CDC gave me a punched card deck that would run that program.
The computer operators at the University were more than a little
freaked out when they saw the eyes.
No, I don't have the card deck anymore.
--
Michael Thompson
Message: 8
Date: Tue, 30 Oct 2012 12:25:26 -0400
From: Keith Monahan <keithvz at verizon.net>
To: cctalk at classiccmp.org
Subject: PLCC extraction tool
Message-ID: <508FFF76.6050409 at verizon.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I've got to remove a PLCC from a socket, and intend on just using a
couple screwdrivers/picks.
I may need to do this a few times, but I generally don't find the need
to do it.
Is a specialized PLCC extraction tool really required/much easier/safer/etc?
There seem to be a ton of tools online starting around $2 US a piece. If
I'm going to spend the time/shipping to order one, I may as well get a
decent one. Can anyone recommend a specific model/US source for it?
Warning, levering them out with a tool can easily crack the socket, then you
will get poor contact. I've got a $10 tool that easily fits the larger
sockets,
but the first time I used it on a 68-pin PLCC, the pulling hooks broke off.
I filed new hooks out of decent steel and brazed them to the existing
tool's arms, and it works great, now. So, I can't recommend an
off-the shelf tool that actually works well right out of the box.
Jon
I've got to remove a PLCC from a socket, and intend on just using a
couple screwdrivers/picks.
I may need to do this a few times, but I generally don't find the need
to do it.
Is a specialized PLCC extraction tool really required/much easier/safer/etc?
There seem to be a ton of tools online starting around $2 US a piece. If
I'm going to spend the time/shipping to order one, I may as well get a
decent one. Can anyone recommend a specific model/US source for it?
Thanks,
Keith
Hello,
I'm searching for Unibus disk controllers for my 11/24 and 11/730 machines.
It could be ESDI, SMD or better SCSI, of course the price will change.
Also an RL02 or RX02 interface could be interesting, if somebody has
one to rid of.
I already have an SDI interface, but no SDI working disk, unfortunately...
Preferred location is within EU.
Thanks
Andrea
From the Computerworld Sharktank. I think this also the system with
the B in the lights as well.
Flashback to the mid-1960s, when the Control Data 6600 computer was the
fastest thing going, according to this IT pilot fish who remembers it well.
"It was about 1 megaFLOPS," says fish. "The operator console, manned
24/7 of course, had two large, circular CRT screens, side-by-side, that
almost always displayed operator messages scrolling up the screens. As
long as those messages were scrolling, the operator seldom had to pay
attention to them.
"But the CRTs were actually vector displays, capable of more, under
program control.
"It's 2 o'clock in the morning. Halloween. Suddenly, the two screens go
blank. Then two closed eyes appear. Slowly open. Eyeballs look slowly to
the left, then slowly to the right -- then slowly stare straight ahead.
Then eyelids slowly close, the two displays blank, and go back to
scrolling plain text.
"Of course, nobody is going to believe the operator..."
