test-drb April 2019

test-drb@ccmp.vtda.org

134 participants
129 discussions

by dennis.grevenstein＠gmail.com

Hi John, thank you for the idea. I finally managed to boot and install Ultrix 3.0. I prepared a new harddisk image under Ultrix 4.0. I could find /usr/sys/SAS.net/vmunix in the Ultrix 3.0 distribution tapes. This is a standalone kernel that will start the installation process. It can be booted like a normal kernel and can use the 3.0 tape images available from bitsavers. Dennis

6 years

H960 rack on eBay

by jnc＠mercury.lcs.mit.edu

H960 (rack only, really, although it looks like there are two NA11-N/S sheaths as well): https://www.ebay.com/itm/123729450695 Not a bad price; pick-up only though (just as well, considering how much it costs to ship the blasted things). Noel

6 years

NOS HP 7906 disk heads

by aek＠bitsavers.org

If someone needs top heads, this seems to be a decent price https://www.ebay.com/itm/303136246855

6 years

No subject

by couryhouse＠aol.com

Tom -? ?Thanks much for? ?filling in? some of the blanks on the history!? ?Ed# In a message dated 4/23/2019 2:36:37 PM US Mountain Standard Time, t.gardner at computer.org writes: ISS was an independent company in the era (late 60s) of the 714 (IBM 2314 compatible).? It was later acquired by Itel (a leasing company) and then by Univac and sort of disappeared in the 80s. Depending upon your application almost any plug compatible 2314 might work or could be made to work.? The interfaces were very much 2314 like except the PCMs and OEMs didn't use IBMs +/- 1.5v signaling levels on the interface but instead used DTL driver/receiver signaling.? There was also some weirdness in the power sequencing all of which can be worked around if u are up to it. Tom -----Original Message----- From: ED SHARPE [mailto:couryhouse at aol.com] Sent: Monday, April 22, 2019 11:37 AM To: cctalk at classiccmp.org; aek at bitsavers.org Subject: Re: Telex 20 Meg 10 platter very heavy monster drive needed drop line off list..r Thanks? Al? yes, that? is? the? one. and? as? I? recall? ISS? was a? offshoot? on? univac Do? you? have? any? Thanks Ed# In a message dated 4/22/2019 11:34:58 AM US Mountain Standard Time, cctalk at classiccmp.org writes: Thanks? Al? yes, that? is? the? one. and? as? I? recall? ISS? was a? offshoot? on? univac?In a message dated 4/22/2019 11:21:50 AM US Mountain Standard Time, cctalk at classiccmp.org writes: On 4/22/19 11:05 AM, ED SHARPE wrote:> Al,? the? drive? you mention at? its? largest? was? 7.5 meg? and? 6? platters... not? ? the? one Telex bought their drives from ISS.You're looking for a ISS 714 (ca. 1970) 2314 compat.https://ia800608.us.archive.org/15/items/TNM_Information_Storage_Sys… aek at bitsavers.org;cctalk

6 years

Elliott 5-level code: just in case you have some oddball 5-level paper tapes

by tshoppa＠wmata.com

Immensely happy this morning to have finally tracked this down. This is a 5-level code by Elliott used on many of their computers. It seems to have used standard looking 5-level teletype I/O devices but with custom typewheel and keyboard/function bar encoding. It has 3 things in common with other 5-level codes: 1: Letter shift and Number/Figure shift 2: Null is all zeroes 3: Letter shift is all ones and also works as delete just like the other codes But some interesting properties, different than other 5 level codes: 1: Letter shift has the letters in alphabetic A-Z sequence. 2: In number shift, the lower 4 bits are the digit 0-9, and the upper bit is a parity 3: Figure shift, space, carriage return, and line feed are at the extreme top end of the code space right under letter shift. The code is documented in Figure B.2 of this wonderful document: http://rabbit.eng.miami.edu/oldcomputers/Elliott-400-series.pdf I'm a little surprised that my standard character code references don't mention this. This is a super elegant layout that any of the 1960's character code standard guys must've known about, but somehow it never made it into any of my usual reference books. Maybe MacKenzie was just too dismissive of all 5-bit codes. He mentions ITA2 for a couple pages and then never talks about 5-level codes again, but he never stops talking about BCDIC and he goes on and on about hypothetical 12-row punchcard ASCII. Tim N3QE

6 years

Televideo 925 character rom dump

by guykd＠optusnet.com.au

