Re: Revive 11/34

[Jerry Weiss via cctalk]

> On 12/8/2017 3:50 PM, Jerry Weiss wrote:
>> On Dec 8, 2017, at 2:25 PM, John Welch via cctech 
>>  wrote:
>> 
>>> I am reviving an 11/34. Cards are:
>>> 
>>> Back/Fans [M8266]  Front of machine where keypad is.
>>>   [M8265]
>>>   [M9312] [M7859]
>>>   [M7762]
>>>   [OPEN]  [M7860]
>>>   [M7840]
>>>   Bus grant in third from front slot
>>>   [M9302] [M7856]
>>> The 7856 is hooked to a cable/null modem (i think)/PC running 
>>> XP
>>> 
>>> When I first powered on the programmers console said '7' and I powered off, 
>>> then back on, and now it says '5'
>>> 
>>> Any suggestions as to what to try first?  I may have the bus grant in 
>>> backwards.  I have other boards I can try.
>>> 
>>> Sincerely,
>>> John Welch
>>> :qw
>>> 
>> 
>> 1) The G727A bus grant card is keyed (somewhat). It should be in Row D 
>> (fourth from the back)
>>  It won’t seat evenly if reversed. At least that is what my scraped 
>> knuckles remember. 
>> 
>>  You can temporarily pull it out to finish the check out.  There’s 
>> nothing past the 
>>   M7840 that requires DMA.

Ignore this last suggestion (see below).

>> 
>> 2) Check the baud rate, stop bits and parity settings on both the 
>> Hyperterminal and the M785 to make sure they match. 
>>  
>> 3)  Are you seeing a single 7 or 5 on  KY11-LB Programmer Console or on the 
>> Hyperterminal?
>>  
>>  An other status led’s lit on the KY11-LB?
>> 
>> 4) I don’t see any memory listed…  Do you have any M7847’s?  
>> 
>> 5) Grab a copy of EK-11034-UG-001 PDP-11-34 System User’s Manual for more 
>> info.
>> 
>> 
>> Jerry
>> 
>> 
> 
> 
> On Dec 8, 2017, at 5:26 PM, John Welch via cctech  
> wrote:
> 
> Update:
> This is the map of the machine:
> 
>    AAA BBB CCC DDD EEE FFF 
> (Rear/Fans/Power Supply) 1 [M8266] (Front/Keypad/DC ON)
>  2 [M8265] 
>  3 [M9312] [M7859] 
>  4 [M7891] 
>  5 [M7762] 
>  6 [M7860] 
>  7 [M7840] 
>  8 GNT 
>  9 [M9302] [M7856] 
>    AAA BBB CCC DDD EEE FFF 
> Reseating the ribbon cable on the M7859 changed the display.  I have replaced 
> the M7840 with a G7273.
> Now when I power on it says (dim)0, (bright)0, blank, (dim)0, blank, blank.
> I have reseated the M7859, I don't think I have another one.
> Maybe I should hit it with a vacuum.
> I had forgotten about needing to cut a wire for DMA.  Can you give me a 
> refresher on how to tell which slots are cut?  I remember having to turn the 
> chassis over and looking for a particular wire but that was >15 years ago.

Your update has a M7891 (MS11) which addresses the memory questions.

The Programmers Console display is not correct.  It should be 7 digits, either 
000 when running or some other data or address value.
Check the cable orientation.  see 
http://bitsavers.informatik.uni-stuttgart.de/pdf/dec/pdp11/1134/KY11-LB_MaintMan.pdf
 

 chapter 9.

A light cleaning and reseating all the boards is an easy place to start.

For NPG changes see 
http://bitsavers.informatik.uni-stuttgart.de/pdf/dec/pdp11/1134/1134_UsersManual.pdf
 

 section 4.2.2.2

Ignore my earlier comment about leaving out the G727a.  I had slipped into QBUS 
thinking mode in error.



> On Dec 8, 2017, at 5:49 PM, John Welch  wrote:
> 
> I also have an 11/04 that I went and drug out.  It is configured like this:
> 
> 11/04:
>    AAA BBB CCC DDD EEE FFF  
> (Rear/Fans/Power Supply) 1 [M7263]  (Front/Keypad/DC ON)
>  2 [M7847]  
>  3 [M7859]  
>  4 [M7847]  
>  5 GNT  
>  6 [M7762]  
>  7 [M7840]  
>  8 [DILOG]  
>  9   {nothing}  
>    AAA BBB CCC DDD EEE FFF  
> I am 

Re: Revive 11/34

[Jerry Weiss via cctalk]

