test-drb

test-drb@ccmp.vtda.org

101090 discussions

by kylevowen＠gmail.com

I am noticing something odd in SimH when sending a 0377 (all ones) character. It seems to be duplicating the byte. I haven't read anything regarding this behavior. I'm away from my hardware PDP-8 at the moment, so I can't confirm that this is not the behavior that I would experience on the real thing. Here's how I reproduced it: test.pal: *200 CLA OSR JMS SEND JMP 200 SEND, 0 6416 6411 JMP .-1 CLA JMP I SEND $ pdp8.ini: at ttix 2222 set ttox0 8b load test.bin br 200 d sr 0377 Run 'nc localhost 2222 | od -to1' in a terminal, then 'go 200' and repeatedly press 'c', seeing how many times it takes to generate a line of characters in 'od'. Then, 'd sr 0376' and confirm that it takes twice as many presses, indicating half as many characters being sent per TLS instruction with the latter. Can anyone else confirm this for me? Thanks, Kyle

11 years, 6 months

SimH PDP-8 ttox device help

by kylevowen＠gmail.com

I've been attempting to interface with SimH in the least invasive way possible, by connecting two programs together via a pseudo-TTY created by socat connected to one of the telnet ports of a TTIX device. Something like this: TTIX -> telnet port -> socat -> /dev/ttyPDP (pty) This works fine for the console port. I personally like having minicom pulled up for the serial terminal but keep the other window cluttered with SimH backend commands. I have been able to manipulate EDIT.SV with a simple C program to transfer text files, character by character, which is neat. I wanted to extend this to a VC8-E emulator, again in the simplest way possible. I am sending out the X- and Y-coordinates for the point over TTOX0, but seem to be encountering some problems. I noticed that it likes to get hung up on a TSF (6411) instruction, causing it to keep looping even in single-step mode! Assuming everything is buffered, I would be under the assumption that TSF would almost always skip with a successful device send. [...] Step expired, PC: 00313 (IOT 411) \ a lot more of these (~50) Step expired, PC: 00314 (JMP 313) / Step expired, PC: 00313 (IOT 411) Step expired, PC: 00314 (JMP 313) Step expired, PC: 00313 (IOT 411) Step expired, PC: 00314 (JMP 313) Step expired, PC: 00313 (IOT 411) Step expired, PC: 00315 (IOT 416) <- finally skips! By the way, I am initializing the device with a CLA; TLS (6416) at the beginning of the program. I noticed David Gesswein opened up a somewhat related issue, now marked as closed, in October 2013. https://github.com/simh/simh/issues/85 Once I'm back to the real hardware, I intend to try it there to verify. I am running V3.9-0, by the way. Any insight into what might be holding TSF up would be much appreciated. Thanks, Kyle

11 years, 6 months

MEM11 Status Update

by jnc＠mercury.lcs.mit.edu

> From: Henk Gooijen > but RP11 will never be possible, isn't that MASSBUSS!? Maybe you're thinking of the RH70, the MASSBUS <-> PDP-11/70 memory bus interface? But there was also the RH11, a MASSBUS <-> UNIBUS interface, which supported all the same devices (RP04-6, etc) as the RH70, but plugged into a UNIBUS. (The two were programming-wise almost identical, the RH70 had an extra register for the extended memory address bits, plus a 'CSR3'.) But I was speaking of the RP11, a UNIBUS interface for the RP03 (different beast from the RH11, although very similar). Noel

11 years, 6 months

IMSAI PCS-80/15

by spereira1952＠comcast.net

Hello from a lurker here, I am looking for a pointer to where I might be able to obtain the assembly / reference / user manual for the IMSAI PCS-80/15. Printed form or electronic copy, either way will be fine with me. Thanks very much, in advance, for your attention, and, hopefully, positive response! smp - - - Stephen Pereira Bedford, NH 03110 KB1SXE

11 years, 6 months

Maxtor XT-2190

by djg＠pdp8online.com

Someone was using my MFM reader to read a Maxtor XT-2190 and was having problems. From the looks of it the heads are out of alignment. Does anyone know if this drive has a microstep mode like some Seagates have? I didn't find any mention in the manuals I could find. Some heads are mostly unreadable, some heads are mostly ok and some were unreadable on cylinder 0 and on other cylinders the header says they are one cylinder less than where it stepped to. Some of the other heads headers said the cylinder is what was expected.

11 years, 6 months

MEM11 Status Update

by jnc＠mercury.lcs.mit.edu

> From: Guy Sotomayor > a multi-function Unibus board that contains all of the more difficult > items to allow a PDP-11/20 to run Unix V1 entirely within the CPU > chassis. Other than the CPU and the RK11-D controller, everything else > will be on the MEM11 board. > ... > What's on the board is the following: > ... > RF11 controller with non-volatile memory emulating 8 RS11 drives What form is the NVM in - an SD card, or just a chip, or what? I assume it's flash memory of some kind? (What's the limit on the number of write cycles with current flash memory, I wonder...) BTW, a removable card would be great - that would provide a way to get bits into the machine, other than loading them all in over a serial line. I'm kind of curious about your decision to only have an RF11, given the capacity of contemporary flash memory chips/cards. Why not an RK11 too? (You may have plenty of RK controllers/drives, but some of the rest of us aren't so lucky... :-) Is there not enough room in the 16K code block to do that too? And how about an RP11 too, for those of us running these cards in later PDP-11's? :-) (Oh, speaking of the 16K limit - any way to increase the size? Probably not without munging the J1 architecture, I would guess - I need to go grab it and read it. But limited addresses spaces always turn out to bit you where it hurts... :-) > As I was competing the configuration UI, I found that I couldn't have > both the configuration UI and the emulation code both fit in 16K > (strings take up a lot of space). I seem to recall this problem from my days of writing packet switches for PDP-11's... :-) The code was famous for log messages that left out all the vowels, to save space.. :-) Please, make the UI as cryptic as needed to make all the features (e.g. more disk controllers :-) fit - documentation can explain what all the cryptic names are. (Or perhaps even a front-end running on a PC which is connected to the MEM11 over the serial line.) Don't take any of this to mean I don't think this is really, really neat, and very impressive - it's both! Needless (perhaps) to say, I'll be buying a stack of these when they are ready! :-) Noel

11 years, 6 months

Operating systems of the 1970s handling dates beyond the year 2000

by cubexyz＠gmail.com

After trying to get Unix v5 to understand dates beyond the year 2000 I had to wonder if any of the older operating systems from the 1970s or older could do this. So, did any operating system programmers from this time period have the foresight to use 4 digits for the year? I just checked APL/360 and it seems that it does not. Mark L

11 years, 6 months

MEM11 Status Update

by jnc＠mercury.lcs.mit.edu

> From: Jay West > My hope is to drop one of these boards in my 11/45. The only issue is > I'm afraid even though it will give the /45 maximum memory Well, there is that board (by Able?) that allowed a /45 to have up to 2MB of main memory. I know they exist[ed], we had one on our 11/45 at MIT 'BITD'. It didn't require any mods, it was a simple plugin - although my memory doesn't recall how the bus from the board to the memory worked, whether it used an over-the-back connector, or if the expansion board, and memory, plugged into a custom backplane (I have this vague memory that it could use Extended UNIBUS memory, a la 11/44, so maybe it was a custom backplane). I do recall that it had a whole separate set of mapping registers, to map the entire 'outbound' (from the CPU) UNIBUS to the larger memory, and also a UNIBUS map for the 'inbound' UNIBUS (from the devices) to map into the memory - i.e., it did not have access to the CPU mode/space signals, so it didn't have K/S/I PARs. One had to set up the mapping registers in the 11 as well. We used a static mapping where User I and D went to fixed chunks of address space in the 'outbound' UNIBUS, and the expansion MMU then mapped those chunks (variably) into the larger main memory. IIRC, we just changed the definition of the address of the User PAR registers (but kept the User PDRs), and the UNIBUS map registers (although maybe those were at the same locations as those in the 11/70), and then re-compiled the affected kernel modules. (The assembler startup required a bunch of changes, too.) I should have all that code on my backup tapes... That might not have supported I+D for K, S and I (since together they need 128KB*3 bytes, more than a complete UNIBUS address space), but it worked OK for the early Unix we were running. > I think I have too many pdp11 racks and it could be time to thin the > herd before too long. Or maybe I just need to get more space. Yah, > that's the ticket! Please put me on the list for an -11 stuff you get rid of... ;-) Noel

11 years, 6 months

Data Products 2230 manual?

by hachti＠hachti.de

Hi folks, my Data Products 2230 drum printer recently stopped working. The trouble began a few years ago: Startup went wrong from time to time so that the printer control logic was stuck after power on. Repowering helped. But now it does not help anymore. I found the DP2230 service manual 2 on bitsavers. It contains the machine's schematics. That already helped me to trace the problem - a bit. It looks like the buffer/interface logic does mad stuff. At this point it gets quite difficult to understand the logic without any explanation. Does anyone have the service manual part ONE? I assume that this contains info about state machines, test points and procedures, explanations etc. A (probably pdf) copy of that manual would help me a lot. I would very much appreciate to get hold of it. Kind regards Philipp :-)

11 years, 6 months

Shipping antique computers

by marc.verdiell＠gmail.com

Thank you Todd. Very useful info. Marc >From: Todd Goodman <tsg at bonedaddy.net> >Subject: Re: Shipping antique computers >Message-ID: <20150118203355.GG4901 at ns1.bonedaddy.net> >I've palletized and shipped computer stuff as well as pinball machines >as well as received both on pallets. >[...] >Just my experience with it. >Todd

11 years, 6 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

test-drb