Moving right along from Part IX, I advance to the later part of 1986, where I not only played with computers, but also managaed to stand watches in the Med from Jan to May, while we bombed Libya from north of the “Line of Death.” Details of that story are in the series “A Journey Into History” (Part I is here). One of the other details not previously discussed in either series, is I began “offline blogging” back in those days, as I began to write “Life Between the Catapults or What I did on My Indian Ocean Cruise.” Unfortunately, I have lost the 5 1/4″ floppies that contained my musings, but, I do recall it was a daily writing effort for while. At some point, some of those adventures will become part of the the weekly (on Wednesdays) Ropeyarn Sunday “Sea Stories” and Open Trackback postings, like the story of USS FAKEFISH.

We returned from that cruise and were tasked with some tactical R&D effort for the Tomahawk Anti-Ship Missile (TASM). Rather than retype it all here, click over to this post and see how I used the Mac 512K to take the edge off the rather extensive data reduction and report writing. It was Apple that saved the world (notice how Apple computers are prominent in so many movies these days, many of them about hi-tech stuff and svaing the world?)

Apple Mac SE

From that job, I headed to school in Newport. While enroute, I found out my sister’s company that sold lab equipment had added the Mac SE to their line, and that she would purchase one for me. I got settled in in Newport and the SE arrived. When I unboxed it and plugged it in, the supplied keyboard didn’t work. That turned out to not be a problem, as using the mouse and a Apple Menu item named “Key Caps,” I was able to click on a graphical keyboard, then select the typed text and copy and paste it. I set up the entire system, including several layers of folders using the mouse alone. A few days later, a new keyboard arrived and thigs were great.

The Mac SE was my first system with the “ADB” (Apple Desktop Bus). This was a serial interface that allowed you to “daisy chain” items, such as the mouse and keyboard and other input devices, in line. Sounds familiar? That was 1987. Now we see it in the form os the “USB” interface, but, once more, Apple enigineers were out ahead of the pack. I out the SE to good use for the later part of 1987, and into early 1988. It was very handy when doing those class papers, and I could graphically maneuver the page margins and font size to make my paper fit the magical 8 page standard. It was great if you were short on what to say, and also if you had too much to say.

