G
Guest
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
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