Problem with FBA Generic Command (again...)

  • Thread starter Thread starter Ricky
  • Start date Start date
R

Ricky

Just another update.
The same script doesn't work with wscript also.
I obtain the same error (0x1).

Any suggestion?

Ricky
 
Circling back to my original reply - The only caveat to using wscript is
setting the right mode for cscript.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit
 
Circling back to my original reply - The only caveat to using wscript is
setting the right mode for cscript.
Click to expand...

I setted up a Generic command with wscript as path and //H:cscript as
argument but I obtain the same result (0x1).

Ricky
 
Ricky,

Let me ask you again. What happens if you run the same command you are setting as the FBA Generic command (try to duplicate command
as close as possible) when FBA is already done and using Start-->Run window, for instance?

And last but not least. Do you have Windows Script engine components included in your image??
 
Ricky,

Let me ask you again. What happens if you run the same command you are setting as the FBA Generic command (try to duplicate command
as close as possible) when FBA is already done and using Start-->Run window, for instance?
Click to expand...

It works. But, also, it works if I open a cmd windows before FBA ends and
insert the same command.
More strange, the script works also if before launching the generic command
with the script I open a cmd prompt (with generic command) with /K argument
and then close it with exit. If I try to open the cmd with /C switch I
obtain the same error when launching the script (0x1)

And last but not least. Do you have Windows Script engine components included in your image??
Click to expand...

Yes.

Ricky
 
Ricky,

It all sounds linke a timing issue. I never tried IIS's adsutil.vbs script myself but I think it may have some dependencies on
component initialization that happens during FBA.

Anyway, you may want to try to launch the command from a batch script during FBA. Just make sure to put a wait statement for a few
seconds or more just before the call to launch the script.
For simplicity you can implement wait in batch mode by using any technique such as:
- Use Sleep or Timeout utility from NT Resource Kit. Or you can write your own Sleep tool (just one API call),
- Use ping to ping local host address with # of seconds limitted and specified:
PING 127.0.0.1 -n <secs>
- etc.

Another workaround would probably be in launching yoru script in automated mode *after* FBA is done. You can implement this by
launching a self-cleaning (self-deleting) batch script from All Users\Startup folder and have Autologon setup (you can disable the
autologon from the same script if not required for final image).
 
Ricky,

It all sounds linke a timing issue. I never tried IIS's adsutil.vbs script myself but I think it may have some dependencies on
component initialization that happens during FBA.

Anyway, you may want to try to launch the command from a batch script during FBA. Just make sure to put a wait statement for a few
seconds or more just before the call to launch the script.
For simplicity you can implement wait in batch mode by using any technique such as:
- Use Sleep or Timeout utility from NT Resource Kit. Or you can write your own Sleep tool (just one API call),
- Use ping to ping local host address with # of seconds limitted and specified:
PING 127.0.0.1 -n <secs>
- etc.
Click to expand...

I'll try.
Another workaround would probably be in launching yoru script in automated mode *after* FBA is done. You can implement this by
launching a self-cleaning (self-deleting) batch script from All Users\Startup folder and have Autologon setup (you can disable the
autologon from the same script if not required for final image).
Click to expand...

I taught about this type of solutions but, if I use EWF, will the update
been wrote on the final image?

Thanks a lot.

Ricky
 
Ricky,

It all sounds linke a timing issue. I never tried IIS's adsutil.vbs script myself but I think it may have some dependencies on
component initialization that happens during FBA.

Anyway, you may want to try to launch the command from a batch script during FBA. Just make sure to put a wait statement for a few
seconds or more just before the call to launch the script.
Click to expand...

It was a timing issue. I setted up a sleep command with 3 seconds as param
and now the script works.

Thanks a lot.

Ricky
 
Ricky,
I taught about this type of solutions but, if I use EWF, will the update
been wrote on the final image?
Click to expand...


Well, even with EWF your batch script can commit the overlay and reboot the device if necessary.
 
Super. Perhaps you didn't set the FBA phase for the command launch high enough to be run after IIS routine was initialized.
 
Back
Top