The 1.08 alpha builds were slowly trickled out as several incremental updates
over the years which makes releasing a single, easy upgrade a bit difficult.
I've tried to streamline the upgrade process from 1.07.3 to 1.08A33 as much
as possible.

1. Back up your old setup... just in case!
2. Make note of your individual node configurations along with your language
   configurations. You may need to redo these later.
3. Copy all of the included executable files to your Mystic directory,
   overwriting any existing ones. Don't forget to update the copies of MIDE
   and MPLC in your scripts directory while you're at it.
4. Run 107to108.exe and then delete it.
5. Run a31toa33.exe and then delete it.
6. Make the following additions and subtitutions to your language files. You
   usually only have one, called "default.txt" by default and located in your
   root Mystic directory. These changes are all expanded upon in whatsnew.108
   if you need/want to know more.

; Protocol list prompt &1=HotKey &2=Description
061 |14[|15|&1|14] |&2
; Protocol select prompt
062 |14Select Protocol [|15Q/Quit|14]:
145 |CR|09(R)eply to Message or (ENTER/Continue): |15
; Move message to where?
282 |CR|09Move to which base (?/List):
; Node login ACS failed
315 |CR|14You do not have access to call this node.
318 |CR|14Moving message to |15|&1|14...; Lightbar Y/N: YES text
316 |09|17Y|15Yes|09_|16  |14N|11o |16
; Lightbar Y/N: NO text
317 |14 Y|11es  |09|17Y|15No|09_|16
; Moving message. &1=base name
318 |CR|14Moving message to |15|&1|14...
; Protocol List Header
359 |CR|14Available Protocols:|CR
; NodeMsg reply &1=from &2=node#
360 |CR|09Sending reply to |&1 on node |&2:
; no history data
454 |CR|12No history data available.|CR|CR|PA
; history header
455 |CL|15Daily System History|CR|CR  Date    Calls  New    Posts  Email  DLs    DLkb       ULs    ULkb|CR|08|$D79-
; history list
; &1=date  &2=calls  &3=newusers  &4=posts  &5=emails  &6=dls  &7=dlkb
; &8=uls   &9=ulkb
456 |07|&1  |$R05|&2  |$R05|&3  |$R05|&4  |$R05|&5  |$R05|&6  |$R09|&7  |$R05|&8  |&9
; history footer &1=total days
457 |08|$D79-|CR|15* Total days: |&1|CR|CR|PA
; msg scan date prompt
458 |CR|09Enter new message scan date |01[|10|UF|01]|09: |11
; msg scan date global prompt
459 |CR|12Set this date for all bases? |11
; msg scan date: updating pointers
460 |CR|12Updating pointers: Please wait...
461 |CR|12File of this name already exists.|CR|CR|09Enter new file name (max 70 chars)|CR:
; line editor edit subject
462 |CR|09Enter new subject:
; FS editor edit subject
463 |CR|09Enter new subject:
; msgtext quote header &1=date &2=from &3=initials
464 On |&1, |&2 said the following...
; new email node msg: &1=from  &2=subj
465 You've just received new e-mail from |&1.

7. Compile your newly updated language file(s) with the new makelang.exe in
   your root Mystic directory.
8. Recompile all of your MPL scripts with the new mplc.exe file in your
   your Mystic scripts directory. pro tip: "mplc *"
9. Read through the entire whatsnew.108 file. A lot has changed since 1.07.3
   and you may not be aware of it all otherwise. I've also included a
   compiled version of the 1.07, 1.07.2, and 1.07.3 whatsnew files for
   reference as well since these changes are not in the mystic doc file.

Additional tidbits:

1. You may need to fix some of your modifications though unlike older Mystic
   updates I can't think of much that 1.08 breaks off the top of my head.
2. If Mystic, Tserver, MIS, and some other utilities crash immediately
   you may need to delete your node configuration files (node#.dat) in your
   Mystic data directory and recreate them in the configuration editor. 
3. Your default language may be corrupt. Delete it via the configuration
   editor and insert a new one to restore it to default. I hope you followed
   step 1! :)
4. MIS.EXE was intended to replace TSERVER.EXE. It includes some other
   rudimentary server daemons, such as a pop server that lets your users
   fetch their BBS email via pop3. You can configure these servers in MCFG
   though to my knowledge MIS was never completed and some of these daemons
   probably don't work well nor are they fully integrated into Mystic yet.
   The TSERVER.EXE included here was released well after MIS.EXE was first
   introduced and seems to be, from my own personal testing, the most stable
   option easily surpassing both MIS.EXE and older versions of TSERVER.EXE
   in stability.
5. Users have reported that this latest version of MYSTPACK.EXE doesn't work.
   Sorry!

Thanks all I can think of for now. Have fun!

Jack Phlash - SysOp of Distortion @ telnet://d1st.org
