Ive got a button that copies images from an image LE to another location on the users hard drive via the @Shell command.

All my @Shell commands cause the black DOS box to flash on and off for each record (sometimes the program does not continue until the box closes).

I'm sure there are reasons for this, but I don't know why. Is there a way to run @Shell commands without the DOS box flashing on the screen?

I'd rather see the writeln slate display the progress of the program instead.

Thanks,
Steve

Check the folder where the executable command is located. 

See if there is a PIF file for that program.  The PIF file will usually have the same name with no extension.  (One may frequently be created if that program is called from another one).  In Explore, under the Type column you may see something like "Performs text-based (command-line) functions."

If there is a PIF file, edit the properties for that file.  Go to the tab for Properties and change the value in the Run field to minimized.

If no PIF file exists, then you could make a batch file with a single line to run the program.  Calling that batch file will usually create a PIF file.  Now you edit that as noted above.

Look in the folder where you keep Launch.bat for a PIF file for Launch.

Change property of PIF for RUN to Run Minimized.

That's all you need to do.  DOS box will not be visible.

Let me know if you need help to make a PIF file if none is there.

On XP the easiest thing to do is make a shortcut to the batch file. 

Using Explore, open the folder with launch.bat.  Right click on file and select Make a Shortcut.  That shortcut is the same as the PIF file I referred to.  Edit that to run minimized.   

You may need to change your routine to call the shortcut vs. the batch file, or the batch file may use these settings anyway.  The "PIF"/shortcut file values are written to the registry for that batch file.

Since Shortcuts to applications aren't recognized by DOS, you can't execute them directly. However, there is a way to launch them, either from the prompt, or from a batch file.  The answer is to use the start command:

Type the following: start "C:\Path\Shortcut to Someprog.exe.lnk", where C:\Path is the full path containing the shortcut, and Shortcut to Someprog.exe.lnk is the filename of the shortcut.

Note that the shortcut filename may not have an extension, that is OK.  You can try this manually in a command window before you  put it into your programming.  The quotes are included to allow for spaces in long path/file names.
=================
Now that I think a bit more about it, you don't even need the shortcut.  When you use start  you can tell it to run minimized at the same time with the /m switch. 

Try this: Quote:
I should have thought of this earlier.

Be sure to try both from my last message: The start /m launch.bat and the start /m launch.lnk that has been modified to Run minimized.

I have not yet tried in Sesame myself, these are just normal functions that work with other programs.  I have been thinking that Sesame's @shell should handle them also.

Whether or not this works,  provide example of the @shell command you are using.  If good, we will all know, if no good we can all contribute to solution.

Nope, the /m goes right after start.........

Here is the format for syntax for start:

Quote: