Re: Using XyWrite with XP OS

["Patricia M. Godfrey" PriscaMG@xxxxxxxx]

Harry wrote:
≪some setting I did for the DOS .pif or .lnk (or whatever it is).≫
The following posts from Robert Holmgren on the dates specified may help
straighten out (once and for all) the diferences between LNKs and PIFs:
Mar 22 2004
≪I don't use a PIF in XP; I use a LNK. You get that by setting the
shortcut to:
 cmd.exe /c d:\path\editor.exe
instead of just plain
 d:\path\editor.exe
Try it.≫

Mar 24 2004
≪if you have a PIF, and you add "CMD.EXE /C " in front of the program
entry, you're essentially tricking the system into running what should
be a LNK as a PIF. Then when you delete CMD.EXE, you're tricking the
trick.≫

25 Jul 2005
≪NTVDM.EXE is the DOS subsystem. CMD.EXE is the default *command
processor* (but can use COMMAND.COM too, and if you just say
"EDITOR.EXE" in the shortcut, the system will automatically choose
COMMAND.COM as your command processor); CMD isn't "DOS itself" -- NTVDM
is. PIFs are used by COMMAND.COM, LNKs by CMD.EXE. You can *force*
Editor to use CMD.EXE, if you want. However, you have more control over
things that matter to XyWrite, such as memory settings, if you stick
with COMMAND.COM ≫
Query: when you say, "if you have a PIF, and you add "CMD.EXE /C " in
front of the program entry, you're essentially tricking the system into
running what should be a LNK as a PIF" don't you mean "tricking the
system into running a PIF as a LNK"?
One thing I would add on my own is that one should have a SEPARATE
shortcut (whether PIF or LNK) for Xy, not simply launch it from an MSDOS
prompt (9x) or CMD prompt (NT-builds). That way you can set its own
properties, independent of those of any other DOS apps.

Patricia M. Godfrey