test-drb January 2017

test-drb@ccmp.vtda.org

198 participants
283 discussions

I finall flashed my XTIDE rev 1, now what?

by rdawson16＠hotmail.com

Yippie! But what a long haul it was. Just getting the data on a disk that I could read was a nightmare. I bought a USB 3.5 floppy drive (Sabrent SBT-UFDB, $19 at Frys), and it does not write 720K reliably. Comments on the net say it does not work, under windows 7 lots of errors, but bringing up in Linux (Fedora) it sort of does work. Remember to unmount so that it flushes the data out to the floppy! After several back and forth tries with abort, retry, fail errors, I finally got xtidecfg to run on the target (Compaq model 1, the luggable XT). Next, I could not flash the EEPROM. Turns out I had one 74F573 in upside down. $100 Digikey overnight later, I got one (several, I spared all the parts and the EEPROM just in case). OK now XTIDE comes up on boot, and responds with the timeout screen and lets me select the floppy for the boot. I have a Compact Flash adapter and card, while I wait for the soldering iron to heat up and make the power cable for it, I wanted to ask, what are the next steps? FORMAT, or FDISK /MBR? What is the recommended way to initialize the CF flash and put a system on it? Anything special to do, so that I can use the whole 2GB of the flash? Thanks to anyone who has been there and done this... Randy

7 years, 10 months

Looking to read past EOT on DDS/DLT/LTO

by sieler＠allegro.com

Hi, Maciej mentioned "winding a tape past a medium error and read...". I have several times successfully skipped past media errors on DDS-1 drives by doing a FSF (Forward Skip File ... tells drive to skip to the next EOF). (Although, IIRC, once I encountered a read error, I couldn't do that ... I recall having to 'sneak up' on the error by positioning the drive to the prior EOF and then skipping forward. But since I haven't done it for more than 10 year, maybe my memories are classic, er, rusty.) My recollection is that DDS-1 (and perhaps -2?) had 'set marks' that few people knew about, and even fewer ever used. The explanation I recall is that the drive could do a "forward to next setmark" *much* faster than "forward to next EOF". (BTW, when reading, a setmark was reported like an EOF (although if you requested extra status you could tell them apart).) I never tried using the skip-to-next-setmark to get past errors, partially because the tapes I was recovering years ago didn't have setmarks. (Set marks are one reason I prefer my tape archiving format, since I record them, as well as retry information :) Al: thanks for expanding my answer about cutting out a portion of the tape ... I'd forgotten about helical recording. (Note that on ordinary multi-track tapes, cutting a section does indeed lose data from n different places on the tape ... any tape that requires multiple passes over the tape to get from BOT to the full capacity of the tape.) Stan

7 years, 10 months

Service Manual Direct 831, Direct 825 or Basic Four S/10

by ad＠ardiehl.de

finally got one of the Basic Four S10. Does someone have a service manual for these or the Direct Inc. models ? The one i got was a little bit damaged due to shipping within Europe. Found at least one transistor and one cap that broke off the video monitor board. Will try to fix that next week. The Basic Four S/10 was developed and build by Direct Inc, Santa Clara, California. They sold the machine as a serial terminal (Dec/HP) as well as a terminal in combination with a CP/M 2 board. Direct 825 with CP/M: http://basicfour.de/pics/s10/Direct_825.jpg Direct 831 as a terminal without the second cpu/floppy controller board: http://basicfour.de/pics/s10/s-l500.jpg and the basic four s/10: http://www.obsoletecomputermuseum.org/mai/ Btw, I'm also looking for MAI Basic Four Software for the Models 2000, 210/510/730 Thx machine with floppy and terminal boards: http://basicfour.de/pics/s10/3.jpg --------------------- Armin Diehl ad at ardiehl.de

7 years, 10 months

General Electric EF-140

by bill.gunshannon＠hotmail.com

I hope this is considered apporopriate for this list, if not, I am sure y'all will let me know. :-) And, yes, it is about a truly classic computer. I am trying to restore my 1961 General Electric EF-140 Analog Computer. The insulation on all of the wires has basicly turned to stick goo. I would really like to rebuild it. Does anyone have or know where I might find a wiring diagram for this box? I got it thru National Technical Schools when I was about 11 years old and sadly, while it survived, my mother threw out all of the courses and manuals that came with the correspondence course I took back then. If someone has it but it's buried away, no problem. I just loaned it for a static display at the University where I used to work in the CS Department. I expect they will want to keep it for at least the Semester. On another note, it's good to be back on the list after many years away. I still have and use a number of systems that people here would consider more in line with their notions of Classic Computers. Some of you may even remember me. I was and still am big on PDP-11's and VAX. But I also have a number of old Micros as well (and some of the newer ones that try to bring the old flavor back like the Maximite and The P112.) bill

7 years, 10 months

ISO: Documentation for a Northern Scientific NS-600

by derschjo＠gmail.com

