Cold boot/Warm boot

Hi
I want to run an application on cold boot only, there are times when I warm
boot the terminal and I don't want this particular application to run.

I have tried a number of methods and have not been successful;

1) myapp.exe and myapp.lnk are in the windows directory and I use
platform.dat to move myapp.lnk to the startup directory, on a coldboot the
application starts up as expected, but it also starts up on a warm boot.

2) removed above changes from platform.dat and put the following in
platform.reg
"Launch60"="myapp.exe"
"Depend60"=hex:1E,00

Again on a cold boot the application runs, but it also runs on a warm boot.

Any help would be appreciated.

Regards

voidcoder
Wed Mar 30 08:39:59 CST 2005

Are the sources available for this application? If so then just
remove "Launch60"="myapp.exe" key programmatically
when Your program starts, lets say in WinMain or whatever
entry point You have. Several calls to registry APIs like
RegOpenKey, RegDeleteValue, RegCloseKey....



"Tweeeek" <Tariq.Mahmood@nospam.com> wrote in message
news:d2eas1$nbd$1$8302bc10@news.demon.co.uk...
> Hi
> I want to run an application on cold boot only, there are times when I
warm
> boot the terminal and I don't want this particular application to run.
>
> I have tried a number of methods and have not been successful;
>
> 1) myapp.exe and myapp.lnk are in the windows directory and I use
> platform.dat to move myapp.lnk to the startup directory, on a coldboot the
> application starts up as expected, but it also starts up on a warm boot.
>
> 2) removed above changes from platform.dat and put the following in
> platform.reg
> "Launch60"="myapp.exe"
> "Depend60"=hex:1E,00
>
> Again on a cold boot the application runs, but it also runs on a warm
boot.
>
> Any help would be appreciated.
>
> Regards
>
>

Bruce
Wed Mar 30 09:06:57 CST 2005

I don't think that will solve the problem either, unless the OP is using
registry HIVES, then it will.

Another solution would be to let it run on *any* reset, but check the reset
cause and exit early if warm boot. You may need to add some code to the
bootloader and/or HAL to make this work. I would recommend an OEMIoctl to
get the reset cause.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member


"voidcoder" <voidcoder@yahoo.com> wrote in message
news:u%23UFQZTNFHA.2136@TK2MSFTNGP14.phx.gbl...
> Are the sources available for this application? If so then just
> remove "Launch60"="myapp.exe" key programmatically
> when Your program starts, lets say in WinMain or whatever
> entry point You have. Several calls to registry APIs like
> RegOpenKey, RegDeleteValue, RegCloseKey....
>
>
>
> "Tweeeek" <Tariq.Mahmood@nospam.com> wrote in message
> news:d2eas1$nbd$1$8302bc10@news.demon.co.uk...
> > Hi
> > I want to run an application on cold boot only, there are times when I
> warm
> > boot the terminal and I don't want this particular application to run.
> >
> > I have tried a number of methods and have not been successful;
> >
> > 1) myapp.exe and myapp.lnk are in the windows directory and I use
> > platform.dat to move myapp.lnk to the startup directory, on a coldboot
the
> > application starts up as expected, but it also starts up on a warm boot.
> >
> > 2) removed above changes from platform.dat and put the following in
> > platform.reg
> > "Launch60"="myapp.exe"
> > "Depend60"=hex:1E,00
> >
> > Again on a cold boot the application runs, but it also runs on a warm
> boot.
> >
> > Any help would be appreciated.
> >
> > Regards
> >
> >
>
>

Bruce
Wed Mar 30 09:09:07 CST 2005

On second thought, even with HIVE Voidcoder's solution will not work. It
will keep the app from running on warm boot and cold boot 2-n. It will only
run on the first cold boot.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member


