Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!malgudi!caen!umich!vela!m.cs.uiuc.edu!wuarchive!decwrl!uunet!pmafire!dave From: dave@pmafire.inel.gov (Dave Remien) Newsgroups: comp.unix.sysv386 Subject: Re: Using MS-DOS with the UNIX* system ? Summary: WP isn't the only problem program Keywords: WP Q&A VP/IX DOSMerge Message-ID: <1991May01.023343.28432@pmafire.inel.gov> Date: 1 May 91 02:33:43 GMT References: <1991Apr26.042805.26981@chinet.chi.il.us> <1991Apr30.171445.22045@nusdecs.uucp> Distribution: wo Organization: WINCO Lines: 27 In article <1991Apr30.171445.22045@nusdecs.uucp> rwhite@nusdecs.uucp (Robert White) writes: >In article rcbarn@urc.tue.nl writes: >>I think VP/ix is not to blame for this. WP however distinguishes between >>'real' drives and 'networked' devices; it won't work properly with the latter, >>presumably just because this enables WP Corp. (why do I address those people >>politely while they cripple people's minds with their trashware) to sell >>a version capable of running in a network as a separately priced (read: more >>expensive, but actually the same) product. > >Actually there is no separate and more expensive WP for use in a network >environment. The same package is used but the netsetup program is then >run after a normal installation. The wordperfect problem under VP/ix >seems to stem from the tendency of WP to do marginally illegal things >to it's own files. > WP isn't the only offender in this behavior; we've had Symantec's Q&A mutter about being on a networked drive (under DOSMerge in the UNIX file system) just before annihilating whatever it is that's being worked on. Works OK on a DOS partition, also; same as WP. DOSMerge includes a command to switch the UNIX file system from appearing as a network drive to a local drive, but that didn't help. -- Dave Remien +*+*+*+*+*+*+*+*+*+*+*+*+*+*+ WINCO Computer Engineering Group dave@pmafire.inel.gov or rzd@inel.gov "Dave Barry for President"