test-drb

test-drb@ccmp.vtda.org

101090 discussions

by healyzh＠aracnet.com

I just finished posting the following to, alt.sys.pdp10, and I figure some others here might be interested in the instructions on how setup the emulator. Note, at this time ts10 works best under Linux. Work is being done to get it working on other UNIX varients, but at this time Linux is your best bet. The following is a *Rough Draft*, but it should be enought to get a system setup. Zane Installation of TOPS-10 v7.03 I'm guessing this might be of use to some people, and it can serve as a starting point to a better document. I'm sure it's in need of corrections, as I've doubts as to wether or not the system is coming up right. The following procedure is mainly based on stuff Greg Satz, Parag Patel, and Timothy Stark have posted. I'd figured out a lot of this, but this looks a lot better than what I'd done :^) Based on Mark Hittinger's comments about the RIB errors which I'd noticed in my first install, I've used 1990 as the year in the following and it seems to have not had any problem. I believe others have done this giving the correct date without any problem though. STEP 1. First get the following tapes from http://pdp-10.trailing-edge.com > BB-X138B-BB KS Bootable TOPS-10 v7.03 tape > BB-X140B-SB TOPS-10 v7.03 Monitor sources > BB-X128B-SB TOPS-10 v7.03 w/sources #1 > BB-FP63A-SB TOPS-10 v7.03 w/sources #2 > BB-FP64A-SB TOPS-10 v7.03 Tools w/sources > BB-X130B-SB CUSP w/sources You can also get the sources for the ts10 emulator here. STEP 2. Apply the following patch. diff -c -r1.1 system.c *** pdp10/system.c 2001/02/27 14:17:06 1.1 --- pdp10/system.c 2001/03/11 22:01:50 *************** *** 120,126 **** } text7[p] = 0; ! sprintf(text, "%012Lo ('%s' '%s')", data, text6, text7); return text; } --- 120,126 ---- } text7[p] = 0; ! sprintf(text, "%012qo ('%s' '%s')", data, text6, text7); return text; } *************** *** 348,355 **** // int reqBoot = FE_P0_MONITOR_PREBOOT; // int reqBoot = FE_P0_DIAGNOSTIC_PREBOOT; // int reqBoot = FE_P0_BOOTCHECK2_PREBOOT; ! uint8 inBuffer[0777 * 5]; ! int36 inBlock[0777]; int36 idHom = util_PackedASCII6("HOM"); int36 dAddr36; int36 data36; --- 348,355 ---- // int reqBoot = FE_P0_MONITOR_PREBOOT; // int reqBoot = FE_P0_DIAGNOSTIC_PREBOOT; // int reqBoot = FE_P0_BOOTCHECK2_PREBOOT; ! uint8 inBuffer[01000 * 5]; ! int36 inBlock[01000]; int36 idHom = util_PackedASCII6("HOM"); int36 dAddr36; int36 data36; STEP 3. Startup the emulator. [healyzh@ts10 ts10]$ ./ks10 -f ks10.cfg Welcome to TS10 Emulator v0.7 (Alpha) Unit uba: had been created. Addr=776700 Mask=000077 IntBR=6 IntVec=254 Addr=772440 Mask=000037 IntBR=6 IntVec=224 Device RPA0: had been created. Device RPA1: had been created. Device MTA: had been created. Device MTA0: had been created. Device MTA1: had been created. Device MTB: had been created. Device MTB0: had been created. Device MTB1: had been created. Unit rha0 had been initialized. Unit rpa0 had been initialized. Unit rha1 had been initialized. Unit mta had been initialized. Unit mtb had been initialized. Unit 0 dType RP06 Unit rpa0 had been attached with 'tops10_703.dsk' file. Unit 0 dType TU45 Unit mta0 had been attached with 'tops10_703_ksbootable_bb-x138b-bb.tap' file. TS10> boot mta0: Booting MTA0... Now running... BOOTM V6(37) BTM>/tm02 KS10 03-19-86 Why reload: new Date: 11-mar-90 Time: 11:00 Startup option: destroy % WARNING: All structures will be refreshed. All disk files will be destroyed. All information on currently spinning packs will be lost. Do not proceed unless you are positive that you want to do this. Proceed? (Y or <CR>)y HOME blocks written on all units RPA0 first BAT block consistency error RPA0 second BAT block consistency error Both BAT blocks are bad. Do you want to initialize the BAT blocks on this unit? y Not normally done, are you sure? y Initializing BAT blocks Start system? (Y or <CR>)y Disk file structures: DSKB:RPA0(ONC403) To automatically log-in under [1,2] type "LOGIN" KS10 11:00:10 . LOGIN .ASSIGN MTA0: TAPE: MTA000 assigned .GET TAPE:BACKUP Job setup .SAVE BACKUP BACKUP saved .RUN BACKUP /TAPE TAPE: /SUPERSEDE ALWAYS /INTERCHANGE /FILES /RESTORE SYS:=*.* ! SYSTEM EXE "Done /RESTORE DEC:=*.* ! SMFILE EXE SMFILE HLP SMFILE TXT T10KL ULD KSBOOT EXE BOOTM RDI T10KL RAM "Done /EXIT [^E pressed] .TS10> attach mta0: cuspmar86binsrc_1of2_bb-x128b-sb.tap Unit 0 dType TU45 Unit mta0 had been attached with 'cuspmar86binsrc_1of2_bb-x128b-sb.tap' file. TS10> continue Running now... .RUN BACKUP /TAPE TAPE: /INTERCHANGE /SUPERSEDE ALWAYS /PROTECTION 055 /FILES /RESTORE DSKB: [a lot of filenames print out] $BKPEOT Reached EOT--mount new tape then type "GO" [^E Pressed] /TS10> attach mta0: cuspmar86binsrc_2of2_bb-fp63a-sb.tap Unit 0 dType TU45 Unit mta0 had been attached with 'cuspmar86binsrc_2of2_bb-fp63a-sb.tap' file. TS10> continue Running now... GO [a lot more filenames print out] "Done [^E pressed] .TS10> attach mta0: cuspmar86binsrc_1of2_bb-x128b-sb.tap Unit 0 dType TU45 Unit mta0 had been attached with 'cuspmar86binsrc_1of2_bb-x128b-sb.tap' file. TS10> continue .RUN BACKUP /TAPE TAPE: /INTERCHANGE /SUPERSEDE ALWAYS /PROTECTION 055 /FILES /@dskb:[10,7,build]cusps.rst [You'll need to change to the second tape when it wants you to. When this is done, make the disk bootable.] .RUN DEC:SMFILE DECSYSTEM 2020 DIAGNOSTICS FE-FILE PROGRAM VERSION 2.5, TOPS-10, KS10, CPU#=5000 [FOR HELP TYPE "HELP"] SMFILE>WRITE SETUP DSKB:[1,5\5\4] SMFILE>WRITE RESET SMFILE>READ DEC:T10KL.ULD SMFILE>WRITE CRAM SMFILE>WRITE BOOT DEC:KSBOOT.EXE SMFILE>WRITE DONE SMFILE>EXIT EXIT .R CREDIR Create directory: ACT: [^E pressed] TS10> quit STEP 4. Now you should be ready to startup your system from disk. [healyzh@ts10 ts10]$ ./ks10 -f ks10.cfg Welcome to TS10 Emulator v0.7 (Alpha) Unit uba: had been created. Addr=776700 Mask=000077 IntBR=6 IntVec=254 Addr=772440 Mask=000037 IntBR=6 IntVec=224 Device RPA0: had been created. Device RPA1: had been created. Device MTA: had been created. Device MTA0: had been created. Device MTA1: had been created. Device MTB: had been created. Device MTB0: had been created. Device MTB1: had been created. Unit rha0 had been initialized. Unit rpa0 had been initialized. Unit rha1 had been initialized. Unit mta had been initialized. Unit mtb had been initialized. Unit 0 dType RP06 Unit rpa0 had been attached with 'tops10_703.dsk' file. Unit 0 dType TU45 Unit mta0 had been attached with 'tops10_703_ksbootable_bb-x138b-bb.tap' file. TS10> boot rpa0: Booting RPA0... [Reading first HOM block...] [Reading FE-FILE Page 0 at C 213 T 11 S 1] [Reading Monitor Pre-boot at C 213 T 13 S 13] Now running... BOOT V3(47) BOOT> [Loading from DSKB:SYSTEM.EXE[1,4]] KS10 03-19-86 Why reload: sched Date: 11-mar-90 Time: 19:36 Startup option: go [Rebuilding the system search list from the HOMe blocks] [Rebuilding the active swapping list from the HOMe blocks] [Rebuilding the system dump list from the HOMe blocks] KS10 19:36:01 CTY system 5000 Connected to Node (0) Line # 42 .LOGIN 1,2 .R OPSER [OPRPAF Processing auto command file] ?OPRALF LOOKUP failure 0 * [CCPWFD Waiting for file daemon to start] %%TTY STOMPER - Starting *^C .R LOGOUT [LGTOUL Other users logged-in under [1,2]] Job 2 User OPSER [1,2] Logged-off CTY at 19:36:42 on 11-Mar-90 Runtime: 0:00:01, KCS:10, Connect time: 0:00:41 Disk Reads:126, Writes:0, Blocks saved:0 .LOGIN 1,2 Job 2 KS10 CTY [LGNJSP Other jobs same PPN] [LGNLAS Last access to [1,2] succeeded on 4-Mar-86:17:48:53] 19:36 11-Mar-90 Sunday . SYSTAT Status of KS10 at 19:49:53 on 11-Mar-90 Uptime 13:52, 117% Null time = 117% Idle + 0% Lost, 0% Overhead 12 Jobs in use out of 35. 12 logged in, 10 detached. Job Who Line# What Size(P) State Run Time 1 [OPR] DET41 STOMPR 7+8 SL 1 01 2 [OPR] CTY SYSTAT 21+SPY RN 1 4 [OPR] DET41 ACTDAE 180+39 SL 4 5 [OPR] DET41 DAEMON 20+SPY SL 1 6 [OPR] DET41 FILDAE 17 HB 0 7 [OPR] DET41 QUASAR 108+39 SL 2 8 [OPR] DET41 PULSAR 65+39 HB 1 9 [OPR] DET41 CATLOG 30+39 HB 1 10 [OPR] DET41 ORION 96+39 SL 2 11 [OPR] 41 4 ^C 0 17 [OPR] DET41 BATCON 38+39 SL 1 29 [OPR] DET41 LPTSPL 58+39 HB 1 n means job runs in HPQ n High Segments: Program Device Owner High(P) Users INITIA DSKB [SYS] 8 1 GLXLIB DSKB [SYS] 39 7 Swapping space used = 655/2000 = 33% Virt. Core used = 691/2000 = 35% 84P Core left Active swapping ratio = 21/775 = .02 Virt. Core saved by sharing = 234/(234+691) = 25% Average job size =644/12 = 53.6P+281/12 = 23.4P Total=925/12 = 77.0P No busy devices System File Structures: Name Free Mount DSKB 213910 2 Total Free 213910 . -- | Zane H. Healy | UNIX Systems Administrator | | healyzh(a)aracnet.com (primary) | OpenVMS Enthusiast | | healyzh(a)holonet.net (alternate) | Classic Computer Collector | +----------------------------------+----------------------------+ | Empire of the Petal Throne and Traveller Role Playing, | | and Zane's Computer Museum. | | http://www.aracnet.com/~healyzh/ |

