VCF East - 10 days away!

[Evan Koblentz via cctalk]

Friendly reminder that Vintage Computer Festival East XII is only 10 
days away! March 31-April 2 in New Jersey. Two hands-on exhibit halls, a 
dozen tech talks, three keynotes, consignment sale, and you can visit 
the year-round Vintage Computer Federation museum while you're here. All 
the details are here: 
http://vcfed.org/wp/festivals/vintage-computer-festival-east/



Evan Koblentz, director
Vintage Computer Federation
a 501(c)3 educational non-profit

e...@vcfed.org
(646) 546-

www.vcfed.org
facebook.com/vcfederation
twitter.com/vcfederation

Re: Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not spin up ?

[Pete Lancashire via cctalk]

I took a closer look at the adapter, and not only is the an cracked trace
next to a via but a soldering​ short.  The place in CN is sending me
another one. For now I have put back the original drive. Somewhere in the
junk is the solution to the next issue, either an old hub Tha has coax/BNC
or the box of MAUs that came with the pallet of Sun pizza s

-Pete to much junk

On Mar 21, 2017 5:22 PM, "Glen Slick via cctalk" 
wrote:

> On Tue, Mar 21, 2017 at 5:49 AM, Pete Lancashire via cctalk
>  wrote:
> > Found at least one issue, open trace next to a via on the adapter. Ran
> out
> > of time to keep checking.
> >
> > -pete
>
> I just checked my HP 9000/382 and found I put the dead original
> Quantum 50-pin SCSI hard drive back in it. I must have been using a
> 68-pin 9GB SCSI hard drive the last time I was tinkering with it, with
> a 50-pin male / 68-pin male adapter. I don't remember having any
> issues with that configuration.
>
> I did a clean install of HP-UX 9.10 on my 9000/382 from a B2378-87054
> CD image I got from hpmuseum.net
>
> http://hpmuseum.net/display_item.php?sw=525
>
>

Re: Timesharing/multiuser BASIC for MC68K

[Pete Lancashire via cctalk]

Just want to add the thumbs up on your project.

-pete

On Mar 20, 2017 3:38 PM, "jim stephens via cctalk" 
wrote:

>
>
> On 3/20/2017 2:20 PM, Joseph Zatarski via cctalk wrote:
>
>> More info on the hardware I'm using is available here:
>> https://hackaday.io/project/6150-beckman-du600-reverse-engineering
>>
> I have a copy of Diab and MQX that would run on it if you have the full
> docs.  the 68332 was a nice micro
> that was used in several projects I worked on.  The first one I used an
> ice box that was a crude affair
> done by an operation in Massachusetts, which allowed in circuit testing
> via on chip facilities.
>
> Their development compiler was essentially GCC with a chip startup to set
> up the rom, ram etc. registers,
> then transfer control to the first instruction of main().
>
> Diab is much like that with a cc setup that prepares the processor, but
> the MQX goes and runs much like
> your OS sounds.  it is initially fixed number of tasks, but can add tasks,
> etc.  Not really a timeshare type
> system, but a pretty powerful embedded OS of course.
>
> I have several boxes with the 68332 and will have to see if your gizmo
> would come up and run on it.  I'd
> need to figure out how to get either an ethernet stack (there are some out
> there), or something to
> get to a serial mux from our hardware though.  I think we have 2mb, and
> 1mb rom though.  Also a
> very nice ASIC which was the reason for the hardware.
>
> Nice project
> thanks
> Jim
>
>
>

Re: Introducing the UUCP/Usenet Project

[goetz--- via cctalk]

Am 21.03.2017 um 01:33 schrieb Warren Toomey via cctech :

> A map of what nodes we have so far is at:
> https://raw.githubusercontent.com/DoctorWkt/4bsd-uucp/4.3BSD/uucp.png

Please add (rough) locations, where the boxes are, and what OS/stack these are 
using, if anyhow possible! Would love to see that.

Regards
Götz

Re: Any faithful VT100 Emulators?

[Lars Brinkhoff via cctalk]

Warren Toomey wrote:
> are there any _good_ VT100 terminal emulators

This emulates the 8080 and runs off ROMs, if you want that kind of
accuracy:

https://github.com/phooky/VT100-Hax

Re: booting os/8

[Jerry Weiss via cctalk]

