Shell .PIF file to DOS nogo due to invalid Autoexec.bat line.

A visual basic app of mine submits a pif file to run an EXE file under
DOS. This is done with a "Shell run-fit.pif parm1 parm2 parm3 ..."
command from my Windows 95/98 app. My autoexec.bat includes two lines
attached by my the Windows app. The first line should be for starting
my DOS app but has an error. This line is as follows: "Call /c
MyApp.bat parm1 parm2 parm3 ..." This "/c" in this command is the
problem. How to get rid of it, ideas?

A pif file is shelled from VB6. Is VB adding the "/c" or is it some
parameter/setting on the pif file?

My vb compiler is not available for changes right now so need some
other way for a fix.

Thanks,
Phil

Either boot to a command prompt and type the command:
edit c:\autoexe.bat and press Enter

or in Windows, right click and select Edit.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375




"Phil" wrote in message oups.com...
A visual basic app of mine submits a pif file to run an EXE file under
DOS. This is done with a "Shell run-fit.pif parm1 parm2 parm3 ..."
command from my Windows 95/98 app. My autoexec.bat includes two lines
attached by my the Windows app. The first line should be for starting
my DOS app but has an error. This line is as follows: "Call /c
MyApp.bat parm1 parm2 parm3 ..." This "/c" in this command is the
problem. How to get rid of it, ideas?

A pif file is shelled from VB6. Is VB adding the "/c" or is it some
parameter/setting on the pif file?

My vb compiler is not available for changes right now so need some
other way for a fix.

Thanks,
Phil

On 24 Apr 2006 16:46:35 -0700, "Phil" wrote:

A visual basic app of mine submits a pif file to run an EXE file under
DOS. This is done with a "Shell run-fit.pif parm1 parm2 parm3 ..."
command from my Windows 95/98 app. My autoexec.bat includes two lines
attached by my the Windows app. The first line should be for starting
my DOS app but has an error. This line is as follows: "Call /c
MyApp.bat parm1 parm2 parm3 ..." This "/c" in this command is the
problem. How to get rid of it, ideas?

A pif file is shelled from VB6. Is VB adding the "/c" or is it some
parameter/setting on the pif file?

My vb compiler is not available for changes right now so need some
other way for a fix.

Thanks,
Phil

If I understand the problem and If the PIF is in the root try this
line instead:

Call C:\MyApp.bat parm1 parm2 parm3

To change the line. Start Run and enter Sysedit. Change the line
and save it. Or use one of the suggestions by Brian.

Regards,

Bill Watt
Win98 Computer Help & Other Information http://home.ptd.net/~bwatt/

This is an application that has this problem, must fix for -all-
general runs. My app shells to a pif and adds some parameters but where
does this '/c' on the autoexec.bat files come from? Or how to remove
it?

Thanks,
Phil

On 24 Apr 2006 16:46:35 -0700, "Phil" put
finger to keyboard and composed:

A visual basic app of mine submits a pif file to run an EXE file under
DOS. This is done with a "Shell run-fit.pif parm1 parm2 parm3 ..."
command from my Windows 95/98 app. My autoexec.bat includes two lines
attached by my the Windows app. The first line should be for starting
my DOS app but has an error. This line is as follows: "Call /c
MyApp.bat parm1 parm2 parm3 ..." This "/c" in this command is the
problem. How to get rid of it, ideas?

A pif file is shelled from VB6. Is VB adding the "/c" or is it some
parameter/setting on the pif file?

Launch run-fit.pif manually and observe autoexec.bat, or r-click the
..pif file and select Properties, or manually launch the .exe file in a
DOS box.

You could also view the contents of any suspect files using the Edit
command in a DOS box:

edit /r /64 filename.ext

Search for "Call /c".

My vb compiler is not available for changes right now so need some
other way for a fix.

Once you find the offending file, use the Edit command to replace the
"/c" with two spaces. Do this in overstrike mode, not insert mode.

Note that Edit's "/r" switch selects read-only mode. To allow editing,
use the following syntax:

edit /64 filename.ext

Thanks,
Phil

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.