24 years, 1 month

Found a Commodore SX-64 but with a strange problem.

by spectre＠stockholm.ptloma.edu

> This was one of the few missing things in my CBM collection until yesterday. > The system first appeared dead, showing just a blank screen. But then it > worked fine with any of my assorted game cartridges in the cartridge slot. > To test the disk drive, I pulled out a cartridge-based spreadsheet which had > load and save commands and the disk drive worked OK. > > The big surprise was when I put in the Simons Basic cartridge and this heavy > old "portable" C64 came up with its normal opening screen "SX-64 Basic" etc > and it loaded and ran a variety of programs from disk without a problem. But > without a cartridge, or with a C64 Super Expander cartridge, just a blank > screen. Differential diagnosis of a blank screen on a Commodore (I'm a med student :-) ------------------------------------------------------------------------------ If the screen is *black* your first suspects, in order, are the PLA and then the VIC-II. Also, as always, check the fuse. I'm guessing that the blank screen you get is a *white* screen and possibly a cyan border? If cartridges work, as they do in yours, the problem is clearly one of the ROMs. Since the disk drive is operational my first guess is the BASIC ROM, which is fortunate for you because the Kernal ROM is unique to the SX :-) I don't remember the number on it, though, but the SX Kernal should be labelled 251104 with possibly a revision number (-04?). DON'T swap that one out. The BASIC ROM is probably labelled 901226 but that's in the breadbox systems. You can take that from any regular C64, and it should work fine. If both ROMs are shot, all is not lost if you have an EPROM burner -- see this wonderful archive: http://www.funet.fi/pub/cbm/firmware/computers/c64/index.html Just my $0.02! (You adjust for AUS$.) -- ----------------------------- personal page: http://www.armory.com/~spectre/ -- Cameron Kaiser, Point Loma Nazarene University * ckaiser(a)stockholm.ptloma.edu -- Mickey Mouse wears a Spiro Agnew watch. ------------------------------------

