Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!uhccux!uhunix1.uhcc.Hawaii.Edu!todd From: todd@uhunix1.uhcc.Hawaii.Edu (Todd Ogasawara) Newsgroups: comp.windows.ms Subject: Re: WFW Default Directory Message-ID: <10885@uhccux.uhcc.Hawaii.Edu> Date: 10 Jan 91 07:46:28 GMT References: <90362.151544YTHPRGDB@MTUS5.BITNET> <2770008@hparc0.HP.COM> Sender: news@uhccux.uhcc.Hawaii.Edu Organization: University of Hawaii Lines: 45 In article <2770008@hparc0.HP.COM> dak@hparc0.HP.COM (Dave Kruger) writes: >/ hparc0:comp.windows.ms / / 7:15 am Dec 29, 1990 / >> Is there any way to change the WFW default document directory? I want >> documents to automatically go into the C:\DOCUMENT directory. > >This seems convoluted to me (especially if, as someone else has mentioned, a >simple "ChDir C:\DOCUMENT" statement in the AutoExec macro works), but I use it >and it works well. Thanks to the kind person who suggested it. Umm.. I think that was me.. And, you're very welcome... >STICK THE BOOTS IN FLAG: ON > >I can guess what the above commands do, but don't know for sure. To know this, >I would have to buy the "Microsoft Word for Windows Technical Reference". If >*that* book is as atrocious as the rest of the W4W documentation (and Microsoft >documentation in general) it would be a great waste of money. Fair Dinkum, >I've never seen such hopeless documentation as that which comes with W4W. I just have to add my two cents to this... I've complained about this before.. but what the heck... I upgraded from Word 5.0 to WfW windows the day I received the upgrade notice. When I received my upgrade package, I was disgusted to find that Microsoft had unbundled the hardcopy macro language reference guide (I much later found that they did include a file with the macro reference guide contents in it though) and wanted another $22.95 for it (why didn't they just have that option on the original upgrade form????). Worse, when I recieved the macro language manual (a poorly photocopied set of pages in a three ring binder), it was nearly useless. While it listed all the commands, it had very few examples of the functions/commands unique to WordBASIC. I have never become comfortable with WordBASIC and am dead-certain I am not even coming close to using WfW to its fullest potential. This is a shame since WordBASIC appears to be a powerful tool but I just can't spend the time going through the gawd-awful reference manual that Microsoft provided me. Heck, GNU EMACS Lisp is easier to figure out and use than WordBASIC (given the documentation Microsoft provides)....todd -- Todd Ogasawara, U. of Hawaii UUCP: {uunet,ucbvax,dcdwest}!ucsd!nosc!uhunix!todd BITNET: todd@uhunix INTERNET: todd@uhunix.UHCC.HAWAII.EDU