RE: Compaq Portable brightness knob

2022-01-23 Thread David Griffith via cctalk
My reply is at the bottom. Please put your reply there too. On Sat, 22 Jan 2022, Ali wrote: Is that for me? Because my reply is at the bottom. See bottom. >> Out of curiosity does your brightness >>adjustment work at all?  >I'm looking for the actual plastic knob.  The pot >itself seems to

RE: Building a BA08 for a pdp8/L

2022-01-23 Thread pbirkel--- via cctalk
Thank you. I _would have_ probably also looked at the analogous "MM8I_Schem_Aug69.pdf" print set. But those were antediluvian times; no Bitsavers and DEC wasn't handing out free print sets. You could purchase them, though -- I still have KA10 and MA10 documentation that I acquired that way fo

Re: Typing in lost code

2022-01-23 Thread Mark Kahrs via cctalk
No, OCR totally fails on olde line printer listing. At least the ones I've tried (tesseract, online, ...) On Sat, Jan 22, 2022 at 8:06 PM Ethan O'Toole wrote: > > Can the listings be OCR'ed? > > - Ethan > > > > Has anyone ever used Amazon Mechanical Turk to employ typi

Re: Compaq Portable brightness knob

2022-01-23 Thread Liam Proven via cctalk
On Sun, 23 Jan 2022 at 07:28, David Griffith via cctalk wrote: > > Would someone please suggest a replacement for the Compaq Portable's > brightness knob? This was missing on mine when I got it. 3D print one? -- Liam Proven ~ Profile: https://about.me/liamproven Email: lpro...@cix.co.uk ~ gMa

Re: Typing in lost code

2022-01-23 Thread Paul Koning via cctalk
I've run into that situation too, with listings so difficult that even a commercial OCR program (FineReader) couldn't handle it. At the time Tesseract was far less capable, though I haven't tried it recently to see if that has changed. Anyway, my experience was that the task was hard enough th

Re: Typing in lost code

2022-01-23 Thread Jonathan Chapman via cctalk
I recently dealt with this with the DaJen SCI monitor listing out of the manual. The copy is pretty bad, and either their printer was having issues, or slashing of "zero" vs "O" was inconsistent somehow. OCRing it produced more of a mess than just sitting with the original and a text editor open

PDP-8 clone built by Canadian company Consolidated Computer Inc

2022-01-23 Thread Rod Smallwood via cctalk
I am trying to locate documentation on the PDP-8 clone built by Canadian company Consolidated Computer Inc (Mers Kutt) in the mid 1970's. An example exists in the UK and will be restored when more data than just the system can be found. Rod Smallwood - digital equipment corporation 1975-1985

Re: Typing in lost code

2022-01-23 Thread Gavin Scott via cctalk
On Sun, Jan 23, 2022 at 9:11 AM Paul Koning via cctalk wrote: > One consideration is the effort required to repair transcription errors. > Those that produce syntax errors aren't such an issue; > those that pass the assembler or compiler but result in bugs (say, a mistyped > register number) ar

Re: Typing in lost code

2022-01-23 Thread Noel Chiappa via cctalk
> From: Gavin Scott > I think if I had a whole lot of old faded greenbar etc. ... Someone may > even have done this already See: https://walden-family.com/impcode/imp-code.pdf Someone's already done the specialist OCR to deal with faded program listings. Noel

Re: Typing in lost code

2022-01-23 Thread Gavin Scott via cctalk
On Sun, Jan 23, 2022 at 11:31 AM Noel Chiappa via cctalk wrote: > See: > > https://walden-family.com/impcode/imp-code.pdf > > Someone's already done the specialist OCR to deal with faded program listings. Neat. Though all the complex character recognition part of that work is now like 15-20 lin

Re: Typing in lost code

2022-01-23 Thread dwight via cctalk
It is unlikely that no current day OCR will produce an error free listing. It is possible to train an AI to do this but it requires specific training. It must be on the specific machine code and on the same format. Any generic OCR will have many errors if the text is hard to read. The final produ

Re: Typing in lost code

2022-01-23 Thread Paul Koning via cctalk
> On Jan 23, 2022, at 12:09 PM, Gavin Scott wrote: > > On Sun, Jan 23, 2022 at 9:11 AM Paul Koning via cctalk > wrote: >> One consideration is the effort required to repair transcription errors. >> Those that produce syntax errors aren't such an issue; >> those that pass the assembler or co

Re: Typing in lost code

2022-01-23 Thread Lars Brinkhoff via cctalk
Noel Chiappa wrote: > https://walden-family.com/impcode/imp-code.pdf > Someone's already done the specialist OCR to deal with faded program > listings. I tried to contact the author about converting some of the other IMP listings, but got no reply.

mystery S-100 available

2022-01-23 Thread Stan Sieler via cctalk
Hi, I have a mystery S-100 computer that I'm would like to sell, from the estate of the late Ken Gielow (author of Z80DIS, a great Z80 disassembler). The proceeds will be donated to a non-tax-deductible magic group Ken was a long-time member of. The computer is located in Cupertino, CA (aka "the

Re: Typing in lost code

2022-01-23 Thread Chuck Guzis via cctalk
On 1/23/22 10:16, Paul Koning via cctalk wrote: > Maybe. But OCR programs have had learning features for decades. I've spent > quite a lot of time in FineReader learning mode. Material produced on a > moderate-quality typewriter, like the CDC 6600 wire lists on Bitsavers, can > be handled t

Question about DECtape formulation

2022-01-23 Thread Gary Oliver via cctalk
I've always thought the physical tape wound on a DECtape spool was a fairly conventional 'sandwich' of mylar/oxide/mylar, but a recent 'test' makes me think there is something else involved. I have a number of tapes I'm cleaning (removing dust, etc.)  to make ready to read on a restored (appar

Re: Question about DECtape formulation

2022-01-23 Thread Noel Chiappa via cctalk
> From: Gary Oliver > I've always thought the physical tape wound on a DECtape spool was a > fairly conventional 'sandwich' of mylar/oxide/mylar ... > Was there some kind of 'lubricating' coat on the data side? It makes > sense, but none of my DEC documents or Googling has any

Re: Typing in lost code

2022-01-23 Thread dwight via cctalk
Sorry about the double negative. I was in a hurry as I was supposed to drive over the hill to Santa Cruz for a couple hours. "It is unlikely that no current day OCR will produce an error free listing." Should have read: "It is unlikely that any current day OCR will produce an error free listing."