winscape 2349

Sure. However, there were different stages of booting. Some had to be done "by hand". Some could "start off" at step 3 or 4 or 5. As we learned how to "can" our procedures, we could figure the step to use to recover. As timesharing systems became more experienced, they could even "restart" errors without a crash. TOPS-10 called them job stopcodes.

As the procedures to get a system running became repeated and boring, the humans "canned" them into bits and ordered procedures. This is what I call the evolution of code. Every single aspect of any computing goes through this evolution. If the actions taken by a human are the same and repeated, you can put these actions into bits and call it a boot, a batch script, or a program.

Most people don't get to that detail; they shouldn't have to. However, equating these steps with a complete installation of the software systems is offensive and stinks. :-)

I also believe that the technical meanings were different in detail for each equipment manufacturer.

Yes.

What system does this user use? We have a cold system. It isn't running anything.

How does this writing get done? There aren't any drivers in core.

IBM had problems with their approach. This sysgen could take from 1-2 hour to hours and was required with every system restart and could only be done by the exec or the kernal(unix). Our OSes went through the sysgen once as a user build. At system startup time, the only things that needed to be done was detecting media that was on-line, zeroing memory and starting operator jobs such as access control, accounting, spooling, and system wide IPCF services. This took a very long three or four minutes.

If anything is taking a parameter file, then it has to generate code before executing an instruction that uses the parameter input as part of the instruction, e.g., channel number.

The details of the procedures are different based on who shipped what.

heh. You've never been to a code review.

Now take a look at the biz. There is an enbreasty who is trying to remove all standards and their uses by not complying to any of them. This is also a symptom of PCitis; "nobody else but me matters".

BAH