Parry and Spar, or is it... Reluctant Admiral 4.2 Fulkerson(J) vs Moore (A)

[larryfulkerson]

One of my subs got some hits on a TK near Midway. Remind me to give that sub skipper a metal for attacking on the surface with so
many Allied ships around.

[larryfulkerson]

One of my AKL's shoots back at an Allied sub and gets a hit. That one shell hit on the Miyati Maru causes 1 point of sys damage.

[larryfulkerson]

The xAKL Fumi Maru #2 is showing up on the sunk ships list.......that's what he gets for sailing w/o escorts in dangerous waters.

[larryfulkerson]

Oh no.....now there's Allied subs showing up near Wake. Right in the middle of one of my major shipping lanes too.

[larryfulkerson]

My sub I-166 finds some traffic near Christmas Island I0 and gets a hit on an xAKL.

[larryfulkerson]

An air-to-ground attack SW of Kuantan revealed no Allied CAP so either there were no planes to fly CAP or Jim is saving his planes for
the defense of Singers. Or something.

[larryfulkerson]

The AVG is sweeping Hanoi but my Nates are standing down for maint.

[larryfulkerson]

Operation Beat-Down continues at Manila. Not a whole lot of damage this time either.

[larryfulkerson]

Near Rangoon Jim has given the AVG bombing missions.

[larryfulkerson]

I applaud Jim for his offensive spirit at Cebu. Allied attacks are good for morale.

[witpqs]

ORIGINAL: larryfulkerson

you are absolutely correct. Thanks for fixing my post.

EDIT: On second thought, lemme explain why I wrote it that way originally. When a programmer is writing a program from scratch for
the first time he/she usually has an idea what it's supposed to do and can plan ahead for which variables do what and what functions
are going to be needed to do what etc. And he/she can usually make a reasonably good first draft. The bugs are typos, for loop
off by one, and usually simple things that go wrong and not usually logic errors.

And then comes the need to change a program, which is sometimes a different programmer than the original author and he/she usually
doesn't have a clue what the program was written for, what it's supposed to originally do, what the variables are, what functions there
are and has to "learn" the program by trial and error.

You can tell from what I've written above how long ago I used to write programs and how much has changed since. Object orientation
came along during my later years and I had to re-learn how to program using the object oriented method, which I'm grateful for
because I learned a lot about variable isolation, "method" evolution, and so on. It was a great trip.

I'm with you, Larry! In high school I started working in IT as a computer operator during the summers. RCA Spectra 70/60 36-bit mainframes, IIRC. There were times when we had to patiently explain to a newly hired programmer that a card reader (roughly the size and shape of two and a half washing machines side by side) could not be written to as it was a read-only device. Showing them usually helped, including lifting the cover to reveal the movements (and lack of any punch mechanisms).

[larryfulkerson]

ORIGINAL: witpqs
I'm with you, Larry! In high school I started working in IT as a computer operator during the summers. RCA Spectra 70/60 36-bit mainframes, IIRC. There were times when we had to patiently explain to a newly hired programmer that a card reader (roughly the size and shape of two and a half washing machines side by side) could not be written to as it was a read-only device. Showing them usually helped, including lifting the cover to reveal the movements (and lack of any punch mechanisms).

I remember card readers. In 1968 I took a class in Fortran and I remember "printing" out about 1K blank cards to use as bookmarks and
scratch paper. There weren't any yellow stickies back then. Writing and reading from a hard drive came later and cards were retired.

Anybody remember ALC? Assembly Language Code ( IBM 360/1400 ) for the mainframe? I used to have to write / modify programs
using ALC for a three-letter organization that shall not be named. I remember waking up in the morning and I couldn't wait to get to work
because it was so interesting. I'd work overtime for free if they would let me. But they never would......against union rules.

[moore4807]

ORIGINAL: witpqs

ORIGINAL: larryfulkerson

you are absolutely correct. Thanks for fixing my post.

EDIT: On second thought, lemme explain why I wrote it that way originally. When a programmer is writing a program from scratch for
the first time he/she usually has an idea what it's supposed to do and can plan ahead for which variables do what and what functions
are going to be needed to do what etc. And he/she can usually make a reasonably good first draft. The bugs are typos, for loop
off by one, and usually simple things that go wrong and not usually logic errors.

