``Your Pop-Up Program is Ready''

[Howard Schwartz]

This starts the infamous message one reads when a dos box does not close,
and requires you to hit Ctrl-C to close the window.

The MS knowledge base tells you this happens, when windows detects an
operation like direct disk writes that it believes is associated with
a dos TSR program. It then sets a flag, stops taking input from the
dos windows, and requires the Ctrl-C from your keyboard to close
the window.

The recommended workaround is to create a batch file containing:

command.com /C

And type the name of this file in the ``batch file'' field of a pif or
shortcut tab (which one sees by choosing Properties). This does not
work for me, and I never really understood how the separate fields of
``command line'' and ``batch file'' of a shortcut function. Is the
batch file run, prior to the command, to provide a specific dos environment
or some special variables for the command? In what order are these two
run?

Anyone have another way to stop this annoying message ``Your pop-up menu --
'' ? The trick seems to be to automatically send a close or kill signal for
a dox box, but not from within that box!

 

[hummingbird]

This starts the infamous message one reads when a dos box does not close,
and requires you to hit Ctrl-C to close the window.

The MS knowledge base tells you this happens, when windows detects an
operation like direct disk writes that it believes is associated with
a dos TSR program. It then sets a flag, stops taking input from the
dos windows, and requires the Ctrl-C from your keyboard to close
the window.

The recommended workaround is to create a batch file containing:

command.com /C

And type the name of this file in the ``batch file'' field of a pif or
shortcut tab (which one sees by choosing Properties). This does not
work for me, and I never really understood how the separate fields of
``command line'' and ``batch file'' of a shortcut function. Is the
batch file run, prior to the command, to provide a specific dos environment
or some special variables for the command? In what order are these two
run?

IIRC there is a place in PIF to enter a program path to run before
the PIF DOS proggy is run. You should enter the batch path/name there.

Then, when you run the PIF, the batch will be run first before the
DOS program and 'command.com /c' will be active.

A better place to ask this question is NG "alt.msdos" - there's some
real DOS experts thereabouts.

 

[hummingbird]

IIRC there is a place in PIF to enter a program path to run before
the PIF DOS proggy is run. You should enter the batch path/name there.

Then, when you run the PIF, the batch will be run first before the
DOS program and 'command.com /c' will be active.

A better place to ask this question is NG "alt.msdos" - there's some
real DOS experts thereabouts.

An alternative is to create a batch file to start the DOS proggy and
enter "command.com /c" (w/o the quotes) on a line on its own before
the DOS program.

 

[Howard Schwartz]

An alternative is to create a batch file to start the DOS proggy and
enter "command.com /c" (w/o the quotes) on a line on its own before
the DOS program.

Why does this work? I usually get this message, when my program IS a batch
file, itself - not an exe or com executable. My batch file might have
an interactive program containing a pop-up, such as acd (enhanced change
directory). So a pop up screen lets me pick a director, and then acd goes
thee, the pop up screen vanishes, and I get the Ctrl-C message.

Command.com /c would start a subshell and then immediately close it, and
would do so at the start of my batch file. What good will this do, if the
offending program accurs later in my batch file?

This command.com /c does not work anyway. I have tried it.

 

[DevilsPGD]

In message <[email protected]> Howard

Why does this work? I usually get this message, when my program IS a batch
file, itself - not an exe or com executable. My batch file might have
an interactive program containing a pop-up, such as acd (enhanced change
directory). So a pop up screen lets me pick a director, and then acd goes
thee, the pop up screen vanishes, and I get the Ctrl-C message.

Command.com /c would start a subshell and then immediately close it, and
would do so at the start of my batch file. What good will this do, if the
offending program accurs later in my batch file?

This command.com /c does not work anyway. I have tried it.

IIRC, the default PIF for command.com doesn't have this popup, the
default PIF for some other types (batch files, for example) does...

 

[hummingbird]

Why does this work? I usually get this message, when my program IS a batch
file, itself - not an exe or com executable. My batch file might have
an interactive program containing a pop-up, such as acd (enhanced change
directory). So a pop up screen lets me pick a director, and then acd goes
thee, the pop up screen vanishes, and I get the Ctrl-C message.

This is quite OT on this NG.

Why don't you post the line x line contents of your batch file on
""alt.msdos"" with a summary of the problem and ask for advice there.

You will get an answer.

 

[Howard Schwartz]

IIRC, the default PIF for command.com doesn't have this popup, the
default PIF for some other types (batch files, for example) does...

Do you have any idea why? It must be some of its settings, and it would
help to know which, when setting up other dos box programs.

True, if you are right, one can just justed the default dos pif for
all dos programs.