> On Mar 21, 2017, at 10:49 PM, W2HX via cctalk  wrote:
> 
> Hi folks,
> 
> I have a PDP-8/e that I've been working on. I have completed construction of 
> AK6DN's RX01/02 emulator. I got to the step tonight where I was trying to 
> boot an OS/8 disk image and nothing was happening. I realized that I do not 
> have the bootstrap diode board in my 8/e so begin the bootstrap triggered by 
> the "SW" switch.
> 
> Does anyone have the program I can toggle in for the bootloader? What I found 
> is somewhat confusing. Here is a discussion on this topic.
> 
> https://groups.google.com/forum/#!searchin/alt.sys.pdp8/RX01$20boot|sort:relevance/alt.sys.pdp8/9-GCoA0PCLA/370T3R-Ru_AJ
> 
> It seems one fellow was attempting to edit/improve the bootloader of another 
> fellow. I was wondering if anyone has distilled this into something simple. 
> At the moment, I care only about booting from RX01-Disk0.
> 
> Any pointers greatly appreciated. Thanks
> Eugene W2HX
> 
The Data Systems Design DSD 440 Disk Drive Manual on page 5-34 has a PDP8 RX01 
drive 0 Bootstrap.I can’t vouch for it personally.

The listing basically consists of

• Load the following bootstrap sequence through the front panel.,

33/ 6755 
34/ 5054 
35/ 5045
45/ 7326 
46/ 6751
47/ 4053
50/ 3002
51/ 2050
52/ 5047
53/ 6753
54/ 6753
55/ 5033
56/ 6752
57/ 5453
60/ 7004

• Start at location 33. IF the diskette is write-protected, the 
computer will halt at location 7604. Pressing the CONTINUE (or run) switch on 
the front panel will then start the monitor. Additionally, if at any time the 
is halted and you wish  to restart in the monitor, this can be done by the 
diagnostic diskette in drive 0 and restarting at location 7605. 


Note: The halt/restart locations applies to a vendor supplied diagnostic.  


Good luck,
Jerry  WB9MRI

booting os/8

[W2HX via cctalk]

Hi folks,

I have a PDP-8/e that I've been working on. I have completed construction of 
AK6DN's RX01/02 emulator. I got to the step tonight where I was trying to boot 
an OS/8 disk image and nothing was happening. I realized that I do not have the 
bootstrap diode board in my 8/e so begin the bootstrap triggered by the "SW" 
switch.

Does anyone have the program I can toggle in for the bootloader? What I found 
is somewhat confusing. Here is a discussion on this topic.

https://groups.google.com/forum/#!searchin/alt.sys.pdp8/RX01$20boot|sort:relevance/alt.sys.pdp8/9-GCoA0PCLA/370T3R-Ru_AJ

It seems one fellow was attempting to edit/improve the bootloader of another 
fellow. I was wondering if anyone has distilled this into something simple. At 
the moment, I care only about booting from RX01-Disk0.

Any pointers greatly appreciated. Thanks
Eugene W2HX

RE: Any faithful VT100 Emulators?

[Bill Gunshannon via cctalk]

From: cctalk [cctalk-boun...@classiccmp.org] on behalf of Warren Toomey via 
cctalk [cctalk@classiccmp.org]
Sent: Tuesday, March 21, 2017 9:02 PM
To: cctalk@classiccmp.org
Subject: Any faithful VT100 Emulators?

OK, so I don't have a real VT100, so I'm accessing an old 4.3BSD system
with xterm and LXTerminal terminal emulators on Linux. Last night, for a
laugh, I ran vttest from the 1980s and the terminal emulators performed
woefully.

Which raises the question, are there any _good_ VT100 terminal
emulators, especially for Linux? For any other platforms?

Cheers, Warren

__

I've never formally tested it but people say Putty is very good.  I have even
heard VMS users say it works with LSE.  ANd then, if you have MSDOS
laying around somewhere there is MSKermit which had to be the best I
ever saw.

bill

Re: Any faithful VT100 Emulators?

[John Wilson via cctalk]

On Wed, Mar 22, 2017 at 11:02:58AM +1000, Warren Toomey via cctalk wrote:
>OK, so I don't have a real VT100, so I'm accessing an old 4.3BSD system
>with xterm and LXTerminal terminal emulators on Linux. Last night, for a
>laugh, I ran vttest from the 1980s and the terminal emulators performed
>woefully.
>
>Which raises the question, are there any _good_ VT100 terminal
>emulators, especially for Linux? For any other platforms?

