CompuServe Thread

That's not such a silly question! As a matter of fact I have, but I get lots of unresolved symbols using either of ASTARTUP or LSTARTUP. Since I posted the original message I've hacked the startup code to resolve the symbols and have written my own input routines using the stdin file handle set up in the init code. BTW, when I was messing around with the startup modules, I found that ASTARTUP.ASM doesn't detect that the program has been invoked from the Workbench correctly. It's an easy fix if you compare the code to LSTARTUP and move a stack operation to the correct spot (under the Workbench init code). This all relates to the Lattice 'C' on the IBM cross development system so it may (or may not) affect others on the forum.

That's not such a silly question! As a matter of fact I have, but I get lots of unresolved symbols using either of ASTARTUP or LSTARTUP. Since I posted the original message I've hacked the startup code to resolve the symbols and have written my own input routines using the stdin file handle set up in the init code. BTW, when I was messing around with the startup modules, I found that ASTARTUP.ASM doesn't detect that the program has been invoked from the Workbench correctly. It's an easy fix if you compare the code to LSTARTUP and move a stack operation to the correct spot (under the Workbench init code). This all relates to the Lattice 'C' on the IBM cross development system so it may (or may not) affect others on the forum.