Hi all -- Went spelunking in a hoarder's basement this morning (long story) and came out with a few interesting items, including a Northern Scientific NS-600. >From what I can tell it's from the late 60s and is capable of storing and analyzing digital data (and can display it on a tiny scope display). There isn't any real documentation out there, just a few research papers here and there noting its use in various experiments. Anyone have anything on this? Thanks, Josh

7 years, 10 months

Anyone have the service guide for a Sanyo VM4209 monitor?

by AppleCorey＠optonline.net

I need the schematics. I'm not sure I trust all those "manual" sites on the web that want to sell you a PDF for $15. My monitor seems to be acting up. Thanks in advance, Cheers, Corey corey cohen u??o? ???o?

7 years, 10 months

Looking to read past EOT on DDS/DLT/LTO

by sieler＠allegro.com

Hi, We have a friend with a "tape" (DDS, DLT, or LTO ... don't know which yet) to which was written a system backup. Thousands of files, with an EOF between each file, and a double EOF + EOT at the end. The problem: They then accidentally overwrote the start of the tape yesterday with about 1 KB of data, plus EOT. (By EOT I mean the "logical end-of-tape" indicator placed there by the drive firmware when a tape is rewound / unloaded after it's been written to.) So, we want to try to recover the files after that 1 KB + EOT. On reel tape, no problem. I'd read until I hit the double EOF, and then skip the partial file (by looking for the next EOF), and then...gravy. But, DDS/DLT/LTO drives won't let me get past that darn logical end-of-tape. Are there solutions anyone can suggest? I've only heard of two approaches: 1. find a drive with modified firmware, one that treats an EOT like an EOF While I heard some existed for DDS-1 drives, that lead was 20 years old :) 2. insert tape, start writing (at the start), write until I'm sure I've written over the area where the EOT was, power cycle the drive read from the start, skipping over the data I just wrote, handle the possible corrupted record, and the I've got good data from past the EOT (note that this method loses a small amount of old data past the EOT that we overwrote). On DDS drives, I used this technique once or twice successfully, although I seem to recall I couldn't do the "read until I get to the good stuff" because of the probability of a bad record on the tape (where the power fail was) ... but the solution was to load the tape and then say "skip forward 3 EOFs", and the skip-to-EOF would quietly ignore (usually) any bad record before the EOF. BTW, if this is DDS, it's unlikely to be newer than DDS-4 (but possible), if it's DLT, it's likely one of the first two or three generations, and if it's LTO, it's extremely unlikely to be anything other than LTO-1. thanks, Stan

7 years, 10 months

IBM 7074 and then some: "Systems we love" conference

by steve.maresca＠gmail.com

Just wanted to share an excerpted story just sent to me by a colleague, regarding an IBM 7074 supplying data to Java middleware, ultimately feeding a modern webapp stack: http://thenewstack.io/happens-use-java-1960-ibm-mainframe/ This comes from a conference which occurred last month titled "Systems we love" : http://thenewstack.io/systems-we-love/ http://systemswe.love/ Cheers, Steve

7 years, 10 months

Fourth release of the HP 3000 Series III simulator

by jdbryan＠acm.org

The fourth release of the HP 3000 Series III simulator is now available >from the Computer History Simulation Project (SIMH) site: https://github.com/simh/simh This release adds the HP 32234A COBOL II Extended Instruction Set firmware, enabling execution of programs produced by the COBOL II ('74 and '85) compilers. The new SET CPU CIS option enables the firmware. In addition, two new debug tracing options were added. The SET CPU DEBUG=OPND command turns on memory byte operand tracing to show the values supplied, e.g., to the CMPS (Compare String) instruction. The SET CPU DEBUG=EXEC command turns on execution tracing for a specific instruction or instruction family. The full set of new features is listed in the release notes that accompany the simulator source files. In addition, an updated HP 3000 Simulator User's Guide that covers the new commands is provided in Microsoft Word format with the source download and also as a PDF file at: http://alum.mit.edu/www/jdbryan/hp3000_doc.pdf The preconfigured MPE-V/R disc image available here: http://simh.trailing-edge.com/kits/mpe-vr-software-kit.zip ...has been updated to add the COBOL II runtime routines to the system Segmented Library and COBOL example programs to the OPERATOR.SYS account. The startup command files also now enable the COBOL II instruction set. -- Dave Bryan

7 years, 10 months

DECUS TECO for OS/8

by chd＠chdickman.com

I am trying to build the DECUS TECO with VT support for OS/8. TECO came from ibiblio and the assembler listing says it is OS/8 TECO VERSION 7. I am using MACREL-V1B. It all assembles without error, but the linker fails with a NO ROOM message. I can't find any information on what NO ROOM means from the MACREL documentation. This is using SIMH PDP8 with 32k words. I also found MACREL V2 source, but it in in MACREL, but I have not tried to bootstrap it using V1. I was hoping to make source editing just a little bit easier. -chuck

7 years, 10 months

← Newer
1
2
3
4
5
6
7
8
9
...
29
Older →

Jump to page:

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 January 2017