If I do say so myself, the one in E11 is very true.  Its VT100, VT101,
and VT102 emulations "fail" VTTEST in exactly the same ways that the real
VT100, VT101, and VT102 do (point is:  VTTEST is a fool's paradise, and
anything which 100% passes it is *definitely* not 100% VT100-compatible).

The best E11 flavors for the VT100 emulation are for Windows and OS/2
(those give you pretty much *everything*, including smooth-scroll and blink
and true double-size characters and the correct VT100 font and the SET-UP 0
screen scramble).  DOS and stand-alone give you a good text-mode approximation
(minus smooth scroll, and blink isn't quite accurate, and the double-size
characters reassign unused char-gen cells until they run out and then it
starts to look like a ransom note), but the Linux version works only on
text consoles (mainly because I haven't found a linker that builds from
OMF386 .OBJ files yet also handles ELF imports correctly, so I can't build
it against X).

Currently there's no free-standing version (it exists only built into E11),
which I've been meaning to deal with for centuries (and I'm currently --
as in for the past week -- working on a version for XMOS microcontrollers
as part of my "SchmELF" CDP1802 project), but meanwhile if you go here:

www.dbit.com/pub/e11/

... and grab the "vt100.ini" and "vt100.pdp" files, that gives you a simple
loopback program which makes the E11 VT100 console act as a terminal
connected to whatever's assigned to TT1: (a serial port or "TELCLIENT:"
Telnet client are the most useful -- which currently rules out OS/2 I
guess).

John Wilson
D Bit

Any faithful VT100 Emulators?

[Warren Toomey via cctalk]

OK, so I don't have a real VT100, so I'm accessing an old 4.3BSD system
with xterm and LXTerminal terminal emulators on Linux. Last night, for a
laugh, I ran vttest from the 1980s and the terminal emulators performed
woefully.

Which raises the question, are there any _good_ VT100 terminal
emulators, especially for Linux? For any other platforms?

Cheers, Warren

Re: Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not spin up ?

[Glen Slick via cctalk]

On Tue, Mar 21, 2017 at 5:49 AM, Pete Lancashire via cctalk
 wrote:
> Found at least one issue, open trace next to a via on the adapter. Ran out
> of time to keep checking.
>
> -pete

I just checked my HP 9000/382 and found I put the dead original
Quantum 50-pin SCSI hard drive back in it. I must have been using a
68-pin 9GB SCSI hard drive the last time I was tinkering with it, with
a 50-pin male / 68-pin male adapter. I don't remember having any
issues with that configuration.

I did a clean install of HP-UX 9.10 on my 9000/382 from a B2378-87054
CD image I got from hpmuseum.net

http://hpmuseum.net/display_item.php?sw=525

RE: Introducing the UUCP/Usenet Project

[Bill Gunshannon via cctalk]

From: cctalk [cctalk-boun...@classiccmp.org] on behalf of Seth Morabito via 
cctalk [cctalk@classiccmp.org]
Sent: Tuesday, March 21, 2017 5:44 PM
To: Warren Toomey via cctalk
Subject: Re: Introducing the UUCP/Usenet Project

* On Tue, Mar 21, 2017 at 10:33:36AM +1000, Warren Toomey via cctalk 
 wrote:
> Hi all, as part of the upcoming 50th anniversary of Unix in mid-2019,
> a bunch of people are working to rebuild the mid-1980s uucp/Usenet
> network using (real/simulated) period-accurate systems. To make things
> easier, we are simulating the dialup lines too.

This is an absolutely wonderful idea.

I would very much like to get one of my 3B2s up and running on this new
UUCP network. I still have a mostly fallow land line that I can use.
When I have some time in the next week or two, I'll try to get things
ready under SVR3 UNIX.

-Seth
--
Seth Morabito
w...@loomcom.com


My introduction to UUCPNet, emai and USENET News was on a couple of 3B2's.
Great machines.  I used to have two of them at home but they died over a decade 
ago.
Somewhere arounf  here I still have my xerox of the WE3200 architecture manual. 
 I
loved that CPU.

bill

Re: Introducing the UUCP/Usenet Project

[Ian S. King via cctalk]

On Tue, Mar 21, 2017 at 3:19 PM, Chuck Guzis via cctalk <
cctalk@classiccmp.org> wrote:

