SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : All About Sun Microsystems

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: JC Jaros who wrote (27301)2/7/2000 12:05:00 PM
From: rudedog  Read Replies (1) of 64865
 
JC -
Although times have changed, in the early days Thomas was speaking of, assembler was a high level language... in the late 60's I knew IBM 1800 and 360 machine language by heart and could look at a subroutine and tell what the calling parameters and referenced segments were - I also knew most of the OS at the machine level and occasionally wrote core that modified the OS through a device known as "INSKEL COMMON" which was a common data area in the OS itself... probably to the chagrin of programmers who followed my trail, self-modifying code was one of the tricks I used to save memory.

1800s were used a lot in real-time process control, and several of us became proficient at writing patches in machine language on a running machine, then banging the pointer to link the patch - all in realtime, on a machine that was controlling a glass furnace or steel mill. These were actual "core" machines - the memory didn't go away when powered down - so it was possible to resurrect even a bombed machine if most of the code was still in good shape... and also go around in memory and look at anything you wanted, even after a re-boot.

Virtual operating systems pretty much put an end to that since the memory image was not stable enough to fool with...
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext