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

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

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

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 BASIC environment terminates with "run complete" - does that behavior ring any bells with anyone? I'm mildly curious what machine it may have come from. The other