Re: [M100] Burn in program
On 12/7/21 8:12 am, Peter Noeth wrote: I miss those days of computing I believe you might be amongst like-minded individuals here. :) Cheers, --dt
Re: [M100] Burn in program
This was in the early 80's. I worked on both the Nova 1200 and the Eclipse S230, both were ALU based. The Novas we used were core memory only (4k or 8k x 16 bits). The Eclipses were usually core memory, but there were dynamic memory boards on the later systems. The core memory could be "interleaved" to increase write speed. The Eclipses also had a two board CPU with the second board a kind of math co-processor / accelerator. We also used the Data General S140 in the later systems, which had the "virtual" front console (no blinking lights or switches), but I didn't work on those. As Jerry mentioned, AutoTrol was a competitor with Calma and about two or three others. Calma started with a big digitizing table, to input paper maps. Systems were then developed (the GDS line) to do IC mask design, which was the major business, and then mechanical drafting and finally PCB layout. National Semiconductor was a big customer. We also included pen plotters (HP and Xinetics) of which some could handle a 4'x8' sheet of paper, for plotting out the IC masks at a magnification one could easily see the features and verify measurements. I miss those days of computing Regards, Peter > -- > > Message: 7 > Date: Sun, 11 Jul 2021 10:42:24 +0930 > From: Daryl Tester > To: m...@bitchin100.com > Subject: Re: [M100] Burn in program > Message-ID: > <0618d8d5-1d28-7d6a-542b-fd27c8420...@handcraftedcomputers.com.au> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 11/7/21 9:24 am, Peter Noeth wrote: > > > ... repairing?Data General mini computers, > > Novas, or Eclipses? You said discrete ALU board, so I'm suspecting Nova, > but I've never seen the internals of an Eclipse. > > Cheers, >--dt > >
Re: [M100] Burn in program
computer. > > But that was decades ago now. I should re-make that interface board again > for nostalgia sake. Back in those days, I frequently used my M100 as a test > computer where I was working (CALMA, a CAD/CAM equipment manufacturer), > repairing Data General mini computers, and Lexidata graphics computers > mostly along with the peripherals. Discrete ALU based processor boards with > ~150 74LS type IC's, core and dynamic memory, 9-track tape, video monitors, > serial data terminals, etc. > > Fun times. > > Regards, > > Peter > > >> ------ >> >> Message: 6 >> Date: Fri, 9 Jul 2021 19:58:12 -0500 >> From: "Jeffrey Birt" >> To: >> Subject: [M100] Burn in program >> Message-ID: <02da01d77526$a92cede0$fb86c9a0$@soigeneris.com> >> Content-Type: text/plain; charset="us-ascii" >> >> Hi all, >> >> Burn in test? I was just wondering what sort of program you guys like to >> run >> as a burn in test of a computer you have just repaired. I modified the >> M100 >> test harness code so can run a continuous RAM test but that is not a >> really >> useful test that everyone can use as it only works with the test harness. >> >> Maybe something in BASIC that just runs some calculations, displays things >> on the LCD, etc. to test how stable the computer is when running for a few >> hours. Any favorites? >> >> Thanks, >> >> Jeff Birt >> >>
Re: [M100] Burn in program
On 11/7/21 9:24 am, Peter Noeth wrote: ... repairing Data General mini computers, Novas, or Eclipses? You said discrete ALU board, so I'm suspecting Nova, but I've never seen the internals of an Eclipse. Cheers, --dt
Re: [M100] Burn in program
I would wish something like the same Hardware, but on upgraded Motherboard. With new capcitors etc. I am NEC PC-8201 user, all this Thru-Hole chips are still avaiable today, or maybe its possible to use less components. I build a Minimax 8085 http://www.malinov.com/Home/sergeys-projects/minimax8085 All the parts for this project were avaiable on ebay, so i am pretty sure - it would be tecnically possible. Many Amiga 500 and 1200 computers got new revised mainboards... -- Kind regards / Mit freundlichen Grüßen ExPLIT IT Solutions Pawel Radomychelski -Original Message- From: Peter Noeth Reply-To: m...@bitchin100.com To: m100@lists.bitchin100.com Subject: Re: [M100] Burn in program Date: Sat, 10 Jul 2021 16:54:49 -0700 I have always used ML / BASIC programs I wrote to do troubleshooting / burn-in testing, using loopback connectors to test external ports (on a par with the original IBM XT Diagnostics diskette). The programs could be simple or complex, depending on the situation. Sometimes I only burn-in test the area of repair. For example the serial port, with a loopback connector. If the problem was in the address decode circuitry, then I test all devices (memory, display, RS-232, printer, etc). If the repair required replacement of an IC or module, then I usually test for only one or two hours. If the problem is intermittent connections, then I test for 24 to 48 hours, at elevated temperature. Of course if the uProcessor is not running, then the computer cannot be used to diagnose itself. In that case, if the uProcessor has a pin that can "tri-state" all output pins (the 80C85 does), then I used a test computer with a parallel port interface I designed that could exercise all the address, data and control pins by clipping onto the target computers uProcessor with a cable and test clip. The test program could also write and read from Memory / Port addresses to check the address decoding circuitry on the target computer. But that was decades ago now. I should re-make that interface board again for nostalgia sake. Back in those days, I frequently used my M100 as a test computer where I was working (CALMA, a CAD/CAM equipment manufacturer), repairing Data General mini computers, and Lexidata graphics computers mostly along with the peripherals. Discrete ALU based processor boards with ~150 74LS type IC's, core and dynamic memory, 9-track tape, video monitors, serial data terminals, etc. Fun times. Regards, Peter > > -- > > Message: 6 > Date: Fri, 9 Jul 2021 19:58:12 -0500 > From: "Jeffrey Birt" > To: > Subject: [M100] Burn in program > Message-ID: <02da01d77526$a92cede0$fb86c9a0$@soigeneris.com> > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > Burn in test? I was just wondering what sort of program you guys like > to run > as a burn in test of a computer you have just repaired. I modified > the M100 > test harness code so can run a continuous RAM test but that is not a > really > useful test that everyone can use as it only works with the test > harness. > > Maybe something in BASIC that just runs some calculations, displays > things > on the LCD, etc. to test how stable the computer is when running for > a few > hours. Any favorites? > > Thanks, > > Jeff Birt >
Re: [M100] Burn in program
I have always used ML / BASIC programs I wrote to do troubleshooting / burn-in testing, using loopback connectors to test external ports (on a par with the original IBM XT Diagnostics diskette). The programs could be simple or complex, depending on the situation. Sometimes I only burn-in test the area of repair. For example the serial port, with a loopback connector. If the problem was in the address decode circuitry, then I test all devices (memory, display, RS-232, printer, etc). If the repair required replacement of an IC or module, then I usually test for only one or two hours. If the problem is intermittent connections, then I test for 24 to 48 hours, at elevated temperature. Of course if the uProcessor is not running, then the computer cannot be used to diagnose itself. In that case, if the uProcessor has a pin that can "tri-state" all output pins (the 80C85 does), then I used a test computer with a parallel port interface I designed that could exercise all the address, data and control pins by clipping onto the target computers uProcessor with a cable and test clip. The test program could also write and read from Memory / Port addresses to check the address decoding circuitry on the target computer. But that was decades ago now. I should re-make that interface board again for nostalgia sake. Back in those days, I frequently used my M100 as a test computer where I was working (CALMA, a CAD/CAM equipment manufacturer), repairing Data General mini computers, and Lexidata graphics computers mostly along with the peripherals. Discrete ALU based processor boards with ~150 74LS type IC's, core and dynamic memory, 9-track tape, video monitors, serial data terminals, etc. Fun times. Regards, Peter > -- > > Message: 6 > Date: Fri, 9 Jul 2021 19:58:12 -0500 > From: "Jeffrey Birt" > To: > Subject: [M100] Burn in program > Message-ID: <02da01d77526$a92cede0$fb86c9a0$@soigeneris.com> > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > Burn in test? I was just wondering what sort of program you guys like to > run > as a burn in test of a computer you have just repaired. I modified the M100 > test harness code so can run a continuous RAM test but that is not a really > useful test that everyone can use as it only works with the test harness. > > Maybe something in BASIC that just runs some calculations, displays things > on the LCD, etc. to test how stable the computer is when running for a few > hours. Any favorites? > > Thanks, > > Jeff Birt > >
Re: [M100] Burn in program
Thanks Jerry, reading the entire address range is a good idea so that the whole address bus and all memory is exercised. I added in clearing TIME$ first, and then printing it after the CLS. I also snuck in a BEEP before the GOTO per Josh’s suggestion. It takes 25:07 to walk the entire address range and print out all characters >=32 10 TIME$=”00:00:00” 20 CLS:PRINT TIME$;” “; 30 FOR N=0 TO 65535 40 X=PEEK(N) 50 IF X < 32 THEN 70 60 PRINT CHR$(X); 70 NEXT N 80 BEEP 90 GOTO 20 Jeff From: M100 On Behalf Of Jerry Davis Sent: Saturday, July 10, 2021 11:59 AM To: m...@bitchin100.com Subject: Re: [M100] Burn in program Hey, Jeff Its nothing like a real exorciser but I've been running the following code on BASIC language machines since I was a kid to see how the machine will respond and how long it will run. It's more fun to watch than anything else. 10 CLS 20 FOR N=0 TO 65535 30 X=PEEK(N) 40 IF X < 32 THEN 60 50 PRINT CHR$(X); 60 NEXT N 70 GOTO 10 Machines with memory mapped I/O don't appear to be adversely affected by reads on their ports. I've run it on machines with serial consoles (polled mode), disk drive controllers, etc. I was working on a 6809 machine running Flex09 that would crash intermittently when running a BASIC program. The above program would lock up the machine in a few minutes to a few hours. The RAM pattern test utility would crash faster than I could get a scope on it. I finally found the glitch in a RAM select line and fixed it. The RAM pattern test ran clear. Then I ran this program for a few days without a lockup and called it fixed. Jerry Original message From: Jeffrey Birt mailto:bir...@soigeneris.com> > Date: 7/9/21 7:59 PM (GMT-06:00) To: m...@bitchin100.com <mailto:m...@bitchin100.com> Subject: [M100] Burn in program Hi all, Burn in test? I was just wondering what sort of program you guys like to run as a burn in test of a computer you have just repaired. I modified the M100 test harness code so can run a continuous RAM test but that is not a really useful test that everyone can use as it only works with the test harness. Maybe something in BASIC that just runs some calculations, displays things on the LCD, etc. to test how stable the computer is when running for a few hours. Any favorites? Thanks, Jeff Birt Original message From: Jeffrey Birt mailto:bir...@soigeneris.com> > Date: 7/9/21 7:59 PM (GMT-06:00) To: m...@bitchin100.com <mailto:m...@bitchin100.com> Subject: [M100] Burn in program Hi all, Burn in test? I was just wondering what sort of program you guys like to run as a burn in test of a computer you have just repaired. I modified the M100 test harness code so can run a continuous RAM test but that is not a really useful test that everyone can use as it only works with the test harness. Maybe something in BASIC that just runs some calculations, displays things on the LCD, etc. to test how stable the computer is when running for a few hours. Any favorites? Thanks,Jeff Birt
Re: [M100] Burn in program
Hey, Jeff Its nothing like a real exorciser but I've been running the following code on BASIC language machines since I was a kid to see how the machine will respond and how long it will run. It's more fun to watch than anything else. 10 CLS 20 FOR N=0 TO 65535 30 X=PEEK(N) 40 IF X < 32 THEN 60 50 PRINT CHR$(X); 60 NEXT N 70 GOTO 10 Machines with memory mapped I/O don't appear to be adversely affected by reads on their ports. I've run it on machines with serial consoles (polled mode), disk drive controllers, etc. I was working on a 6809 machine running Flex09 that would crash intermittently when running a BASIC program. The above program would lock up the machine in a few minutes to a few hours. The RAM pattern test utility would crash faster than I could get a scope on it. I finally found the glitch in a RAM select line and fixed it. The RAM pattern test ran clear. Then I ran this program for a few days without a lockup and called it fixed. Jerry Original message From: Jeffrey Birt Date: 7/9/21 7:59 PM (GMT-06:00) To: m...@bitchin100.com Subject: [M100] Burn in program Hi all, Burn in test? I was just wondering what sort of program you guys like to run as a burn in test of a computer you have just repaired. I modified the M100 test harness code so can run a continuous RAM test but that is not a really useful test that everyone can use as it only works with the test harness. Maybe something in BASIC that just runs some calculations, displays things on the LCD, etc. to test how stable the computer is when running for a few hours. Any favorites? Thanks, Jeff Birt Original message From: Jeffrey Birt Date: 7/9/21 7:59 PM (GMT-06:00) To: m...@bitchin100.com Subject: [M100] Burn in program Hi all, Burn in test? I was just wondering what sort of program you guys like to run as a burn in test of a computer you have just repaired. I modified the M100 test harness code so can run a continuous RAM test but that is not a really useful test that everyone can use as it only works with the test harness. Maybe something in BASIC that just runs some calculations, displays things on the LCD, etc. to test how stable the computer is when running for a few hours. Any favorites? Thanks,Jeff Birt
Re: [M100] Burn in program
The beep is a great idea! I think this one was a simple, but it was intermittent for the owner and just happened to quit completely on its way to me. The memory protect switch was gummed up not making good contact. Luckily is was completely open when it got to me so it was easy to track down. Jeff -Original Message- From: M100 On Behalf Of Josh Malone Sent: Saturday, July 10, 2021 11:10 AM To: m...@bitchin100.com Subject: Re: [M100] Burn in program Last time I had an unstable machine, I just used a quick basic program with POWER CONT, a delay loop, a cycle counter, and BEEP (so I could notice across the house when it had died). But, in my case, I knew (or, STRONGLY suspected) that the fault was in the power supply and that the rest of the machine was likely fine. On Fri, Jul 9, 2021 at 8:59 PM Jeffrey Birt wrote: > > Hi all, > > > > Burn in test? I was just wondering what sort of program you guys like to run > as a burn in test of a computer you have just repaired. I modified the M100 > test harness code so can run a continuous RAM test but that is not a really > useful test that everyone can use as it only works with the test harness. > > > > Maybe something in BASIC that just runs some calculations, displays things on > the LCD, etc. to test how stable the computer is when running for a few > hours. Any favorites? > > > > Thanks, > > Jeff Birt > >
Re: [M100] Burn in program
Last time I had an unstable machine, I just used a quick basic program with POWER CONT, a delay loop, a cycle counter, and BEEP (so I could notice across the house when it had died). But, in my case, I knew (or, STRONGLY suspected) that the fault was in the power supply and that the rest of the machine was likely fine. On Fri, Jul 9, 2021 at 8:59 PM Jeffrey Birt wrote: > > Hi all, > > > > Burn in test? I was just wondering what sort of program you guys like to run > as a burn in test of a computer you have just repaired. I modified the M100 > test harness code so can run a continuous RAM test but that is not a really > useful test that everyone can use as it only works with the test harness. > > > > Maybe something in BASIC that just runs some calculations, displays things on > the LCD, etc. to test how stable the computer is when running for a few > hours. Any favorites? > > > > Thanks, > > Jeff Birt > >
[M100] Burn in program
Hi all, Burn in test? I was just wondering what sort of program you guys like to run as a burn in test of a computer you have just repaired. I modified the M100 test harness code so can run a continuous RAM test but that is not a really useful test that everyone can use as it only works with the test harness. Maybe something in BASIC that just runs some calculations, displays things on the LCD, etc. to test how stable the computer is when running for a few hours. Any favorites? Thanks, Jeff Birt