And then comes the need to change a program, which is sometimes a different programmer than the original author and he/she usually
doesn't have a clue what the program was written for, what it's supposed to originally do, what the variables are, what functions there
are and has to "learn" the program by trial and error.

You can tell from what I've written above how long ago I used to write programs and how much has changed since. Object orientation
came along during my later years and I had to re-learn how to program using the object oriented method, which I'm grateful for
because I learned a lot about variable isolation, "method" evolution, and so on. It was a great trip.

I'm with you, Larry! In high school I started working in IT as a computer operator during the summers. RCA Spectra 70/60 36-bit mainframes, IIRC. There were times when we had to patiently explain to a newly hired programmer that a card reader (roughly the size and shape of two and a half washing machines side by side) could not be written to as it was a read-only device. Showing them usually helped, including lifting the cover to reveal the movements (and lack of any punch mechanisms).

Memories!
My geekdom started after High school, I joined an ambulance squad and one of the guys there was the son of a IBM engineer. You want to talk smart? Mike was building computers and writing code in his bedroom - he had tech manuals lining one wall bookshelf. Mike did NOT have the geek look, but when he opened his mouth...

He sold me a TRS-80 he had laying around (greenscreen version) because we played a Dungeons & Dragons type game. You had to actually write in BASIC code what movement/action you wanted to do and then waited for the result, then typed another line of code to react to that... Definitely cool to a noob! I actually set the computer up in my apartment and we played over the phone (really WOWl at the time). Mike even made a "box" that emulated a phone connection and up to four people could play the game at one time. It was definitely before routers were mainstream.

Around 1988 Mike got offered a job in Northern NJ working for Bell Atlantic/Verizon. He went and I still played him over the phone (til the long distance bill came in!) One afternoon a thunderstorm rolled through, I'm sitting on my bed watching TV and the apt building got hit by lightning. The Trash 80 and the small TV both went at least a foot in the air - fire is blowing out of the back of the TRS-80, its laying on the floor with green and orange flames shooting up. Being a smartass fireman, I quickly jumped up and unplugged the cord... well I tried anyway, the plastic was melted into the wall socket and burned my hand on the white hot cord. My fire company was called by my neighbor, they had to put out the fire on the side of the house where the electric service came into the building, and I lost all my electronics "stuff" (uninsured of course!). It was around 6 more years before I could afford to buy a real computer and I first bought Gateways then started building my own computers every two years after and "reverse engineering" (Mike's term) the old ones!

I lost contact with Mike around 15 years ago - he was already some big wig in a private business telephone company that specialized in scrambled signals (or some sort). I'll never forget the memories though. Game on til dawn was the motto!

[larryfulkerson]

Cool story. Keep 'em coming. I had an Atari 800 XL and wrote assembly code on it. Remember 8-bit? It had the same CPU as the Commodore 64 and would run on either of them. I remember a magazine that published code for programs. This was back in the 1980's.

Remember the PC program "Debug"? A poor-man's assembler. I played around with that a lot.

Here's an ALC program to write "hello world" on your screen:

Code: Select all

 HELLO    CSECT               The name of this program is 'HELLO'
 *                            Register 15 points here on entry from Op/sys or caller.
          STM   14,12,12(13)  Save registers 14,15,and 0 thru 12 in callers Save area
          LR    12,15         Set up base register with programs entry point address       
          USING *,12          Tell assembler what register we are using for pgm. base
          LA    15,SAVE       Now Point at our own save area
          ST    15,8(13)      Set forward chain
          ST    13,4(15)      Set back chain               
          LR    13,15         Set R13 to address of new save area
 *                            -end of housekeeping (similar for most programs) -
          WTO   'Hello World' Write To Operator  (Operating System macro)
 *
          L     13,4(13)      restore address to caller-provided save area                     
          LM    14,12,12(13)  Restore registers as on entry
          SR    15,15         Set register 15 to 0 so that the return code (R15) is Zero
          BR    14            Return to caller
 *           
 SAVE     DS    18F           Define 18 fullwords to save calling program registers 
          END  HELLO          This is the end of the program         
 

[larryfulkerson]

