DiabloBackup BETA FAQ: (by Kevin Lambert)

*****************************************
 LAST UPDATE - Monday, February 9, 1998 (see the last paragraph)
*****************************************

 Go to http://www.users.lith.com/~kevin/diablo/
 for the latest DiabloBackup BETA FAQ.


NOTE: if you see a bug in version 2.0 Beta 3, it is safe to assume that 
the bug was present in all version 2.0 Beta 2, and 2.0 Beta 1... 
You get the idea... :)

Bugs & fixes in version 2.0 Beta 1:
----------------------------------
Bug 1) The "Click here to see your computer name" button does not work.
Bug 2) If you transfer characters to a machine that has never had any
     multiplayer characters, you get a "Registry Error"

Bugs & fixes in version 2.0 Beta 2:
----------------------------------
Fix 1) Bug #1 from beta 1 was fixed
Fix 2) Bug #2 from beta 1 was fixed
Bug 1) If you transfer a character from a Windows95 machine to another
     Windows95 machine and you let DiabloBackup delete the character
     from the first machine after transferring that character to the
     floppy disk, DiabloBackup will delete the character in slot 0
     regardless of what character you transferred.  (To be safe using beta
     1 and beta 2, just say "NO" when DiabloBackup asks you to delete the
     character(s) after the transfer... Any other machine to machine
     transfer does not have this problem)

Bugs & fixes in version 2.0 Beta 3:
----------------------------------
Fix 1) Bug #1 from beta 2 was fixed
Bug 1) If you try to transfer a single player to a multiplayer character,
     and the single player character has a space anywhere in his/her
     name, Diablo will crash when you try to restore it.
Bug 2) Some people have reported that when they try to transfer characters
     from one machine to another, DiabloBackup tries to put every
     character in slot 1 on the destination machine. Only some people
     have experienced this, and I "think" I have it fixed in beta 4...
     If not, please let me know... :)

Bugs & fixes in version 2.0 Beta 4:
----------------------------------
Fix 1) Bug #1 from beta 3 was fixed. (Well, DiabloBackup now warns you
     that Diablo will crash if you restore a character with a space in the
     name.)
Fix 2) Bug #2 from beta 3 was fixed, I think... Since I could never 
     reproduce this bug on my machine, all I can go by is the word of two
     people who had the problem with beta 3 but not with beta 4, and no
     word to thecontrary... (yet) :-)
Bug 1) I'm not sure this is a bug in the program... When you transfer a
     single player character to a multiplayer, some of the items get
     changed into other items.  This may simply be a result of the
     difference in the ways that items are identified in single player
     game and a multiplayer game. If you ever come across a program that
     can transfer single player characters to multiplayer characters
     perfectly in a case where DiabloBackup fails, please let me know.
     Until then, I will assume that it is just a consequence of being
     able to transfer a single player character to multiplayer.
Bug 2) Sigh... this is a tough one... It seems that there is some kind of
     additional machine-specific info stored in the save game files
     other than the name of the computer.  This seems to affect about 2
     percent of all the people who have used DiabloBackup to transfer
     characters from one machine to another.  Since I cannot personally
     reproduce this bug on any of my machines, it is going to be REALLY
     tough to fix.  The good news about this bug is that your character
     will transfer successfully.  The bad news is that any equipment the
     character had will be lost.
Bug 3) When transferring a single player character to multiplayer
     character, sometimes you will get a "Unable to determine which
     character was loaded in Diablo" error message. (fixed in beta 5)
Bug 4) When doing a Windows95 to Windows95 machine transfer, sometimes the
     last item in the character's belt gets messed up. (fixed in beta 5)

Bugs & fixes in version 2.0 Beta 5:
----------------------------------
Fix 1) Bug #3 from beta 4 was fixed.
Fix 2) Bug #4 from beta 4 was fixed.
Note: I am now positive that bug #1 from beta 4 is due to the fact that
     items are handled differently in a single player game than a 
     multiplayer game. If you transfer a single player character to a
     multiplayer character or vice-versa, some items will get messed up
     because of this, and nothing can be done about it. (sorry) :-(
Note: Still haven't fixed bug #2 from beta 4... Hopefully I'll figure
     it out sometime. :)

Bugs & fixes in version 2.0 Beta 6:
----------------------------------
Note: This version works with the new Blizzard patch. I have disabled the
     sections that don't work, and I will address them in the next version
     of DiabloBackup. Thanks for your patience!
Note: I took out all those annoying beta reminders, but this version will
     expire at the end of March, 1997. If you get a message saying your
     version has expired, then the date on your computer is incorrectly
     set... please don't e-mail me and ask me why you're getting that
     message! (I got at least 50 messages on the last one) :-)
Note: The only features that were disabled in this version of DiabloBackup
     were transferring single player characters to multiplayer characters,
     (and vice-versa), and transferring characters from one Windows95 
     machine to another Windows95 machine.

Bugs & fixes in version 2.0 Beta 7:
----------------------------------
NOTE: THIS VERSION EXPIRES AT THE END OF MARCH.  If you are getting a
     message saying that it has expired, then the date on your computer
     is set incorrectly!
Note: This version works with the new Blizzard patch... Due to numerous
     requests, I re-enabled the features that I had disabled in version 
     beta 6, but I added a warning that those features only work with the
     original version of Diablo. (You can reinstall Diablo from the CD to
     get the original version of Diablo, then you can use those features
     in DiabloBackup, then upgrade Diablo again, and everything will work
     fine)
Bugs: Not really a bug, but the only two features that do not yet work
     with Diablo v1.02 are transferring characters from one Win95 machine
     to another Win95 machine (with different computer names), and
     transferring a single player character to multiplayer and vice-versa.
     Hopefully I will get these working in future versions of 
     DiabloBackup.

Bugs & fixes in version 2.0 Beta 8:
----------------------------------
Note: Due to numerous requests, I have taken out the exiration feature and
     replaced it with a monthly reminder to check my page for a new
     version... don't worry, you will only have to see it once a month. :)
Note: Other than the expiration notice, beta 8 is essentially the same
     as beta 7.  Hopefully I will have the Win95 to Win95 machine transfer
     feature solved soon so I can release DiabloBackup 2.0 final :)  As
     for the single player to multiplayer (and vice versa) feature, if
     I can't solve that problem when I get the Win95 to Win95 transfer
     feature solved, then I will remove that capability from DiabloBackup
     and create a stand alone program that only works with Diablo v1.0 to
     transfer single player characters to multiplayer and vice versa.

Bugs & fixes in version 2.0 Beta 9:
----------------------------------
Bugs: People who have the problem listed in question 21 in the
     DiabloBackup FAQ who already have their characters backed up don't
     need to follow the entire "Transferring characters" procedure.  I
     added instructions in the DiabloBackup FAQ (see question #21) and made
     it more clear in DiabloBackup version 2.0b10.

Bugs & fixes in version 2.0 Beta 10:
-----------------------------------
Bug 1) When transferring characters from one machine to another,
     DiabloBackup can only launch Diablo in the special mode once and then
     DiabloBackup has to exit.  For this reason, you need to be sure that only
     one character is in your backup directory at a time when you perform
     the transfer procedure, and as soon as you successfully transfer that
     character, you need to exit DiabloBackup.  If you need to transfer more
     than one character, just make sure that the character that you want to
     transfer is in a directory all by itself and run DiabloBackup again and
     repeat the process.
NOTE: A backup/transfer character consists of a .drv file and a .bin file.
     If you are going to be copying and moving character files around, make
     sure that you get BOTH of these files!

Bugs & fixes in version 3.0 Beta 1:
----------------------------------
Fix 1) Bug #1 from version 2.0 Beta 10 was kinda fixed. :-)  Basically
     I made it so that DiabloBackup only lets you transfer one character at
     a time, and DiabloBackup only launches Diablo in the special mode
     once and then exits. (Don't worry, it will all be explained if you
     use that feature in DiabloBackup)
Bug 1) When DiabloBackup launched Hellfire, it doesn't set the current
     directory to the hellfire directory.  Therefore, if Hellfire needs
     to search for a command.txt or another file, it won't find it unless
     you run DiabloBackup from your Hellfire directory... (this is a minor
     bug... just get v3.0b2 and shaddup)  :-)

Bugs & fixes in version 3.0 Beta 2:
----------------------------------
Fix 1) Bug #1 from v3.0b1 was fixed.