ACPI, EWF NTLDR and NTLDR conflict

  • Thread starter Thread starter AG
  • Start date Start date
A

AG

Hello,

We have a stable XPE image, bootable from SanDisk CF. Now we need to make
this CF card write-protected (EWF RAM Reg). In order to do so, we just
followed the Microsoft help:
http://msdn2.microsoft.com/en-us/library/ms940182.aspx "Configuring EWF RAM
Reg Mode". Unfortunately, the dependency checker complains about two
conflicts:
- Component "ACPI Uniprocessor PC" conflicts ....
- Component "Enchanced Write Filter" conflicts ...

they both suggest disabling EWF NTLDR or NT Loader. When we disable or
delete EWF NTLDR (the EWF RAM reg help suggests that regular NL Loader can
be used), it gets added back to the components list by dependency checker.
We would like to keep the NT Loader instead of EWF NTLDR as we may switch
back to the original configuration, depending on a target configuration.

Any help would be very appreciated.

Thanks,
Alex
 
Alex,

First of all, EWF NTLDR is just an enhanced and backward compatible version of NTLDR. You can use the EWF version with your
"original configuration" without an impact on functionality.

Also, NTLDR can be used with EWF RAM Reg mode if you don't plan to use HORM.
(there are also some other enhancements to EWF version of the loader related to Disk overlay mode which should be irrelevant to your
case)

And the last. Hopefully you'll fix your TD errors but just keep in mind that you can ignore some of them as long as you know you
don't break your system functionality.
 
Forgot to mention. To avoid those conflicts in TD, since you are using EWF, you certainly need to include EWF NTDLR component and
disable/remove the NTLDR.
 
Thank you, KM. Just tried what you suggested. I did disable the NT Loader,
but the Dependency checker simply put it back as NT Loader#2, so I run into
the same error message. Should I just simply ignore it or there is some
workaround for that problem?

Thanks,
Alex
 
Alex,

You may want to disable the Auto-dependency resolver in TD options.

Also, what component is trying to bring in the NT Loader? You should be able to see that in the dependency checker log in TD.
 
Just found out that NT Loader was checked on in the Quick Start Helper.
Everything looks good now. Thanks for the help!
 
Back
Top