On December 16, Bill Bradford wrote:
> > > I have little doubt about the appropriateness... of your response.
> > > Care to say when its appropriate to own three S/390's?
> > It's wholly inappropriate. He should give one to me.
>
> No, you've already over-filled your Cray quota; you should have to give
> one of those away (like say, the EL98, to me..) before you can acquire
> any more "big balls" hardware. 8-)
Ahh, you THINK so. ;)
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
> From: Tony Duell <ard(a)p850ug1.demon.co.uk>
> > Well, most of us (except for Tony) have areas that we are not expert
in, or
>
> Whereas I'm not an expert in any area, right???
Wrong. Accept a complement, okay? ;>)
> I am strongly of the opinion that you can't teach creativity. And thus
> you can't teach somebody to be a good programmer or a good electronic
> designer. Yes, there are things that such people need to know (and those
> can be taught, but equally good programmer/designers tend to be
> interested enough to teach themselves a lot of it).
OTOH, methodology certainly *can* be taught. Unfortunately, though, either
it isn't being taught, or the student just doesn't "get it." Some of the
crap I've seen which was written by CS degree-holders has been truly
mind-boggling due to a complete lack of structure or logic in the code.
> So I don't think there's _any_ correlation (or at most a very weak one)
> between qualifications and ability as a programmer/designer.
Agreed, absolutely.
> > Should programmers be licensed? Sure makes me wonder . . .
>
> I don't think so. I've seen enough 'qualified' people who I'd not trust
> anywhere near anything I owned. I've also met a few totally unqualified
> people who I'd be happy handing a toolkit to and letting them loose in my
> workshop, knowing that they'd do no real damage.
>
> And 'licenses' almost always come from 'qualifications' :-(
A test-based license is what I had in mind, but this raises all kinds of
problems (such as who designs and administers the exam, etc.) so in the end
it is probably better that the practitioners of the craft do the "weeding
out" themselves.
Personally, I'm glad to out of programming professionally, although it
remains a favorite hobby of mine. I just got so tired of having to explain
the difference between a "string" and a "character array" to some of these
folks . . . over and over . . . I could tell stories you probably wouldn't
believe, but the memory of them is causing me to lose my lunch so I think
I'd better just log off . . .
Glen
0/0
On December 16, Bill Bradford wrote:
> > That would be something I'd be up for trying...if I can find a chunk
> > of core of low enough density to trace the wiring in. There are some
> > nice low-density planes on eBay right now, but they are priced WAY too
> > high in my opinion.
>
> I've still got these two UNIBUS core planes (H215), but they're probably
> better suited for use in a DEC system instead of being deconstructed.
Yes...I will *not* deconstruct DEC core, unless it's nonfunctional
and unrepairable.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
On December 16, ajp166 wrote:
> The older large ferrite core is easier to work with though
> much slower. The bigger cores produce a larger output
> when they switch but the cycle times are in the
> 3-5uS range. The later is helpful for demos as nothing
> is too fast.
I wonder if it would be possible (and practical) to use a
microcontroller, perhaps a PIC, to act as a core controller. Use the
A/D and D/A hardware to handle the drive and sense stuff, and do all
the timing in firmware...making it easily tweakable.
That would be something I'd be up for trying...if I can find a chunk
of core of low enough density to trace the wiring in. There are some
nice low-density planes on eBay right now, but they are priced WAY too
high in my opinion.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
>Well, I suppose every chip must aspire to mediocrity. :-P
Ok... I guess it took another Mac user to see my point.
I didn't doubt for a moment that the AMD chip was fully compatible with
any other Intel compat OS or software... just that it was REALLY REALLY
sad that they had to stamp it with windows propaganda as if windows was
the only thing out there that mattered.
-c
On Dec 16, 14:58, Gunther Schadow wrote:
> However, there are a few more issues to resolve first. The
> little 16-pole ribbon cable that has DIL chip-like plug on
> both ends that go into a chip-socket. That plug is bent and
> pins are broken off. Seems like that happnes all the time.
> Do I have to and if so how can I replace this? This cable
> runs between the backplane and, I guess, the limited function
> front panel.
Assuming you can afford to shorten the length of the cable by the amount
you'd lose by cutting off the DIL plug, it shouldn't be too hard. You can
buy 16-pin IDC DIL plugs quite easily. The quick-and-dirty way to crimp
one onto the cable is to take a piece of wood (metal is better but much
more work) and shave it so it fits neatly between the pins, and then shave
it down so it's the same depth as the pins are long. Place the cable in
the plug, insert the whole lot in a smal vice and gently tighten it up.
The piece of wood will prevent the pins from bending while you do this.
> Do I need this, is the limited function front panel needed
> at all? What's the function of the 16 lines, I assume
I don't know. If you'd asked this a week or two ago, I might have been
able to look it up in the PDP-8/A handbook I had on loan, but I've returned
it. :-( I think you do need some of the switches, but I'm not sure.
Have you looked at the print sets on some of the PDP-8 websites? David
Gesswein's page at http://www.pdp8.net/query_docs/query_all.html is a good
place to start. More specifically, follow the link labelled "244" from
there, then "245" and you'll be able to download a 1-page diagram of the
Limited Function Board.
--
Pete Peter Turnbull
Network Manager
University of York
How can I detect end of file while reading a text file?
10 print chr$(4)"Open mytextfile"
20 print chr$(4)"read mytextfile"
30 input a$
40 rem process process process
50 if what who how then 30
60 print chr$(4)"close mytextfile"
hep me please! (trying to write a dumb line editor)
I have two NewBrain MD computers with all cables and software including
bespoke Word Processor and Database. Two Data Recorders are also included. In
addition I have a pair of different 5.25" disk drives in a single unit with
the drive controller to fit to the underside of the computer. None of the
equipment has been used for some time, but is packed in original boxes and
complete with instruction booklets. Would be prepared to discuss offers.
Area -- North East UK
Graham C
Website: grahamcarling.com
In a message dated 12/16/01 2:54:15 PM Pacific Standard Time,
rhudson(a)cnonline.net writes:
>
> Did a person string those cores with a needle and
> "thread", or was it done by machine?
>
>
My stepmother worked for Hughes Aircraft in LA assembling core memory by hand
under a microscope. She was making 4X4 panels IIRC. This had to be in the
1960s I bet.
Paxton
Astoria, OR
> From: SUPRDAVE(a)aol.com
Gee, a message from an AOL user with no HTML . . . imagine that . . .
> Kwanzaa is NOT a real holiday.
Okay, I'll bite: why isn't it?
Glen
0/0
On December 15, Richard Erlacher wrote:
> Well, perhaps the reason for all the meetings and other work you find
> uninteresting is that it's necessary to arrive at a firm specification for what
> you have to build before you go off and build it. Since the coding, compiling,
> and debugging only represent about 5% of the task, the bulk of the work has to
> happen sometime, and that's what the "other" stuff is.
Some documentation and speficiation has to happen, sure. But most
of the industry seems to have lost sight of the fact that these are
*overhead tasks* that are secondary to the job of *building
something*. It gives suits a reason to take home a paycheck...they
can shuffle paperwork and Powerpoint bullshit all they want; it
rarely contributes to the finish product.
It's not an issue of my finding it "uninteresting"...I write code.
That's what I do best. If I'm doing something other than writing
code, I'm likely wasting my time...or worse, someone else's...because
if I'm not writing code I'm probaby doing something I'm not
particularly good at.
I'm not trying to be argumentative here...though it may sound that
way, please don't take it as such.
Again I will qualify my statements as pertaining to sub-million-line
development projects, not huge multi-million line behemoths.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
On December 16, UberTechnoid(a)home.com wrote:
> Remember the (iirc) Compaq ad. Thier 286 had a meg of static ram onboard.
> The ad depicted an empty desk with two tire tracks burt into it and a
> surprised user behind.
Static RAM? Are you sure? I've never heard of static RAM in a
PeeCee. That's neat.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
From: Gene Buckle <geneb(a)deltasoft.com>
>belongs with it. Does anyone have a Series 100 box that could give me
>the measurements and connector orientation & location of the floppy
>cable?
Nothing magic. the last one I had used was from a PC.
>Secondly, I don't know what "brand" SCSI controller is built into the
>board. The SCSI chip seems to be an NCR 5830, but that leads me nowhere
>in relation to whether or not it's an Adaptec or other model controller.
>I need to know the brand because the hd formatting software needs to
>know it.
Your applying PC logic to it. It's is not Adaptec, i'ts just SCSI
(SCS1 or II) host and the NCR5380 is one of the early and common
chips used for that.
The brand applies to the "other" board, what is known as a SCSI
bridge board. Adaptec, Xybec, WD and other made them. You
need to know what board and what drive to do the formatting. If
you dont mind hacking Z80 code you can go frm an AMPRO LB
with SCSI to a smaller SCSI drive (64mb or less, or the rest will
be unused).
Allison
People on here have talked about people on eBay taking a perfectly good
working machine and selling it off piece by piece but this takes the
capacitor screwdriver, soldering iron and sucker....
http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=1309283581
This person? is selling 40 little plastic thingies that go under a key on
the Commodore 128's keyboard along with a spring!!!
Bryan
Excuse while I go bang my head against a wall... Did you know if you do that
for an hour you burn 150 calories?
> From: CLeyson(a)aol.com
> Thanks to AOL I can't turn this feature off :-(
Yes, you can! I have posted numerous messages to this list (and others)
>from an AOL account in the past and never sent anything but plain text.
Glen
0/0
> There's a big difference between writing code to solve problems and being
> a software engineer. Designing, coding, and compiling is only 40% of the
> battle. Hopefully you're also spending some time planning and testing.
To me planning and testing are such obviously important parts of any
development process that I didn't mention them in my original post,
assuming (I hope correctly) that most everyone on this list is as
old-fashioned as I am ;>)
> We recently interviewed an electronics engineering graduate who didn't
know
> the difference between NPN and PNP transistors !! What do they teach kids
> these days ??
I repeat, the "faculty" of the "institution" which issued this fellow a
degree should be tarred, feathered, and run out of town on a rail.
Glen
0/0
From: Gene Buckle <geneb(a)deltasoft.com>
>What is so bloody difficult about this? It's not like I'm asking
>questions about quantum mechanics or something. Keerist.
No one knows or has seen one.
>I had two questions. The one about the SCSI interface has been answered
>to my satisfaction. The second however is not only the easiest of the
>two, but seeming the most difficult to answer.
Seriously it's been about 14 years since I've seen one. It's length was
long enough to reach with neat folds. Don't know the exact number of
inches. However that FDC controller worked fine with 24 inches of
cable for another project.
>If you happen to own a Series 100 box, I'd be most appriciative if you'd
>open it up and let me know what you find out about the cable. If you
>_don't_ own one of these things, I don't want to hear from you. Period.
I bet you dont turn up many Series 100 boxes.
>I know how to build my own cables. I know what connectors are required.
>(I even have a purpose built connector compression tool!) I'm trying to
>restore this machine to _factory_ condition. Smart ass comments about
>making my own cables (while simultaneously alluding that I don't know
>what the fsck I'm doing) is not only not wanted, but just pisses me off.
>If I'd wanted to make a generic, "will do the job" cable, I wouldn't
>have asked about the original one!
The Ampro cab was not common as most bought the dry board being
cheaper and use whatever package was handy or one that met their
spec. Even my Ampro LB manuals do not specify a length!
>FYI, the machine is built for CP/M. It runs CP/M quite happily. Even
>with ZCPR3.
We know that too. I run on here.
Allison
From: Ben Franchuk <bfranchuk(a)jetnet.ab.ca>
>I know that. That is why the early memory chips had separate in/out pins
>to emulate core memory. Everything nowadays tends to be 8 bits with
>tri-state
That might have been a factor but not a requirement. The reason back
then
was it simplified the timing and construction of the chip.
>I/O ( Grumbles here as he has a 12 bit computer and has to waste 4 bits
>out of 16 ) >BTW - some say the best way to cook a fish is in the
dishwasher.
Use four bit wide cache parts then. Or if it's EPROM do three bytes wide
and
select the odd(right 12 bits) or even half(left 12bits). There are other
schemes
to reuse loose bits!
Allison
-----Original Message-----
From: Ben Franchuk <bfranchuk(a)jetnet.ab.ca>
>
>After reading the core memory stuff I realized the what I was thinking
>about was dynamic memory (16k chips) for a 2 mhz 8080 in byte. The
>reason
>I got confused was it used the split memory cycle read-write as core
>memory.
Core is one of the few destructive readout memories used. So every
read has a following write to restore the data, often between data
read there will be a modify cycle which means new data written back.
Allison
Suggestion,
Pict the articles on the basic of historic design point like
the Core article or some significant hardware or software.
Usually that kind of article was a feature.
Allison
-----Original Message-----
From: John Allain <allain(a)panix.com>
To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org>
Date: Sunday, December 16, 2001 1:42 PM
Subject: Re: [PDP8-Lovers] how to clean a PDP8/A, dishwasher?
>> Unfortunately these scans aren't from *my* bytes...my collection
>> doesn't go back that far, as I was 7 years old in 1976...so I can't go
>> scan more of 'em. :-(
>
>I guess I can pony up and put at least one jpegged BYTE article up
>for people to see, perhaps one a month. I have no great ideas on
>how to pick the titles, however. Some kind of democratic thing?
>
>John A.
>
>
From: Richard Erlacher <edick(a)idcomm.com>
>I'm curious about something here ... Was this particular system ever
observed to
>run as configured? I've never owned a prepackaged AMPRO box/system, so
I have
>no experience with them on which to base any guesses. With a SCSI drive
and no
>bridge, the thing should either run or not, though, and if it doesn't
there's
>probably a good reason.
Over the years I've seen two and added hard disks to them (purchased
without).
If you have the right controller and drive it's an assemble the peices
project.
Those included some of the early SCSI drives.
>I'm not in a good situation to help you out with this, at the moment,
but I
>could send you a bridge controller of the sort that the firmware is
supposed to
>recognize on its own. With that you can test the Little Board side of
things.
>The Little Board supports the Xebec controller as well as a number of
models
>from OMTI, ADAPTEC, and others. You'd have to attach an
ST506/412-interfaced
>drive that works properly at the other end, though. The Adaptec models
I've got
>are capable of either RLL or MFM, depending on which model you use and,
of
If you match the known configs it's pretty straightforward, if not you
need to go
into the bios and set up the config by hand. The latter is a bit less
obvious as
the Ampro BIOS for hard disk was done in three layers, one for the
physical
SCSI driver, then the SCSI protocal for the controller target and then
hard disk
interface. There are several added tables not normally seen in a CP/M
bios.
Those tables allow for things like assigning logical unit 3 (whatever it
may be) as drive A:. As BIOS for CP/M go it's very sophisticated.
Allison
>> > From: Gene Buckle <geneb(a)deltasoft.com>
>> Funny, the Ampro docs list all these various controllers and whatnot.
>> The software also _asks_ what controller it is going to talk to. The
>> SCSI controller is part of the LB. What would the software consider
the
>> onboard controller to be?
NCR5380! But that's half the picture. The other half is the SCSI
controller on the other end of the cable. What I meant by PC logic
is that in PCs you plug in an adaptec controller or whoever and you
need a driver specific to that controller. The AMPRO-LB has the
onboard NCR5380 which is the controller and the software specific
to that is in both the bootrom and CP/M bios.
The other peice of that that does not conform to the PC standard
is the other end of the 50pin SCSI cable is the "drive" and back then
the drive was MFM (ST225 typically) with a Bridge adaptor to go
>from SCSI to MFM and that could be done with a board made by
Xybec, Adaptec or Western Digital. Now, those bridge boards did
not behave exactly the same like modern SCSI drives so the "driver"
had an install/init that tweeked the CP/M bios to conform as well as
partition the disk for CP/M use. The CP/M Bios (and bootrom for
that fact) do not query the drive for it's config like PCs. It must be
hard coded into tables in the bios. The bridge controllers require
this info to be pushed into them before they can access the
physical drive. This is in contrast to SCSI drives that have the
tables integral to themselves.
FYI: CP/M supported only 8mb per logical drive so a ST225(20mb)
was usually partitioned into three logical drives (for ampro that would
be A, C and D). Drive B is reserved for floppy as is pseudo drive E.
Drive A(physical drive 0) is always the bootable drive and can be
either floppy or hard disk. The tables for logicla drives are limited
to 16 logical drives (A through P) by CP/M itself and if memory
serves only 10 logical hard disk partitions in the Ampro HD
CP/M bios. So any drive larger than 80mb cannot be fully
accessed. There are ways around the latter problem but
that's a different issue.
>What hard-drive are you using? If it is a SCSI drive? Is it set to
>ID=0? If so, choose either Seagate or Maxtor and give that a try.
I used a 45mb fujitsu. The boot roms expect it to be ID=0.
>> > formatting. If you dont mind hacking Z80 code you can go frm
>> > an AMPRO LB with SCSI to a smaller SCSI drive (64mb or less,
>> > or the rest will be unused).
>>
>> I've got a 20MB SCSI drive I'm trying to use. The bootrom rev tells
me
>> that it's got support for the SCSI controller. What coding has to be
>> done?
CP/M bios which is not the boot rom. The reason for that is the Drive
tables and the controller tables in the install(HDINIT) and format(HDFMT)
will not work for all but a limited subset of possible drive/controller
setups.
The only SCSI drive directly supported was the ST157N and maybe the
ST296N might work.
>If you have the proper version of the HD Utilities, you should not need
>to do any.
> - don
Only if you have a supported controller and drive, otherwise they
do not help you much.
Allison
On December 14, Chad Fernandez wrote:
> The Post Office still uses Unisys stuff, although, I think they may be
> switching to IBM. I saw the Portage (next city over) PO had new looking
> IBM stuff a few weeks back.
>
> Unisys had/has a govt. division of the company.
The post office in Beltsville, MD just switched over to that
Unisys stuff maybe 2 years ago...
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
From: Dave McGuire <mcguire(a)neurotica.com>
>> Not likely as the sense voltages are quite small and the slice time
>> has to just right.
>
> Well I wouldn't expect to connect it *directly* to the PIC...some
>analog jellybeans would seem appropriate.
Look at the byte article and see why something like a PIC adds little
to the task.
Allison
> I wonder if it would be possible (and practical) to use a
>microcontroller, perhaps a PIC, to act as a core controller. Use the
>A/D and D/A hardware to handle the drive and sense stuff, and do all
>the timing in firmware...making it easily tweakable.
Not likely as the sense voltages are quite small and the slice time
has to just right.
> That would be something I'd be up for trying...if I can find a chunk
>of core of low enough density to trace the wiring in. There are some
>nice low-density planes on eBay right now, but they are priced WAY too
>high in my opinion.
No need to trace, they are quite regular, you can ohm them. You still
need core drivers, sense amps and a dozens of diodes for current
steering.
Allison
Sridhar wrote...
> S/390 does NOT run on microprocessors of any kind, let alone
> one as slow as PPC.
Don't tell that to the folks at http://www.conmicro.cx/hercules/
(Of course, it depends on what your definition of "on" is).
Brian
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
_| _| _| Brian Knittel / Quarterbyte Systems, Inc.
_| _| _| Tel: 1-510-559-7930 Fax: 1-510-525-6889
_| _| _| Email: brian(a)quarterbyte.com
_| _| _| http://www.quarterbyte.com
On December 16, Innfogra(a)aol.com wrote:
> Found it. A very interesting issue. There are several other stories I would
> be interested in also. Thank you.
You're very welcome.
Unfortunately these scans aren't from *my* bytes...my collection
doesn't go back that far, as I was 7 years old in 1976...so I can't go
scan more of 'em. :-(
Eventually I'll beef up my BYTE collection, probably via eBay. There
are a LOT of great articles in there. Of course I do have all of the
wonderful Ciarcia books, so my BYTE collecting motivation has been
partially satisfied. :-)
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
On December 16, ajp166 wrote:
> > I wonder if it would be possible (and practical) to use a
> >microcontroller, perhaps a PIC, to act as a core controller. Use the
> >A/D and D/A hardware to handle the drive and sense stuff, and do all
> >the timing in firmware...making it easily tweakable.
>
> Not likely as the sense voltages are quite small and the slice time
> has to just right.
Well I wouldn't expect to connect it *directly* to the PIC...some
analog jellybeans would seem appropriate.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
On December 16, Ben Franchuk wrote:
> > > Remember the (iirc) Compaq ad. Thier 286 had a meg of static ram onboard.
> > > The ad depicted an empty desk with two tire tracks burt into it and a
> > > surprised user behind.
> >
> > Static RAM? Are you sure? I've never heard of static RAM in a
> > PeeCee. That's neat.
>
> Yes there is some -- it is called cache.:) I suspect a sever type
> PC is more likely to have static than dynamic. I never did like PC
> marketing -- clock speed -- not memory speed used as a benchmark.
Nonono, I mean *main* memory, not cache. I sincerely doubt there
are any PeeCees in the 486-or-newer arena with static RAM for main
memory.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
>> I have some scans of an old BYTE Magazine article (July 1976 I
think)
>> that details how to build a common interface for an arbitrary chunk of
>> core. I haven't really read it in-depth but I plan to someday. I can
>> put it online if anyone would like to see it.
I'd love to see scans of this one too. I remember the article but
somehow lost it.
Allison
From: Don Maslin <donm(a)cts.com>
>It should not have a twist like a PC cable, and can be a length of
>34-conductor ribbon cable, Gene, with a 50-pin female header on each
>end. What ever length is needed.
Ah, dont you mean 34 pin? 50 pin would be the SCSI.
Allison
The older large ferrite core is easier to work with though
much slower. The bigger cores produce a larger output
when they switch but the cycle times are in the
3-5uS range. The later is helpful for demos as nothing
is too fast.
Allison
-----Original Message-----
From: Loboyko Steve <sloboyko(a)yahoo.com>
To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org>
Date: Saturday, December 15, 2001 11:36 PM
Subject: Re: [PDP8-Lovers] how to clean a PDP8/A, dishwasher?
>I've looked into this too. Problems are many. It's
>definitely not a trivial project, lots of analog and
>electromagnetic voodoo, and the chips that made it
>easier are very hard to find. I've got a small
>capacity large doughnut ca. 1960 core plane from an
>IBM machine and a 4K by 16 plane from the 70's with
>very tiny doughnuts, both unused, and I'd love to
>demonstrate how it worked.
>
>
>--- ajp166 <ajp166(a)bellatlantic.net> wrote:
>> From: John Allain <allain(a)panix.com>
>> >I have a Question for the other core users out
>> there:
>> >How would I test-signal a board, for demos, that is
>> >just a core frame, IE one sacrificed from its stack
>>
>> >and sold at the e- flea market?
>>
>>
>> It's a non trivial thing to do. Core by definition
>> is destructive
>> read out memory. So to demo a core you need to
>> provide
>> the coincident current (x,y) and the
>> inhibit/write/read signals
>> with the associated timing. Both the currents and
>> the
>> timing are critical. takes a lot of stuff to do
>> that.
>>
>> Allison
>>
>>
>
>
>__________________________________________________
>Do You Yahoo!?
>Check out Yahoo! Shopping and Yahoo! Auctions for all of
>your unique holiday gifts! Buy at http://shopping.yahoo.com
>or bid at http://auctions.yahoo.com
From: Gene Buckle <geneb(a)deltasoft.com>
>I know I can use any length of ribbon I want. What I'd like to know is
>what it was when it was new. (and it's 34 pin card-edge connectors that
>are needed :) )
I take them off old PC floppy cables.
>The drive is a Miniscribe 8425S and AFAIK, it's set to ID 0 with the
>terminating resistors installed. Seagate or Maxtor is not listed as a
>_controller_ choice when HFORMAT is run.
Yep! It's possible to use that drive but the Ampro provided tools only
recognized drives from the era, there were many good choices in
later years.
Allison
On December 15, Ben Franchuk wrote:
> > I have some scans of an old BYTE Magazine article (July 1976 I think)
> > that details how to build a common interface for an arbitrary chunk of
> > core. I haven't really read it in-depth but I plan to someday. I can
> > put it online if anyone would like to see it.
>
> I think that was a design for the 8080 and the S100 bus.
> It was a really nice design too if I remember right. I remember
> somebody doing a core-demo on the web. I think it used a iron washer
> as the core. Since this is not high speed only the current is critical
> here.
It should be pretty easy to interface to other processors, then...
> (Boy do I miss the early Bytes -- ordinary people designing and using
> computers
> -- not multi-billion $$$ bloatware companies -- )
Yup.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
> -----Original Message-----
> From: Jochen Kunz [mailto:jkunz@unixag-kl.fh-kl.de]
> On 2001.12.14 18:08 Christopher Smith wrote:
>
> [Sequent Symmetry S81]
> > Drives, but I can probably handle that...
> What interface SMD?
Possibly, it's hard to tell since I'm not sure what an SMD interface looks
like. I could turn it over and check but I don't know what to look for. ;)
> > I believe that the system was board-for-board compatible
> with the S27,
> The Unix-AG once owned a S27 with 8 CPUs, 80MB RAM, 7 SMD disks,
> Exabyte, ... I know where the machine is now, including a complete set
> of OS software. If you get the machine working, ask me for software.
I certainly will.
> Don't expect much of that machine. I could get only 200kB/s via the
> Ethernet, the SMD disk controller could not handle more then 700kB/s.
> (The same disks can deliver more than 2MB/s on a Sun 3/260.) That is
> real poor for such a high end beast. I was really
> disapointed. But it is
Did you get the chance to find out how performance faired when you add more
CPU?
> nice to see an old 4.2BSD UNIX derivate with AT&T universe
> running on 8
> CPUs in a SMP config.
It is amusing for me to see _any_ intel cpu running in an SMP config, and
the fact that from what I've heard, Sequent made them do it fairly well,
intrigues me.
Regards,
Chris
Christopher Smith, Perl Developer
Amdocs - Champaign, IL
/usr/bin/perl -e '
print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");
'
In a message dated 12/15/01 10:54:50 PM Pacific Standard Time,
mcguire(a)neurotica.com writes:
>
>
> The scans are up at http://ti.neurotica.com/core. They're a bunch
> of jpegs. No, that wasn't my idea, I didn't do the scanning. :) I
> might try to turn them into a pdf one of these days.
>
>
Found it. A very interesting issue. There are several other stories I would
be interested in also. Thank you.
Paxton
Astoria, OR
Anyone have any of the docs for this beastie? I have one but no docs. I
have been having trouble figuring out which terminal emulation to use when
connected to it, also If someone has the docs I would be will ing to get my
scanner hooked up again to my computer and see about making a PDF of them
for posterity....
In a message dated 12/15/01 9:15:47 PM Pacific Standard Time,
mcguire(a)neurotica.com writes:
> I have some scans of an old BYTE Magazine article (July 1976 I think)
> that details how to build a common interface for an arbitrary chunk of
> core. I haven't really read it in-depth but I plan to someday. I can
> put it online if anyone would like to see it.
>
I would like to see it. I have several pieces of core.
Paxton
Astoria, OR
On December 16, Pat Finnegan wrote:
> > I have some scans of an old BYTE Magazine article (July 1976 I think)
> > that details how to build a common interface for an arbitrary chunk of
> > core. I haven't really read it in-depth but I plan to someday. I can
> > put it online if anyone would like to see it.
>
> I'd definately be interested.
The scans are up at http://ti.neurotica.com/core. They're a bunch
of jpegs. No, that wasn't my idea, I didn't do the scanning. :) I
might try to turn them into a pdf one of these days.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
On December 16, John Allain wrote:
> > I have some scans of an old BYTE Magazine article (July 1976 I think)
> > that details how to build a common interface for an arbitrary chunk of
> > core. I haven't really read it in-depth but I plan to someday. I can
> > put it online if anyone would like to see it.
>
> It Would help lots more Dave if you dug out that disk drive.
> The mv3500 is still pretty useless w/o swap space.
I've gotten to the bottom of the "staging area"...I think that pile
of drives is in my storage locker up in Maryland. I will know for
sure soon.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
On December 15, ajp166 wrote:
> >I have a Question for the other core users out there:
> >How would I test-signal a board, for demos, that is
> >just a core frame, IE one sacrificed from its stack
> >and sold at the e- flea market?
>
> It's a non trivial thing to do. Core by definition is destructive
> read out memory. So to demo a core you need to provide
> the coincident current (x,y) and the inhibit/write/read signals
> with the associated timing. Both the currents and the
> timing are critical. takes a lot of stuff to do that.
I have some scans of an old BYTE Magazine article (July 1976 I think)
that details how to build a common interface for an arbitrary chunk of
core. I haven't really read it in-depth but I plan to someday. I can
put it online if anyone would like to see it.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
On December 15, Ben Franchuk wrote:
> > > > I have little doubt about the appropriateness... of your response.
> > > > Care to say when its appropriate to own three S/390's?
> >
> > > It's wholly inappropriate. He should give one to me.
> >
> > And one to me. Then he has one, and that's somewhat less inappropriate. ;-)
>
> Why collect 390's? 360's are more impressive! :)
I suspect Sridhar doesn't have the S/390s for "historic"
purposes...Ordinarily I'd just shut up and let him say that, but I
just talked with him on the phone, he's outside of Richmond on his way
down here. I'm going to make him eat some beef while he's here. :-)
> BTW does the 390 architecture still emulate the 360's?
I believe so, yes.
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf
From: Richard A. Cini, Jr. <rcini(a)msn.com>
> On the negative side, a small regression error has crept in and 4k
BASIC
>will no longer run. This is not so bad because if you could run 8k BASIC
>there's no reason to run 4k BASIC.
This is broken. Since 4kbasic and 8kbasic ran on the same altairs it
suggests something in the emulator is broken.
FYI: much of MITS and Altair compatable software used input Port 0FFh
as a 8bit input (usually to configure IO).
Allison
I only needed one floppy and with the twisted end cut off
it was perfect.
Allison
-----Original Message-----
From: Richard Erlacher <edick(a)idcomm.com>
To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org>
Date: Saturday, December 15, 2001 11:00 PM
Subject: Re: Ampro Little Board questions...
>A PC floppy cable certainly wouldn't work with the Little Boards I have,
since
>they use the standard floppy disk cable, which has no twists or cuts.
>
>Dick
>
>----- Original Message -----
>From: "ajp166" <ajp166(a)bellatlantic.net>
>To: <classiccmp(a)classiccmp.org>
>Sent: Saturday, December 15, 2001 2:44 PM
>Subject: Re: Ampro Little Board questions...
>
>
>> From: Gene Buckle <geneb(a)deltasoft.com>
>> >belongs with it. Does anyone have a Series 100 box that could give
me
>> >the measurements and connector orientation & location of the floppy
>> >cable?
>>
>>
>> Nothing magic. the last one I had used was from a PC.
>>
>> >Secondly, I don't know what "brand" SCSI controller is built into the
>> >board. The SCSI chip seems to be an NCR 5830, but that leads me
nowhere
>> >in relation to whether or not it's an Adaptec or other model
controller.
>> >I need to know the brand because the hd formatting software needs to
>> >know it.
>>
>>
>> Your applying PC logic to it. It's is not Adaptec, i'ts just SCSI
>> (SCS1 or II) host and the NCR5380 is one of the early and common
>> chips used for that.
>>
>> The brand applies to the "other" board, what is known as a SCSI
>> bridge board. Adaptec, Xybec, WD and other made them. You
>> need to know what board and what drive to do the formatting. If
>> you dont mind hacking Z80 code you can go frm an AMPRO LB
>> with SCSI to a smaller SCSI drive (64mb or less, or the rest will
>> be unused).
>>
>> Allison
>>
>>
>>
>>
>
>
From: John Allain <allain(a)panix.com>
>I have a Question for the other core users out there:
>How would I test-signal a board, for demos, that is
>just a core frame, IE one sacrificed from its stack
>and sold at the e- flea market?
It's a non trivial thing to do. Core by definition is destructive
read out memory. So to demo a core you need to provide
the coincident current (x,y) and the inhibit/write/read signals
with the associated timing. Both the currents and the
timing are critical. takes a lot of stuff to do that.
Allison
Hello, all:
Just a quick announcement. Today was the official release of version 2.1 of
the Altair32 Emulator. Yeah!
It's been about four months since the 2.0 release and a lot has happened
since then. Floppy disk images for CP/M, Altair DOS and Disk BASIC are fully
functional and the Altair32 now has an integrated debugger, courtesy of Jim
Battle's Sol-20 emulation project. These two items alone took over half of
the time between releases and integrating the debugger required a major
overhaul of the 8080 emulation code.
On the negative side, a small regression error has crept in and 4k BASIC
will no longer run. This is not so bad because if you could run 8k BASIC
there's no reason to run 4k BASIC.
The next phase of the project will hopefully include some or all of the
following:
Continued code cleanup; minor fixes to IMSAI conditional
Further testing of the debugger (it's been only lightly tested with the
Altair32)
A set of Windows-based tools to manipulate diskette images (to enable people
to download programs from http://www.retroarchive.org and get them onto
diskettes)
Support for BBS software
Support for different floppy controllers/disk formats and maybe a
pseudo-floppy hard drive.
That's it for now. As always, you can check out the project at:
http://highgate.comm.sfu.ca/~rcini/classiccmp/Altair32.htm
Rich
Rich Cini
Collector of classic computers
Build Master for the Altair32 Emulation Project
Web site: http://highgate.comm.sfu.ca/~rcini/classiccmp/
/************************************************************/
On Dec 15, 12:28, Matthew Sell wrote:
> Typically, the time spent "in the water" isn't long enough to damage.
Even
> items made of steel and iron won't rust if the water is removed after the
> cycle is complete. If they sit overnight, well, that's a different story.
>
> The only production problem I saw with untreated water was with an
> electronic test instrument that had a lot of high-impedance signal
> interconnects throughout. Many signal lines ran for long distances next
to
> each other. While the design of this piece of test equipment was
> questionable, it was our duty to get it to work.
>
> The two biggest problems were contaminants from the water supply used in
> the washing process (city water - switched to using a commercial
filtration
> system), and humidity (had to paint a sealant on all of the boards).
That's a well-known problem. Some of the residues from a domestic water
supply -- especially in hard water areas -- are mildly hygroscopic, and as
a result, the boards would acquire very small amounts of moisture on the
surface, especially when exposed to a humid atmosphere. In combination
with the salts in the residue, this makes for leakage across the board,
which could easily upset very high impedance circuits.
I heard of someone who had the opposite problem. He designed a CMOS
circuit which worked fine when forst contructed, but stopped when given
anti-environment protection or was potted. He'd inadvertantly relied on
the normal leakage across a PCB to hold the unused inputs of a CMOS gate at
a particular level. Remove the leakage current and the gate stops working
properly. Solution: add the pullup resistor that should have been there in
the first place.
--
Pete Peter Turnbull
Network Manager
University of York
On Dec 15, 1:32, Matthew Sell wrote:
> Here's the secrets to doing this right:
>
> 1) Do not use any detergents. NONE.
Why not? Commercially, detergents are used to remove flux. I use
laboratory detergent to clean PCBs I've made or modified. I don't use
washing-up liquid, though, and I don't use the harsher detergents sometimes
found in dishwasher detergent.
--
Pete Peter Turnbull
Network Manager
University of York
On December 15, Jim Davis wrote:
> IMHO: All software development should be performed as such:
>
> 1) Requirements - what should it do, and not do. Spin this till
> everybody
> signs off.
> 2) Prelim design - Ok, a rough outline of the design, data structures
> and control/data flow defined here.
> 3) Detailed design - Define all the modules and their function, break it
> down.
> 4) Test plan - integrate testing into detailed design, make it unit
> testable.
> a unit is somthing that has input and output and side effects, like a
> function.
> 5) Finally, coding - build modules in parallel with test code.
> 6) Unit testing - verify that modules comply with detailed design.
> 7) Integration testing - hook it all together, make sure it works, apply
> test plan developed in step 4 for fully integrated aplication.
>
> Do 1-3 until marketing decides what they want,4-7 until you find no
> errors.
>
> For safety critical, you should /have to perform statement and decision
> coverage in
> step 6 and 7 and the detailed design should have a one-to-one
> corespondence
> with the detailed design document.
Hmm, that procedure "reads" nice, but it sounds like more meetings
than actual work. But then I've been a software developer for about
twelve years, and nobody that I've worked with can figure out how I
can blow off all the meetings and not get fired...it's because I end
up writing all the code that the rest of the developers are talking
about in their meetings, WHILE they're in their meetings, and by the
time they're doing screwing around, the code is running.
Procedures are nice, but they can be taken too far. Goal-orientation
is better.
(While I'll freely admit that this approach simply doesn't work for
multi-million line applications, I should state that I generally work
on applications of less than one million lines, but generally more
than 100,000. I further state that my methods should probably NOT be
used in life-critical applications...more than two eyes need to look
at that stuff, no matter what.)
-Dave
--
Dave McGuire
St. Petersburg, FL "Less talk. More synthohol." --Lt. Worf