有关WES 2009的一些棘手/高级问题 [英] Some tricky/advanced question about WES 2009

查看:87
本文介绍了有关WES 2009的一些棘手/高级问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

嗨。


我有一些与嵌入式大学讨论的问题,但我的问题的答案总是更多的解决方法,作为"问题"的真正解决方法。


让我们从我最重要的问题开始。


1。如何从"默认用户"编辑ntuser.dat配置单元?在fba州/目标设计师?在构建离线图像后,我找不到蜂巢本身。它似乎是在fba时创建的 - 但这并不是那么好,因为创建像
fba命令这样的工作。 (正如我现在使用的那样)。


2。是否可以使用多个条目修改TD中的boot.ini? - 我可以使用sld组件覆盖boot.ini而没有来自TD的错误(如果我想覆盖生成的boot.ini,我总是有一个)(我需要多个完整条目 - 它是
不是关于交换机喜欢 我可以使用可选的启动组件进行修改。)


3。从ECE安装更新并升级  slx文件后,某些可配置组件在打开配置选项卡时失败。 - 我必须删除该组件并再次添加。如果像用户界面核心那样有一点点
更复杂的组件,这种行为就不那么好了。 (行为从可配置更改为普通不可配置组件。)


4。我观看了一些关于嵌入式的网络广播和一些视频。有一个显示了一个名为"pmq-viewer"的工具。我认为网络直播来自迈克大厅(但也许我错了)。是否有人可以研究该工具并提供它?我知道
pmq文件是xml文件。但pmq查看器无需滚动即可快速查看检测到的组件。


5。什么是组件"DiskOnKey USB个人存储设备"。 for?


6。 TAP.exe为什么WES 2009中的那个不能在PE环境下工作? (测试过)vista / w7?但来自WES 7的那个呢?


7。在tap.exe中描述/ i切换从来没有为我工作。它显示在帮助本身,但对检测到的硬件没有影响。


谢谢。 :)

解决方案

1。用户帐户和许多注册表项在FBA期间进行设置,这就是FBA运行后看不到文件单元的原因。你想编辑什么,是否可以添加到组件中?


2。 boot.ini文件是Target Designer在构建过程中创建的最后一件事。 KM有一个boot.ini的解决方案,发布到
www.xpefiles.com 。另一种解决方法是在FBA期间将应用程序复制到新的boot.ini(从boot.ini.new或某些内容重命名)文件中。基本上,应用程序替换了Target Designer创建的


3。我从未见过这个。配置标签?


4。很久以前,有一个XML Editor工具可以打开来编辑PMQ文件。您想要查看PMQ文件的内容是什么?


5。 DiskOnKey是第一个USB闪存密钥的名称。我相信这是来自IBM的USB密钥。它只是一个驱动因素。


6。 TAP应该在WinPE 1.0上运行。我从未测试过基于Vista / Win7的更高版本。


7。 / i开关被添加到XPe的一个更新中,但我不记得它曾经有效。


-Sean


 


Hi.

I have some question i discussed with an embedded college but the answers to my questions were always more workarounds as real fixing of "problems".

Let's start with my most important question.

1. How can i edit the ntuser.dat hive from "default user" in fba state / target designer? i can't find the hive itself after builing offline image. it seems it gets created while fba - but this issn't that much nice, because of creating workaroungs like fba commands. (as i use now).

2. Is it possible to modify the boot.ini in TD with more than one entry? - can i overwrite the boot.ini with an sld component without an error from TD (i always got one if i want to overwrite the generated boot.ini) (i need more than one full entry - it's not about switches like i can modify with optional boot component.)

3. After installing updates from ECE and upgrading the slx file,  some configureable components are failing while opening the config tab. - i have to delete the component and add it again. this behavior is not that nice if there is a little bit more complex component like the User Interface Core. (the behavior changes from configureable to normal not configureable component.)

4. I watched some webcasts and some vids about embedded. there was one which showd a tool called "pmq-viewer" i think the webcast was from mike hall (but maybe i'm wrong). is it possible that someone can research about the tool and can provide it? i know that pmq files are xml files. but pmq viewer has enabled a very quick view about detected components without scrolling.

5. what is the component "DiskOnKey USB personal storage device" for?

6. TAP.exe why does the one from WES 2009 not work under PE Environment? (tested) vista / w7? but the one from WES 7 does?

7. The described /i switch in tap.exe never worked for me. it's shown in the help itself but has no effected on the detected hardware.

Thanks. :)

解决方案

1. User accounts and many registry keys get setup during FBA, which is why you don't see the file unit after FBA runs. What are you trying to edit and is it something that can be added in a component?

2. The boot.ini file is the last thing Target Designer creates during the build process. KM had a solution for boot.ini posted to www.xpefiles.com. Another work around is to have an application copy over a new boot.ini (renamed from boot.ini.new or something) file during FBA. Bascially, the application replaces the one created by Target Designer.

3. I have never seen this. Configuation tab?

4. A long time ago there was an XML Editor tool that can open to edit PMQ files. What are you trying to get out of viewing the PMQ file?

5. DiskOnKey was the name of the first USB flash keys. I believe this was a USB key from IBM. It is just a driver component.

6. TAP should run on WinPE 1.0. I have never tested on th later versions that are based on Vista/ Win7.

7. /i switch was added to one of the updates to XPe, but I don't remember it ever worked.

-Sean

 


这篇关于有关WES 2009的一些棘手/高级问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