Rename files

Author: jonofoz

README.md

@@ -52,4 +52,5 @@ JonOfOz
 
 ## Journals:
 
-- [Journal 1](./journals/03-20-2023.md)
+- [Journal 1](./journals/001.md)
+- [Journal 2](./journals/002.md)

journals/03-20-2023.md renamed to journals/001.md

@@ -0,0 +1,112 @@
+# 03-20-2023 - it begins!
+
+### Q0: What are we doing today?
+### A: We're going to take a shallow dive into the `ipx` folder.
+I have _absolutely zero_ intentions at this early stage to dive into any part of the game code: I just want to understand what everything does at a high level, _then_ start working my way into the details once I've got the big picture and am comfortable with the codebase.
+
+The research here will likely fit within chunk #5 as outlined in my [README](../README.md), `Network Play'.
+
+As you might have read in [Masters of Doom](https://www.amazon.com/Masters-Doom-Created-Transformed-Culture/dp/0812972155), the idea for multiplayer came about when inspiration struck John Romero, him having seen two enemy NPCs fight each other, and realizing how awesome it would be if those were _players_ instead: that idea spawned an online game made known and revered as, in Romero's own words, **"Deathmatch"**.
+
+A generation was born. LAN parties became a thing. And I'm pretty sure the code I'm about to look into is what made all of that happen.
+
+I'm super excited to start looking into this. 🤩
+
+---
+### Q1: What is the `ipx` folder?
+### A: According to the folder's [README](../ipx/README), it contains code supporting DOOM's IPX network driver.
+
+---
+### Q2: What is _IPX_ anyway?
+### A: [Internetwork Packet Exchange.](https://en.wikipedia.org/wiki/Internetwork_Packet_Exchange) I'd not heard of it until now.
+It was apparently quite popular at the time, and had a small memory footprint, making it a great fit for OS's which obviously didn't have quite the memory we have today. Unfortunately, IPX didn't scale well on large networks, and was eventually phased out and replaced by TCP/IP when the Internet really began to take off.
+
+---
+### Q3: What's in `DOOMNET.C`?
+### A: The `launchDOOM` function—likely, used to launch DOOM.
+This function seems to be called in two places:
+* `IPXSETUP.C`
+* `SERSETUP.C`
+
+(Dunno what's in either of those files yet.)
+
+At a high level, `launchDOOM` does some setup to launch DOOM or DOOM2 as appropriate.
+The file mentions things like `doomcom` (and setting its `id`), hooking in an "interrupt vector", and handling CLI arguments.
+
+A lot of this is over my head right now, and that's okay, I'll dedicate more time to the finer details later.
+
+---
+### Q4: What's in `DOOMNET.H`?
+### A: Various function and constant declarations, plus the declaration of the `doomcom` struct.
+I don't want to spend too long with this one right now, but I see some interesting things like `MAXNETNODES` and `MAXPLAYERS`, set to `8` and `4` respectively.
+
+    Man... It's so hard to believe how far technology has come since then. I can just see Carmack in his office now, typing out those humble little numbers some 30 years ago, dreaming of the days we're in now. 🙂
+
+In the `doomcom` struct, I see some members that catch my eye: `episode`, `map`, `skill`, and `deathmatch`. Others like `extratics` and `ticdup`, I'll need to revisit on a deeper dive.
+
+---
+### Q5: What's in `IPXSTR.H`?
+### A: Various string constants used throughout other files in the `ipx` folder.
+
+Not gonna spend much time here until I need to dig in to the code that uses it.
+
+---
+### Q6: What's in `IPX_FRCH.H`?
+### A: French versions of the constants in `IPXSTR.H`.
+
+I'm not immediately sure why there's just two versions, one for English and one for French, but I can always find out later.
+
+---
+### Q7: What's in `IPXNET.C`?
+### A: The IPX packet driver, and Many functions for handling various IPX network communications.
+
+A little overwhelming right now, but here's the functions inside:
+
+- `OpenSocket`
+- `CloseSocket`
+- `ListenForPacket`
+- `GetLocalAddress`
+- `InitNetwork`
+- `ShutdownNetwork`
+- `SendPacket`
+- `ShortSwap`
+- `GetPacket`
+
+Sounds like an exciting file to explore!
+
+Will continue this file tomorrow.
+
+---
+ ### 03-21-2023
+...Aaaaaaand resuming.
+
+### Q8: What's in `IPXNET.H`?
+### A: Various declarations that I don't know really what to make of.
+
+Some interesting stuff in here: there's a `packet_t` struct which contains instances of other structs, viz. `IPXPacket` and `EBC`. The former is no doubt for storing information about IPX packets; the latter, I'm assuming, has something to do with IBM's "Event (or perhaps "Entry") Control Block", a.k.a "ECB", used to represent the status of an event.
+
+Again, it's a little over my head for now.
+
+---
+### Q9: What's in `IPXSETUP.C`?
+### A: Various functions for IPX setup... just a guess.
+
+There's an `Error` function for handling "abnormal program terminations", a `LookForNodes` function which seems to have and a very curious `void interrupt NetISR` function.
+
+I'd never heard of `interrupt` before. If I had to guess, I think it was an extension of the compiler they were using at the time. Either way, [this comment on StackOverflow](https://stackoverflow.com/a/12353679/5374137) may suggest that Carmack had to combat an issue with serial port character drops on DOS at the time. The `interrupt` function isn't so commonly needed nowadays, I gather, but it's just so interesting to me to see problems programmers used to face back then and what they did to solve them.
+
+---
+### Q10: What's in `IPXSTR.H`?
+### A: Various definitions for messages to be printed out to the console.
+
+
+---
+
+And for now, that's it for the `ipx` folder! 🥳
+
+I'm so excited to dive into another part of the code and document my findings, if still only at this high level. Again, I plan on coming back to understanding to finer details, but only after I've investigated more of the code.
+
+
+**See you in the next journal!**
+
+*JonOfOz*