> On 03/21/2017 02:44 PM, Seth Morabito via cctalk wrote:
>
> > I would very much like to get one of my 3B2s up and running on this
> > new UUCP network. I still have a mostly fallow land line that I can
> > use. When I have some time in the next week or two, I'll try to get
> > things ready under SVR3 UNIX.
>
>
> For those without *nix boxes, there is a DOS/OS2 version called UUPC:
>
> https://github.com/swhobbit/UUPC
>
> I used this back in the pre-web days and it worked fine.
>
> --Chuck
>

There's a VMS version, too.  So many choices

-- 
Ian S. King, MSIS, MSCS, Ph.D. Candidate
The Information School 
Dissertation: "Why the Conversation Mattered: Constructing a Sociotechnical
Narrative Through a Design Lens

Archivist, Voices From the Rwanda Tribunal 
Value Sensitive Design Research Lab 

University of Washington

There is an old Vulcan saying: "Only Nixon could go to China."

Re: Introducing the UUCP/Usenet Project

[Chuck Guzis via cctalk]

On 03/21/2017 02:44 PM, Seth Morabito via cctalk wrote:

> I would very much like to get one of my 3B2s up and running on this
> new UUCP network. I still have a mostly fallow land line that I can
> use. When I have some time in the next week or two, I'll try to get
> things ready under SVR3 UNIX.


For those without *nix boxes, there is a DOS/OS2 version called UUPC:

https://github.com/swhobbit/UUPC

I used this back in the pre-web days and it worked fine.

--Chuck

Re: Introducing the UUCP/Usenet Project

[Seth Morabito via cctalk]

* On Tue, Mar 21, 2017 at 10:33:36AM +1000, Warren Toomey via cctalk 
 wrote:
> Hi all, as part of the upcoming 50th anniversary of Unix in mid-2019,
> a bunch of people are working to rebuild the mid-1980s uucp/Usenet
> network using (real/simulated) period-accurate systems. To make things
> easier, we are simulating the dialup lines too.

This is an absolutely wonderful idea.

I would very much like to get one of my 3B2s up and running on this new
UUCP network. I still have a mostly fallow land line that I can use.
When I have some time in the next week or two, I'll try to get things
ready under SVR3 UNIX.

-Seth
-- 
Seth Morabito
w...@loomcom.com

Re: Pair of Twiggys

[Ray Arachelian via cctalk]

On 03/16/2017 11:28 AM, geneb via cctalk wrote:
> On Wed, 15 Mar 2017, Warner Losh via cctalk wrote:
>
>> I'm waiting for the rise of cell phones to make it
>>
>> 202x All the world's an ARM running Android
>>
> on Linux. :) 
Actually goog's trying to get rid of the linux and replacing it with
another OS: https://en.wikipedia.org/wiki/Google_Fuchsia
Whether they use it to replace Android remains to be seen.

(And meanwhile AAPL is busy, or was, getting rid of all GPL stuff in its
OS.)

Re: Introducing the UUCP/Usenet Project

[Ray Arachelian via cctalk]

On 03/20/2017 08:33 PM, Warren Toomey via cctalk wrote:
> Hi all, as part of the upcoming 50th anniversary of Unix in mid-2019,
> a bunch of people are working to rebuild the mid-1980s uucp/Usenet
> network using (real/simulated) period-accurate systems. To make things
> easier, we are simulating the dialup lines too.
>
> Details of the (nearly) turnkey software to do this is at:
> https://github.com/DoctorWkt/4bsd-uucp
>
> A map of what nodes we have so far is at:
> https://raw.githubusercontent.com/DoctorWkt/4bsd-uucp/4.3BSD/uucp.png
>
> If you are interested in participating, email me back.
> Cheers, Warren
>

That's awesome!  Thank you for doing this!

Please consider adding an encryption layer to tcpdial via
openssl/libressl, even if it's done outside of the netbsd vm/physical
machine, and even if it's done with self-signed certs or even tunneled
over ssh.

Re: Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not spin up ?

[Pete Lancashire via cctalk]

Found at least one issue, open trace next to a via on the adapter. Ran out
of time to keep checking.

-pete

On Tue, Mar 21, 2017 at 4:10 AM, Rik Bos via cctalk 
wrote:

> The HP 9000/382 only supports SE scsi and the drive needs to be terminated.
>
> -Rik
>
> Van: Pete Lancashire via cctalk
> Verzonden: dinsdag 21 maart 2017 07:17
> Aan: General
> Onderwerp: Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not
> spin up ?
>
> Host is a HP 9000/382
>
> Copied the orig drive using a linux box, adaptec 2940N and good old dd
>
> Then swapped drives, a unused 9 GB 80 pin with a Chinese 80 to 50
> adapter.
>
> Did have to issue a spin up command and then copied the data to this drive
> again with dd.
>
> Powered all off, added a motor start jumper to the adapter and put it on
> the
> 9000/382. Motor will not start, added a jumper right on the drive, no spin.
>
> so .. any ideas what I'm doing wrong, or just try a different drive ?
>
> -pete
>
>
>

Re: Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not spin up ?

[Paul Berger via cctalk]

On 2017-03-20 11:50 PM, Pete Lancashire via cctalk wrote:

Host is a HP 9000/382

Copied the orig drive using a linux box, adaptec 2940N and good old dd

Then swapped drives, a unused 9 GB 80 pin with a Chinese 80 to 50
adapter.

Did have to issue a spin up command and then copied the data to this drive
again with dd.

Powered all off, added a motor start jumper to the adapter and put it on the
9000/382. Motor will not start, added a jumper right on the drive, no spin.

so .. any ideas what I'm doing wrong, or just try a different drive ?

-pete
Further to my previous reply, did you use the same SCA to 50 pin 
adapter?  If so then that would suggest the adapter is OK. If you are 
jumpering the drive to spin on power then it should start up as soon as 
power is applied, the pins on the SCA connector that affect motor 
operation are 38 RMT_START and 78 DLYD_START both should be left open 
for spin on power.   If RMT_START is grounded motor will only start on 
command if DLD_START is grounded motor start will be delayed 12 seconds 
X SCSI ID.   Does the drive spin if it is not connected to the SCSI 
bus?  I suppose it is also possible that the drive does not support 
"spin on power" so again knowing what drive model you are using would be 
helpful.


Paul.

Re: Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not spin up ?

[Paul Berger via cctalk]

On 2017-03-20 11:50 PM, Pete Lancashire via cctalk wrote:

Host is a HP 9000/382

Copied the orig drive using a linux box, adaptec 2940N and good old dd

Then swapped drives, a unused 9 GB 80 pin with a Chinese 80 to 50
adapter.

Did have to issue a spin up command and then copied the data to this drive
again with dd.

Powered all off, added a motor start jumper to the adapter and put it on the
9000/382. Motor will not start, added a jumper right on the drive, no spin.

so .. any ideas what I'm doing wrong, or just try a different drive ?

-pete
Well if the drive has an 80 pin SCA interface there is a chance that it 
is a LVD drive, which normally would be ok since LVD devices are obliged 
by the SCSI spec to be able to operate in SE mode as well, but the 
problem may be you 80 to 50 convertor.  I have encounter some that are 
not correctly wired and as a result do not always work.  LVD SCSI 
devices monitor a line call DIFFSENSE which is pin 46 on the SCA 
connector for SE operation this pin needs to be grounded, it is also 
possible that the drive itself has an option jumper to force SE mode if 
it is an LVD device.  It would help if you mentioned what the model of 
the drive in question is.


Paul.

Re: MUMPS in the news

[Philipp Hachtmann via cctalk]

On 03/20/2017 01:57 AM, Shoppa, Tim via cctalk wrote:

http://www.politico.com/agenda/story/2017/03/vista-computer-history-va-conspiracy-000367



Thank you, I ejoyed reading the article!


Philipp

RE: Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not spin up ?

[Rik Bos via cctalk]

The HP 9000/382 only supports SE scsi and the drive needs to be terminated.

-Rik

Van: Pete Lancashire via cctalk
Verzonden: dinsdag 21 maart 2017 07:17
Aan: General
Onderwerp: Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not spin up 
?

Host is a HP 9000/382

Copied the orig drive using a linux box, adaptec 2940N and good old dd

Then swapped drives, a unused 9 GB 80 pin with a Chinese 80 to 50
adapter.

Did have to issue a spin up command and then copied the data to this drive
again with dd.

Powered all off, added a motor start jumper to the adapter and put it on the
9000/382. Motor will not start, added a jumper right on the drive, no spin.

so .. any ideas what I'm doing wrong, or just try a different drive ?

-pete

Re: Introducing the UUCP/Usenet Project

[Warren Toomey via cctalk]

