XPE Documentation update requests?

Hi Everyone,

We're currently working on the next Windows XP Embedded documentation
update, which will include many bug fixes, updates, and new how-to
processes.

If anyone here has any issues they'd like to see addressed in the
documentation, please let me know. We're looking to both improve our
current processes and add new ones. If you have any requests, please send
email to: dansimp@microsoft.com or reply to this thread.

Many, many thanks to all the participants here that make this newsgroup
community so strong!

Thanks,

Dan


Dan Simpson | Windows Embedded User Assistance | dansimp@microsoft.com

>-----Original Message-----
>Hi Everyone,
>
>We're currently working on the next Windows XP Embedded

documentation

>update, which will include many bug fixes, updates, and

new how-to

>processes.
>
>If anyone here has any issues they'd like to see addressed

in the

>documentation, please let me know. We're looking to both

improve our

>current processes and add new ones. If you have any

requests, please send

>email to: dansimp@microsoft.com or reply to this thread.
>
>Many, many thanks to all the participants here that make

this newsgroup

>community so strong!
>
>Thanks,
>
>Dan
>
>
>Dan Simpson | Windows Embedded User Assistance |

dansimp@microsoft.com

>
>
>.
>Dan,

I am looking for any documentation (preferable with
examples) that would help me make a component for a custom
VB 6.0 application. The only documentation I have been
able to find for making a application into a component
deals with very simple applications (ie. paint,hello world)
.. These simple applications are very straight foward and
require no dll registrations or registry changes. If
documentation like this is not available perhaps something
can be included in your next documentation update. I think
it would be very helpfull.

Thanks,
Manuel

Dan Simpson [MS] schrieb/wrote:

> If anyone here has any issues they'd like to see addressed in the
> documentation, please let me know.

The documentation still has references to Windows File Protection (WFP) as
if it was included in XPE. I would prefer a clear statement instead that
it's *not* part of XPE.

Thanks Manuel,

That's a great suggestion. There's a whitepaper on MSDN that details how to
componentize 3rd party application with InCtrl. If you haven't seen it,
that would be a good place to start:
http://msdn.microsoft.com/library/de...tomxpecomp.asp

We'll see about adding some of the info you requested to the docs.

Thanks!
Dan


--
This posting is provided "AS IS" with no warranties, and confers no rights.


"manuel garza" <manuel.garza@cubic.com> wrote in message
news:081d01c376e9$11228b80$a001280a@phx.gbl...

>

> documentation

> new how-to

> in the

> improve our

> requests, please send

> this newsgroup

> dansimp@microsoft.com

>
> I am looking for any documentation (preferable with
> examples) that would help me make a component for a custom
> VB 6.0 application. The only documentation I have been
> able to find for making a application into a component
> deals with very simple applications (ie. paint,hello world)
> . These simple applications are very straight foward and
> require no dll registrations or registry changes. If
> documentation like this is not available perhaps something
> can be included in your next documentation update. I think
> it would be very helpfull.
>
> Thanks,
> Manuel

Hi Dan,

This explanation of diskpart could come handy to have in XPE doc.
http://support.microsoft.com/?id=300415

And better description for boot.ini ARC names. Something from MSDN would be
nice.


Best regards,
Slobodan

I agree about the ARC paths description, we do get a lot of questions on
that one. The age old question then arises:

"But where do you draw the line when some basic level of knowledge of the NT
operating system is required when doing dev work on an Embedded NT operating
system?" <grin>

Would you be interested in writing a Tip article to be posted here:
http://www.microsoft.com/windows/emb...xp/default.asp If
you're interested in writing one for this topic or any XPe topic, please
contact me offline and i'll walk you through it.

Again, thanks for the feedback Slobodan!

Andy
--

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ========


"Slobodan Brcin" <sbrcin@ptt.yu> wrote in message
news:OraTf6udDHA.3992@TK2MSFTNGP11.phx.gbl...

> Hi Dan,
>
> This explanation of diskpart could come handy to have in XPE doc.
> http://support.microsoft.com/?id=300415
>
> And better description for boot.ini ARC names. Something from MSDN would

be

> nice.
>
>
> Best regards,
> Slobodan
>
>

Actually, I just finished adding a section about using Diskpart with WinPE.
This topic will soon be posted on MSDN, probably sometime this week.

And I think expanding on the Boot.ini ARC names would definitely be helpful.
I'll see how best we can address this specific to embedded.

Thanks for your suggestions!

Dan


--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Slobodan Brcin" <sbrcin@ptt.yu> wrote in message
news:OraTf6udDHA.3992@TK2MSFTNGP11.phx.gbl...

> Hi Dan,
>
> This explanation of diskpart could come handy to have in XPE doc.
> http://support.microsoft.com/?id=300415
>
> And better description for boot.ini ARC names. Something from MSDN would

be

> nice.
>
>
> Best regards,
> Slobodan
>
>

Please do not make the assumption that all XPe developers are Windows
programmers. I believe developers will be approaching XPe from two directions
-- from the "real" embedded world and from the Windows world. I've been
developing embedded systems and doing other kinds of "programming in the small"
for over 30 years and I've never heard of ARC paths and many of the other
conventions that must be understood in order to cope with XPe. And if I search
for "arc path" in MSDN I get lots of articles referencing it but it's very hard
to find an article explaining it. I believe the documentation should be self
contained in the sense that for any MS specific term or concept there should
either be an explanation or a reference to the explanation. Once again, using
arc path as an example there are references that further explanation exists in
the documentation but I haven't found it.

Perhaps even more important IMHO would be a review and cleanup of the runtime
error messages. I've only been at this a few weeks but I have yet to encounter
an error message that made it reasonably clear what the problem was.

Roger Levy

"Andy Allred [MS]" wrote:

>
> I agree about the ARC paths description, we do get a lot of questions on
> that one. The age old question then arises:
>
> "But where do you draw the line when some basic level of knowledge of the NT
> operating system is required when doing dev work on an Embedded NT operating
> system?" <grin>

Thanks Roger, I agree with you to a certain degree. When I have an NT OS
question, the first place I check is MSDN or http://support.microsoft.com.

Since XPe is based on XP-Pro, it's not unreasonable to expect a developer to
use that existing resource (MSDN or the KB articles) that answers thousands
of NT OS questions.

You are correct in that common NT questions that XPe devs ask *should* have
their answers duplicated in the XPe documentation such as Arc path
conventions, and we can probably do a better job here. This is why Dan
Simpson is asking for your feedback for Doc updates in another thread,
you've had some valid points this past week please feed that back to Dan.

Thanks again Roger.

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ========


"Roger Levy" <rhl@i3e.org> wrote in message
news:3F5F26BD.1AE35D45@i3e.org...

> Please do not make the assumption that all XPe developers are Windows
> programmers. I believe developers will be approaching XPe from two

directions

> -- from the "real" embedded world and from the Windows world. I've been
> developing embedded systems and doing other kinds of "programming in the

small"

> for over 30 years and I've never heard of ARC paths and many of the other
> conventions that must be understood in order to cope with XPe. And if I

search

> for "arc path" in MSDN I get lots of articles referencing it but it's very

hard

> to find an article explaining it. I believe the documentation should be

self

> contained in the sense that for any MS specific term or concept there

should

> either be an explanation or a reference to the explanation. Once again,

using

> arc path as an example there are references that further explanation

exists in

> the documentation but I haven't found it.
>
> Perhaps even more important IMHO would be a review and cleanup of the

runtime

> error messages. I've only been at this a few weeks but I have yet to

encounter

> an error message that made it reasonably clear what the problem was.
>
> Roger Levy
>
> "Andy Allred [MS]" wrote:

the NT

operating

Thanks for the insights, Roger.

I've started working on a topic wrt Boot ARC paths specific to Windows XP
Embedded. It should provide enough information to get you up and running,
and link out to other relevant MSDN articles if you want to dig deeper into
how to use the different boot.ini flags. If you like, I'd be happy to get
some customer feedback on it when it's complete. Let me know if you would
like to review it and I'd be happy to send it to you.

Coming from a non-windows embedded world myself, I will work to better
introduce and explain Windows conventions.

I abolutely agree with you about the error messages. This is something that
we are currently scoping out.

Thanks for your feedback!

Dan


--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Roger Levy" <rhl@i3e.org> wrote in message
news:3F5F26BD.1AE35D45@i3e.org...

> Please do not make the assumption that all XPe developers are Windows
> programmers. I believe developers will be approaching XPe from two

directions

> -- from the "real" embedded world and from the Windows world. I've been
> developing embedded systems and doing other kinds of "programming in the

small"

> for over 30 years and I've never heard of ARC paths and many of the other
> conventions that must be understood in order to cope with XPe. And if I

search

> for "arc path" in MSDN I get lots of articles referencing it but it's very

hard

> to find an article explaining it. I believe the documentation should be

self

> contained in the sense that for any MS specific term or concept there

should

> either be an explanation or a reference to the explanation. Once again,

using

> arc path as an example there are references that further explanation

exists in

> the documentation but I haven't found it.
>
> Perhaps even more important IMHO would be a review and cleanup of the

runtime

> error messages. I've only been at this a few weeks but I have yet to

encounter

> an error message that made it reasonably clear what the problem was.
>
> Roger Levy
>
> "Andy Allred [MS]" wrote:

the NT

operating