rodrigol@ulrik.uio.no (Rodrigo Lopez) (07/04/90)
I'm new to this conferebce so please ignore my faults. I've been watching this newgroup for some time and enjoyed very much its content. I got WIndows 3.0 about 2 weeks ago and...boy does its feel right! But, I'm having some problems trying to get our Pc-Nfs network to survive windows 3.0 in 386 enhanced mode. The network software behaves very well in standard mode, but as soon as I run win/3 the network dies. Maybe I should describe our system in short: Mitac 2386 (386sx), 5 Mb Ram, Paradise VGA, EtherLink II TP, 2 x serial, ...and the rest you all know. I managed to get Pc-Nfs to work nicely under Windows/386, so I can't see what the problem may be. Another matter I would like to know about is the availability of Windows 3.0 drivers for the Paradise VGA Plus Card 800x600. The drivers that came with the machines work in Standard mode but the scroll bars, push boxes (the whole of the new windows look goes away), are displayed in good old windows 2.x fashion. Reply as follow up or to: rodrigol@ulrik.uio.no Thank you all very much!
pilger@uhunix1.uhcc.Hawaii.Edu (Eric Pilger) (09/05/90)
So far, PC-NFS and Windows 3.0 work fairly well together. One strange thing that has happened (occassionally) is that after finding all the applications on a network disk during an installation, the control panel just aborts. No error messages, it's as if I simply hit <cancel>. This happens just after it's found all the applications, and before I get a chance to pick the ones I want. Anybody have a clue to this odd behavior? In a second, possibly unrelated issue. Has anyway seen any instances of Word for Windows garbaging large files. I have someone attempting to edit a 40+ page document. Things will go fine for a few days them, wham! No more useable document. The junking ususally occurs near the end of the file. This is all on a 286, and with a fairly naive user. I can't guarentee he isn't doing something crazy, but it doesn't speak well for the robustness of Word for Windows. Thanks in advance for any help. Eric Pilger NASA Infrared Telescope Facility
CC65SRAD@MIAMIU.BITNET (09/10/90)
Eric, I have beed using Word for Windows for quite some time, and have edited some large files. The problem may lie in the fact that Windows is VERY straining on a hard disk. It is a good practice to run CHKDSK /F every time you start the machine, and to use a program like Disk Doctor often, as well as a disk compression program at regular intervals. I added CHKDSK to my AUTOEXEC.BAT file, and perform a Disk Test and compression as part of my bi-weekly backup routine. Windows pushes a 286 system to its limits, I'm sure, and the only way to prevent failures is to practice good system management straight from the textbooks. -Chris