Camiel wrote:
> What would the requirements for the system be? How often would it need to
> be online?

I added an answer here:
https://github.com/DoctorWkt/4bsd-uucp#joining-the-growing-uucp-network

For central sites (like decvax) that had a lot of connectivity, you will
be expected to run them continuously. For edge sites which only dial in
to one other site to exchange news and e-mail, you can run them whenever
you want.

It's mostly simulated sites right now, but I'd love to see some real
systems come up and connect in. Not sure how to connect the simulated
sites (using TCP for the dialup links) and the real sites.

Cheers, Warren

Re: Introducing the UUCP/Usenet Project

[Camiel Vanderhoeven via cctalk]

Hi Warren,

What would the requirements for the system be? How often would it need to
be online? I¹m working on getting an OS for it, but if I succeed I might
be able to get my Convex C1 up and running in a few weeks, and wouldn¹t it
be nice to have that participate?


Camiel


On 3/21/17, 1:33 AM, "cctalk on behalf of Warren Toomey via cctalk"
 wrote:

>Hi all, as part of the upcoming 50th anniversary of Unix in mid-2019,
>a bunch of people are working to rebuild the mid-1980s uucp/Usenet
>network using (real/simulated) period-accurate systems. To make things
>easier, we are simulating the dialup lines too.
>
>Details of the (nearly) turnkey software to do this is at:
>https://github.com/DoctorWkt/4bsd-uucp
>
>A map of what nodes we have so far is at:
>https://raw.githubusercontent.com/DoctorWkt/4bsd-uucp/4.3BSD/uucp.png
>
>If you are interested in participating, email me back.
>Cheers, Warren

Re: TRS-80 Model 1 Expansion Interface question?

[Eric Smith via cctalk]

On Mon, Mar 20, 2017 at 6:46 PM, Win Heagy via cctech  wrote:

> The expansion interface hardware manual indicates
> it is an FD1771B-01, but the service manual indicates a couple
> possibilitiesFD1771 A/B -01 -11.  Any considerations to look for here?
>

All other things being equal, I'd use the FD1771x-01, with x being either A
or B.

The A vs. B is just whether the chip is in a ceramic (A) or plastic (B)
package. This makes no difference in the TRS-80 EI.

The numeric suffix indicates functional or specification differences.
The -01 suffix is rated for operation at 1 MHz or 2 MHz, which is fine for
the TRS-80 EI, which runs it at 1 MHz (as required for 5.25-inch
standard-density floppies).
The -02 suffix is rated for operation at 2 MHz only, so in principle it
isn't guaranteed to work in the TRS-80 EI, but in practice it should work
fine.
The -11 suffix is for a part that has an internal substrate bias generator,
so pin 1 (Vbb) should be disconnected. This wouldn't meet spec in the
TRS-80 EI without disconnecting pin 1, though it's possible that it might
work OK without doing so.

At 1 MHz, the available stepping rate selections for the -01 and -11 are
12, 20, and 40 ms, while for the -02 they are 12, 16, and 20 ms.

Re: TRS-80 Model 1 Expansion Interface question?

[Fred Cisin via cctalk]

On Mon, 20 Mar 2017, Win Heagy via cctech wrote:

But, the FD1771 IC, for some reason, was removed from an otherwise
apparently functional EI.
http://imgur.com/a/3NzOh
Is there any reason why this chip would be removed?  I see a number of them
on ebay for around $25.  The expansion interface hardware manual indicates
it is an FD1771B-01, but the service manual indicates a couple
possibilitiesFD1771 A/B -01 -11.  Any considerations to look for here?



Some owners replaced the 1771 with a daughterboard that contained a 1771 
plus a better data separation circuit.  The 1771 included internal data 
separation, which WD advised not to use.

"EVERYBODY" used one of those.
Before selling the Expansion Interface, the previous owner might have 
removed the data separator and sold it separately.


Some owners replaced the 1771 with a daughterboard that contained a 1771 
plus a 179x, called a "Doubler".  That added double density (MFM) support. 
The Doubler included a 1771 because the 179x was incapable of writing some 
of the address marks that Model 1 TRSDOS used in its disk format.

"EVERYBODY" used one of those.
Before selling the Expansion Interface, the previous owner might have 
removed the Doubler and sold it separately.


Both the Data Separator and the Doubler COULD HAVE used the 1771 that was 
taken out, but usually came with one already installed.
1) it made for one less prying out, bending pins and reinstalling with 
bent pins or backwards

2) it meant that there was a known good chip going in.


Some owners replaced the 1771 with an aftermarket daughterboard that 
contained a 1771 plus some circuitry to do 8" SSSD.  Often that was 
accompanied by a sandwich board for the Z80 in the CPU to remap memory for 
CP/M, and a CP/M for it.

(such as Parasitic Engineering, and Omikron Mapper)
"not EVERYBODY" used one of those.
Before selling the Expansion Interface, the previous owner might have 
removed the adapter and sold it separately.
(There also existed a "remapped" CP/M for the TRS80 that would work 
without the hardware remapping, although in general no known 
commercial software worked with that setup.)




In addition to the 1771, does your Expansion Interface include the "RS232 
board"?  A Radio Shack Computer Store manager asserted that any 
incompatabilities with the standard were legitimate, "because OUR RS-232 
board is RADIO SHACK 232"
Before selling the Expansion Interface, the previous owner might have 
removed the adapter and sold it separately.



There were a few modifications to the EI over time.
The first version had a simple straight through cable.
Then they made some changes and switched to a cable with a circuit box in 
the middle of it.
Then they made some changes and switched to a cable with a circuit box in 
the middle of it, plus a small second cable.
Then they made some changes and switched to a simple straight through 
cable.
Make sure that you use the appropriate cable(s) for the level of changes 
that were made to yours.


To keep reliability, do not plug/unplug and move the CPU and the EI.
If you are going to do so, then bolt both pieces to a piece of plywood. 
RIV-NUTS or NUTSERTS into holes drilled into the bottom of the EI and CPU.



You did not HAVE TO put the power supply for the CPU into the compartment 
in the EI.  If you do, cutting a notch in the case means that you can tuck 
the excess cord in there to have 3" of power cord between the EI and CPU, 
instead of a couple of feet going out the BACK and around to the front.



The RCA TV set that Radio Shack used as a monitor had a great big empty 
space where the tuner used to be.  Plenty of room for a disk drive, or a 
pair of half-height drives.  Mu-metal surround was kinda important.


The CPU needed a trivial modification to add lower-case.  Often 
accompanied by adding a "Control key", and sometimes a mod to give reverse 
video.  Remember to put glyptol on the screw after making modifications, 
since warranty was void if there wasn't any glyptol.



--
Grumpy Ol' Fred ci...@xenosoft.com

Re: TRS-80 Model 1 Expansion Interface question?

[Fred Cisin via cctalk]

On Mon, 20 Mar 2017, ben via cctech wrote:

Act quick before Radio Shack closes its doors forever.


Radio Shack stores haven't had any of that stuff for decades.


One Doubler on eBay; no 1771s

Re: TRS-80 Model 1 Expansion Interface question?

[ben via cctalk]

On 3/20/2017 9:43 PM, Fred Cisin via cctech wrote:

On Mon, 20 Mar 2017, Win Heagy via cctech wrote:

But, the FD1771 IC, for some reason, was removed from an otherwise
apparently functional EI.
http://imgur.com/a/3NzOh
Is there any reason why this chip would be removed?  I see a number of
them
on ebay for around $25.  The expansion interface hardware manual
indicates
it is an FD1771B-01, but the service manual indicates a couple
possibilitiesFD1771 A/B -01 -11.  Any considerations to look for
here?



Some owners replaced the 1771 with a daughterboard that contained a 1771
plus a better data separation circuit.  The 1771 included internal data
separation, which WD advised not to use.
"EVERYBODY" used one of those.
Before selling the Expansion Interface, the previous owner might have
removed the data separator and sold it separately.

Some owners replaced the 1771 with a daughterboard that contained a 1771
plus a 179x, called a "Doubler".  That added double density (MFM)
support. The Doubler included a 1771 because the 179x was incapable of
writing some of the address marks that Model 1 TRSDOS used in its disk
format.
"EVERYBODY" used one of those.
Before selling the Expansion Interface, the previous owner might have
removed the Doubler and sold it separately.

Both the Data Separator and the Doubler COULD HAVE used the 1771 that
was taken out, but usually came with one already installed.
1) it made for one less prying out, bending pins and reinstalling with
bent pins or backwards
2) it meant that there was a known good chip going in.