"Bruce Eitman (eMVP)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net> wrote in
message news:elJ%23joTNFHA.2544@TK2MSFTNGP10.phx.gbl...
> I don't think that will solve the problem either, unless the OP is using
> registry HIVES, then it will.
>
> Another solution would be to let it run on *any* reset, but check the
reset
> cause and exit early if warm boot. You may need to add some code to the
> bootloader and/or HAL to make this work. I would recommend an OEMIoctl to
> get the reset cause.
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> beitman AT applieddata DOT net
>
> Applied Data Systems
> www.applieddata.net
> An ISO 9001:2000 Registered Company
> Microsoft WEP Gold-level Member
>
>
> "voidcoder" <voidcoder@yahoo.com> wrote in message
> news:u%23UFQZTNFHA.2136@TK2MSFTNGP14.phx.gbl...
> > Are the sources available for this application? If so then just
> > remove "Launch60"="myapp.exe" key programmatically
> > when Your program starts, lets say in WinMain or whatever
> > entry point You have. Several calls to registry APIs like
> > RegOpenKey, RegDeleteValue, RegCloseKey....
> >
> >
> >
> > "Tweeeek" <Tariq.Mahmood@nospam.com> wrote in message
> > news:d2eas1$nbd$1$8302bc10@news.demon.co.uk...
> > > Hi
> > > I want to run an application on cold boot only, there are times when I
> > warm
> > > boot the terminal and I don't want this particular application to run.
> > >
> > > I have tried a number of methods and have not been successful;
> > >
> > > 1) myapp.exe and myapp.lnk are in the windows directory and I use
> > > platform.dat to move myapp.lnk to the startup directory, on a coldboot
> the
> > > application starts up as expected, but it also starts up on a warm
boot.
> > >
> > > 2) removed above changes from platform.dat and put the following in
> > > platform.reg
> > > "Launch60"="myapp.exe"
> > > "Depend60"=hex:1E,00
> > >
> > > Again on a cold boot the application runs, but it also runs on a warm
> > boot.
> > >
> > > Any help would be appreciated.
> > >
> > > Regards
> > >
> > >
> >
> >
>
>

Nicolas
Wed Mar 30 09:18:13 CST 2005

The easiest way is to delete the myapp.lnk file after your application
sucessfully start. This prevents it from running again on warm boot.

Nicolas

----------------------------------------------------------------
Nicolas BESSON
ADENEO (ADESET)
Windows Embedded Consultant
<nbesson AT adeneo DOT adetelgroup DOT com>
http://www.adeneo.adetelgroup.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------


"Tweeeek" <Tariq.Mahmood@nospam.com> a écrit dans le message de
news:d2eas1$nbd$1$8302bc10@news.demon.co.uk...
> Hi
> I want to run an application on cold boot only, there are times when I
warm
> boot the terminal and I don't want this particular application to run.
>
> I have tried a number of methods and have not been successful;
>
> 1) myapp.exe and myapp.lnk are in the windows directory and I use
> platform.dat to move myapp.lnk to the startup directory, on a coldboot the
> application starts up as expected, but it also starts up on a warm boot.
>
> 2) removed above changes from platform.dat and put the following in
> platform.reg
> "Launch60"="myapp.exe"
> "Depend60"=hex:1E,00
>
> Again on a cold boot the application runs, but it also runs on a warm
boot.
>
> Any help would be appreciated.
>
> Regards
>
>

Steve
Wed Mar 30 09:52:15 CST 2005

Simplest solution is #1 with a twist - The application deletes the lnk file
in the startup folder after running the first time. This is how the Pocket
PCs run the "Welcome" application on first boot.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

Tweeeek
Wed Mar 30 10:00:54 CST 2005

Hi
Another solution would be to let it run on *any* reset, but check the reset
cause and exit early if warm boot. You may need to add some code to the
bootloader and/or HAL to make this work. I would recommend an OEMIoctl to
get the reset cause.

I'm using the above method, sounds good and clean.

Cheers


