Hi group,

Is there a way to create a program interface file (.pif) on Windows 2000?
Thanks.

BobS

In microsoft.public.win2000.cmdprompt.admin BobS wrote:

> Hi group,
>
> Is there a way to create a program interface file (.pif) on
> Windows 2000? Thanks.

Assuming you mean from a CLI, most shortcut (LNK) creation methods
work fine by just specifying .PIF and the 16-bit executable. However
none of the PIF-sepific properties can be set this way with tools
such as shortcut.exe. Not certain that helps any.

Hi Mark,

Thanks for the response. CLI or otherwise, doesn't matter. Unfortunately,
it is the pif specific properties (i.e., memory) that I need to modify.
Available properties in config.nt and autoexec.nt don't seem to relieve the
problem.
The MS answer seems to be to use Win98 and copy to Win2000. I'll try that
but I need to load a Win98 box.

BobS

"Mark V" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In microsoft.public.win2000.cmdprompt.admin BobS wrote:
>
> > Hi group,
> >
> > Is there a way to create a program interface file (.pif) on
> > Windows 2000? Thanks.
>
> Assuming you mean from a CLI, most shortcut (LNK) creation methods
> work fine by just specifying .PIF and the 16-bit executable. However
> none of the PIF-sepific properties can be set this way with tools
> such as shortcut.exe. Not certain that helps any.

In microsoft.public.win2000.cmdprompt.admin BobS wrote:

> Hi Mark,
>
> Thanks for the response. CLI or otherwise, doesn't matter.
> Unfortunately, it is the pif specific properties (i.e., memory)
> that I need to modify. Available properties in config.nt and
> autoexec.nt don't seem to relieve the problem.
> The MS answer seems to be to use Win98 and copy to Win2000. I'll
> try that but I need to load a Win98 box.

Possibly the http://www.jsiinc.com
Tip # 6080
solution of using the Win3x pifedit.exe is useful?

But once created, copying the .PIF file from one system to another
should work. Not tested here with pifs. Watch for path diffs.


>
> "Mark V" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> In microsoft.public.win2000.cmdprompt.admin BobS wrote:
>>
>> > Hi group,
>> >
>> > Is there a way to create a program interface file (.pif) on
>> > Windows 2000? Thanks.
>>
>> Assuming you mean from a CLI, most shortcut (LNK) creation
>> methods work fine by just specifying .PIF and the 16-bit
>> executable. However none of the PIF-sepific properties can be
>> set this way with tools such as shortcut.exe. Not certain that
>> helps any.
>
>
>

I had looked at 6080 before and the same info is avail as MS KB articles but
hard to find. I've created pif and copied from WinNT but that sometimes
raised network issues. If you look at the pif in WordPad you will find the
name of the creating computer which seems to be the cause. Pifedit.exe may
work but I haven't come up with pifedit.exe from a win3.1 system. I'll try
copying the pif from a Win98 box after I can get one loaded. If all else
fails, I'll try removing the computer name from the Win2000 pif. I'm sure
the root problem is the mixture of 16-bit apps but i'm stuck with that.
Something has gotta work!

Thanks again.

BobS


"Mark V" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In microsoft.public.win2000.cmdprompt.admin BobS wrote:
>
> > Hi Mark,
> >
> > Thanks for the response. CLI or otherwise, doesn't matter.
> > Unfortunately, it is the pif specific properties (i.e., memory)
> > that I need to modify. Available properties in config.nt and
> > autoexec.nt don't seem to relieve the problem.
> > The MS answer seems to be to use Win98 and copy to Win2000. I'll
> > try that but I need to load a Win98 box.
>
> Possibly the http://www.jsiinc.com
> Tip # 6080
> solution of using the Win3x pifedit.exe is useful?
>
> But once created, copying the .PIF file from one system to another
> should work. Not tested here with pifs. Watch for path diffs.
>
>
> >
> > "Mark V" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> In microsoft.public.win2000.cmdprompt.admin BobS wrote:
> >>
> >> > Hi group,
> >> >
> >> > Is there a way to create a program interface file (.pif) on
> >> > Windows 2000? Thanks.
> >>
> >> Assuming you mean from a CLI, most shortcut (LNK) creation
> >> methods work fine by just specifying .PIF and the 16-bit
> >> executable. However none of the PIF-sepific properties can be
> >> set this way with tools such as shortcut.exe. Not certain that
> >> helps any.
> >
> >
> >
>

