skelley@umiacs.umd.edu (Stephen Kelley) (05/21/91)
The Good News: EotB is not copy protected, installs easily on the hard disk and will run on an A3000 under 2.03 (WB 36.102) with the only caveat; you *have* to have run NOFASTRAM before starting up EotB. I clicked on the NFR tool after my system was booted and then EotB and everything worked fine. NFM should *really* be called NoMOREFastRam! I have KS and a few background tools running in the hinter regions of memory and after clicking on NFR my available chip mem stayed the same - a hefty 1.9MB. I guess this means that internal code/function calls in EotB are either time or addr. dependent whereas calls to the OS are not - odd! The Bad News: Shoot! There goes my evenings & holiday weekend into the video bit bucket (:-). OK. So where are all the EotB spoiler postings, already. Synopsis: EotB is a new (read FTL interface) role playing adventure of a (I guess) pure D&D senario. Characters must be picked from std D&D char. classes w/ std. D&D attributes & attribute ranges (eg STR 1-18.xx). The interface is straight from DM. The chars. are displayed in the same 2 modes; "face and hands" and "full body". In f&h you use weapons, potions, etc w/ the "active" hand and hold a shield or other passive generic object in the other. In fb mode you get to shuffle clothes, weapons etc around the various body "pockets". From fb mode you can see the characters attributes in detail. The play is a bit *slower* than Dm & CSB. In the "pure" D&D style of playing you have to rest to learn & memorize spells. You have to "preplan" what spells you "might" need in the next few encounter since you have to have them memorized/written before their use. Fighting is pretty much the same as DM - give your front mental slugs heavy objects and have them wail away at the monsters. Encounters are animated so you get to see slashing swords & identified (or unidentified) flying objects. (more) Hah! Next time (;-) -- =============================================================================================== Steve Kelley UMCP CS/UMIACS Internet: skelley@umiacs.umd.edu