Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!mp2k+ From: mp2k+@andrew.cmu.edu (Michael Palmquist) Newsgroups: comp.sys.ibm.pc Subject: Re: window386 && their WORD Message-ID: <8ZxJTyi00W06E2H1B3@andrew.cmu.edu> Date: 7 Mar 90 18:50:38 GMT References: <754@eedsp.eedsp.gatech.edu> <1779@uklirb.informatik.uni-kl.de> <542@cpqhou.UUCP> <2113@milton.acs.washington.edu> , <100289@linus.UUCP> Organization: English, Carnegie Mellon, Pittsburgh, PA Lines: 39 In-Reply-To: <100289@linus.UUCP> In an earlier post, Bruce Carlson writes: "I would appreciate hearing any comments/problems that anyone has found with Word for Windows. I bought my upgrade about a week ago and at this point I'm about ready to use the 30 day return option and give it back to Microsoft." I've been using Word for Windows for a few weeks now and I'm generally happy with it. I've got a weird setup on my computer -- I'm using an XT with a Quadram 386xt (which is a lot like the Intell Inboard 386). I initially used it with the smartdrive that comes with the run-time version of MS Windows that's bundled with WFW. That worked okay, but I've found that things work much more quickly if I run the program out of a ramdrive. So I've set up an 864k ramdrive and I load the program and the two .ini files in and execute the program from there. So far, the only problems I've had is some sort of compatibility problem with the bios on my floppy disk controller (XT's can't run 1.44 drives, so you have to use either a software patch or use a controller with its own bios). I haven't figured it out yet, but other than that, it's fine. It seems about as quick as Word 4.0 on a Mac II and in general it runs about as fast as Word 5.0 did on the same machine -- and I don't have any problems updating the display or scrolling quickly through text. If I could figure out the problems I'm having with my floppies, I'd be much happier. If anyone has any ideas, I'd appreciate it. I'm using a Northgate UFDC to control a 360K and a 1.44M floppy. I've relocated the address that the bios use a few times, but the problem doesn't go away. According to Microsoft, the runtime version of windows needs four full page frames to load. It seems like I've given it that, and the program works fine as long as I just use the hard drive and the ram drive. But the program sometimes blows up when I try to read or write to the floppies. Mike Palmquist ************************ mp2k@andrew.cmu.edu Department of English Carnegie Mellon University voice: 412/268-5636