I'm using XP and when I create a shortcut to a 16 bit app (I tried
debug.exe), the shortcut is in fact a .pif, not a .lnk file. I have used the
Wscript.Shell object's CreateShortCut method to do this as well (even though
you can only use the .lnk in the definition, the file created is a .pif -
assuming the target app is 16 bit).

Having created the .pif, it is possible to then alter it's memory setting
manually. The only way I know of to alter it under program control is to use
the Wscript.Shell object's AppActivate and Sendkeys methods (simulating doing
itmanually).

Tom Lavedas
===========

"BobS" wrote:

> I had looked at 6080 before and the same info is avail as MS KB articles but
> hard to find. I've created pif and copied from WinNT but that sometimes
> raised network issues. If you look at the pif in WordPad you will find the
> name of the creating computer which seems to be the cause. Pifedit.exe may
> work but I haven't come up with pifedit.exe from a win3.1 system. I'll try
> copying the pif from a Win98 box after I can get one loaded. If all else
> fails, I'll try removing the computer name from the Win2000 pif. I'm sure
> the root problem is the mixture of 16-bit apps but i'm stuck with that.
> Something has gotta work!
>
> Thanks again.
>
> BobS
>
>
> "Mark V" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > In microsoft.public.win2000.cmdprompt.admin BobS wrote:
> >
> > > Hi Mark,
> > >
> > > Thanks for the response. CLI or otherwise, doesn't matter.
> > > Unfortunately, it is the pif specific properties (i.e., memory)
> > > that I need to modify. Available properties in config.nt and
> > > autoexec.nt don't seem to relieve the problem.
> > > The MS answer seems to be to use Win98 and copy to Win2000. I'll
> > > try that but I need to load a Win98 box.
> >
> > Possibly the http://www.jsiinc.com
> > Tip # 6080
> > solution of using the Win3x pifedit.exe is useful?
> >
> > But once created, copying the .PIF file from one system to another
> > should work. Not tested here with pifs. Watch for path diffs.
> >
> >
> > >
> > > "Mark V" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed)...
> > >> In microsoft.public.win2000.cmdprompt.admin BobS wrote:
> > >>
> > >> > Hi group,
> > >> >
> > >> > Is there a way to create a program interface file (.pif) on
> > >> > Windows 2000? Thanks.
> > >>
> > >> Assuming you mean from a CLI, most shortcut (LNK) creation
> > >> methods work fine by just specifying .PIF and the 16-bit
> > >> executable. However none of the PIF-sepific properties can be
> > >> set this way with tools such as shortcut.exe. Not certain that
> > >> helps any.
> > >
> > >
> > >
> >
>
>
>

Using Explorer right click on the program file and click on
"Properties". When you create a shortcut to MS-DOS programs you will
create a PIF. Look in your Windows 2000 Help and search for PIF for
more information.

John

BobS wrote:

> Hi Mark,
>
> Thanks for the response. CLI or otherwise, doesn't matter. Unfortunately,
> it is the pif specific properties (i.e., memory) that I need to modify.
> Available properties in config.nt and autoexec.nt don't seem to relieve the
> problem.
> The MS answer seems to be to use Win98 and copy to Win2000. I'll try that
> but I need to load a Win98 box.
>
> BobS
>
> "Mark V" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
>>In microsoft.public.win2000.cmdprompt.admin BobS wrote:
>>
>>
>>>Hi group,
>>>
>>>Is there a way to create a program interface file (.pif) on
>>>Windows 2000? Thanks.
>>
>>Assuming you mean from a CLI, most shortcut (LNK) creation methods
>>work fine by just specifying .PIF and the 16-bit executable. However
>>none of the PIF-sepific properties can be set this way with tools
>>such as shortcut.exe. Not certain that helps any.
>
>
>

Thanks guys...sorry for the delay. Got iced out of the office for a few
days.

BobS



"BobS" <(E-Mail Removed)> wrote in message
news:%23qu$4lw$(E-Mail Removed)...
> Hi group,
>
> Is there a way to create a program interface file (.pif) on Windows 2000?
> Thanks.
>
> BobS
>
>