24 years, 1 month

Found a Commodore SX-64 but with a strange problem.

by rhblake＠bigfoot.com

Hmmm it doesn't sound normal. The SX model usually has problems with the keyboard cable for the most part. -----Original Message----- From: owner-classiccmp(a)classiccmp.org [mailto:owner-classiccmp@classiccmp.org]On Behalf Of Phil Guerney Sent: Tuesday, March 11, 2025 5:01 AM To: classiccmp(a)classiccmp.org Subject: Found a Commodore SX-64 but with a strange problem. OK - So it might not be strange to those experts in Commodore hardware, so I hope one of them reads this! This was one of the few missing things in my CBM collection until yesterday. The system first appeared dead, showing just a blank screen. But then it worked fine with any of my assorted game cartridges in the cartridge slot.

24 years, 1 month

Found a Commodore SX-64 but with a strange problem.

by claudew＠videotron.ca

Hi Lucky guy a SX64,,,but it depends how much you paid...I was offered one for $500CAN not too long ago....sure I am crazy... I would check all chips on the boards and push on all of the socketed ones...specially the ROMs.... By the way, I have been told that 5000 of these SX64 were made...does that sound right or can someone confirm this? Claude ----- Original Message ----- From: Phil Guerney <guerney(a)bigpond.com> To: <classiccmp(a)classiccmp.org> Sent: Tuesday, March 11, 2025 6:00 AM Subject: Found a Commodore SX-64 but with a strange problem. > OK - So it might not be strange to those experts in Commodore hardware, so > I hope one of them reads this! > > This was one of the few missing things in my CBM collection until yesterday. > The system first appeared dead, showing just a blank screen. But then it > worked fine with any of my assorted game cartridges in the cartridge slot. > To test the disk drive, I pulled out a cartridge-based spreadsheet which had > load and save commands and the disk drive worked OK. > > The big surprise was when I put in the Simons Basic cartridge and this heavy > old "portable" C64 came up with its normal opening screen "SX-64 Basic" etc > and it loaded and ran a variety of programs from disk without a problem. But > without a cartridge, or with a C64 Super Expander cartridge, just a blank > screen. > > Could it be a RAM chip that is faulty, with Simons Basic causing some > relocation of memory that allowed the system to work? Unfortunately, the > insides are not nearly as easy to get at compared to a standard C64. > > Thanks in advance for any suggestions. > Phil > (Brisbane, Australia) > >

