-John Rollins typed:
>
>>OK, does anyone know what this card came from? Anyone know what uses and
86
>>pin bus?
This is from vague memory, but if the card is roughly the same size as an
S-100 card (5 x 10 inches) and has an 86 pin bus connector, I think it might
be an old Motorola bus. I don't remember what they called it, never used
Motorola development systems, but it was Motorola's answer to Intel's
Multibus.
Joe,
I don't know if software is available but will ask. Does the NS
horizon use a S-100 bus? I was told the unit I'm (hopefully) about to
acquire has an internal 10MB hard drive. i'm going to go eyeball the
unit within the next few days.
Marty
______________________________ Reply Separator
_________________________________
Subject: Re: North Star Horizon
Author: classiccmp(a)u.washington.edu at internet
Date: 2/24/98 1:00 PM
Marty,
I have some manuals for the NS Horizon; disk controller, DOS, BASIC,
Pascal. I'm looking for the software.
Joe
At 12:36 PM 2/24/98 -0500, you wrote:
> Does anybody have any information on a North Star Horizon? I may be
> acquiring one of these soon but don't know much about it except that
> it has wooden side panels and used to support a half-dozen terminals.
> Is it a S-100 bus?
>
> Thanks for any help-
>
> Marty Mintzell
>
>
------ Message Header Follows ------
Received: from lists3.u.washington.edu by smtp.itgonline.com
(PostalUnion/SMTP(tm) v2.1.9i(b5) for Windows NT(tm))
id AA-1998Feb24.130031.1767.28490; Tue, 24 Feb 1998 13:00:34 -0500
Received: from host (lists.u.washington.edu [140.142.56.13])
by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP
id JAA14977; Tue, 24 Feb 1998 09:53:52 -0800
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP
id JAA53378 for <classiccmp(a)lists.u.washington.edu>; Tue, 24 Feb 1998
09:53:44 -0800
Received: from star1.intellistar.net (star1.intellistar.net [206.105.64.2])
by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP
id JAA05718 for <classiccmp(a)u.washington.edu>; Tue, 24 Feb 1998 09:53:43
-0800
Received: from lizard ([206.105.68.41]) by star1.intellistar.net
(Post.Office MTA v3.1 release PO203a ID# 0-41809U2500L250S0)
with SMTP id AAA22727 for <classiccmp(a)u.washington.edu>;
Tue, 24 Feb 1998 12:53:39 -0500
Message-Id: <3.0.1.16.19980224125410.0877b306(a)intellistar.net>
Date: Tue, 24 Feb 1998 12:54:10
Reply-To: classiccmp(a)u.washington.edu
Sender: CLASSICCMP-owner(a)u.washington.edu
Precedence: bulk
From: Joe <rigdonj(a)intellistar.net>
To: "Discussion re-collecting of classic computers"
<classiccmp(a)u.washington.edu>
Subject: Re: North Star Horizon
In-Reply-To: <1998Feb24.123503.1767.83436(a)smtp.itgonline.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: rigdonj(a)intellistar.net
X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN
Joe,
Thanks for the information. I'm located in northern Virginia just
outside Washington, D.C.
Marty
______________________________ Reply Separator
_________________________________
Subject: Re: Re[2]: North Star Horizon
Author: classiccmp(a)u.washington.edu at internet
Date: 2/24/98 5:07 PM
Marty,
I think it uses the S-100 bus. According to their manual, North Star
used the same disk controller in the Horizon that they sold for the S-100
systems. I have a NS S-100 controller. They are the same electricaly and
software wise but maybe physically different.
Sounds like a neat system, I've never heard of one having a hard drive.
Keep me posted.
BTW where are you? I'm in Orlando, Florida.
Joe
At 01:10 PM 2/24/98 -0500, you wrote:
> Joe,
>
> I don't know if software is available but will ask. Does the NS
> horizon use a S-100 bus? I was told the unit I'm (hopefully) about to
> acquire has an internal 10MB hard drive. i'm going to go eyeball the
> unit within the next few days.
>
> Marty
>
>
>______________________________ Reply Separator
>_________________________________
>Subject: Re: North Star Horizon
>Author: classiccmp(a)u.washington.edu at internet
>Date: 2/24/98 1:00 PM
>
>
> Marty,
>
> I have some manuals for the NS Horizon; disk controller, DOS, BASIC,
> Pascal. I'm looking for the software.
>
> Joe
>
> At 12:36 PM 2/24/98 -0500, you wrote:
> > Does anybody have any information on a North Star Horizon? I may be
> > acquiring one of these soon but don't know much about it except that
> > it has wooden side panels and used to support a half-dozen terminals.
> > Is it a S-100 bus?
> >
> > Thanks for any help-
> >
> > Marty Mintzell
> >
> >
>
>
> ------ Message Header Follows ------
> Received: from lists3.u.washington.edu by smtp.itgonline.com
> (PostalUnion/SMTP(tm) v2.1.9i(b5) for Windows NT(tm))
> id AA-1998Feb24.130031.1767.28490; Tue, 24 Feb 1998 13:00:34 -0500
> Received: from host (lists.u.washington.edu [140.142.56.13])
> by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP
> id JAA14977; Tue, 24 Feb 1998 09:53:52 -0800
> Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
> by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP
> id JAA53378 for <classiccmp(a)lists.u.washington.edu>; Tue, 24 Feb 1998
> 09:53:44 -0800
> Received: from star1.intellistar.net (star1.intellistar.net [206.105.64.2])
> by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP
> id JAA05718 for <classiccmp(a)u.washington.edu>; Tue, 24 Feb 1998 09:53:43
>
> -0800
> Received: from lizard ([206.105.68.41]) by star1.intellistar.net
> (Post.Office MTA v3.1 release PO203a ID# 0-41809U2500L250S0)
> with SMTP id AAA22727 for <classiccmp(a)u.washington.edu>;
> Tue, 24 Feb 1998 12:53:39 -0500
> Message-Id: <3.0.1.16.19980224125410.0877b306(a)intellistar.net>
> Date: Tue, 24 Feb 1998 12:54:10
> Reply-To: classiccmp(a)u.washington.edu
> Sender: CLASSICCMP-owner(a)u.washington.edu
> Precedence: bulk
> From: Joe <rigdonj(a)intellistar.net>
> To: "Discussion re-collecting of classic computers"
> <classiccmp(a)u.washington.edu>
> Subject: Re: North Star Horizon
> In-Reply-To: <1998Feb24.123503.1767.83436(a)smtp.itgonline.com>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> X-Sender: rigdonj(a)intellistar.net
> X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN
>
>
------ Message Header Follows ------
Received: from lists3.u.washington.edu by smtp.itgonline.com
(PostalUnion/SMTP(tm) v2.1.9i(b5) for Windows NT(tm))
id AA-1998Feb24.170757.1767.28555; Tue, 24 Feb 1998 17:07:58 -0500
Received: from host (lists.u.washington.edu [140.142.56.13])
by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP
id OAA07336; Tue, 24 Feb 1998 14:01:10 -0800
Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8])
by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP
id OAA35550 for <classiccmp(a)lists.u.washington.edu>; Tue, 24 Feb 1998
14:01:03 -0800
Received: from star1.intellistar.net (star1.intellistar.net [206.105.64.2])
by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP
id OAA11194 for <classiccmp(a)u.washington.edu>; Tue, 24 Feb 1998 14:01:02
-0800
Received: from lizard ([206.105.66.22]) by star1.intellistar.net
(Post.Office MTA v3.1 release PO203a ID# 0-41809U2500L250S0)
with SMTP id AAA26712 for <classiccmp(a)u.washington.edu>;
Tue, 24 Feb 1998 17:00:54 -0500
Message-Id: <3.0.1.16.19980224170000.376726fc(a)intellistar.net>
Date: Tue, 24 Feb 1998 17:00:00
Reply-To: classiccmp(a)u.washington.edu
Sender: CLASSICCMP-owner(a)u.washington.edu
Precedence: bulk
From: Joe <rigdonj(a)intellistar.net>
To: "Discussion re-collecting of classic computers"
<classiccmp(a)u.washington.edu>
Subject: Re: Re[2]: North Star Horizon
In-Reply-To: <1998Feb24.130843.1767.83458(a)smtp.itgonline.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: rigdonj(a)intellistar.net
X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN
<But surely this is a limitation of the front panel not the processor.
<I/O bus cycles can (easily) be generated from an appropriately designed
<front panel.
Processor. The 8080 CPU does I/O To/From the accumulator which is
inaccessable from the front pannel being an internal register. An altair
did things by forcing a jump(C3h, xx, zz) the address switches were used
as zzxx forcing the PC to take the set value. Data at a given MEMORY
address was displayed as a result of the current address and stopping
before the next instructing fetch. Writing to MEMORY was simply gating
the data switches and forcing a write pulse (no cpu execution). Its
design was to allow insetion of code into memory and examination of
memory as those were direct. IO however while it would be nice to
interogate or write to devices could leave the cpu "out of sync" since
all IO is done from the accumulator. To do that you really need a soft
front panel and once you do that, displaying or altering the Acc, BC, DE,
HL and SP registers and associated flags are possible.
Did my fair share of 8080/8085/z80 designs in the '70s.
Allison
Again things have slowed down but a few goodies were found: A Rockwell
AIM65 4k computer inside what looks like a large calculator case that is
black and grey in color, has a onboard thermal printer using calculator
size paper, not tested yet, free; also got 6 R6500 mb's some are marked as
being bad all free; a Mac IIcx missing HD and memory simms for free; a
working Mac SE/30 without KB and mouse for $15; a Victor 386sx/20 laptop
broken screen with power adapter for free. Other manuals gotten at thrift
stores and some software that's been the week. Keep Computing - John
Tony Duell quoted me as having written:
>> On the subject of BBC video problems, it occurs to me that the BBC micro
>> does scrolling by moving the pointer to the start of the screen (under
>> some conditions?). If you can get it to do this, and see how the
>> display behaves, you may be able to determine easily if it's an
>> addressing problem.
>
> Is this going to tell you very much?
>
> The BBC _does_ use hardware scrolling (it changes the start-of-memory
> register in the 6845), but as the screen is a contiguous array of bytes,
> all that a scroll does is effectively increment that pointer by the
> number of bytes/line of characters (= 640 bytes in mode 0, etc) and then
> clear the new bytes displayed on the bottom line.
>
> So the new line 0 will be the old line 1, etc, but there are no other
> changes. A given byte on the screen is displayed in the same relative
> position to other given bytes on the screen. In mode 0, &3281 is still the
> second dot row of a character in the far left column. Of course if the
> text goes all over the place on a hardware scroll then you can be
> virtually certain that the 6845 is playing up.
What I meant was that addressing problem _external_ to 6845 generally
means that the fault will occur at the same _memory_ address. So that
type of scrolling means the fault will scroll up the screen, appearing
at the same place in the _text_ every time. Won't it?
If the screen line length were an integer power of two, a fault in the
bottom few address lines would appear at the same place on every line.
Fortunately the BBC micro is 80 characters per line, so you will see
things recurring on a slant. This slanted line of fault should move up
the screen as it scrolls.
Something to try, anyway. I am a firm believer in non-invasive tests!
Philip.
Sam Ismail <dastar(a)wco.com> wrote:
> First stop: Computer Recycling Center
[list elided]
Hmph. I stopped by weekend before last (14 Feb) and it looked like
they'd been cleaned out. Even the bookshelves were mostly empty.
Probably for the best though, given how far behind I am with other
stuff that needs doing.
> Corvus Systems Hard Drive unit - I believe this goes with the rest of the
> Corvus Concepts computer. It has several connectors on the back labeled
> "Processor", "Drive"...it also has one labeled "VCR" and a video IN and
> OUT jack. McFrank, this is so you can backup to a VCR right?
Yep, that's what it's for (although the hard drive could have been
used with about a half-dozen different kinds of systems, not just the
Concept). I'm not sure whether the jacks imply the presence of
whatever you actually need to do the backup or whether there is
additional hardware or software required (this is one of those
things that I know I need to figure out some day when I get all
those manuals in front of me at once).
-Frank McConnell
<> The Intellec MCS8i and the PDP11 (obviously, since all I/O is memory
<> mapped) do allow you to access I/O devices directly from the panel.
<
<...and the front panel on the Altair 8800b.
The 8008 does not have memory mapped IO, there are distinct IO
instructions. It's not to say MM/io is not done. The PDP-11 memory
and devices are the same things and there are no specialized IO
instructions.
The altair...(8800 and 8800a) from the front pannel there is no way to
interrogate an port mapped IO device or write to it. You must do it with
a little code.
Allison
On Mon, 23 Feb 1998 20:14:09 +0000 (GMT), Tony Duell
<ard(a)p850ug1.demon.co.uk> wrote:
>>I have a text file somewhere explaining how to make a functional copy of
>>this unit using more modern parts (LEDs and ULN2803 driver chips, I
>>think) if anybody wants it.
If you can put your hands on that text file, I'd be interested in it.
Thanks!
-------------------------------------------------
Rich Cini/WUGNET
<nospam_rcini(a)msn.com> (remove nospam_ to use)
- ClubWin Charter Member (6)
- MCP Windows 95/Windows Networking