{"id":1184,"date":"2010-02-10T00:01:48","date_gmt":"2010-02-10T08:01:48","guid":{"rendered":"http:\/\/www.wambooli.com\/blog\/?p=1184"},"modified":"2010-02-09T16:28:34","modified_gmt":"2010-02-10T00:28:34","slug":"a-nerdy-post-on-programs","status":"publish","type":"post","link":"https:\/\/www.wambooli.com\/blog\/?p=1184","title":{"rendered":"A Nerdy Post on Programs"},"content":{"rendered":"

Here I go! Off the deep end! Prepare to flee in terror from this blog post, because I’m going to be talking about how programs work on a computer. Not how to work a program, but what happens when the operating system takes a program from the computer’s mass storage system and tosses that code into computer memory.
\n
\nAre you still there? Weird. I thought most people would be off to Stumble Upon<\/a> by now, playing that cool game with the little guy sliding down the lines you randomly draw. Anyway.<\/p>\n

One of the operating system’s primary duties is to run software, the programs you have installed on your computer. Like everything else, programs are stored on the computer’s mass storage system, typically the hard drive.<\/p>\n

(I’m moving away from referring to long-term computer storage as “the hard drive” or “on disk” as not all computers have disk drives these days, and in the future everything will be solid state.)<\/p>\n

The operating system takes a program from mass storage, then transfers that data \u2014 the raw program code \u2014 into the computer’s short-term storage, or memory. Once loaded into memory, the operating system then passes computer control over to that program. That’s the bare bones description.<\/p>\n

There are two types of programs in the Windows world: image and executable.<\/p>\n

An image program file is the older kind of program file that DOS used. The filename extension was COM<\/code>, but BIN<\/code> could also be used. (Though DOS wouldn’t run a BIN<\/code> file directly from the command prompt.)<\/p>\n

COM<\/code> stands for Command. BIN<\/code> for Binary.<\/p>\n

COM<\/code> files were exact images of the code, simply plopped down into memory by the operating system. After loading, the operating system passed control to the program, starting at a certain offset (100 hex) in memory. At that point, the program ran \u2014 or not, whatever the case would be.<\/p>\n

COM<\/code> programs were tiny and tight. At most they could only be 64K in size. Obviously you can see that would be an issue for any advanced program, such as, well, anything.<\/p>\n

The executable program files sported the EXE<\/code> filename extension, which stands for executable<\/em>. Unlike COM<\/code> files, EXE<\/code> files could be huge. (excel.exe<\/code> weighs in at over 19MB.)<\/p>\n

EXE<\/code> program files contain binary information, but they also contain a loader that tells the operating system where to place the program in memory. That way, the program can be laid out in larger swaths and use memory more effectively and efficiently than the older COM<\/code> programs.<\/p>\n

Today, Windows uses EXE<\/code> files as the primary program file format and filename extension.<\/p>\n

Over in the Unix world, program files are not known by their filename extension, but rather by their attributes<\/em>. That’s a whole ‘nuther worm I’ll probably write about someday when I’m feeling nerdy again!<\/p>\n","protected":false},"excerpt":{"rendered":"

Here I go! Off the deep end! Prepare to flee in terror from this blog post, because I’m going to be talking about how programs work on a computer. Not how to work a program, but what happens when the operating system takes a program from the computer’s mass storage system and tosses that code […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1184","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1184","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1184"}],"version-history":[{"count":4,"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1184\/revisions"}],"predecessor-version":[{"id":1188,"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1184\/revisions\/1188"}],"wp:attachment":[{"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1184"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1184"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wambooli.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}