Was about to Google it.. and.. you've done the work for me. Thank you!

I'm confused by the code listing in the magazine. The Os are 0s and the 0s are Os for no good reason.

Here is the code typed up: https://github.com/LiquidFox1776/oregon-trail-1978-basic

In the early days, the important thing was to be able to distinguish between zero and oh. There was no standard yet established for the best way to do that. At least it was better than typewriters, which didn't have zero or one keys at all - you had to use the upper-case O and lower-case L instead.

I get that, but this is the opposite of what is normal. This is replacing Os with 0s which I've never seen outside of warez sites in my 40 years with computers.

If you go back far enough, there was no "normal". 40 years might not be far enough back. Different equipment did things differently. Which was O and which was 0 was a matter of convention, there weren't any rules for it and still aren't.

Programmers had been putting slashes through zeros long before The Oregon Trail showed up, and my Mom might even have an old, hand-written IBM coding form lying around to prove it. I imagine in this case it is probably OCR gone awry that confused the zeros and Os.

As one who originally took typing class on manual typewriters, I can tell you that every typewriter I’ve ever used had zeros and ones. If one were to tell me that there existed portable typewriters that did not have those characters, I might believe it.

I never said slashed zeros were unknown, just that conventions hadn't settled yet and were far from universal. Sometime you got a dot in the middle instead of a slash.

I don't know if OCR even existed back when this was published. If it did, it wasn't common.

The manual typewriter I learned to type on did not have a zero or one.

How might one go about running this original code on a modern day PC? An emulator of sorts?

It's BASIC.

BASIC has lots of different dialects. Anybody know which one this is, and what modern choices would be compatible with it?

I don't see too many quirks in the listing, so most any classical BASIC variant should handle it. Like PC-BASIC[1], FreeBASIC[2], or the venerable GW-BASIC[3]. (The later I think you need to run in DOSBox though.)

I did notice one unique keyword that should be easy to fix.

    6200 PRINT "TYPE "; S$(56)
    6210 B3 = CLK(0)
    6220 INPUT C$
    6230 B1 = CLK(0)
    6240 B1=((B1-B3)*3600)=(D9-1)

I couldn't find 'CLK' in any of the BASICs I know of. Seems from context to be a time function. My guess is it returns number of seconds since system boot, or program start.

[1] http://www.pc-basic.org/

[2] https://www.freebasic.net/

[3] http://gw-basic.com/