When I saw this thread I thought 'Oh, I have a 925!' Which was working last time (years ago.) But wouldn't you know. When I checked, it's a Televideo 924. Off by one. But perhaps the character ROM content is the same? Anyway I will see if it still works, and secure all the ROM images. Today. I have the user manuals, but does anyone have schematics for the 925 & 924? Guy At 09:38 AM 23/04/2019 -0700, you wrote: >On Tue, Apr 23, 2019 at 8:25 AM Patrick Finnegan <pat at vax11.net> wrote: > >> On Tue, Apr 23, 2019 at 11:02 AM Jon Elson via cctalk < >> cctalk at classiccmp.org> wrote: >> >>> Is the ROM totally bad, or just losing a few bits here and >>> there? If the latter, you could probably read it out, figure >>> out how the rows, columns and characters are mapped, and fix it. >>> >> >> Considering that 925s are really common, and a replacement EPROM should be >> easy to source and program, this sounds like an overly difficult approach >> that will yield something different than what he wants. >> > >The thought had crossed my mind, but only as a last resort. I'm not >entirely sure what the internal fault is, but the end result is two rows of >every character have all bits stuck "on." I've verified that the ROM >addressing is correct and that there's nothing on the output side causing >this behavior. Patrick, thanks very much for offering to read the ROM! > >- Josh > > > >> Pat >> >

6 years

TSX-Plus help needed!

by charlesmorris800＠centurytel.net

OK, I have figured out how to modify TSGEN.MAC, use PUTR to make a disk image, load it in SIMH, reassemble, relink, and *finally* send it to an RL02 pack via vtserver! TIme-consuming but doable. I've been wrestling with this all day. BUT - TSX+ 6.50 just will not run. At all. Using RT-11SJ (5.01), after typing "R TSX" I can hear the disc access for a few seconds, a pause, a few more accesses... then nothing. It just hangs. Nothing on the console either., no response to <CR>. When starting it in SIMH (the same disk image), I get the error message ?TSX-F-Computer line clock is not working. Figured that was just a SIMH thing. But the address/vector is correct in TSGEN.MAC... and when checking TIME in RT-11, the seconds advance in real-time like it should. On the real hardware, the error message doesn't display, and the clock is running... My old version of TSX+ is 6.16 and it runs fine on console and SLU 2, just needs rebuilt to use different serial cards than the original system. So where should I start looking first? RT-11 version incompatibility? Any TSX+ experts online? Thanks for any help. This is driving me nuts!

6 years

VTserver problem (bug?)

by charlesmorris800＠centurytel.net

And even more bizarrely... it crawled its way up to the 7400K block, and now it's going at normal speed again! 10MB should be done soon. I have no idea what could be causing this major slowdown from 6.6-7.4 MB. It's not the drive because two different ones do the same thing (and they work perfectly otherwise)... Hopefully I won't have to go through the (edit, reassemble, relink, PUTR transfer to an image, vtserver to the disk) loop too many times, attempting to get my DHV11/16D to function with TSX+ 6.50... I had somehow inserted a couple of characters that didn't belong there while editing (bumped the keyboard maybe?) so I'm on the second pass. Also I found what looks like a typo in the TSGEN.MAC file if anyone's interested.

6 years

VTserver problem (bug?)

by charlesmorris800＠centurytel.net

-----Original Message----- >But there is some kind of bug that always appears at the same point, in the >middle of the next 100K block after "6600K written". >The data transfer stops (no more head motion/ready light flicker on the >RL02), and the character that vtserver uses to indicate a write operation >just repeats endlessly and rapidly until I kill it. More information and a correction: I let it run on, and it is still reading and writing, but at a much slower and intermittent rate than the first 6.6 MB. The filler character is just a time marker of some kind, since I can still see the "r" indicating a read from the .dsk image, and the light on the RL02 flickers after a few of those. So it's slowed way down, but not stopped! Even more mysterious. Anyway, this disk has 13800 blocks out of 20800 used. If RT-11 stores data (including the directory structure) starting from block 0, I may be able to kill the writes after 7 MB. (Unfortunately I think I neglected to squeeze the image before sending it to the RL - and naturally the important TSX files are near the end - which means I have to wait for most of it). If I have to do it again, I'll squeeze and then kill it after 7 MB and see what I got!

6 years

(no subject)

by charlesmorris800＠centurytel.net

>But there is some kind of bug that always appears at the same point, in the >middle of the next 100K block after "6600K written". >The data transfer stops (no more head motion/ready light flicker on the >RL02), and the character that vtserver uses to indicate a write operation >just repeats endlessly and rapidly until I kill it. More information and a correction: I let it run on, and it is still reading and writing, but at a much slower and intermittent rate than the first 6.6 MB. The filler character is just a time marker of some kind, since I can still see the "r" indicating a read from the .dsk image, and the light on the RL02 flickers after a few of those. So it's slowed way down, but not stopped! Even more mysterious. Anyway, this disk has 13800 blocks out of 20800 used. If RT-11 stores data (including the directory structure) starting from block 0, I may be able to kill the writes after 7 MB. (Unfortunately I think I neglected to squeeze the image before sending it to the RL - and naturally the important TSX files are near the end - which means I have to wait for most of it). If I have to do it again, I'll squeeze and then kill it after 7 MB and see what I got!

6 years

← Newer
1
2
3
4
5
6
7
...
13
Older →

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 April 2019