Tuesday July 20th, 2004:

Not much new.  As before, overwrite the existing GameSrv.mdb and see ChangeLog.txt
to see what's new.  I'll work on the upgrade process for the next version so you
shouldn't have to overwrite GameSrv.mdb again.  I'll also include an import tool
so you can upgrade from the last version (if you're running it).



Sunday July 11th, 2004:

You'll have to overwrite your existing GameSrv.mdb with the new one.  Once
the final version is out I'll make sure there is an automatic upgrade process,
but for now the only process is to overwrite what you've got (which is why I
said it's probably not a good idea to use this in a production environment).

Read ChangeLog.txt to see what's new.



Sunday July 4th, 2004:

Well, I had a power outtage here so I didn't get as much done as I wanted
tonight.  So here's what you should test and expect to work:

- Connecting via both Telnet and RLogin
- RLogin connections should only be accepted from hosts in RLoginHostTbl
- These "Actions" are available in the MenuTbl table:
  - DISPLAY_FILE ("Parameters" = file to display)
  - EXEC ("Parameters" = door to run - use this for Door32 doors)
  - EXEC_MSYNCFOS (like EXEC, but for DOS doors using mSyncFos)
  - EXEC_NETFOSS (like EXEC_MSYNCFOS, but uses NetFoss)
  - GOTO_MENU ("Parameters" = menu to change to)
  - LOGOFF (no "Parameters" required)
- These "Actions" are available in the LogonProcessTbl table:
  - LOGOFF (no "Parameters" required)
  - LOGON (no "Parameters" required - prompts user for username/password)
  - MAINMENU (no "Parameters" required - sends user to main menu)
- In the LogonProcessTbl table, the StepNumber is used to define the order
  that the actions are done in.  Lower number runs first.  Not recommended
  to ever use equal numbers since order is undefined then.
- User #1 in the UserTbl is the "template" user...new users will have the
  same settings as this user (so far only the AccessLevel is applied to
  new users).  Feel free to change it's settings, but do not delete it!
- In order to create a relationship between the UserTbl and RLoginHostTbl,
  even non-RLogin users need to be associated with a RLoginHostTBl record.
  So RLoginHost #1 is the TELNET host.  It's best to leave this host alone,
  but changing the settings shouldn't hurt anything.  Definitely do not
  delete it though.
- For EXEC* commands, the following MCI's are available (and will probably
  be changing):
  - *D1 = full path\filename to DOOR32.SYS
  - *D2 = full path\filename to DOOR.SYS
  - *D3 = full path\filename to DORINFO1.DEF
  - *H = socket handle
  - *N = node number

And here is what you shouldn't expect to work:

- In the ConfigTbl table, these settings don't do much yet:
  - DoorVisibility (for now, all doors run minimized)
  - RLoginUserName (RLogin connections still go through the login process)
  - VerifyEmail (the SMTP stuff isn't done yet so emails cant be sent)
- The main thing I wanted to finish tonight but didn't was the user stuff.
  So in this ALPHA, even though users can create new accounts, that information
  isn't used.  Every user in the system will be seen as the same person in the
  doors.  Hopefully next weekend I'll have a new ALPHA with the user settings
  working.
- ANSI menus don't work either.  For now you're stuck with the canned menus.


Okay, so these docs suck and I'm sure I left a lot of stuff out.  If you have
any problems, head to http://www.randm.ca/forum/index.php and post a message
in the GameSrv forum.  That's probably a better choice than email since a
public discussion of bugs / suggestions / etc can be had.