Add New Hardware wizard appears on each boot

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

Each time I boot my new XPe image I get the Add New Hardward wizard. The
wizard installs a USB printer (Star TSP700) and I can even see the printer
in Control Panel \ Printers before I reboot. As soon as I've rebooted, the
printer is not in Printers and the wizard is displayed again.

Can someone help me out? I'm doing all my work on a single machine with
one physical drive; XPe on C and XP Pro on D.
 
Hi Chris,

You are again with same problem, EWF?
Same thing was happening to you when you tried to change boot.ini.

Who made this XPe image? Can you tell us if you have EWF in your image or not?

Regards,
Slobodan
 
Slobodan,

My image has the components 'Enhanced Write Filter' & 'EWF NTLDR'. I also
ran a dependency check prior to the image build. I can even print a test
page on the printer in XPe.

The previous image (which I'm told was working) was produced by someone else
on the same machine. I have simply added the Message Queue components
(excluding HTTP support), run a dependency check, rebuilt the image and
deployed it.

Chris
 
Chris,

Do you know what is the purpose of EWF (Enhanced Write Filter)?
Do you need help with EWF?
Do you know how to configure and use it?
Do you use RAM or DISK overlay?

Use ewfmgr.exe to check for EWF state (enabled/disabled).
Before reboot use ewfmgr c: -commit if EWF is enabled.

Regards,
Slobodan

PS:
EWF is enabled (probably ) and causing you all problems that you have reported.
Probably it stayed enabled from previous build. (It is configured trough hidden EWF partition on your disk)
 
We've always found that the first boot of a cloned image will show the Add
New Hardware wizard. We think this is because our build machines and real
hardware have slightly different configurations. Build machines, for
example, have KB/Mouse ports and Video. Real machines don't. Real machines
have extra NICs and a proprietary PCI device. Build machines don't. We
live with it. Since each customer needs to do some personization of his
machine, and since we use stateless EWF, we have a documented procedure for
them to follow. In great simplicity, it goes like this:
- Boot and connect using remote desktop
- Answer 'no' to all the add hardware prompts
- Commit EWF and reboot (commit not necessary because EWF isn't active
until the second boot)
- Connect using remote desktop
- Personalize the machine (name, IP, application settings, etc)
- Commit EWF and reboot
- Machine is now ready
- Use web browser to access all normal functions of the machine (remote
desktop is for setup and debug only)

--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Chris,

Do you know what is the purpose of EWF (Enhanced Write Filter)?
Do you need help with EWF?
Do you know how to configure and use it?
Do you use RAM or DISK overlay?

Use ewfmgr.exe to check for EWF state (enabled/disabled).
Before reboot use ewfmgr c: -commit if EWF is enabled.

Regards,
Slobodan

PS:
EWF is enabled (probably ) and causing you all problems that you have reported.
Probably it stayed enabled from previous build. (It is configured trough
Click to expand...
hidden EWF partition on your disk)
 
Hi Mark,

Yes, but he have slightly different problem. To him this happens each time he boot same device.

For your case:

1. Rename newdev.dll to some other name. (newdev.bkp)
2. fbreseal.
3. multiply disk.
4. boot cloned device and let FBA complete itself. (You can add option to autorename newdev.bkp back to newdev.dll)
5. Machine is ready.

In between add your personilazation settings.

Now you won't have to bother and explain to your customer why Add New Hardware wizard pop-up.

Regards,
Slobodan
 
Cool. I'll make a component that wraps this up in a neat way, test it, and
put in in a future build. Thanks.

--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Hi Mark,

Yes, but he have slightly different problem. To him this happens each time he boot same device.

For your case:

1. Rename newdev.dll to some other name. (newdev.bkp)
2. fbreseal.
3. multiply disk.
4. boot cloned device and let FBA complete itself. (You can add option to
Click to expand...
autorename newdev.bkp back to newdev.dll)
 
Right.

I have no idea why you use Add Hardware Wizard in the first place. PnP is capable of doing things without user intervention just
fine.

Regards,
Slobodan
 
We don't use the Add Hardware Wizard at all. Its just there because of some
dependancy, and gets in the way. Maybe I should take it out and ignore the
dependancy check. Or, just delete the newdev.dll after the build and before
FBA.

--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Right.

I have no idea why you use Add Hardware Wizard in the first place. PnP is
Click to expand...
capable of doing things without user intervention just
 
Mark,
We don't use the Add Hardware Wizard at all. Its just there because of some
dependancy, and gets in the way. Maybe I should take it out and ignore the
dependancy check. Or, just delete the newdev.dll after the build and before
FBA.
Click to expand...

Then open component in TD find newdev.dll and disable it. This way file won't be included and you will not have warnings at all.

Regards,
Slobodan
 
I'll try that. Removing the component and ignoring the warning isn't good
enough. The system crashes during FBA. I disabled two wizards that are
useless to me, but apparrently needed. I'll try disabling just the file...

--
Regards.
Mark K Vallevand
Slobodan Brcin (eMVP) said:
Mark,


Then open component in TD find newdev.dll and disable it. This way file
Click to expand...
won't be included and you will not have warnings at all.
 
Back
Top