Re: Slashed letter O, unslashed letter zero

On 4/26/22 20:10, ben via cctalk wrote: > On 2022-04-26 8:48 p.m., Chuck Guzis via cctalk wrote: > >> CDC actually adopted OCR-A as their official internal font.  My office >> typewriter (Olivetti) had such a font.   I hated it. >> > > Well you can't have them use IBM equipment. > Looking at

new Z80 monitor ROM works with no RAM

I wrote a new monitor ROM for the Z80, called umonz, which can provide some basic monitor functionality even if there is no working RAM. In other words, it doesn't use a stack or store any variables in RAM. It supports reading and writing memory, I/O ports, and loading and dumping Intel hex

Re: Slashed letter O, unslashed letter zero

On Tue, Apr 26, 2022 at 6:25 PM Shoppa, Tim via cctalk wrote: > I'm 99% sure I've seen a listing of various Model 33 type-cylinder choices on > some greenkeys site. Maybe it's in one of my paper Teletype manuals. Most are > at least related to ASCII but there were a handful that were really

Re: Slashed letter O, unslashed letter zero

On 2022-04-26 8:48 p.m., Chuck Guzis via cctalk wrote: CDC actually adopted OCR-A as their official internal font. My office typewriter (Olivetti) had such a font. I hated it. Well you can't have them use IBM equipment. Looking at some IBM DOC's from the 60's they had boxed tables for

Re: Slashed letter O, unslashed letter zero

On 4/26/22 19:05, Fred Cisin via cctalk wrote: > I remember about 30 years ago, a registration card for a Microsoft > product had specific forms that they wanted for certain letters, for the > sake of a slightly inadequate handwriting recognition program.  Among > those was "ticked letter O".  A

Re: Slashed letter O, unslashed letter zero

I remember about 30 years ago, a registration card for a Microsoft product had specific forms that they wanted for certain letters, for the sake of a slightly inadequate handwriting recognition program. Among those was "ticked letter O". A round 'O", with an extra mark on the upper right.

Re: BASIC environment ending with "run complete", and slashed 'O' characters?

