Re: Infocom mystery binary

2019-04-24 Thread John Foust via cctalk
At 05:14 AM 4/24/2019, David Griffith via cctalk wrote: >When I first noticed that the binary wasn't stripped, I tried poking around >with assorted disassemblers and decompilers hoping to get something resembling >C code out of it. And you found what? - John

Re: Infocom mystery binary

2019-04-24 Thread David Griffith via cctalk
My reply is at the bottom. Please put your reply there too. On Wed, 24 Apr 2019, Ethan Dicks wrote: On Tue, Apr 23, 2019 at 9:58 PM David Griffith via cctalk wrote: In one of the repositories of Infocom game source code recently uploaded to Github, there's an executable that appears to have

Re: Infocom mystery binary

2019-04-23 Thread Ethan Dicks via cctalk
On Tue, Apr 23, 2019 at 9:58 PM David Griffith via cctalk wrote: > In one of the repositories of Infocom game source code recently uploaded > to Github, there's an executable that appears to have come from an m68k > Unix machine of some sort. It's at > https://github.com/historicalsource/zork-ger

Re: Infocom mystery binary

2019-04-23 Thread Warner Losh via cctalk
On Tue, Apr 23, 2019, 9:42 PM Phil Budne via cctalk wrote: > $ file zap > zap: mc68k COFF object not stripped (demand paged) > > ISTR A/UX had a COFF. 68k SunOS used a.out format. > SunOS used a.out for all architectures. Solaris used ELF. Warner P.s. the Solaris rebranding of SunOS notwithst

Re: Infocom mystery binary

2019-04-23 Thread Phil Budne via cctalk
$ file zap zap: mc68k COFF object not stripped (demand paged) ISTR A/UX had a COFF. 68k SunOS used a.out format.

Infocom mystery binary

2019-04-23 Thread David Griffith via cctalk
In one of the repositories of Infocom game source code recently uploaded to Github, there's an executable that appears to have come from an m68k Unix machine of some sort. It's at https://github.com/historicalsource/zork-german/blob/master/zap. Over at intfiction.org[1], it was initially cl