And even CP/M apps were somewhat sensitized... Ever
type A:ASM FOO.ASM and
wonder why you got a disk specification error?
Doesn't it try to write the object to S:, and the listing to M: ? Neither
of which probably exist.
I remember the first time I used ZASM (a CP/M Z80 assembler) on an
RML380Z. I typed 'ZASM FOO,ZSM and got a 'BDOS ERROR ON Z: SELECT' for my
efforts....
To return to the original question, how far back do you have to go for
unix's cc(1) to require .c on C source files, .o on object files (to be
linked it), and so on?
-tony