Hi everybody,
I have an old SGI Indigo (IP12) which refuses my attempts to populate
the harddisk with Irix 5.3. The harddisk doesn't boot, so I assume it to
be empty.
I get sashIP12 and fx.IP12 to load from cd, but using fx with that hd fails:
SGI Version 5.3 IP12 Oct 31, 1994
fx: "device-name"= (dksc)
fx: ctrl#= (0)
fx: drive#= (1)
... opening dksc(0,1,)
dks0d1s10: Drive not ready: RAM failure, ASQ=0x80.
fx: warning: Failed to open dksc(0,1,10)
SGI Version 5.3 IP12 Oct 31, 1994
(and the same again, if I want)
Is it trying to open a non-existent partition dks0d1s10? Is it a
software-fault? If it's a hardware fault: What's broken: hd or ram?
The hd is in the bottom drive bay. After my enter keystroke in line 4
(drive#=1) the led flashes for a short time and at the same time (or
maybe some millisecconds later) the error message appears.
The error isn't very meaningful to me. Does anybody know about the
problem or does have any hints?
Thanks in advance,
Fabian
I fool around with a lot of systems that want small (by today's
standards) 50-pin SCSI drives. A few years ago you couldn't walk
around the streets of Palo Alto without tripping over big stacks of
500MB drives. These days, though, the stacks are made out of 9GB SCA
drives -- far too large for my needs, and often far too large to be
recognized by the computers I fool around with. But drives smaller
than that are suddenly "rare" and "expensive", $30 or $40 for any
SCSI drive under 9GB at a lot of resellers I've visited lately.
Anyone know where those stacks went? Are small drives just impossible
to come by for less than $30 now?
-Seth
--
"It looks just like a Telefunken U47! Seth Morabito
You'll love it." - Frank Zappa sethm(a)loomcom.com
>From: "Fred Cisin" <cisin(a)xenosoft.com>
>
>> >There was an attempt to "simplify" connection of multiple floppy drives
>> >(meaning TWO) at one time by adding a "twist" to the cable-- some
>> >conductors in the ribbon are cut out and reversed, which is a sort of
>> >"cable select" for floppy drives.
>
>Several manufacturers had problems with their field dealers, such as
>Computerland, being unable to properly handle things as complex as
>jumpers.
>
>> >I seem to recall in this case that one would jumper both drives as drive A
>> >in such a case, or as DS0.
>
>In the case of IBM, with a twist, jumper both as DS1 (SECOND drive).
>In the case of TRS80, with pins removed in connector cables, jumper all
>drive positions on the drive.
>
>> >Stupid idea. Use a straight thru floppy cable and jumper one for DS0 and
>> >one for DS1. We get it.
>> >If you intermingle the two drive select ideas you may have problems where
>> >both or niether drives light up and niether can read.
>> ---snip---
>> Hi
>> As I recall, the two drives with the twist were actually
>> DS0 and DS2 as seen by the controller. If using a straight
>> cable, one had to skip DS1.
>
>On PC (5150), with straight cable, I used drives jumpered DS0 and DS1.
>On PC (5150), with twisted cable, I used drives jumpered DS1 and DS1.
>
Hi
I stand corrected. Thanks Fred. I knew it was something like that.
Dwight
I started inventorying the manuals a week ago, below is a bad
copy of the spreadsheet, in two parts (software and hardware). A
lot of it is common (Cromemco), maybe a few others are of
interest:
Phoenix Software PDOS. Manuals and software (pasm, plink, plib,
etc) but also linkable objects to make the operating system
(Z80, very high-perf (sic), CP/M-80 superset).
JRT Pascal, 8", CP/M-80, xeroxed manual, includes letter
mentioning the price drop from $250 to $25!
Microsoft BASIC Compiler, 8" flop, CP/M-80, xeroxed manual.
Software sucked then, probably amusing now.
I have enough boot disks to simply bring the machine up (assuming
the hardware doesn't catch fire, etc) and copy the files
off. I once had some weird EPROM burner, brand forgotten, that
wanted input as Intel hex, so I have a program called ZAPLOAD
that converts to hex; I'll convert (assuming it does files >
RAM) and send out the serial port as text using Telink, my old
XMODEM program (or at worst, PIP) to my linux laptop. Twice for
good measure, diff. It will have to wait until the rest of the
machine arrives.
I assume no one ever got an 8" flop going under DOS/Win/Linux?
If any manuals are not floating around, I'll scan and make
available.
quan manual software location
tomj TJ's mongrel computer (FIDO) hardware configuration 2/10/81 S1000 binder covered sheets; IO ports, boot/bugger manual
Phoenix Software Associates Ltd PDOS User's Guide 1.0 1 yes ? S1000 binder CSSN-labelled copy in S1000 binder
Phoenix Software Associates Ltd PDOS Programmer's Guide 1 yes ? S1000 binder 29227
Phoenix Software Associates Ltd PASM Users Manual 1 yes ? S1000 binder rev 1.0, 1 Feb 80
Phoenix Software Associates Ltd TEXT EDITOR User's Manual 1 yes ? S1000 binder 29202
Phoenix Software Associates Ltd LINK User's Manual 1 yes ? S1000 binder 29202
Phoenix Software Associates Ltd Plink II 1 yes ? S1000 binder 15 Jan 81, xerox, Lifeboat Associates
Phoenix Software Associates Ltd BUG/uBUG 1 yes ? S1000 binder 29202
Computer Service Systems Network Inc (CSSN) Backup 1 yes ? S1000 binder written by tomj, undated, includes 25 Nov 80 addendum larger than the manual
Microsoft, Inc MBASIC Compiler 1 yes probably, 8? flop Black binder
Digital Research CP/M 2.2 Users Guide 1 yes yes CPM80 binder xerox
Digital Research CP/M 2.2 Interface Guide 1 yes yes CPM80 binder xerox
Digital Research CP/M 2.2 Alteration Guide 1 yes yes CPM80 binder xerox
Digital Research CP/M Assembler (ASM) User's Guide 1 yes yes CPM80 binder original looseleaf
Digital Research An Introduction of CP/M Features and Facilities 1 yes yes CPM80 binder original looseleaf
Digital Research CP/M Interface Guide 1 yes ? CPM80 binder 1.4 I think
Digital Research ED: A context editor for the CP/M disk system users manual 1 yes ? CPM80 binder 1.4 I think
Digital Research CP/M Dynamic Debugger Tool (DDT) User's Guide 1 yes yes CPM80 binder 1.4 I think
Digital Research CP/M System Alteration Guide 1 yes yes CPM80 binder 1.4 I think
Alloy Computer Products TIP (Tape Interchange Package) 1 yes ?
JRT ? JRT Pascal 1 yes yes blue binder 1982
quan manual software location
HARDWARE
Mountain Hardware Inc 100,000 day clock 1 yes Two manuals, different versions
Teletek FDC-1 1 yes
Scitronics Inc Real Time Clock 1 yes
Cromemco TU-ART 2 yes
Macrotech International Corp. SS256 1 ? 36ea HM4864P-2's
Alloy Engineering S100/DEI 1 yes yes tape interface
Central Data Corp. 64K RAM 1 yes
Measurement Systems and Controls Inc DM6400 1 yes 64K RAM; rev C
Cromemco 32K Bytesaver 1 ? no
Cromemco ZPU 1 yes fido Modified as per LITTLE FIDO
Cromemco 4FDC 1 yes yes fido Modified as per LITTLE FIDO
Cromemco 16FDC 1 yes
Cromemco RDOS ? yes EPROM on 4FDC card?
Seattle Computer Products 16K PLUS ? yes static memory
Industrial Micro Systems Inc Model 370 32K RAM ? yes
Data Electronics Inc The Funnel ? yes yes fits Alloy card
CMC Marketing Inc Model 2018R 1 yes fido notes for fromt panel in rear
Microft Inc EPROM board 1 yes yes fido TC's homemade board
Cromemco PRI 1 yes yes ?
Solid State Music Microcomputer Products Inc VB3A 80-char video 1 yes yes fido
TeleVideo Inc Operators Reference Manual 1 yes n/a Manual is for TVI-912B, 920B, 912C, 920C
TeleVideo Inc 912, 920 Operating Instructions 1 yes n/a
Shugart Associates SA800/801 Diskette Storage Drive yes n/a
Hi Joe
Actually, the East Germans fab ours. They are packaged
in Singapore. We do the design and debug, though.
That may change in the future, who knows. Still,
by we, I included all of the AMD employees.
Dwight
>From: "Joe R." <rigdonj(a)cfl.rr.com>
>
>At 10:25 AM 12/10/04 -0800, you wrote:
>
>>Hi
>> I don't think I'm giving away any trade secrets by mentioning
>>that the primary reason for going to lower voltages is to
>>reduce power consumption. The thinner oxides are to make them
>>work at lower voltages( needs more gain ). Power is a squared
>>factor of the voltage. Even a small reduction in voltage is
>>a big payoff in power. If we could make the transistors work
>>at 0.1 volts, we'd be doing it.
>> Remember, we make these things.
>
> No you don't. The Chinese, Koreans, Malaysians and other Asians do.
>
> Joe
>
>
>>Dwight
>>from AMD.
>>
>>
>>
>
>
>From: "Steve Thatcher" <melamy(a)earthlink.net>
>
>there is a secondary aspect to voltage reduction and that is reduced power
dissipation... which also translates to shoving more stuff into smaller
spaces...
>
>-----Original Message-----
>From: "Joe R." <rigdonj(a)cfl.rr.com>
>Sent: Dec 9, 2004 9:51 PM
>To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk(a)classiccmp.org>
>Subject: Re: electro-Physics: 3.3 volts
>
>At 09:30 PM 12/9/04 -0500, you wrote:
>>Today I started mothballing the VAX 6000 and noticed that a large part
>>of its power supply is on 3.3 volts, now common, but probably not in 1988.
>>
>>Seems like something was invented, probably in chip design that made
>>3.3 so useful. I wonder what that was, when that landmark was reached.
>
> It wasn't a new invention. In was the fact that ICs were getting so
>dense that they couldn't squeeze in any more circuits unless they could
>reduce the space that the insualting layers took up. The layers were
>already so thin that they'd break down at about 5 1/2 volt so they had to
>reduce the voltage to 3.3 volts. Since then they've further reduced it to
>1.8 volts and (I think) now to 1.1 volts. And there are plans to reduce it
>even more. All so that they can reduce the bulk of the insulating layers
>and add more gates.
>
> Joe
>
Hi
I don't think I'm giving away any trade secrets by mentioning
that the primary reason for going to lower voltages is to
reduce power consumption. The thinner oxides are to make them
work at lower voltages( needs more gain ). Power is a squared
factor of the voltage. Even a small reduction in voltage is
a big payoff in power. If we could make the transistors work
at 0.1 volts, we'd be doing it.
Remember, we make these things.
Dwight
>from AMD.
How about documenting the switch and jumper positions on your drive
before you send it off.
--
I can do that. Tom wanted to try some other things first.
The manuals for the DT8 and the 1/2 height 242 are up at www.bitsavers.org/pdf/qume
Antonio Carlini <a.carlini(a)ntlworld.com> wrote:
> The DSV-11 was rated at 256kbps but
> it can actually do either a tiny smidgen over (or a tiny
> smidgen under) 1Mbps on a worst case HDLC sequence,
> essentially forever.
Hmm, interesting. I assume that's the limit for single channel operation,
right? Do you know the true limit for operation with both channels?
(64 kbps officially.)
MS
I haven't tried to use that on the output of my rfloppy->dmk2raw
programs, but if it doesn't work it should probably be fairly easy
to adapt it.
--
It works fine.
Tom, I have a Qume DT8 you can borrow to read your discs. Send an
adr offlist and I'll send it off.