On Dec 8, 2017, at 2:25 PM, John Welch via cctech  wrote:
> 
> I am reviving an 11/34. Cards are:
> 
> Back/Fans [M8266]  Front of machine where keypad is.
> 
>   [M8265]
> 
>   [M9312] [M7859]
> 
>   [M7762]
> 
>   [OPEN]  [M7860]
> 
>   [M7840]
> 
>   Bus grant in third from front slot
> 
>   [M9302] [M7856]
> The 7856 is hooked to a cable/null modem (i think)/PC running XP
> 
> When I first powered on the programmers console said '7' and I powered off, 
> then back on, and now it says '5'
> 
> Any suggestions as to what to try first?  I may have the bus grant in 
> backwards.  I have other boards I can try.
> 
> Sincerely,
> John Welch
> :qw


1) The G727A bus grant card is keyed (somewhat). It should be in Row D 
(fourth from the back)
 It won’t seat evenly if reversed. At least that is what my scraped 
knuckles remember. 

 You can temporarily pull it out to finish the check out.  There’s nothing 
past the 
  M7840 that requires DMA.

2) Check the baud rate, stop bits and parity settings on both the Hyperterminal 
and the M785 to make sure they match. 
 
3)  Are you seeing a single 7 or 5 on  KY11-LB Programmer Console or on the 
Hyperterminal?
 
 An other status led’s lit on the KY11-LB?

4) I don’t see any memory listed…  Do you have any M7847’s?  

5) Grab a copy of EK-11034-UG-001 PDP-11-34 System User’s Manual for more info.


Jerry

RE: Revive 11/34

[Henk Gooijen via cctalk]

Van: John Welch via cctech
Verzonden: vrijdag 8 december 2017 21:25
Aan: cct...@classiccmp.org
Onderwerp: Revive 11/34

I am reviving an 11/34. Cards are:

Back/Fans [M8266]  Front of machine where keypad is.

   [M8265]

   [M9312] [M7859]

   [M7762]

   [OPEN]  [M7860]

   [M7840]

   Bus grant in third from front slot

   [M9302] [M7856]
The 7856 is hooked to a cable/null modem (i think)/PC running
XP

When I first powered on the programmers console said '7' and I powered
off, then back on, and now it says '5'

Any suggestions as to what to try first?  I may have the bus grant in
backwards.  I have other boards I can try.

Sincerely,
John Welch
:qw


It is not completely clear (to me) how the modules are installed in the
backplane. Standing in front of the 11/34 processor box (looking at the
console), slot number 1 is at the right side. Each slot has 6 positions.
Position A is at the rear side, followed by B thru F. Position F is
thus at the front side.
There is no confusion about the first 4 slots.

Slot 1 and 2 hold the 11/34A processor boards, with M8266 in slot 1,
and M8265 in slot 2.
Slot 3, positions A and B has the M9312 bootstrap/terminator board,
and slot3, positions C thru F has the M7859 KY11-LB programmer's console
interface board.
Slot 4 holds the RL11 interface. This module does "DMA", so the NPR
jumper must be cut (open) on the backplane.
Slot 5 has an SPC in positions C thru F. I had to look it up; it is the
DR11-C.

We are up to slot 6. Now things get "interesting" ... is that M7840 a typo?
The field guide says that this is a KE11-B Extended Arithmetic Element.
I do not know that board, is it "hex" or "quad"?
Not sure that board belongs there ... and if it is quad, I assume it has
to be in positions C thru F. I would suggest to pull this module, and
check the NPR wire presence on the backplane. You need a G727A or G7273
in this slot when the M7840 is removed.

If you are not skipping slots (see below), we are now at slot 7. There
is probably a G727A grant continuity card (aka "knockle buster") in
position D. That would be OK, but if the NPR jumper is cut on the
backplane, you would need a G7273 continuity and NPR card in positions
C - D. It is easy to have the G727 put in wrong. The 4 copper "jumper"
traces should be facing the next higher-numbered slot.

Then you say that the next slot has the M9202 (in position A - B) and
the M7856 (SLU and RTC) in positions C thru F.
The M9202 connects two system units (backplanes). So, what is the next
backplane?  Or do you have the M9202 in slot 8 and slot 9, positions
A - B?  I have never seen that ...

I am missing one slot. The 11/34 backplane has 9 slots.

When you power up the system, the display should show 6 octal numbers.
If only one digit shows a number (7 or 5 or whatever), there is an
issue with the console itself, or the M7859. The 6 digits of the display
are multiplexed. Maybe the connection cable between the console and the
M7859 - damaged/knicked? It is worth checking out the simpler things first.

Henk.

Re: IBM 3270 controller emulation

[Guy Sotomayor Jr via cctalk]

It might be worthwhile to look at the source for hercules (370, 390, z/series) 
emulator since that
includes support for 3270 terminals through tn3270.  It’s pretty good since I 
can use actual 327x
CUT terminals connected to a 3174 controller which connects to hercules 
emulating the mainframe.

TTFN - Guy

