Re: EWF Ram Reg AND Static IP Script
- From: "MJ" <MJ@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Jun 2005 10:36:06 -0700
What phase does EWF Ram Reg setup run?
"Slobodan Brcin (eMVP)" wrote:
> Hi,
>
> Your shell can determine when it is required to change IP address and do that only when needed.
>
> Regarding your script.
> If you want it to change IP address then you can execute net programs at phase 8500, 8501.
> Make sure that you execute "rundll32 netshell.dll HrRenameConnection " at phase 8500
> and at 8501 something like "netsh interface ip set address "Local Area Connection" static 192.168.1.10 255.255.255.0 192.168.1.1 1"
>
> Regards,
> Slobodan
>
>
> "MJ" <MJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:A5EC525E-7163-4260-AF12-3ECEF4653B85@xxxxxxxxxxxxxxxx
> > Slobodan,
> > We have a custom script the runs as an FBA Command that uses NetSh to change
> > the IP during FBA. We can't do it at boot every time because we have very
> > strict timing requirements for boot time.
> >
> > "Slobodan Brcin (eMVP)" wrote:
> >
> > > MJ,
> > >
> > > I have no ides of what script you are talking about, but regardles of that.
> > >
> > > Why can't your shell launcher change IP address? Why would that be a problem?
> > >
> > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xehowNamingNetworkInterfacesOnRun-TimeImage.asp
> > >
> > > Regards,
> > > Slobodan
> > >
> > >
> > > "MJ" <MJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D1776ED4-2C98-4F6D-B866-A52F528F7A8F@xxxxxxxxxxxxxxxx
> > > > Hello,
> > > > I had an XPe image that during a second boot of the FBA runs a script that
> > > > sets the IP address to a static one. We now have to add EWF Ram Reg to the
> > > > image. It should be noted that in the final version of this code, we will be
> > > > running a custom shell, so there will be no command shell access.
> > > >
> > > > Here's a summary of the problems:
> > > > The static ip script used to run on a second first boot run.
> > > >
> > > > Now with EWF Ram Reg, the IP script runs, then the system boots up, but it
> > > > seems that the script is no longer considered part of the fba.
> > > >
> > > > Every time the system boots now, it runs the script - and the script doesn't
> > > > work!
> > > >
> > > > I can only set the static ip now if I run the script manually after boot and
> > > > commit the ewf. Unfortunately once we have a custom shell this method will
> > > > be a problem.
> > > >
> > > > Does anyone have any idea how to get the EWF Ram Reg and Static IP script to
> > > > play nice together?
> > > >
> > > > Thanks!
> > > > MJ
> > >
> > >
> > >
>
>
>
.
- Follow-Ups:
- Re: EWF Ram Reg AND Static IP Script
- From: Slobodan Brcin \(eMVP\)
- Re: EWF Ram Reg AND Static IP Script
- References:
- EWF Ram Reg AND Static IP Script
- From: MJ
- Re: EWF Ram Reg AND Static IP Script
- From: Slobodan Brcin \(eMVP\)
- Re: EWF Ram Reg AND Static IP Script
- From: MJ
- Re: EWF Ram Reg AND Static IP Script
- From: Slobodan Brcin \(eMVP\)
- EWF Ram Reg AND Static IP Script
- Prev by Date: Re: CF booting problem sbc845000vea
- Next by Date: Re: net start server SP2
- Previous by thread: Re: EWF Ram Reg AND Static IP Script
- Next by thread: Re: EWF Ram Reg AND Static IP Script
- Index(es):
Relevant Pages
|
