Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!dptg!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Use UNIX for MSDOS development?
Message-ID: <9488@chinet.chi.il.us>
Date: 4 Sep 89 19:21:25 GMT
References: <21714@cup.portal.com> <4009@internal.Apple.COM> <1649@mtunb.ATT.COM>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 33

In article <1649@mtunb.ATT.COM> dmt@mtunb.UUCP (Dave Tutelman) writes:
[Re: Lan access to source files]

>	My experience is that my UNIX environment crashes significantly
>	more often than my DOS environment.  Most (but not all) the time
>	its the access line rather than the UNIX system itself, but the
>	deffect on my work is the same. 

That's hardly going to be a problem running VP/ix from the console.

>UNIX is an excellent development environment.  But we are talking here
>SPECIFICALLY about developing software to run under MSDOS.  The LAN-based
>approach allows us to use the DOS-optimized development tools that
>Borland, Microsoft, and others provide.  It also allows us to use
>the UNIX tools when they are more appropriate.

I agree that this approach does work well, but it is more appropriate
for an environment with several users.  Vp/ix can give the same effect
to a single user at the console plus the advantage of the multiple
virtual consoles.  Serial line access is available for non-graphic
programs dos programs and they can be run from shell scripts.

>I am biased.  I work at AT&T, in the organization that develops the
>StarGROUP products.  But I'm also experienced; we use our products
>in our process, and have had successful results.

The VP/ix and DOS SERVER programs can compliment each other, but
you really should get together and agree on a netbios interface so
that file and record locking, releasing print jobs, etc. would work
properly when both methods are used to access files on the same
server.

Les Mikesell