We formed an Mac club and also succeeded in converting most of the local Apple ][ users group to Mac users, because we could. I tried my hand at editing a newsletter for club. I used Aldus PageMaker and one of the other page layout programs, and I learned about kerning and leading and linking columns across pages. I learned a lot more, too.

Once more, I pulled Excel out and developed two logistical problems we had to solve. It took 20 hours over the weekend, but I’m sure it would have taken much, much longer by hand. I brought it into class, and passed out the handouts. The Air Force Col, who was one of our moderators flipped through the spreadsheet and said: “I’m not going to ask any questions because you’ll probably point at one of these numbers and make me feel stupid.” Well, it was a good briefing and I have to admit I gained a lot of respect for the “loggies” as I spend the time at home trying to figure out how to get a few divisions and fighter wings, along with all their equipment loads, into Kuwait very quickly (this was in late 1987).

Next time: Mac IIs, 256 colors, 8 bit sound editing and color business cards.

Vought VE-7

1922 – Lt. Cmdr. Virgil C. Griffin, in a Vought VE-7SF makes first the takeoff from a U.S. Navy aircraft carrier, USS Langley (CV 1) anchored in York River, Va.

From the Richmond-Times Dispatch:

On Oct. 17, 1922, as the Langley lay anchored in the York River, Lt. V.C. Griffin’s Vought VE-7SF biplane took off from its deck, the first takeoff from a Navy aircraft carrier. Griffin is believed to have flown the plane back to Norfolk, where it had been loaded onto the Langley, Forrest said.

Lt. Cmdr. Griffin was attached to the “Bounty Hunters” of “Fighting Two” (VFA-2 is the present name for the squadron and it is still commissioned).

Interested in more aircraft carrier aviation history? Here’s your link.

Gee, I can’t believe I scooped SteelJaw Scribe and Far East Cynic (both CV aviation guys, but since they are VAW and not VF/VFA types), and Instapinch! I’m letting Capt Lex have a pass, since he’s doing the “I’m here from da gov’ment, and I’m here to help!” thing with forward deployed forces right now.

Part VIII is here.

In the fall of 1986, I also purchased an Apple ][gs. The short story of the acquisition is the Surface Forces, Atlantic Officer’s Wives Club had a scholarship and annually held an auction to raise money. We were *ahem* encouraged to find worthwhile items to donate for this endeavor. I did track down a few items that did make some money for the scholarship in the silent auction part of the evening and later, a ][gs went up for the main auction. I, being the hobbyist I was, lusted after the 128K of the newer version of the workhorse, the new mouse “pointing device” and it’s early graphical user interface (GUI). They brought it out and wanted to start the bidding at $900. No one raised their hand or spoke. It was a great item, but no one seemed rich enough. Finally, after much cajoling from the CNSL Chief or Staff’s wive, we began the bidding. I think someone first said $600. Anyhow, the “battle enused” and I won at $825. My evil plan was to put it in the paper and make a few dollars, as I couldn’t really afford it at the time. As I walked out to the car with my prize, one couple said they wanted it and asked if I’d take $850. I turned them down politely, and the next day put my ad in the paper.

One call came that week, and, after the initial fact finding by the caller, and I guess the attempt to see how little I’d take, I never got another call. I sold it to my sister for what I paid for it the following week. I will admit to having pulled it all out of the boxes and booting it up for a few hours, before I reboxed it for shipment.

Somewhere in this time period, I got a look at a program by Owl Software named “Guide.” I can’t find any links to it, but I saw it running on the Apple ][ series. It may have been at AppleFest in 1983 (held in Boston). Anyhow, I was intrigued for you could mark a section of text and when a user clicked on it, another document would load and be displayed. You could use it for acronyms, of more detailed info on a topic, and there seemed to be no limits to the “depth” of the linking. I thought you could generate a document coveinr all aspects of a topic, to the very minutest level of detail, yet the reader wold only have to dig in as far as necessary to make sure they followed/understood the writing. Of course, now we know this as HTML, but, if you’ve followed the series, this is my second encouter with software that used the methodolgy of the Wolrd Wide Web, years after I had seen it.

Also in this time frame, probably around early 1986, I convinced the spouse we should upgrade to a Mac, now that used ones were on the market. I do recall seeing the 1984 SuperBowl commercial for the Mac, and then kept my eye on the development, but it was too expensive. I finally found one two years later, when someone else was upgrading their system, and I bought their Mac 512K, complete with the single external 400K 3.5″ floppy.

Now, about 4.5 years into owning computers, I moved from 1Mhz (8 bit words)/48K/134K (storage) to 8Mhz (16 bit words) /512K/400K (storage) Moden spped had moved from 300 bps to 1200 bps over the same time frame.

From here I began learning about “object oriented programming” (OOP) from a program that was part of the Mac purchase (if new) or $30 if purchased separately with HyperCard ( I bought it when it came out in 1987). It allowed you to manage data and pictures and place buttons all over the background, and you could “program” on a set of cards, much like having a rolodex, and each card was a new surface to work on. Not only did you do much of the work graphically, you cold then attach code to any of the “objects” on the screen. I, once more, figured out some things I wanted to do and then figured out how to make HyperCard do it for me. I hacked up someone else’s public domain address book, and I transmogrified it so I could also keep track of who I send Christmas cards to each year, and also for the current year, where I made it print out all my mailing labels for the year I was working on them.

I also found out it was much more fun to create a “this is everything” letter for Chritmas, then I’d cut and paste each one going out, depending on how much contact I’d had with the friendd/relative that year. Ah, the magic of word processing…

Next “expose:” Retreading other serial posts, the HyperCard in Navigation and 4th Dimension helps lay out a long range project.

Sikorsky YR-4B (HNS-1) in NASA wind tunnel testing

1943 – The Navy accepts its first helicopter, a Sikorsky YR-4B (HNS-1), at Bridgeport, Conn.

Click on the picture for more history of this helo from Fiddler’s Green.

How about this for deck quals?:

H Frank Gregory, now a Lieutenant Colonel, subsequently demonstrated the XR-4 from a platform mounted on the tanker SS Bunker Hill. in May, 1943, 24 landings and take-offs being made. Additional tests were conducted in July 1943 with the XR-4, and the first YR-4A, operating from a stern platform on the troopship SS James Parker. In the course of this 20-hour test, the two helicopters made 162 landings and take-offs.

That was before they had NWP-42!

To my former shipmates from HC-6 (LCDR Al Jacka), HSL-32 (LCDR “Buzz” Buzzell) and HSL-44 (LCDR Marty ??? (age…sorry)), this one’s for you!

Part VII talked about getting ready for the deployment to the Med/North Arabian Sea.

I packed the Apple //c, the 9″ green screen monitor and the ImageWriter ][ in a footlocker (with padding) and off went. I know the computer was moved by VERTEP (vertical replenishment) (meaning it was on a pallet with other stuff, staged on a flight deck and picked up by a helicopter (usually CH-46D Sea Knights)) from a rolling, pitching deck, and deposited on another rolling, pitching deck of another ship 9 times. Yes, that’s right: NINE times.

And that little Apple “portable” kept on operating. It’s “operational availability” was 100%. We also moved a few more times by hauling the equipment down the ship’s gangways and up others a few times, too.

I had gotten reasonable proficient with the integrated suite of programs of Appleworks (which, still exists for the Mac today) because of this cruise. As the Combat Systems Material Officer, I was responsible for helping the ships stay at the highest level of readiness possible. As equipment failed, and the ship’s submitted their reports and parts requests, I was on the hook to figure out the status and keep the Commodore on the status of the repairs and parts availability. I set up a database in AW for tracking the repair parts and the estimated time the repairs would be effected.

I formatted a letter, where the body of the letter contained the current status of all casualties to the ships assigned to us. AW took care of inserting the most up to date data at printout time. All I had to do was maintain the database file when new information arrived. This sounds pretty mundane and routine for the current sate of the art of software and office suites today, but my point is in 1985, Apple had produced a very effective program to do this. I’m not sure if AppleWorks was the first of it’s kind (see the Wikipedia article linked above “one of the first”), but as far as I can recall, it was. Another milestone development, from which many other companies have gone on to “emulate” and market very well, but it was Apple software vision that most likely paved the way for all the other developments of Office software with integration.

Back in those days, Apple made the hardware and software. Years later, the software department of Apple was spun off as it’s own company, Claris. Certainly the great advantage of writing software application within the company lead to exceptionally smooth operations for the end user.

We were standing “port and starboard, chow-to-chow” watches, which meant two teams of us traded the watch when each mealtime came around. While on watch, if an update to a part status came in, I could hand annotate the info on page 1 (the casualty report status letter) of the Staff Watch Officer’s Notebook. As soon as I got off watch, I would go and make any changes, then printout a fresh copy of the letter and go back to the watch station and replace the outdated page.

The trend of my learning, documented in this series, is that I learned programs and systems more effectively and quickly when I had to face a real challenge of my management time. I then would have excellent motivation to sit down and focus on the documentation for the program I needed to get the job done.

Next time: Owl Software’s “Guide” program and stepping up to a Mac

Plenty of others have beat me too this post, but, I’m not one that likes birthdays much anyhow.

But, to the only service that has a mandate to Congress to be constantly authorized, 231 years of fine service to the Nation, at home and aboard.

Much has changed, an back in the begining, the CHENG was the Deck Deparment Head.

There were no aviators to sit in the wardroom and complain thay had seen all the movies already

There were wooden ships and “Iron Men.” We still have one of those two commodities.

Submariners were a “Navy of One.”

The Navy was a “wet” one. It took a politician many years later to make it “dry.”

Deployments could last much longer than 6-8 months.

There was no “Trade School” for officers; you learned by an apprenticeship type program.

No evaporators, so no complaining about “water hours.”

No “twidgets,” but no cool electronic gadgets, either.

Anyhow…just a few thoughts on this 231st occasion of the Birth of the US Navy.

Eagle1 posted, as did others, in rememberance of the the attack by a small boat on the USS COLE (DDG-67) in Yemen.

At Linda Sog’s blog, she has posted pictures of the 17 shipmates we lost that day.

We can take solace in knowing the USS COLE, as are all other vessels attacked in the the ramp up to the GWoT, returned to sea service and were not lost, a tribute to the crews we entrusted with these large vessels.

Moving right along from Part VI, where I chronicled my attempts to “obtain” Zenith Z-248 computers from the Supply Corps. It didn’t work….

So, now I’m about 3.5 years into owning a personal computer. In Oct 1981, I had a 1Mhz processor with 48K of RAM. BY the spring of 1985, I had moved up to a 1 Mhz processor with 64K of RAM. Wow…consider how long that was compared to now. Macs were still in my future…

Apple //c with 9″ “green screen” monitor

Anyhow, I was now moving from a fixed grey hull to the life of a nomadic “tactical DESRON” troll. The Apple //c was around
by now. I was digging throught the classified ads of the Virginian Pilot and found someone advertizing a //c and it also included a 1200 baud modem! I Watched the ad for a few days and the day after the ad went out of the paper, I called and asked if he still had the computer. Yes, was the reply. I told him I’d give him $1200 for everything. He balked, I fingered the freshly withdrawn $20s to get his attention and asked “How do I get to your house?” He gave me directions.

I picked up the //c, the modem and an ImageWriter ][ 9 pin dot matrix, serially interfaced printer. Home I went with my find and had my 300 baud modem sold shortly there after.

One of the programs that had come with the //c was “AppleWorks.” AppleWorks was a combination word processor, spreadsheet and database program, and I think it also had an intergrated communications management function. This was the fore runner of the “office suite” software packages we are so reliant on anymore. I had obviously done word processing, and had played with the very first spreadsheet, Visicalc (written to run on the Apple ][ first), and also had been doing work with dBase II in C/PM. Now I had the three functions all resident within one program, which, came in very handy later on at work.

While on this adventure, and I’m not completely clear on the dates, I was able to attend the Apple Expo in Boston. I think it was in 1983, while I was at Department Head School in Newport (yes, this part is out of sequence). I recall being fascinated with speech recognition software for the Apple ][ series. You could have 64 voice files per “library.” You would speak the command, then type in the command it would execute. You could interact with the disk operating system, so you could easily increase the “vocabulary” by using some commands to load other library files. I spoke to one of the programmers and found out Apple was employing several Ph.Ds to engineer the digitizing of speech. Part of the discussion was about how we speak in analog streams, yet we still think of speech as sets of words with “white space” between them. No so for the computer. The computer has to be powerful enough to constantly be guessing which part of the captured wave form comprises discrete words, no small task. Obviously, we have come a long way, but some of the extra money I spent on Apple products went to thier extrensive R&D efforts that brought us the first viable GUIs and many other things we now take for granted.

I can’t recall the exact circumstances, but as we geared up for the Mediterranean/North Arabian Sea cruise, one of my Apple Club friends began dabbing with the IBM PC stuff and showed me a program named R:Base 5000. It was a database manager, and you could type in english like questions and it would roll out the answers from the data tables. I got a copy and loaded it on the Z-248 the staff had gotten for administrative work. We packed up our cruise boxes and I devoted a blue and white footlocker to be the carrying case for my Apple //c computer anf the printer, so I could use them to do my work while we made the world free for democracy.

I tell the story of the cruise in the series A Journey into History.

Coming next: The Watch Officer’s Notebook and rugged computers

Sometime in late 1989, there I was, watching Marty, the valiant rotary wing aviator and Det Officer-in-Charge (OIC), and one of his boy wonders saunter past me in the centerline passageway, wearing their flight helmets, and carrying helmet bags that appeared to have helmets in them. Me, having recalled the warning to always heed the “little warning bells in the back of your head” at Prospective Executive Officer (PXO) school, I called to marty to inquire at what looked to be out of sorts.

It went something like this:

Me: “Marty, what’s in the helmet bags?”
Marty: “Oh, tapes, XO.”
Me: “Really, what kind?”
Marty: “Music cassettes.”
Me: “Why, pray tell, are you taking music cassettes up in the helo?”
Marty: “The training device in the console can also play music.”

Interesting. Never forget sailors (and officers) will always figure out the capabilities of anything you provide to them. I will admit to also being much like that as a JO. Certainly if one person doesn’t, the next one will, and the word spreads.

Me: “So, you’re gonna be cranking up the tunes while you fly your mission?”
Marty: “Sure, it gets boring up there.”

That, well not exactly the precise words, nevertheless, portray the conversation. They headed out to pre-flight and off they went into the skies over the Med, or the Persian Gulf, to head bang while conducting surface surveillance. I’m sure they were not the only crew in the fleet to figure out they had a built in stereo system to chase away the boredom while being vibrated along with several thousand other parts of the SH-60B airframe.

The epilogue to this happened a few years later, when I was inspecting Atlantic Fleet ships for Combat Systems readiness. I poked my head into the Electronic Warfare module of a DDG-38 Class ship, and pushing back the curtain, saw the Electronic Warfare On Board Trainer (EWOBT), an IBM PC system, equipped with a CD-ROM, off to the side. This computer was fielded to keep EW operators proficient by running training scenarios, complete with audio of various electronic emitters fro the CD-ROMs provided. The headset hung close by on a hook, and there was a heavy metal band music CD laying out of it’s jewel case on top of the case. Once more, being curious, I asked the EW on watch what the CD was there for. “Oh, we can play music CDs on there, too” he said without flinching, or thinking. I had had an EWOBT on my ship (same as the one discussed above with the musical helo), and had no clue the EWs were most likely playing tunes while on watch, looking very much like they were sharpening their skills as EW operators. Oh, well.

I made a point of letting the officers on the ships that the EWs might also be enjoying some entertainment on the mid-watch.

In Part V, I described some of the wonderous “cutting edge” technologies, such as a Z-80 co-processor and a 300 bps modem. I paid the bleeding edge pricing, ‘coz I wanted them.

I had left FCTCL for Dept Head School in Jan-June 83, hauling my trusty Apple ][+ along for the geobachelor thing. I kept working on th TAGG program, cleaning it up and writing the manual. AFter some extra schooling enroute, I flew south (way south, as in Chile) to catch my ride as Engineer Officer on USS CONOLLY (DD-979). The ship’s schedule was 3 more months of UNITAS, then home for Chritmas and then off to Portland, ME and 10 months in the new Bath Iron Works facility. My CO, CDR Harry Maxiner, had prepped the ship for the overhaul, by having them get as much material as possible to complete the ship’s force portion of the ROH work package, while we were on cruise. He was another man who thought way ahead. Besides being the Naval emmissaries we had been sent south to be, the work that should have been held off until early February 84, was being knocked out daily. Some readers, if you were along for that ride will recall the installation of extra flourescent lighting in the bilge areas, and the replacement of fasterners with stainless stell ones all over the ship. This project to complete the “Ship’s Force Work List” (SFWL) resulted in a few things:

We found out COMNAVSURFLANT had a pile of Z-248 computers to be issued to the ships. Having spoken to some of the shipyard and SUPSHIP people about the upcoming yard period, they indicated they had developed a computerized interface for the ROH (regular overhaul – back then every 5 years, stretched from 3) work pacakge. We could update our work for the SFWL via a computer and modem it into the SUPSHIP Offices, and we could get status on all the shipyard and other organization’s job status in return. Pretty sweet deal. I set about, when we returned from UNITAS, to convince SURFLANT Supply to give us a few of those Zenith computers. We begged, we pleaded, the CO went and knocked on doors around the various offices, but…the “Chops” were not letting us have anything. This adventure gave me my primary education on “programatics.” The computers were bought with funding justified to support an application to assist the shipboard disburing officers, and that was all they could be used for. Handing them over for ROH work package tracking was a non-starter, and would have been a violation of the expediture of public funding. I didn’t “get it” for a while, but my later years helped me comprehend this issue much better. Net result: Updates of work lists by hand…

I will say this about the Supply Corps. They didn’t just get a bunch of computers and toss them aboard ships to the DISBO. They contracted for the design, production, support and training for the life cycle of the plan. By centralizing their effort, a lot of standardiztion saved the day. That, I saw them do with programs for the Ship’s Store, the spare parts and one other area (I can’t recall exactly what it was), all were raging successes. The black shoes never had the logic wear off on them for the most of the rest of my career.

The second effect of the early completion of much of the planned work was the free time made available for the crew to train for the end of the yard inspections, in my case, the “LOE” (Light Off Exam). Captain Maxiner wanted to know whare we were in the process and I sat down, once more at the Apple ][+, armed with dBase ][ and designed and programmed an application to track the items to be done for the LOE. It was an early lesson n relational databases, but you have much more manual work to do to connect the different data tables. I would print out the report of all items daily and hang in on the side of the file cabinets forward of my desk in the Log Room. The people responsible. mostly my five division officer, would mark up the status by the end of the work day and I’d edit the progress/chnages into the computer. Each morning, the CO also got a copy, fresh as of the end of the day before. This helped keep him on top of things without coming down to the Log Room of the Engineering spaces. Not that he didn’t but he didn’t need to come nearly as often. It was a fun project, and helped a lot of us keep on top of the many individual tasks necessary to pass the LOE on the first try. The same POA&M (Plan of Action and Milestones) tracking program was filled out to get us ready for the post-ROH REFTRA (refresher training) in GTMO, where we were also going to have the OPPE (operational propulsion plant exam) Equivalent exam at the end of the 6 weeks down south. Both REFTRA and OPPE went very well, and because we could devote more time to training, and less time to paperwork.

Near the end of overhaul, the Weapons Officer, LCDR John Taylor, was being relieved. He turned over the Senior Watch Officer duty to me. This entailed managing the watch assignments for inport, and also the officers when at sea. About this time I had moved up to an Apple ][e, but was pretty much like the Apple ][+ from a performance standpoint. Using the ][e, I did another database project, where I entered the entire crew into the tables, then recorded their status for the seven major watchstanding duties: Command Duty Officer (CDO), Officer of the Deck (Inport), Petty Officer of the Watch (POOW), Duty Engineer, Duty Operations, Duty Supply and Duty Combat Systems. I also recorded their date of achievement, from their service record entries, and I had the computer assign a weighted value by paygrade. This accounted for experience. Besides just then tweaking the major qualifications portion, all we had to do, as we headed into port, was put in the desired inport section assignments. The initial printout then added up the values and gave an overview of the experience any one section had, as well as the body count. If these values were markedly different, it became an easy task to move people between the sections and balance things out. Someone asked me wahy I spent all the time writing that program, beacuse they could do it faster by hand. I told them they could the first time, but every time after that, I’d win. They got it.

During the ROH, I had the opportunity to pick up my first hard drive, the first one Apple produced. A few days ago, I found a picture of it, but, in amongst the many bookmarks I have, I can’t track it down. It held a whopping 5 megabytes of data and was about the size of a shoebox. That doesn’t seem like much, but given floppies held 134K of data, this was a huge axpansion of capability, not having to constantly dig through showboxes full of 5 1/4″ floppies to run anything. Cost (as best I recall): $1200.

I picked up my first paying job near the end of this tour, when a shipmate, who had retired, hired me to come and assist his programmers in getting their dBase ][ application up and running. I drove for 2 hours to NC, worked most of the day, had the program doing all they wanted it to do, and was paid $200 and a steak dinner. Not bad for one day of work, but it was a result of almost 3 years of creating and managing databases.

Next segment: Auctions, portable computers, SQL before it was SQL, and how to buy smart.