> On Dec 8, 2017, at 5:22 PM, Charles Anthony via cctalk 
>  wrote:
> 
> I am trying to wire 3270 support into the DPS8/M emulator.
> 
> Multics supports 3270 via a bisync connection to the 3270 controller.
> Multics sends commands to the Front End Network processor, which
> (originally) passed the commands down the bisync line to the 3270.
> 
> I have a running Multics and running 3270 display emulators using tn3270
> (3270 over telnet), so I need to write the code that maps the Multics
> commands into 3270 controller commands (and vice versa) and manages the
> telnet connections to the 3270 display emulators and maps the tn3270
> traffic into 3270 controllers.
> 
> I don't need to actually implement the bisync communications; the
> controller emulator will be running inside the FNP emulator, but I need to
> express controller responses to Multics in the bisync format, as Multics is
> expecting that the responses arrived over a bisync connection.
> 
> The problem is that I have no idea how the 3270 controllers worked; I've
> looked through the bitsavers collection; those documents are largely
> concerned with the displays and tend to treat the controllers as 'black
> boxes' that just do the right thing.
> 
> So I am seeking pointers to documentation that will give me a better grasp
> of the controller functionality and/or discussions with someone who knows
> how they work.
> 
> Thanks,
> -- Charles

IBM 3270 controller emulation

[Charles Anthony via cctalk]

I am trying to wire 3270 support into the DPS8/M emulator.

Multics supports 3270 via a bisync connection to the 3270 controller.
Multics sends commands to the Front End Network processor, which
(originally) passed the commands down the bisync line to the 3270.

I have a running Multics and running 3270 display emulators using tn3270
(3270 over telnet), so I need to write the code that maps the Multics
commands into 3270 controller commands (and vice versa) and manages the
telnet connections to the 3270 display emulators and maps the tn3270
traffic into 3270 controllers.

I don't need to actually implement the bisync communications; the
controller emulator will be running inside the FNP emulator, but I need to
express controller responses to Multics in the bisync format, as Multics is
expecting that the responses arrived over a bisync connection.

The problem is that I have no idea how the 3270 controllers worked; I've
looked through the bitsavers collection; those documents are largely
concerned with the displays and tend to treat the controllers as 'black
boxes' that just do the right thing.

So I am seeking pointers to documentation that will give me a better grasp
of the controller functionality and/or discussions with someone who knows
how they work.

Thanks,
-- Charles

Re: RX02 Difficulties

[jim stephens via cctalk]

On 12/8/2017 4:34 PM, Charles Anthony via cctalk wrote:

On Fri, Dec 8, 2017 at 4:30 PM, Jerry Weiss via cctalk <
cctalk@classiccmp.org> wrote:


On Dec 8, 2017, at 5:17 PM, Aaron Jackson  wrote:
=
3) Try and contrast to the other drive as previously covered.

This will help rule out a few things and provide some better direction.



I know that there some very low-level disk analysis tools (Kyroflux or
something?) Would it be feasible to use one of those tools to verify the
format and data integrity of the floppies?

-- Charles
This brings up a point I'm interested in.  I've got a kryoflux and the 
parts that hopefully will let me run regular 8" drive.  Does anyone have 
experience writing RX01 or RX02 images with such drives onto blank media 
(non dec pre-formatted)?


I'm really hoping to create test media to use before I risk any of the 
masters I have to any drives (I have a Minc 11 with a lot of floppies).


I hope to image all the media I have via the same 8" drives, and not 
fiddle with the Minc or RX02 I have, but to just get them going, and use 
them on systems.


thanks
Jim

Re: RX02 Difficulties

[Charles Anthony via cctalk]

On Fri, Dec 8, 2017 at 4:30 PM, Jerry Weiss via cctalk <
cctalk@classiccmp.org> wrote:

> On Dec 8, 2017, at 5:17 PM, Aaron Jackson  wrote:
> >
> =
> 3) Try and contrast to the other drive as previously covered.
>
> This will help rule out a few things and provide some better direction.
>
>
I know that there some very low-level disk analysis tools (Kyroflux or
something?) Would it be feasible to use one of those tools to verify the
format and data integrity of the floppies?

-- Charles

Re: RX02 Difficulties

[Jerry Weiss via cctalk]

On Dec 8, 2017, at 5:17 PM, Aaron Jackson  wrote:
> 
>>> On Dec 8, 2017, at 12:53 PM, Aaron Jackson via cctalk 
>>>  wrote:
>>> 
 On Fri, Dec 8, 2017 at 3:03 PM, Aaron Jackson  
 wrote:
> 
> Manual says it should be S1=off, S2=on for RX211 and RXV21
 
 In the photo, I think S1 is on and S2 is off. Check them with an
 ohmmeter if in doubt!
 
 -tony