24 years, 1 month

SCSI connectivity

by ajp166＠bellatlantic.net

From: Chad Fernandez <fernande(a)internet1.net> > >EISA won't go into an ISA system, either. Yes, but most ISA-8 or and ISA-16 cards do fit EISA and VESA bus machines as they generally provide ISA. I know that as I have a boat load of antiques at work still running. >I don't think any wide scsi >ISA cards exist. Ebay, again, is the best source for an EISA scsi card. Most wide SCSI drives work just fine with narrow. It's not as if the machine is likely to be fast enough to really use wide SCSI performance. I generally use a ISA card from ADAPTEC as I have a 1542 and a 2906 (PCI) handy. That works in everything but the XT class boxen and MCA. Allison

24 years, 1 month

new additions: IBM S36, kaypro and more

by SUPRDAVE＠aol.com

it's been quite some time since Ive picked up anything new. I've reached critical mass and have had to pass by on machines which I already own except for IBM PS/2s which I salvage for adaptor cards. anyway, just this past week, I beat out several others and responded to an email about a free kaypro 10. Its in great shape and will get the disks for it later hopefully. also got an amstrad PC20 with second floppy drive and the special mouse, two mac quadra 630 and just today got an IBM 5364 which is a S/36 PC complete with the display unit and funky cables. didnt get the keyboard though. Anyone have a keyboard for an IBM 3196? Later, I discovered I left behind the host IBM PC 5150 that was there too so i returned for that. It even has the S36 boot floppy still in the drive with dust on it. Can't do an IPL though, probably because the S36 keyboard is missing. Not much info can be found on the 5364, but will make a good addition to my IBM PC RT 6150. DB Young Team OS/2 antique computer collection, hot rod pinto, and more at: http://www.nothingtodo.org

