roode@hydra.cf.uci.edu (Dana Roode) (10/10/89)
We've been running a group of Apollo DN3000 and 3500s running 10.1 for sometime, but recently we've had to help some folks with their DN3000s (1 3500) running Aegis 9.7. Im having a hard time figuring out how the startup files work - in particular, which ones are executed when and how the system determines this. Picking a startup file depends on the "type" of system - how can I verify what "type" a system thinks it is? One particular case is a diskless DSP node that, according to my interpretation of the manuals, should run /sys/node_data/startup.spm. I make changes to that file, they seem to be ignored. The other systems all have disks and monitors - they should execute startup.1280bw or .1280color? Where do startup.19l and startup.color fit in? Please reply directly to me, as I might miss entries to this newgroup. Any help would be greatly appreciated, kind comp.sys.apollo folks have made more sense to me than all of the Apollo manuals put together. Dana Roode Academic Computing UC Irvine
derstad@CIM-VAX.HONEYWELL.COM ("DAVE ERSTAD") (10/11/89)
A DSP should bring up the SPM (rather than the DM, as on a head-ed node) at boot time, which will execute the startup.spm file (assuming, of course, you're getting past the phase II boot shell). Any startup files you don't recognize probably deal with older hardware. For example, startup.19l works with the 19" landscape displays found on DN300, 320, and 330 models. Dave Erstad Honeywell SSEC DERSTAD@cim-vax.honeywell.com