rk@bigbroth.UUCP (rohan kelley) (08/27/89)
We're running Dell (interactive 3.2) unix on a dell 310. We can't get
wp5.0 to run although 4.2 runs ok, including library. Is anyone out
there successfully running this configuration with wp5.0?
thanx
=======================================================================
Rohan Kelley -- UNIleX Systems, Inc. (Systems and software for lawyers)
UUCP: ...{gatech!uflorida,ucf-cs}!novavax!bigbroth!rk (office)
novavax!mdlbrotr!rk (home)
ATTmail: attmail!bigbroth!rk
3365 Galt Ocean Drive, Ft. Lauderdale, FL 33308 Phone: (305) 563-1504
"Go first class or your heirs will" -somebodyelse
=======================================================================les@chinet.chi.il.us (Leslie Mikesell) (09/03/89)
In article <597@bigbroth.UUCP> rk@bigbroth.UUCP (rohan kelley) writes: >We're running Dell (interactive 3.2) unix on a dell 310. We can't get >wp5.0 to run although 4.2 runs ok, including library. Is anyone out >there successfully running this configuration with wp5.0? I got it working under AT&T 3.2 by putting it on a DOS partition on the hard disk - it has no problems accessing data files in the unix filesystem. It will probably also work if you install it on the VP/ix C: drive or set up another similar virtual disk. The problem appears to with VP/ix file locking, since the files are handled individually in the unix file system but the floppies and DOS hard disk partitions are given to the first user that grabs them. Of course only one user can run WP and in only one session unless you make other copies. I don't see why VP/ix doesn't provide a real netbios interface to each DOS session. It certainly isn't usable as a multi-user platform without it. The funny thing is that this same 386 machine is running AT&T's STARLAN DOS SERVER and has no problem providing netbios services for its client machines including file locking and unlocking, it just can't do it for itself with VP/ix. On the other hand, WP is probably just getting a different error code back from the open to indicate that the file is read-only and could just as well ignore it (it doesn't mind being loaded from read-only network drives). Les Mikesell
tneff@bfmny0.UUCP (Tom Neff) (09/03/89)
In article <9476@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes: >I got [WP 5.0] working under AT&T 3.2 by putting it on a DOS partition on >the hard disk - it has no problems accessing data files in the >unix filesystem. It will probably also work if you install it on >the VP/ix C: drive or set up another similar virtual disk. This usually indicates that the program is trying to do sector or FAT operations on a "drive" that is really the UNIX filesystem, disguised by REDIR. VP/ix will let you do any file operation you like on a redirected file, but when you start to peek underneath the rug you blow up. I had this problem with some Intel translator tools that were defaulting :WORK: to the current drive and directory. In some cases the solution can be as simple as putting a "C:" drive change command in your WORD.BAT file, to change the current drive and directory over to something DOS sector operations work on (a pseudodrive or mapped DOS partition) before invoking WORD.COM itself. > The >problem appears to with VP/ix file locking, since the files are >handled individually in the unix file system but the floppies and >DOS hard disk partitions are given to the first user that grabs >them. Of course only one user can run WP and in only one session >unless you make other copies. No, VP/ix gives the first requester Read/Write access and all subsequent requesters Read/Only access, except for serial ports. If you run into this, Word should complain about a write protected drive. -- Annex Canada now! We need the room, \) Tom Neff and who's going to stop us. (\ tneff@bfmny0.UU.NET
les@chinet.chi.il.us (Leslie Mikesell) (09/04/89)
In article <14623@bfmny0.UUCP> tneff@bfmny0.UU.NET (Tom Neff) writes: >>I got [WP 5.0] working under AT&T 3.2 by putting it on a DOS partition on >>the hard disk - it has no problems accessing data files in the >>unix filesystem. It will probably also work if you install it on >>the VP/ix C: drive or set up another similar virtual disk. >This usually indicates that the program is trying to do sector or FAT >operations on a "drive" that is really the UNIX filesystem, disguised by >REDIR. VP/ix will let you do any file operation you like on a >redirected file, but when you start to peek underneath the rug you blow >up. In this case I doubt it - the same program runs just fine using the starlan DOS file server and accessing the directory on the unix machine from from another PC. Unless WP acts differently when it thinks it is on a network and VP/ix doesn't "appear" to be a network drive. I'm using the network version and it always asks what type of network it is on, which indicates that it doesn't recognize it. >> The >>problem appears to with VP/ix file locking, since the files are >>handled individually in the unix file system but the floppies and >>DOS hard disk partitions are given to the first user that grabs >>them. Of course only one user can run WP and in only one session >>unless you make other copies. >No, VP/ix gives the first requester Read/Write access and all subsequent >requesters Read/Only access, except for serial ports. If you run into >this, Word should complain about a write protected drive. ^^^ Make that WP5.0. But using the network to access the program directory from a DOS machine, WP is perfectly happy with seeing a write protected drive and/or read-only files. However under VP/ix it won't load at all directly from the unix file system and only lets one user/session load it from the DOS drive. Les Mikesell