24 years, 1 month

SCSI connectivity

by ajp166＠bellatlantic.net

From: Chad Fernandez <fernande(a)internet1.net> > >What is DRivX? Is that a Linux program or is it Windows or DOS? Somthing I fond on a bbs about 9 years ago. Runs under dos but doesnt actually use dos IO. >Well yes, I know it won't be fast, but this is for an XT class system >:-) Expect less. ;) > >Cool, I get board with a perfectly working computer with nothing for it >to do. Some of them run the same apps I've used for years...sometimes for profit. I do remember the not so boring years with them. Then I find another and start over. >I get frustrated with PCs as well. I hate it when stuff won't fit >together, correctly, for instance. Unfortunetly, PCs are about all I >have, until I pick up my PDP11/53 Monday or Tuesday :-) Ah a late model Qbus machine. The PDP-11 collection inculeds: LSI-11/03 PDP-11/23 PDP-11/23B PDP-11/73 Also a PDT-11/130 Pro350 Pro380 An ex digit (DEC employee). Allison

24 years, 1 month

SCSI connectivity

by ajp166＠bellatlantic.net

From: Eric J. Korpela <korpela(a)ellie.ssl.berkeley.edu> >The classic-cmp question I have is at what point is a machine too slow for >SCSI, and how do things degrade as a machine gets slower. My Apple IIgs Well expereince is that there is no too slow. I have SCSI on a 4mhz Z80 and it's decently fast compared to the MFM bridge controllers. > But I assume there is a point at which things >break if bytes don't move fast enough. Anyone know what that point is? I've No such point. I've run SCSI on said same z80 at 1mhz clock (testing something else). SCSI does not have a minimum speed. >been thinking about sticking an 8 bit SCSI card in my old Epson PC which, >because of brain damaged bus design can only pull 150 kB/s off of its drives. >Think it will work? Yes. Likely it will be faster. Most of the "slow" older PCs were due to the limited buffers on the then current disk controllers. My Leading Edge D running the 8088 (4.77mhz) ran much faster with the 8bit IDE adaptor (acculogic) and a WD420mb IDE. Allison

24 years, 1 month

carter afb

by ajp166＠bellatlantic.net

From: <many echos> >> I have a 1969 AMC Javelin SST - 343 with a Carter AFB Carb - my Likely it was a bug, aka Outlook virus that echoed an Email and the attachment was likely the bugs pass along. Allison

24 years, 1 month

SCSI connectivity

by ajp166＠bellatlantic.net

From: Jeff Hellige <jhellige(a)earthlink.net> >>In general, I'd say that if you can find an alternative to ADAPTEC, at least >>with their PCI products, I'd use the alternative. > > I've never had any problems with the 2930U with CD-R's, >scanners and hard disks. I've not used the 2940U2B enough to make a >judgement yet. I'll likely be running both in the same machine soon >though so that I don't have to try and mix the LVD and SCSI-2 stuff >on the same bus. The 2930U would be just for legacy stuff I don't >feel like upgrading anyway, such as my scanner. Same here. the 2930 series (most are U but I have a u2B)is a good board that seems to be unbreakable. I must have at least 6 in use plus another here at home. Two of those were installed to support Plextor CDwriters exclusively on systems with IDE disks. Mixing drive interface types on SCSI busses is somthing I DO NOT do, two many performance impacts. Allison

24 years, 1 month

Jump to page:

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