> On Apr 26, 2022, at 7:55 PM, Jules Richardson > wrote: > > Hi Paul, > > Thanks for that! I'd mentioned this over on Facebook, where I'd also been > able to post a photo of the transcript, and someone there pointed out that > the BASIC listing uses single quotes around strings (what I'd

Re: BASIC environment ending with "run complete", and slashed 'O' characters?

Hi Paul, Thanks for that! I'd mentioned this over on Facebook, where I'd also been able to post a photo of the transcript, and someone there pointed out that the BASIC listing uses single quotes around strings (what I'd expect to be ASCII 27h) rather than the double quotes that BASIC

H7816-BA power supply (Was Re: H7821 power supply in MicroVAX 3100, SCSI disk enclosures and others)

A few months ago, I mentioned a faulty H7816-BA power supply in a rackmount DEC 3000/600 Alphaserver. I finally got around to looking at it again recently. I hoped I had an identical working power supply to compare it to but I didn't. It turns out what I had is two working H7816-AA power

Re: Slashed letter O, unslashed letter zero

On 2022-04-26 4:28 p.m., Fred Cisin via cctalk wrote: On Tue, 26 Apr 2022, Chuck Guzis wrote: Whole operating systems got written at night, I suspect. I suspect that Windoze was written during business hours. if you change that to "Whole operating systems got written/DEBUGGED at night, I

Re: Slashed letter O, unslashed letter zero

On Tue, 26 Apr 2022, Gavin Scott wrote: Forgive me, but is this not why we had a place on the coding forms explicitly for this purpose, as seen in: https://upload.wikimedia.org/wikipedia/commons/1/18/FortranCodingForm.png where "Punching Instructions" consisted of example pairs of a writer's

Re: Slashed letter O, unslashed letter zero

On Tue, 26 Apr 2022, Chuck Guzis wrote: Whole operating systems got written at night, I suspect. I suspect that Windoze was written during business hours.

Re: Slashed letter O, unslashed letter zero

On 4/26/22 13:41, ben via cctalk wrote: > PS: Did any common I/O devices have the ALGOL symbols Less than or > Equals, Greater than or equals , not , arrows and other misc symbols? > CDC Display code certainly started out that way. See https://en.wikipedia.org/wiki/CDC_display_code. If you

Re: Slashed letter O, unslashed letter zero

Bummer, no attachments... paul > On Apr 26, 2022, at 5:14 PM, Paul Koning via cctalk > wrote: > > > >> On Apr 26, 2022, at 4:41 PM, ben via cctalk wrote: >> >> ... >> PS: Did any common I/O devices have the ALGOL symbols Less than or Equals, >> Greater than or equals , not ,

Re: Slashed letter O, unslashed letter zero

> On Apr 26, 2022, at 4:41 PM, ben via cctalk wrote: > > ... > PS: Did any common I/O devices have the ALGOL symbols Less than or Equals, > Greater than or equals , not , arrows and other misc symbols? Yes, the Flexowriters at TU Eindhoven used to punch ALGOL programs for the Electrologica

Re: Slashed letter O, unslashed letter zero

On 2022-04-26 2:01 p.m., Gavin Scott via cctalk wrote: On Tue, Apr 26, 2022 at 2:44 PM Fred Cisin via cctalk wrote: We did have one old-timer who slashed letter O. We talked to the keypunchers, and solved it by a discussion, and having him put his name in red LARGE on every sheet. Forgive

Re: Slashed letter O, unslashed letter zero

On 4/26/22 12:44, Fred Cisin wrote: > One of my cow-orkers, a programmer, insisted that it was much faster for > him to type as he composed, even on a 026, than it was to write on > coding sheets, and then hand it off. There is something to that. Many was the time that I'd be punching late at

RE: Slashed letter O, unslashed letter zero

At the University Of Maryland, in the Computer Science building (in the basement) there were about a dozen punches. A few (two I think?) were labeled "EXPRESS PUNCH 10 CARDS OR LESS". One evening, there was a line of 15 people waiting for a regular punch and a line of about 5 people waiting for

Re: Slashed letter O, unslashed letter zero

On Tue, Apr 26, 2022 at 2:44 PM Fred Cisin via cctalk wrote: > We did have one old-timer who slashed letter O. We talked to the > keypunchers, and solved it by a discussion, and having him put his name in > red LARGE on every sheet. Forgive me, but is this not why we had a place on the coding

Re: Yet another TRS-80 question

On 4/26/22 7:00 PM, Bill Gunshannon wrote: Has anyone ever seen a TRSDOS equivalent of the CP/M LOAD command?  I have the PL/M-80 compiler running but it's output is an Intel HEX File. Works great for CP/M but I would really like to try some programs under TRSDOS.  The only other option at this

Re: Slashed letter O, unslashed letter zero

On Tue, 26 Apr 2022, Chuck Guzis via cctalk wrote: I recall getting a job back from keypunch with a note attached: "I wasn't sure if you meant zero or oh (I always slashed my zeroes; the keypunch form specifically called that out), so I did some of both". Card deck into trash; go find a

Re: Slashed letter O, unslashed letter zero

On 4/26/22 10:48, Warner Losh via cctalk wrote: > On Tue, Apr 26, 2022 at 11:25 AM Shoppa, Tim via cctalk < > cctalk@classiccmp.org> wrote: > >> This website has a history of slashing the letter O (and also ticked, >> center-dotted, etc.) oriented around computing: >>

Re: Slashed letter O, unslashed letter zero

On Tue, Apr 26, 2022 at 11:25 AM Shoppa, Tim via cctalk < cctalk@classiccmp.org> wrote: > This website has a history of slashing the letter O (and also ticked, > center-dotted, etc.) oriented around computing: > https://circuitousroot.com/artifice/letters/characters/slashed-o/index.html Now I

Slashed letter O, unslashed letter zero

Paul writes: > As for the slashed letter O, that's strange. Certainly it is not CDC > practice; the only place I ever ran into this is with IBM, I always > considered it an example of IBM doing > things the weird way. So it sounds like whoever bought those Teletype > machines had them

Re: BASIC environment ending with "run complete", and slashed 'O' characters?

I used to use some tty33’s in the 70s which were used to connect to an hp2000 timeshared system. Those tty’s had the slash O and non-slash zero that you describe. It may have been a common tty33 configuration. -Bob > On Apr 26, 2022, at 9:24 AM, Paul Koning via cctalk > wrote: > >

Re: BASIC environment ending with "run complete", and slashed 'O' characters?

Apparently so. The word from a CDC experts list is that the "run complete" message is not from BASIC itself (which is indeed a CDC product) but rather from the time sharing executive, called TELEX in KRONOS and early NOS, and IAF in later versions of NOS. As for the slashed letter O, that's

Re: BASIC environment ending with "run complete", and slashed 'O' characters?

Yes - CDC 6000 and CYBER series machines running BASIC 2.1 (and all later versions) under KRONOS and NOS output "RUN COMPLETE." when the user program finished. Tom On Tue, Apr 26, 2022 at 7:29 PM Jules Richardson via cctalk < cctalk@classiccmp.org> wrote: > On 4/26/22 02:05, Raymond Wiker

Re: BASIC environment ending with "run complete", and slashed 'O' characters?

On Tue, Apr 26, 2022, 07:29 Jules Richardson via cctalk < cctalk@classiccmp.org> wrote: > > (oddly I never saw my post make it to the list, so assumed it was down or > the message had got caught somewhere. Evidently it did make it though and > for some reason my 'list copy' of it never made it

Re: BASIC environment ending with "run complete", and slashed 'O' characters?

On 4/26/22 02:05, Raymond Wiker wrote: https://en.wikipedia.org/wiki/CDC_Kronos , perhaps? Could well be, given the MECC / Minnesota / Cray connections. Question then is whether the CDC 6000 series (or later) machines had a BASIC environment that

Re: BASIC environment ending with "run complete", and slashed 'O' characters?

https://en.wikipedia.org/wiki/CDC_Kronos , perhaps? > On 26 Apr 2022, at 03:08, Jules Richardson via cctalk > wrote: > > > Perhaps a long shot, but I've got an old piece of paper here showing a BASIC > listing followed by a program run where the