XPE on 2 drives with EWF

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does anyone have a comprehensive list of things to do to deploy XPe with the
OS on a CF drive protected with RegMode EWF (or a CD-ROM), Drive C, and the
second drive (HDD), Drive D that is unprotected. The idea is that ALL logs,
temporary files, page file, Document and Settings folders, Dr Watson crash
dumps, etc. are directed to the HDD for persistence.
The latest release FP2007 documents how to move the Document and Settings
folder to a different drive. What if anything else, needs to be done, for
example Event logs, WBEM logs etc?
There have been numerous messages and various solutions to specific
questions posted here over the years, but has anyone compiled a single
document that works?
I've been testing a number of things over the years, but I must admit that
its been ad hoc at best.

The second question is related to the list of Predefined System Environment
variables and other substitution variables. It is possible to "add" to this
list? For example, to change the location of the event logs to Drive D
rather than Drive C. The default path is
%SystemRoot%\system32\config\AppEvent.Evt. Where / how is %SystemRoot%
defined? Would be nice to change it to something like
%WindowsDRoot%\config\AppEvent.Evt.

Thanks,
Joe
 
Joe,

Not all of them but some: http://msdn.microsoft.com/embedded/community/community/tips/xp/ramewf/default.aspx

I don't know if anyone has compiled the final list (it would be really hard to do since there are thousand components with all their
settings and not all of them are typically included in a image).


You can always add an Environment variable in TD or at runtime. It is stored in registry under :
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment].
 
Thanks for the response KM.

I have the info at the link you sent. Some of the other components and
variables that potentially needs to be changed are as I mentioned previously.

Dr. Watson, WBEM logs, System Variables: TEMP and TMP, Explorer Temporary
Internet Files location, Startup and Recovery Dump File location, Target
Device Settings Document and Settings folder,...

I was hoping that the result would be that there will be no writes
whatsoever to the C drive, hence no net memory usage by the EWF. Our app
runs 24 / 7 / 365 and I'm still hoping that this deployment arrangement is
possible with the two drives. I want to be assured that the system will not
crash after 6 months due to a lack of available memory because the EWF has
used it all up.

I was hoping that someone had already done the grunt work. I guess I'll
have to start...

Thanks again,
Joe


KM said:
Joe,

Not all of them but some: http://msdn.microsoft.com/embedded/community/community/tips/xp/ramewf/default.aspx

I don't know if anyone has compiled the final list (it would be really hard to do since there are thousand components with all their
settings and not all of them are typically included in a image).


You can always add an Environment variable in TD or at runtime. It is stored in registry under :
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment].

--
=========
Regards,
KM
Does anyone have a comprehensive list of things to do to deploy XPe with the
OS on a CF drive protected with RegMode EWF (or a CD-ROM), Drive C, and the
second drive (HDD), Drive D that is unprotected. The idea is that ALL logs,
temporary files, page file, Document and Settings folders, Dr Watson crash
dumps, etc. are directed to the HDD for persistence.
The latest release FP2007 documents how to move the Document and Settings
folder to a different drive. What if anything else, needs to be done, for
example Event logs, WBEM logs etc?
There have been numerous messages and various solutions to specific
questions posted here over the years, but has anyone compiled a single
document that works?
I've been testing a number of things over the years, but I must admit that
its been ad hoc at best.

The second question is related to the list of Predefined System Environment
variables and other substitution variables. It is possible to "add" to this
list? For example, to change the location of the event logs to Drive D
rather than Drive C. The default path is
%SystemRoot%\system32\config\AppEvent.Evt. Where / how is %SystemRoot%
defined? Would be nice to change it to something like
%WindowsDRoot%\config\AppEvent.Evt.

Thanks,
Joe
Click to expand...
Click to expand...
 
Joe,

Most of the components you mentioned were discussed in this NG so the group's archive may be a good source of info for you when you
are compiling the list.

Another approach you may find helpful is exploring settings pages and resources of corresponding components. E.g., Dr.Watson
component will show you where its log files stored, where crash dumps go, etc. You can change the log location on the Settings page
(at least on FP2007).
System variables - you already know where it is stored.

The Explorer and IE stuff is probably the most popular and lots of info availalble about it on Web.
I.e. you can set up all the folder paths under [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell
Folders]. (Cache, Local Settings, etc.)

I think many of us here have done such work (including myself). Personally, I can't send out my final reg files as it belongs a real
customer :-)

--
=========
Regards,
KM
Thanks for the response KM.

I have the info at the link you sent. Some of the other components and
variables that potentially needs to be changed are as I mentioned previously.

Dr. Watson, WBEM logs, System Variables: TEMP and TMP, Explorer Temporary
Internet Files location, Startup and Recovery Dump File location, Target
Device Settings Document and Settings folder,...

I was hoping that the result would be that there will be no writes
whatsoever to the C drive, hence no net memory usage by the EWF. Our app
runs 24 / 7 / 365 and I'm still hoping that this deployment arrangement is
possible with the two drives. I want to be assured that the system will not
crash after 6 months due to a lack of available memory because the EWF has
used it all up.

I was hoping that someone had already done the grunt work. I guess I'll
have to start...

Thanks again,
Joe


KM said:
Joe,

Not all of them but some: http://msdn.microsoft.com/embedded/community/community/tips/xp/ramewf/default.aspx

I don't know if anyone has compiled the final list (it would be really hard to do since there are thousand components with all
their
settings and not all of them are typically included in a image).


You can always add an Environment variable in TD or at runtime. It is stored in registry under :
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment].

--
=========
Regards,
KM
Does anyone have a comprehensive list of things to do to deploy XPe with the
OS on a CF drive protected with RegMode EWF (or a CD-ROM), Drive C, and the
second drive (HDD), Drive D that is unprotected. The idea is that ALL logs,
temporary files, page file, Document and Settings folders, Dr Watson crash
dumps, etc. are directed to the HDD for persistence.
The latest release FP2007 documents how to move the Document and Settings
folder to a different drive. What if anything else, needs to be done, for
example Event logs, WBEM logs etc?
There have been numerous messages and various solutions to specific
questions posted here over the years, but has anyone compiled a single
document that works?
I've been testing a number of things over the years, but I must admit that
its been ad hoc at best.

The second question is related to the list of Predefined System Environment
variables and other substitution variables. It is possible to "add" to this
list? For example, to change the location of the event logs to Drive D
rather than Drive C. The default path is
%SystemRoot%\system32\config\AppEvent.Evt. Where / how is %SystemRoot%
defined? Would be nice to change it to something like
%WindowsDRoot%\config\AppEvent.Evt.

Thanks,
Joe
Click to expand...
Click to expand...
Click to expand...
 
Back
Top