Here's a list of the cities with the most oil to ship to the home islands.

[larryfulkerson]

Here's where all the Resources are to ship to the home islands:

[larryfulkerson]

Did I happen to mention that I had the 114th INF Rgt headed for Singkawang? It'll be there in a couple of days.

[larryfulkerson]

Here's a display of the ships that were damaged by the Allied guns at Cebu and the extend of the damage. But I really needed to
deliver some supplies to the troops there so the war could continue.

[moore4807]

ORIGINAL: larryfulkerson

Here's a display of the ships that were damaged by the Allied guns at Cebu and the extend of the damage. But I really needed to
deliver some supplies to the troops there so the war could continue.

Larry, from the look of the zeros after capacity - you were successful in dropping over +15K worth of supply on Cebu. . . without counting the two damaged ships capacity in. Nice Job.

[moore4807]

AFTER ACTION REPORTS FOR Jan 25, 42
--------------------------------------------------------------------------------

Sort of a mixed bag here, not a lot of action and setting up some more "surprises" for Larry. . .

Sub attack near Johnston Island at 164,112
Japanese Ships
SS I-173

Allied Ships
AS Pelias
DD Jarvis

See, I don't leave EVERYTHING unescorted!!!

ASW attack near San Diego at 226,80
Japanese Ships
SS I-25

Allied Ships
YP-197
YP-343


THREE ASW patrols in this hex and I still can't stop another sinking. . . breathe, hold, exhale, repeat. . .

Submarine attack near Midway Island at 160,90
Japanese Ships
SS I-9

Allied Ships
TK Pat Doheny, Shell hits 7, Torpedo hits 4, heavy fires, heavy damage



Plucky bahsterd, an xAKL vs sub shouldnt have been a fair fight.

Submarine attack near Truk at 110,111
Japanese Ships
xAKL Miyati Maru, Shell hits 1

Allied Ships
SS Swordfish, hits 1, on fire


Now THATS more like it!

Submarine attack near Muntok at 51,89
Japanese Ships
xAKL Fumi Maru #2, Torpedo hits 2, heavy damage

Allied Ships
SS KXIII


What my feeble mind cannot remember is, are these the batteries unloaded from the beginning of the game, or were they already there?, Either way 3 hits on nine shots is nice shootin Tex!

Invasion Support action off Cebu (80,86)
Defensive Guns engage approaching landing force
9 Coastal gun shots fired in defense.

Japanese Ships
xAK Mito Maru, Shell hits 3, on fire
xAK Karachi Maru
xAK Argun Maru
xAP Hakozaki Maru

155mm M1918 GPF Battery engaging xAK Mito Maru at 5,000 yards
155mm M1918 GPF Battery engaging xAK Mito Maru at 5,000 yards
155mm M1918 GPF Battery engaging xAK Mito Maru at 5,000 yards
xAK Karachi Maru fired at enemy troops
xAK Argun Maru fired at enemy troops
xAP Hakozaki Maru fired at enemy troops


Invasion Support action off Cebu (80,86)
Defensive Guns engage approaching landing force
9 Coastal gun shots fired in defense.

Japanese Ships
xAK Mito Maru, on fire
xAK Argun Maru, Shell hits 1, on fire
xAK Karachi Maru
xAP Hakozaki Maru


Various ASW/Sub attacks around the Pacific, no damage done to either side. . .

ASW attack near Kochi at 107,62
Japanese Ships
DD Makigumo
Allied Ships
SS Spearfish

Submarine attack near Wake Island at 131,95
Japanese Ships
xAK Matsue Maru
Allied Ships
SS Cachalot

ASW attack near Johnston Island at 164,112
Japanese Ships
SS I-173
Allied Ships
DD Jarvis

Sub attack near Midway Island at 158,91
Japanese Ships
SS I-9
Allied Ships
AO Cuyama

ASW attack near Kochi at 106,63
Japanese Ships
DD Hatsushima
Allied Ships
SS Porpoise

ASW attack near Molokai at 180,110
Japanese Ships
SS I-23
Allied Ships
DMS Boggs

More grandiose announcements from Orphan Annie on Radio Tokyo tonight!
Japanese forces CAPTURE Bima !!!
Japanese forces CAPTURE Roti !!!