Some owners replaced the 1771 with an aftermarket daughterboard that
contained a 1771 plus some circuitry to do 8" SSSD.  Often that was
accompanied by a sandwich board for the Z80 in the CPU to remap memory
for CP/M, and a CP/M for it.
(such as Parasitic Engineering, and Omikron Mapper)
"not EVERYBODY" used one of those.
Before selling the Expansion Interface, the previous owner might have
removed the adapter and sold it separately.
(There also existed a "remapped" CP/M for the TRS80 that would work
without the hardware remapping, although in general no known commercial
software worked with that setup.)



In addition to the 1771, does your Expansion Interface include the
"RS232 board"?  A Radio Shack Computer Store manager asserted that any
incompatabilities with the standard were legitimate, "because OUR RS-232
board is RADIO SHACK 232"
Before selling the Expansion Interface, the previous owner might have
removed the adapter and sold it separately.


There were a few modifications to the EI over time.
The first version had a simple straight through cable.
Then they made some changes and switched to a cable with a circuit box
in the middle of it.
Then they made some changes and switched to a cable with a circuit box
in the middle of it, plus a small second cable.
Then they made some changes and switched to a simple straight through
cable.
Make sure that you use the appropriate cable(s) for the level of changes
that were made to yours.

To keep reliability, do not plug/unplug and move the CPU and the EI.
If you are going to do so, then bolt both pieces to a piece of plywood.
RIV-NUTS or NUTSERTS into holes drilled into the bottom of the EI and CPU.


You did not HAVE TO put the power supply for the CPU into the
compartment in the EI.  If you do, cutting a notch in the case means
that you can tuck the excess cord in there to have 3" of power cord
between the EI and CPU, instead of a couple of feet going out the BACK
and around to the front.


The RCA TV set that Radio Shack used as a monitor had a great big empty
space where the tuner used to be.  Plenty of room for a disk drive, or a
pair of half-height drives.  Mu-metal surround was kinda important.

The CPU needed a trivial modification to add lower-case.  Often
accompanied by adding a "Control key", and sometimes a mod to give
reverse video.  Remember to put glyptol on the screw after making
modifications, since warranty was void if there wasn't any glyptol.


Act quick before Radio Shack closes its doors forever.



--
Grumpy Ol' Fred ci...@xenosoft.com


Ben.
What happens to my life tube replacement guarantee now?

Suggestions why SCSI 80 drive w/ SCSI2 (50) adapter will not spin up ?

[Pete Lancashire via cctalk]

Host is a HP 9000/382

Copied the orig drive using a linux box, adaptec 2940N and good old dd

Then swapped drives, a unused 9 GB 80 pin with a Chinese 80 to 50
adapter.

Did have to issue a spin up command and then copied the data to this drive
again with dd.

Powered all off, added a motor start jumper to the adapter and put it on the
9000/382. Motor will not start, added a jumper right on the drive, no spin.

so .. any ideas what I'm doing wrong, or just try a different drive ?

-pete

Re: TRS-80 Model 1 Expansion Interface question?

[Peter Cetinski via cctalk]

> On Mar 20, 2017, at 8:46 PM, Win Heagy via cctech  
> wrote:
> 
> Is there any reason why this chip would be removed?  I see a number of them
> on ebay for around $25.  The expansion interface hardware manual indicates
> it is an FD1771B-01, but the service manual indicates a couple
> possibilitiesFD1771 A/B -01 -11.  Any considerations to look for here?
> 

The EI may have had a double density board which plugs into the FDC chip 
socket.  The FDC chip then plugs into the doubler.  Without the doubler you 
only have single density.  Original Percom or Tandy doublers are fairly rare to 
find today so someone may have pulled it out to sell.  Ian Mavric in Australia 
does make reproductions though.

TRS-80 Model 1 Expansion Interface question?

[Win Heagy via cctalk]

I have a clean, and somewhat functional expansion interface that I just
tested over the weekend.  Without the EI connected, the model 1 reports
~16K RAM and with the EI the model 1 reports ~48K, so the RAM seems OK.
But, the FD1771 IC, for some reason, was removed from an otherwise
apparently functional EI.
http://imgur.com/a/3NzOh

Is there any reason why this chip would be removed?  I see a number of them
on ebay for around $25.  The expansion interface hardware manual indicates
it is an FD1771B-01, but the service manual indicates a couple
possibilitiesFD1771 A/B -01 -11.  Any considerations to look for here?

Thanks,

Win