>>> 
>>> Yes - you are right. I switched them back to how they were when I got
>>> the drive. I think one of the switches was half down because XXDP
>>> actually does something now.
>>> 
>>> Most of the tests now look something like this:
>>> 
>>> CZRXFB0 DVC FTL ERR  00034 ON UNIT 00 TST 031 SUB 000 PC: 003476
>>> SECTOR ADR - LGC TST
>>> SECTOR ADDRESS ERROR
>>>  EXPECTED SECTOR=18.
>>>TARGET SECTOR=17.
>>> 
>>> I suppose these should match?
>>> 
>>> Starting to think I might need to confuse myself with my logic analyzer
>>> and the RX02 control board.
>>> 
>>> Thanks,
>>> Aaron.
>> 
>> To isolate the problem further, try to see if any of the errors follow
>> the media  as you move them between drives.  
>> 
>> If the same errors occur on both drives, regardless of media then the
>> RX02 system board or perhaps the Qbus controller are at fault.  
>> The field maintenance prints should allow you to trace the fault down
>> a bit further,  with or w/o a logic analyzer.
>> 
>> How many different types of errors do you see?
>> 
>> Jerry
> 
> Thanks for the info Jerry.
> 
> I get read errors, data errors, density errors, sector addressing
> errors. Probably every kind of error xxdp can give :)
> 
> Please see this link if you are interested:
> 
> https://aaronsplace.co.uk/private/o/48859c14f6a619a5316d6af37d60579c.txt
> 
> I will take a proper look through the field manuals tomorrow, and also
> try what you suggested with trying the same media in both drives.
> 
> Thanks,
> Aaron.


 When you have many errors it can be hard to separate the primary fault(s) from 
the knock-on errors.
 The M7745/M7744 or Media Errors dominate the entries.
 
1) Try to verify the media is a DEC 8 Inch formatted RX02 or RX01 if you do not 
know the source of the 
 the disks.   The disk should have only 1 hole punched for index  on the 
media itself.   Even if it is
 a DEC Brand, there’s still possibility that the media has been exposed to 
strong magnetic fields.

 I have not seen much natural  bit-rot on my floppy media, but YMMV.   If 
could find someone local 
 with RX02 drives to confirm your media, that would also help rule out some 
things.   

  Many third party drives and controllers that were DEC compatible also had 
the ability to do a 
  low level format of media, something the native RX02 did not.  So if the 
media type is correct, but
  the format is not, they may be salvageable (with complete loss of 
original data).

2) Check the connections between the drives and controllers. Gently clean 
contacts, especially anything
gold plated.  Getting clean signals from the floppies is critical if the RW 
electronics are to function.

3) Try and contrast to the other drive as previously covered.  

This will help rule out a few things and provide some better direction.


Jerry 

Re: Types of corrosion on computers

[Santo Nucifora via cctalk]

I've seen this a few times.  I never knew exactly what it was but it
usually comes off but there is staining left over.  Here are a couple of
explanations from Google.

*White rust* is a *white* powdery deposit formed from a natural *corrosion*
process that can occur on any new zinc coated steel product. It is damaging
to the appearance of the steel, not to mention to the anti-*corrosion*
layer of zinc that protects the body of the steel.

Galvanized *metals* also *rust*, but they do so at a slow rate unless the
galvanized coating has been damaged. Brass, silver, and bronze tarnish as
they interact with the atmosphere. Aluminum oxidizes into a *white powder*,
although the *powder* binds chemically to the *metal* beneath, blocking
further *corrosion*.

On Fri, Dec 8, 2017 at 6:09 PM, Adrian Stoness via cctalk <
cctalk@classiccmp.org> wrote:

> water get sprayed on it?
>
>
> On Fri, Dec 8, 2017 at 5:06 PM, dwight via cctalk 
> wrote:
>
> > Could be the zinc plating?
> >
> > Dwight
> >
> >
> > 
> > From: cctalk  on behalf of Sam O'nella
> via
> > cctalk 
> > Sent: Friday, December 8, 2017 2:46:40 PM
> > To: General Discussion: On-Topic and Off-Topic Posts
> > Subject: Types of corrosion on computers
> >
> > I've seen rust and dust, but there's an old vaxstation II at Goodwill
> > Computers in Austin right now (very cheap, anyone welcome to buy it and
> get
> > it off my mind) but as most things, I checked out the back and see some
> > circles of white corrosion on the back where the cards? are contacting
> the
> > case.
> >
> > I don't really have room or time but I don't own anything that uses QBUS
> or
> > is almost related to some of the neat iron some of you all collect (I've
> > mostly collected way too many home computer history items).
> >
> > Anyway, what is that type of white corrosion on metal?  Would one
> probably
> > assume this means any bus would be corroded and this wouldn't be a
> computer
> > for the faint of heart hobbyist? I've only seen that maybe from batteries
> > but it's in an unusual place and pattern (I think).
> >
>

Re: RX02 Difficulties

[Aaron Jackson via cctalk]

>> On Dec 8, 2017, at 12:53 PM, Aaron Jackson via cctalk 
>>  wrote:
>> 
>>> On Fri, Dec 8, 2017 at 3:03 PM, Aaron Jackson  
>>> wrote:
 
 Manual says it should be S1=off, S2=on for RX211 and RXV21
>>> 
>>> In the photo, I think S1 is on and S2 is off. Check them with an
>>> ohmmeter if in doubt!
>>> 
>>> -tony
>> 
>> Yes - you are right. I switched them back to how they were when I got
>> the drive. I think one of the switches was half down because XXDP
>> actually does something now.
>> 
>> Most of the tests now look something like this:
>> 
>> CZRXFB0 DVC FTL ERR  00034 ON UNIT 00 TST 031 SUB 000 PC: 003476
>> SECTOR ADR - LGC TST
>>  SECTOR ADDRESS ERROR
>>   EXPECTED SECTOR=18.
>> TARGET SECTOR=17.
>> 
>> I suppose these should match?
>> 
>> Starting to think I might need to confuse myself with my logic analyzer
>> and the RX02 control board.
>> 
>> Thanks,
>> Aaron.
>
> To isolate the problem further, try to see if any of the errors follow
> the media  as you move them between drives.  
>
> If the same errors occur on both drives, regardless of media then the
> RX02 system board or perhaps the Qbus controller are at fault.  
> The field maintenance prints should allow you to trace the fault down
> a bit further,  with or w/o a logic analyzer.
>
> How many different types of errors do you see?
>
> Jerry

Thanks for the info Jerry.

I get read errors, data errors, density errors, sector addressing
errors. Probably every kind of error xxdp can give :)

Please see this link if you are interested:

https://aaronsplace.co.uk/private/o/48859c14f6a619a5316d6af37d60579c.txt

I will take a proper look through the field manuals tomorrow, and also
try what you suggested with trying the same media in both drives.

Thanks,
Aaron.

Re: Types of corrosion on computers

[Adrian Stoness via cctalk]

water get sprayed on it?


On Fri, Dec 8, 2017 at 5:06 PM, dwight via cctalk 
wrote:

> Could be the zinc plating?
>
> Dwight
>
>
> 
> From: cctalk  on behalf of Sam O'nella via
> cctalk 
> Sent: Friday, December 8, 2017 2:46:40 PM
> To: General Discussion: On-Topic and Off-Topic Posts
> Subject: Types of corrosion on computers
>
> I've seen rust and dust, but there's an old vaxstation II at Goodwill
> Computers in Austin right now (very cheap, anyone welcome to buy it and get
> it off my mind) but as most things, I checked out the back and see some
> circles of white corrosion on the back where the cards? are contacting the
> case.
>
> I don't really have room or time but I don't own anything that uses QBUS or
> is almost related to some of the neat iron some of you all collect (I've
> mostly collected way too many home computer history items).
>
> Anyway, what is that type of white corrosion on metal?  Would one probably
> assume this means any bus would be corroded and this wouldn't be a computer
> for the faint of heart hobbyist? I've only seen that maybe from batteries
> but it's in an unusual place and pattern (I think).
>

Re: Types of corrosion on computers

[dwight via cctalk]

Could be the zinc plating?

Dwight



From: cctalk  on behalf of Sam O'nella via 
cctalk 
Sent: Friday, December 8, 2017 2:46:40 PM
To: General Discussion: On-Topic and Off-Topic Posts
Subject: Types of corrosion on computers

I've seen rust and dust, but there's an old vaxstation II at Goodwill
Computers in Austin right now (very cheap, anyone welcome to buy it and get
it off my mind) but as most things, I checked out the back and see some
circles of white corrosion on the back where the cards? are contacting the
case.

I don't really have room or time but I don't own anything that uses QBUS or
is almost related to some of the neat iron some of you all collect (I've
mostly collected way too many home computer history items).

Anyway, what is that type of white corrosion on metal?  Would one probably
assume this means any bus would be corroded and this wouldn't be a computer
for the faint of heart hobbyist? I've only seen that maybe from batteries
but it's in an unusual place and pattern (I think).

Types of corrosion on computers

