Mail Archives: djgpp/1997/12/24/20:16:32
In article <67qh4q$i77 AT freenet-news DOT carleton DOT ca>, ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire) wrote:
>"Finn Kettner" (fk AT akf DOT dk) writes:
>[stuff]
>
>Flame me if I'm wrong, but isn't it simpler just to put a 16 bit
>pegasus.exe in some path on the 3.1 machines and a 32-bit pegasus.exe,
>same name, same path on the 95 ones, and have the login script load a
>"pegasus.exe" at that path?
I'm afraid not. The Pegasus program file is named differently in the Win
and Win32 versions, and both are typically stored in the same shared
network directory to allow many users to send messages to each other.
On the other hand, creating a batch file on each computer that points
to the appropriate version would work. A more general solution to the
problem of dupilcate Dos/Win16 and Win32 programs on the same computer
is to put the Win32 version in a directory with a long filename and
the Dos version in one without. Eg:
PATH C:\Utilities\bin;C:\BIN;%PATH%
Put the win32 (console) programs in the Utilities\bin directory and
the dos programs in the BIN directory. The Utilities directory will
only be visible as such when in Win95 or NT, but the similarly named
dos programs in BIN will show up in dos mode. I use this to organize
my unix clone command line utilities like du and zip, automatically
using ones with long filename support when appropriate.
Brian Hawley, brian DOT hawley AT bigfoot DOT com
- Raw text -