From owner-pc532%daver@mips.com Thu Mar  1 20:58:08 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Thu, 1 Mar 90 17:44:14 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: Question
Status: O

[In the message entitled "Re: Question" on Mar  1, 17:19, Jim Penny writes:]
> I do not personally have any EPROM burners.  I think it would be fair if
> you guys charged some kind of a PROM burning fee.
I'm sure that local companies could burn proms for you, or someone more
local could do it. We can do it in a pinch.

> Oh, I forgot.  Do I owe you for shipping on the kit.  You guys are out
> enough on time and effort that I don't want you to be out of pocket as
> well.

Yup. If you haven't paid in advance, we would appreciate it if you would
pay for the shipping (as we indicated earlier). For the domestic folks,
the charge was about $5.50 plus insurance (and boxes, packing material,
etc.) - about $9.00. The people overseas are being billed for the shipping
(unless you sent money in advance), that is about $30-60 depending on
destination. The carrier will bill you for the shipping charges.

Thanks, and I hope you enjoy building them!


-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From owner-pc532%daver@mips.com Sat Mar  3 07:43:54 1990
Flags: 000000000001
Reply-To: pc532@daver.bungi.com
Subject: playing hard to get
To: pc532@daver
Date: Sat, 3 Mar 90 3:12:52 PST
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls (Karl Swartz)
Status: O

George, did you select the 'AS1004A, 'AS1034A, and 'ALS1034A
specifically for how difficult they would be to obtain?!  I've
gotten quotes of anything up to 4 months delivery time, or in
stock but $250.00 minimums.  Arrow seems to be about the best
shot, with only a few weeks delivery times.  I'm about halfway
to the $25 minimum order -- anybody else want to join in to
get over the edge?

BTW, Arrow has 'ALS1034s, sans the A suffix as specified in
the build list.  Can I assume that this will be adequate?

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Sat Mar  3 13:12:26 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: george@wombat (George Scolaro)
Date: Sat, 3 Mar 90 09:10:34 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: playing hard to get
Status: O

[In the message entitled "playing hard to get" on Mar  3,  3:12, Karl Swartz writes:]
> George, did you select the 'AS1004A, 'AS1034A, and 'ALS1034A
> specifically for how difficult they would be to obtain?!  I've

How did you guess? :-) It seems that over the last couple of months the '1034
drivers have become very popular. I find it quite boggling that all the
vendors have simultaneously run out. It would appear that they (including the
semi houses) all have very poor inventory accounting!

> gotten quotes of anything up to 4 months delivery time, or in
> stock but $250.00 minimums.  Arrow seems to be about the best
> shot, with only a few weeks delivery times.  I'm about halfway
> to the $25 minimum order -- anybody else want to join in to
> get over the edge?
> 
> BTW, Arrow has 'ALS1034s, sans the A suffix as specified in
> the build list.  Can I assume that this will be adequate?

Yes, the als1034 is only used as a buffer for the address lines going to the
peripheral devices, it's speed isn't overly critical. The 'A' version is a
couple of nanoseconds faster than the non 'A'. If it makes ordering easier,
(as I have already mentioned) you can use an AS1034 in place of the ALS1034
(faster is ok..)

Now, if you are really desperate to get the board running (i.e. at all
costs), you could actually (probably) bypass the ALS1034/AS1034's in the
short term (sic). Build up three 14 pin headers that connect input/output of
each of the 6 buffers in each device and plug them into the sockets on the
pc532 (you did use sockets right?). Of course you will probably have to run
the board a bit slower (and have 4 SIMMs in only), since the load on the
main devices will be greater without the drivers in place. 20MHz would
probably be quite safe (i.e. 40 MHz crystal).

best regards,

-- 
George Scolaro
george@wombat
(try {pyramid|sun|vsi1|killer} !daver!wombat!george) [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Sat Mar  3 18:44:22 1990
Flags: 000000000001
Reply-To: pc532@daver.bungi.com
To: pc532@daver.uu.NET
Subject: ordering parts
Date: Sat, 03 Mar 90 09:23:18 EST
From: Trip Martin <night@pawl.rpi.edu>
Status: O

Subject: playing hard to get
To: pc532@daver
Date: Sat, 3 Mar 90 3:12:52 PST
X-Mailer: ELM [version 2.2t PL7]
Message-Id: <9003030312.AA08387@ditka.UUCP>
From: ditka!kls (Karl Swartz)

>George, did you select the 'AS1004A, 'AS1034A, and 'ALS1034A
>specifically for how difficult they would be to obtain?!  I've
>gotten quotes of anything up to 4 months delivery time, or in
>stock but $250.00 minimums.  Arrow seems to be about the best
>shot, with only a few weeks delivery times.  I'm about halfway
>to the $25 minimum order -- anybody else want to join in to
>get over the edge?
>
>BTW, Arrow has 'ALS1034s, sans the A suffix as specified in
>the build list.  Can I assume that this will be adequate?

I've been working mostly with Newark Electronics, and they
have a different set of problem parts: 74ALS14 (not stocked),
74AS258 (not stocked), and 74AS374 (12-14 wks!).  

All the other TTL chips, they have in stock, including the three
you're looking for (and I'm pretty sure in with the A suffix, but
I'd have to check on that again).

I'd be willing to tack on the three parts I need to your order,
Karl.  I'd also be willing to take orders from other people needing
any of the other parts.  I would like to get this order out soon,
so I'm shooting for Wed. to make the order. 

One other question: does Arrow carry the SCSI diodes and the 50MHz
oscillator module?  I need them too.  If not, will an RCA SK3311 do a
s a substitute for the SCSI diodes?  Newark came up with that as a 
cross-reference.

While we're on the subject of ordering stuff, I've recently run
across a special on SCSI hard disks at Corporate Systems Center.  
They have a Miniscribe 9380 SCSI 335MB 16ms HD for $1095, or 
$995 in quantities of 5+.  I realize this is quite a bit of money,
but it's one hell of a deal for a hard disk that large.  Would
anyone be interested in a group order to get the discount?  CSC
is offering a one-year warranty, since Miniscribe went under.  

Trip Martin
night@pawl.rpi.edu

From owner-pc532%daver@mips.com Sat Mar  3 21:32:38 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: george@wombat.bungi.com (George Scolaro)
Date: Sat, 3 Mar 90 18:10:26 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: ordering parts
Status: O

[In the message entitled "ordering parts" on Mar  3,  9:23, Trip Martin writes:]

> I've been working mostly with Newark Electronics, and they
> have a different set of problem parts: 74ALS14 (not stocked),
> 74AS258 (not stocked), and 74AS374 (12-14 wks!).  

Note: The 74als14 can actually be any variant, i.e. 74AS14, 74LS14, 74HCT14,
74F14, 74[whatever]14 since it is only used to generate the reset signal.
I have already mentioned that you can use the 74AS158 in place of the 74AS258
since all lines are buffered (by the 74AS1004/74AS1034 devices). The 74AS374
has to be what it is, but it should be very very easy to get!

> One other question: does Arrow carry the SCSI diodes and the 50MHz
> oscillator module?  I need them too.  If not, will an RCA SK3311 do a
> s a substitute for the SCSI diodes?  Newark came up with that as a 
> cross-reference.

DigiKey sells the 50MHz xtal module, I have got them there in the past.
Regarding the diode, all you need is a 1 amp (or so) schottky diode, in fact
I was really slack and just put a normal diode in (naughty naughty!). Its
only needed to power terminators on the target scsi boards (and they are
usually self powered anyway).

> While we're on the subject of ordering stuff, I've recently run
> across a special on SCSI hard disks at Corporate Systems Center.  
> They have a Miniscribe 9380 SCSI 335MB 16ms HD for $1095, or 
> $995 in quantities of 5+.  I realize this is quite a bit of money,
> but it's one hell of a deal for a hard disk that large.  Would
> anyone be interested in a group order to get the discount?  CSC
> is offering a one-year warranty, since Miniscribe went under.  

Sounds like a bargain. Put both Dave and myself down for one each. CSC is
actually a local company here in sillycone valley (John C. has mentioned it
a few times). We'll give them a call on Monday and find out some more
details.

regards,


-- 
George Scolaro
george@wombat
(try {pyramid|sun|vsi1|killer} !daver!wombat!george) [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Sun Mar  4 01:53:07 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Thu, 1 Mar 90 17:42:47 EST
From: Jerry Callen <jcallen@maxzilla.encore.com>
To: pc532@daver.bungi.com
Subject: 74AS32 and SCSI terminators
Cc: jcallen@maxzilla.encore.com
Status: O


I have a few questions about the board; now that I'm building it, I've
actually started to pay attention to the schematic a bit. :-)

My first question is about the following substitution:

>	well, due to the xtal input difference between the 2681 DUART and
>the 2692 DUART, the 74AS32 device must be changed to a 74AC32 device. The
>2692 outputs a signal that does not reach below about 1V causing the TTL
>level of the 74AS32 to be violated. Using a 74AC32 gives us speed, which is
>needed through one of the other gates (in the same package) and 50%
>threshold for the oscillator output of the 2692. Signetics recommends the
>use of a 74Cxx device to buffer the oscillator, but we need a 74AC (for
>speed). We will supply the 74AC32 part with the kit.
>
>George Scolaro

In addition to being used to generate the clock for the 2681s, the 74AS32 is
used to generate an enable into the 74AS646 that drives the data bus for the 
SCSI interface chips (/PERG). The inputs (/SLOWC and /SLOWS) are produced
by a 74AS174 F/F and a PAL16L8B. Well, I don't have a data sheet for the
74AS174, but the data sheet for the PAL indicates that VOH is only guaranteed
to be 2.4V (although 3.4 is the "typical" value). This is BELOW the input
threshold for a CMOS chip! 

My second question is really an observation. The SCSI terminator resistors
present a substantial load to the power supply, on the order of 400ma! I got
this number by computing the parallel resistance for 48 550ohm resistors
(which is just 550/48 = about 12) and plugging into good ole E=IR for 5V.
Each of those resistor packs is going to be pulling about a half a watt.
Keep your fingers clear! I would expect some of the PALs to get pretty warm,
too.

BTW, the way I came to notice this is that I put my trusty VOM across +5
and GND and noticed a mere 12 ohms! I always do this rudimentary sanity
check before performing the actual "smoke test" on a new project...


-- Jerry Callen
   jcallen@encore.com
   (508) 460-0500 (work)
   (617) 876-5330 (home)

From owner-pc532%daver@mips.com Sun Mar  4 02:44:59 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Sat, 3 Mar 90 23:38 PST
From: dlr@daver.bungi.com (Dave Rand)
To: pc532@daver.bungi.com
Subject: Now how much would you pay...
Status: O

Now that you have the boards in your hands (at least most of you have
the boards in your hands) I have a couple a questions. I would prefer
private email on this - mail to dlr@daver.bungi.com.

Assumptions: I can (somehow) cut a deal to get Real (tm) UNIX (reg. tm).
I would provide a re-configurable binary, plus full source for anything
that was written by me (like the drivers). *NOTE* This is an assumption.
This does not mean that it is currently, or ever will be available. 
Don't order it now.

1. How much would you pay for System V release 3.1? This would be
   a stock release kind of thing, and would not include NFS, VPIX
   or YP.
2. How much would you pay for a BSD-derivative (assuming that I could
   get one)?
3. How much would you pay for a System V release 2 will full support
   for multiprocessors?

This will help me figure out which avenue to push the hardest. Things
are in progress. Other suggestions are welcome! I continue to look at
MACH, etc. as possible alternatives.

Thanks much.

Dave Rand
+1 408 434-0600 X4555 work
+1 408 733-4125 home

From owner-pc532%daver@mips.com Sun Mar  4 02:53:12 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: george@wombat.bungi.com (George Scolaro)
Date: Sat, 3 Mar 90 23:42:30 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: 74AS32 and SCSI terminators
Status: O

[In the message entitled "74AS32 and SCSI terminators" on Mar  1, 17:42, Jerry Callen writes:]
> 
> I have a few questions about the board; now that I'm building it, I've
> actually started to pay attention to the schematic a bit. :-)
> 
> 74AS174, but the data sheet for the PAL indicates that VOH is only guaranteed
> to be 2.4V (although 3.4 is the "typical" value). This is BELOW the input
> threshold for a CMOS chip! 

Yeah, well 2.4 volts is the guaranteed min Voh when the output of the PAL is
fully loaded (i.e. driving a resistive load), but the input of a 74AC32 gate
is nearly purely capacitive, the SLOWC/SLOWS outputs are very lightly loaded.
If you are really worried then tack 1k pullup resistors to the input of the
gate from the PAL.

> My second question is really an observation. The SCSI terminator resistors
> present a substantial load to the power supply, on the order of 400ma! I got

One other fellow constructor also just noticed this very low board
resistance, which had him worried until I explained the terminator loading.

> BTW, the way I came to notice this is that I put my trusty VOM across +5
> and GND and noticed a mere 12 ohms! I always do this rudimentary sanity
> check before performing the actual "smoke test" on a new project...

Always a good idea. This is the one area that modern (PC/AT) switching power
supplies can save you. They will not start up (or will switch off) very
rapidly if presented with a short circuit, unlike linear power supplies that
find a short circuit a challenge they just can't resist!

best regards,


-- 
George Scolaro
george@wombat
(try {pyramid|sun|vsi1|killer} !daver!wombat!george) [37 20 51 N / 122 03 07 W]

From budd Sun Mar  4 00:26:42 1990
Flags: 000000000000
Date: Sun, 4 Mar 90 00:26:41 EST
From: budd@bu-it.bu.edu (Phil Budne)
To: budd@bu-it.bu.edu, gnu@toad.com
Subject: Re: missing, fixed and new files...
Cc: pozar@toad.com
Status: O

UUNET was ill at the time.  I saved the set when I mailed it,
I'll resend 2 4 5 and 7 now...

-p

From owner-pc532%daver@mips.com Sun Mar  4 05:14:34 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Sun, 4 Mar 90 04:09:28 EST
From: budd@bu-it.bu.edu (Phil Budne)
To: pc532@daver.UU.NET
Subject: Re:  Media and monitors
Status: O

	Subject: Media and monitors
	Date: 1 Feb 90 13:50:06 GMT (Thu)
	From: ken%mm%gatech@ames.arc.nasa.gov (Ken Seefried iii)

	A company called Insite has a 3.5", SCSI-based `super-floppy'
	drive they call a `floptical'.  The media has imbedded optical
	tracks to allow very precise placement of the head.  End
	result is an ability to stuff 20MB on one disk (looks like a
	3.5" disk).  The new model can even read and write 720K and
	1.44MB disks.  The drive itself is pretty cheap, as I remember
	(<$300) and the optical media isn't to bad either.

This sounds very interesting!  Do you have more information?

-Phil


From owner-pc532%daver@mips.com Sun Mar  4 07:33:25 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: Anthony J Stieber <astieber@csd4.csd.uwm.edu>
Subject: Re:  Media and monitors
To: pc532@daver.uu.NET
Date: Sun, 4 Mar 90 4:10:29 CDT
X-Mailer: ELM [version 2.2 PL10]
Status: O

-> 
-> 	Subject: Media and monitors
-> 	Date: 1 Feb 90 13:50:06 GMT (Thu)
-> 	From: ken%mm%gatech@ames.arc.nasa.gov (Ken Seefried iii)
-> 
-> 	A company called Insite has a 3.5", SCSI-based `super-floppy'
-> 	drive they call a `floptical'.  The media has imbedded optical

Unfortunatly Insite won't sell to non-OEMs their drive.  You can
talk to the Unknown User (unknown@ucscb.ucsc.edu).  This *is* a real
person.  He has repeatably tried to organize a group buy, but
Insite just won't bite.  The other company, Brier, is even worse.

Maybe some of the company affiliated people here could manage it,
the hobbist oriented group could not.  It might be that the only
way to get these drives is to get them from an OEM.
--
<-:(= Tony Stieber	astieber@csd4.csd.uwm.edu   att!uwm!uwmcsd4!astieber

From owner-pc532%daver@mips.com Sun Mar  4 07:33:14 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: 	Sun, 4 Mar 90 02:53:57 EST
From: neil@skatter.USask.CA
Subject: Re:  ordering parts
To: pc532@daver.bungi.com
Status: O

I would like to join in with Trip Martin's order if he goes ahead with it.

Trip, Could you post a price for everything you will be ordering. We
can work out payment later, but I doubt if you will get much by Wednesday.


regards,

Neil Johnson

From owner-pc532%daver@mips.com Mon Mar  5 01:06:39 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: Miniscribe 9380 drives.
To: pc532%tarpit@daver.bungi.com
Date: Sun, 4 Mar 90 10:50:34 EST
From: John L. Connin <johnc%manatee%uunet@daver>
X-Mailer: Elm [version 2.1 PL1]
Status: O


>> While we're on the subject of ordering stuff, I've recently run
>> across a special on SCSI hard disks at Corporate Systems Center.  
>> They have a Miniscribe 9380 SCSI 335MB 16ms HD for $1095, or 
>> $995 in quantities of 5+.  I realize this is quite a bit of money,
>> but it's one hell of a deal for a hard disk that large.  Would
>> anyone be interested in a group order to get the discount?  CSC
>> is offering a one-year warranty, since Miniscribe went under.  
>

[ george writes ]

>Sounds like a bargain. Put both Dave and myself down for one each. CSC is
>actually a local company here in sillycone valley (John C. has mentioned it
>a few times). We'll give them a call on Monday and find out some more
>details.

For planning purposes, put me down for one (possibly two) of the drives.

Perhaps a better deal can be negotiated with an order greater than 5 *and*
if we stress the world wide exposure the pc532 list can provide (or some
other story).  I sure they have alot of margin to work with.

BTW: I have purchased items from CDC in the past and have no complaints.  

The warranty is probably only as strong as CDC and thus indeterminate
in value.  Some arrangement probably needs to be worked out so the
warranty is assigned to the 'real' purchaser, not the group representative
(eg. invoice from CDC to end purchaser with terms and conditions stated).

Is the reliability of the Miniscribe 9380's known ??  My understanding
is the 9380's have a short field history.  Is there anyway we can get
the inside scoop on these drives  ??

Best regards,
johnc



From owner-pc532%daver@mips.com Mon Mar  5 14:48:27 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Re: ordering parts 
Date: Mon, 05 Mar 90 11:01:33 EST
From: Trip Martin <night@pawl.rpi.edu>
Status: O

Here's the price list for the parts I'm getting:

74AS00      $0.47
74AS74      $0.65
74F138      $0.65
74AS174     $1.59
74AS280     $1.39
74AS646     $6.01
74AS1004A   $1.11
74ALS1034A  $0.65
74AS1034A   $1.11

I realize that I probably won't get any money by Wed., but
I'd like to get the parts soon (yes, I'm impatient!).  I figured
that people should be able to let me know by then by email if they 
want to get in on the order.  If I get swamped by people wanting 
to get in on the order, then I'll probably put off the order until 
I have at least some of the money.  Otherwise, as long as I have 
the money by the time I send the parts out to people, that's fine. 
That will most likely happen next weekend, or early the following week.  

The sales tax is 7%, and figure a dollar or two for shipping.  Please
send me your postal address by email, and a list of which of the above
parts you want me to order, or the full list if that's what you need.
I'll assume people will want the number of parts the pc532 needs unless
you tell me otherwise.

My address is:
      Trip Martin
      1599 Tibbits Ave.
      Troy, NY 12180

--
Trip Martin
night@pawl.rpi.edu

From owner-pc532%daver@mips.com Mon Mar  5 20:24:29 1990
Flags: 000000000001
Reply-To: pc532@daver.bungi.com
Date: Mon, 5 Mar 90 16:21:24 PST
From: bpan@yogi (Benjamin Pan)
To: pc532@daver.bungi.com
Subject: Re: Miniscribe drive
Status: O


John asked in his previous message regarding the SCSI hard drive:

>Is the reliability of the Miniscribe 9380's known ??  My understanding
>is the 9380's have a short field history.  Is there anyway we can get
>the inside scoop on these drives  ??

I don't have any experience with the 9380 SCSI drive. However, the 9380E -
ESDI version of the drive, has been around for a while. My understanding is that
COMPAQ uses the 9380E in its 300M configurations. (type 38)  Currently, I
have a 9380E in a 386 machine for continuous operation for almost two months
now. No problems so far. This drive is a bit noiser than Imprimis (CDC) 383H
dirve, espacially with a distinctive clicking sound during head movement.
The price for the 9380E was around $1400 (not from COMAQ!) before Miniscribe
got itself into a law suit and went Chapter 11.  It should be cheaper now
because the company is in need for cash. Nevertheless, around $900 sounds like
a good deal if it includes an one-year warranty for parts AND labor.

the configuration of the 9380E in terms of cylinders, heads, sectors per track,
starting current, operation current, etc. is unclear. You probably
don't care about those anyway.  What matters is that 
1) the 16ms average access time is correct, and
2) a 220W PC/AT power supply should have no problem to drive it.
On the same system, I have both the 9380E and a CDC 150M drive powered
by a 220W power supply.

Regards,

-Benjamin Pan-
{mips, daver}!chips!bpan

From budd Mon Mar  5 23:36:38 1990
Flags: 000000000000
Date: Mon, 5 Mar 90 23:36:31 EST
From: budd@bu-it.bu.edu (Phil Budne)
To: unknown@ucscb.ucsc.edu
Subject: Insite floptical
Cc: astieber@csd4.csd.uwm.edu, budd@bu-it.bu.edu
Status: O

Tony Stieber said you have repeatedly tried to purchase
the Insite 3.5" floptical disk drive, but they won't sell
to non-OEMS!!

What OEM's buy from them?

Thanks!
	-Phil Budne

From unknown@ucscb.UCSC.EDU Tue Mar  6 03:03:50 1990
Flags: 000000000000
Date: Tue, 6 Mar 90 00:04:44 -0800
From: unknown@ucscb.UCSC.EDU (The Unknown User)
To: budd@bu-it.bu.edu
Subject: Re:  Insite floptical
Status: O

	I dunno...

	Why do you want to know what OEMs buy from them?

bye

From unknown@ucscb.UCSC.EDU Tue Mar  6 03:36:27 1990
Flags: 000000000000
Date: Tue, 6 Mar 90 00:37:08 -0800
From: unknown@ucscb.UCSC.EDU (The Unknown User)
To: budd@bu-it.bu.edu
Subject: Re:  Insite floptical
Status: O

	Well I thought of it.

	You wanna take charge and write to Brier and Insite?

	They already know my name and might be bugged.

  _    __       __           __       _     /-------------------------------\
 /_\  |__| |    __|    |_|  |_  \  / |_|   |    unknown@ucscb.ucsc.edu       |
/   \ |    |__ |__       |  |__  \/  | \   | unknown%darkside.com@ames.arpa  |
                                            \-------------------------------/ 

From unknown@ucscb.UCSC.EDU Tue Mar  6 04:10:44 1990
Flags: 000000000000
Date: Tue, 6 Mar 90 01:11:37 -0800
From: unknown@ucscb.UCSC.EDU (The Unknown User)
To: budd@bu-it.bu.edu
Subject: Re:  Insite floptical
Status: O

Brier Technology
2363 Bering Drive
San Jose CA 95131
408 435 8463

Insite Peripherals
4433 Fortran Drive
San Jose CA  95134-2302
408 946 8080

So be sure to keep me up to date.

  _    __       __           __       _     /-------------------------------\
 /_\  |__| |    __|    |_|  |_  \  / |_|   |    unknown@ucscb.ucsc.edu       |
/   \ |    |__ |__       |  |__  \/  | \   | unknown%darkside.com@ames.arpa  |
                                            \-------------------------------/ 

From tarpit!manatee!johnc@uunet.UU.NET Tue Mar  6 19:29:18 1990
Flags: 000000000001
Subject: Re: Circuit Cellar BBS, file list 
To: budd@bu-it.bu.edu (Phil Budne)
Date: Tue, 6 Mar 90 12:15:33 EST
From: John L. Connin <johnc%manatee@uunet.UU.NET>
X-Mailer: Elm [version 2.1 PL1]
Status: RO

> 
> Can you send me the complete list?
> 
> Thanks!
> 	-Phil
> 

Consider it done.
johnc
	------------------------------------------------------

The following is a list of all the files contained on the Circuit Cellar BBS
as of Friday, December 22, 1989.  The Circuit Cellar BBS may be reached at
(203) 871-1988.  Remember that the Circuit Cellar BBS isn't a file clearing-
house, but is a forum in which to exchange information through the message
base.  Every user is limited to downloading 250K in any 24-hour period.  There
are no exceptions to this limit.  If you want to download more, you must
spread it out over several days.

Finally, note that files in areas 1 and 2 may NOT be posted on other BBSs or
information services.

File area #  1 ... Circuit Cellar INK project files
File area #  2 ... Ciarcia's Circuit Cellar files (BYTE)
File area #  3 ... User-modified Circuit Cellar files
File area #  4 ... Microprocessor development tools
File area #  5 ... Electrical engineering programs & files
File area #  6 ... User-written ImageWise programs
File area #  7 ... User-uploaded ImageWise pictures
File area #  8 ... X-10 files
File area #  9 ... PC Pursuit files
File area # 10 ... CP/M files and programs
File area # 11 ... Utility programs for the IBM PC
File area # 12 ... Miscellaneous IBM PC files
File area # 13 ... Miscellaneous text files
File area # 14 ... Files that don't fit elsewhere

--------------------------------------------------------------------------

File area #  1 ... Circuit Cellar INK project files

This section contains files related to past Circuit Cellar INK
articles.

Files contained in this directory may not be reposted on other BBSs or
information services without express permission from Circuit Cellar Inc.

One or more of the following programs may be needed to break apart
certain "grouped" files found later in the list.

ARC.EXE        65339  Breaks apart ARC files on IBM PC systems
UNARC.COM       4736  Breaks apart ARC files on CP/M systems
NULU.COM       15360  Breaks apart LBR files on CP/M systems


 December 89/January 90, Issue #12

MIDISEQ.ARC    52426  Software for MIDISeq MIDI sequencer
NETDEMO.ARC    24568  Sample INKnet application programs

 October/November 1989, Issue #11

INKNET.ARC    140114  INKnet executable code (MONITOR & node)

 August/September 1989, Issue #10

TRACER.ASM     12077  Firmware Furnace source code
TRACER.COM       866  TRACER executable code for IBM PC
SATELLIT.TXT    4480  Soviet satellite receiver sample code

 SCSI Data Acquisition System files may be found
  listed under issue 9 below.


 June/July 1989, Issue #9

X10IR.PAS       4992  EPROM code generator for IR543 trainer
X10IR.HEX      46208  Final EPROM image
ANN.FOR        31886  Chris Ciarcia's neural network (FORTRAN)
SAMPLRUN.TXT    5414  Sample of neural network in action
PFT.FOR         9653  Polar Fourier Transform in FORTRAN
ADALINE.BAS    10060  ADALINE Learning Neuron code
DAQ3000.ASM    14170  6502 code for DAQ3000 (for Apple ][)
SCSIFAST.ASM    5319  68000 SCSI transfer routines
SCSIMOVE.PAS   11461  Macintosh Pascal portion of DAQ3000
INVNET.ARC     81418  "From the Bench" Invisible Net
FPCONV.ARC     50692  Fixed point/floating point conversion

 April/May 1989, Issue #8

LCDTEST.C      23936  Firmware Furnace LCDTEST source code
LCDTEST.MAK      280  Batch file for compiling LCDTEST
LCDTEST.EXE    36344  Executable version of LCDTEST
IWPCPROC.TXT   10496  ImageWise/PC procurement list
IWPCEXE.ARC   249998  ImageWise/PC executable code
IMWPC.HEX      19725  ImageWise/PC EPROM image
IWPCSRC.ARC   132938  ImageWise/PC IBM PC source code

 Source code for the ImageWise/PC EPROM is not available.
 RTOS files may be found listed under issue 7 below.


 January/February 1989, Issue #7

DATALOG.C      32880  Remote Data Logger system software
AD-READ.ME      1694  File describing following hex files
AD-INTEL.HEX   11668  Compiled Data Logger code (Intel hex)
AD-MOT.HEX      9918  Compiled Data Logger code (Motorola hex)
OS.MAC         13056  Real-time operating system (RTOS) kernel
OSMACRO.MAC     1920  RTOS macros
OSAPP.MAC       2944  RTOS example application
LONGMULT.ASM    9216  Mandelbrot engine multiplication code
DEFINES.INC     6351  Include file for LONGMULT.ASM
MACROS.INC      3739  Include file for LONGMULT.ASM
IWPCPROC.TXT   10496  ImageWise/PC procurement list

 November/December 1988, Issue #6

DEBUG31.ARC    54182  DDT-51: 8031 debugger for IBM PC
KERNEL.ARC      8297  DDT-51: 8031 kernel for IBM PC
TEST31.ARC     42907  DDT-51: Test code for circuit debugging
DDT51UPD.TXT    5248  DDT-51 update information
DDT51NOT.TXT   11648  Some DDT-51 notes from Ed Nisley
GAFFE06.NOT     1024  All about the Furnace #6 blunder

 September/October 1988, Issue #5

ROVERRX.Z80    14336  ROVER receiver EPROM source
ROVERTX.Z80    13312  ROVER transmitter EPROM source
PORTS.LIB       3200  Macro file for ROVER and X10RCVR files
PP68KPAL.ARC   11359  Weather Center PAL equations
DSCOPE.ARC     13771  Digital oscilloscope DSCOPE program
PLOT.ARC       19852  Digital oscilloscope PLOT program
TDS12.ARC       7158  Combined TDS1 and TDS2 programs
SWIO.PDS        1702  Digital oscilloscope U7 PAL equations
20X.PDS         3229  Digital oscilloscope U8 PAL equations
X10RCVR.Z80     9344  TW523 receiver code for the BCC180

 July/August 1988, Issue #4

SONAR.ARC      60150  Scanning sonar sensor software
SEQUENCE.ARC   19963  Program to help determine motor setup
ROBOT.BAS       1536  Robot arm control code in BASIC-52
ROBOT.ASM       3840  Robot arm control code in 8052 assembly
JOYSTICK.ARC   22784  Joystick code from Firmware Furnace
WXRDR10.ARC   118215  Weather radar modules (10/24/88)

 May/June 1988, Issue #3

WEATHR13.ARC   41120  WEATHER.EXE and README files (10/24/88)
WXCOMM13.ARC   80248  Overlay files for WEATHER.EXE (10/24/88)
SOFTUART.ASM   49664  Bill Curlew's SoftUART software
X10BC180.Z80    6272  X-10 PL513 software for the BCC180
PORTS.LIB       3200  Macro file for X10BC180.Z80
X10BCC52.ARC    7988  X-10 PL513 software for the BCC52
X10IBMPC.ARC   21991  X-10 PL513 software for the IBM PC

 March/April 1988, Issue #2

BOTTLE.ARC     22144  Bottle rocket data collection programs
COLOR8.BAS       541  8-bar RGBI-to-NTSC alignment program
COLOR16.BAS      773  16-bar RGBI-to-NTSC alignment program
PROG1.BAS       4552  QuadTherm program #1: CHOOSE
PROG2.BAS       2389  QuadTherm program #2: COR CAP
PROG3.BAS       8064  QuadTherm program #3: CAL
PROG4.BAS       5984  QuadTherm program #4: DATALOG
PROG5.BAS       6808  QuadTherm program #5: DAT REDUC

 January/February 1988, Issue #1

CAMMUX.BAS      2736  Steve Ciarcia's Camera Multiplexer
HANDSCAN.ARC  112504  Ed Nisley's Video Handscanner
SYNCGNV1.HEX   92288  RGBI-to-NTSC Converter EPROM


This code is posted as a convenience to Circuit Cellar INK
readers.  It is intended for noncommercial use only by micro
enthusiasts and experimenters who build Circuit Cellar INK
projects from scratch.

--------------------------------------------------------------------------

File area #  2 ... Ciarcia's Circuit Cellar files (BYTE)

This section contains files related to past Ciarcia's Circuit
Cellar articles which have appeared in BYTE magazine.

For each article, the first file in the list contains complete
descriptions of what files are available for that article.  Please
read that file before asking questions about what's available.

Files contained in this directory may not be reposted on other BBSs or
information services without express permission from Circuit Cellar Inc.

One or more of the following programs may be needed to break apart
certain "grouped" files found later in the list.

ARC.EXE        65339  Breaks apart .ARC files on IBM PC system
UNARC.COM       4736  Breaks apart .ARC files on CP/M systems
NULU.COM       15360  Breaks apart .LBR files on CP/M systems


 October, November, December 1988: Multiprocessor Mandelbrot Engine

OCT88.ART       1024  Text file describing what's available
LONGMULT.ASM    9216  Multiplication routines
DEFINES.INC     6351  Include file for LONGMULT.ASM
MACROS.INC      3739  Include file for LONGMULT.ASM
DRIVER.ARC     91136  Complete source code for DRIVER
CCME.ARC       64512  Compiled object code for the project

 August, September 1988: DDT-51 8031/8051 Development System

AUG88.ART       1152  Text file describing what's available
DDT51UPD.TXT    5248  DDT-51 update information (9/6/88)
DDT51NOT.TXT   11648  Some notes from Ed Nisley (9/6/88)
DEBUG31.ARC    54182  8031 debugger for IBM PC (12/4/88)
KERNEL.ARC      8297  8031 kernel for IBM PC (12/12/88)
TEST31.ARC     42907  Test code for circuit debugging (12/12/8
BLINKY.ASM      2560  Sample program for target computer
BLINKY.HEX       128  8031 hex file to match BLINKY.ASM
PS51A14.ARC    82092  8051 cross-assembler for the IBM PC
COPYERRS.ARC    5120  User-written tool for 8051 assembler
PSKERNEL.ARC    8576  User-converted DDT-51 KERNEL for PS51A14

 June, July 1988: HAL EEG Brain-Wave Monitor

JUN88.ART       1280  Text file describing what's available
HAL4.ARC       63752  Source for HAL EPROM and IBM PC code
BIO31V10.HEX     896  Version 1.0 of the HAL EPROM
FFT.BAS         4090  Fast Fourier Transform written in BASIC

 April, May 1988: SmartSpooler

APR88.ART       1024  Text file describing what's available
SPOOL11.HEX    25728  Version 1.1 of the SmartSpooler EPROM

 January-March 1988: BCC180 Computer/Controller

JAN88.ART       1280  Text file describing what's available
180MON10.HEX   19584  Version 1.0 of the BCC180 ROM Monitor

 November, December 1987: Circuit Cellar IC Tester

NOV87.ART       1024  Text file describing what's available
ICTROM12.HEX   74377  Version 1.2 of the IC Tester's EPROM

 May-August 1987: ImageWise Video Digitizer

MAY87.ART       2816  Text file describing what's available
REC10.HEX       2944  Version 1.0 of the Receiver EPROM
TRAN10.HEX      2176  Version 1.0 of the Transmitter EPROM
IWPAS.ARC      38528  Pascal source for ImageWise IBM programs
IWPICS.ARC     53632  Two sample ImageWise pictures
RECPROC.WS      6272  Procurement list for Receiver/Display
TRANPROC.WS     8064  Procurement list for Digitizer/Trans.
GRAB9600.COM   20736  Version of GRAB compiled for 9600 bps
SHOW9600.COM   20387  Version of SHOW compiled for 9600 bps

 March 1987: Infrared Master Controller

MAR87.ART       1664  Text file describing what's available
MCROM110.HEX   11904  Version 1.10 of Master Controller EPROM
MASTER.ARC     56064  Pascal source for IBM PC menu program
IRCMDS.DOC     10496  Protocols used between MC and IBM PC
.                      (Revised 7/12/88)

 February 1987: Build an Infrared Remote Controller

LEDPCM11.ASM    8704  Version 1.1 of program in Listing 1
LEDPCM11.PRN   14336  Assembly listing of LEDPCM.ASM
LEDPCM11.HEX    1024  Assembled code in Intel hex format

 October 1986: Circuit Cellar Serial EPROM Programmer

OCT86.ART       1024  Text file describing what's available
SEPROM16.HEX   46208  Version 1.6 of the SEP EPROM
SEPMAN.TXT     46592  Text of SEP users manual
SEPPARTS.LST    6400  Complete parts list for SEP

 September 1986: Hardware Data Encryptor

ENCRYPTR.HEX   10368  Version 1.0 of Data Encryptor EPROM
LOOPBACK.BAS    1152  BASIC program for loopback encrypting

 January 1986: 12-bit Analog-to-Digital Converter

JAN86.ART        384  Text file describing what's available
BCC30.BUG        896  List of BCC30 schematic errors

 November 1985: Build the World's Smallest 1200-bps Modem

MOSART.ARC     72639  All the files described in the article

 February 1985: Primitive Serial EPROM Programmer

FEB85.ART       1024  Text file describing what's available
EPROMBAS.BAS   19328  BASIC program listed in the article
EPROMBAS.ARC    8576  ARC file containing EPROMBAS.BAS 
EPROMBAS.EXE   20480  Compiled version of EPROMBAS.BAS
EPROM22.LBR    45952  CP/M program to control programmer
FEB85COR.TXT     768  List of schematic errors

This code is posted as a convenience to Circuit Cellar
readers.  It is intended for noncommercial use only by micro
enthusiasts and experimenters who build Circuit Cellar
projects from scratch.

--------------------------------------------------------------------------

File area #  3 ... User-modified Circuit Cellar files

This directory contains files related to past Circuit Cellar articles in
both BYTE and Circuit Cellar INK.  The programs and files are either user
written or are derivatives of officially released programs with user
modifications.  They are *not* official Circuit Cellar releases.

Use these programs *at your own risk*.  Circuit Cellar will not be
responsible for the proper operation of any program here and will not fix
bugs.  Contact the person who made the modifications if you have any
problems.

DDT51MOD.ARC   65280  Modified DDT-51 files
DDT51-C.ARC    66115  C Version of DDT-51 programs
DDT51C.ARC     24576  A Different DDT-51 host program

BIO2.ARC       43084  EGA BIO program (graph) for HAL project
BIO2.BAS        5372  Source for BIO2 program
BIO3-1.ARC     77824  HAL: 4 channels + graphics, sound; v1.1
XBIO.ARC       43904  A faster version of BIO.BAS for HAL-4
HAL2F.EXE      12288  HAL-4 data to file from COM1
MACHAL.SIT     13952  Mac demo program for HAL-4 project
HALHFT.DOC      2732  Documentation for HALHFT.C
HALHFT.C        7036  Hartley Transform (in C) for HAL project
HALGRAPH.ARC   26745  SULLIVAN' Plots a graph of data from HAL

MONITOR.ARC    11995  Low-level monitor for RTC31 board

LCDTEST.TC     21504  Turbo C translation w/ minor enhancement

--------------------------------------------------------------------------

File area #  4 ... Microprocessor development tools

This area contains cross-development tools and sample code for several
different microprocessors and microcontrollers.

 Intel 80xx series

BAS051.ARC     40704  BASIC Compiler v1.2 for 8051 family
PS48A14.ARC    58368  PseudoSam 8048 Xassembler ver 1.4
PS51A14.ARC    62464  PseudoSam 8051 Xassembler ver 1.4
PS96A14.ARC    57344  PseudoSam 8096 Xassembler ver 1.4
COPYERRS.ARC    5120  Tool for PS51A14 cross-assembler
TASM27.ARC    128647  Assembler: 8048,8051,6502,6805,Z80,...
UASM.ARC      158720  Universal Assembler: 8051,Z8,6805
DIS8051.ARC    11648  Disassembles 8051 HEX files into .ASM
DIS_8048.ARC    8576  Diassembler for the 8048 family
DIS51.LBR      30336  8051/8031 disassembler for CP/M
SKEL8051.ARC    6528  Skeleton for 8051 program w/serial I/O

 Motorola 68xx and 68xxx series

ASREF.ARC      31104  Full docs for the Motorola AS series asm
AS0.EXE        18432  Cross-assembler for MC6800
AS9.EXE        21504  Cross-assembler for MC6809
AS11.EXE       19456  Cross-assembler for MC68HC11
ASEMBLER.ARC   51518  Source for Motorola AS assemblers
SMALLC11.ARC   62976  SmallC compiler for 68HC11
RTE11.ARC      78848  Real-time kernel for the 68HC11
HC11FP.DOC     17792  Docs for HC11FP.ASM
HC11FP.ASM     76032  Floating-point code for 68HC11
FP11.ASM       11904  Floating-point code for 68HC11
MATH11.ARC     69632  Improved FP library for 68HC11
MATH11A.ARC    71296  Improved FP library for 68HC11
MATH11B.ARC    71936  Improved FP library for 68HC11
MUL16C11.ASM    1792  16-bit multiply routine for 68HC11
X68000.ARC    102912  68000 cross-assembler; Modula-2 source
PD68KCC.ARC   119936  MS-DOS "C" input, output 680x0.Source
6870X.ARC      30080  C source for the 6870x assembler
TBI68K.ARC     47207  Tiny BASIC source code for 680x0

 8080, NSC800, Z80, and HD64180

PSZ80A14.ARC   65536  PseudoSam Z80 Xassembler ver 1.4
ZMAC.ARC       81408  Z80 macro cross-assembler. C source incl
VASM.ARC       52088  8080/8085 xassembler (macros & conds)

 Other processors or host computers

Z8CA.ARC       43904  Z8 cross-assem for Amiga with 'C' source
Z8_IBM.ARC     43008  Z8 xassembler converted for IBM PC

 Utility programs for the IBM PC

BINTEL10.ARC   33792  Binary-to-Intel Hex converter
HEXFILE.COM    18432  Intel Hex File Conversion Utility
BINHEX.ARC      5167  A much better bin-hex-bin converter
SPLIT.EXE       8960  16-bit to 8-bit file splitter
S-RECORD.ARC   23296  Motorola S-Record <--> Binary conversion
CONVERT.DOC     2048  Documentation for CONVERT.EXE
CONVERT.EXE    55296  Convert Motorola S19 files to binary
CONVERT.PAS     3072  Pascal source for CONVERT.EXE

--------------------------------------------------------------------------

File area #  5 ... Electrical engineering programs & files

 The following are programs related to Electrical Engineering.  It is *not*
 possible to download individual files from within an .ARC file.

EEPD1.ARC     133120  Assorted public domain EE software #1
EEPD2.ARC     196352  Assorted public domain EE software #2
EEPD3.ARC     134784  Assorted public domain EE software #3
EEPD4.ARC      58496  Assorted public domain EE software #4
SCHEM.ARC      23424  Schematic CAD
PCB1.ARC      172416  PC board layout (1 of 2)
PCB2.ARC      128640  PC board layout (2 of 2)
LOGSIM.ARC     51691  Logic simulator
ROOTLOC.ARC    85061  Graphics-oriented root locus
RTLOC.ARC      96121  Graphics-oriented root locus
POLYROOT.ARC   54786  Polynomial root finder
PRFEXP.ARC     61486  Partial fraction expansion
TRANS.ARC      39712  Transistor amplifier design
TRANAMP.ARC   167340  Transistor amplifier design
RFTOOL.ARC    168936  Teledyne's RF Toolbox
3DSURFAC.ARC   51584  3D surface plotting program
FLODRAW.ARC    74752  Flowchart/schematic editor
FILTER11.ARC   57216  Active filter design tool
EE-CALC.ARC     7168  Handy circuit formulas program in BASIC
QCKT87.ARC    129024  RF design program, need 80x87
MATHPAK.ARC    84864  Math package of usable formulas
MATHPKII.ARC   45952  Math package with more formulas
NETWORK.ARC    42240  RF design tool
LOCI11.ARC    168320  World's Best Root Locus design program
FFT26.ARC     102656  256-Filter FFT for CGA/EGA (src & bin)
FASTFFT.ARC    19456  Table creation FFT program
SMITTY.ARC     67328  Smith Chart calculator (Pascal)
EE4120.ARC    204800  Antenna design from Virginia Tech
FREQDOM.ARC    89088  Extensive frequency domain analysis--EE
CHEBY.ARC      62336  High-, low-, and bandpass filter design
PSDOCS.ARC     59701  Docs for Pspice v4.0
PSPICE1.ARC   154591  PSpice Classroom version (Part 1)
PSPICE2.ARC   226100  PSpice Classroom version (Part 2)
PSPICE3.ARC    89600  PSpice Classroom version (Part 3)
FREETK.ARC    185771  TK Solver equation processor demo
FERRITE.ARC    16599  Calc mH/1000 for powd. ferrite toroids
IRON.ARC       17408  Calc uH/100 for powdered iron torroids
ROUTE.ARC     130816  PCB autorouter in `C'
PMI.ARC       128000  Search for analog parts..u input req'mts
LATTICE.ARC   141618  Assorted GAL s/w from the Lattice BBS
TI_PLUG.ARC   141312  TI's Programmable Logic User's Guide
ELECTRON.ARC  209287  Programs for electronics
FIBER.ARC      80640  BASIC fiber-optic progs (tokenized)

--------------------------------------------------------------------------

File area #  6 ... User-written ImageWise programs

The following are programs that have been uploaded by users of this
system designed to support the Circuit Cellar ImageWise video
digitizer/display system.  Note that ImageWise files from the July 1987
issue of BYTE may be found in the Ciarcia's Circuit Cellar files area (2).

 The first set of programs are for the IBM PC and compatibles.

EGA-PIX.ARC    76672  Display ImageWise files with EGA/18+colr
EGAIMW.ARC     25344  Fast display of IW pics on EGA
ICAP.C         11648  IW capture program written in C
SHOWVGA.ARC    43776  Display ImageWise pics on VGA two ways
VIDEO.ARC      89088  EGA/VGA and TIF support for ImageWise 
RG8.ARC        22016  Convert ImageWise files to GIF format
IMWSTRIP.ARC    4224  Utility to strip IW video control bytes
IMAGEWIS.TPU   16384  ImageWise files for Turbo Pascal Ver 4
IMW-EVGA.ARC   25344  Show four ImageWise pics on super VGA
VGA-VIEW.ARC   10240  ImageWise VGA viewer w/Tecmar 640 sup.
IW-HGC.ARC     35840  Display ImageWise pics on Hercules Adap
IWPRINT.ARC    26752  Print IW pictures on SG-10 or IBM
IW4TH.ARC      45696  Displays ImageWise in 256x244 VGA mode
SHOWSS.ARC     75648  Universal ImageWise display program
SHOWIW2.ARC     7672  Better IW displays w/capture, monitor
PIXELED.ARC   114560  EGA pixel editor V1.1

 The following programs are for the Macintosh.  Use STUFF140 to unpack files
 with the SIT extension.

STUFF140.BIN   97280  File archiver for the Macintosh
MACIMG20.SIT   60416  ImageWise capture/display/print for Mac
MACIMGES.SIT  100352  Three ImageWise pictures for MACIMG20

 The following programs are for the TI99/4A.

README          8064  Instructions for TI99/4A>ImageWise files
GRAB            1664  ImageWise GRAB program for TI99/4A (Pt1)
GRAC            1152  ImageWise GRAB program for TI99/4A (Pt2)
GRAB/S         11136  Source code for GRAB program on TI99/4A
SHOW             896  SHOW program for ImageWise on TI99/4A
CONVERT         2688  Convert GRAB file > TI artist file (Pt1)
CONVERU          896  Convert GRAB file > TI artist file (Pt2)
CONV1/S         9856  ImageWise > TI99/4A Source code Part 1
CONV2/S        10112  ImageWise > TI99/4A Source code Part 2
CONVERT/S        640  ImageWise > TI99/4A Source code Part 3

--------------------------------------------------------------------------

File area #  7 ... User-uploaded ImageWise pictures

 The following are digitized pictures which have been uploaded by users
 of this system.  They were all digitized using the Circuit Cellar
 ImageWise video digitizer and are meant to be displayed using the
 ImageWise video display board.  The pictures can also be displayed on
 an IBM PC with an EGA display adapter using the display programs found
 in the file IWPAS.ARC in the Ciarcia's Circuit Cellar files area (2).

ZSTLAWR.ARC    41984  Image of St. Lawrence Seaway
NOVASC.ARC     45312  Image from a Russian Meteor Sat
NOAA10.ARC     42880  Image from a NOAA10 Weather Sat
IMW-XWIM.ARC   66688  Two digitized weather pictures
TEXAS1IW.ARC   26752  ImageWise picture of TEXAS-GEOS Satelit
DISNEY.PIC     62720  ImageWise pic of castle at Disneyland
CHICAGO.PIF    62464  ImageWise picture of Chicago skyline

MACIMGES.SIT  100352  Three pictures for the Macintosh

--------------------------------------------------------------------------

File area #  7 ... User-uploaded ImageWise pictures

 The following are digitized pictures which have been uploaded by users
 of this system.  They were all digitized using the Circuit Cellar
 ImageWise video digitizer and are meant to be displayed using the
 ImageWise video display board.  The pictures can also be displayed on
 an IBM PC with an EGA display adapter using the display programs found
 in the file IWPAS.ARC in the Ciarcia's Circuit Cellar files area (2).

ZSTLAWR.ARC    41984  Image of St. Lawrence Seaway
NOVASC.ARC     45312  Image from a Russian Meteor Sat
NOAA10.ARC     42880  Image from a NOAA10 Weather Sat
IMW-XWIM.ARC   66688  Two digitized weather pictures
TEXAS1IW.ARC   26752  ImageWise picture of TEXAS-GEOS Satelit
DISNEY.PIC     62720  ImageWise pic of castle at Disneyland
CHICAGO.PIF    62464  ImageWise picture of Chicago skyline

MACIMGES.SIT  100352  Three pictures for the Macintosh

--------------------------------------------------------------------------

File area #  8 ... X-10 files

 The following are programs and files related in some way to the X-10
 power line control system.

SYNCHX10.ARC   46976  Synchronize PowerHouse clock w/PC clock
SENDX10.ARC    47232  Send X-10 codes from MS-DOS command line
X10BASIC.ARC   10752  Basic programs for the X-10 rs232 int
X10UNIX.ARC    44032  X-10 Powerhouse driver written in C

--------------------------------------------------------------------------

File area #  9 ... PC Pursuit files

 The following are files related to Telenet's PC Pursuit service.  Download
 the first file on the list for information about what PC Pursuit is.

PCPINFO         2164  General description of PC Pursuit
WHYUSE          2048  Why use PC Pursuit?
BILLING         1024  Price and billing information
EXCHANGE.ARC   41984  Complete information on cities covered

--------------------------------------------------------------------------

File area # 10 ... CP/M files and programs

 This area contains CP/M files and programs of all catagories.  They are
 separated into groups below for clarity.

 Files and programs for the SB180 or SB180FX single-board computer

SWTIME10.LBR   28928  SB180 support code for the SmartWatch
MDM180V2.LBR  112128  MDM740 terminal prog w/ SB180 overlay
MXO-SBS4.ZZ0   18176  MEX overlay for SB180 serial port
MXO-MO10.LBR   36352  MEX overlay for SB180/COMM180/MOSART
KERMIT.COM     14720  Kermit installed for SB180 serial port
MANJUL1.MOD    11264  GT180 Mandlebrot generator.  In Modula-2
GIFPAK.LBR      9216  GT180 GIF image display utility
M2TRMFIX.LBR    3328  Fix for ANSI mode bug in Modula-2
TM2UPD12.LBR   38912  Update for Z80 and 64180 Modula-2
SHELL11M.LBR    8576  Command line support for Modula-2

 Files and programs related to ZCPR3.  (ZCPR3 is a direct replacement for
 the CP/M 2.2 command processor that adds *many* enhancements.)

ZCPR33.LBR    109952  Version 3.3 of ZCPR
ZAPG.SZ        26112  ZCPR3 Application Guide
ZNODES44.LZT    3456  List of Z-Nodes around the world

 CP/M 2.2 utility programs

DAZLSTAR.LBR   81280  Full-screen Z80 disassembler
DASM16.LBR     65536  8080/Z80/HD64180 disassembler
XIZI-3.LBR     19456  Intel-Zilog, Zilog-Intel converter
DE-LBR.COM      6272  Break apart .LBR files
DE-LBR.DOC       256  Documentation for DE-LBR.COM
FBAD60.ASM     37760  Find bad sectors on any disk
FINDF22.LBR    18048  Find files on range of drives
HSH14.LBR      28800  History SHell command line editor
HSHBUG.DOC      3968  HSH14 bug report
IOBUG.LBR      50816  Screen-oriented I/O debugging system
MLOAD24.LBR    27008  Convert HEX files to COM files
SQ.COM          6016  Squeeze: file compressor (*.?Q? files)
USQ.COM         2176  Unsqueeze: file decompressor (*.?Q?)
Z8E.LBR        89600  Excellent full-screen Z80 debugger
Z8E-SRC.LBR   114944  Source for Z8E.LBR
Z8E-ROM.LBR    66816  ROM-based version of Z8E
18E.LBR        23168  Excellent full-screen HD64180 debugger
18E-SRC.LBR    92800  Source for 18E.LBR
CRUNCH24.LBR   31104  Compression utility; makes *.?Z? files
LT23.LBR       39040  Lists and/or extract *.?Z? filesFromLBR
PALASM.ARC     61258  PAL equation assembler; in FORTRAN
Z280ASM2.LBR   22528  Z280 assembler (new version)
UNARC16.ARK    38656  UNARC for CP/M; rename to UNARC16.COM
DDIR.COM        3584  Displays a directory with size
SORTMK22.LBR   32512  General small file sort package.
PERSET16.LBR   35968  Make peripheral setup programs.
NXSET13.LBR    14848  Send printer codes for Micronics NX Star
MXSET13.LBR    14464  Send printer control codes for Epson MX
DOTSET12.LBR   14848  Send printer codes for DotsPerfect Epson
BA24.LBR       30720  Build Aliases from .CMD files.

 CP/M 2.2 modem programs

MDM180V2.LBR  112128  MDM740 terminal prog w/ SB180 overlay
MEX114.LBR    154624  MEX 1.14 terminal program (generic)
MXO-SBS4.ZZ0   18176  MEX overlay for SB180 serial port
MXO-MO10.LBR   36352  MEX overlay for SB180/COMM180/MOSART
KERMIT.COM     14720  Kermit installed for SB180 serial port
MB3SB180.Z80    8320  MBOOT modem bootstrap program for SB180
IMP245.LBR     80128  A CP/M communications package
IMP-C128.COM   18432  Communications program for C128 computer
ZMP-OVL3.LBR   64256  Nine ready-made overlays for ZMP13.COM
RZMP13.LBR     34304  The "other end" for ZMP. Runs under BYE.
ZMP15.LBR      79872  X/Y/ZMODEM + terminal program for CP/M
C128NEW2.LBR   83968  Need to use MEX on C128

 Miscellaneous files and programs

HD64180.WS     26368  Good description of HD64180 features
BIGCAL22.LBR   28288  Create a large calendar
X25.LBR       100992  X.25 System for 8080, with source code
TNYBAS31.LBR   38656  Tiny BASIC V3.1 with source code
RESISTOR.MOD    5248  Prints parallel resistor combinations
BRAD2A.LBR    108416  CP/M printer fonts--Any doc, many fonts
BRAD2B.LBR     92800  Additional fonts for BRAD2A
BUZZ11.LBR      7680  Make buzzword phrases for any occasion.

--------------------------------------------------------------------------

File area # 11 ... Utility programs for the IBM PC

 The following are utility programs for the IBM PC and compatibles:

Z80MU310.ARC  178816  CP/M 2.2 emulator for the IBM PC
22DSK124.ARC  218112  Read CP/M disks on IBM PC
ARC602.EXE    135865  ARC v6.02, FAST and does subdirs
PKX35A35.EXE   71680  Alternative to ARC; handles new method
ARCIT31.ARC    66560  Front-End Shell for PKARC/PKPAK - GREAT!
PAK10.ARC      60416  Archiver (compt w/ARC,ARCE,PKARC)
NARC.ARC       50816  A very handy uNARC utility
LHARC10.COM    29022  Best yet compression/decomp utility
PKZ102.EXE    136192  PKZIP/PKUNZIP ver 1.02 file compression
SHEZ481.ARC   114439  Zip,Arc,Pak Shell; Supports Zip 1.02
LUE192.COM      2048  Extract files from CP/M .LBR files
LU.COM         24320  CP/M .LBR file utility for IBM PC
NUSQ.COM        2176  Unsqueeze *.?Q? files
UNCR232.ARC    16384  Utility for uncrunching *.?Z? files
LIST64A.ARC    58368  Powerful file viewing utility
CPUTYPE.ARC    10240  Differentiate between 8086/80286/80386
PAS-TO-C.ARC   33792  Turbo Pascal to C converter
PROFILER.ARC   30336  Programmer's profiler; C and assembly
DISASMBL.ARC  102272  MS-DOS disassembler with source code
PCPLUSTD.ARC  235267  Procomm Plus test drive (comm program)
TERMINAL.EXE   35712  Dumb terminal program for the IBM PC
XPORT13B.ARC   31205  Nice PC-PC file xfer utility via RS-232
VT100.ARC     129024  VT52/100/102 terminal emulator with docs
LPTX.ARC       18432  Redirect printer output to disk file
LPT.ARC          640  Swap LPT1 and LPT2
EXE2HEX.ARC     2432  Converts an EXE file to an Intel hex fil
SPLTFILE.ARC   45056  File splitter for those HUGE files
WHERE26.ARC    17518  WHEREIS: find files on disk (and ARCs)
TELEDISK.ARC   57231  FD image to HD file w/compression
STRIP.ARC       6016  Removes tabs and EOF marks; Ver 1.01
LOCATE88.ARC   25856  .EXE to .HEX relocate utility for 8088
IAU_19D.ARC    96059  Optimize interleave; leaves data intact!
2DCAD1.ARC    220800  Real CAD that went PD after 3-D Rev (1)
2DCAD2.ARC    205440  Part 2 of 2-D CAD

--------------------------------------------------------------------------

File area # 12 ... Miscellaneous IBM PC files

 The following are assorted files and programs meant for use
 specifically on an IBM PC or compatibles:

FSP.ARC        41984  FLU_SHOT+...Protection from viruses.  I
.                      guarantee this to be good since it comes straight
.                      from the author.  Supercedes FLUSHOT3.
CHK4BOMB.ARC   12288  Checks potential viruses before running
BOMBSQAD.DOC    6144  Documentation for bombsquad protector
BOMBSQAD.COM    3072  The write, read, format protector
VIRUSCC.TXT     2944  Description of virus that hit Lehigh U.
RISESET.EXE    19072  Compute sunrise/set for anywhere/time
NNS10.ARC      40960  200-neuron Neural Network Simulator
NNBRAIN.ARC    11264  Neural Net "Brain-Maker" from DDJ
NNTTT.ARC       9216  Neural Net plays Tic-Tac-Toe
DRAW2ME.ARC   103424  Draw pixs over modem (CGA)
AUDIOLAB.ARC   29696  Calculations provide data about stereo.
CHAOS.ARC      98304  Model chaotic systems (from Micro-C)
SWTIME.ARC     23808  SmartWatch stuff for IBMs (DS1216E)
MLINK16.ARC    35712  MEGAlink external protocol
EEPROM.ARC     31744  Simple (and cheap) EEPROM programer
KEYS310.ARC    28800  Info on IBM keyboards of various types
DIGITIZE.ARC   64512  Plays digitized voice/music on PC spkr
DIGITIZ2.ARC   57088  LaserJet schematic and song "Daisy"
CRYPTO.ARC      7168  Scramble DIGITIZE.ARC output files
TRAN.ARC       38991  Translates ASCII text to speech
SERVO88.ARC     6016  Demo of servo control
CHEMVIEW.ARC   51200  3-D models of molecular formulae
WEATHER.ARC    56320  Weather forecasting program.  Neat!
CHKCOP.ARC      9216  80x87 Diagnostic by Intel
RNA.ARC         8576  Random number analyzer
STS26.ARC      65536  Space shuttle tracking program
SCUBA.ARC      45368  A must for divers; excellent log plus
MSCHRTV2.ARC   16512  MS C 5.1 Hi Res Timer Toolbox
TPHRTV2.ARC    12928  Turbo Pascal V5 Hi Res Timer Toolbox
TCHRTV2.ARC    16512  Turbo C Hi Res Timer Toolbox
CHILL.ARC       1152  Windchill function--Turbo Pascal/Turbo C
NBS.ARC        93824  The NBS time program for IBM PCs
FRACT70.ARC   130336  Fractal Generator (w/source) up to VGA
MAP-SRC.ARC    21504  Draws perspective maps on screen Turbo-C
MAP-BIN.ARC   205084  Executable code & data for drawing maps
PROCALC.ARC    96391  Calculates complex user-defined formulae
FFP225.DOC      2688  Intro docs for a PD IBM PC Forth
FFPC225A.ARC  132224  IBM PC Forth (Part 1)
FFPC225H.ARC   82944  IBM PC Forth (Part 2)
FFPC225S.ARC  130176  IBM PC Forth (Part 3)
DSTUFF.ARC    100255  The colorful info package update
CALENDAR.ARC    9984  Ada Calendar pkg source - PC Hi-Res Time
MTE.ARC        22528  4800 bps on a 2400-bps modem!
HP11C.ARC      48982  On-screen HP-11C calculator
TDD5PT2.ARC    12288  Simulate Deaf Teletype (Software MODEM)
EMSIM.ARC      12034  Extended/expanded memory program
VMIX210.ARC   178157  Multiuser/tasking operating system
BMENU.EXE      14592  A neat program for batch file windows
SPEEDUP.ARC    17920  Speed up your IBM PC

--------------------------------------------------------------------------

File area # 13 ... Miscellaneous text files

 The following are miscellaneous text files which deal with a whole range of
 topics.  Note that many of the files are in ARC format to take advantage
 of ARC's compression facility.

RS232EX.ARC    11264  A description of RS-232
FIGHTSEA.ARC    8192  Info on SEA's actions against PKWARE.
EISA-ALL.ARC   12288  Text file describing EISA bus
PRIVACY.ARC    33357  E.C.Privacy Act of 1986 (No Scanners!)
CCSP8149.ARC   39936  Patches for CCSEP Serial EPROM Programme
MENGINE.NOT     5280  Straight dope on Mandelbrot Engine
8251A.ARC       4096  How to program the 8251A USART
PARALLEL.ARC    8192  IBM PC parallel port tutorial
LIM_SPEC.ARC   46336  Lotus/Intel/Microsoft extended mem doc
INTELHEX.ASC    3968  Example of how to make Intel Hex records
ZNODES44.LST    5888  April '87 list of Z-Node ZCPR3 BBSs
CTASK.ARC     131072  Multitasking example with "C" source
SMART.ASM       7168  Sample IBM PC/SmartWatch source code
WXMATION.ARC   10624  Weather info from NOAA by modem
WEATHER.DOC    25088  WXMATION.ARC unarced
KEYSCAN.DOC     3968  Example of how to do a 4x5 mux keyboard
ADC.DOC         7168  Example of how S.A. A/D works
DIRTYD8A.ARC   32768  02/21/88 Dirty Dozen Trojan & Virus list
USBBS59.ARC    43774  April 1,1989 Darwin U.S. BBS list
SPEEDUP.ARC    17830  Pieces to help speed up your IBM PC
HACKSUR.TXT     7168  Survey of your attitude to hacking
VIRUSD.ARC     31274  Virus discussion by IBM-very interesting
XMS.ARC       143360  Microsoft's ExTended Memory Spec. w/src
MODEM7.ARC      6881  Pascal source for MODEM7 (XMODEM)
CARCODES.TXT    3456  How to read GM car computer diag codes
KIDNAP2.TXT     7552  Teach kids about stranger abduction
KIDNAP.TXT      5248  Recognize & report abducted children
DOPEHS.TXT      3456  Recognize and report dope houses
YZMODEM.ARC    87040  Definitive description of X/Y/Z/MODEM
USPCP62.ARC    17922  Darwin's USBBS62 list for PC Pursuit
XEROXPCB.TXT   12288  Use a copier to make circuit boards
E_CAD.LST       3328  A list of ECAD prgms and who writes them

--------------------------------------------------------------------------

File area # 14 ... Files that don't fit elsewhere

 The following files are here because they just don't fit in anywhere else
 on the system.

CENTRONX.ARC    9144  Centronics driver for 8255 on BCC52
XMODEM.C        6784  xmodem example source code in "C"
NEURAL.C       11392  A Neural Net simulator
VISION.ARC     15360  Vision neural network
HAM.ARC         4096  Hamming neural network
XINU.ARC       74752  C source code for UNIX-like O/S
XINU-1.ARC     33792  Missing file, Z80 goodies, news
DAA.ARC        22912  DAA in Orcad and FX80 printer output
DAAOPT.ARC     12544  Optoisolated telephone interface
PCPFONS.ARC    64828  Telix 3.11 PC Pursuitable Phone Dirs
RCCL-1.ARC    181095  Purdue U  Robotics "C" Library disk 1/3
RCCL-2.ARC    158664  Purdue U  Robotics "C" Library disk 2/3
RCCL-3.ARC    142233  Purdue U  Robotics "C" Library disk 3/3
I3ECONV.EXE    33098  Converts IEEE754 <-> single-prec format
XARCMAC.EXE    16000  DeArchives ArcMac files
PIDWARE.ARC    38400  Optomux PID sample programs

DIGSIM.SIT     33920  Digital Circuit Simulator for Macintosh
MANDEL.SIT     26240  Mandelbrot generator for Mac II only
UNPACK.MAC     61952  Will unpack Packit and Stuffit files
ARCMAC.SIT    126848  Stuffit file for Macs
ARCPOP.MAC     29440  Decompress ARC files on a Macintosh

CHAMELEON      47104  Apple File Xfer Pgm for ProDos, CP/M, Do
SHRINKIT.SYS     384  Basic launcher for Shrinkit
SHRINKIT.DOC   30720  Documentation for Shrinkit


From owner-pc532%daver@mips.com Tue Mar  6 14:01:32 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Tue, 6 Mar 90 10:54:01 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: Miniscribe
Status: O

[In the message entitled "Re: Miniscribe" on Mar  6,  9:52, uunet!convex.com!bobm writes:]
> I lost (or never received) the original mail on the Miniscribes.  I
> can't find any record of who was taking the orders.  Whoever you are,
> please note that I'll take one (1) and send me email; I'll send you my
> shipping address and some money and...
> 

I don't think anyone was taking orders yet (please correct me if I
am wrong!)

I called about them yesterday. They are for real, and they do have lots of
them. I talked to Cynthia there yesterday. The price is quite negotiable.
We are looking at $850-$900 per drive (plus tax). 

Would someone like to collect the money and ship the drives out? At this
price, they are not willing to do drop shipments, or individual invoices.
They want $1095 quantity one, and $995 for groups of 5.

Dave Rand
+1 408 434-0600 X4555 work
+1 408 733-4125 home


-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From owner-pc532%daver@mips.com Tue Mar  6 15:37:51 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: Re: Miniscribe
To: pc532@daver.bungi.com
Date: Tue, 6 Mar 90 12:23:53 PST
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls (Karl Swartz)
Status: O

> Would someone like to collect the money and ship the drives out? At this
> price, they are not willing to do drop shipments, or individual invoices.
> They want $1095 quantity one, and $995 for groups of 5.

I'm willing to do this, and since I'm only a few miles away from
them it probably makes more sense for me to do it than somebody
far away.

To start, why doesn't everybody who wants one (or more) of these
drives send me mail (to kls@ditka.uucp, or daver.uu.net!ditka!kls
and *NOT* to the pc532 mailing list) telling me how many you are
interested in at the $995 (plus 7 1/4% tax and shipping) price.
Don't send any money yet -- I know we have at least five and can
get the $995 price but if there is enough interest perhaps we
can get the price down even further.

For those who missed earlier messages, this is a MiniScribe 9380
disk drive, which provides about 335 megabytes of storage (380
unformatted) at an average access speed of 16 ms.  It's a 5 1/4"
full-height drive if I'm not mistaken, and Benjamin Pan reports
that the ESDI version appears to be reasonably reliable.

As for warranty, MiniScribe is still in business but not in very
good shape at all, so the chances of getting any warranty through
them is slim if not nil.  The folks selling these drives will
provide a one-year warranty on them, but you may have to go thru
me if I buy them since Dave reports they don't want to deal with
multiple invoices.  I'll see about transferring the warranties
when I talk to them about prices.


From owner-pc532%daver@mips.com Tue Mar  6 17:33:02 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: rjohnson@kiwi.mpr.ca (Robbin Johnson)
To: pc532@daver.bungi.com
Date: Tue, 6 Mar 90 11:20:44 PST
Subject: Re: Miniscribe 9380 drives. 
X-Mailer: Elm [version 1.5]
Status: O


> > >> While we're on the subject of ordering stuff, I've recently run
> > >> across a special on SCSI hard disks at Corporate Systems Center.  
> > >> They have a Miniscribe 9380 SCSI 335MB 16ms HD for $1095, or 
> > >> $995 in quantities of 5+.  I realize this is quite a bit of money,
> > >> but it's one hell of a deal for a hard disk that large.  Would
> > >> anyone be interested in a group order to get the discount?  CSC
> > >> is offering a one-year warranty, since Miniscribe went under.  

I think I'll want 3-4 units.  Depends on the exact pricing.  One each for the
two pc532 systems a friend and I are building, and one each for two other
systems I have... this seems like a really good price for this sized drive!

Bdale



From owner-pc532%daver@mips.com Wed Mar  7 00:35:50 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Tue, 6 Mar 90 21:22 PST
From: dlr@daver.bungi.com (Dave Rand)
To: pc532@daver
Subject: Cut off date for next run
Status: O

We will cut off orders for the next run of the PC532 PCB March 31, 1990.
Please mail your orders to pc-order@daver.bungi.com. By George's order,
if you don't have your Name, Address and Telephone number in the mail
your order will be refused.

Please plan to have your cheques in by April 21, 1990. The boards should
be back towards the end of April, but we will let you know the exact
dates as we get them.

The price remains at $200 USD. No kits of parts will be available from
us, but I have had some indication of one of the list members doing
the kitting. If it pans out, I'm sure he will post and let you know.

The Ethernet board (ET532) will be run at the same time. We don't have
firm prices on that yet, but expect that it will be in the $200-$250
range. We will do only a small run of these boards (10 or so), to
make sure they are functional. If you are interested in participating,
please send private mail to George <george@wombat.bungi.com> or
Dave <dlr@daver.bungi.com>.

Thanks again for your interest.
Dave Rand / George Scolaro


From owner-pc532%daver@mips.com Wed Mar  7 04:08:47 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: power connections
To: pc532@daver
Date: Wed, 7 Mar 90 1:05:26 PST
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls (Karl Swartz)
Status: O

George, my power supply, along with several others I've looked at,
has two 6-pin connectors rather than one 12-pin connector.  One is
labelled P8, the other P9.  Which one connects to which half of the
pc532 power connector?  (I'm posting here since I suspect other may
have similar power supplies.)

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Wed Mar  7 11:32:37 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: george@wombat.bungi.com (George Scolaro)
Date: Wed, 7 Mar 90 08:07:25 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: power connections
Status: O

[In the message entitled "power connections" on Mar  7,  1:05, Karl Swartz writes:]
> George, my power supply, along with several others I've looked at,
> has two 6-pin connectors rather than one 12-pin connector.  One is
      ^^^^^^^^  this is the normal configuration.

> labelled P8, the other P9.  Which one connects to which half of the
> pc532 power connector?  (I'm posting here since I suspect other may
> have similar power supplies.)
> 
> --
> Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls

P8 should be towards to top of the board (near the crystal for the
DUARTs) and P9 towards the bottom of the board. You should end up
with the black wires (the grounds) being in the middle of the 12
pins (4 of them), the red (+5) at the bottom - i.e. refer to the
silkscreen legend. Also, you must have the connector (on the PCB)
with pins facing out.

-------------------------
  _____			|
  |   | XTAL		|
  |   |			|
  -----			|
   | |		_____	|
		|  :|P8	|
		|  :|---|------- Pins facing out
		|  :|	|
		|  :|	|GND  BLACK (4 of them)
		|  :|	|
		|  :|P9	|+5   RED (3 of them)
		-----	|

regards,

-- 
George Scolaro
george@wombat
(try {pyramid|sun|vsi1|killer} !daver!wombat!george) [37 20 51 N / 122 03 07 W]

From george%wombat%daver@mips.com Thu Mar  8 00:31:18 1990
Flags: 000000000000
From: george@wombat.bungi.com (George Scolaro)
Date: Wed, 7 Mar 90 20:30:52 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: budd@bu-it.bu.edu (Phil Budne)
Subject: Re: 74xx32
Status: O

[In the message entitled "74xx32" on Mar  7, 15:00, Phil Budne writes:]
> I recieved my kit with 2681's and a 74AC32.  Is this an accepable
> combination, or will the 73xx32 work with 2681s ot 2692s

The 74AC32 must be used with the 2692. Either the 74AC32 or 74AS32
can be used with the 2681.

> What is the difference between the two DUARTs?  I see the 2692
> is CMOS and has a "power down" mode.

Not much. The main difference is the CMOS stuff. The power down is useless
for our application since it turns most of everything off, its really only
useful for embedded use etc. A couple of things that were a bit 'un-nice'
have been fixed in the 2692, but again nothing major. The bottom line is
that as far as the pc532 goes the 2681 and 2692 are compatible.

> What *ARTs are on the et532 daughter board design?

The et532 uses up to 2 Octarts (8 channels/device - 84 pin plcc), they are
Signetics SCC2698BC1A84 (full part #).

regards,


-- 
George Scolaro
george@wombat
(try {pyramid|sun|vsi1|killer} !daver!wombat!george) [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Fri Mar  9 12:52:09 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: gcc 1.37.1 ns32k.md patch
Date: Fri, 09 Mar 90 02:09:51 EST
From: David Taylor <taylor@Think.COM>
Status: O

In tonight's mail I received the following patch, from rms, to the
ns32k.md file in gcc version 1.37.1.  With this patch, gcc configured
for the ns32k is able to successfully cross compile itself.

Replace the movdi/movsi patterns with what follows.

David

(define_insn "movdi"
  [(set (match_operand:DI 0 "general_operand" "=&g<,*f,g")
	(match_operand:DI 1 "general_operand" "gF,g,*f"))]
  ""
  "*
{
  if (FP_REG_P (operands[0]))
    {
      if (FP_REG_P (operands[1]) || GET_CODE (operands[1]) == CONST_DOUBLE)
	return \"movl %1,%0\";
      if (REG_P (operands[1]))
	{
	  rtx xoperands[2];
	  xoperands[1] = gen_rtx (REG, SImode, REGNO (operands[1]) + 1);
	  output_asm_insn (\"movd %1,tos\", xoperands);
	  output_asm_insn (\"movd %1,tos\", operands);
	  return \"movl tos,%0\";
	}
      return \"movl %1,%0\";
    }
  else if (FP_REG_P (operands[1]))
    {
      if (REG_P (operands[0]))
	{
	  output_asm_insn (\"movl %1,tos\;movd tos,%0\", operands);
	  operands[0] = gen_rtx (REG, SImode, REGNO (operands[0]) + 1);
	  return \"movd tos,%0\";
	}
      else
        return \"movl %1,%0\";
    }
  return output_move_double (operands);
}")

;; This special case must precede movsi.
(define_insn ""
  [(set (reg:SI 17)
	(match_operand:SI 0 "general_operand" "rmn"))]
  ""
  "lprd sp,%0")

(define_insn "movsi"
  [(set (match_operand:SI 0 "general_operand" "=g<,*f,g")
	(match_operand:SI 1 "general_operand" "gx,g,*f"))]
  ""
  "*
{
  if (FP_REG_P (operands[0]))
    {
      if (GET_CODE (operands[1]) == REG && REGNO (operands[1]) < 8)
	return \"movd %1,tos\;movf tos,%0\";
      else
	return \"movf %1,%0\";
    }
  else if (FP_REG_P (operands[1]))
    {
      if (REG_P (operands[0]))
	return \"movf %1,tos\;movd tos,%0\";
      return \"movf %1,%0\";
    }
  if (GET_CODE (operands[1]) == CONST_INT)
    {
      int i = INTVAL (operands[1]);
      if (i <= 7 && i >= -8)
	return \"movqd %1,%0\";
      if (i < 0x4000 && i >= -0x4000)
#ifdef GNX_V3
	return \"addr %c1,%0\";
#else
	return \"addr @%c1,%0\";
#endif
      return \"movd %1,%0\";
    }
  else if (GET_CODE (operands[1]) == REG)
    {
      if (REGNO (operands[1]) < 16)
        return \"movd %1,%0\";
      else if (REGNO (operands[1]) == FRAME_POINTER_REGNUM)
	{
	  if (GET_CODE(operands[0]) == REG)
	    return \"sprd fp,%0\";
	  else
	    return \"addr 0(fp),%0\" ;
	}
      else if (REGNO (operands[1]) == STACK_POINTER_REGNUM)
	{
	  if (GET_CODE(operands[0]) == REG)
	    return \"sprd sp,%0\";
	  else
	    return \"addr 0(sp),%0\" ;
	}
      else abort (0);
    }
  else if (GET_CODE (operands[1]) == MEM)
    return \"movd %1,%0\";
  /* Check if this effective address can be
     calculated faster by pulling it apart.  */
  if (REG_P (operands[0])
      && GET_CODE (operands[1]) == MULT
      && GET_CODE (XEXP (operands[1], 1)) == CONST_INT
      && (INTVAL (XEXP (operands[1], 1)) == 2
	  || INTVAL (XEXP (operands[1], 1)) == 4))
    {
      rtx xoperands[3];
      xoperands[0] = operands[0];
      xoperands[1] = XEXP (operands[1], 0);
      xoperands[2] = gen_rtx (CONST_INT, VOIDmode, INTVAL (XEXP (operands[1], 1)) >> 1);
      return output_shift_insn (xoperands);
    }
  return \"addr %a1,%0\";
}")

From owner-pc532%daver@mips.com Fri Mar  9 12:53:20 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 9 Mar 90 15:03:36+1100
From: s871943@minyos.xx.rmit.OZ.AU (Simon Burge [Snark])
To: pc532@daver.bungi.com
Subject: Australian prices for 32k chipset
Status: O

G'day folks,

I guess this really only applies to the people in Australia (and all prices
are in $AUS)...

One of the kids I go to school with told me he was quoted $750 for the
CPU/FPU/ICU set, so I decided to get serious about checking out the prices.
I've been talking to a guy at NSD in Melbourne (the distributors for NatSemi
here), and there's some good news and some bad news.

The FPU unit price is about $202 plus tax (20%), and the ICU is $46 plus tax,
both in single unit quantities.  In 5 unit quantites, the prices drop to
something like $178 plus tax and $37 plus tax respectively.  The FPU price is
about a 1/3 of the standard price ($595 plus tax), but once I meantioned I was
a student working on a high performance pc project, and the guy spoke to the
NatSemi rep, the price came tumbling down.

The big killer is however the '532 - $1195 plus tax, or $970ish plus tax for
10 or more.  Apparently, NatSemi are pushing the 32gx32, so they put the price
of the '532 through the roof.

How do these prices sound compared with current US prices?  I know Dave was
talking about $US1k for the lot earlier, but what about individual chip prices?
Hopefully we may be able to get the '532 in the States and the rest here.  By
the way, the above parts have about an 8 week delivery time, which is a bit of
a bummer.

regards,
  Simon.

--
Simon Burge,                        Royal Melbourne Institute of Technology.
s871943@minyos.xx.rmit.oz.au

From owner-pc532%daver@mips.com Fri Mar  9 13:03:35 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: gcc 1.37.1 (update)
Date: Fri, 09 Mar 90 09:45:12 EST
From: David Taylor <taylor@Think.COM>
Status: O

I may have spoken too soon.  While it successfully cross compiles itself
>From a vax, it doesn't successfully cross compile itself on a sun4.

More details when I get them.

David

From ames!zorch!ditka!kls@XN.LL.MIT.EDU Tue Mar 13 06:12:44 1990
Flags: 000000000000
Posted-Date: Tue, 13 Mar 90 2:08:35 PST
Subject: group disk buy
To: ditka!pc532-disks, pc532@daver.bungi.com
Date: Tue, 13 Mar 90 2:08:35 PST
X-Mailer: ELM [version 2.2t PL7]
From: ames!ditka.UUCP!kls@XN.LL.MIT.EDU (Karl Swartz)
Status: O

I've received mail from over a dozen people indicating interest in a
total of 17 drives (two tentative) plus at least two more possibles:

  1	kls@ditka.uucp (Karl Swartz)
  1	dlr@daver.bungi.com (Dave Rand)
  1	george@wombat.uucp (George Scolaro)
  1	rjohnson@kiwi.mpr.ca (Robbin Johnson)
  1(+)	taylor@think.com (David Taylor)
  1(+)	johnc@manatee.uucp (John L. Connin)
  3	bdale@col.hp.com (Bdale Garbee)
  1(?)	bdale@col.hp.com (Fred Schneider c/o Bdale Garbee)
  1(?)	s892024@minyos.xx.rmit.oz.au (Richard Muirden)
  1	mark-geisert@ladc.bull.com (Mark Geisert)
  1	budd@bu-it.bu.edu (Phil Budne)
  2	pell@isy.liu.se (Pell Emanuelsson)
  1	buck@siswat.lonestar.org (A. Lester Buck)
  1	david@dogmelb.dog.oz.au (David Le Blanc)

If you expected to see your name on this list but it's not there I
didn't get any mail from you; please try again or send to the pc532
mailing list if you feel you must.

I'll be talking to Corporate Systems Center tomorrow to nail down a
price, but with this kind of volume it should be quite attractive.
The warrantee question will also be discussed then.  More tomorrow.
I'm also exploring the best way to buy the things so non-California
residents don't have to pay the sales tax without instead saddling
California residents with freight to Timbuktu and back in addition
to taxes.  Again, more tomorrow.

For those who haven't already heard, Corporate Systems Center (not
CDC) in Sunnyvale, California, bought MiniScribe's entire inventory
of 9380S disk drives.  These are full-height 5 1/4" disk drives with
a formatted capacity of 335 megabytes and 16ms access time.  They
have a synchronous SCSI interface which should work quite nicely in
a pc532 system.  CSC has advertised them for $1095; in the quantity
we are buying we should be able to get the price below US$900.

The cloud behind this silver lining is that MiniScribe has filed for
bankruptcy, and while they are continuing operations these drives
should be view as orphans.  Though new (1990 product) there is not
a warrantee from the manufacturer; CSC is however providing a one-
year warrantee.

 -- Karl

From owner-pc532%daver@mips.com Tue Mar 13 05:13:53 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.UU.NET
Subject: Re: HD64180 for floppy 
Date: Mon, 12 Mar 90 15:13:27 MST
From: Bdale Garbee <bdale@col.hp.com>
Status: O

> >I'm already looking at good ways to do a card with 8530's or equivalents and
> >DMA for fast packet radio links...

> Me too!!!!!!  Please tell if there is any progress/ if I can be of any help!
> I suppose to get a pc532 from Dave soon...

A friend of mine, Don Lemley N4PCR, has just gotten a standalone card working
with a Motorola 68302 and an 8530.  The 3 high-speed ports on the 68302 give
up to 6Mbit/sec, the 8530 ports handle "low speed" ports up to about 38400bps.
The anticipated aggregate throughput of the card is about 1.5Mbits/sec.

I may try to get permission from him to do a version of the card with a SCSI
interface to plug in to the pc532.  It would be a bit expensive, but it would
also be a screamer...

Bdale



From owner-pc532%daver@mips.com Tue Mar 13 14:07:53 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Tue, 13 Mar 90 10:56:53 PST
X-Mailer: Mail User's Shell (6.5 4/17/89)
From: gs@vw25.chips.com (George Scolaro)
To: pc532@daver.bungi.com
Subject: Re: Clock Termination Resistors
Status: O

[In the message entitled "Clock Termination Resistors" on Mar 13, 11:18, Jerry Callen writes:]
> 
> I think George already answered this and I missed it. What values should be
> used for the clock line termination resistors?

Refer to the documentation that came with the Kit, i.e. the functional
description document. 220/330 ohm seems to work fine, check the document for
the actual placement etc.

regards,

-- 
George Scolaro
(try (pyramid|hoptoad|sun|vsi1)daver!vw25.chips.com!gs)

From ames!zorch!ditka!kls@XN.LL.MIT.EDU Wed Mar 14 05:50:23 1990
Flags: 000000000000
Posted-Date: Wed, 14 Mar 90 1:34:14 PST
Subject: MiniScribe disk buy -- the fine print!
To: pc532@daver.bungi.com, ditka!pc532-disks
Date: Wed, 14 Mar 90 1:34:14 PST
X-Mailer: ELM [version 2.2t PL7]
From: ames!ditka.UUCP!kls@XN.LL.MIT.EDU (Karl Swartz)
Status: RO

Well, folks, I talked to Corporate Systems Center and my bank
today.  The bad news is ... nonexistant!

They'll sell us the disk drives for $895 each as long as I get
orders for at least 25.  We're already quite close to that, and
if we're one or two short they'll probably still give us that
price.  Residents of California *ONLY* will owe an additional
$64.89 per drive for state sales tax.

These drives will come with a one-year warrany directly from
Corporate Systems Center.  All you'll need to do is call them
(not me) with your drive's serial number and an invoice number,
which you'll receive with the drive or via e-mail.

Here's a complete rundown of the specs from CSC's brochure:

    Drive:			MiniScribe 9380S
    Capacity (unformatted):	380MB
    Capacity (formatted):	335MB
    Average access:		16ms
    Track-to-track seek:	5ms
    SCSI transfer rate:		4MB/sec
    MTBF:			100,000 POH
    Dimensions:			5 1/4" full height

I'm planning on picking the drives up next Thursday (March 22)
so I need to have money from you by Wednesday, March 21st.  The
total cost per drive is as follows:

    MiniScribe 9380S 335MB 16ms			$ 895.00
    handling (bank, paperwork, etc.)		    2.50
						--------
						$ 897.50

plus:

    sales tax (California residents only)	   64.89
    shipping (United States -- UPS Blue Label)	   12.00
    shipping (Canada -- UPS)			   25.00
    shipping (outside North America)		    ???
    wire charge (if you wire me money)		   10.00

Shipping
    If you are in the San Francisco Bay Area you can pick your
    drive up from me in San Jose, or if Dave and George are
    closer I suspect they'll let you pick it up from them.  All
    other North American orders will be shipped via UPS.

    If you are outside North America please tell me when you
    order how you would like your drive(s) shipped, I'll leave
    it up to you to send the right amount of money.  You will
    also be responsible for whatever customs or import duties
    might apply.  (This applies to Canadian orders too.)

Payment
    I need to receive payment by Wednesday, March 21st, either
    a cashier's check or wire transfer.  I'll accept a personal
    check if I receive it by Tuesday and it is drawn on a local
    (i.e. California) bank.  Checks should be made payable to

        Karl L. Swartz

    and mailed to

        pc532 Disk Buy
        c/o Karl Swartz
        1738 Deer Creek Ct.
        San Jose, California 95148

    Non-US orders may be paid (in US dollars) by wire transfer,
    international money order, or a draft payable through a US
    bank, though given the timing the wire transfer is probably
    the only method feasible.  I'll send the wire information
    to all foreign buyers in separate e-mail.  Please note that
    my bank exacts at US$10 fee on all *incoming* wire transfers
    and that any intermediary correspondent bank (Citibank is a
    likely one I'm told) may also charge a fee, so please make
    sure you send enough to fill all the pockets along the way.

    Canadian orders are probably an exception -- if you think
    the check will get here in time go ahead and use the draft
    or international money order if you like and save the wire
    charge(s).

Confirmation
    Please send me e-mail telling me how many drives you will
    be ordering, your shipping address, and how you are sending
    your payment.  I'll send you confirmation of your order and
    of your payment via e-mail as soon as I receive each.  If
    you are sending a check please include your shipping and
    e-mail address with it as well so I can put the money with
    the order.

    Plausible e-mail addresses include

        kls@ditka.uucp
        ditka!kls@daver.bungi.com

Tentative Orders
    Here's the list of people who've sent me tentative orders:

	1	kls@ditka.uucp (Karl Swartz)
	1	dlr@daver.bungi.com (Dave Rand)
	1	george@wombat.uucp (George Scolaro)
	1	rjohnson@kiwi.mpr.ca (Robbin Johnson)
	1	taylor@think.com (David Taylor)
	1(+)	johnc@manatee.uucp (John L. Connin)
	3	bdale@col.hp.com (Bdale Garbee)
	1	bdale@col.hp.com (Fred Schneider c/o Bdale Garbee)
	1	bdale@col.hp.com (Mike Westlund c/o Bdale Garbee)
	cancl.	s892024@minyos.xx.rmit.oz.au (Richard Muirden)
	1	mark-geisert@l66a.ladc.bull.com (Mark Geisert)
	1(+)	budd@bu-it.bu.edu (Phil Budne)
	2	pell@isy.liu.se (Pell Emanuelsson)
	1	buck@siswat.lonestar.org (A. Lester Buck)
	1	david@dogmelb.dog.oz.au (David Le Blanc)
	1(?)	bob@arthur.wwu.edu (Bob Hayes)
	1	bobm@convex.com (unknown)
	1	glowell@hpda.hp.com (Gary Lowell)
	1	loeliger@convex.com (Jon Loeliger)
	1	eyrie!athos@labtam.oz.au (David Burren)


I think that covers everything.  I'm looking forward to getting
everything put together ... and getting Unix running.  (Not to
be impatient Dave but will we have it by the time we get our
disks?  8-) )

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Thu Mar 15 05:54:34 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: more disk order info
To: pc532@daver.bungi.com
Date: Thu, 15 Mar 90 2:45:58 PST
Cc: ditka!pc532-disks
Reply-To: ditka!kls
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls (Karl Swartz)
Status: O

> Please count me in for one disk.

However, I still need shipping info.  Same goes for several
other orders.  If you haven't sent me shipping info please
send it to me.  If you aren't sure send it.

> Is it ok (and possible to arrange) for foreign buyers to not pay the 7% tax?

As indicated in last night's message the tax only applies
to California residents.  And for the record, the rate is
7 1/4%, the extra 1/4% having been added to pay for damage
>From the October 17th earthquake.

Several other notes ...

George mentioned that he and Dave sent many pc532s overseas
via UPS, freight collect.  I'll use this method by default
for overseas shipments.

John Connin asked if the $12 for UPS includes insurance.
I can't say for sure but I suspect not.  UPS charges $0.25
per $100.00 insurance over the basic $100 insurance, so you
may wish to include an additional $2.25 for $1000 insurance
if you're buying one disk.  Larger quantities *may* ship in
one box, so it might be wise to send $2.50 for additional
disks.  I'll see if I can get this straight tomorrow.  As
with foreign orders please let me know what you want in this
regard.

John also asked about documentation.  Like any programmer I
can't even find this word in my dictionary.  :-)  Seriously,
I don't know.  I'll check on this tomorrow as well.  I would
not really count on full SCSI documentation with every drive
but will make sure at least basic info is provided and that
full programming info is available for those who need it.
Like for Dave so he can write the Unix device driver.  Right
Dave?  8-)

Several people have mentioned problems getting e-mail to me.
My machine, ditka, is directly connected to daver, so if you
can get to the pc532 mailing list it shouldn't be *too* hard
to reach me.  Other possibilities from the Internet:

    ditka!kls@apple.com
    kls@scssun1.slac.stanford.edu

And, God forbid, from BITNET (I'm so embarrassed):

    KLS AT SLACVM

The latter two are at my office but copies are forwarded to
me at home.

Finally, I have received expressions of interest for a total
of 34 drives, with 19 confirmed and awaiting money.  Here is
the list, with a 'c' after the count on confirmed orders:

	1c	kls@ditka.uucp (Karl Swartz)
	1c	dlr@daver.bungi.com (Dave Rand)
	1c	george@wombat.uucp (George Scolaro)
	1	rjohnson@kiwi.mpr.ca (Robbin Johnson)
	1	taylor@think.com (David Taylor)
	2c	johnc@manatee.uucp (John L. Connin)
	3	bdale@col.hp.com (Bdale Garbee)
	1	bdale@col.hp.com (Fred Schneider c/o Bdale Garbee)
	1	bdale@col.hp.com (Mike Westlund c/o Bdale Garbee)
	cancel	s892024@minyos.xx.rmit.oz.au (Richard Muirden)
	1c	mark-geisert@l66a.ladc.bull.com (Mark Geisert)
	2c	budd@bu-it.bu.edu (Phil Budne)
	2	pell@isy.liu.se (Pell Emanuelsson)
	1	buck@siswat.lonestar.org (A. Lester Buck)
	1	david@dogmelb.dog.oz.au (David Le Blanc)
	1c	bob@arthur.wwu.edu (Bob Hayes)
	2c	bobm@convex.com (Bob Miller)
	1	glowell@hpda.hp.com (Gary Lowell)
	2c	loeliger@convex.com (Jon Loeliger)
	1	eyrie!athos@labtam.oz.au (David Burren)
	2c	dlr@daver.bungi.com (Morris Jones c/o Dave Rand)
	1c	night@pawl.rpi.edu (Trip Martin)
	1c	eyal@ucisae.isae.cancol.oz.au (Eyal Lebedinsky)
	2c	s861298@minyos.xx.rmit.oz.au (Marc A. Boschma)
	2	s861019@minyos.xx.rmit.oz.au (George Seremetidis)

Thanks to all of you for making this possible!

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Fri Mar 16 01:12:44 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 16 Mar 90 14:23:34+1100
From: s871943@minyos.xx.rmit.OZ.AU (Simon Burge [Snark])
To: pc532@daver.bungi.com
Subject: are TTL ACL good for replacing AS ?
Status: O

George:
	TTL AS chips are damn hard to come by in Australia, but one
guy I was talking to at a supplier said that TTL ACL should be as good
as TTL AS, with respect to propogation delay/power usage.  Any ifs, buts,
or whys on this comment?

Simon.

--
Simon Burge,                        Royal Melbourne Institute of Technology.
ACSnet:	s871943@minyos.xx.rmit.oz
CSNET:	s871943@minyos.xx.rmit.oz.au

From owner-pc532%daver@mips.com Fri Mar 16 04:14:29 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: disk buy info
To: pc532@daver.bungi.com
Date: Fri, 16 Mar 90 0:54:09 PST
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls (Karl Swartz)
Status: O

I talked to CSC again today and got answers to several questions.
First, each drive will come with complete documentation, a manual
with all the SCSI info, circuit diagrams, etc.  Also, the $12 UPS
charge does *not* include insurance, so the shipping charge in the
US should be $14.25.  If you've already sent money for the drive
just drop me a check (a personal check is fine for this) to cover
the insurance.

I've gotten a substantial amount of mail from people who've just
joined the pc532 mailing list who wonder what all this disk stuff
is about, enough that it seems justified to report the purchase
info.  If you've already read it you can safely ignore the rest
of this message.

I see you're still here, so you must want to know more about this
disk purchase.  Corporate Systems Center (aka CSC, no relation to
CDC) bought the entire stock of MiniScribe 9380S disk drives after
MiniScribed filed for bankruptcy.  They have advertised them for
$1,095 each, but by putting together a large order we are getting
them for only $895 each.  Any MiniScribe warranty would probably
be worthless, but CSC is offering a one-year warranty which will
be honored directly by CSC -- you won't have to go thru me if you
buy a disk through the pc532 disk buy and have problems with it.

Here's a complete rundown of the specs from CSC's brochure:

    Drive:			MiniScribe 9380S
    Capacity (unformatted):	380MB
    Capacity (formatted):	335MB
    Average access:		16ms
    Track-to-track seek:	5ms
    SCSI transfer rate:		4MB/sec
    MTBF:			100,000 POH
    Dimensions:			5 1/4" full height

I'm planning on picking the drives up next Thursday (March 22)
so I need to have money from you by Wednesday, March 21st.  The
total cost per drive is as follows:

    MiniScribe 9380S 335MB 16ms			$ 895.00
    handling (bank, paperwork, etc.)		    2.50
						--------
						$ 897.50

plus:

    sales tax (California residents only)	   64.89
    shipping (United States -- UPS Blue Label)	   12.00
        plus insurance				    2.25
    shipping (Canada -- UPS)			   25.00
    shipping (outside North America)		    ???
    wire charge (if you wire me money)		   10.00

Shipping
    If you are in the San Francisco Bay Area you can pick your
    drive up from me in San Jose, or if Dave and George are
    closer I suspect they'll let you pick it up from them.  All
    other North American orders will be shipped via UPS.

    If you are outside North America please tell me when you
    order how you would like your drive(s) shipped, I'll leave
    it up to you to send the right amount of money.  You will
    also be responsible for whatever customs or import duties
    might apply.  (This applies to Canadian orders too.)  If
    you prefer I can have the drive(s) shipped UPS freight
    collect; Dave and George used this for some of the pc532
    kits and it worked out well for them.

Payment
    I need to receive payment by Wednesday, March 21st, either
    a cashier's check or wire transfer.  I'll accept a personal
    check if I receive it by Tuesday and it is drawn on a local
    (i.e. California) bank.  Checks should be made payable to

        Karl L. Swartz

    and mailed to

        pc532 Disk Buy
        c/o Karl Swartz
        1738 Deer Creek Ct.
        San Jose, California 95148

    Non-US orders may be paid (in US dollars) by wire transfer,
    international money order, or a draft payable through a US
    bank, though given the timing the wire transfer is probably
    the only method feasible.  I'll send the wire information
    to all foreign buyers in separate e-mail.  Please note that
    my bank exacts a US$10 fee on all *incoming* wire transfers
    and that any intermediary correspondent bank (Citibank is a
    likely one I'm told) may also charge a fee, so please make
    sure you send enough to fill all the pockets along the way.

    Canadian orders are probably an exception -- if you think
    the check will get here in time go ahead and use the draft
    or international money order if you like and save the wire
    charge(s).

Confirmation
    Please send me e-mail telling me how many drives you will
    be ordering, your shipping address, and how you are sending
    your payment.  I'll send you confirmation of your order and
    of your payment via e-mail as soon as I receive each.  If
    you are sending a check please include your shipping and
    e-mail address with it as well so I can put the money with
    the order.

    Plausible e-mail addresses include

        kls@ditka.uucp
        ditka!kls@daver.bungi.com
        ditka!kls@apple.com
        kls@scssun1.slac.stanford.edu
        KLS AT SLACVM (BITNET)

    I'd prefer *not* to receive pc532 related mail at SLAC and
    especially not via BITNET, so please try to reach me at ditka
    before resorting to one of the last two addresses.

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Fri Mar 16 15:51:32 1990
Flags: 000000000401
Reply-To: pc532@daver.bungi.com
Date: Fri, 16 Mar 90 11:53:40 PST
X-Mailer: Mail User's Shell (6.5 4/17/89)
From: gs@vw25.chips.com (George Scolaro)
To: pc532@daver.bungi.com
Subject: Re: Disk drive power requirements
Status: O

[In the message entitled "Disk drive power requirements" on Mar 16,  8:45, Jon Loeliger writes:]
> 
> I'm actively looking for a box and power supplies now, and
> I'd like to account for the disk drives if possible.  Can
> someone tell me what the power requirements for 1 drive
> will be?  I actually plan on placing two on the machine,
> so other than doing 2*Amps, is there a gotcha this software
> weenie might miss?

Since the pc532 was designed to fit into an AT case, I assume that you will
do this and power it from an AT powersupply. If this is the case then you
don't have a problem, AT supplies start at 200 Watts and go up...
The pc532 draws less than 3A from 5 volts, and negligible power from the +/-
12 (just enough for the CMOS RS232 transceivers). An average disk drive will
draw 1-2A at 5V and 2-3A at +12V. The AT supply will supply 20A or so at 5V
and 10A or so at +12V.

> Also, I am planning on building up a second board that isn't in
> kit form and I am having a small problem finding some PGA sockets
> in the, uh, large size.  Can someone tell me a source for the
> 175 pin PGA socket for the 532?

McKenzie manufactures such a beast. I bought the ones for the pc532 kits
>From one of their reps in Santa Clara. They cost around $10 each (depending
on quantity). The part number is PGA175M 1618, this is the exact part # as
per the ones shipped with the pc532 kit. McKenzie is at 415-651-2700 or fax
# 415-651-1020.

regards,

-- 
George Scolaro
(try (pyramid|hoptoad|sun|vsi1)daver!vw25.chips.com!gs)

From zygot!ditka!kls@apple.com Thu Mar 15 05:31:01 1990
Flags: 000000000000
Subject: Re:  MiniScribe disk buy -- the fine print!
To: budd@bu-it.bu.edu (Phil Budne)
Date: Thu, 15 Mar 90 1:14:29 PST
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls@apple.com (Karl Swartz)
Status: O

> At the 897.50 price I'll go for 2 (I had been a 1+).

Great!

> Is the correct ammount 1819.00 (2 * (897.50 + 12.00))?

I'm not sure the $12 shipping includes insurance; John Connin
checked and found that insurace for $900 runs an extra $2.25
so you may wish to add $4.50 for that.  I'll check on this in
the morning.  Otherwise, $1819 is the right amount.

 -- Karl

From ames!zorch!ditka!kls@XN.LL.MIT.EDU Thu Mar 15 07:11:57 1990
Flags: 000000000000
Posted-Date: Thu, 15 Mar 90 2:45:58 PST
Subject: more disk order info
To: pc532@daver.bungi.com
Date: Thu, 15 Mar 90 2:45:58 PST
Cc: ditka!pc532-disks
Reply-To: ames!ditka.uucp!kls@XN.LL.MIT.EDU
X-Mailer: ELM [version 2.2t PL7]
From: ames!ditka.UUCP!kls@XN.LL.MIT.EDU (Karl Swartz)
Status: O

> Please count me in for one disk.

However, I still need shipping info.  Same goes for several
other orders.  If you haven't sent me shipping info please
send it to me.  If you aren't sure send it.

> Is it ok (and possible to arrange) for foreign buyers to not pay the 7% tax?

As indicated in last night's message the tax only applies
to California residents.  And for the record, the rate is
7 1/4%, the extra 1/4% having been added to pay for damage
>From the October 17th earthquake.

Several other notes ...

George mentioned that he and Dave sent many pc532s overseas
via UPS, freight collect.  I'll use this method by default
for overseas shipments.

John Connin asked if the $12 for UPS includes insurance.
I can't say for sure but I suspect not.  UPS charges $0.25
per $100.00 insurance over the basic $100 insurance, so you
may wish to include an additional $2.25 for $1000 insurance
if you're buying one disk.  Larger quantities *may* ship in
one box, so it might be wise to send $2.50 for additional
disks.  I'll see if I can get this straight tomorrow.  As
with foreign orders please let me know what you want in this
regard.

John also asked about documentation.  Like any programmer I
can't even find this word in my dictionary.  :-)  Seriously,
I don't know.  I'll check on this tomorrow as well.  I would
not really count on full SCSI documentation with every drive
but will make sure at least basic info is provided and that
full programming info is available for those who need it.
Like for Dave so he can write the Unix device driver.  Right
Dave?  8-)

Several people have mentioned problems getting e-mail to me.
My machine, ditka, is directly connected to daver, so if you
can get to the pc532 mailing list it shouldn't be *too* hard
to reach me.  Other possibilities from the Internet:

    ditka!kls@apple.com
    kls@scssun1.slac.stanford.edu

And, God forbid, from BITNET (I'm so embarrassed):

    KLS AT SLACVM

The latter two are at my office but copies are forwarded to
me at home.

Finally, I have received expressions of interest for a total
of 34 drives, with 19 confirmed and awaiting money.  Here is
the list, with a 'c' after the count on confirmed orders:

	1c	kls@ditka.uucp (Karl Swartz)
	1c	dlr@daver.bungi.com (Dave Rand)
	1c	george@wombat.uucp (George Scolaro)
	1	rjohnson@kiwi.mpr.ca (Robbin Johnson)
	1	taylor@think.com (David Taylor)
	2c	johnc@manatee.uucp (John L. Connin)
	3	bdale@col.hp.com (Bdale Garbee)
	1	bdale@col.hp.com (Fred Schneider c/o Bdale Garbee)
	1	bdale@col.hp.com (Mike Westlund c/o Bdale Garbee)
	cancel	s892024@minyos.xx.rmit.oz.au (Richard Muirden)
	1c	mark-geisert@l66a.ladc.bull.com (Mark Geisert)
	2c	budd@bu-it.bu.edu (Phil Budne)
	2	pell@isy.liu.se (Pell Emanuelsson)
	1	buck@siswat.lonestar.org (A. Lester Buck)
	1	david@dogmelb.dog.oz.au (David Le Blanc)
	1c	bob@arthur.wwu.edu (Bob Hayes)
	2c	bobm@convex.com (Bob Miller)
	1	glowell@hpda.hp.com (Gary Lowell)
	2c	loeliger@convex.com (Jon Loeliger)
	1	eyrie!athos@labtam.oz.au (David Burren)
	2c	dlr@daver.bungi.com (Morris Jones c/o Dave Rand)
	1c	night@pawl.rpi.edu (Trip Martin)
	1c	eyal@ucisae.isae.cancol.oz.au (Eyal Lebedinsky)
	2c	s861298@minyos.xx.rmit.oz.au (Marc A. Boschma)
	2	s861019@minyos.xx.rmit.oz.au (George Seremetidis)

Thanks to all of you for making this possible!

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From ames!zorch!ditka!kls@XN.LL.MIT.EDU Sat Mar 17 01:44:42 1990
Flags: 000000000001
Posted-Date: Fri, 16 Mar 90 21:47:32 PST
Subject: MiniScribe 9380S specs
To: pc532@daver.bungi.com, ditka!pc532-disks
Date: Fri, 16 Mar 90 21:47:32 PST
X-Mailer: ELM [version 2.2t PL7]
From: ames!ditka.UUCP!kls@XN.LL.MIT.EDU (Karl Swartz)
Status: O

George and I picked up one disk today so Dave could play with it
over the weekend.  I was driving while George looked things over
but it appeared that the manual was reasonably complete, several
dozen pages of material with all the SCSI programming info and
the like.

We also picked up a couple of copies of MiniScribe's brochure on
the drive with all sorts of specs.  Here's the rundown for those
of you with enquiring minds:

    Capacity Unformatted
	Per Drive (MBytes)		382
	Per Track (Bytes)		20,832

    Typical Capacity Formatted (SCSI)
	Per Drive (MBytes)		347
	Sector Size (Bytes)		1,024
	Sectors/Track			19
	Number of Cylinders		1,224

    Functional
	Disks				8
	Recording Heads			15
	Total Cylinders			1,224
	Data Tracks			18,316
	Track Density (tpi)		1,100
	Recording Density (bpi)		20,388
	Data Encoding Method		2,7 RLL
	Rotational Speed (RPM)		3,600

    Data Transfer Rate
	(Mbits per second)		10

    Access Time (including settling)
	Average (msec.) *		16
	Track-to-track (msec.)		3.8
	Maximum (msec.)			35
	Latency (average, msec.)	8.33

	* Average of all possible seeks.

    Reliability
	MTBF				30,000 Hours
	PM				None
	MTTR				30 minutes
	Component Design Life		5 years

    Error Rates
	Soft Read Errors		1 per 10^10 bits/read
	Hard Read Errors		1 per 10^12 bits/read
	Seek Errors			1 per 10^6 seeks

    DC Power Requirements
	+ 5 VDC +/- 5%			.6 amps typical
	+12 VDC +/- 5%			1.2 amps typical
					2.7 amps peak
	Max. Starting (3 sec.)		5.0 amps

    Power Dissipation
	Idle				18 watts typical
	Seeking				22 watts typical

    Environmental Limits
	Ambient Temperature
	    Operating			10F to 122F
					(10C to 50C)
	    Non-operating		-40F to 140F
					(-40C to 60C)
	    Thermal Gradient		18F/hour
					(10C/hour) max.
	Relative Humidity		8% to 80%
					(non condensing)
	Maximum Wet Bulb		78F (26C)

    Accoustic Noise
	Idle mode			43 dBa sound pressure level
	Seeking mode			50 dBa sound pressure level

    Physical
	Height				3.25 in (82.6 mm)
	Width				5.75 in (146 mm)
	Depth				8.0 in (203 mm)
	Weight				6.0 lbs (2.7 kg)

There was also some question regarding export restrictions on
multiple drives.  Apparently there is a bit of extra paperwork
for overseas shipments involving more than one drive but nothing
else.

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Sat Mar 17 03:35:54 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Fri, 16 Mar 90 23:18:29 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: MiniScribe 9380S specs
Status: O

[In the message entitled "MiniScribe 9380S specs" on Mar 16, 21:47, Karl Swartz writes:]
> George and I picked up one disk today so Dave could play with it
> over the weekend.  I was driving while George looked things over
> but it appeared that the manual was reasonably complete, several
> dozen pages of material with all the SCSI programming info and
> the like.

Small edit required...

...
but it appeared that the manual was reasonably INCOMPLETE, several
dozen pages of material with NONE of the SCSI programming info and
the like.
...

On the positive side, we hooked it up the the pc532, and I was able
to select it, and transfer data. I have had it on the ICM since
about 2000 PST, with everything going well. Formatted fine, and data
transfer is fast. Too fast for the ICM, BTW - it tops out at 500K/sec.

Drive seems to be happy - I'm moving George's news partition onto it
now, and I'll let it run overnight. It does not get hot, nor is it
objectionably noisy (like Maxtor drives). I like it! (Is it too late
to get another one or two?) Can't beat it for the price...


-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From owner-pc532%daver@mips.com Sat Mar 17 03:37:50 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: Re: Disk drive power requirements
To: pc532%tarpit@daver.bungi.com
Date: Fri, 16 Mar 90 21:39:12 EST
From: John L. Connin <johnc%manatee@uunet.UU.NET>
X-Mailer: Elm [version 2.1 PL1]
Status: O


>[In the message entitled "Disk drive power requirements" on Mar 16,  8:45, Jon Loeliger writes:]
>> 
>> I'm actively looking for a box and power supplies now, and
>> I'd like to account for the disk drives if possible.  Can
>> someone tell me what the power requirements for 1 drive
>> will be?  I actually plan on placing two on the machine,
>> so other than doing 2*Amps, is there a gotcha this software
>> weenie might miss?

[ George responds ]

>Since the pc532 was designed to fit into an AT case, I assume that you will
>do this and power it from an AT powersupply. If this is the case then you
>don't have a problem, AT supplies start at 200 Watts and go up...
>The pc532 draws less than 3A from 5 volts, and negligible power from the +/-
>12 (just enough for the CMOS RS232 transceivers). An average disk drive will
>draw 1-2A at 5V and 2-3A at +12V. The AT supply will supply 20A or so at 5V
>and 10A or so at +12V.

One nice feature of SCSI drives in general is the ability to sequence
power-up (ie. disk and head motors).  For examples Maxtor drives provide
jumper  options for:

   a) power-up upon application of power
   b) power-up after delay proportional to SCSI id.
   c) power-up/down upon receipt of SCSI command.

Obviously, this permits staging of surges or placing infrequently used
drives in a quiscent state.
 
Best regards,
johnc



From owner-pc532%daver@mips.com Sat Mar 17 03:37:59 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
From: Dave Mason <mason%tmsoft%uunet@daver>
Subject: Re: Disk drive power requirements
Organization: TM Software Associates Inc.
Date: 16 Mar 90 19:24:02 EST (Fri)
Status: O

In message <m0h9NMi-0000nFC@vw25.chips.com> on Fri, 16 Mar 90 11:53:40 PST.
George Scolaro <daver!vw25.chips.com!gs> wrote:

> [In the message entitled "Disk drive power requirements" on Mar 16,  8:45, Jon Loeliger writes:]
> > 
> > will be?  I actually plan on placing two on the machine,
> > so other than doing 2*Amps, is there a gotcha this software
> > weenie might miss?
> 
> The pc532 draws less than 3A from 5 volts, and negligible power from the +/-

Is that with full 32MB memory? or what?

> An average disk drive will
> draw 1-2A at 5V and 2-3A at +12V. The AT supply will supply 20A or so at 5V
> and 10A or so at +12V.

Note that "power-on" (while the disk is spinning up) power
requirements can be almost triple normal.  It's fairly common for
high-performance to draw 4.5 amps (on the +12V line) at power-on
(versus 1.57 typical), so you may need most of that 10A for 2 disks,
unless you sequence the power to them.  (Which is to say, a floppy or
tape drive COULD push it past the limits.)

When I was first building my power supply for my ICM3216, I had a 5A
12V regulator.  When I plugged it in (with one Priam V185 disk) it
would make some interesting noises that I can't duplicate in print,
but would basically accelerate for about 10 seconds, then spin down,
wait a couple of seconds and repeat...  The voltage was falling off as
the current draw exceeded 5A and the disk was getting unhappy with the
lousy power & resetting.  I replaced the regulator with a 10A 12V & it
worked fine.  (tmsoft currently runs off an ex-PDP11 power supply
rated 35A at 5V and 20A at +/- 12! (with 2 levels of transient
supression, connected to a UPS... you CAN'T have too good power!))

	../Dave

From owner-pc532%daver@mips.com Sat Mar 17 04:25:56 1990
Flags: 000000000001
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Sat, 17 Mar 90 00:56:47 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: Disk drive power requirements
Status: O

[In the message entitled "Re: Disk drive power requirements" on Mar 16, 16:30, Neal A Sedell writes:]
> Well, now we (new subscribers) have the low-down on the disks, what's the
> deal on the '532 board and any options????

The pc532 second run will be started at the end of the month. We are
currently offering only PCB's - parts & sockets will not be available
>From us. The price will be $200 USD, plus shipping. There are no cuts/jumps
required on the current revision of the PCB.

If you are interested, please mail your request to:

pc-order@daver.bungi.com -or- {sun|mips|pyramid|vsi1|uunet}!daver!pc-order

*PLEASE*! Include your Name, *ADDRESS*, telephone number, and
quantity desired. Also, please include your address. And, if it
is not too much trouble, your address. That is, please include the
address you would like the board shipped to.

(too many people didn't include their address on the last go-around)

We will probably do the ET-532 board (the first planned add-in card for
the SCSI bus of the PC532) at the same time. We will only do a small
quantity of these boards (perhaps 10 or so) so we can fully test them before
we do a larger run.

If anyone needs further details, please mail directly to me and/or George.
George is at george@wombat.bungi.com or george@bungi.com.


-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From owner-pc532%daver@mips.com Sat Mar 17 04:50:03 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: memory configuration
To: pc532@bungi.com
Date: Sat, 17 Mar 90 0:37:20 PST
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls (Karl Swartz)
Status: O

I finally got the board all soldered up this afternoon.  Took
about 20 minutes, thanks to a housemate who does hardware and
who got his wave soldering friends (Arxe in Milpitas, Calif.)
to do it as a favor.  Looks nice!

Naturally the first thing I did when I got home was sit down
with all the ICs and plug 'em in.  There are just three empty
sockets left waiting for the '1034 chips (hurry up Trip!) and
an unused SCSI disk connector (hurry up *me*!) ... and slots
for the SIMMs.

I bought four 1Mx9 SIMMs through Benjamin Pan, but I'm not at
all sure which sockets they go in.  Looking at the diagrams I
*think* they should be in U6, U8, U10, and U12, but I trust
my hardware expertise even less than Alex's.  Being a Golden
Retriever his primary hardware knowledge involves shedding or
chewing on it -- not terribly helpful in this case.

Even if I did get that right, J1 and J2 have me baffled.  Any
illumination for the hardware ignorant, George?

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Sun Mar 18 00:17:35 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Sat, 17 Mar 90 21:05:19 mst
From: Bdale Garbee <bdale@col.hp.com>
To: pc532@daver.bungi.com
Subject: my board is up!
Status: O

I got things plugged in and turned on this morning.  Nothing happened.  Turns
out the first thing I checked was the output of the 50Mhz oscillator, and sure
enough the one I'd scraped out of my piles of junk wasn't oscillating.  Put
in a 40.337 that happened to be handy, and voila!  Sure was nice having an
EPROM that at least gave me a banner when it turned on.

Looks to me like some overshoot is still on the clock lines with 330/220
terminating resistors, will look at that more tomorrow... 

For the curious, I used 74F174's instead of 74AS174's, and 74F280's instead of
74AS280's.  Looked to me like they're about equivalent timing specs.  George?
Makes me feel ok about running at a bit over 20Mhz instead of 25 for the
duration.

Fred is bringing his board down tomorrow, and we'll try to get his going too.
He has all the sockets soldered, but none of the bypass caps, etc... we should
be able to get it done!

Does anyone have a spare ICU?  We didn't get in on the full kits, and I only
have one 10Mhz part handy... will order one this week, I guess.

Bdale

From owner-pc532%daver@mips.com Sun Mar 18 00:29:45 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
X-Mailer: Mail User's Shell (6.2 5/11/88)
To: pc532@daver.bungi.com
Subject: Re: Disk drive power requirements
Date: 17 Mar 90 21:08:33 PST (Sat)
From: george@wombat.bungi.COM (George Scolaro)
Status: O

[In the message entitled "Re: Disk drive power requirements" on Mar 16, 19:24, Dave Mason writes:]
> > The pc532 draws less than 3A from 5 volts, and negligible power from the +/-
> 
> Is that with full 32MB memory? or what?

It's actually around 2.5A with 4 SIMMs in place. Since the only time all 8
SIMMs can be active is during refresh, 3A or less would be very typical of a
full memory complement. Of course it also depends on whether you pc532 has
the CMOS or NMOS duarts.  1Mbyte SIMMs will be much the same as 4Mbyte SIMMs.
Scaling the size has typically scaled (down) the power consumption.

> Note that "power-on" (while the disk is spinning up) power
> requirements can be almost triple normal.  It's fairly common for
> high-performance to draw 4.5 amps (on the +12V line) at power-on

True, you definitely need the initial surge capability. The high current
draw usually last a few seconds, but many supplies will shutdown during the
high current phase.

regards,

-- 
George Scolaro
george@wombat.bungi.com                [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Sun Mar 18 00:54:28 1990
Flags: 000000000001
Reply-To: pc532@daver.bungi.com
X-Mailer: Mail User's Shell (6.2 5/11/88)
To: pc532@daver.bungi.com
Subject: Re: memory configuration
Date: 17 Mar 90 21:28:05 PST (Sat)
From: george@wombat.bungi.COM (George Scolaro)
Status: O

[In the message entitled "memory configuration" on Mar 17,  0:37, Karl Swartz writes:]
> 
> I bought four 1Mx9 SIMMs through Benjamin Pan, but I'm not at
> all sure which sockets they go in.  Looking at the diagrams I
> *think* they should be in U6, U8, U10, and U12, but I trust
> my hardware expertise even less than Alex's.  Being a Golden

Yep, those are the ones for the first bank. Remember again to make sure that
the edges (i.e. the ends near the socket clips) are clean and smooth. I used
an exacto knife to clean the edge down. Also, you'll find that SIMMs wont
appear to want to go in. Just be careful while 'jiggling' and you'll get
them in.

---------------------------------------------------------------------------

> Even if I did get that right, J1 and J2 have me baffled.  Any
> illumination for the hardware ignorant, George?

J1 and J2 select the DRAM size. For the 1Mbyte modules you need to jumper
2-3 on J1 and J2. For the 4Mbyte modules (for the really rich) you jump 1-2
on J1 and J2.

---------------------------------------------------------------------------

By the way, the MiniScribe drive works very nicely, its actually accessing
right now as I type. You can tell a fast seeking drive by the particular
cute rattling sounds that it makes while seeking. Also, for those that are
worried about loading down an AT powersupply when dozens (sure!) of these
drives are powering up, the MiniScribe does support power up/down sequencing
via a SCSI command.

Now all we have to find is a nice cheap source of high capacity SCSI mag
tape drives for backup.... Maybe CSC has some.

regards,

-- 
George Scolaro
george@wombat.bungi.com                [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Sun Mar 18 01:14:38 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
X-Mailer: Mail User's Shell (6.2 5/11/88)
To: pc532@daver.bungi.com
Subject: Re: my board is up!
Date: 17 Mar 90 21:56:12 PST (Sat)
From: george@wombat.bungi.COM (George Scolaro)
Status: O

[In the message entitled "my board is up!" on Mar 17, 21:05, Bdale Garbee writes:]
> 
> in a 40.337 that happened to be handy, and voila!  Sure was nice having an
> EPROM that at least gave me a banner when it turned on.

Good to hear that another one is up and running.
 
> Looks to me like some overshoot is still on the clock lines with 330/220
> terminating resistors, will look at that more tomorrow... 

Thats 220 ohms to +5, 330 to ground right? Also I assume that you are using
a 400mhz or better scope with no ground wire. I measured the clocks by using
a 400mhz tektronix scope with the short 'Z' ground probe. i.e. the ground
probe connects to the probe tip directly to give a very short connection. I
probed by touching the tip of the scope directly to the resistor end, and the
ground 'Z' directly to the other side of the resistor (the ground). If you use
the ground lead from the scope probe with the alligator clip etc, then most
of the overshoot etc will be due to ground connection. The clocks on my board
looked very clean, remember a bit of overshoot and undershoot will still be
within the spec of the input devices (as long as it isn't -1V or +2V etc).

> For the curious, I used 74F174's instead of 74AS174's, and 74F280's instead of
> 74AS280's.  Looked to me like they're about equivalent timing specs.  George?

The 74F280 is fine, it is actually a bit faster (hence better) than the
74AS280. I too have used the 74F280 on one of our boards. The 74F174 is 1ns
slower (worst case) than the 74AS174. Again, the board was designed worst
case in all directions, in reality it will work just fine (since the worst
case figures are over temperature and voltage). I have looked at many of the
signals (such as through the DRAM drivers) and some of the flip flops and
PALs and even after heating and freezing (while running) the signals were all
many nseconds better than worst case. Of course the idea of doing worst case
design in the first place is to ensure that a product is capable of being
manufactured using components from a variety of vendors with different
batches (i.e. Friday chips...).

> Makes me feel ok about running at a bit over 20Mhz instead of 25 for the
> duration.

If it makes you happier. Of course you could run the board at 49.9Mhz :-)

best regards,

-- 
George Scolaro
george@wombat.bungi.com                [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Sun Mar 18 08:33:20 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: athos%eyrie@labtam.oz.au
To: pc532list@munnari.oz.au
Subject: SCSI
Date: Sun Mar 18 22:47:38 1990
Status: O

In L. Brett Glass's SCSI articles in Byte the following text appears:

	The X3T9.2 committee working documents, CAM committee documents,
	and the most current draft of the SCSI-2 specification are
	available for downloading from the SCSI BBS at (316) 636-8700
	(300, 1200, or 2400 bps; 24 hours).

Someone mentioned this a while back in the mailing list also.  That BBS being
on almost the other side of the globe to me, I'm not keen to increase my phone
bill THAT much...

Are these files available anywhere for anonymous ftp?  And if not, can some
kind soul out there provide them?  Many thanks in advance.

Oh, and please ignore my previous posting about spare pins on the AIC-6250
SCSI chip.  Since then I've read the documentation....
___________________________________________________________________________
David Burren (Athos),			ACSnet: athos%eyrie@labtam.oz.au
img Consultants,
G.P.O. Box 3304GG, Melbourne,		- DON'T TRUST THE MAIL HEADER -
Australia 3001


From owner-pc532%daver@mips.com Sun Mar 18 10:57:20 1990
Flags: 000000000001
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Re: SCSI
Date: Sun, 18 Mar 90 09:25:19 EST
From: Trip Martin <night@pawl.rpi.edu>
Status: O

Most of the files on the SCSI BBS are also available from the archive
server on mgse.uucp.  Since this an item of general interest, I'm 
including the files needed to get started.  There is one annoying thing
about the files: they assume everyone has an IBM PC.  The text files are
in Wordstar format (or in a few cases, Lotus 1-2-3), and collections are
either zipped or arc'ed.

I've already gotten a few of the files (mainly the SCSI-1 and SCSI-2
drafts), and at some point, I'm planning to convert them to nroff 
format.  It would be nice if we could set up an archive site for Unix
versions of these documents.  I'm willing to help out with converting
the files (my site has arc, and I've gotten hold of a unix unzipper).  
Anyone else interested in such a project?  
--
Trip Martin
night@pawl.rpi.edu
night@uruguay.acm.rpi.edu
============================== Cut here ============================
Return-Path: archived@mgse
Return-Path: <archived@mgse>
Received: from rex.cs.tulane.edu by pawl.rpi.edu (4.1/HUB10);
	id AA04985; Thu, 15 Feb 90 04:57:31 EST for night
From: <archived@mgse>
Received:  by rex.cs.tulane.edu; Thu, 15 Feb 90 03:59:36 -0600
Message-Id: <9002150959.AA15994@rex.cs.tulane.edu>
To: night@pawl.rpi.edu
Subject: archive request help 
Date: Wed Feb 14 23:14:25 1990

	This is the mgse archive server help file.  This file is
sent because you sent a line to the archive server requesting help.

	The archive server knows several commands, they are TEST,
SET, SEND, HELP, INDEX, LIST, NEW, and PATH. The archive software
is new and new commands will be added in. You may want to get the
help message once in a while to see what is new in the way of commands.

	The TEST command just sends a reply back to you, i added
this command so people could find a good address to the system, as
well as finding the time required for the message to travel a
certain path.

	The SET command takes one option, they are CBITS16, CBITS12,
COMPRESS, PACK, UUENCODE, and BTOA. CBITS12 and CBITS16 cause
compress to use either 12 or 16 bit compression 16 bit is the
default.  COMPRESS and PACK specify the type of file compression
you want, they both default to "no". The BTOA and UUENCODE options
set what type of conversion a binary (or ascii) file undergoes
before it is sent out. The also defaults to "no". You must SET
UUENCODE or SET BTOA if you set COMPRESS OR PACK, or want to receive
a binary file.

	The SEND command is used to send an individual file. The
SEND command takes a single argument, the name of the file to send.
This system has a 14 character length limit on file names, so you
must use slashes instead of dots when specifiing the news group
name. For instance to get a file from comp.sources.games, use
comp/sources/games instead of comp.sources.games. The file names
you specify will be first checked to see if they can be found, it
they can not, then the compressed file name is tried. In this manner
you do not have to add the ".Z" extension of a file is compressed,
The software will find it, and send the uncompressed file to you.

	The HELP command is the command you use to send the file
you are looking at right now.

	The INDEX command will send back a complete index of the
files available to the archive server. This index contains the
descriptions of the files, as well as the sizes of each ones.  For
new postings with more than one part, you can see what parts are
available, as well as what I have.

	The LIST command will send back a complete listing of files
available from the archive server. The index is your typical Un*x
ls-lR listing. The listing may contain files that are not included
in the index file that is availabe with the INDEX command.

	The NEW command sends back a text file that describes any
changes in the archive or archive server software if there are any,
otherwise a short message is sent saying there is nothing new.F

	The PATH will allow you to override the From line and allow
you to send archive requests back via a particular route, pleawse
use this command to avoid ginosko or to force the archive software
to take the fastest/cheapest route.

	File requests are queued up, and sent at set times. If you
are a few hops away, don't be upset if you don't receive the files
right away.

	I just started writing this server earlier this week, so
far the INDEX and LIST commands will only get you the master index
and list files, these files are 258K and 320K respectively.  Until
I fix the software to allow the requester to get a specific index,
you may want to use the SEND command and get the index and lists
>From the differant net areas.

Currently the following group news groups are archived;

Newsgroup                                       Directory
--------------------------------------------------------------------------
alt.sources                                     alt/sources/
comp.binaries.amiga                             comp/binaries/amiga/
comp.binaries.atari.st                          comp/binaries/atari.st/
comp.binaries.ibm.pc                            comp/binaries/ibm/pc/
comp.binaries.mac                               comp/binaries/mac/
comp.sources.amiga                              comp/sources/amiga/
comp.sources.atari.st                           comp/sources/atari/st/
comp.sources.games                              comp/sources/games/
comp.sources.mac                                comp/sources/mac
comp.sources.misc                               comp/sources/misc
comp.sources.sun                                comp/sources/sun
comp.sources.unix                               comp/sources/unix
comp.sources.x                                  comp/sources/x/

	So to get the index for comp.sources.unix, you want file
comp/sources/unix/index.

	These archives are by no means complete, there are a number
of usenet postings I have missed and not been able to find at
archive sites. If you have something that I am missing please send
it to either user 'root' or user 'marks'. If you have something
you would like me to add to the archives and make available to
other users, please send me a note.

	A quick note, i have been watching requests come in, there
is no need to send a index and a help command in seperate messages,
any number of commands can be in the same message. The archive
server is not case sensitive for the  commands, just the file names,
sending a message with the commands "TEST" and "test" will get you
two test messages back. There was a bug in the software that would
allow one server request to be processed several times, this caused
some bad feelings from "ginosko.samsung.com", until this is resolved,
please don't route anything thru ginosko at all. I have not talked
to ginosko about it, they felt it was more important to talk to my
feed site about it than me (to get him to drop the connection with
me?) I am working on changes to let the archive software reject
anything that will go thru certain sites to keep these system
administrators off of my back. When that happens stuff that goes
thru uunet to ginosko to rex will not be sent, i can't think of
any other way to do it.

When you request files, the file list or file index, please use
the compress/pack and uuencode/btoa SET commands if you can, it
will make can only help to get the file to you faster as well as
decrease the cost of sending it.

Last update:
Thu Sep 14 02:41:22 CDT 1989

Return-Path: archived@mgse
Return-Path: <archived@mgse>
Received: from rex.cs.tulane.edu by pawl.rpi.edu (4.1/HUB10);
	id AA04990; Thu, 15 Feb 90 04:57:57 EST for night
From: <archived@mgse>
Received:  by rex.cs.tulane.edu; Thu, 15 Feb 90 03:59:59 -0600
Message-Id: <9002150959.AA15995@rex.cs.tulane.edu>
To: night@pawl.rpi.edu
Subject: /archive/other/scsi-bbs/list
Date: Wed Feb 14 23:14:44 1990


----------------------------------- cut here -----------------------------------

area01:
total 1178
-rw-r--r--   2 news     news        1471 Jan 25 05:41 !note
-rw-r--r--   2 news     news        7487 Jan 25 05:41 87-029r1.txt.Z
-rw-r--r--   2 news     news       12927 Jan 25 05:41 87-071r0.brf.Z
-rw-r--r--   2 news     news        8385 Jan 25 05:41 87-080r0.txt.Z
-rw-r--r--   2 news     news       15774 Jan 25 05:41 87-090r0.brf.Z
-rw-r--r--   2 news     news        8853 Jan 25 05:42 87-107r0.txt.Z
-rw-r--r--   2 news     news       12696 Jan 25 05:42 87-135r1.brf.Z
-rw-r--r--   2 news     news       11365 Jan 25 05:42 87-153r1.txt.Z
-rw-r--r--   2 news     news       17494 Jan 25 05:42 87-171r0.brf.Z
-rw-r--r--   2 news     news       10426 Jan 25 05:42 87-185r0.txt.Z
-rw-r--r--   2 news     news       14759 Jan 25 05:42 87-200r2.brf.Z
-rw-r--r--   2 news     news        6750 Jan 25 05:42 88-011r0.txt.Z
-rw-r--r--   2 news     news       15728 Jan 25 05:43 88-020r1.brf.Z
-rw-r--r--   2 news     news        8759 Jan 25 05:43 88-031r0.txt.Z
-rw-r--r--   2 news     news       15671 Jan 25 05:43 88-040r1.brf.Z
-rw-r--r--   2 news     news        9542 Jan 25 05:43 88-050r0.txt.Z
-rw-r--r--   2 news     news       18269 Jan 25 05:43 88-066r0.brf.Z
-rw-r--r--   2 news     news       12738 Jan 25 05:43 88-072r0.txt.Z
-rw-r--r--   2 news     news       18668 Jan 25 05:43 88-096r0.brf.Z
-rw-r--r--   2 news     news       10813 Jan 25 05:44 88-109r2.txt.Z
-rw-r--r--   2 news     news       18458 Jan 25 05:44 88-130r2.brf.Z
-rw-r--r--   2 news     news        9415 Jan 25 05:44 88-153r0.txt.Z
-rw-r--r--   2 news     news         936 Jan 25 05:44 88-155r0.txt.Z
-rw-r--r--   2 news     news       16337 Jan 25 05:44 88-164r0.brf.Z
-rw-r--r--   2 news     news        7041 Jan 25 05:44 89-019r1.txt.Z
-rw-r--r--   2 news     news       22956 Jan 25 05:45 89-028r1.brf.Z
-rw-r--r--   2 news     news        1351 Jan 25 05:45 89-041r0.txt.Z
-rw-r--r--   2 news     news        4675 Jan 25 05:45 89-042r0.txt.Z
-rw-r--r--   2 news     news       16635 Jan 25 05:45 89-049r0.brf.Z
-rw-r--r--   2 news     news       11364 Jan 25 05:45 89-066r1.txt.Z
-rw-r--r--   2 news     news       20522 Jan 25 05:45 89-075r0.brf.Z
-rw-r--r--   2 news     news        9651 Jan 25 05:45 89-090r0.txt.Z
-rw-r--r--   2 news     news       19207 Jan 25 05:46 89-111r0.brf.Z
-rw-r--r--   2 news     news        9183 Jan 25 05:46 89-120r0.txt.Z
-rw-r--r--   2 news     news       19596 Jan 25 05:46 89-126r0.brf.Z
-rw-r--r--   2 news     news        9506 Jan 25 05:46 89-138r0.txt.Z
-rw-r--r--   2 news     news       14416 Jan 25 05:46 89-149r0.brf.Z
-rw-r--r--   2 news     news       12081 Jan 25 05:46 90-009r0.txt.Z
-rw-r--r--   2 news     news        1618 Jan 25 05:46 90-025r0.txt.Z
-rw-r--r--   2 news     news        2660 Jan 25 05:47 dr.txt.Z
-rw-r--r--   2 news     news        1202 Jan 25 05:47 feb_agnd.txt.Z
-rw-r--r--   2 news     news        3629 Jan 25 05:47 files.bbs
-rw-r--r--   2 news     news         962 Jan 25 05:47 how2get.txt.Z
-rw-r--r--   2 news     news        2635 Jan 29 14:37 index
-rw-r--r--   2 news     news        3032 Jan 25 05:47 jan_mail.txt.Z
-rw-r--r--   2 news     news        1373 Jan 25 05:47 mem_form.txt.Z
-rw-r--r--   2 news     news       21556 Jan 25 05:47 members.txt.Z
-rw-r--r--   2 news     news        1213 Jan 25 05:47 name_con.txt.Z
-rw-r--r--   2 news     news        2264 Jan 25 05:47 proj132.txt.Z
-rw-r--r--   2 news     news         613 Jan 25 05:47 s2pr.txt.Z
-rw-r--r--   2 news     news        1127 Jan 25 05:47 schedule.txt.Z
-rw-r--r--   2 news     news        2734 Jan 25 05:47 scsi2nws.txt.Z
-rw-r--r--   2 news     news        6084 Jan 25 05:48 t9docreg.txt.Z
-rw-r--r--   2 news     news        2650 Jan 25 05:48 t9sumacr.txt.Z
-rw-r--r--   2 news     news        2099 Jan 25 05:48 t9sumadr.txt.Z
-rw-r--r--   2 news     news         889 Jan 25 05:48 t9sumint.txt.Z
-rw-r--r--   2 news     news         821 Jan 25 05:48 t9sumorg.txt.Z
-rw-r--r--   2 news     news        3124 Jan 25 05:48 t9sumpro.txt.Z
-rw-r--r--   2 news     news        6305 Jan 25 05:48 t9sumq&a.txt.Z
-rw-r--r--   2 news     news        7409 Jan 25 05:48 t9sumtrm.txt.Z
-rw-r--r--   2 news     news        2711 Jan 25 05:48 vendorid.txt.Z
-rw-r--r--   2 news     news        2207 Jan 25 05:48 x3t9_2.txt.Z

area02:
total 448
-rw-r--r--   2 news     news       53332 Jan 25 11:57 dsz0208.zip
-rw-r--r--   2 news     news        1688 Jan 25 11:57 files.bbs
-rw-r--r--   2 news     news        1082 Jan 25 11:57 help4dsz.zip
-rw-r--r--   2 news     news         277 Jan 29 14:29 index
-rw-r--r--   2 news     news       34361 Jan 25 11:57 opuser.zip
-rw-r--r--   2 news     news      131517 Jan 25 11:58 pkz101.exe

area04:
total 464
-rw-r--r--   2 news     news        1087 Jan 25 11:56 abstract.doc
-rw-r--r--   2 news     news         972 Jan 25 11:56 files.bbs
-rw-r--r--   2 news     news         377 Jan 28 16:43 index
-rw-r--r--   2 news     news       43757 Jan 25 11:56 nbs_c.zip
-rw-r--r--   2 news     news      116154 Jan 25 11:56 nbs_exe.zip
-rw-r--r--   2 news     news       45105 Jan 25 11:56 nbs_tp.zip
-rw-r--r--   2 news     news       16673 Jan 25 11:57 scsitest.zip
-rw-r--r--   2 news     news        5118 Jan 25 11:57 specify.txt

area05:
total 366
-rw-r--r--   2 news     news       36723 Jan 25 11:53 90-001r0.txt.Z
-rw-r--r--   2 news     news        5990 Jan 25 11:53 90-004r0.txt.Z
-rw-r--r--   2 news     news       56032 Jan 25 11:54 90-005r0.txt.Z
-rw-r--r--   2 news     news       56623 Jan 25 11:55 90-006r0.txt.Z
-rw-r--r--   2 news     news       12081 Jan 25 11:55 90-009r0.txt.Z
-rw-r--r--   2 news     news        3622 Jan 25 11:55 90-021r0.txt.Z
-rw-r--r--   2 news     news        4426 Jan 25 11:55 90-023r0.txt.Z
-rw-r--r--   2 news     news        1618 Jan 25 11:55 90-025r0.txt.Z
-rw-r--r--   2 news     news        1421 Jan 25 11:55 files.bbs.Z
-rw-r--r--   2 news     news         506 Jan 28 16:40 index

area06:
total 182
-rw-r--r--   2 news     news         546 Jan 25 11:58 files.bbs
-rw-r--r--   2 news     news         570 Jan 26 08:33 index
-rw-r--r--   2 news     news        1216 Jan 25 11:58 scsiarb.zip
-rw-r--r--   2 news     news        6984 Jan 25 11:58 smiley.txt
-rw-r--r--   2 news     news        9181 Jan 25 11:58 strip_z.exe
-rw-r--r--   2 news     news        9201 Jan 25 11:58 technote.zip
-rw-r--r--   2 news     news       10139 Jan 25 11:58 wsc.zip
-rw-r--r--   2 news     news       36394 Jan 25 11:58 wscnvn.zip
-rw-r--r--   2 news     news       13334 Jan 25 11:59 wstxt.zip

area07:
total 376
-rw-r--r--   2 news     news      187041 Jan 25 12:01 17b.zip
-rw-r--r--   2 news     news         747 Jan 25 12:01 files.bbs
-rw-r--r--   2 news     news         419 Jan 26 08:29 index

area08:
total 914
-rw-r--r--   2 news     news        3281 Jan 25 12:01 files.bbs
-rw-r--r--   2 news     news        1146 Jan 29 14:42 index
-rw-r--r--   2 news     news         685 Jan 25 12:01 notice.txt.Z
-rw-r--r--   2 news     news       22523 Jan 25 12:02 rev10b.zip
-rw-r--r--   2 news     news        5162 Jan 25 12:02 s2r10-op.zip
-rw-r--r--   2 news     news        3251 Jan 25 12:02 s2r10-pc.zip
-rw-r--r--   2 news     news       10056 Jan 25 12:02 s2r10asc.zip
-rw-r--r--   2 news     news       16756 Jan 25 12:02 s2r10b00.zip
-rw-r--r--   2 news     news        3489 Jan 25 12:02 s2r10b01.zip
-rw-r--r--   2 news     news         893 Jan 25 12:02 s2r10b02.zip
-rw-r--r--   2 news     news        4022 Jan 25 12:02 s2r10b03.zip
-rw-r--r--   2 news     news       14943 Jan 25 12:02 s2r10b04.zip
-rw-r--r--   2 news     news       31129 Jan 25 12:02 s2r10b05.zip
-rw-r--r--   2 news     news       19050 Jan 25 12:02 s2r10b06.zip
-rw-r--r--   2 news     news       61209 Jan 25 12:03 s2r10b07.zip
-rw-r--r--   2 news     news       58025 Jan 25 12:03 s2r10b08.zip
-rw-r--r--   2 news     news       36344 Jan 25 12:03 s2r10b09.zip
-rw-r--r--   2 news     news        9891 Jan 25 12:03 s2r10b10.zip
-rw-r--r--   2 news     news        5385 Jan 25 12:03 s2r10b11.zip
-rw-r--r--   2 news     news        3404 Jan 25 12:03 s2r10b12.zip
-rw-r--r--   2 news     news       32780 Jan 25 12:03 s2r10b13.zip
-rw-r--r--   2 news     news       11599 Jan 25 12:04 s2r10b14.zip
-rw-r--r--   2 news     news       15233 Jan 25 12:04 s2r10b15.zip
-rw-r--r--   2 news     news       22651 Jan 25 12:04 s2r10b16.zip
-rw-r--r--   2 news     news        6164 Jan 25 12:04 s2r10b17.zip
-rw-r--r--   2 news     news       32663 Jan 25 12:04 s2r10ba.zip
-rw-r--r--   2 news     news        8968 Jan 25 12:04 style.zip

area11:
total 498
-rw-r--r--   2 news     news        3433 Jan 25 12:04 diffprot.zip
-rw-r--r--   2 news     news        1338 Jan 25 12:04 files.bbs
-rw-r--r--   2 news     news        6113 Jan 25 12:04 icon.zip
-rw-r--r--   2 news     news        1077 Jan 29 14:46 index
-rw-r--r--   2 news     news        9590 Jan 25 12:04 noncbl.zip
-rw-r--r--   2 news     news       10006 Jan 25 12:05 noncblb.zip
-rw-r--r--   2 news     news       20666 Jan 25 12:05 nondev.zip
-rw-r--r--   2 news     news       21602 Jan 25 12:05 nondevb.zip
-rw-r--r--   2 news     news        1664 Jan 25 12:05 notice
-rw-r--r--   2 news     news        3093 Jan 25 12:05 passdiff.zip
-rw-r--r--   2 news     news        4272 Jan 25 12:05 phwarb.zip
-rw-r--r--   2 news     news        3772 Jan 25 12:05 phwoarb.zip
-rw-r--r--   2 news     news        7045 Jan 25 12:05 s2_apx_a.zip
-rw-r--r--   2 news     news        5638 Jan 25 12:05 sampcnfg.zip
-rw-r--r--   2 news     news       28780 Jan 25 12:05 shldcbl1.zip
-rw-r--r--   2 news     news       27594 Jan 25 12:05 shldcbl2.zip
-rw-r--r--   2 news     news       19366 Jan 25 12:06 shlddev1.zip
-rw-r--r--   2 news     news       30914 Jan 25 12:06 shlddev2.zip
-rw-r--r--   2 news     news        8568 Jan 25 12:06 signlseq.zip
-rw-r--r--   2 news     news        7206 Jan 25 12:06 snapdxfr.zip
-rw-r--r--   2 news     news        6750 Jan 25 12:06 snapsel.zip
-rw-r--r--   2 news     news        3380 Jan 25 12:06 termdiff.zip
-rw-r--r--   2 news     news        3241 Jan 25 12:06 termse.zip

area13:
total 442
-rw-r--r--   2 news     news       25794 Jan 25 12:19 atbuscam.txt.Z
-rw-r--r--   2 news     news        3659 Jan 25 12:19 atbusmin.txt.Z
-rw-r--r--   2 news     news        8528 Jan 25 12:20 camdoc.txt.Z
-rw-r--r--   2 news     news       14250 Jan 25 12:20 camsim.txt.Z
-rw-r--r--   2 news     news       10408 Jan 25 12:20 camstuff.zip
-rw-r--r--   2 news     news       10178 Jan 25 12:20 cl_ata.txt.Z
-rw-r--r--   2 news     news        1014 Jan 25 12:20 dal_prop.txt.Z
-rw-r--r--   2 news     news        1168 Jan 25 12:20 dmaresrc.txt.Z
-rw-r--r--   2 news     news        1557 Jan 25 12:20 dos_msg0.txt.Z
-rw-r--r--   2 news     news        4010 Jan 25 12:20 dos_osd.txt.Z
-rw-r--r--   2 news     news        6338 Jan 25 12:20 dos_osd1.txt.Z
-rw-r--r--   2 news     news        6508 Jan 25 12:20 dos_osd2.txt.Z
-rw-r--r--   2 news     news        3028 Jan 25 12:20 files.bbs
-rw-r--r--   2 news     news        1996 Jan 29 15:01 index
-rw-r--r--   2 news     news        2082 Jan 25 12:20 init-int.txt.Z
-rw-r--r--   2 news     news        1043 Jan 25 12:21 issues.txt.Z
-rw-r--r--   2 news     news        4930 Jan 25 12:21 justify.txt.Z
-rw-r--r--   2 news     news        2617 Jan 25 12:21 library.txt.Z
-rw-r--r--   2 news     news        5351 Jan 25 12:21 min8810.txt.Z
-rw-r--r--   2 news     news        2651 Jan 25 12:21 min8812.txt.Z
-rw-r--r--   2 news     news        3953 Jan 25 12:21 min8901.txt.Z
-rw-r--r--   2 news     news        2726 Jan 25 12:21 min8902.txt.Z
-rw-r--r--   2 news     news        3014 Jan 25 12:21 min8903.txt.Z
-rw-r--r--   2 news     news        4525 Jan 25 12:21 min8904.txt.Z
-rw-r--r--   2 news     news        3922 Jan 25 12:21 min8905.txt.Z
-rw-r--r--   2 news     news        5192 Jan 25 12:21 min8906.txt.Z
-rw-r--r--   2 news     news        4118 Jan 25 12:21 min8907.txt.Z
-rw-r--r--   2 news     news        3748 Jan 25 12:21 min8908.txt.Z
-rw-r--r--   2 news     news        2446 Jan 25 12:22 newidea.doc.Z
-rw-r--r--   2 news     news        2528 Jan 25 12:22 oct_unix.txt.Z
-rw-r--r--   2 news     news        3131 Jan 25 12:22 pdiag.doc.Z
-rw-r--r--   2 news     news        1930 Jan 25 12:22 phy2log.txt.Z
-rw-r--r--   2 news     news        2804 Jan 25 12:22 phystolg.txt.Z
-rw-r--r--   2 news     news        5486 Jan 25 12:22 pick-chs.txt.Z
-rw-r--r--   2 news     news        3161 Jan 25 12:22 structur.txt.Z
-rw-r--r--   2 news     news        7306 Jan 25 12:22 target.txt.Z
-rw-r--r--   2 news     news        4108 Jan 25 12:22 u9001041.txt.Z
-rw-r--r--   2 news     news        3731 Jan 25 12:22 u9001042.txt.Z
-rw-r--r--   2 news     news        3475 Jan 25 12:22 u9001043.txt.Z
-rw-r--r--   2 news     news        4741 Jan 25 12:22 u9001044.txt.Z
-rw-r--r--   2 news     news        6861 Jan 25 12:22 u9001061.txt.Z
-rw-r--r--   2 news     news        1244 Jan 25 12:23 unixosd.txt.Z

area14:
total 1008
-rw-r--r--   2 news     news         629 Jan 25 12:23 files.bbs
-rw-r--r--   2 news     news         428 Jan 29 15:07 index
-rw-r--r--   2 news     news       12977 Jan 25 12:23 ipihppi.prt.Z
-rw-r--r--   2 news     news       13373 Jan 25 12:23 ipihppi.txt.Z
-rw-r--r--   2 news     news      126785 Jan 25 12:23 iso1.zip
-rw-r--r--   2 news     news       64395 Jan 25 12:24 iso2d.zip
-rw-r--r--   2 news     news      256287 Jan 25 12:25 iso3d.zip
-rw-r--r--   2 news     news        9115 Jan 25 12:25 l3tapcg.txt.Z
-rw-r--r--   2 news     news        9115 Jan 25 12:25 l3tapwg.txt.Z
-rw-r--r--   2 news     news        3667 Jan 25 12:25 rdeferr.txt.Z
-rw-r--r--   2 news     news        7677 Jan 25 12:25 rl3tpwg.txt.Z

area16:
total 426
-rw-r--r--   2 news     news        8801 Jan 25 12:06 89-139r1.prn.Z
-rw-r--r--   2 news     news        6025 Jan 25 12:06 89-139r1.zip
-rw-r--r--   2 news     news       69867 Jan 25 12:07 esdifigs.zip
-rw-r--r--   2 news     news         250 Jan 25 12:07 files.bbs
-rw-r--r--   2 news     news         222 Jan 29 15:13 index
-rw-r--r--   2 news     news      127850 Jan 25 12:07 isoe.zip

area17:
total 324
-rw-r--r--   2 news     news        2327 Jan 25 12:27 88-112r0.txt.Z
-rw-r--r--   2 news     news       19680 Jan 25 12:27 88-129r0.txt.Z
-rw-r--r--   2 news     news        9138 Jan 25 12:28 88-160r0.txt.Z
-rw-r--r--   2 news     news       10849 Jan 25 12:28 89-020r0.txt.Z
-rw-r--r--   2 news     news       10265 Jan 25 12:28 89-045r0.txt.Z
-rw-r--r--   2 news     news        3328 Jan 25 12:28 fcdastre.zip
-rw-r--r--   2 news     news        1314 Jan 25 12:28 files.bbs
-rw-r--r--   2 news     news         774 Jan 25 12:28 fomtnot.txt.Z
-rw-r--r--   2 news     news       15391 Jan 25 12:28 fowg0689.txt.Z
-rw-r--r--   2 news     news       11591 Jan 25 12:28 fowg0789.txt.Z
-rw-r--r--   2 news     news       11614 Jan 25 12:28 fowg0889.txt.Z
-rw-r--r--   2 news     news       18175 Jan 25 12:29 fowg0989.txt.Z
-rw-r--r--   2 news     news        4651 Jan 25 12:29 fowg1089.txt.Z
-rw-r--r--   2 news     news       13410 Jan 25 12:29 fowg1189.txt.Z
-rw-r--r--   2 news     news       14251 Jan 25 12:29 fowg1289.txt.Z
-rw-r--r--   2 news     news         673 Jan 29 15:15 index

area18:
total 1220
-rw-r--r--   2 news     news       37271 Jan 25 12:29 89-001r0.txt.Z
-rw-r--r--   2 news     news        1451 Jan 25 12:29 89-008r1.txt.Z
-rw-r--r--   2 news     news         394 Jan 25 12:30 89-009r0.txt.Z
-rw-r--r--   2 news     news         548 Jan 25 12:30 89-010r0.txt.Z
-rw-r--r--   2 news     news         416 Jan 25 12:30 89-011r0.txt.Z
-rw-r--r--   2 news     news         909 Jan 25 12:30 89-012r1.txt.Z
-rw-r--r--   2 news     news         726 Jan 25 12:30 89-013r1.txt.Z
-rw-r--r--   2 news     news         825 Jan 25 12:30 89-016r1.txt.Z
-rw-r--r--   2 news     news        3512 Jan 25 12:30 89-018r0.txt.Z
-rw-r--r--   2 news     news        7796 Jan 25 12:30 89-019r1.zip
-rw-r--r--   2 news     news       10849 Jan 25 12:30 89-020r0.txt.Z
-rw-r--r--   2 news     news        1318 Jan 25 12:30 89-021r0.txt.Z
-rw-r--r--   2 news     news         890 Jan 25 12:30 89-023r0.txt.Z
-rw-r--r--   2 news     news        1264 Jan 25 12:30 89-024r0.zip
-rw-r--r--   2 news     news        1140 Jan 25 12:30 89-025r0.txt.Z
-rw-r--r--   2 news     news       22958 Jan 25 12:31 89-028r1.brf.Z
-rw-r--r--   2 news     news        3197 Jan 25 12:31 89-035r0.zip
-rw-r--r--   2 news     news        3591 Jan 25 12:31 89-036r1.zip
-rw-r--r--   2 news     news        5306 Jan 25 12:31 89-042r0.zip
-rw-r--r--   2 news     news        4707 Jan 25 12:31 89-047r0.zip
-rw-r--r--   2 news     news       16642 Jan 25 12:31 89-049r0.brf.Z
-rw-r--r--   2 news     news       13671 Jan 25 12:31 89-050r1.zip
-rw-r--r--   2 news     news        3710 Jan 25 12:31 89-053r0.txt.Z
-rw-r--r--   2 news     news       45322 Jan 25 12:31 89-055r1.zip
-rw-r--r--   2 news     news        2491 Jan 25 12:31 89-058r0.zip
-rw-r--r--   2 news     news        7952 Jan 25 12:31 89-061r0.zip
-rw-r--r--   2 news     news       12527 Jan 25 12:32 89-066r1.zip
-rw-r--r--   2 news     news        1134 Jan 25 12:32 89-068r0.zip
-rw-r--r--   2 news     news       20518 Jan 25 12:32 89-075r1.brf.Z
-rw-r--r--   2 news     news       10240 Jan 25 12:32 89-090r0.zip
-rw-r--r--   2 news     news       18112 Jan 25 12:32 89-094r6.zip
-rw-r--r--   2 news     news        7722 Jan 25 12:32 89-095r1.ws.Z
-rw-r--r--   2 news     news         713 Jan 25 12:32 89-101r0.txt.Z
-rw-r--r--   2 news     news         806 Jan 25 12:32 89-102r0.txt.Z
-rw-r--r--   2 news     news        3275 Jan 25 12:32 89-103r1.zip
-rw-r--r--   2 news     news      107871 Jan 25 12:33 89-108r0.zip
-rw-r--r--   2 news     news        4889 Jan 25 12:33 89-109r1.zip
-rw-r--r--   2 news     news        2406 Jan 25 12:33 89-110r0.zip
-rw-r--r--   2 news     news       19218 Jan 25 12:33 89-111r0.brf.Z
-rw-r--r--   2 news     news        8127 Jan 25 12:33 89-120r0.zip
-rw-r--r--   2 news     news       19668 Jan 25 12:33 89-126r0.brf.Z
-rw-r--r--   2 news     news       85926 Jan 25 12:34 89-130r1.zip
-rw-r--r--   2 news     news        6843 Jan 25 12:34 89-133r1.zip
-rw-r--r--   2 news     news        8498 Jan 25 12:34 89-138r0.zip
-rw-r--r--   2 news     news        6025 Jan 25 12:34 89-139r1.zip
-rw-r--r--   2 news     news        2347 Jan 25 12:34 89-140r0.txt.Z
-rw-r--r--   2 news     news         996 Jan 25 12:34 89-145r1.txt.Z
-rw-r--r--   2 news     news       14524 Jan 25 12:34 89-149r0.brf.Z
-rw-r--r--   2 news     news        3065 Jan 25 12:34 89-150r0.zip
-rw-r--r--   2 news     news        4526 Jan 25 12:34 89-150r1.zip
-rw-r--r--   2 news     news        3898 Jan 25 12:34 89-153r0.txt.Z
-rw-r--r--   2 news     news         676 Jan 25 12:35 89-161r0.txt.Z
-rw-r--r--   2 news     news        7661 Jan 25 12:35 files.bbs
-rw-r--r--   2 news     news        2644 Jan 29 15:37 index
----------------------------------- cut here -----------------------------------

Return-Path: archived@mgse
Return-Path: <archived@mgse>
Received: from rex.cs.tulane.edu by pawl.rpi.edu (4.1/HUB10);
	id AA04994; Thu, 15 Feb 90 04:58:31 EST for night
From: <archived@mgse>
Received:  by rex.cs.tulane.edu; Thu, 15 Feb 90 04:00:34 -0600
Message-Id: <9002151000.AA16198@rex.cs.tulane.edu>
To: night@pawl.rpi.edu
Subject: /archive/other/scsi-bbs/index
Date: Wed Feb 14 23:15:00 1990


----------------------------------- cut here -----------------------------------
These files were sent to me by John Lohmeyer, sysop of the SCSI BBS
(316-636-8700). Most of the files from the BBS are here, available 
>From the archive mail server in file are other/scsi/ or via anonymous
uucp in file area /archive/other/scsi.

Things are laid out like the bbs, files for a particular subject are in a
sub-directory named after that file area.


file area	Contents
---------------	---------------------------------------
area01/*	X3T9.2 General Information
area02/*	Communications Software
area04/*	NBS SCSI Verification Tests
area05/*	X3T9.2 Recent Documents (Current Year)
area06/*	Miscellaneous Files
area07/*	SCSI-1 Revision 17B Text Files
area08/*	SCSI-2 Draft Standard Text Files
area11/*	SCSI-2 AutoCAD Figures
area13/*	SCSI-2 Common Access Method File Area
area14/*	IPI files
area16/*	ESDI Document and Related Files
area17/*	Fiber Channel File Area
area18/*	X3T9.2 Documents from 1989



File area: area01

87-029r1.txt.Z	X3T9.2 &.3 Minutes - Feb 87
87-071r0.brf.Z	X3T9.2 &.3 Minutes - Apr 87
87-080r0.txt.Z	May 87 SCSI Working Group Minutes
87-090r0.brf.Z	X3T9.2 &.3 Minutes - Jun 87
87-107r0.txt.Z	Jul 87 SCSI Working Group Minutes
87-135r1.brf.Z	X3T9.2 Minutes - Aug 87
87-153r1.txt.Z	Aug 87 SCSI Working Group Minutes
87-171r0.brf.Z	X3T9.2 Minutes - Oct 87
87-185r0.txt.Z	Oct 87 SCSI Working Group Minutes
87-200r2.brf.Z	X3T9.2 Minutes - Dec 87
88-011r0.txt.Z	Jan 88 SCSI Working Group Minutes
88-020r1.brf.Z	X3T9.2 Minutes - Feb 88
88-031r0.txt.Z	Mar 88 SCSI Working Group Minutes
88-040r1.brf.Z	X3T9.2 Minutes - Apr 88
88-050r0.txt.Z	May 88 SCSI Working Group Minutes
88-066r0.brf.Z	X3T9.2 Minutes - Jun 88
88-072r0.txt.Z	Jul 88 SCSI Working Group Minutes
88-096r0.brf.Z	X3T9.2 Minutes - Jul 88
88-109r2.txt.Z	Aug 88 SCSI Working Group Minutes
88-130r2.brf.Z	X3T9.2 Minutes - Oct 88
88-153r0.txt.Z	Nov 88 SCSI Working Group Minutes
88-164r0.brf.Z	X3T9.2 Minutes - Dec 88
89-019r1.txt.Z	Jan 89 SCSI Working Group Minutes
89-028r1.brf.Z	X3T9.2 Minutes - Feb 89
89-042r0.txt.Z	Mar 89 SCSI Working Group Minutes
89-049r0.brf.Z	X3T9.2 Minutes - Apr 89
89-066r1.txt.Z	May 89 SCSI Working Group Minutes
89-075r0.brf.Z	X3T9.2 Minutes - Jun 89
89-090r0.txt.Z	Jul 89 SCSI Working Group Minutes
89-111r0.brf.Z	X3T9.2 Minutes - Aug 89
89-120r0.txt.Z	Sep 89 SCSI Working Group Minutes
89-126r0.brf.Z	X3T9.2 Minutes - Oct 89
89-138r0.txt.Z	Oct 89 SCSI Working Group Minutes
89-149r0.brf.Z	X3T9.2 Minutes - Dec 89
90-009r0.txt.Z	Jan 90 SCSI Working Group Minutes
90-025r0.txt.Z	March '90 Working Group Meeting Announcement
dr.txt.Z	X3T9.2 Recent Document Register 
feb_agnd.txt.Z	February 1990 Plenary Meeting Draft Agenda
how2get.txt.Z	How to obtain SCSI Standards 
jan_mail.txt.Z	Cover Page from the January Mailing
mem_form.txt.Z	Application Form for Membership and Mailings
members.txt.Z	X3T9.2 Current Membership List
name_con.txt.Z	File Name conventions on the SCSI BBS
proj132.txt.Z	132-column Summary of X3T9 Projects 
s2pr.txt.Z 	here to send SCSI-2 Public Review Comments
schedule.txt.Z	X3T9.2 Meeting Schedule
scsi2nws.txt.Z	What SCSI-2 is about--how it differs from SCSI
t9docreg.txt.Z	X3T9 1987 Document Register
t9sumacr.txt.Z	X3 and ANSI Jargon and Acronyms
t9sumadr.txt.Z	Useful Addresses and phone numbers
t9sumadr.txt.Z	Useful Addresses and phone numbers
t9sumint.txt.Z	Introduction
t9sumorg.txt.Z	Standards Organizations
t9sumpro.txt.Z	Hints on getting proposals accepted
t9sumq&a.txt.Z	X3T9 Questions and Answers
t9sumtrm.txt.Z	Interface jargon
vendorid.txt.Z	The current SCSI-2 Vendor ID List
x3t9_2.txt.Z	Introduction to X3T9.2 


File area: area02

pkz101.exe    ZIP file utility. Fastest, best compression.
dsz0208.zip   DSZ from Omen Technology
help4dsz.zip  Batch files to use ZMODEM from Procomm
opuser.zip    Opus Users Manual (The SCSI runs Opus)

---
files.bbs.Z	Listing of available files from the bbs as of 20 Jan 90


File area: area04

specify.txt   Read this file (You can type it online)
nbs_c.zip     'C' Source files, SCSI conformance test for Adaptec dev sys
nbs_exe.zip   Executable files
nbs_tp.zip    Test Procedure and Misc files

abstract.doc Abstract of the NIST project for testing
scsitest.zip The files including the Abstract

---
files.bbs.Z	Listing of available files from the bbs as of 20 Jan 90


File area: area05

90-001r0.txt.Z	1989 X3T9.2 Annual Report
90-004r0.txt.Z	32-bit on a single 110-pin connector (L cable)
90-005r0.txt.Z	16/32-bit P/Q cable stand alone document
90-006r0.txt.Z	16/32-bit P/L cable stand alone document
90-009r0.txt.Z	San Jose Working Group Minutes (1/9-10/90)
90-021r0.txt.Z	Additional SCSI Caching Control
90-023r0.txt.Z	Cable Working Group Minutes - Jan '90
90-025r0.txt.Z	March '90 Working Group Meeting Announcement

---
files.bbs.Z	Listing of available files from the bbs as of 20 Jan 90


File area: area06

--- Miscellaneous files --- 

fix_type.com  Lets you examine fixed disk types
ft.zip        a better fix_type than fix_type.com! 
scsiarb.zip   SCSI Arbitration Timing Model
smiley.txt    Assorted faces 8-) from Jeff Stai
strip_z.exe   Removes ^Z characters from text files
technote.zip  Mac Tech Note #96.  SCSI Problems. 
wsc.zip       A wordstar pagination program..simple. 
wscnvn.zip    WordStar File Conversion Utility - Useful!
wstxt.zip     WordStar to/from TXT w/ IBM graphics characters 

---
files.bbs	Listing of available files from the bbs as of 20 Jan 90



File area: area07

--- SCSI Version 1 Revision 17B WordStar Files --- 

    (This is the last revision prior to publication by ANSI.
     The editorial changes made during the final edit are not
     included in these files.  These files may be useful in 
     preparing functional specifications, etc.)

--- The whole SCSI-1 document (all of the above):

17b.zip  

---
files.bbs	Listing of available files from the bbs as of 20 Jan 90



File area: area08

notice.txt.Z	Copyright Notice - Read this first
rev10b.zip	Shows just what changed from Rev 10 to Rev 10b
s2r10-op.zip	Opcode Spreadsheet
s2r10-pc.zip	Page Code Spreadsheet
s2r10asc.zip	Additional Sense Code Spreadsheet
s2r10b00.zip	Section 00 Cover Page and Table of Contents
s2r10b01.zip	Section 01 Scope        
s2r10b02.zip	Section 02 Reference Documents    
s2r10b03.zip	Section 03 Glossary and Editorial Conventions 
s2r10b04.zip	Section 04 Physical Characteristics   
s2r10b05.zip	Section 05 Logical Characteristics   
s2r10b06.zip	Section 06 SCSI Commands and Status   
s2r10b07.zip	Section 07 Common Section for All Devices  
s2r10b08.zip	Section 08 Direct-Access      
s2r10b09.zip	Section 09 Sequential-Access     
s2r10b10.zip	Section 10 Printer       
s2r10b11.zip	Section 11 Processor       
s2r10b12.zip	Section 12 Write-Once       
s2r10b13.zip	Section 13 CD-ROM        
s2r10b14.zip	Section 14 Scanner       
s2r10b15.zip	Section 15 Optical Memory Device    
s2r10b16.zip	Section 16 Medium Changer Device    
s2r10b17.zip	Section 17 Communications Device    
s2r10ba.zip	Section A Appendixes       
style.zip	SCSI-2 Style manual


File area: area11

diffprot.zip	SCSI-2 Fig: Differential Protection Circuit
icon.zip	SCSI Icon (not currently in the document)
noncbl.zip	SCSI-2 Fig: Nonshielded Cable A Connector
noncblb.zip	SCSI-2 Fig: Nonshielded Cable B Connector (Obs)
nondev.zip	SCSI-2 Fig: Nonshielded Device A Connector
nondevb.zip	SCSI-2 Fig: Nonshielded Device B Connector (Obs)
passdiff.zip	SCSI-2 Fig: Passive Differential Terminator
phwarb.zip	SCSI-2 Fig: Phase Diagram (Obs)
phwoarb.zip	SCSI-2 Fig: Phase Diagram (Obs)
s2_apx_a.zip	SCSI-2 Fig: Signal Sequence Diagram (DWG file)
sampcnfg.zip	SCSI-2 Fig: Sample Configurations
shldcbl1.zip	SCSI-2 Fig: Shielded Cable Alternative 1 (Obs)
shldcbl2.zip	SCSI-2 Fig: Shielded Cable Alternative 2
shlddev1.zip	SCSI-2 Fig: Shielded Device Alternative 1 (Obs)
shlddev2.zip	SCSI-2 Fig: Shielded Device Alternative 2
signlseq.zip	SCSI-1 Fig: Signal Sequence Diagram (Obs)
snapdxfr.zip	SCSI-2 Fig: Snapshot Prior to Data Transfer
snapsel.zip	SCSI-2 Fig: Snapshot Prior to Selection
termdiff.zip	SCSI-2 Fig: Differential Terminator
termse.zip	SCSI-2 Fig: Single-ended Terminator


File area: area13

atbuscam.txt.Z	The initial draft of the proposed ATBus device 
atbusmin.txt.Z	AT Bus Committee Minutes 3/9/89 
camdoc.txt.Z	CAM Working Document from 1/12/89 meeting
camsim.txt.Z	Merged SIM and Initialization Spec 
cl_ata.txt.Z	Cirrus Logic ATA rev. 1.2 Proposals
dal_prop.txt.Z	Layering and Control Blocks
dmaresrc.txt.Z	DMA Resource message from Greg Slaughter
dos_msg0.txt.Z	DOS OSD 
dos_osd.txt.Z	OSD interface spec for DOS 
dos_osd1.txt.Z	Revised DOS OSD proposal 
dos_osd2.txt.Z	Revised DOS OSD proposal 
init-int.txt.Z	Comments on Shishir's proposal 
issues.txt.Z	NCR presentation - ISSUES 
justify.txt.Z	Justification and call to arms
library.txt.Z	NCR SCSI Library Description 
min8810.txt.Z	Minutes of the October 19 meeting in San Jose
min8812.txt.Z	Minutes of the December 7 meeting in San Diego
min8901.txt.Z	Minutes of January 17 meeting in Irvine
min8902.txt.Z	Minutes of February 22 meeting in Austin
min8903.txt.Z	Minutes of March 8 meeting in Milpitas 
min8904.txt.Z	Minutes of April 13 meeting in Denver 
min8905.txt.Z	Minutes of May 10 meeting in Wichita
min8906.txt.Z	Minutes of June 8 meeting in Cupertino
min8907.txt.Z	Minutes of July 12 meeting in Chicago
min8908.txt.Z	Minutes of August 9-10 meeting in Costa Mesa
newidea.doc.Z	Rom/Ram Bios stratagy for backward compatiblity 
oct_unix.txt.Z	October Unix OSD notes and Nov Agenda.
pdiag.doc.Z	ATA PDIAG / DASP Timing Specification 
phy2log.txt.Z	phyical to logical conversiov C program 
phystolg.txt.Z	CONVERSION TO/FROM PHYS/LOGICAL CAPACITIES 
pick-chs.txt.Z	Algorithm to pick C/H/S values from # blocks 
structur.txt.Z	NCR CAM structure definition 
target.txt.Z	NCR proposal for section 9 of CAM Document
u9001041.txt.Z	Gallant's comments on Richman's proposal
u9001042.txt.Z	Bob Snively's Target Mode Proposal
u9001043.txt.Z	Unix-OSD Mailing list (Internet and UUCP)
u9001044.txt.Z	Richman's response to Gallant's comments
u9001061.txt.Z	Gallant's further remarks
unixosd.txt.Z	Interested parties UNIX-OSD, mail list


File area: area14

ipihppi.prt	Draft copy of IPI-3 Command Set on HPPI
ipihppi.txt	IPI-3--HPPI Proposed Standard 
iso1.zip	IPI-1 Physical Layer
iso2d.zip	IPI-2 Device Specific Magnetic Disk
iso3d.zip	IPI-3 Device Generic Magnetic and Optical Disk
l3tapcg.txt	Changes to stds from tape working group 
l3tapwg.txt	Feb 1 Tape Working Group Minutes 
rdeferr.txt	Revised std changes for deferred errors 
rl3tpwg.txt	Revised tape working group minutes 


File area: area16

89-139r1.prn.Z	Differences between ESDI Rev 3 and Rev 3A
89-139r1.zip	Differences between ESDI Rev 3 and Rev 3A
esdifigs.zip	Some ESDI Connector figures (.DXF files)
isoe.zip	ISO ESDI Draft International Standard (Rev 3A)


File area: area17

88-112r0.txt.Z	August '88 Fiber Optic Study Group Highlights
88-129r0.txt.Z	August & September '88 Minutes
88-160r0.txt.Z	Fiber Channel Description
89-020r0.txt.Z	December '88 Minutes
89-045r0.txt.Z	January '89 Minutes
fcdastre.zip	Los Alamos Fiber Channel Data Streaming paper 
fowg0689.txt.Z	June 22&23 FO Working Group Minutes 
fowg0789.txt.Z	July 89 Fiber Channel Working Group Minutes
fowg0889.txt.Z	August 23 Fiber Channel Working Group Minutes
fowg0989.txt.Z	9/11&12 Fiber Channel Working Group Minutes
fowg1089.txt.Z	10/16 Fiber Channel Working Group Minutes
fowg1189.txt.Z	11/2&3 Fiber Channel Working Group Minutes
fowg1289.txt.Z	Dec 89 FC Working Group Minutes 


File area: area18

89-001r0.txt.Z	X3T9.2 Annual Report
89-008r1.txt.Z	"Brief" Description of Density Code Operation
89-009r0.txt.Z	COPY and Partitioned Tape
89-010r0.txt.Z	REQUEST SENSE EOM data on Partitioned Tape
89-011r0.txt.Z	MODE SELECT Device Configuration Parameters
89-012r1.txt.Z	Separation of BOM and BOP0
89-013r1.txt.Z	9.2.13 SPACE Command, Rev 6a, page 9-30
89-016r1.txt.Z	Active Format field in Device config page
89-018r0.txt.Z	Preliminary Cable Test Results
89-019r1.zip	Costa Mesa Working Group Minutes Jan '89
89-020r0.txt.Z	Fiber Optic Channel Working Group Minutes
89-021r0.txt.Z	Tape Read Underlength Detection
89-023r0.txt.Z	Synchronized Sector Offset for ESDI
89-024r0.zip	When not to clear sense data
89-025r0.txt.Z	SEARCH DATA Transfer Length Inconsistency
89-028r1.brf.Z	Feb 89 X3T9.2 Minutes (ASCII w/o enclosures)
89-035r0.zip	Tape Read Overlength Detection w/SILI Bit
89-036r1.zip	SCSI-3 Preparations for New Physical Layer(s)
89-042r0.zip	Milpitas Working Group Minutes Mar '89
89-047r0.zip	NCR Proposal for a LOGICAL UNIT RESET Message
89-049r0.brf.Z	Apr 89 X3T9.2 Minutes (ASCII w/o enclosures)
89-050r1.zip	Dan Davies' proposed changes to S2R8 Section 9
89-053r0.txt.Z	Tom Wicklund's comments on S2R8
89-055r1.zip	Gene Milligan's comments on S2R8
89-058r0.zip	John Lohmeyer's X3T9 Letter Ballot on SCSI-2
89-061r0.zip	SCSI Bus Fairness Proposal (ZIP'd ws.Z	4)
89-066r1.zip	Wichita Working Group Minutes
89-068r0.zip	Maxtor Public Review Comment on ESDI
89-075r1.brf.Z	Jun 89 X3T9.2 Minutes (ASCII w/o enclosures)
89-090r0.zip	Chicago Working Group Minutes
89-094r6.zip	Single-cable 16-bit proposal
89-095r1.ws.Z	Read Sub-channel CD-ROM command fixes (SCSI-2)
89-101r0.txt.Z	Max Burst Size Rounding Definition
89-102r0.txt.Z	Another ESDI boo-boo cought by steely eyes
89-103r1.zip	Comments on r10 SCSI-2 document
89-108r0.zip	SONY proposal for CD-ROM device
89-109r1.zip	New Copy Segment Descriptors (Rev 1)
89-110r0.zip	Target Initiated SDTR Message Control
89-111r0.brf.Z	Aug 89 X3T9.2 Minutes (ASCII w/o enclosures)
89-120r0.zip	Oklahoma City Working Group Minutes
89-126r0.brf.Z	Oct 89 X3T9.2 Minutes (ASCII w/o enclosures)
89-130r1.zip	Packetized SCSI Proposal
89-133r1.zip	Multi-ported SCSI
89-138r0.zip	Santa Ana Working Group Minutes
89-139r1.zip	ESDI Changes 1/19/89 to 12/2/89 (Printer file)
89-140r0.txt.Z	WD public review comment/ASCII text
89-145r1.txt.Z	Proposed Additional Sense Code Qualifiers
89-149r0.brf.Z	Dec 89 X3T9.2 Minutes (ASCII w/o enclosures)
89-150r1.zip	16-bit single-cable Appendix Form
89-153r0.txt.Z	Minutes of SCSI Cable Impedance WG 12/4/89
89-161r0.txt.Z	Response letter to Alec Cawley (Quantel)

----------------------------------- cut here -----------------------------------

From owner-pc532%daver@mips.com Sun Mar 18 14:47:40 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: Re: SCSI
To: pc532%tarpit@daver.bungi.com
Date: Sun, 18 Mar 90 9:37:38 EST
From: John L. Connin <johnc%manatee@uunet.UU.NET>
X-Mailer: Elm [version 2.1 PL1]
Status: O


regards,
johnc

	------------------------------------------------------------

From: archived@mgse.UUCP (Archive Request Daemon)
Newsgroups: comp.periphs,comp.sources.wanted,alt.sources.wanted,comp.misc,comp.periphs.scsi
Subject: mgse archive server - SCSI BBS files
Message-ID: <1084@mgse.UUCP>
Date: 1 Mar 90 06:00:13 GMT
Organization: mgse
Lines: 47


Last Changed:	Sun Feb 18 14:08:54 CST 1990

This is a periodic posting of information about the mgse archive server
and the available files from the SCSI-bbs, including SCSI, ESDI, IPI,
and Fiber Channel documents from the standards committees.

Thanks to John Lohmeyer of NCR, a majority of the SCSI related files from the
SCSI BBS are now available from the mgse mail archive server. These files were
sent to me by Mr. Lohmeyer at his expense so that more people would have access
to them. The SCSI BBS (316-636-8700) contains a large amount of data relating
to SCSI, and ESDI as well as SCSI-2, IPI, and Fiber Channel, as well as the
last revision of the SCSI-1 standard before it went to publication by ANSI. If
you are interested in finding out what is available from the archive server,
send the message that follows to archive@mgse and you will get back an index
of names and descriptions and a unix style ls -lR listing of filenames and
sizes.

- cut here -----------------------------------------------------------------
help
send other/scsi-bbs/list
send other/scsi-bbs/index
- cut here -----------------------------------------------------------------

if you are interested in the SCSI Version 1, Revision 17B document, have
the bbs send other/scsi-bbs/area07/17b.zip in addition to the index and list
by including these lines at the end of the above message;

- cut here -----------------------------------------------------------------
set uuencode
send other/scsi-bbs/area07/17b.zip
- cut here -----------------------------------------------------------------

There files are also available for anonymous uucp at 504-467-1069,
2400 baud, login 'archive' in /archive/other/scsi-bbs. Callers at
300 or 1200 baud will have to send a break.

Thanks John!

Sun Feb 18 13:58:10 CST 1990, The Fiber Channel file area has been updated
with more files from the SCSI BBS.

-- 
Archive Server Deamon,  Metairie, LA.
uucp:           rex.cs.tulane.edu!mgse!archived or rex!mgse!archived
bitnet:         archived%mgse@REX.CS.TULANE.EDU
internet:       archived%mgse@rex.cs.tulane.edu



From owner-pc532%daver@mips.com Mon Mar 19 13:41:53 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Re: SCSI 
Date: Mon, 19 Mar 90 08:01:40 MST
From: Bdale Garbee <bdale@col.hp.com>
Status: O

> It would be nice if we could set up an archive site for Unix
> versions of these documents.  I'm willing to help out with converting
> the files (my site has arc, and I've gotten hold of a unix unzipper).  
> Anyone else interested in such a project?  

I am more than willing to make space available for things relevant to the pc532
group on col.hp.com for anonymous ftp.  We are not capable of supporting uucp
access for a variety of reasons, and we've not investigated running a mail
based server, but for the ftp-capable world, we're quite accessible.

I already have some of Bruce Culbertson's bits available, and now have floppy
copies of much of the crud that was on beowulf, and will be making that
available too.

Bdale

From owner-pc532%daver@mips.com Mon Mar 19 13:42:00 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Re: my board is up! 
Date: Mon, 19 Mar 90 07:48:49 MST
From: Bdale Garbee <bdale@col.hp.com>
Status: O

> Thats 220 ohms to +5, 330 to ground right? Also I assume that you are using
> a 400mhz or better scope with no ground wire. I measured the clocks by using
> a 400mhz tektronix scope with the short 'Z' ground probe.

Well that explains it!  You used a Tek scope!  :-)  Until recently, I designed
scopes for HP... now I is a manager... sigh...  after de-fluxing the resistor
pins, things look better... I think maybe I was getting a capacitive
connection to the probe through the flux.  Yes, I'm using a fast single-shot
digital scope.

> Of course the idea of doing worst case
> design in the first place is to ensure that a product is capable of being
> manufactured using components from a variety of vendors with different
> batches (i.e. Friday chips...).

Heartily agree!

> > Makes me feel ok about running at a bit over 20Mhz instead of 25 for the
> > duration.

> If it makes you happier. Of course you could run the board at 49.9Mhz :-)

What I meant by "for the duration" was "until I can get a working 50Mhz
oscillator"...  I'm the guy who ran his 10Mhz 32016 at just over 12.3 Mhz
with a heat sink and fan on the MMU... and cursed NS under my breath because
they never did a CMOS variant of the MMU.

Bdale

From owner-pc532%daver@mips.com Mon Mar 19 13:43:22 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Mon, 19 Mar 90 07:40:26 mst
From: Bdale Garbee <bdale@col.hp.com>
To: pc532@daver.bungi.com
Subject: another one going!
Status: O

Fred's board fired up the first time yesterday afternoon, with one of my
40.337Mhz oscillators, and the 32202 stolen from my board.  Fred is a novice at
this kind of hardware construction, so another round of kudos to Dave and George...
it's a nice design...

Now for disks and software...

Bdale

From owner-pc532%daver@mips.com Mon Mar 19 19:33:16 1990
Flags: 000000000011
Reply-To: pc532@daver.bungi.com
Date: Mon, 19 Mar 90 16:03 PST
From: dlr@daver.bungi.com (Dave Rand)
To: pc532@daver
Subject: Minisribe manuals
Status: O

If you want a Real manual on the Miniscribe 9380S, you must order it from
Minisribe. Their telephone number is +1 303 651 6000. The manual that
comes with the drive is (barely) enough to get it installed correctly.

BTW - the drive is working great! Very fast, and much quieter than Maxtor
drives...

Dave

From owner-pc532%daver@mips.com Tue Mar 20 04:39:44 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: arghhhhhh......
Date: 19 Mar 90 21:29:36 MEZ (Mon)
From: jkh@meepmeep.pcs.com (Jordan K. Hubbard)
Status: O

Well, it had to happen eventually and more fittingly to probably the only
person on this list that doesn't eat hardware for breakfast. My pc532
did not come up smiling upon first application of power. Sigh, alas poor
Yorick.. LED's don't light up, no nice banner on the terminal.

I took great care in soldering in things and placing the chips, but
nonethless..

My configuration is a stock pc532 with 8 1x9MB SIMMS (parity PAL has
been pulled to avoid having to deal with parity at this early stage).

Anyway. I called Dave & George (who were both very helpful despite being
rung up at work) and asked what to do next, being somewhat naive about
these matters (as previously mentioned) and a little distressed about it.

They told me to check a number of things, which I more-or-less did
(with the caveat of being little more than a fool holding an oscilloscope
probe) and here's what's going on so far (please excuse me if I toss out
a little useless or redundant information, I'm just noting what looks
important to my inexperienced eye).

1. All crystals are ocsillating merrily along at their assigned clock rates.

2. The CE and RD lines of the EPROM are being pulsed, though at slightly
   different times (sorry for the vague description but my ability to
   accurately calculate the period of a waveform given the number of divisions
   spanned and horizontal sweep speed of the scope has deteriorated).

3. There appears to be data on all data pins of the EPROM (though dammed if
   I can read it :-).

4. The select line (pin 4) of the ICU is high. Data appears to be getting
   here from the data bus. There is a signal on the /RD line but not the
   /WR line (makes sense, I guess). There appears to be naught but low
   amplitude noise on /ICU when the CPU is running (low during reset).
   SWAP (pin 11) and /INT seem to be always HIGH, even during and after
   reset. Is this right?. 

5. The SCSI Pal select (pin 5) is always HIGH. The /DACK0 and /DACK1 lines
   and always HIGH.


I'm not really sure what else to measure. I'm more or less SOL at this
point since it will take me a very long time to learn enough about
hardware this complex to start figuring out who is doing what to whom.
Even a simple buffer stage leaves me stumped for awhile since I have
to look everything up (what's that? What's it do?) and I had enough trouble
just with active filters back in EE2. Anyhoo, I really didn't write all this
up just to have a whine fest over the airwaves, what I'd really rather do
is suggest that the Folks That Know put us even further in their debt
(and a nice sized debt it's becoming, what with all the kit hassles and
design work done gratis) and start compiling a simplistic "What to do when
it don't work" sort of cribsheet.

With 50+ kits out there and a second board run coming up, I somehow don't
think I'll be the only hardware bonehead to assemble a dead system. It sure
would be nice to have someplace to start for us software types. The current
docs presume a great deal of hardware knowledge.

I posted this message to the list so that any threads starting from it
have some sort of anchor point.

If anyone else can make helpful suggestions about what (and I mean really
explicit "Look For ... at ..." information) to check further, I'd really
welcome the help. Nothing more frustrating than staring at $800+ worth of
fully populated board that's deader than a doornail. If I get any useful
stuff from folks other to George and Rand I'll package it up and forward
it to them for possible inclusion in the general problems sheet I mentioned.

Agh.. All dressed up and no place to go.

					Jordan Hubbard

From owner-pc532%daver@mips.com Tue Mar 20 05:10:49 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Mon, 19 Mar 90 15:15:11 EST
From: Jerry Callen <jcallen@maxzilla.encore.com>
To: pc532@daver.bungi.com
Subject: clock termination, ports, ROM
Status: O

The closer I get to being ready to power up, the more questions I have.
Here's my latest round.
   
1) I spent some time this weekend looking at the board, and at the nice
   Functional Specifications that George and Dave sent with the kits. I
   couldn't come up with a way of installing the termination resistors that
   didn't seem like a serious kludge. How are people doing this? I suppose I
   could carefully shave down the leads on the 220/330 ohm resistors so
   that I could stuff two in one hole. But there HAS to be a better way, eh?
   
2) What's the pinout for a 9-pin AT-style serial port? I'm probably
   going to initially just make a cable to go directly to the 25-pin
   socket on the back of my terminal, but eventually I want to have
   "proper" serial ports.

3) What does the ROM monitor want in the way of modem control signals?
   Can I make it happy with just pins 2/3/7 (TD, RD, signal ground)?

4) Presumably the ROM talks to the first of the serial ports? At 9600 baud?

-- Jerry "waiting for the $#@ 74AS1004As" Callen
   jcallen@encore.com
   (508) 460-0500 (work)
   (617) 876-5330 (home)

From owner-pc532%daver@mips.com Tue Mar 20 05:11:45 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: mea@mea.utu.fi (Matti Aarnio)
Subject: Re: Disk drive power requirements
To: pc532@daver.bungi.com
Date: Tue, 20 Mar 90 8:31:30 EET
X-Mailer: ELM [version 2.2 PL10]
Status: O

Hello,

	I have been looking boxes for pc532, and also wondering how to
boot the machine so that reasonable 200W power supply is enough.

	On average +12V is available for about 8 amps - reasonable for
four SCSI hard disks on run.  However on boot (at least CDC WREN series)
they are specified to draw up to 4.5A for up to 30 secs.

	With second hard disk we need a power up sequencer.
(timers & relays...)  -- Have you ever been around to do complete power up
cycle for really large IBM mainframe system ? (From quiet hall to full blast
90+ dB noise... :-)

	Gives the feel of BIG system ;-)
Conventional approach is propably to use more powerfull +12V supply specified
by peak demand, but why ?   Still, 1.7A+1.7A+4.5A = 7.9A, 3 disks is max.

	/Matti Aarnio <mea@mea.utu.fi> OH1MQK


From owner-pc532%daver@mips.com Tue Mar 20 05:14:23 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: pp@prosys.se
Date: Tue, 20 Mar 90 09:01:16 +0100
To: pc532@daver.bungi.com
Subject: Minix
Status: O

(I know you have worked alot with this project already...)

How is the work with Bruce's Minix going? I'm one of those not able to
pay $$$ for a "real" unix and still has the nerve to want sources.
The reason for asking is that I want to order Minix in time.

	This is a great project. It will be even greater when
	we have software. /pp

From owner-pc532%daver@mips.com Tue Mar 20 05:15:05 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: mea@mea.utu.fi (Matti Aarnio)
Subject: Re: SCSI
To: pc532@daver.bungi.com
Date: Tue, 20 Mar 90 11:31:36 EET
X-Mailer: ELM [version 2.2 PL10]
Status: O

> > It would be nice if we could set up an archive site for Unix
> > versions of these documents.  I'm willing to help out with converting
> > the files (my site has arc, and I've gotten hold of a unix unzipper).  
> > Anyone else interested in such a project?  
> 
> I am more than willing to make space available for things relevant to the pc532
> group on col.hp.com for anonymous ftp.  We are not capable of supporting uucp
> access for a variety of reasons, and we've not investigated running a mail
> based server, but for the ftp-capable world, we're quite accessible.

  Me too...  Actually contact  Mr  ojala@funic.funet.fi.
There we have several hundred MBytes of free disk space and anonymous FTP.
I will put mail server there as well - soon I hope.
(No uucp here either - and you wouldn't like trans-atlantic phone calls
 anyway.)

> I already have some of Bruce Culbertson's bits available, and now have floppy
> copies of much of the crud that was on beowulf, and will be making that
> available too.
> 
> Bdale

	/Matti Aarnio	<mea@mea.utu.fi> OH1MQK
			<mea@funic.funet.fi>

PS: My own - like all other finnish boards - are waiting for local dealer to
    deliver sockets and TTLs, and...


From owner-pc532%daver@mips.com Tue Mar 20 09:10:04 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Tue, 20 Mar 90 05:58:38 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: Minix
Status: O

[In the message entitled "Minix" on Mar 20,  9:01, pp@prosys.se writes:]
> 
> How is the work with Bruce's Minix going? I'm one of those not able to
> pay $$$ for a "real" unix and still has the nerve to want sources.
> The reason for asking is that I want to order Minix in time.

George build up a "tower" case over the weekend. The SCSI hard drive will
be coming off the ICM today (no failures, worked fine), and will go into
that case. The porting will continue in earnest at that point (I have
a binary to try - Bruce has alerted me to a number of potential problems,
though).



-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From owner-pc532%daver@mips.com Tue Mar 20 09:22:33 1990
Flags: 000000000001
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Tue, 20 Mar 90 06:08:50 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: Disk drive power requirements
Status: O

[In the message entitled "Re: Disk drive power requirements" on Mar 20,  8:31, Matti Aarnio writes:]
> 	With second hard disk we need a power up sequencer.
> (timers & relays...)  -- Have you ever been around to do complete power up
> cycle for really large IBM mainframe system ? (From quiet hall to full blast
> 90+ dB noise... :-)
> 

The Miniscribe drives have the sequencer built in - they will not spin up
(optionally) until they receive a "Start unit" SCSI command. In fact, you
can spin them down with a "Stop unit". The +12 drain is nominal until you
spin them up, as well. I'll kmore (about these units) after the manual I
ordered gets here...


-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From jap@proteon.com Tue Mar 20 14:25:10 1990
Flags: 000000000000
Date: Tue, 20 Mar 90 14:31:15 EST
From: jap@proteon.com (John A. Papadopoulos)
To: budd@bu-it.bu.edu
Subject: Re:  LED question
Status: O


Anode is the longer lead


	|-----------------------|
	|			|
	|	   |\ |		|
	|	___| \|__	|
	|	|  | /|	|	|
	|	|  |/ |	|	|
	|	|	|	|
	|	|	|	|
	|-----------------------|
		|	|
		|	|
		|	|
		|	|
	  anode	|	| cathode
		|	|
		|	
		|

From owner-pc532%daver@mips.com Tue Mar 20 15:21:02 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Re: clock termination, ports, ROM 
Date: Tue, 20 Mar 90 09:17:39 MST
From: Bdale Garbee <bdale@col.hp.com>
Status: O

> The closer I get to being ready to power up, the more questions I have.
> Here's my latest round.

Feeling on top of the world about just having turned on two boards, I'll try
to help...  :-)

>    couldn't come up with a way of installing the termination resistors that
>    didn't seem like a serious kludge. 

Standard kludge practice says put the 330 ohm in the two holes as normal, and
tack the 220 ohm to VCC on the back of the board.  Careful bending of the leads,
combined with careful placement of the resistor and careful soldering, will
allow a neat-looking back of the board hack, with no shorts.  If the board
layout ever has to be changed, another pair of holes for the second resistor
in each stack would be neat...

> 2) What's the pinout for a 9-pin AT-style serial port? I'm probably
>    going to initially just make a cable to go directly to the 25-pin
>    socket on the back of my terminal, but eventually I want to have
>    "proper" serial ports.

That's what I did.  I crimped ribbon cable in a 10-pin header, then fanned it
out and (kludge) crimped the fanned out pins into a DB25 in the right order
(ugly but it works for now).  This cute little book I have says:

	db9 pin		db25 pin

	1		8		DCD
	2		3		RX
	3		2		TX
	4		20		DTR
	5		7		GND
	6		6		DSR
	7		4		RTS
	8		5		CTS
	9		22		RI

The "trick", if there is one, is to remember that DB9's are wired 1-5 on one
side of the connector, and 6-9 on the other side, while 2x5 headers are
"traditionally" numbered odds on one side, evens on the other.  The pattern
you should use with the above numbering on the 2x5 headers is like:

	1	x.	6
	2	..	7
	3	..	8
	4	..	9
	5	..	N/C

> 3) What does the ROM monitor want in the way of modem control signals?
>    Can I make it happy with just pins 2/3/7 (TD, RD, signal ground)?

I made one of the above, which yields a DTE DB25 maile, then used a fem to 
fem cable that swapped 2/3 and connected 7, and it worked. 

> 4) Presumably the ROM talks to the first of the serial ports? At 9600 baud?

I assumed 9600-N-8-1, and it worked.  The lowest numbered 10-pin header, which
is the one nearest the CPU (inside row, farthest from the back of the board).

By the way, the monitor ROM as supplied appears to be good for little more than
making sure your console port is working, and dumping registers.  I'm chatting
with Bruce offline, he's working on the monitor now.  Someone will comment when
a version that works for non-trivial operations is available.

> -- Jerry "waiting for the $#@ 74AS1004As" Callen

I happened to have some in my junk box... along with the 1034's...

Any progress on a floppy controller?

Bdale

From owner-pc532%daver@mips.com Tue Mar 20 15:21:40 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Tue, 20 Mar 90 10:07:14 pst
From: Bruce Culbertson <culberts@hplwbc.hpl.hp.com>
To: pc532@daver.bungi.com
Subject: Re:  Minix
Status: O

> How is the work with Bruce's Minix going?

I have been working on the monitor for the last few weeks.  I haven't
touched pc532 Minix yet.  Having the monitor in good shape should
make working on Minix easier.

Bdale Garbee told me that he had serious problems with the monitor in
the EPROM he received with his pc532 kit.  Sorry about that.  An early
version Dave Rand cooked up did not have enough stack space.  (The
monitor uses a fair amount of recursion and, hence, a fair amount of
stack.)  I am assuming that Bdale received the version with too little
stack.  Presumably, everyone got the same damaged version.

I was already aware of another problem.  When the kits went out, we
had still not updated the monitor routine which switches contexts
between user code and monitor code.  The context switching routine in
your EPROM's is for my 32016, not the 32532.

Dave and George sent out the monitor, knowing that it had problems,
because they did not want to delay shipping your kits.  Also, they
assumed that most of you would be able to reprogram your EPROM's with
a better version which we could supply over the net.  We will have to
make special arrangements for those who do not have access to EPROM
programmers.

I have enlisted Bdale to test the current monitor since I still have
not set up the pc532 which George and Dave lent me.  I hope to set
mine up this week.

Last week I added and tested SCSI read, write, and "raw" commands for
the 32016 monitor.  This week I will merge them into the pc532 monitor
and get Bdale to test them.  When we have confidence in this version
of the monitor, I will post it so you can burn new EPROM's.  By the
way, my SCSI commands use the 8490, not the Adaptec.  I figure someone
else can write an Adaptec driver while I start in on Minix.

It would be nice to have a user manual for the monitor, although it
does have built in help.  Which would you rather have: a monitor user
manual or an earlier version of Minix?

I expect to have a little more free time now and a lot more starting
in May.  Hence, I expect to get Minix running sometime in May.  If
Dave beats me to it, so much the better.

Cheers,
Bruce

From owner-pc532%daver@mips.com Tue Mar 20 16:13:16 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Tue, 20 Mar 90 09:57:27 PST
X-Mailer: Mail User's Shell (6.5 4/17/89)
From: gs@vw25.chips.com (George Scolaro)
To: pc532@daver.bungi.com
Subject: Re: clock termination, ports, ROM
Status: O

[In the message entitled "clock termination, ports, ROM" on Mar 19, 15:15, Jerry Callen writes:]
 
>    didn't seem like a serious kludge. How are people doing this? I suppose I
>    could carefully shave down the leads on the 220/330 ohm resistors so
>    that I could stuff two in one hole. But there HAS to be a better way, eh?

Well, not really since the 220ohm (the pull up) isn't allowed for on the
board. I soldered mine under the board, to the nearest +5 (on the parity
latch pin 20 of 74as374) and to the BCLK side of the resistor. /BCLK doesn't
need any termination, it looked very clean on my boards (shorter trace than
the BCLK).

> 2) What's the pinout for a 9-pin AT-style serial port? I'm probably

Huh? Its on the schematics and in the Functional Description...

> 3) What does the ROM monitor want in the way of modem control signals?
>    Can I make it happy with just pins 2/3/7 (TD, RD, signal ground)?

Just TX,RX and ground.

> 4) Presumably the ROM talks to the first of the serial ports? At 9600 baud?

Yes, CONN3 at 9600 baud.

Maybe someone else that has got a board up by themselves (John C. Bdale?)
should post some of the steps that they took to run up their boards for those
that are yet to do so...

best regards,

-- 
George Scolaro
(try (pyramid|hoptoad|sun|vsi1)daver!vw25.chips.com!gs)

From owner-pc532%daver@mips.com Tue Mar 20 21:46:48 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: disk buy update and missing persons list
To: pc532@daver.bungi.com
Date: Tue, 20 Mar 90 12:22:55 PST
Cc: athos%eyrie@labtam.oz.au (David Burren)
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls (Karl Swartz)
Status: O

There is one person who had expressed interest in a disk who I
have not heard anything from since:

    eyrie!athos@labtam.oz.au (David Burren)

David, I only received one mail message from you, postmarked
the 14th, and haven't heard anything since.  If you still want
one of the drives please try to reach me somehow.  Since email
seems to be letting us down, try calling me at 1-408/223-1308
and at least leave a message telling me you want one.  If you
did not receive wire transfer info and I'm not home, call the
Bank of America at 1-415/853-4554 and ask for Marco Remedios.
He's the Assistant Manager and should be able to help you out.
Just tell him you need to wire money to Karl Swartz's account
and he should be able to go from there.

Also, I got a rather upset call from Cynthia at CSC earlier
today.  Evidently some called and said they knew about this
deal and the one that George got last week and wanted to get
one for $895.  Their price for single units is $1,095, they
gave us one last week at the lower price simply because it
was part of an order for over 40.  If you want *one* at $895
call me, not CSC.  If you want one directly from CSC, expect
to pay $1,095.  They are giving us a very nice deal (in more
ways than just monetary) and I don't want to get them mad at
us, especially since we very well may do another order for
tape drives.  (They have a very good deal on some, but more
about that after the dust settles from the disks.  Besides,
my wallet needs time to recuperate, and I know many other
folks feel the same way.)

Here is the list of orders.  The first column is the number of
drives desired, with a 'c' for confirmation and 'm' for orders
for which money has arrived.

   1c	kls@ditka.uucp (Karl Swartz)
   1cm	dlr@daver.bungi.com (Dave Rand)
   1cm	george@wombat.uucp (George Scolaro)
   1cm	rjohnson@kiwi.mpr.ca (Robbin Johnson)
   2c	taylor@think.com (David Taylor)
   2cm	johnc@manatee.uucp (John L. Connin)
   3c	bdale@col.hp.com (Bdale Garbee)
   1c	bdale@col.hp.com (Fred Schneider c/o Bdale Garbee)
   1cm	mark-geisert@l66a.ladc.bull.com (Mark Geisert)
   2c	budd@bu-it.bu.edu (Phil Budne)
   2c	pell@isy.liu.se (Pell Emanuelsson)
   1c	buck@siswat.lonestar.org (A. Lester Buck)
   1c	david@dogmelb.dog.oz.au (David Le Blanc)
   1cm	bob@arthur.wwu.edu (Bob Hayes)
   2cm	bobm@convex.com (Bob Miller)
   1cm	glowell@hpda.hp.com (Gary Lowell)
   2cm	loeliger@convex.com (Jon Loeliger)
   1	eyrie!athos@labtam.oz.au (David Burren)
   2cm	morris@chips.com (Morris Jones)
   1cm	night@pawl.rpi.edu (Trip Martin)
   1c	eyal@ucisae.isae.cancol.oz.au (Eyal Lebedinsky)
   2c	s861298@minyos.xx.rmit.oz.au (Marc A. Boschma)
   2c	s861019@minyos.xx.rmit.oz.au (George Seremetidis)
   4c	jto@tut.fi (Jarkko Oikarinen)
   1c	xrolfa@dna.lth.se (Rolf Andersson)
   1c	ojala@cs.hut.fi (Petri Ojala)
   1c	freb@goldfnch.mv.com (Karl Freburger)
   1c	jonathan@comp.vuw.ac.nz (Jonathan Stone)

An addition wire transfer came in from Sweden this morning for two
drives but I haven't gotten the name; I assume it's Pell's.

To save you the trouble of counting 'em yourself, that's a total of
41 confirmed drives!

Thanks all!

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Wed Mar 21 04:10:33 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Re: clock termination, ports, ROM 
Date: Tue, 20 Mar 90 17:23:16 MST
From: Bdale Garbee <bdale@col.hp.com>
Status: O

> Maybe someone else that has got a board up by themselves (John C. Bdale?)
> should post some of the steps that they took to run up their boards for those
> that are yet to do so...

Without going into too much (potentially boring) detail, after soldering in 
all the parts, and flux stripping, I powered up the board with no IC's 
installed, and checked voltages at various points.  5V on pins 7/14 of some of
the chips, power on the right pins of the 532 socket, +/12 in the right places
on the level shifters, etc.  Everything looked good.

Then I stuffed all the chips, made up a console cable, and plugged things in.
Turns out I forgot the 74xx14 for the reset circuit on the first pass, it's
over in the corner and somehow I didn't notice the socket.  Nothing smoked,
and it took me about 20 seconds to realize that wasn't there, so I powered
down, stuck a chip in, and powered back up.  Still nothing on the screen, but
no smoke, and none of the chips were obviously getting warm... so I grabbed
my scope and the first thing I checked was the 50Mhz oscillator, which was bad.
After swapping that as I've already related, the board came right up.

After Fred finished soldering in all the r's and c's on his board, we did the
same "no IC smoke test", and the voltages looked good.  Then we plugged in all
the ic's, including the ICU stolen from my board, and moved the console cable
over.  It came up and ran the first time.

Boring?  Nah... you should have been standing next to Fred when he bellowed
"YES!".

Bdale

From owner-pc532%daver@mips.com Wed Mar 21 04:12:34 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: gcc 1.37.1 and the ns32k (update)
Date: Wed, 21 Mar 90 01:46:22 EST
From: David Taylor <taylor@Think.COM>
Status: O

I got a patch to gcc 1.37.1 from rms and it now successfully cross
compiles itself on both a vax and a sun4.  The patch is short; here it
is -- replace the ashlsi3 pattern in ns32k.md with:

(define_insn "ashlsi3"
  [(set (match_operand:SI 0 "general_operand" "=g,g")
	(ashift:SI (match_operand:SI 1 "general_operand" "r,0")
		   (match_operand:SI 2 "general_operand" "I,rmn")))]
  ""
  "* return output_shift_insn (operands);")

David

From ames!zorch!ditka!kls@XN.LL.MIT.EDU Wed Mar 21 15:41:54 1990
Flags: 000000000000
Posted-Date: Wed, 21 Mar 90 12:03:08 PST
Subject: money for disks
To: budd@bu-it.bu.edu (Phil Budne)
Date: Wed, 21 Mar 90 12:03:08 PST
X-Mailer: ELM [version 2.2t PL7]
From: ames!ditka.UUCP!kls@XN.LL.MIT.EDU (Karl Swartz)
Status: O

Phil,

Your check for $1,824 arrived a few minutes ago.  I've got
the shipping address down now as

    Ship to:	Philip Budne
		58 Playstead Rd.
		Newton, MA 02158

Thanks!

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Wed Mar 21 20:13:02 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Wed, 21 Mar 90 15:50:12 PST
X-Mailer: Mail User's Shell (6.5 4/17/89)
From: gs@vw25.chips.com (George Scolaro)
To: pc532@daver.bungi.com
Status: O

[In the message entitled "" on Mar 21,  9:21, Sverre Froyen [PV930201] writes:]
> 
> (in addition to the sockets in the kit).  I am now debating with
> myself whether to socket anything else and would like to get some
> pros and cons.  Anyone?

I didn't socket any of the 74ASxxx, 74Fxxx or 74ALSxxx parts (except for the
74ALS6311 which I did). I also soldered all the resistor packs in. The
general rule I use is to not socket anything that would cost less than a
good quality machined socket, except of course things that can go pop, like
RS232 transceivers etc or devices that may need to be re-programmed
(obviously).

> 2 74AS258 (I bought Denver's entire supply of one)

Remember that you can use 74AS158's with the same timing margin.

> 1 74AS374 (I found a 74F374 -- will that do?)

Yes, that is fine, its only 1ns slower worst case (the timing margin is 15ns
worst case with a 74F374, i.e. more than enough!).

best regards,


-- 
George Scolaro
(try (pyramid|hoptoad|sun|vsi1)daver!vw25.chips.com!gs)

From owner-pc532%daver@mips.com Wed Mar 21 19:55:57 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Wed, 21 Mar 90 09:21:55 MST
From: sverre@lars.Seri.GOV (Sverre Froyen [PV930201])
To: pc532@daver.bungi.com
Status: O

Spent yesterday evening soldering in Rs, Cs, and sockets.  Only
bummer was that the connector strips I bought had pins too thick
for the holes on the board.

I have socketed all the PALs and GALs,
the 15406s, the oscillators, and the SCSI termination resistors
(in addition to the sockets in the kit).  I am now debating with
myself whether to socket anything else and would like to get some
pros and cons.  Anyone?

In addition to the parts I am expecting
>From Trip Martin I am still missing a couple:

2 74AS258 (I bought Denver's entire supply of one)
1 74AS374 (I found a 74F374 -- will that do?)
1 50MHz oscillator (I got a 40 MHz for now)

If anyone have extras of these, I can take them off their hands.

Sverre

From owner-pc532%daver@mips.com Thu Mar 22 01:08:34 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: a couple of small ns32k.md changes (gcc 1.37.1)
Date: Wed, 21 Mar 90 18:36:57 EST
From: David Taylor <taylor@Think.COM>
Status: O

Here's a copy of a message that I just sent to bug-gcc and rms
concerning a couple of small changes to ns32k.md to allow it to get
along with gas 1.35.

David

There are three lines in the gcc 1.37.1 file ns32k.md, that gas 1.35
doesn't like -- gas configured for the ns32k supports `#' as a comment
character at the beginning of a line, but it uses `|', not `#', as the
comment character within lines.

Here are the changes to use `|' when USE_GAS is defined.  Even simpler
would be to remove the comments, but I felt that they were useful, so I
left them.

RCS file: RCS/ns32k.md,v
retrieving revision 1.6
diff -c -r1.6 ns32k.md
*** /tmp/,RCSt1019710	Wed Mar 21 18:19:37 1990
--- ns32k.md	Wed Mar 21 18:10:51 1990
***************
*** 810,818 ****
--- 810,826 ----
    "*
  {
    if (INTVAL (operands[0]) == 8)
+ #if defined(USE_GAS)
+     return \"cmpd tos,tos | adjsp -8\";
+ #else
      return \"cmpd tos,tos # adjsp -8\";
+ #endif
    if (INTVAL (operands[0]) == 4)
+ #if defined(USE_GAS)
+     return \"cmpqd %$0,tos | adjsp -4\";
+ #else
      return \"cmpqd %$0,tos # adjsp -4\";
+ #endif
    if (INTVAL (operands[0]) < 64 && INTVAL (operands[0]) > -64)
      return \"adjspb %$%n0\";
    else if (INTVAL (operands[0]) < 8192 && INTVAL (operands[0]) >= -8192)
***************
*** 1932,1938 ****
--- 1940,1950 ----
        else
  	output_asm_insn (\"movzbd 3(sp),%0\", operands);
      }
+ #if defined(USE_GAS)
+   return \"cmpqd %$0,tos | adjsp -4\";
+ #else
    return \"cmpqd %$0,tos # adjsp -4\";
+ #endif
  }")
  
  (define_insn ""
--
David Taylor
taylor@think.com, ...{ames,bloom-beacon,harvard}!think!taylor

From taylor@Think.COM Thu Mar 22 11:55:02 1990
Flags: 000000000000
To: budd@bu-it.bu.edu (Phil Budne)
Cc: pc532@daver.bungi.com
Subject: Re: a couple of small ns32k.md changes (gcc 1.37.1) 
Date: Thu, 22 Mar 90 11:52:33 EST
From: David Taylor <taylor@Think.COM>
Status: O

<Date: Thu, 22 Mar 90 01:16:45 EST
<From: budd@bu-it.bu.edu (Phil Budne)

<Earler this week you mentioned you had gcc cross compiling itself
<on vaxen and sun4.  Does that include gas and gnu-ld?

It includes gas; it doesn't include gnu ld.  I haven't tried gnu ld,
yet.  I've heard from two people that it doesn't work for the ns32k.

One specific problem that was mentioned was immediate operands.  It's
unclear to me why you need to worry about immdiate operands -- do you
really need to fix them up at link time?  Isn't it sufficient to say
that they have to be know at assembly time and let the assembler worry
about them?

In any case, I haven't (yet) worried about the gnu ld.  I'm hoping that
someone else has figured out the changes and will post them to either
this mailing list or to bug-gnu-utils.  The vax ld is able to link
things without complaint; I don't, however, know if it *correctly* links
things.  If the gnu ld proves unusable, there's always Bruce
Culbertson's ld.  (But, I don't think Bruce's ld supports stabs (i.e.
debugger symbols).  Bruce?)

BTW, the when running gcc on the vax it doesn't correctly handle
floating point arithmetic as I haven't defined the various REAL
ARITHMETIC macros.  One of the reasons why I wanted to get gcc running
as a cross compiler on a sun is the hope that I won't have to sit down
and define the macros -- suns, like the ns32k, use ieee format floating
point.  But, then the byte ordering is wrong...

If anyone has done the necessay work to get gcc to support ieee
arithmetic on the vax, I'd like to know about it.

Gas 1.35 produces byte for byte identical output when run on a vax as
when run on a sun.

David

From owner-pc532%daver@mips.com Thu Mar 22 14:15:18 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
X-Mailer: Mail User's Shell (6.2 5/11/88)
To: pc532@daver
Subject: debug doc.
Date: 22 Mar 90 08:42:24 PST (Thu)
From: george@wombat.bungi.COM (George Scolaro)
Status: O

Hi folks, 
	the following is an attempt to generate a debug document for the
pc532. As can be imagined it is difficult to cover all possible problems,
especially ones that haven't yet occurred. Expect (I hope not) that this
document will grow as we get more feedback (problems?). Thanks to John C.
for some of the material.


In outline form:

Materials needed:
-----------------

1).  Assembled pc532 without IC's installed and without BCLK terminators
     installed.
2).  IC's.
3).  PC power supply.
4).  Terminal / terminal emulator.
5).  Terminal cable(s) 
     (eg. 10 pin header -> 10 D-sub -> 10 to 25 pin adapter -> 25 pin cable)

Optional/essential materials:
-----------------------------

1).  RS-232 break-out box.
     (To facilate swapping connections and to provide visual indicator of
     line state).
2).  Logic probe. If you are running at 25MHz, then the logic probe better
     be able to resolve 20ns wide pulses of better.
3).  Multimeter.
4).  Oscilliscope (the higher the bandwidth better, 100MHz more than
     adequate for checkout). Even a 35MHz scope is better than none.
5).  Logic Analyser?

Support equipment checkout:
---------------------------

1).  Verify rs-232 cabling results in desired connections.
2).  Verify terminal / terminal emulator is functioning.
3).  Verify power supply voltages.  
4).  Verify power supply connector cabling.

Note: Many PC/XT/AT powersupplies (switching supplies) will not operate
correctly without a load. In fact many will not operate without a reasonable
load on the +12V supply. I usually use an old floppy/harddisk as a load.

Prime equipment (ie pc532) checkout:
------------------------------------

1).  Solder in all resistors/capacitors/sockets/connectors. Take extreme care
     in orienting the PGA and PLCC sockets correctly. The correct orientation
     is silkscreened on the top of the PCB. If you solder the PLCC sockets in
     incorrectly, you are in real trouble!

1a). After soldering in all resistors/capacitors/connectors etc, but before
     inserting any integrated circuits, measure the resistance from +5 to
     ground. You should not have a short circuit (!), the resistance should
     be roughly 11 ohms (due to the terminator resistors, 4 packs x 12
     effective 550 ohm resistors in parallel across the +5/Gnd. Verify that
     there are no shorts between +/-12 and +5/Gnd.

1b). Sanity check, without chips, apply power and check voltages.
     Make sure the two power connectors are not interchanged before
     applying power (eg. black wires on each connector are adjacent, this
     means that the black wires (all of them) are in the middle of the
     connector).

2).  Insert all chips, except for the parity PAL U20.

3).  Inspect all chips to make sure the pins are properly seated.
     Make sure the PGA devices are fully seated.  Double check that
     the ring on certain PGA pins is level with the surface of the
     socket.
     (This one bit me. I did not have the 32532 fully seated and as a
     result one or more of the 175 pins were intermittent).

4).  Insert SIMM's.  Closely inspect the seating of each device.
     Make sure the SIMM's are at 90 degrees to the motherboard and
     the contact fingers are fully engaged in the socket.

     If you have 8 Mbytes of RAM, my recommendation is to start with
     4 Mbytes.  The theory being that it is easier to inspect for 
     proper seating and there are 4 fewer items to cause trouble.

     With 4 Mbytes, connector positions U6, U8, U10, and U12 should
     be occupied.

5).  Configure jumpers.     

	With 4 Mbytes (ie: 4 SIMM's of 1M x 9)

	J1 - jumper between pin 2 and pin 3
        J2 - jumper between pin 2 and pin 3
        J3 - open (shorting resets the hardware)

6).  Smoke test, apply power, re-measure power supply voltages.

7).  The LED's should glow. If not, the ROM code did not execute.

8).  Connect terminal and verify ROM Monitor operation.
     The terminal connects to CONN3, and the terminal should be
     configured for 9600-N-8.  
	
9).  Install parity PAL (if you have x9 DRAM SIMMS) and re-verify operation.

10). If you have 8 Mbytes of RAM, install remaining SIMM's.

10a). Re-verify  operation.

11).  Install BCLK terminators.

12).  Re-verify operation.

     
Misc thoughts, in case of trouble:
----------------------------------
1)   Lower the CPU clock frequency (eg 25Mhz module) by changing out the 
     osillator in U25.

     This should eliminate any possible time delay problems (eg, using
     lower speed parts) and make it easier to scope for vital signs.

2)   Verify vital signs with a scope.

---------------

Following are some discussions over a dead pc532:

Still trying to debug this thing. In answer to your first query, there's
no chip select signal going to the ICU (and thus no refresh signal either).

	The supplied monitor will program the ICU to generate a 30usec
	square wave on the counter output of the ICU. This operation is
	performed in the first few instruction of the monitor (before any
	DRAM/DUART/SCSI operations). If this step fails then something very
	drastic is wrong (and basic).

I checked all 8 data lines coming from the EPROM and there does appear to
be data coming from them. Same with the data pins of the 32532 and
the output from the 646 (if there's data on the CPU pins I assume that it's
coming back..) Anyway, I noticed something that may or may not be
important and I figured I'd ask about it..

We were examining the clock outputs and noticed that we were getting BCLK
>From the CPU but not /BCLK. I'm not sure of C23 is bad and is dragging it
down or if it's just not coming from the CPU at all. Is this normal?

	BCLK and /BCLK come from the CPU, they are always present,
	even during reset. There must be a short circuit somewhere, find it.
	/BCLK is used (among other places) to clock /DDIN through U26 to
	form /DDINL. /DDINL is used (among other places) to control the
	direction of U43 (the 74AS646) which buffers all data to and from
	all 8 bit devices (including the EPROM). If /DDINL is stuck high,
	because /BCLK is missing, then U43 will always drive data to the
	peripherals even if a read is in progress, and visa-versa.

Like I said, the EPROM does appear to be getting addresses and does appear
to be getting data (if lots of indecipherable staircase signals == ADDRESS/DATA
signals, that is) back to the CPU. That's all I've managed to figure
out so far (help from the hardware hackers has not yet materialized).

On a similar note, the clock signal from the 20MHz crystal appears to
be 1/2 the amplitude of the 50Mhz clock. Also normal? I noticed this while
checking the termination resistors and seeing that I had soldered one of the
220 Ohm guys to pin 6 (+V) of the 74F138 which was only +2VDC. I said "Hmmmm.

	Wrong. +V is a pullup in RES13. You must connect to +5V directly.

The spec does say 2VDC min for that guy, maybe I'd better solder this guy
to somebody who explicitly claims to be 5VDC instead of this pin. I then
re-soldered it to the VCC of the 74AS1034 and got thereafter 5VDC on
pin 6 of the 74F138 as well! The 20Mhz clock signal stayed at its previous
amplitude.

	The 20MHz clock should reach at least the minimum high for TTL,
	i.e. it must get to at least 2.4V, I would suspect that the module
	is faulty, since the only load is the AIC6250.

------

Hi,
	well let me just mention the initial things you should check for,
we'll get more complicated as necessary:

The software in the EPROM attempts to

1) program the ICU for the refresh, you should see 30usec (approx) square
wave coming from Pin 29 of the ICU (U46).

2) Jump to the high EPROM address from the 0 address and then program the
ICU to assert the SWAP signal low (should be high at reset). SWAP comes from
pin 11 of U46.

3) Program the AIC6250 SCSI chip to assert all the LEDs (i.e. all LED outputs
go low, lighting the LEDs). All 8 LED signals should go low, for the 4 LEDs
on the board + the 4 on CONN2.

4) The DUART gets programmed etc etc.

So, the first thing to check is whether the ICU gets selected after reset,
i.e. pin 21 of U46 should blip low. If this happens then you should see
the 30usec square wave. If you have got this far then the EPROM must be
basically working (email me if you get this far).
If the ICU never gets blipped then you have a real basic problem with the
data getting to the CPU. The things to check are that all the data lines from
the EPROM get to the 74AS646 and from there to the CPU. Make sure that the
74AS646 is actually functional.

Also check that the DEC32 pal is outputting the right signals. You should
see /EPROM being asserted and also /SLOW and /SLOWS which controls the gating
of data via the 74AS646. To check the gating controls of data from 74AS646,
the /DDINL signal from U26 should be mostly low (for read), but it should
blip high (especially after each reset, since the 32532 writes to the ICU,
then the SCSI and then the DUART) and /PERG from U58/B should be low to gate
the data on via U43. /PERG is also used to inform the 32532 that the current
address refers to an 8 bit device (via the BW0,BW1 inputs of the 32532).
/PERG should always be low for any peripheral select, the DRAM being the
only 32 bit device.

Also if /EPROM and /RD are both asserted but the /NRDY (pin 13 U38) is stuck
low (after reset) then the WAIT pal is doing something screwy. /NRDY is the
not ready for peripherals and /NRDYR is the not ready for the DRAM. They
get or-ed/inverted by U30/A to form the /RDY for the 32532, i.e. when /RDY
is low the 32532 can finish the bus cycle and go on to the next one.

I have high confidence with the PALS since I ran test vectors through all of
them (took a long time!!!). Similarly with the EPROM.

Also make sure that RES13 (the 4.7kohm pull up dip) is plugged in the right
way, and that BCLK and /BCLK are both toggling (they are the clocks coming
>From the CPU that go to the rest of the system).

Basically all that needs to work to get the ICU to generate the square wave
is:

	U35, U30/A, U25, U44, U46, U37, U38, U42/A/B, U43, U58/B, U39,
U45 and U50.

The /A etc is the gate number.

 U45 buffers the low address lines from the 32532 to drive all the peripheral
address selects (for the internal registers within the peripherals).

Anyhow, try that and we'll see if we can track the problem down a step at
the time.

best regards,

-- 
George Scolaro
george@wombat.bungi.com                [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Thu Mar 22 14:52:51 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Date: Thu, 22 Mar 90 09:26:08 MST
From: Bdale Garbee <bdale@col.hp.com>
Status: O

> I didn't socket any of the 74ASxxx, 74Fxxx or 74ALSxxx parts (except for the
> 74ALS6311 which I did). I also soldered all the resistor packs in. The
> general rule I use is to not socket anything that would cost less than a
> good quality machined socket, except of course things that can go pop, like
> RS232 transceivers etc or devices that may need to be re-programmed
> (obviously).

I went a bit overboard this time.  Since I didn't have to pay for the socket
strips, I did all the dip packages.  Resistor packs and everything.  Fred I
think appreciated this since he's a pretty novice solderer, and this lowered
the danger of his having to remove IC's from a multi-layer board... I do it
all the time, but...

Normally, I have all the IC's wave-soldered except expensive VLSI, EPROM's, and
I/O transceivers... but since I may want to hack things on later, being able
to extract an IC, bend a pin out, etc...

Whatever you do, *DONT* use cheap sockets.  They are far worse than no sockets.

Bdale

From owner-pc532%daver@mips.com Thu Mar 22 14:55:58 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Thu, 22 Mar 1990 22:06:58 +1000
From: ian@sibyl.eleceng.ua.oz.au
To: pc532@daver.bungi.com
Subject: gcc 1.37.1 and the ns32k (update)
Status: O

David Taylor writes:
 > I got a patch to gcc 1.37.1 from rms.

Thanks, it is a moving target. I am just re building the whole thing
to check before I post the patches for the whole thing.

I have got gcc able to pass it's stage 2 verification in two versions,
one which uses the native assembler and loader and one which uses gas
and the gnu loader. I have successfully had the native version passing
this test since 1.31 or so.

The gnu loader needed quite a few changes to support the 32k, but I am
pretty happy with it now.

I am just cleaning everything up and checking that those latest
patches you sent me didn't break anything and will make it all
(patches to gcc, gdb, gas and binutils) available for anonymous ftp
tomorrow.


From att!oucsace!oucsboss!Sun.COM!daver!owner-pc532 Thu Mar 22 22:28:49 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: budd@bu-it.bu.edu (Phil Budne)
Cc: pc532@daver.bungi.com
Subject: Re: a couple of small ns32k.md changes (gcc 1.37.1) 
Date: Thu, 22 Mar 90 11:52:33 EST
From: David Taylor <taylor@Think.COM>
Status: O

<Date: Thu, 22 Mar 90 01:16:45 EST
<From: budd@bu-it.bu.edu (Phil Budne)

<Earler this week you mentioned you had gcc cross compiling itself
<on vaxen and sun4.  Does that include gas and gnu-ld?

It includes gas; it doesn't include gnu ld.  I haven't tried gnu ld,
yet.  I've heard from two people that it doesn't work for the ns32k.

One specific problem that was mentioned was immediate operands.  It's
unclear to me why you need to worry about immdiate operands -- do you
really need to fix them up at link time?  Isn't it sufficient to say
that they have to be know at assembly time and let the assembler worry
about them?

In any case, I haven't (yet) worried about the gnu ld.  I'm hoping that
someone else has figured out the changes and will post them to either
this mailing list or to bug-gnu-utils.  The vax ld is able to link
things without complaint; I don't, however, know if it *correctly* links
things.  If the gnu ld proves unusable, there's always Bruce
Culbertson's ld.  (But, I don't think Bruce's ld supports stabs (i.e.
debugger symbols).  Bruce?)

BTW, the when running gcc on the vax it doesn't correctly handle
floating point arithmetic as I haven't defined the various REAL
ARITHMETIC macros.  One of the reasons why I wanted to get gcc running
as a cross compiler on a sun is the hope that I won't have to sit down
and define the macros -- suns, like the ns32k, use ieee format floating
point.  But, then the byte ordering is wrong...

If anyone has done the necessay work to get gcc to support ieee
arithmetic on the vax, I'd like to know about it.

Gas 1.35 produces byte for byte identical output when run on a vax as
when run on a sun.

David

From owner-pc532%daver@mips.com Thu Mar 22 20:43:28 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Thu, 22 Mar 90 16:44:03 EST
From: Jerry Callen <jcallen@maxzilla.encore.com>
To: pc532@daver.bungi.com
Subject: Intel-based floppy controller
Status: O

Well, I give up. the HD64180 is proving to be hard to get and expensive
(at least $30), so I'm dumping it in favor of an, er, well, ah, an Intel
chip. (cough, choke....)  It seems likely that the floppy controller will
contain an 80C188, clocked at (at least) 10 MHz, maybe 16, if the price
isn't too high. The chip divides this by two, so the system clock will 
be 5 (or maybe 8) MHz. I can easily get the 10MHz part for $15, I don't
know yet about the 16 MHz part.

I have to admit that the on-board chip selects are nice. The 80C188 also
has DRAM refresh logic (missing on the 80188) and a pair of DMA channels.
I'll have to add a serial port, though. I don't yet know what this does
to the memory system, but I suspect the eventual configuration will be:

	80C188 (CPU)
	DP8490 (SCSI)
	DP8473 (floppy)
	8255 (parallel port)
	8-32K EPROM
	32-96K SRAM
	0-512K DRAM
	some serial chip
	glue logic

Not too different from the 64180 system, really. Most of my work to this point
is now obsolete; oh, well.

SO - anyone know of any free/cheap 80x86 tools (C, assembler) for either
Unix or a Macintosh?

-- Jerry "eating my words isn't a very tasty lunch" Callen
   jcallen@encore.com
   (508) 460-0500 (work)
   (617) 876-5330 (home)

From owner-pc532%daver@mips.com Fri Mar 23 00:56:04 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 12:32:47 +0930
From: idall@augean.ua.OZ.AU (Ian Dall)
To: pc532@daver.bungi.com, taylor@Think.COM,
        mason%tmsoft%munnari.oz@uunet.uu.net, meissner@osf.org
Subject: GCC, GDB, GAS and binutils for the ICM3216 and other NS32k Systems
Status: O


This is the README file describing the patches I have made available (or will
have in about 2 hours!).

-----------------------------------------------------------------------------
		GCC, GDB, GAS and GLD for the ICM3216

This directory contains patch files to make GCC, GDB, GAS and GLD work
for the ICM3216. Some of the changes are to get around operating
system peculiarities and others are enhancements. The patches enable
building either native coff format executables or the FSF's
coff-encapsulated-a.out format.

RMS has said that he is not interested in maintaining seperate
configurations for "obscure" computers --- by implication the icm3216
is obscure :-). He will accept fixes which are generic to all 32k
systems, but as I don't have an Encore and a Sequent, I sometimes have
difficulty convincing him that my enhancements *are* generic.  Also,
even when RMS *has* accepted something as a good idea, *and* I've
signed over the copyright as requested, it *still* seems to be no
guarantee that it will actually get into the distribution. I have no
idea why that is. Maybe somethings just get lost? Anyway, for all
those reasons, I am maintaining this archive for Ns32k users. These
changes may or may not make it into future FSF distributions.

I welcome corrections/bug reports.

	     Applicability to non ICM3216, Ns32k systems.

The icm3216 is a fairly basic (but very functional) machine based on
the ns32016 cpu.  The patches here are all for the NS Sys V.2.2
operating system although many of the changes are more widely
applicable. In particular, if you are using GAS and GLD, there should
be very little which would need to be changed to run on a BSD system.

			How to Get

The follwowing files are available in the gnu/ns32k directory of the
public area on augean.eleceng.ua.au:

README:		This file

INSTALL.Z	Details on how to apply the patches, configure and make the
		programs.

gcc.1.37.1.patch.Z
		Compressed patches for gcc 1.37.1

gdb.1.35.patch.Z
		Compressed patches for gdb 1.35

gas.1.35.patch.Z
		Compressed patches for gas 1.35

binutils.patch.Z
		Compressed patches for the GNU binutils package, including
		the loader and robotussin.

They are accessable by anonymous ftp to augean.eleceng.ua.oz.au.

ACSnet users can fetchfile from augean.eleceng.ua.oz. Eg

  "fetchfile -daugean.eleceng.ua.oz gnu/ns32k/README"

should get you this file.
---------------------------------------------------------------------------

Ian Dall


From owner-pc532%daver@mips.com Tue Mar 20 15:21:40 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Tue, 20 Mar 90 10:07:14 pst
From: Bruce Culbertson <culberts@hplwbc.hpl.hp.com>
To: pc532@daver.bungi.com
Subject: Re:  Minix
Status: O

> How is the work with Bruce's Minix going?

I have been working on the monitor for the last few weeks.  I haven't
touched pc532 Minix yet.  Having the monitor in good shape should
make working on Minix easier.

Bdale Garbee told me that he had serious problems with the monitor in
the EPROM he received with his pc532 kit.  Sorry about that.  An early
version Dave Rand cooked up did not have enough stack space.  (The
monitor uses a fair amount of recursion and, hence, a fair amount of
stack.)  I am assuming that Bdale received the version with too little
stack.  Presumably, everyone got the same damaged version.

I was already aware of another problem.  When the kits went out, we
had still not updated the monitor routine which switches contexts
between user code and monitor code.  The context switching routine in
your EPROM's is for my 32016, not the 32532.

Dave and George sent out the monitor, knowing that it had problems,
because they did not want to delay shipping your kits.  Also, they
assumed that most of you would be able to reprogram your EPROM's with
a better version which we could supply over the net.  We will have to
make special arrangements for those who do not have access to EPROM
programmers.

I have enlisted Bdale to test the current monitor since I still have
not set up the pc532 which George and Dave lent me.  I hope to set
mine up this week.

Last week I added and tested SCSI read, write, and "raw" commands for
the 32016 monitor.  This week I will merge them into the pc532 monitor
and get Bdale to test them.  When we have confidence in this version
of the monitor, I will post it so you can burn new EPROM's.  By the
way, my SCSI commands use the 8490, not the Adaptec.  I figure someone
else can write an Adaptec driver while I start in on Minix.

It would be nice to have a user manual for the monitor, although it
does have built in help.  Which would you rather have: a monitor user
manual or an earlier version of Minix?

I expect to have a little more free time now and a lot more starting
in May.  Hence, I expect to get Minix running sometime in May.  If
Dave beats me to it, so much the better.

Cheers,
Bruce

From owner-pc532%daver@mips.com Fri Mar 23 02:44:51 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 15:36:50 +0930
From: idall@augean.ua.OZ.AU (Ian Dall)
To: pc532@daver.bungi.com
Subject: Re: GCC, GDB, GAS and binutils for the pc532
Status: O


Might I suggest we use this version of these programs as a base for
tools for the pc532 development. I have taken care to isolate the SysV
dependent bits.  (Once you are using gnu loader and assembler there
are not that many system dependancies left).

Gas tended to have sequent dependent brain damage built into it. I
have made it so that the default is what I consider a pretty clean
implimentation and sequent compatability only happens if you make the
appropriate predefines.

It should nearly all work in a cross development environment. GAS and
GCC try to be independent of byte order of the running machine. LD
made no such attempt. The bits I added to ld should be endian
independent, (which means that the text and data should get relocated
properly) but I think that the reading and writing of the headers will
stuff up on a big-endian machine.

If anyone wants to make useful contribution, writing gnulib in
assembler (or in C with GCC style asm statements) would free us from
the only step still requiring proprietry code. GNU lib must currently
be compiled using a machines native assembler. It is a fairly small
library containing functions to do certain type conversions. It might
be cheating a bit, but I suppose I could start by running cc -S to get
the first assembler version.

Anyway, I suspect that this is the only complete set (including a
loader) of free tools available. Further more, it is a big comfort
to me to know that the same (or very similar) version demonstrably
works on another system (the icm3216).

Ian Dall.

From owner-pc532%daver@mips.com Fri Mar 23 02:44:51 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 15:01:11 +0930
From: idall@augean.ua.OZ.AU (Ian Dall)
To: pc532@daver.bungi.com, taylor@Think.COM,
        mason%tmsoft%munnari.oz@uunet.uu.net, meissner@osf.org
Subject: Re: GCC, GDB, GAS and binutils for the ICM3216 and other NS32k Systems
Status: O


There might have hve been some confusion over the correct internet address
for this site after reading my message describing these patches.

I corrected one instance of the address and not another.

The best address to use is

   augean.ua.oz.au

If you get really stuck use 129.127.4.2

Ian Dall

From owner-pc532%daver@mips.com Fri Mar 23 02:44:57 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: owner-pc532%daver@Sun.COM
Reply-To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 12:32:47 +0930
>From: idall@augean.ua.OZ.AU (Ian Dall)
To: pc532@daver.bungi.com, taylor@Think.COM,
        mason%tmsoft%munnari.oz@uunet.uu.net, meissner@osf.org
Subject: GCC, GDB, GAS and binutils for the ICM3216 and other NS32k Systems
Status: O


This is the README file describing the patches I have made available (or will
have in about 2 hours!).

-----------------------------------------------------------------------------
		GCC, GDB, GAS and GLD for the ICM3216

This directory contains patch files to make GCC, GDB, GAS and GLD work
for the ICM3216. Some of the changes are to get around operating
system peculiarities and others are enhancements. The patches enable
building either native coff format executables or the FSF's
coff-encapsulated-a.out format.

RMS has said that he is not interested in maintaining seperate
configurations for "obscure" computers --- by implication the icm3216
is obscure :-). He will accept fixes which are generic to all 32k
systems, but as I don't have an Encore and a Sequent, I sometimes have
difficulty convincing him that my enhancements *are* generic.  Also,
even when RMS *has* accepted something as a good idea, *and* I've
signed over the copyright as requested, it *still* seems to be no
guarantee that it will actually get into the distribution. I have no
idea why that is. Maybe somethings just get lost? Anyway, for all
those reasons, I am maintaining this archive for Ns32k users. These
changes may or may not make it into future FSF distributions.

I welcome corrections/bug reports.

	     Applicability to non ICM3216, Ns32k systems.

The icm3216 is a fairly basic (but very functional) machine based on
the ns32016 cpu.  The patches here are all for the NS Sys V.2.2
operating system although many of the changes are more widely
applicable. In particular, if you are using GAS and GLD, there should
be very little which would need to be changed to run on a BSD system.

			How to Get

The follwowing files are available in the gnu/ns32k directory of the
public area on augean.eleceng.ua.au:

README:		This file

INSTALL.Z	Details on how to apply the patches, configure and make the
		programs.

gcc.1.37.1.patch.Z
		Compressed patches for gcc 1.37.1

gdb.1.35.patch.Z
		Compressed patches for gdb 1.35

gas.1.35.patch.Z
		Compressed patches for gas 1.35

binutils.patch.Z
		Compressed patches for the GNU binutils package, including
		the loader and robotussin.

They are accessable by anonymous ftp to augean.eleceng.ua.oz.au.

ACSnet users can fetchfile from augean.eleceng.ua.oz. Eg

  "fetchfile -daugean.eleceng.ua.oz gnu/ns32k/README"

should get you this file.
---------------------------------------------------------------------------

Ian Dall


From owner-pc532%daver@mips.com Fri Mar 23 04:56:03 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: mea@mea.utu.fi (Matti Aarnio)
Subject: Re: GCC, GDB, GAS and binutils for the ICM3216 and other NS32k Systems
To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 9:26:18 EET
X-Mailer: ELM [version 2.2 PL10]
Status: O

> This is the README file describing the patches I have made available (or will
> have in about 2 hours!).
> 
> -----------------------------------------------------------------------------
> 		GCC, GDB, GAS and GLD for the ICM3216
...
> They are accessable by anonymous ftp to augean.eleceng.ua.oz.au.
> 
> ACSnet users can fetchfile from augean.eleceng.ua.oz. Eg
> 
>   "fetchfile -daugean.eleceng.ua.oz gnu/ns32k/README"
> should get you this file.

  Hmm.  I tried.  Its  pub/ns32k/README (et.al.)
FYI:  I snatched a copy of them into FUNIC.FUNET.FI -- all finns take a note!
  Anonymous FTP: pub/gnu/unsupported/ns32k.mods -directory

> ---------------------------------------------------------------------------
> 
> Ian Dall

	/Matti Aarnio	<mea@mea.utu.fi>
			<mea@funic.funet.fi>


From owner-pc532%daver@mips.com Fri Mar 23 04:56:35 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 03:26:29 EST
From: budd@bu-it.bu.edu (Phil Budne)
To: mason%tmsoft%munnari.oz@uunet.uu.net, meissner@osf.org,
        pc532@daver.bungi.com, taylor@Think.COM
Subject: Re:  GCC, GDB, GAS and binutils for the ICM3216 and other NS32k Systems
Status: O

I now have Ian's files (along with many other 32k goodies) in North
America.  Use anonymous ftp to BU.EDU (128.197.2.6) and look in
~ftp/users/budd/32k

ftp to Ozzie was pretty fast! Not worse than say FTP from coast to
coast was in 1980!

-Phil

Culbertson-32016/	Monitors/		tech-sheets/
DIR.augean.ua.oz.au	PC532/			tools32k/
DIR.isy.liu.se		README.isy.liu.se	tools32k.tar.Z
INDEX.beowulf		gnu/			unclean/

Culbertson-32016:
Header		Minix		memcspal	partlist
Header2		README		netlist		rfshpal
Mail		dramcpal	nmipal

Monitors:
apollo2.a32	catalog		chrss1.a32	srm.doc
apoltext.a32	chr3p3s.a32	splitr.bas	t1.a32
bu.bat		chr8251.a32	srm.a32		t2.a32

PC532:
Build-List	gcc-patch	noram.hex	schema/
DIR.isy.liu.se	gcc-patch2	pals/		scsi/
bruce/		gcc-patch3	pcbinfo/

PC532/bruce:
download.c	modtab.c	scsi.c		scsi.hdr	scsi_hd.c

PC532/pals:
DEC32.DOC.Z	DRAMEN.DOC.Z	PARITY.JED.Z	SCSI.PLD.Z
DEC32.JED.Z	DRAMEN.JED.Z	PARITY.PLD.Z	WAIT.DOC.Z
DEC32.PLD.Z	DRAMEN.PLD.Z	SCSI.DOC.Z	WAIT.JED.Z
DRAMC.PLD.Z	PARITY.DOC.Z	SCSI.JED.Z	WAIT.PLD.Z

PC532/pcbinfo:
532.TXT		532INFO.TXT

PC532/schema:
532.P01.Z	532.P04.Z	532.P07.Z	532.P10.Z
532.P02.Z	532.P05.Z	532.P08.Z	LOCAL.LBR.Z
532.P03.Z	532.P06.Z	532.P09.Z

PC532/scsi:
README		asc/		spc/		util.doc

PC532/scsi/asc:
README		asccom.lib	ascstruc.lib	constant.h	util.lib
asc.c		ascrot.lib	check.lib	stoprint.c

PC532/scsi/spc:
README		commands.h	easio.src	printer.src	scsi.c
arbitrat.lib	const.h		easisym.src	prnsym.src	sym.h
command.lib	dma.lib		print.lib	process.lib

gnu:
DIR.augean.ua.oz.au	butils.patch.Z		gdb.patch.Z
INSTALL.Z		gas-patch.Z
README			gcc.patch.Z

tech-sheets:
00MANIFEST	32016s.bug	32082m.bug	32332c.bug	32532b3.bug
00README	32032f.bug	32082n.bug	32332d.bug	32580a.bug
32008c.bug	32032g.bug	32201c.bug	32381b1.bug	32c016e.bug
32008d.bug	32032h.bug	32202e.bug	32381b2.bug	32c016f.bug
32008e.bug	32081d.bug	32202f.bug	32381c.bug	32c032a.bug
32016m.bug	32081e.bug	32202g.bug	32532a1.bug	32c201b.bug
32016n.bug	32081f.bug	32203c.bug	32532a2.bug	32c201c.bug
32016r.bug	32081h.bug	32203d.bug	32532b1.bug	32cg16a.bug
32016rt.bug	32082l.bug	32203f.bug	32532b2.bug	32cg16b.bug

tools32k:
as_dist/	include/	ld_dist/	utl_dist/

tools32k/as_dist:
Makefile	glob.h		list.c		phase1.c	pseudo.c
exp.c		init_in		main.c		phase2.c	util.c
glob.c		inst.c		mk_init.c	phase3.c	version

tools32k/include:
a.out.h		ar.h		conv.h		magic.h		ranlib.h

tools32k/ld_dist:
Makefile	ld.h		ld1.c		ld2.c

tools32k/utl_dist:
Makefile	ar.c		nm.c		ranlib.c

From taylor@Think.COM Thu Mar 22 11:55:02 1990
Flags: 000000000000
To: budd@bu-it.bu.edu (Phil Budne)
Cc: pc532@daver.bungi.com
Subject: Re: a couple of small ns32k.md changes (gcc 1.37.1) 
Date: Thu, 22 Mar 90 11:52:33 EST
From: David Taylor <taylor@Think.COM>
Status: O

<Date: Thu, 22 Mar 90 01:16:45 EST
<From: budd@bu-it.bu.edu (Phil Budne)

<Earler this week you mentioned you had gcc cross compiling itself
<on vaxen and sun4.  Does that include gas and gnu-ld?

It includes gas; it doesn't include gnu ld.  I haven't tried gnu ld,
yet.  I've heard from two people that it doesn't work for the ns32k.

One specific problem that was mentioned was immediate operands.  It's
unclear to me why you need to worry about immdiate operands -- do you
really need to fix them up at link time?  Isn't it sufficient to say
that they have to be know at assembly time and let the assembler worry
about them?

In any case, I haven't (yet) worried about the gnu ld.  I'm hoping that
someone else has figured out the changes and will post them to either
this mailing list or to bug-gnu-utils.  The vax ld is able to link
things without complaint; I don't, however, know if it *correctly* links
things.  If the gnu ld proves unusable, there's always Bruce
Culbertson's ld.  (But, I don't think Bruce's ld supports stabs (i.e.
debugger symbols).  Bruce?)

BTW, the when running gcc on the vax it doesn't correctly handle
floating point arithmetic as I haven't defined the various REAL
ARITHMETIC macros.  One of the reasons why I wanted to get gcc running
as a cross compiler on a sun is the hope that I won't have to sit down
and define the macros -- suns, like the ns32k, use ieee format floating
point.  But, then the byte ordering is wrong...

If anyone has done the necessay work to get gcc to support ieee
arithmetic on the vax, I'd like to know about it.

Gas 1.35 produces byte for byte identical output when run on a vax as
when run on a sun.

David

From att!oucsace!oucsboss!Sun.COM!daver!owner-pc532 Thu Mar 22 22:28:49 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: budd@bu-it.bu.edu (Phil Budne)
Cc: pc532@daver.bungi.com
Subject: Re: a couple of small ns32k.md changes (gcc 1.37.1) 
Date: Thu, 22 Mar 90 11:52:33 EST
From: David Taylor <taylor@Think.COM>
Status: O

<Date: Thu, 22 Mar 90 01:16:45 EST
<From: budd@bu-it.bu.edu (Phil Budne)

<Earler this week you mentioned you had gcc cross compiling itself
<on vaxen and sun4.  Does that include gas and gnu-ld?

It includes gas; it doesn't include gnu ld.  I haven't tried gnu ld,
yet.  I've heard from two people that it doesn't work for the ns32k.

One specific problem that was mentioned was immediate operands.  It's
unclear to me why you need to worry about immdiate operands -- do you
really need to fix them up at link time?  Isn't it sufficient to say
that they have to be know at assembly time and let the assembler worry
about them?

In any case, I haven't (yet) worried about the gnu ld.  I'm hoping that
someone else has figured out the changes and will post them to either
this mailing list or to bug-gnu-utils.  The vax ld is able to link
things without complaint; I don't, however, know if it *correctly* links
things.  If the gnu ld proves unusable, there's always Bruce
Culbertson's ld.  (But, I don't think Bruce's ld supports stabs (i.e.
debugger symbols).  Bruce?)

BTW, the when running gcc on the vax it doesn't correctly handle
floating point arithmetic as I haven't defined the various REAL
ARITHMETIC macros.  One of the reasons why I wanted to get gcc running
as a cross compiler on a sun is the hope that I won't have to sit down
and define the macros -- suns, like the ns32k, use ieee format floating
point.  But, then the byte ordering is wrong...

If anyone has done the necessay work to get gcc to support ieee
arithmetic on the vax, I'd like to know about it.

Gas 1.35 produces byte for byte identical output when run on a vax as
when run on a sun.

David

From owner-pc532%daver@mips.com Fri Mar 23 17:59:08 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 14:02:05 EST
From: Jerry Callen <jcallen@maxzilla.encore.com>
To: pc532@daver.bungi.com
Subject: Floppy controller
Status: O

I wrote:

>> ....It seems likely that the floppy controller will
>> contain an 80C188, clocked at (at least) 10 MHz, maybe 16, if the price
>> isn't too high. The chip divides this by two, so the system clock will 
>> be 5 (or maybe 8) MHz. I can easily get the 10MHz part for $15, I don't
>> know yet about the 16 MHz part.

Hmmm, closer reading shows that the rating on the chip is the CLKOUT
frequency, so the 10MHz part runs with a 20MHz clock, and can do a bit
over 1Mbyte/second via the onchip DMA channel. I can live with that.

>From: Bdale Garbee <bdale@col.hp.com>
>
>PLEASE use a V40 instead of an 80C188, I can't remember the details offhand,
>but there are "features" of the DMA stuff in the 188 that are a pain.  My 
>local NEC guy bent over backwards to get me books on the chipset...

Since the CPU choice is open again, I'll look at it. I've asked my
local distributor for data books.

>> I'll have to add a serial port, though. I don't yet know what this does
>> to the memory system, but I suspect the eventual configuration will be:
>
>There's a serial port on the V40, looks like an 8251.  They share the pins for
>that with one of the 4 DMA channels, but if you only need 3 DMA channels, the
>serial port is free.

Fine, I only need two channels. If a third is available, that makes it even
easier to drive a parallel printer port. Who could POSSIBLY want 4 DMA
channels? Or >640k of memory? :-)

>> SO - anyone know of any free/cheap 80x86 tools (C, assembler) for either
>> Unix or a Macintosh?
>
>I can probably help here.  HP makes a good cross-development environment, and
>I also have ACK, the Amsterdam Compiler Kit, which generated K&R compilers for
>the Intel iapx86 family among others.

Great, once I've settled on a processor, I'll come pleading for a compiler. :-)

>Bdale

-- Jerry Callen
   jcallen@encore.com
   (508) 460-0500 (work)
   (617) 876-5330 (home)

From owner-pc532%daver@mips.com Fri Mar 23 18:03:49 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 09:15:50 pst
From: Bruce Culbertson <culberts@hplwbc.hpl.hp.com>
To: pc532@daver.bungi.com
Subject: Re: GCC, GDB, GAS and binutils for the pc532
Status: O

> Might I suggest we use this version of these programs as a base for
> tools for the pc532 development.
> ...
> Anyway, I suspect that this is the only complete set (including a
> loader) of free tools available. Further more, it is a big comfort
> to me to know that the same (or very similar) version demonstrably
> works on another system (the icm3216).

Wait a minute, please, before mandating a set development tools
we are all supposed to use.

I also have a complete set of development tools which can be freely
distributed.  Mine have been quite stable for over two years and have
proved themselves by compiling an entire operating system and all
its utilities.  My tools have run on big endian and little endian
machines.  In fact, they have compiled or cross-compiled Minix 32000 on
an Amdahl running UTS, an HP9000 (Motorola 68000) running HP-UX, and
a 32016 running Minix.

Furthermore, as Dave Rand and I move my 32000 Minix port to the
pc532, I plan to change one thing at a time.  When something breaks,
I want to know that the problem is in Minix and not in the development
tools.  Also, I want to at least get a first version of Minix running
on the pc532 before considering changing a.out formats.

I am currently using gcc-1.36 (with modifications) with my own
assembler, linker, ar, nm, and ranlib.  Someday I would like to upgrade
to gcc-<the latest> and I can see the benefit in using a gdb compatible
a.out format.  But, today, my tools already produce quite acceptable code.
Getting Minix running on the pc532 is a higher priority for me.

Please do not misunderstand me.  I think it is great that people are
working on development tools.  By all means, please continue.  I am not
saying that I do not want to use your tools.  I am saying that I do not
want to use them now.

Bruce Culbertson

From owner-pc532%daver@mips.com Fri Mar 23 18:07:36 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: bobm@convex.com
To: pc532@daver.bungi.com
Subject: Re: a couple of small ns32k.md changes (gcc 1.37.1) 
X-Quote-Of-The: When a new technology rolls over you, if you're not part of
                the steamroller, you're part of the road.  -- Stewart Brand
X-Gnat-State: Grummet
Date: Thu, 22 Mar 90 23:24:48 CST
Status: O

> It includes gas; it doesn't include gnu ld.  I haven't tried gnu ld,
> yet.  I've heard from two people that it doesn't work for the ns32k.

I've been working on the gnu tools.  I've got ld (and ar and size and
ranlib and nm and strip and gprof) working.  Also gas.

BTW, I made a change to the a.out format: vaxen pad a.out to a 1K
boundary.  This is because the 4bsd vax click size is 1k.  On a
hypothetical demand paging pc532 OS, the click size would be 4k
(hardware page size).  So I padded the a.out header to 4k, and
similarly padded the size of the text segment.

Still no running pc532's in Texas, so I'm leery of sending out my
binutils versions (unless you promise not to hold me responsible...).
But on small files that I can stand to hand-assemble/load, my tools
generate the same result as I get by hand.

> One specific problem that was mentioned was immediate operands.  It's
> unclear to me why you need to worry about immdiate operands -- do you
> really need to fix them up at link time?  Isn't it sufficient to say
> that they have to be known at assembly time and let the assembler worry
> about them?

Immediate doesn't mean absolute.  Consider the C fragment,

	extern char foo[];
	register char *p = foo;

gcc would probably generate the instruction,

	movd	foo, r5

Then &foo goes into the instruction stream, in bigendian order, and its
value can't be determined until link time.

> Gas 1.35 produces byte for byte identical output when run on a vax as
> when run on a sun.

I've been doing all my work on a convex, which is big endian.
Byte ordering in object files and a.out files is handled explicitly.

(Gee, it's nice that this list is finally starting to discuss
something I know about!)

					K<bob>

From owner-pc532%daver@mips.com Fri Mar 23 18:07:39 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: idall@augean.ua.OZ.AU (Ian Dall)
Cc: pc532@daver.bungi.com
Subject: Re: GCC, GDB, GAS and binutils for the pc532 
Date: Fri, 23 Mar 90 12:59:56 EST
From: David Taylor <taylor@Think.COM>
Status: O

<Date: Fri, 23 Mar 90 15:36:50 +0930
<From: augean.ua.OZ.AU!idall@ames.UUCP (Ian Dall)

<If anyone wants to make useful contribution, writing gnulib in
<assembler (or in C with GCC style asm statements) would free us from
<the only step still requiring proprietry code. GNU lib must currently
<be compiled using a machines native assembler. It is a fairly small
<library containing functions to do certain type conversions. It might
<be cheating a bit, but I suppose I could start by running cc -S to get
<the first assembler version.

Actually, this isn't necessary *if* you have an FPU.  Instead, just
compile them with gcc.  Seriously.  While I haven't yet applied your
patches, so I can't say how they affect things, it used to be the case
(and probably still is), that gcc on the ns32k generated *inline* code
for each of the functions in gnulib.c.  To see if it's still true, do:

	make gnulib OLDCC=gcc532 CCLIBFLAGS="-O -S"

in the gcc directory (where gcc532 is replaced by whatever name you gave
it when you installed it) and then look at the various .s files.  If any
of the functions get called, then you have to write that one.  Last time
I did this (after RMS's changes to movsi and movdi, but before the change
to ashlsi3), *NONE* of them got called.

It would be nice to have copies of the floating point routines so that
it would be possible to do compiles with the -msoft-float option, but I
can't think of anything else that might cause problems.

David

From owner-pc532%daver@mips.com Fri Mar 23 18:14:21 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 23 Mar 90 12:35 PST
From: Mark Geisert <Mark-Geisert@l66a.ladc.bull.com>
To: pc532%daver@uunet.uu.net
Really-To: pc532%daver@uunet.uu.net
Subject: info on upcoming Amoeba distribution
Status: O

Here's some information that may be of interest from Andy Tanenbaum (of
MINIX fame) regarding Amoeba.  I hope this *does not* have any effect
on the work being done now for MINIX on the pc532.  This is just FYI.
----------------------cut here----------------------------------------
INFO-V: 67 (sent 03/23/90 01:17)
To:       INFO-V
From:     Andy Tanenbaum
Reply-to: ast%cs.vu.nl@LADCGW
Subject:   (Free) book on the Amoeba distributed system available
 
1. SUMMARY
     The purpose of this message is to announce the availability of
a (free) book about the Amoeba distributed operating system.  The system
itself will be available later this year.   Amoeba originated at the
Vrije Universiteit in Amsterdam, The Netherlands, and is now being developed
jointly there and at the Centre for Mathematics and Computer Science, also
in Amsterdam.
 
 
2. OVERVIEW OF AMOEBA
     Amoeba is a true distributed operating system that runs on a collection
of machines on a network.  Currently SUN-3 and VAXSTATIONS are supported.
386s are in the works, RISC machines eventually.  The idea is that to the user,
the entire thing looks like a conventional timesharing system.  There is no
concept of remote login or remote mount or remote anything else.  You can
directly access any file for which you have permission, without doing anything
special, no matter where it is.  The network acts like a single computer.
 
     A normal Amoeba configuration will have one workstation per user,
some file servers, and a collection of pool processors, to which processes are
dynamically assigned. For example, if you start up 'make', all the compilations
will automatically run in parallel on different pool processors.  You don't
have to do anything.  There is no concept of a 'home machine' on which things
run unless you explicitly tell them to run elsewhere.  Your own workstation is
normally just used to run the window manager (X windows); computing is done
on the processor pool.  You can use SUN-3s or VAXSTATIONS for the processor
pool, or you can use 680x0-based single board computers in a rack, which gives
an excellent price performance.
 
     The whole idea behind Amoeba is to explore distributed computing, so the
design assumes that you have a substantial number of machines that you
want to have working together.  We have designed a language, called Orca, that
makes parallel programming much easier by cleverly simulating an
object-based shared memory on a network of disjoint machines.  Orca will soon
be ported to Amoeba.
 
 
3. SYSTEM DESIGN
     Amoeba has a microkernel, which basically handles communication, I/O,
and low-level memory management, and little else.  Communication is based on
RPC and is extremely fast (1.4 msec RPC on Sun 3/50s; see ACM Operating
System Review, Oct. 1988, pp. 25-34).  The rest of the system is implemented
as a collection of servers running in user space, spread over many machines.
There has been a great emphasis on high performance.  The file server can
transfer at 5.4 megabits/sec, for example, which is over half the theoretical
capacity of the Ethernet, and is many times faster than NFS.
 
    A single integrated naming and protection scheme is used, based on
encrypted capabilities.  If you have the capability for a file or other object
in your directory, you can just access it, no matter where it is (including
international access, although this is still experimental).
 
 
4. RELATION TO OTHER SYSTEMS
     A UNIX emulation package is part of the basic system, so you can recompile
and run most well-behaved UNIX utilities.  There has been no attempt at
providing binary compatibility.  Amoeba comes with about 100 programs
that are similar to their UNIX counterparts, including a C compiler (based on
the Amsterdam Compiler Kit).  Some of the utilities have been borrowed from
MINIX and some are new.  There is not a single line of AT&T code anywhere in
the system--not in the operating system, not in the compilers, and not in any
of the utilities.  There are also 50 new utilities specifically for Amoeba.
 
     No doubt some people will want to compare Amoeba to Mach.  It is hard to
summarize the differences, but very briefly, Mach is an attempt to replace
UNIX.  Amoeba is more of a research system designed to make dozens or
hundreds of processors function together seamlessly.  It was designed to be
as fast as possible, gaining speed through careful software design and through
use of parallelism.
 
    No doubt other people will want to compare Amoeba to MINIX.  There is no
comparison.  MINIX is a quasi-toy.  Amoeba is a serious high-performance
system.  It is being used by the European Space Agency for transmitting
real-time television images, for example, because no other system was found to
be fast enough to handle the load.  OSF has provided us with considerable
funding so they can evaluate its potential for use in OSF/2 or OSF/3.
 
 
5. AMOEBA BOOK
     We have published dozens of papers on Amoeba over the years.  We have now
collected 17 of the most interesting ones in a 278-page paperback book.  The
papers provide an introduction to Amoeba, an overview of the design,
discussion of the measured performance, as well as 9 papers on programming
and applications.
 
     This book is now available.  Since processing of international checks is
a big pain, we have decided to send it out for free.  Please do not ask for it
unless you are seriously interested, and no more than one to a customer.  You
are permitted to make as many copies of it as you wish.  To order, send me
your snail mail address.
 
 
6. AVAILABILITY
    But when is Amoeba going to be available and under what conditions?  The
next tape is going to OSF by March 31, 1990.  While they are looking at it,
we will continue testing, putting together a proper distribution, and writing
documentation until it comes out our ears. (Although I don't mind writing, the
programmers on the project prefer C to English.)  We expect that a version will
be made available to universities and corporate research labs during the
second half of 1990, for a nominal fee and with few restrictions on use for
educational or research purposes.  All of the Amoeba source code will be
included.
 
Andy Tanenbaum (ast@cs.vu.nl)
 
----------------------cut here----------------------------------------
 
..mark  (Mark-Geisert@LADC.Bull.COM or ..!uunet!ladcgw!Mark-Geisert)

From owner-pc532%daver@mips.com Sat Mar 24 03:14:49 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: PC532 Mailing List <pc532%daver@uunet.UU.NET>
From: Dave Mason <mason%tmsoft%uunet@daver>
Subject: chip rev numbers and bug lists
Date: 23 Mar 90 17:50:54 EST (Fri)
Organization: TM Software Associates Inc.
Status: O

I just FTP'ed to bu.edu to pick up a copy of Ian's gnu patches, and
noticed that Phil had some chip bugsheets on line, so I transferred
those too.  I have a question:

How do I find out what rev number my chips are (and thus which of
these horrible lists of bugs apply :-)?  My chips say, for example:
	    CPU		    FPU		    ICU
	N  II8923C4	N  IS8952C4	N  S8750B d
	NS32532U-25	NS32381U-25	NS32202D10-MSP
	IFA93255	IFA93331
	C/5		D/10
(the N in the top left being the National logo, the `d' in the top
right of the ICU is really a delta)

My guess is that I have a C4 CPU, C4 FPU, and B ICU.  What are the C/5
and D/10 then?  Phil's directory had buglists for the 532 only up to
b3, and the ICU only e,f,g.  Does anyone else have online buglists for
other revs?  I'm doing my own O/S, not using Dave & Bruce's Minix
port, so I need to know what's going to be flooey.

(P.S. to Dave Rand, I sent you a note asking for what you have in the
way of drivers for the board.  Any luck?)

	../Dave

From owner-pc532%daver@mips.com Sat Mar 24 12:11:21 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
X-Mailer: Mail User's Shell (6.2 5/11/88)
To: pc532@daver.bungi.com
Subject: Re: chip rev numbers and bug lists
Date: 24 Mar 90 08:44:20 PST (Sat)
From: george@wombat.bungi.COM (George Scolaro)
Status: O

[In the message entitled "chip rev numbers and bug lists" on Mar 23, 17:50, Dave Mason writes:]
> 
> How do I find out what rev number my chips are (and thus which of
> these horrible lists of bugs apply :-)?  My chips say, for example:
> 	    CPU		    FPU		    ICU
> 	N  II8923C4	N  IS8952C4	N  S8750B d
> 	NS32532U-25	NS32381U-25	NS32202D10-MSP
> 	IFA93255	IFA93331
> 	C/5		D/10
> (the N in the top left being the National logo, the `d' in the top
> right of the ICU is really a delta)
> 
> My guess is that I have a C4 CPU, C4 FPU, and B ICU.  What are the C/5
> and D/10 then?  Phil's directory had buglists for the 532 only up to
> b3, and the ICU only e,f,g.  Does anyone else have online buglists for


You have a Rev C CPU and a rev D FPU. The /5 and /10 mean (as far as I know)
that the part is with 5% or 10% of the published spec (timing wise). If
anyone knows better I'd like to hear about it...

Rev C cpu and Rev D FPU are the latest revisions.

The ICU does not have a rev spec on the front, but on the back of the two I
have here, that have the -MSP on the front, the rev is designated by a (G),
ie Rev G, which also the latest.

regards,

-- 
George Scolaro
george@wombat.bungi.com                [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Sat Mar 24 12:56:49 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Sat, 24 Mar 1990 20:36:28 +1000
From: ian@sibyl.eleceng.ua.oz.au
To: pc532@daver.bungi.com
Status: O

I have acquired (or am acquiring) nearly all the components for my pc532.
The only things I still don't have a source for are 3 x 74AS158 (or 74AS258)
and 1 x 74AS374.

If anyone can help me with these I would very much appreciate it!


From owner-pc532%daver@mips.com Sat Mar 24 12:56:54 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Sat, 24 Mar 1990 13:22:48 +1000
From: ian@sibyl.eleceng.ua.oz.au
To: pc532@daver.bungi.com
Subject: Re: a couple of small ns32k.md changes (gcc 1.37.1) 
Status: O

David Taylor writes:
 > One specific problem that was mentioned was immediate operands.  It's
 > unclear to me why you need to worry about immdiate operands -- do you
 > really need to fix them up at link time?

Probably the compiler avoids it but there is no reason why

	.data
foo:	.double	0x0
	.text
	movd foo, r0    # movd $foo, r0 on NS assemblers

should not load r0 with the relocatable value foo, and every reason why one
might want to do so.

 > In any case, I haven't (yet) worried about the gnu ld.  I'm hoping that
 > someone else has figured out the changes and will post them to either
 > this mailing list or to bug-gnu-utils.

Have done.

 >  The vax ld is able to link
 > things without complaint; I don't, however, know if it *correctly* links
 > things.

I don't think it can.

 > BTW, the when running gcc on the vax it doesn't correctly handle
 > floating point arithmetic as I haven't defined the various REAL
 > ARITHMETIC macros.

Gas totally stuffes up floating point byte order for the 32k. Fixed by
the patches on augean.

 > Gas 1.35 produces byte for byte identical output when run on a vax as
 > when run on a sun.

And wrong. Try for example assembling

	.text
	cmpqd 1,1

That is compare quick 1 with immediate 1. Again, fixed by the patches
on augean.


From owner-pc532%daver@mips.com Sun Mar 25 02:50:00 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: ian%sibyl.eleceng.ua.oz@augean.ua.oz.au
Cc: pc532@daver.bungi.com
Subject: Re: gcc 1.37.1 and the ns32k (update) 
Date: Sun, 25 Mar 90 02:14:14 EST
From: David Taylor <taylor@Think.COM>
Status: O

I think I may have forgotten to post these small changes from Jay
Fenlason (the current maintainer of GAS).  The changes are fairly small.

The line numbers are *before* applying Ian's changes.  The changes are
fairly minor -- one was to as.c the other to ns32k.c.

The intent of changes is to prevent infinite loops printing "Interrupted
by signal 10" (as.c) and to avoid generating the bus error in the first
place (ns32k.c).  [The message was being generated on a sun4 -- sun4's
have some strict alignment requirements.]

The as.c change is:

RCS file: RCS/as.c,v
retrieving revision 1.1
diff -c -r1.1 as.c
*** /tmp/,RCSt1006128	Sun Mar 25 01:59:22 1990
--- as.c	Tue Mar 20 22:05:02 1990
***************
*** 283,289 ****
--- 283,293 ----
  got_sig(sig)
  int sig;
  {
+ 	static here_before = 0;
+ 
  	as_bad("Interrupted by signal %d",sig);
+ 	if(here_before++)
+ 		exit(1);
  }
  
  /* end: as.c */

and the ns32k.c change is:

RCS file: RCS/ns32k.c,v
retrieving revision 1.2
diff -c -r1.2 ns32k.c
*** /tmp/,RCSt1006152	Sun Mar 25 02:01:02 1990
--- ns32k.c	Tue Mar 20 22:04:57 1990
***************
*** 1062,1073 ****
  		  md_number_to_chars(memP+l,generic_bignum[l>>1],sizeof(LITTLENUM_TYPE));
  		}
  	      } else { /* flonum */
  		switch(size) {
  		case 4:
! 		  gen_to_words(memP,2,8);
  		  break;
  		case 8:
! 		  gen_to_words(memP,4,11);
  		  break;
  		}
  	      }
--- 1062,1081 ----
  		  md_number_to_chars(memP+l,generic_bignum[l>>1],sizeof(LITTLENUM_TYPE));
  		}
  	      } else { /* flonum */
+ 		LITTLENUM_TYPE words[4];
+ 
  		switch(size) {
  		case 4:
! 		  gen_to_words(words,2,8);
! 		  md_number_to_chars(memP                       ,(long)words[0],sizeof(LITTLENUM_TYPE));
! 		  md_number_to_chars(memP+sizeof(LITTLENUM_TYPE),(long)words[1],sizeof(LITTLENUM_TYPE));
  		  break;
  		case 8:
! 		  gen_to_words(words,4,11);
! 		  md_number_to_chars(memP                         ,(long)words[0],sizeof(LITTLENUM_TYPE));
! 		  md_number_to_chars(memP+sizeof(LITTLENUM_TYPE)  ,(long)words[1],sizeof(LITTLENUM_TYPE));
! 		  md_number_to_chars(memP+2*sizeof(LITTLENUM_TYPE),(long)words[2],sizeof(LITTLENUM_TYPE));
! 		  md_number_to_chars(memP+3*sizeof(LITTLENUM_TYPE),(long)words[3],sizeof(LITTLENUM_TYPE));
  		  break;
  		}
  	      }


From owner-pc532%daver@mips.com Mon Mar 26 07:26:36 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Mon, 26 Mar 1990 14:57:53 +1000
From: idall@augean.ua.oz.au
To: pc532@daver.bungi.com
Subject: GDB patches
Status: O

I have merged in David Taylors gdb patches so they are now contained
by the patches on augean.ua.oz.au 

I have also revised the makefiles for GDB a bit so that no hand intervention
should be required for either of the two configurations supported.
(If you are using the coff-encapsulation stuff though, make sure that your
PATH is such that is picks up the GNU nm first.)

I have also renamed the files so that the name reflects the version of
the GNU utility it is to be applied to and also the version of my patch.

Thus the new gdb patch file is

   gdb-3.5.patch1.1.Z

..patch1.0 files are unchanged.


From owner-pc532%daver@mips.com Mon Mar 26 07:26:40 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Sun, 25 Mar 1990 09:33:09 +1000
From: ian@sibyl.eleceng.ua.oz.au
To: pc532@daver.bungi.com
Subject: Re: GCC, GDB, GAS and binutils for the pc532
Status: O

Bruce Culbertson writes:
 > > Might I suggest we use this version of these programs as a base for
 > > tools for the pc532 development.
 > > ...
 > > Anyway, I suspect that this is the only complete set (including a
 > > loader) of free tools available. Further more, it is a big comfort
 > > to me to know that the same (or very similar) version demonstrably
 > > works on another system (the icm3216).
 > 
 > Wait a minute, please, before mandating a set development tools
 > we are all supposed to use.

Well, I only wanted to stop anyone else wasting time on the same thing.
ie lets build on each others work instead of competing.

 > I also have a complete set of development tools which can be freely
 > distributed.  Mine have been quite stable for over two years and have
 > proved themselves by compiling an entire operating system and all
 > its utilities.

I must confess, I forgot about your stuff when I said "the only..".
However, let me assure everyone that this version of gcc has built a
large array of working software. Indead, pretty much everything
*except* the kernel which is small potatoes in terms of lines of code.

To me, it is a big win to be able to compile and test on my
icm3216/SysV It is no doubt a big win for you to be able to test code
running on your ??32k/minix system.

 > Getting Minix running on the pc532 is a higher priority for me.

Yup use what works. Changing a.out formats later will not be that big
a deal but, as you say, would be a mistake to do now.


From owner-pc532%daver@mips.com Mon Mar 26 07:29:04 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Sun, 25 Mar 1990 12:49:14 +1000
From: ian@sibyl.eleceng.ua.oz.au
To: pc532@daver.bungi.com
Subject: Assembler syntax.
Status: O

David Taylor writes:
 > . ns32k-opcode.h -- why WHY ***WHY*** do you default labels to
 > immediate?  I can understand not wanting them to be absolute.  But,
 > ***WHY*** immediate?  I'm sorry, I don't like this.

David doesn't like my choice of assembler syntax and I would like to
see if we can come up with a concensus on what assembler syntax we
want.

First note that gas doesn't distinguish between labels and other
symbols when parsing references to the symbols. The way I look at it
is that a symbol has a value and by default it should behave as if
that value were simply substituted.

	.set foo, 0x100
	movd foo, r0

should be the same as

	movd 0x100, r0

The original gas syntax meant that

	.set foo, 0x100
	movd #foo, r0

was equivalent to

	movd 0x100, r0

I think that sucks.

The NS native assembler defaults to absolute addressing and requires a
$ prefix to specify immediate mode. This also makes sense

	.set foo, 0x100
	movd $foo, r0

is the same as

	movd $0x100, r0

I think this is OK. I just object to the default for constants being different
to the default to symbols.

So... assume the following assembler is to go through cpp.

/* ABSOLUTE_CONSTANT_PREFIX */
#define ABS_C @
/* ABSOLUTE_SYMBOL_PREFIX */
#define ABS_S @
/* IMMEDIATE_SYMBOL_PREFIX */
#define IM_S
/* IMMEDIATE_CONSTANT_PREFIX */
#define IM_C
/* BRANCH_PREFIX */
#define BRA

	.set x, 0xfff000		/* Assume there is some free memory here */
	.text
foo:
	movd IM_S/**/x, r0
	movd IM_C/**/0xfff000, r1
	cmpd REG/**/r0, REG/**/r1
	bne BRA/**/error
	movd IM_S/**/foo, ABS_S/**/x
	movd 0(r0), r1
	cmpd r0, r1
	bne BRA/**/error
	movqd IM_C/**/0, r0
	ret 0
error:
	movqd IM_C/**/-1, r0
	ret 0

If this looks confusing, feed it through a traditional (pre ANSII) cpp
(gcc -E -traditional will do).

What would you define the above preprocessor variables to in order for
the above function to be valid (always return 0) in your idea of the ideal
assembler syntax?

You cannot have IM_C == ABS_C or IM_S == ABS_S.

Current assemblers I know of require

                        -----------------------------------------
                        |  IM_C |  IM_S | ABS_C | ABS_S |  BRA  |
------------------------|-------|-------|-------|-------|-------|
| 1. NS Instruction Set |       |       |       |       |       |
|    Reference Manual   |       |       |   @   |   @   |       |
|-----------------------|-------|-------|-------|-------|-------|
| 2. NS 5.2.2 as        |   $   |   $   |       |       |       |
|-----------------------|-------|-------|-------|-------|-------|
| 3. Sequent            |       |   #   |   @   |       |       |
|-----------------------|-------|-------|-------|-------|-------|
| 4. Encore             |       |   #   |   @   |       |       |
|-----------------------|-------|-------|-------|-------|-------|
| 5. Original Gas       |       |   #   |   @   |       |       |
|-----------------------|-------|-------|-------|-------|-------|
| 6. Ian's Gas          |       |       |   @   |   @   |       |
-----------------------------------------------------------------

I am accepting votes for the "correct" syntax to use. (And also
corrections to the above table). I personally dislike having different
syntax for symbols and constants which I think means 1. or 2. Further,
GAS uses BSD style directives so it seems sensible to use BSD style
syntax which basically means 1.

As well as opinions(!) I would like to hear any compelling technical
arguments in favour of a particular syntax.

> I've been thinking myself of changing the default from 21 to DEFAULT (==
> -1) or some such magic number and then having command line switches
> which would select either absolute or (yea) pc-relative.  A large part
> of my reason for wanting this is that I figure it would go a LONG way
> towards allowing gcc/gas output to be made position independent.
> 
> As a consequence, I don't want gcc generating '@'s all over the place.

If you really want switches to override assembler modes it doesn't
seem to me that the presence of the "@" signs make the job much (if at
all) harder.  I don't think this is the best way to tackle the
problem. I reckon assemblers should do what they are told. If you
really want to generate position independent code, I reckon it
wouldn't be too hard to make gcc do that (for this machine). You need
to make GO_IF_ILLEGITIMATE_ADDRESS consider absolute addresses
illegal. I think it would then go ahead and generate relative
addresses for everything. You would also need to check for any places
where assembler is directly generated by various macros and in the
machine definition file.


Ian Dall


From owner-pc532%daver@mips.com Mon Mar 26 14:23:50 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Mon, 26 Mar 90 10:59:46 pst
From: Bruce Culbertson <culberts@hplwbc.hpl.hp.com>
To: pc532@daver.bungi.com
Subject: Re:  Assembler syntax.
Status: O

Hi gang,

I want to throw my two bits in on assembler syntax.

> ... I would like to
> see if we can come up with a concensus on what assembler syntax we
> want.

I'm in favor of this!

> First note that gas doesn't distinguish between labels and other
> symbols when parsing references to the symbols.

My tools also do not distinguish.

> The way I look at it
> is that a symbol has a value and by default it should behave as if
> that value were simply substituted.
>
>	.set foo, 0x100
>	movd foo, r0
>
> should be the same as
>
>	movd 0x100, r0
>
> The original gas syntax meant that
>
>	.set foo, 0x100
>	movd #foo, r0
>
> was equivalent to
>
>	movd 0x100, r0
>
> I think that sucks.

I agree.

> The NS native assembler defaults to absolute addressing and requires a
> $ prefix to specify immediate mode. This also makes sense
> 
> 	.set foo, 0x100
> 	movd $foo, r0
> 
> is the same as
> 
> 	movd $0x100, r0
> 
> I think this is OK. I just object to the default for constants being different
> to the default to symbols.

Let me bore you with my philosophy.  We all know that abstraction is the
key to building large systems with our feeble human minds.  However,
I feel there should be a lowest level where the abstaction stops.
Assembler is that level.  I like everything to be explicit at the
assembler level.  My assembler has no defaults.  If want some addressing
mode, you must use @, (pc), or whatever.  Otherwise, you get
immediate.  Given this rule, what is the point of the # or $?
I do not use # or $.

An early National assembler had, as a symbol attribute, the default
addressing mode to be used with the symbol.  I think this was horrible.
It was too hard to figure out what was going on.

I guess I violated my rule in one minor respect.  For br, bsr, and (pc)
offsets, I use "symbol", not "symbol - *".

> So... assume the following assembler is to go through cpp.
> 
> /* ABSOLUTE_CONSTANT_PREFIX */
> #define ABS_C @
> /* ABSOLUTE_SYMBOL_PREFIX */
> #define ABS_S @
> /* IMMEDIATE_SYMBOL_PREFIX */
> #define IM_S
> /* IMMEDIATE_CONSTANT_PREFIX */
> #define IM_C
> /* BRANCH_PREFIX */
> #define BRA
> ...
> I am accepting votes for the "correct" syntax to use. (And also

I agree with this.  I vote for choice number 1.

> A large part
> of my reason for wanting this is that I figure it would go a LONG way
> towards allowing gcc/gas output to be made position independent.

I made gcc generate code which was as position independent as possible.
I use (pc) addressing mode primarily.  Real position independence is
hard to achieve, however, because of things like pointer initialization
at link time.  I am opposed to pointer initialization at run time.

I assume that SB is always set to zero.  That way, "*foo" (foo a global)
can be referred to as "0(_foo(sb))".

Bruce Culbertson

From owner-pc532%daver@mips.com Mon Mar 26 15:51:06 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Mon, 26 Mar 90 12:40:50 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: last chance pc532 run
Status: O

[In the message entitled "last chance pc532 run" on Mar 26, 12:28, George Scolaro writes:]
> 	well, the second run of pc532 motherboards will get underway at the
> beginning of next week. So, any and all who want one (and haven't already
> emailed in your order) please do so now. At this stage there are 20 or so
> firm orders so the PCB's should be around the $200 mark, probably less since
> the tooling & setup was a one time deal that was paid for on the previous run
> of 65. I'll post the actual board cost as soon as I can get hold of West
> Coast Circuits...

Don't forget:

If you are interested, please mail your request to:

pc-order@daver.bungi.com -or- {sun|mips|pyramid|vsi1|uunet}!daver!pc-order

*PLEASE*! Include your Name, *ADDRESS*, telephone number, and
quantity desired. Also, please include your address. And, if it
is not too much trouble, your address. That is, please include the
address you would like the board shipped to.

(too many people didn't include their address on the last go-around)

-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From owner-pc532%daver@mips.com Mon Mar 26 16:17:12 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Mon, 26 Mar 90 12:28:46 PST
X-Mailer: Mail User's Shell (6.5 4/17/89)
From: gs@vw25.chips.com (George Scolaro)
To: pc532@daver
Subject: last chance pc532 run
Status: O

Hi Folks,
	well, the second run of pc532 motherboards will get underway at the
beginning of next week. So, any and all who want one (and haven't already
emailed in your order) please do so now. At this stage there are 20 or so
firm orders so the PCB's should be around the $200 mark, probably less since
the tooling & setup was a one time deal that was paid for on the previous run
of 65. I'll post the actual board cost as soon as I can get hold of West
Coast Circuits...


regards,

-- 
George Scolaro (gs@vw25.chips.com)	Chips & Technologies
+1 408/434-0600 X4556 work		3050 Zanker Road
					San Jose, CA  95134

From owner-pc532%daver@mips.com Mon Mar 26 16:40:45 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Re: chip rev numbers and bug lists 
Date: Sat, 24 Mar 90 19:19:52 MST
From: Bdale Garbee <bdale@col.hp.com>
Status: O

> that the part is with 5% or 10% of the published spec (timing wise). If
> anyone knows better I'd like to hear about it...

No idea.  Fred and I are running B3/10 CPU's, B0/10 FPU's, and I have a G ICU.
I know the FPU's have some ugly bugs, but they were free, so...  we'll worry
about it at some point.

Bdale

From owner-pc532%daver@mips.com Tue Mar 27 04:08:55 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Mon, 26 Mar 90 22:55:43 -0800
From: chaim%nsc%voder@daver (Chaim Bendelac)
To: pc532@daver.bungi.com
Subject: re: assembler syntax
Status: O

> ... concensus on assembler syntax ...

While perhaps not the most elegant, I'd suggest that you stick as close as
you can to National's own assembler. You remain source-compatible (if that
ever becomes an issue, which it may), and your syntax is automatically
and extensively documented. If the need ever comes up, you have a trivial
upgrade-path to our tools too.
--
chaim@nsc.nsc.com (Chaim Bendelac - National Semiconductor)

From owner-pc532%daver@mips.com Tue Mar 27 12:34:48 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Tue, 27 Mar 90 02:27:49 EST
From: budd@bu-it.bu.edu (Phil Budne)
To: pc532@daver.bungi.com
Subject: PC532 (ICU) Initialization
Status: O

Could someone (ie; Dave, George or Bruce) post sample values (or code)
for initializing the PC532, especially the ICU (esp ELTG, TPL, OCASN,
CLKM, CCTL) and DUARTs.  Since I don't have my board finished yet I
can't poke around on my own.  It took me until this weekend to realize
that 2 of the ICU input/outputs are being used for SWAP and SCSI
select. Is auto-rotate mode of any value?

George; the data book shows !HBE tied down to GND, while the PC532
ties it up (to +V). Whats the scoop?

Bruce; As far as I'm concerned if the monitor has examine, deposit and
jump you should spend your time on Minix.  The last time I did a port
to bare metal thats about all I put in ROM.  I then used deposit to
load a block by block checksumming loader (stolen from Xinu).  [See
bu.edu:~ftp/src/KERNEL/68010-dev.tar.Z for the loader, monitor and a
(Sun) a.out to Intel hex converter].

It seems that much traffic on the list (compilers, loaders, and their
associated archive sites) could beneift comp.sys.nsc.32k, but I'm
hesitant to recommend any action.  I'd hate to see the signal to noise
ratio go down, and lets face it Usenet is mostly noise!

-Phil

From owner-pc532%daver@mips.com Tue Mar 27 13:11:12 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Tue, 27 Mar 90 09:44:46 PST
X-Mailer: Mail User's Shell (6.5 4/17/89)
From: gs@vw25.chips.com (George Scolaro)
To: pc532@daver.bungi.com
Subject: Re: PC532 (ICU) Initialization
Status: O

[In the message entitled "PC532 (ICU) Initialization" on Mar 27,  2:27, Phil Budne writes:]

> George; the data book shows !HBE tied down to GND, while the PC532
> ties it up (to +V). Whats the scoop?

Since we never program the ICU to the 16 bit mode, HBE (high byte enable) is
a don't care pin.  It's nice to tie it to something rather than to let it
float.

regards,

-- 
George Scolaro (gs@vw25.chips.com)	Chips & Technologies
+1 408/434-0600 X4556 work		3050 Zanker Road
					San Jose, CA  95134

From owner-pc532%daver@mips.com Tue Mar 27 14:04:26 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: AWESOME!
Clarity-Index: null
Threat-Level: none
Quote-Of-The-Moment: 's/./&&/g' Tom sed expansively.
Date: Mon, 26 Mar 90 23:27:29 CST
From: Jon Loeliger <loeliger@convex.com>
Status: O

Hey!  We've got another live one!  The PC532 runs.

The only problem during bringup was that the RS232 line needed a null modem.

Yee Haw!!

Thanks, Dave!  Thanks, George!

Now it's just a small matter of programming....


					jdl/K<bob>



From owner-pc532%daver@mips.com Tue Mar 27 18:39:48 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Tue, 27 Mar 90 15:30:36 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: PC532 (ICU) Initialization
Status: O

[In the message entitled "PC532 (ICU) Initialization" on Mar 27,  2:27, Phil Budne writes:]
> Could someone (ie; Dave, George or Bruce) post sample values (or code)
> for initializing the PC532, especially the ICU (esp ELTG, TPL, OCASN,
> CLKM, CCTL) and DUARTs.  Since I don't have my board finished yet I
> can't poke around on my own.  It took me until this weekend to realize
> that 2 of the ICU input/outputs are being used for SWAP and SCSI
> select. Is auto-rotate mode of any value?
I'll try to get to this in the next day or so... 

> 
> It seems that much traffic on the list (compilers, loaders, and their
> associated archive sites) could beneift comp.sys.nsc.32k, but I'm
> hesitant to recommend any action.  I'd hate to see the signal to noise
> ratio go down, and lets face it Usenet is mostly noise!
> 

Yes - what say we either:

1) start our own newsgroup 
2) take over c.s.n.32k (evil chuckle)

Now is a good time. I mail to >150 addresses, and it is evident that >200
people are reading this list...

Someone want to take the ball here please? I'm running very short on time
(more on this in a few days, Friday perhaps).



-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From owner-pc532%daver@mips.com Tue Mar 27 18:49:34 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Tue, 27 Mar 90 15:35:31 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: re: last chance pc532 run
Status: O

[In the message entitled "re: last chance pc532 run" on Mar 27, 10:07, KENYEE@s49.prime.com writes:]
> An Engineering student friend of mine heard about the PC532   project and
> was wondering how to get a copy of the design documentation...cost
> for postage and copying, who to send it to..,etc.
> 

The design is available from George and myself. To get a copy, either find
someone close to you that has it (and get a photocopy), or mail to us.
The kit we send out has the Theory of Operation, schematic (printed & 
machine readable), pal equations, etc. Someone suggested that $5 would
cover postage & diskette within the US, and $10 would be more than enough
for overseas.

Dave Rand / George Scolaro
941 Chehalis Drive
Sunnyvale, CA  94087


-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From kls@SCSSUN1.SLAC.STANFORD.EDU Tue Mar 27 23:59:45 1990
Flags: 000000000000
Date: Tue, 27 Mar 90 20:44:41 PST
From: kls@SCSSUN1.SLAC.STANFORD.EDU
Subject: disk buy status
To: @labtam.oz.au:athos@eyrie, bdale@col.hp.com, bob@arthur.wwu.edu,
        bobm@convex.com, bpan@vw26.chips.com, buck@siswat.lonestar.org,
        budd@bu-it.bu.edu, david@dogmelb.dog.oz.au, dlr@daver.bungi.com,
        drf@zinn.mv.com, eyal@ucisae.isae.cancol.oz.au, freb@goldfnch.mv.com,
        glowell@hpda.hp.com, manatee!johnc, jonathan@comp.vuw.ac.nz,
        jto@tut.fi, ditka!kls, loeliger@convex.com,
        mark-geisert@l66a.ladc.bull.com, morris@chips.com, night@pawl.rpi.edu,
        pell@isy.liu.se, rjohnson@kiwi.mpr.ca, s861019@minyos.xx.rmit.oz.au,
        s861298@minyos.xx.rmit.oz.au, sef@kithrup.com, taylor@think.com,
        xrolfa@dna.lth.se
X-Envelope-To: budd@bu-it.bu.EDU
Status: O

I talked to my bank this afternoon and *finally* got an complete
cross reference of names and wire transfer.  It seems they usually
deposit the money then take their time telling you about it, so I
haven't been able to figure out *who* has paid!  There is still one
wire (for a single) drive that I haven't attached to a name but I
should have that info tomorrow.

That will leave two people with a total of three drives unpaid:

    2 drives	s861298@minyos.xx.rmit.oz.au (Marc A. Boschma)
    1 drive	jonathan@comp.vuw.ac.nz (Jonathan Stone)
    1 drive	drf@zinn.mv.com (Don Fairchild)

I suspect the unnamed wire, which arrived on Wednesday, March 21,
is Don's but it could be Jonathan's.  Like I said, I'll find out
>From the bank tomorrow.

Unless I hear otherwise by morning I'll cancel the unpaid orders
and buy the remaining drives tomorrow afternoon.  Those of you in
the US should thus have them by Friday.

Karl Swartz
1-408/223-1308
kls@ditka.uucp or zygot!ditka!kls@apple.com

From owner-pc532%daver@mips.com Wed Mar 28 18:40:30 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: ian@sibyl.eleceng.ua.oz.au
Date: Wed, 28 Mar 1990 21:40:50 +1000
To: pc532%daver@uunet.UU.NET
Subject: esoteric parts
Status: O

George Scolaro writes:
 > [In the message entitled "pc532 part type questions" on Jan 30, 12:11, Jukka Virtanen writes:]
 > > 	Could you please specify the exact part numbers/types
 > > 	for the following parts (we are going to make a group
 > > 	order from the local Arrow distributor, or some such):
 > > 		- no slot clock
 > 
 > Dave & I just went down to a local computer/electronics place and bought one
 > for the IBM XT. All we can say is that it is a 28 pin device that sits under
 > a standard 27256 EPROM. Dallas Semiconductor manufactures the actual device
 > and it is then sold by other companies. JDR (advertise in BYTE) sells this
 > one.

I am not sure if I am ordering the right thing for the No-Slot Clock.
I have looked through the 1989 IC Master, and have come up with the
following possibilities:

   1)	"Real Time Clock plus RAM (NVRAM)"	DS1287
		
   2)	"Real-Time Clock Plus RAM (replacement
	 for IBM AT computer clock/calander)"	DS1285

   3)	"Smart Watch (watch or clock, nonvolatile
	 RAM control) with socket, battery.	DS1216
						DS1216C
						DS1216E

   4)	"Smart Watch, Calendar/Clock with embedded
	 Lithium Cell.				DS1216F

All are made by Dallas Semiconductor. 2 sounds most promising but you
said replacement for an IBM XT.


From owner-pc532%daver@mips.com Wed Mar 28 18:44:09 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Wed, 28 Mar 90 11:04:57 pst
From: Bruce Culbertson <culberts@hplwbc.hpl.hp.com>
To: pc532@hplwbc.hpl.hp.com
Subject: Some Monitor Sources
Status: O

Hi pc532'ers,

Here are a few source files from the monitor.  Resume532.s has the
"boot" code following the symbol "start".  Dblib.s has code to
initialize the UART's and to send and receive characters.

In my last message I mentioned that it took twenty seconds to
initialize 32 megabytes of DRAM.  I solved the mystery.  I screwed
up the code to initialize the config register and, consequently,
had the i-cache turned off.  The next EPROM image I post will have
this fixed.

Bruce Culbertson
----------------------------------------------------------------------
# This is a shell archive.  Remove anything before this line,
# then unpack it by saving it in a file and typing "sh file".
#
# Wrapped by Bruce Culbertson <culberts@hplwbc> on Wed Mar 28 10:55:45 1990
#
# This archive contains:
#	resume532.s	dblib.s		
#

LANG=""; export LANG
PATH=/bin:/usr/bin:$PATH; export PATH

echo x - resume532.s
cat >resume532.s <<'@EOF'
; NSC 32000 ROM debugger.
; Bruce Culbertson  Bob Kraus
;
; Boot starts here.  Also, code to switch between debugger and user code.


table_start:	.equ	h'20
modtab_adr:	.equ	table_start
inttab_adr:	.equ	modtab_adr + h'20
mem_len:	.equ	32*h'100000	;32 megabytes
db_stack:	.equ	h'800
psr_usp:	.equ	h'200
psr_ie:		.equ	h'800
bpt_vec:	.equ	8

cfg_i:		.equ	h'001
cfg_f:		.equ	h'002
cfg_m:		.equ	h'004
cfg_dc:		.equ	h'200
cfg_ic:		.equ	h'800
cfg_default:	.equ	h'0f0 or cfg_i or cfg_f or cfg_m or cfg_dc or cfg_ic

;These are offsets into _machState
ms_r:		.equ	0
ms_cpu:		.equ	32
ms_pc:		.equ	ms_cpu+4*0
ms_sb:		.equ	ms_cpu+4*1
ms_fp:		.equ	ms_cpu+4*2
ms_usp:		.equ	ms_cpu+4*3
ms_isp:		.equ	ms_cpu+4*4
ms_intbase:	.equ	ms_cpu+4*5
ms_mod:		.equ	ms_cpu+4*6
ms_psr:		.equ	ms_cpu+4*6+2
ms_mmu:		.equ	60
ms_ptb0:	.equ	ms_mmu+4*0
ms_ptb1:	.equ	ms_mmu+4*1
ms_tear:	.equ	ms_mmu+4*2
ms_mcr:		.equ	ms_mmu+4*3
ms_msr:		.equ	ms_mmu+4*4
ms_debug:	.equ	80
ms_dcr:		.equ	ms_debug+4*0
ms_dsr:		.equ	ms_debug+4*1
ms_car:		.equ	ms_debug+4*2
ms_bpc:		.equ	ms_debug+4*3
ms_fpu:		.equ	96
ms_fsr:		.equ	ms_fpu+0
ms_f:		.equ	ms_fpu+4
ms_cfg:		.equ	164

	.static
_cfg_init::	.word	cfg_default	;used in init_machState()
dbsp:		.blkd	1
dbfp:		.blkd	1
in_db:		.byte	1		;true if in debugger

	; Debugger starts here.  Initialize things.
	.program
;--------------------------------------------------------------------------
; This code is lifted from MONSTART by Dave Rand.
;--------------------------------------------------------------------------
codesp:	.equ	h'10000000		; swapped code space
datasp:	.equ	h'0			; real data space
SECOND:	.equ	4000000			; ACB count for 1 second (rough)
SCSI:	.equ	h'30000000		; SCSI address

; The code from start to reset1 starts up the refresh, and swaps the
; rom to high memory.  Start must be the first thing in the rom.

start::					; must be visible to linker
	lprw	cfg,cfg_default
	movd	(SECOND/1000000)*800,r1 ; get 800 microsecond delay
h1:	acbd	-1,r1,h1
	movd	h'fffffe00,r7		; point to ICU
	movb	h'15,22(r7)		; set up refresh
	movqb	0,16(r7)
	movb	13,24(r7)
	movqb	0,25(r7)
	movqb	-1,19(r7)		; set up a 1 in all outputs
	movqb	0,20(r7)		; set as all I/O
	movqb	-2,21(r7)		; g0 as output
	br	reset1+codesp

reset1:	movqb	-2,19(r7)		; kill rom at zero, swap RAM

;the following code lights all of the LEDs connected to the SCSI
	movd	SCSI,r0			; point to scsi
	movb	h'8,0(r0)		; register 8
	movb	h'4,1(r0)		; no reset, 20 Mhz
	movqb	7,0(r0)			; register 7
	movb	h'10,1(r0)		; port A output
	movb	h'd,0(r0)		; register D
	movqb	-1,1(r0)		; LED status

; This code wakes up the DRAM, according to the spec.
; It also initializes (at txl1) the first 2K of ram by overwriting.
	addr	@10,r2			; do it 10 times
txl2:	movd	(SECOND/1000000)*8000,r1 ; get 8 millisecond delay
h2:	acbd	-1,r1,h2
	movd	datasp,r0		; point to data space
	movqd	0,0(r0)			; write to page zero
	movqd	0,h'2000000-4(r0)	; write to last page
	movqd	0,0(r0)			; write to page zero
	movqd	0,h'2000000-4(r0)	; write to last page
	movqd	0,0(r0)			; write to page zero
	movqd	0,h'2000000-4(r0)	; write to last page
	movqd	0,0(r0)			; write to page zero
	movqd	0,h'2000000-4(r0)	; write to last page
	addr	@512,r1			; write first 512 doubles (2048 bytes)
txl1:	movqd	0,0(r0)	; write data
	addqd	4,r0			; next block
	acbd	-1,r1,txl1		; and loop
	acbd	-1,r2,txl2		; loop 10 times

;
; The following actually enables the NMI/parity error.
	movd	h'28000040,r0
	cmpqb	0,h'10(r0)		; clear NMI error

;Initialize the first 4 megabyte of memory
;
parin2:
	movd	datasp+h'800,r0		; point to start of data space
	movd	(mem_len-h'800)/32,r1; number of chunks to write
parin3:	movqd	0,0(r0)
	movqd	0,4(r0)
	movqd	0,8(r0)
	movqd	0,12(r0)
	movqd	0,16(r0)
	movqd	0,20(r0)
	movqd	0,24(r0)
	movqd	0,28(r0)
	addd	32,r0
	acbd	-1,r1,parin3
	movd	h'28000040,r0
	cmpqb	0,h'10(r0)		; clear NMI error

rst14:
	bicpsrw	psr_usp	or psr_ie	;int stack
	lprd	sp,db_stack
	lprd	intbase,inttab_adr
	lprw	mod,modtab_adr
	lprd	sb,0
;--------------------------------------------------------------------------
; End of MONSTART
;--------------------------------------------------------------------------
	br	_main

_isr_nvi::
	bicpsrw	psr_ie
	movqd	0,tos
	br	exit_user
_isr_nmi::
	bicpsrw	psr_ie
	cmpqb	0,in_db(pc)
	beq	_isr_nmi_user
	reti
_isr_nmi_user:
	movqd	1,tos		;in user
	br	exit_user
_isr_abt::
	bicpsrw	psr_ie
	movqd	2,tos
	br	exit_user
_isr_slv::
	bicpsrw	psr_ie
	movqd	3,tos
	br	exit_user
_isr_ill::
	bicpsrw	psr_ie
	movqd	4,tos
	br	exit_user
_isr_svc::
	bicpsrw	psr_ie
	movqd	5,tos
	br	exit_user
_isr_dvz::
	bicpsrw	psr_ie
	movqd	6,tos
	br	exit_user
_isr_flg::
	bicpsrw	psr_ie
	movqd	7,tos
	br	exit_user
_isr_bpt::
	bicpsrw	psr_ie
	addr	@8,tos
	cmpd	_ret_save,4(sp)
	bne	_isr_bpt1
	addr	@11,0(sp)	;really user just did ret
_isr_bpt1:
	br	exit_user
_isr_trc::
	bicpsrw	psr_ie
	addr	@9,tos
	br	exit_user
_isr_und::
	bicpsrw	psr_ie
	addr	@10,tos
	br	exit_user
_isr_rbe::
	bicpsrw	psr_ie
	addr	@11,tos
	br	exit_user
_isr_nbe::
	bicpsrw	psr_ie
	addr	@12,tos
	br	exit_user
_isr_ovf::
	bicpsrw	psr_ie
	addr	@13,tos
	br	exit_user
_isr_dbg::
	bicpsrw	psr_ie
	addr	@14,tos
	br	exit_user
_ret_save::
	bpt			;use bpt to return to debugger
_ret_save_bpt:			;to distinguish from reg bpt
	br	_ret_save	;in case user resumes

; There is an image of the 532 registers in RAM.  The image is called machState
; and is a MachState struct, defined in debugger.h.  The monitor's SET and
; various SHOW commands change and display this image.  When the RUN and
; STEP commands are executed, the image is copied to the actual registers
; using instructions like lprd and lmr.  Conversely, when the user code
; re-enters the monitor via a trap, the 532 registers are copied to the
; RAM image, using instructions like sprd and smr.  All this copying
; happens in the code which follows.

exit_user::
	sprd	sp,_machState+ms_isp(pc)
	lprd	sp,_machState+32
	save	[r0,r1,r2,r3,r4,r5,r6,r7]
	sprd	sp,r1		;r1 = &_machState
	lprd	sp,ms_isp(r1)
	movd	tos,r0		;return val = trap type	
	movd	tos,ms_pc(r1)
	movw	tos,ms_mod(r1)
	movw	tos,ms_psr(r1)
	sprd	sp,ms_isp(r1)
	sprd	sb,ms_sb(r1)
	sprd	fp,ms_fp(r1)
	sprd	intbase,ms_intbase(r1)
	bispsrw	psr_usp
	sprd	sp,ms_usp(r1)
	bicpsrw	psr_usp
	sprw	cfg,r2
	movw	r2,ms_cfg(r1)

	sprd	dcr,ms_dcr(r1)		;debug
	sprd	dsr,ms_dsr(r1)
	sprd	car,ms_car(r1)
	sprd	bpc,ms_bpc(r1)

	tbitb	cfg_m,r2
	bfc	x_no_mmu
	smr	ptb0,ms_ptb0(r1)	;mmu
	smr	ptb1,ms_ptb1(r1)
	smr	tear,ms_tear(r1)
	smr	mcr,ms_mcr(r1)
	smr	msr,ms_msr(r1)
x_no_mmu:

	tbitb	cfg_f,r2
	bfc	x_no_fpu
	sfsr	ms_fsr(r1)		;fpu
	movl	f0,ms_f+0(r1)
	movl	f2,ms_f+8(r1)
	movl	f4,ms_f+16(r1)
	movl	f6,ms_f+24(r1)
	movl	f1,ms_f+32(r1)
	movl	f3,ms_f+40(r1)
	movl	f5,ms_f+48(r1)
	movl	f7,ms_f+56(r1)
x_no_fpu:

	;user saved, now restore debugger
	lprd	mod,modtab_adr
	lprd	intbase,inttab_adr
	lprd	sb,0
	lprd	sp,dbsp(pc)
	lprd	fp,dbfp(pc)
	restore	[r1,r2,r3,r4,r5,r6,r7]
	movqb	1,in_db(pc)
	ret	0

_resume::
	save	[r1,r2,r3,r4,r5,r6,r7]	;monitor state
	sprd	sp,dbsp(pc)
	sprd	fp,dbfp(pc)
	movqb	0,in_db(pc)

	lprd	sp,_machState
	lprd	dcr,ms_dcr(sp)		;debug
	lprd	dsr,ms_dsr(sp)
	lprd	car,ms_car(sp)
	lprd	bpc,ms_bpc(sp)

	movw	ms_cfg(sp),r2
	lprw	cfg,r2

	tbitb	cfg_f,r2
	bfc	r_no_fpu
	lfsr	ms_fsr(sp)		;fpu
	movl	ms_f+0(sp),f0
	movl	ms_f+8(sp),f2
	movl	ms_f+16(sp),f4
	movl	ms_f+24(sp),f6
	movl	ms_f+32(sp),f1
	movl	ms_f+40(sp),f3
	movl	ms_f+48(sp),f5
	movl	ms_f+56(sp),f7
r_no_fpu:

	lprd	fp,ms_fp(sp)
	lprd	intbase,ms_intbase(sp)
	restore [r0,r1,r2,r3,r4,r5,r6,r7]	;clobbers sp
	bispsrw	psr_usp
	lprd	sp,_machState+ms_usp(pc)
	bicpsrw	psr_usp
	lprd	sp,_machState+ms_isp(pc)
	movw	_machState+ms_psr(pc),tos
	movw	_machState+ms_mod(pc),tos
	movd	_machState+ms_pc(pc),tos

	tbitb	cfg_m,_machState+ms_cfg(pc)
	bfc	r_no_mmu
	lmr	ptb0,_machState+ms_ptb0(pc)	;mmu
	lmr	ptb1,_machState+ms_ptb1(pc)
	lmr	tear,_machState+ms_tear(pc)
	lmr	msr,_machState+ms_msr(pc)
	lmr	mcr,_machState+ms_mcr(pc)
r_no_mmu:
	rett	0
@EOF

chmod 660 resume532.s

echo x - dblib.s
cat >dblib.s <<'@EOF'
;****************************************************
; SCN 2681 routines for debugger
;
; Note: These i/o routines are raw.  Do mappings
;       (e.g. cr -> nl) elsewhere.
;
; Uart numbers:
;   There are eight uart addresses currently decoded
;   in the address space:
;	 h'28000000 duart 0 (uart 0, 1)
;	 h'28000010 duart 1 (uart 2, 3)
;	 h'28000020 duart 2 (uart 4, 5)
;	 h'28000030 duart 3 (uart 6, 7)
;****************************************************

duart:		.equ	h'28000000
stat_reg:	.equ	1
data_reg:	.equ	3
in_rdy:		.equ	0
out_rdy:	.equ	2
	.program

bconv:	.word	75
	.word	110
	.word	134
	.word	150
	.word	300
	.word	600
	.word	1200
	.word	2000
	.word	2400
	.word	4800
	.word	1800
	.word	9600
	.word	19200
	.word	0		; end of table marker




;****************************************************
; _db_fgetc --  read a character from a uart into r0.
;
;     Enter: db_fgetc (<uart number>)
;      Exit: character in r0
;  Destroys: r0, flags
;****************************************************
_db_fgetc::
	enter	[r1],0
	movd	8(fp),r1	;r1 = uart number
	bsr	get_uart_adr
getchar_loop:
	tbitb	in_rdy,stat_reg(r1)
	bfc	getchar_loop
	movzbd	data_reg(r1),r0
	exit	[r1]
	ret	0

;****************************************************
; _db_fputc --  write character to a uart
;
;     Enter: db_putchar (<character>, <uart number>)
;      Exit:
;  Destroys: flags
;****************************************************
_db_fputc::
	enter	[r1],0
	movd	12(fp),r1	;r1 = uart number
	bsr	get_uart_adr
putchar_loop:
	tbitb	out_rdy,stat_reg(r1)
	bfc	putchar_loop
	movb	8(fp),data_reg(r1)
	exit	[r1]
	ret	0

;****************************************************
; _db_setbaud -- Set baud rate of uart.
;
;    Enter: db_setbaud (<rate>, <uart>)
;     Exit: r0 = 0 if Ok, nonzero else
; Destroys: flags
;****************************************************
_db_setbaud::
	enter	[r0,r1,r2,r3],0
	movd	12(fp),r1	;r1 = uart number
	bsr	get_uart_adr
	movd	8(fp),r0	;r0 = baud rate
	addr	@bconv,r2	; point to baud conversion table
	movqd	0,r3		; start with a zero offset
dbsbl1:	cmpqw	0,r2[r3:w]	; are we at the end of the table?
	beq	setbaud_err	; yes, exit with error now
	cmpw	r0,r2[r3:w]	; have a look at the table
	beq	dbsbl2		; matched, exit now
	addqd	1,r3		; move to next table entry
	br	dbsbl1		; loop to do next one

dbsbl2:	mulb	17,r3		; this moves the index into both
				; nibbles of r3, for the 2681 baud
				; rate register. 0xb becomes 0xbb
	movd	r1,r2		; get address of uart
	bicb	h'8,r2		; point to base of duart
	movb	h'20,2(r1)	; clear rx
	movb	h'30,2(r1)	; clear tx
	movb	h'40,2(r1)	; clear any errors
	movb	h'10,2(r1)	; clear byte pointer
	movb	h'13,0(r1)	; no rts, no parity, 8 bits
	movb	h'7,0(r1)	; no cts, 1 stop bit
	movb	r3,1(r1)	; set baud rate
	movb	h'80,4(r2)	; set ACR to set 2 (19.2 Kbps)
	movb	h'85,2(r1)	; enable rx & tx, set RTS for 2692
	movb	h'5,2(r1)	; enable rx & tx for 2681
	movb	h'0,13(r2)	; ensure RTS mode set
	movb	h'3,14(r2)	; set RTS on

	movqd	1,r0		;return value
	br	setbaudx
setbaud_err:
	movqd	0,r0
setbaudx:
	exit	[r0,r1,r2,r3]
	ret	0

;****************************************************
; Get uart base address.
;
; Enter: uart number in r1
;  Exit: uart base address in r1
;****************************************************
get_uart_adr:
	andd	7,r1		;be sure 0 - 7
	lshd	3,r1		;mult by h'8
	addd	duart,r1	;r1 = uart base adr
	ret	0
@EOF

chmod 666 dblib.s

exit 0

From ames!pacbell!zygot!ditka!kls@XN.LL.MIT.EDU Thu Mar 29 08:04:27 1990
Flags: 000000000000
Posted-Date: Thu, 29 Mar 90 1:32:33 PST
Subject: And away they go!
To: ditka!pc532-disks
Date: Thu, 29 Mar 90 1:32:33 PST
X-Mailer: ELM [version 2.2t PL7]
From: ames!ditka.UUCP!kls@XN.LL.MIT.EDU (Karl Swartz)
Status: O

This afternoon I gave CSC a check for 41 disks; 4 more for
Australia are waiting for a late wire to come in and should
be taken care of by Friday.  I was told that they would get
all the drives shipped within the next few days, so expect
them starting early next week.

Each shipment will have its own invoice -- you'll need this
invoice number, along with the drive's serial number, if you
need any warranty work to be done.  If any problems arise
please let me know.

Now if you'll all excuse me, I'm going to go rest up for a
month or so!  :-)

PS: If CSC still has any of these drives in a month I *may*
    consider another group buy for those people who couldn't
    get a drive this time around, or want more.  No promises
    and DO NOT send orders now, but keep it in mind if you
    think you (or a friend) might be interested.

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148


From owner-pc532%daver@mips.com Thu Mar 29 02:21:08 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
X-Mailer: Mail User's Shell (6.2 5/11/88)
To: pc532@daver.bungi.com
Subject: Re: esoteric parts
Date: 28 Mar 90 22:11:32 PST (Wed)
From: george@wombat.bungi.COM (George Scolaro)
Status: O

[In the message entitled "esoteric parts" on Mar 28, 21:40, daver!uunet!uunet!munnari!sibyl.eleceng.ua.oz.au!ian writes:]
> 
> 
>    1)	"Real Time Clock plus RAM (NVRAM)"	DS1287 <- just a clock
> 		
>    2)	"Real-Time Clock Plus RAM (replacement
> 	 for IBM AT computer clock/calander)"	DS1285 <- just a clock
> 
>    3)	"Smart Watch (watch or clock, nonvolatile
> 	 RAM control) with socket, battery.	DS1216  this is for srams
> 						DS1216C and so is this
> 						DS1216E <- use this one
> 
>    4)	"Smart Watch, Calendar/Clock with embedded
> 	 Lithium Cell.				DS1216F <- this is for 32 pin
								eproms 

The actual part we used is the DS1216E. It is for 28 pin Jedec EPROMS. In
normal use the EPROM works as always, but if a special 64 bit pattern is
detected by the Dallas chip, it disables the EPROM (since it sits under
the EPROM) and then goes into the clock mode, sending the data out via
one of the data pins. Of course to use it, the code that is accessing the
clock must not be in EPROM (obviously!).

regards,

-- 
George Scolaro
george@wombat.bungi.com                [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Thu Mar 29 07:55:17 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: athos%eyrie@labtam.oz.au
To: pc532%labtam@daver.bungi.com
Subject: PostScript board
Date: Thu Mar 29 10:00:02 1990
Status: O

> From: gatech.edu!mm!ken@munnari.oz (Ken Seefried iii)
>
> What ever happened to the Aussies that were talking about the
> postscript board?


I don't know if Marc Boschma is going to beat me in replying to this first, but
the design of the "PS532" seems to have been put on hold at the moment while
we concentrate on building at least one of our PC532s (we only have two boards
here at the moment, and mine is the only one that's starting to look slightly
"built") as well as organizing operating systems, hard disks, etc.  (Not to
mention the day-to-day hassles of work)

Last I saw the design, it was in the form of 32532 software, with critical
functions implemented in a CSU (what NatSemi calls a Custom Slave Unit).
I suspect you'll hear more details later.


Oh, and Dave, I was wondering why the mailing list went quiet for half a week
or so......
___________________________________________________________________________
David Burren (Athos),			ACSnet: athos%eyrie@labtam.oz.au
img Consultants,
G.P.O. Box 3304GG, Melbourne,		- DON'T TRUST THE MAIL HEADER -
Australia 3001


From owner-pc532%daver@mips.com Thu Mar 29 07:55:18 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Download CRC question for someone...
Clarity-Index: null
Threat-Level: none
Quote-Of-The-Moment: 's/./&&/g' Tom sed expansively.
Quote-Of-The-Moment: Termoter messesers temperrs.  -- A 4th grader
What-Was-Meant: A thermometer measures temperature.
Date: Thu, 29 Mar 90 01:06:52 CST
From: Jon Loeliger <loeliger@convex.com>
Status: O

Hi guys,      (Are there, in fact, any women reading this list?)

Would someone please compute the correct check sum for the following
test text:

SunOS Release 4.0.3 (valid.4.0.3.sunthree) #1: Mon Aug 14 16:14:10 CDT 1989
                                                                          
There is a newline (\n) on the end of that line for a total of 76 bytes.
(I know I should be downloading *real* programs (rogue) by now, I'm just
tryingto get *anything* into memory...)

My copy of Bruce's download program says:
	Length=76 CRC=61213

Upon return to the monitor, I get:
	CRC error, received 7434, expected 61210, length 76

When I `( stty -cstopb cs8 -parenb ; download motd ) | od -c` I get:
0000000    :   L  \0  \0  \0   S   u   n   O   S       R   e   l   e   a
0000020    s   e       4   .   0   .   3       (   v   a   l   i   d   .
0000040    4   .   0   .   3   .   s   u   n   t   h   r   e   e   )
0000060    #   1   :       M   o   n       A   u   g       1   4       1
0000100    6   :   1   4   :   1   0       C   D   T       1   9   8   9
0000120   \n 035 357

Now (in base 8) 357 * 400 + 35 =  61213 (base 10).
I've byte swapped 357 and 35, masked off the high bit, and diced and
sliced and haven't been able to get either 7434 or 61210 in any fashion.

Another clue for the Sherlockian crowd:  Sometimes a return will regain
the consciousness of the monitor, other times it won't.

Mind you, the whole text actually makes it into memory just fine:

CRC error, received 7434, expected 61210, length 76
Command (? for help): dump 2000 100
00002000 53 75 6E 4F | 53 20 52 65 | 6C 65 61 73 | 65 20 34 2E SunOS Release 4.
00002010 30 2E 33 20 | 28 76 61 6C | 69 64 2E 34 | 2E 30 2E 33 0.3 (valid.4.0.3
00002020 2E 73 75 6E | 74 68 72 65 | 65 29 20 23 | 31 3A 20 4D .sunthree) #1: M
00002030 6F 6E 20 41 | 75 67 20 31 | 34 20 31 36 | 3A 31 34 3A on Aug 14 16:14:
00002040 31 30 20 43 | 44 54 20 31 | 39 38 39 0D | 00 00 00 00 10 CDT 1989.....


Will trundling down to the lab and placing Bruce's new EPROM image
onto some new sand solve this problem?

BTW, I made one small change to the download program that other UNIXites
might want to inherit.  Since I'm not writing to a PORT, but instead
stdout, I'd like my CRC/length message to go to stderr, not stdout.

Try it, you'll like it.
jdl

From owner-pc532%daver@mips.com Thu Mar 29 21:10:36 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: My earlier blathering about possible CRC errors
Clarity-Index: a bit mumbled
Threat-Level: none
Date: Thu, 29 Mar 90 08:12:02 CST
From: Jon Loeliger <loeliger@convex.com>
Status: O

OK, folks,

I figured out the rest of the CRC mystery.  (For those *still* intent
on solving it themselves, I now know that all the clues are present
in my previous posting to enable one to figure out ws wrong...)

So, everyone remember this little ditty off the (Sun 4.0.3) stty man page?:

     [-]onlcr    Map NEWLINE to RETURN-NEWLINE on output.  With a
                 `-', do not map.

Yep, I had  onlcr  set.  So, that newline (\n, ie, 0x0a) gets translated
into return-newline (0x0d, 0x0a).  I get a 0x0d stuffed into memory
instead of 0x0a, producing a value of 0d - 0a = 3 difference (61210
vs. 61213).  Occasionally (?), the return gets sucked up by the monitor.

So, today's lesson in terminal characteristics either use -onlcr or -raw
in addition to cs8 -parenb and -cstopb.

Sorry to bore you all with this,
jdl

From owner-pc532%daver@mips.com Fri Mar 30 17:42:41 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 30 Mar 1990 06:11:23 +1000
From: ian@sibyl.eleceng.ua.oz.au
To: pc532@daver.bungi.com
Subject: GAS patches
Status: O

I have merged in David Taylors gas patches so they are now contained
by the patches on augean.ua.oz.au 

Thus the new gas patch file is

   gas-1.35.patch1.1.Z


From owner-pc532%daver@mips.com Fri Mar 30 17:51:06 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 30 Mar 1990 06:53:50 +1000
From: ian@sibyl.eleceng.ua.oz.au
To: pc532@daver.bungi.com
Subject: Re:  Assembler syntax.
Status: O

Bruce Culbertson writes:
 > Hi gang,
 > 
 > I want to throw my two bits in on assembler syntax.
 > I feel there should be a lowest level where the abstaction stops.
 > Assembler is that level.  I like everything to be explicit at the
 > assembler level.  My assembler has no defaults.  If want some addressing
 > mode, you must use @, (pc), or whatever.  Otherwise, you get
 > immediate.

Couldn't agree more.

 > Given this rule, what is the point of the # or $?
 > I do not use # or $.

Well, arguably you have made the default
immediate.

 > I guess I violated my rule in one minor respect.  For br, bsr, and (pc)
 > offsets, I use "symbol", not "symbol - *".

Yep. GAS does the same. I'd like to propose a new rule. Defaults are OK
but they should be instruction, not symbol dependent. Thus br takes only
pc relative addresses, so it is OK to default to pc relative. Also immediate
operands are illegal with "addr" so it is OK to make the default something
which is not immediate. As a matter of style, I would prefer to not use this
feature though.

 > I made gcc generate code which was as position independent as possible.
 > I use (pc) addressing mode primarily.  Real position independence is
 > hard to achieve, however, because of things like pointer initialization
 > at link time.

I can see the value in real position independence for run time linking
of shared libraries, but I can see little value (or harm!) in making
the compiler prefer pc relative references. They should be the same
speed unless the size of the displacements is normally smaller for pc
relative.  Since in most compiled code, data is in another segment, I
would have thought that the displacements would have to have all been
4 byte in either case.

 > I assume that SB is always set to zero.  That way, "*foo" (foo a global)
 > can be referred to as "0(_foo(sb))".

I was caught by the static base stuff. GCC wanted to generate rtl which would
be disp(symbol) if translated literally. Of course the 32k can't do that so
you generate disp(symbol(sb)) which is equivalent iff sb == 0. I found
that on the icm3216, sb is munged by the kernel during context switches so
I had to add some #ifdef SB_TRASHED ... #endif lines.


From owner-pc532%daver@mips.com Fri Mar 30 17:52:56 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 30 Mar 1990 07:09:38 +1000
From: ian@sibyl.eleceng.ua.oz.au
To: pc532@daver.bungi.com
Subject: Assembler syntax.
Status: O

ian@sibyl.eleceng.ua.oz writes:
 > Current assemblers I know of require
 > 
 >                         -----------------------------------------
 >                         |  IM_C |  IM_S | ABS_C | ABS_S |  BRA  |
 > ------------------------|-------|-------|-------|-------|-------|
 > | 1. NS Instruction Set |       |       |       |       |       |
 > |    Reference Manual   |       |       |   @   |   @   |       |
 > |-----------------------|-------|-------|-------|-------|-------|
 > | 2. NS 5.2.2 as        |   $   |   $   |       |       |       |
 > |-----------------------|-------|-------|-------|-------|-------|
 > | 3. Sequent            |       |   #   |   @   |       |       |
 > |-----------------------|-------|-------|-------|-------|-------|
 > | 4. Encore             |       |   #   |   @   |       |       |
 > |-----------------------|-------|-------|-------|-------|-------|
 > | 5. Original Gas       |       |   #   |   @   |       |       |
 > |-----------------------|-------|-------|-------|-------|-------|
 > | 6. Ian's Gas          |       |       |   @   |   @   |       |
 > -----------------------------------------------------------------
 > 
 > I am accepting votes for the "correct" syntax to use. (And also
 > corrections to the above table). I personally dislike having different
 > syntax for symbols and constants which I think means 1. or 2. Further,
 > GAS uses BSD style directives so it seems sensible to use BSD style
 > syntax which basically means 1.

I was under a misaprehension here. When NS where using BSD 4.1 they used
1, when they were using SysV they used 2. However, it seems that these
are unrelated to the operating system. A quick check on a VAX running 4.3 BSD,
and Sun3 and a Sun4 both running SunOs 4 revealed

                        -----------------------------------------
                        |  IM_C |  IM_S | ABS_C | ABS_S |  BRA  |
------------------------|-------|-------|-------|-------|-------|
| 7. VAX 4.3 BSD        |   $   |   $   |       |       |       |
|-----------------------|-------|-------|-------|-------|-------|
| 8. 68k SunOS 4        |   #   |   #   |       |       |       |
|-----------------------|-------|-------|-------|-------|-------|
| 9. Sparc SunOS 4      |       |       |  N/A  |  N/A  |       |
|-----------------------|-------|-------|-------|-------|-------|

There is no absolute mode on a sparc (you load a register and then
load register indirect basically).

So in terms of precedents, 2 is about as BSDish as you get.

(I am saving all your responses and will present a summary soon. Anyone
who has had their mail to ian@sibyl.eleceng.ua.oz.au bounce; sorry it was
a local problem with my Internet gateway and has been fixed.)


From owner-pc532%daver@mips.com Fri Mar 30 18:16:34 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
From: dlr@daver.bungi.com (Dave Rand)
Date: Fri, 30 Mar 90 14:44:45 PST
X-Mailer: Mail User's Shell (7.0.1 12/13/89)
To: pc532@daver.bungi.com
Subject: Re: Question again.
Cc: phil@unicorn.wwu.edu
Status: O

[In the message entitled "Question again." on Mar 30,  8:51, Phil Nelson writes:]
> Well, I will try again.  I am interested in your pc532.  BUT I don't know
> how much it has cost people to "finish" the board.  (i.e. get all the parts
> to complete a working board (current configuration))   Please answer soon.
> I would like the answer before ordering the board and I would like to be
> able to order a board after knowing more of the costs.
> 
> Phil Nelson
> phil@unicorn.wwu.edu

The bare board is $200. Misc. parts (decoupling caps, sockets, AS series,
etc) will run about $300. MSI parts will be about $100 (duarts, SCSI, etc).
LSI parts will be about $1,000 (CPU/FPU/ICU). DRAM is about $90/meg, 4 meg
minimum.

All of these prices are approximate, and will be subject to change depending
on the state of your parts cabinet and local vendors.

Count on a final project cost of $1500-$15,000 :-) 

Disk and tape will also factor in - how much disk do you want? What type
of terminal will you use? Tape? What kind? Floppy?

Perhaps some of the other folks would like to offer comments on assembled
prices...


-- 
Dave Rand
{pyramid|hoptoad|sun|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

From owner-pc532%daver@mips.com Fri Mar 30 20:08:12 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 30 Mar 90 21:04:44+1100
From: s861298@minyos.xx.rmit.OZ.AU (Marc A. Boschma)
To: pc532@daver.bungi.com
Subject: PostScript board...
Status: O

>From: athos@eyrie@labtam.oz
>> From: gatech.edu!mm!ken@munnari.oz (Ken Seefried iii)
>> What ever happened to the Aussies that were talking about the
>> postscript board?

Its still being designed. Ive spent alittle time looking at the public domain
PostScript interpreters, and most of them are too buggy.
 
>I don't know if Marc Boschma is going to beat me in replying to this first, but
	yep you did...
>the design of the "PS532" seems to have been put on hold at the moment while
>we concentrate on building at least one of our PC532s (we only have two boards
>here at the moment, and mine is the only one that's starting to look slightly
>"built") as well as organizing operating systems, hard disks, etc.  (Not to
>mention the day-to-day hassles of work)

Work is really taking up alot of time. Project deadlines are real pains.
Hopefully I'll be able to get some more time for it next month (crossed fingers)

>Last I saw the design, it was in the form of 32532 software, with critical
>functions implemented in a CSU (what NatSemi calls a Custom Slave Unit).
>I suspect you'll hear more details later.

I haven't progressed much past that stage. Documentation on CSU's for 32000
CPUs are abit thin on the ground at the moment (any would greatly be
appreciated). The actual PostScript interpreter is not that much work at
all (except for the graphics functions, which with hardware support should
be ok...)

I'm also in touch with Cogent who have written (PIX a X11/NeWS clone) and will
hopefully be working with them in getting that into the public domain and thus
at the same time getting PostScript as well.


----------------------------------------------------------------------------
Inteligent Networks		Marc A. Boschma
Telecom Australia		ACSnet/CSNET: marcb@minyos.rmit.oz
5th Floor,			UUCP: ...!uunet!munnari!minyos.rmit.oz!marcb
459 Lt. Collins St.		ARPA: marcb%minyos.rmit.oz@uunet.uu.net
Melbourne, Australia. 3001
				or

			img Consultants
			GPO Box 3304GG,
			Melbourne, Australia. 3001

From owner-pc532%daver@mips.com Fri Mar 30 22:31:58 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Date: Fri, 30 Mar 90 03:50:34 EST
From: budd@bu-it (Phil Budne)
To: pc532%daver@uunet.UU.NET
Subject: parts...
Status: O

>From dec 20th;

Jerry asked;
>> What substitutions are possible for the 74xxnnn parts? George has specified
>> mostly 74ALSnn and 74ASnn, and none of the catalogs I've checked have these.
>> Can I substitute 74F or 74HCT? Maybe someone could post a table of
>> acceptable substitutions?

George replied;
>Nope. All parts must be as specified except for the 74als14, it can be
>whatever you want, since its only used in the reset area. Remember that the
>board runs at 25Mhz, and each ns counts, and 74ASxx is typically 1 or more ns
>faster than 74Fxx stuff.

Since then, in various messages George has said where substitutions
are ABOSOLUTELY forbidden, and where the brave may try using F series
parts.  however, there are still a few 74ASxxx parts people haven't
asked about substitutions for!  Here is the scoreboard (of non-kit
parts) by my records;

74AS74			74F74 ok
74F138			already F series!
74AS174			74F174 ok
74AS280			74F280 better!!

74ALS14			anything!
74ALS1034A		74AS1034A ok

MUST be 74ASxxx;
74AS374			NO SUBS
74AS1004A		NO SUBS
74AS1034A		NO SUBS

not yet asked;
74AS00			??
74AS646			??
74AS258 (or 74AS158)	??

P.S. Does anyone have a source for 5pf caps?

From owner-pc532%daver@mips.com Sat Mar 31 02:56:56 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
To: pc532@daver.bungi.com
Subject: Re: Wrong address - good questions! 
Clarity-Index: null
Threat-Level: none
Quote-Of-The-Moment: Termoter messesers temperrs.  -- A 4th grader
What-Was-Meant: A thermometer measures temperature.
Date: Fri, 30 Mar 90 09:36:21 CST
From: Jon Loeliger <loeliger@convex.com>
Status: O

> [In the message entitled "Need Advice" on Mar 29,  9:38, Roger Hanscom writes:]

> I'd really like a high performance, 32-bit machine, but am unsure of
> my ability to build something like the pc532 (and get it working @:^) )
> ...
> I've built lots of Z80 stuff from kits, and wire-wrapped some simple cards.
> ...  I tried to build up a Xerox 820-1 from a bare board,
> and never got it running. 

Sounds like me.  I hate to sound like The Living Testimony here, but
I think I sent a message *amazingly* similar to yours about 4 months
ago in early December.  I've had nothing more than some home-brew Z80
sorts of Experiences, right down to owning a (working) 820 board.  I
too seriously doubted my ability to build one of these Snazzo PC532
boards let alone get it working...  I took the leap of faith and now
I am Converted.  I actually have a working pc532 on my desk that is
now plugged into the back of my Sun.

To give credit where credit is due, I don't think that my ability was
really the critical factor in the whole system.  Rather, I think the
ease with which it did come up is a testimony to a very nice, clean
design by George (and Dave).  Furthermore, they (and others on the list)
have proven again and again to be *more* than willing to help both
in further development and in answering questions.

> I'm tired of the
> INTEL/IBM 88/86/286/386 crap and the brain-damaged architecture they
> use.

As well you should be.  (Sigh...)

> Do you think that a guy with limited diagnostic resources available to
> him can make a go of this??  It is, after all, a fairly expensive
> experiment to indulge in.

IMHO, I think that some of the technical things you have mentioned indicate
you probably have the ability to make the board.  If you make a fairly
carefull effort to follow the design and follow Good Construction Advice,
get the right parts and all, it should just Come Up.

Tell you what (read: neck on limb).  I have access to some fairly reliable
and good lab equipment (not that *I* know how to use it all :-).  If you
decide to build the board, completely populate it, and can't bring it up
after some reasonable debugging effort and find yourself still SOL and
Up The Creek, and are willing to do the postage number, I'll help look
at the board here as best I can.

Having said that, let me clarify a few things.  No guarantees and no
promises from a dedicated Hardware Jock.  This is strictly a Good Faith
offer on a time-available basis from an admitted Software Weenie.
I'm willing to help in what ways I feel that I can, just as many people
on the list have already done.

One thing you might be concerned about is how much *time* you are willing
to sink into the whole project.  I spent a couple of weeks tracking down
parts despite the fact that all the Tough Ones were supplied by Dave and
George.  Once all the chips are down, I think there is still a lot of
time to be sunk into the whole software issue...  What I'm saying,
naturally, and you already know this, is don't expect a simple turn-key
system.

I think you can do it, though.

>             roger             rzh@lll-lcc.llnl.gov

Gross generalizations not from the desk Eugene Miya but rather,
jdl
------------------------------------------------------------------------------
Jon Loeliger			    | loeliger@convex.com
Convex Computer Corporation	    | I'm the thirteenth at your table,
3000 Waterview, Richardson TX 75080 | I'm the uninvited guest.  - Marillion


From owner-pc532%daver@mips.com Sat Mar 31 03:59:43 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
X-Mailer: Mail User's Shell (6.2 5/11/88)
To: pc532@daver.bungi.com
Subject: Re: parts...
Date: 30 Mar 90 22:26:20 PST (Fri)
From: george@wombat.bungi.COM (George Scolaro)
Status: O

[In the message entitled "parts..." on Mar 30,  3:50, Phil Budne writes:]
> 
> Since then, in various messages George has said where substitutions
> are ABOSOLUTELY forbidden, and where the brave may try using F series
> parts.  however, there are still a few 74ASxxx parts people haven't
> asked about substitutions for!  Here is the scoreboard (of non-kit
> parts) by my records;
> 
> 74AS74		74F74 ok
			but 74AS74 better
> 74F138		already F series!
> 74AS174		74F174 ok
			but 74AS74 better
> 74AS280		74F280 better!!
	Actually, the 74F280 is not good, the 74F280A is ok, but
	the 74F280B is better. National doesn't make the A or B, but
	Signetics does.
> 74ALS14		anything!
> 74ALS1034A		74AS1034A ok
> 
> MUST be 74ASxxx;
> 74AS374		NO SUBS
			74F374 ok
> 74AS1004A		NO SUBS
> 74AS1034A		NO SUBS
> 
> not yet asked;
> 74AS00		??
			NO
> 74AS646		??
			74F646 equal
> 74AS258 (or 74AS158)	??
			NO

regards,

best regards,

-- 
George Scolaro
george@wombat.bungi.com                [37 20 51 N / 122 03 07 W]

From owner-pc532%daver@mips.com Sat Mar 31 06:37:07 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: Re: Question again.
To: pc532@daver.bungi.com
Date: Sat, 31 Mar 90 2:50:12 PST
X-Mailer: ELM [version 2.2t PL7]
From: ditka!kls (Karl Swartz)
Status: O

> Well, I will try again.  I am interested in your pc532.  BUT I don't know
> how much it has cost people to "finish" the board.  (i.e. get all the parts
> to complete a working board (current configuration))

I was lucky enough to get one of the initial kits, which included
the CPU/FPU/ICU chip set, SCSI controllers, DUARTs, the obscure
sockets and connectors, and a few random bits like the resistor
packs.  That cost $450 including the PCB.  Starting from just the
raw board ($200) there's maybe $1,250 worth of parts there if you
go out and buy 'em on your own.

Other big ticket items included 4MB memory ($320), case and power
supply ($150), and a disk ($960).  On top of the I spent another
$170 on the remaining ICs, discretes, and random other bits.

That comes to a grand total of $2,050 to get the thing up to its
current state.  I still need software, probably a tape drive, and
an Ethernet controller ... no guess on prices for these.

Parts of the whole picture that may vary for you:

    VLSI ICs
	Tack on another $1,000 if you're just buying a board now
	unless Dave wrangles another deal with National.

    disk drive
	You might pick up something for a few hundred bucks, or
	you could spend gigabucks.  Depends on what you want.

    terminal
	Gotta have a way to talk to the sucker once it's up and
	running.  I've got ditka here and can cu over to the '532
	so I didn't need to dump money here.

    bits
	Your junk bin might be better than mine, though you may
	not have access to as nice a selection of surplus stores
	as I do.  Also, I socketed everything, which was possibly
	a bit overboard.  What the hell, another few dozen bucks
	on sockets wasn't gonna kill me.

Does that give you a better idea?

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From owner-pc532%daver@mips.com Sat Mar 31 08:19:01 1990
Flags: 000000000000
Reply-To: pc532@daver.bungi.com
Subject: Re: parts...
To: pc532@daver.bungi.com
Date: Sat, 31 Mar 90 3:14:35 PST
X-Mailer: ELM [version 2.2t PL7]
From: ditka!pc532-disks (pc532 disks)
Status: O

> P.S. Does anyone have a source for 5pf caps?

Being here in Sillycon Valley has been an enormous asset in
building this thing -- the only parts not in the kit that I
could *not* obtain locally were the {AS,ALS}1034A's.  I can
pick up the caps for you if you like.

How many people would be interested in buying a kit of all
the parts for the new run?  Having just gotten done with the
disk drive group buy I'm not exactly eager to volunteer more
of my time, but if there's enough demand and nobody else is
willing to do it I'll entertain thoughts of putting together
parts kits for folks who don't mind me adding on a small cut
for my time.

If you're interested, send mail to

    pc532-parts@ditka.uucp

or to the pc532 mailing list at daver.  DO NOT send mail to
me -- tax day is coming up quickly and I'll be out of town
the second week of April, so I want to keep this stuff out
of the way of my normal flood of mail.

--
Karl Swartz			 |UUCP	uunet!apple!zygot!ditka!kls
1-408/223-1308			 |INet	zygot!ditka!kls@apple.com
"I never let my schooling get in |BIX	kswartz
the way of my education."(Twain) |Snail	1738 Deer Creek Ct., San Jose CA 95148

From bobm@convex.com Sat Mar 31 14:59:43 1990
Flags: 000000000000
From: bobm@convex.com
To: budd@bu-it (Phil Budne)
Subject: Re: parts... 
X-Quote-Of-The: Charisse: It sounds like it's a bitch to get mail through
                          your gateways.
                DEC FE:   We like it that way.  Keeps the Morris worms out.
                Charisse: Hey, he's a good guy. I used to rent my house to him.
                DEC FE:   (speechless)
X-Gnat-State: Grummet
Date: Sat, 31 Mar 90 13:45:41 CST

That's a really useful list.  Thanks!

					K<bob>