[Sam O'nella via cctalk]

I've seen rust and dust, but there's an old vaxstation II at Goodwill
Computers in Austin right now (very cheap, anyone welcome to buy it and get
it off my mind) but as most things, I checked out the back and see some
circles of white corrosion on the back where the cards? are contacting the
case.

I don't really have room or time but I don't own anything that uses QBUS or
is almost related to some of the neat iron some of you all collect (I've
mostly collected way too many home computer history items).

Anyway, what is that type of white corrosion on metal?  Would one probably
assume this means any bus would be corroded and this wouldn't be a computer
for the faint of heart hobbyist? I've only seen that maybe from batteries
but it's in an unusual place and pattern (I think).

Re: RX02 Difficulties

[Jerry Weiss via cctalk]

> On Dec 8, 2017, at 12:53 PM, Aaron Jackson via cctalk  
> wrote:
> 
>> On Fri, Dec 8, 2017 at 3:03 PM, Aaron Jackson  
>> wrote:
>>> 
>>> Manual says it should be S1=off, S2=on for RX211 and RXV21
>> 
>> In the photo, I think S1 is on and S2 is off. Check them with an
>> ohmmeter if in doubt!
>> 
>> -tony
> 
> Yes - you are right. I switched them back to how they were when I got
> the drive. I think one of the switches was half down because XXDP
> actually does something now.
> 
> Most of the tests now look something like this:
> 
> CZRXFB0 DVC FTL ERR  00034 ON UNIT 00 TST 031 SUB 000 PC: 003476
> SECTOR ADR - LGC TST
>  SECTOR ADDRESS ERROR
>   EXPECTED SECTOR=18.
> TARGET SECTOR=17.
> 
> I suppose these should match?
> 
> Starting to think I might need to confuse myself with my logic analyzer
> and the RX02 control board.
> 
> Thanks,
> Aaron.

To isolate the problem further, try to see if any of the errors follow
the media  as you move them between drives.  

If the same errors occur on both drives, regardless of media then the
RX02 system board or perhaps the Qbus controller are at fault.  
The field maintenance prints should allow you to trace the fault down
a bit further,  with or w/o a logic analyzer.

How many different types of errors do you see?

Jerry

Re: RX02 Difficulties

[js--- via cctalk]

On 12/8/2017 2:13 PM, Aaron Jackson via 
cctalk wrote:

I wonder if there's a problem with the floppy you are using?

Remember, the RX0x drives can't hard reformat the floppies (as in, write the
sector headers), so if the floopy has a problem, you can't fix it with the
RX02.

Noel

Possibly, but I ran the same test on about 4 floppies and failed in the
same way. I bought a box of 13 floppy disks a while ago off eBay, so
unless the box was kept on top of a magnet or something, I'd expect at
least one of them to work.


On the contrary, I wouldn't expect ANY of your floppy disks to work.

Having been through getting an RX01 rejuvenated and working again, I had to 
fresh format some diskettes.

- J.

Re: RX02 Difficulties

[Aaron Jackson via cctalk]

> > From: Aaron Jackson
>
> > Most of the tests now look something like this:
> > ...
> >  SECTOR ADDRESS ERROR
> >   EXPECTED SECTOR=18.
> > TARGET SECTOR=17.
>
> I wonder if there's a problem with the floppy you are using?
>
> Remember, the RX0x drives can't hard reformat the floppies (as in, write the
> sector headers), so if the floopy has a problem, you can't fix it with the
> RX02.
>
>   Noel

Possibly, but I ran the same test on about 4 floppies and failed in the
same way. I bought a box of 13 floppy disks a while ago off eBay, so
unless the box was kept on top of a magnet or something, I'd expect at
least one of them to work.

Some of them have quite interesting names:

  Rutherford Appleton Laboratory Software

and

  Code from Neutron Divider

So I am quite interested to see what's on them.

Thanks,
Aaron.

Re: RX02 Difficulties

[Noel Chiappa via cctalk]

> From: Aaron Jackson

> Most of the tests now look something like this:
> ...
>  SECTOR ADDRESS ERROR
>   EXPECTED SECTOR=18.
> TARGET SECTOR=17.

I wonder if there's a problem with the floppy you are using?

Remember, the RX0x drives can't hard reformat the floppies (as in, write the
sector headers), so if the floopy has a problem, you can't fix it with the
RX02.

Noel

Re: RX02 Difficulties

[Aaron Jackson via cctalk]

> On Fri, Dec 8, 2017 at 3:03 PM, Aaron Jackson  wrote:
>>
>> Manual says it should be S1=off, S2=on for RX211 and RXV21
>
> In the photo, I think S1 is on and S2 is off. Check them with an
> ohmmeter if in doubt!
>
> -tony

Yes - you are right. I switched them back to how they were when I got
the drive. I think one of the switches was half down because XXDP
actually does something now.

Most of the tests now look something like this:

CZRXFB0 DVC FTL ERR  00034 ON UNIT 00 TST 031 SUB 000 PC: 003476
 SECTOR ADR - LGC TST
  SECTOR ADDRESS ERROR
   EXPECTED SECTOR=18.
 TARGET SECTOR=17.

I suppose these should match?

Starting to think I might need to confuse myself with my logic analyzer
and the RX02 control board.

Thanks,
Aaron.

Re: RX02 Difficulties

[allison via cctalk]