"Bruce Eitman (eMVP)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net> wrote in
message news:%23wnfxpTNFHA.3296@TK2MSFTNGP15.phx.gbl...
> On second thought, even with HIVE Voidcoder's solution will not work. It
> will keep the app from running on warm boot and cold boot 2-n. It will
> only
> run on the first cold boot.
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> beitman AT applieddata DOT net
>
> Applied Data Systems
> www.applieddata.net
> An ISO 9001:2000 Registered Company
> Microsoft WEP Gold-level Member
>
>
> "Bruce Eitman (eMVP)" <beitmannospam@NOSPAM_applieddata.NOSPAM_net> wrote
> in
> message news:elJ%23joTNFHA.2544@TK2MSFTNGP10.phx.gbl...
>> I don't think that will solve the problem either, unless the OP is using
>> registry HIVES, then it will.
>>
>> Another solution would be to let it run on *any* reset, but check the
> reset
>> cause and exit early if warm boot. You may need to add some code to the
>> bootloader and/or HAL to make this work. I would recommend an OEMIoctl
>> to
>> get the reset cause.
>>
>> --
>> Bruce Eitman (eMVP)
>> Senior Engineer
>> beitman AT applieddata DOT net
>>
>> Applied Data Systems
>> www.applieddata.net
>> An ISO 9001:2000 Registered Company
>> Microsoft WEP Gold-level Member
>>
>>
>> "voidcoder" <voidcoder@yahoo.com> wrote in message
>> news:u%23UFQZTNFHA.2136@TK2MSFTNGP14.phx.gbl...
>> > Are the sources available for this application? If so then just
>> > remove "Launch60"="myapp.exe" key programmatically
>> > when Your program starts, lets say in WinMain or whatever
>> > entry point You have. Several calls to registry APIs like
>> > RegOpenKey, RegDeleteValue, RegCloseKey....
>> >
>> >
>> >
>> > "Tweeeek" <Tariq.Mahmood@nospam.com> wrote in message
>> > news:d2eas1$nbd$1$8302bc10@news.demon.co.uk...
>> > > Hi
>> > > I want to run an application on cold boot only, there are times when
>> > > I
>> > warm
>> > > boot the terminal and I don't want this particular application to
>> > > run.
>> > >
>> > > I have tried a number of methods and have not been successful;
>> > >
>> > > 1) myapp.exe and myapp.lnk are in the windows directory and I use
>> > > platform.dat to move myapp.lnk to the startup directory, on a
>> > > coldboot
>> the
>> > > application starts up as expected, but it also starts up on a warm
> boot.
>> > >
>> > > 2) removed above changes from platform.dat and put the following in
>> > > platform.reg
>> > > "Launch60"="myapp.exe"
>> > > "Depend60"=hex:1E,00
>> > >
>> > > Again on a cold boot the application runs, but it also runs on a
>> > > warm
>> > boot.
>> > >
>> > > Any help would be appreciated.
>> > >
>> > > Regards
>> > >
>> > >
>> >
>> >
>>
>>
>
>

Bruce
Wed Mar 30 10:11:57 CST 2005

Argh, of course. I need more coffee before answering questions some days.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member


"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> wrote in message
news:eAH92BUNFHA.3380@TK2MSFTNGP15.phx.gbl...
> Simplest solution is #1 with a twist - The application deletes the lnk
file
> in the startup folder after running the first time. This is how the Pocket
> PCs run the "Welcome" application on first boot.
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>

Jun
Thu Mar 31 00:36:16 CST 2005

How to delete the lnk file in the startup folder after running the app?

--
Regards
Jun
"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> дÈëÏûÏ¢ÐÂÎÅ:eAH92BUNFHA.3380@TK2MSFTNGP15.phx.gbl...
> Simplest solution is #1 with a twist - The application deletes the lnk
> file in the startup folder after running the first time. This is how the
> Pocket PCs run the "Welcome" application on first boot.
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>

Tweeeek
Thu Mar 31 01:59:14 CST 2005

Hi
Gosh thats even cooler than the previous solution, I'll give it a whirl.

Regards

"Jun Meng" <mengjunhappy@163.com.cn> wrote in message
news:eYhn4xbNFHA.3668@TK2MSFTNGP14.phx.gbl...
> How to delete the lnk file in the startup folder after running the app?
>
> --
> Regards
> Jun
> "Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com>
> дÈëÏûÏ¢ÐÂÎÅ:eAH92BUNFHA.3380@TK2MSFTNGP15.phx.gbl...
>> Simplest solution is #1 with a twist - The application deletes the lnk
>> file in the startup folder after running the first time. This is how the
>> Pocket PCs run the "Welcome" application on first boot.
>>
>> --
>> Steve Maillet
>> EmbeddedFusion
>> www.EmbeddedFusion.com
>> smaillet at EmbeddedFusion dot com
>>
>>
>
>

Tweeeek
Thu Mar 31 03:20:41 CST 2005

DeleteFile(L"\\Windows\\Startup\\myapp.lnk");


"Jun Meng" <mengjunhappy@163.com.cn> wrote in message
news:eYhn4xbNFHA.3668@TK2MSFTNGP14.phx.gbl...
> How to delete the lnk file in the startup folder after running the app?
>
> --
> Regards
> Jun
> "Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com>
> дÈëÏûÏ¢ÐÂÎÅ:eAH92BUNFHA.3380@TK2MSFTNGP15.phx.gbl...
>> Simplest solution is #1 with a twist - The application deletes the lnk
>> file in the startup folder after running the first time. This is how the
>> Pocket PCs run the "Welcome" application on first boot.
>>
>> --
>> Steve Maillet
>> EmbeddedFusion
>> www.EmbeddedFusion.com
>> smaillet at EmbeddedFusion dot com
>>
>>
>
>