Re: Starting applications automagically from command shell

From: Heidi Linda <heidi.linda@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 23 Nov 2005 17:25:51 +0000

Stas Pavlov (eMVP) wrote:

Ups... Sorry. You need to autrun inside command prompt.

You can create you own shell with cmiShellPath like this:
%11%\cmd.exe /k %30%\my_autorun.bat

where %30%\my_autorun.bat contain all needed autorun apps.

OK well all I want to do is run a single batch file. I was under the impression that autoexec.nt should actually do something under the command shell. .

References:
- Starting applications automagically from command shell
  - From: Heidi Linda
- Re: Starting applications automagically from command shell
  - From: Stas Pavlov \(eMVP\)
- Re: Starting applications automagically from command shell
  - From: Stas Pavlov \(eMVP\)

Prev by Date: Re: .Net Framework 2.0
Next by Date: Re: FBRESEAL and EWF RAM
Previous by thread: Re: Starting applications automagically from command shell
Next by thread: .Net Framework 2.0
Index(es):
- Date
- Thread

Relevant Pages

Re: unresolved external symbol/using an external dll
... Michael J. Salamone [eMVP] wrote: ... > Actually Windows CE only has cdecl calling convention. ... I got the impression that the OP is using code to read a CE database outside ...
(comp.lang.cpp)
Re: unresolved external symbol/using an external dll
... Michael J. Salamone [eMVP] wrote: ... > Actually Windows CE only has cdecl calling convention. ... I got the impression that the OP is using code to read a CE database outside ...
(microsoft.public.vc.language)
Re: unresolved external symbol/using an external dll
... Michael J. Salamone [eMVP] wrote: ... > Actually Windows CE only has cdecl calling convention. ... I got the impression that the OP is using code to read a CE database outside ...
(microsoft.public.windowsce.app.development)