On 12/08/2017 09:45 AM, Aaron Jackson via cctalk wrote:
> Hi everyone,
>
> I originally posted this on VCFed (which was new to me) but the
> moderation queue has had me waiting for about 3 days, so I thought I'd
> ask here as well, the usual of gurus. :)
>
> I was recently sent an RXV21 controller so I could test out my RX02
> drive. When I power up the PDP-11 or reset the machine I get the nice
> clunking sound which I have been told is normal. I expect I wouldn't
> hear this if the ribbon cable was in the wrong way.
>
> To test, I tried to use VTserver to dump the contents of a disk, but it
> immediately threw an error. I soon realised there are two DIP switches
> on the logic board of the RX02 drive which had to be adjusted to work
> with the RXV21. So, I had some progress. Output of VTserver almost
> looked promising but then it hangs, as below:
>
> ]] Tape record n from device xx is written as xx(0,0,n)
> ]] Disk drive xx is written as xx(0,0,0)
> ]]
> ]] Enter name of input record/device: rx(0,0,0)
> ]] Enter name of output record/device: vt(0,0,1)
> ]]
> ]] Opened copy.out read-write
> ]]
>
> So, following some advice I booted via TU58em into XXDP and ran the
> diagnostics:
>
> ]] DR>STA
> ]]
> ]] CHANGE HW (L)  ? N
> ]]
> ]] CHANGE SW (L)  ? N
> ]]
> ]] CZRXFB0 SYS FTL ERR  00040 ON UNIT 00 TST 011 SUB 000 PC: 003476
> ]]  CSR BITS - LGC TST
> ]]   AC LOW FATAL ERROR
> ]]   REG ACTUAL=00
> ]]   REG EXPECT=00
> ]]
> ]]   POSSIBLE FAILING "FRU'S":
> ]] INTERFACE - M8029
> ]]
> ]]   UNIT#0 RXCSR=00 RXESR=00 CMD=00 ->
> ]]  ->NO PWR, CABLED BACKWARDS, STRAPPED RX01, PDP-8
> ]]  DROP UNIT#0 FROM TEST
> ]]
> ]] PASS ABRTD THS UNIT
> ]] CZRXFB0 SYS FTL ERR  00040 ON UNIT 01 TST 011 SUB 000 PC: 003476
> ]]  CSR BITS - LGC TST
> ]]   AC LOW FATAL ERROR
> ]]   REG ACTUAL=00
> ]]   REG EXPECT=00
> ]]
> ]]   POSSIBLE FAILING "FRU'S":
> ]] INTERFACE - M8029
> ]]
> ]]   UNIT#1 RXCSR=00 RXESR=00 CMD=00 ->
> ]]  ->NO PWR, CABLED BACKWARDS, STRAPPED RX01, PDP-8
> ]]  DROP UNIT#1 FROM TEST
> ]]
> ]] PASS ABRTD THS UNIT
> ]] CZRXFB0 EOP1
> ]] 2 TOTAL ERRS
>
> So, the possible errors according to XXDP:
>
> - Bad power - I get 25v, 5v and -5v. The motors are spinning, not
>   convinced it is this?
>
> - Cable backwards - I don't think I'd be hearing that clunk.
>
> - Strapped RX01 - I don't know what this means
>
> - PDP8 - eh?
>
> If anyone has any suggestions it would be great to hear them.
>
> Thanks,
> Aaron.

Why not do the obvious and flip the able at one end?  Its not like it
can hurt something.

FYI the two switches are for set for PDP-8 (12 bit) operation and the
other sets is for RX01
or RX02 mode.  RX01 mode locks the logic for RX01 operation only and the
RX02 mode
allows it to do both RX01 and RX02 media.

]]  ->NO PWR, CABLED BACKWARDS, STRAPPED RX01, PDP-8

That means check for:
 No power, drive has now power.
 Cable reversed
 set for RX01 or Set for PDP-8

Its a list of things that can be wrong to make it not work.

Allison

Re: RX02 Difficulties

[Tony Duell via cctalk]

On Fri, Dec 8, 2017 at 3:03 PM, Aaron Jackson  wrote:
>
> Manual says it should be S1=off, S2=on for RX211 and RXV21

In the photo, I think S1 is on and S2 is off. Check them with an
ohmmeter if in doubt!

-tony

Re: RX02 Difficulties

[Aaron Jackson via cctalk]

> On Fri, Dec 8, 2017 at 2:45 PM, Aaron Jackson via cctalk
>  wrote:
>
>> - Strapped RX01 - I don't know what this means
>>
>> - PDP8 - eh?
>
> No idea as to the fault (heck, it's not in front of me with a logic analyser
> to hand), but I think I can explain that.
>
> There is a pair of DIP switches on the controller board (the upper board
> in the RX02 itself, the one that hinges up). Three of the 4 settings are
> used : RX02 (which is the one you want, it is an RX02 drive to link
> to an RX211 or RXV21 interface), RX01 (turns the drive into a single-
> density-only RX01-a-like to link to an RX11 or RXV11) and 'PDP8' which
> is used to link to an RX8e for Omnibus PDP8 machines. The switch
> settings are in one of the manuals, you should check them.
>
> -tony

I think I have this set correctly, can be seen in this photo, unless I
misunderstand the colouring. Originally it was the other way around and
VTserver would throw an error instead of hang. I can try it again, with
the originally settings, under xxdp and see what happens.

http://aaronsplace.co.uk/private/pics/rx02insides/logic.jpg

Manual says it should be S1=off, S2=on for RX211 and RXV21

Re: RX02 Difficulties

[Tony Duell via cctalk]

On Fri, Dec 8, 2017 at 2:45 PM, Aaron Jackson via cctalk
 wrote:

> - Strapped RX01 - I don't know what this means
>
> - PDP8 - eh?

No idea as to the fault (heck, it's not in front of me with a logic analyser
to hand), but I think I can explain that.

There is a pair of DIP switches on the controller board (the upper board
in the RX02 itself, the one that hinges up). Three of the 4 settings are
used : RX02 (which is the one you want, it is an RX02 drive to link
to an RX211 or RXV21 interface), RX01 (turns the drive into a single-
density-only RX01-a-like to link to an RX11 or RXV11) and 'PDP8' which
is used to link to an RX8e for Omnibus PDP8 machines. The switch
settings are in one of the manuals, you should check them.

-tony

RX02 Difficulties

[Aaron Jackson via cctalk]

Hi everyone,

I originally posted this on VCFed (which was new to me) but the
moderation queue has had me waiting for about 3 days, so I thought I'd
ask here as well, the usual of gurus. :)

I was recently sent an RXV21 controller so I could test out my RX02
drive. When I power up the PDP-11 or reset the machine I get the nice
clunking sound which I have been told is normal. I expect I wouldn't
hear this if the ribbon cable was in the wrong way.

To test, I tried to use VTserver to dump the contents of a disk, but it
immediately threw an error. I soon realised there are two DIP switches
on the logic board of the RX02 drive which had to be adjusted to work
with the RXV21. So, I had some progress. Output of VTserver almost
looked promising but then it hangs, as below:

]] Tape record n from device xx is written as xx(0,0,n)
]] Disk drive xx is written as xx(0,0,0)
]]
]] Enter name of input record/device: rx(0,0,0)
]] Enter name of output record/device: vt(0,0,1)
]]
]] Opened copy.out read-write
]]

So, following some advice I booted via TU58em into XXDP and ran the
diagnostics:

]] DR>STA
]]
]] CHANGE HW (L)  ? N
]]
]] CHANGE SW (L)  ? N
]]
]] CZRXFB0 SYS FTL ERR  00040 ON UNIT 00 TST 011 SUB 000 PC: 003476
]]  CSR BITS - LGC TST
]]   AC LOW FATAL ERROR
]]   REG ACTUAL=00
]]   REG EXPECT=00
]]
]]   POSSIBLE FAILING "FRU'S":
]] INTERFACE - M8029
]]
]]   UNIT#0 RXCSR=00 RXESR=00 CMD=00 ->
]]  ->NO PWR, CABLED BACKWARDS, STRAPPED RX01, PDP-8
]]  DROP UNIT#0 FROM TEST
]]
]] PASS ABRTD THS UNIT
]] CZRXFB0 SYS FTL ERR  00040 ON UNIT 01 TST 011 SUB 000 PC: 003476
]]  CSR BITS - LGC TST
]]   AC LOW FATAL ERROR
]]   REG ACTUAL=00
]]   REG EXPECT=00
]]
]]   POSSIBLE FAILING "FRU'S":
]] INTERFACE - M8029
]]
]]   UNIT#1 RXCSR=00 RXESR=00 CMD=00 ->
]]  ->NO PWR, CABLED BACKWARDS, STRAPPED RX01, PDP-8
]]  DROP UNIT#1 FROM TEST
]]
]] PASS ABRTD THS UNIT
]] CZRXFB0 EOP1
]] 2 TOTAL ERRS

So, the possible errors according to XXDP:

- Bad power - I get 25v, 5v and -5v. The motors are spinning, not
  convinced it is this?

- Cable backwards - I don't think I'd be hearing that clunk.

- Strapped RX01 - I don't know what this means

- PDP8 - eh?

If anyone has any suggestions it would be great to hear them.

Thanks,
Aaron.

Tandy 1000 keyboard keys

[Alexandre Souza via cctalk]

Greetings from Brazil :)

Just got a Tandy 1000 SX. Nice shape, but it is missing the ESC and F10 
keys. Would someone have a complete assembly (switch + caps) to sell, 
shipping to Brazil incuided?


I'd also be interested in the monitor cable and one or two joysticks.

Thanks!
Alexandre
http://tabajara-labs.blogspot.com