Re: eXP Component Documentation Sources

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 01/18/05 

Date: Tue, 18 Jan 2005 02:13:31 +0100

Hi Argus,

> I guess there is a philosophical difference in so much as some of us need to
> know that something works and some of us also need to know why it works.
> I guess it is, in part, the difference between the software and hardware
> engineering mindsets.

For this I know how you feel. I also need to know how each piece of my hardware works and how each piece of software is working.
If you are looking for big picture here then you will need to do heavy research on system internals, drivers, services and other
cool low level stuff along with high level APIs. I do not know you level of expertise so I don't know what kind of information's do
you seek.

I'm writing firmware for microcontroller devices, and also I'm in charge for driver writing and all other low level windows
programming stuff. So I'm stuck in both hardware and software worlds.

What part of documentation do you need?
- Low level like how to write install and use drivers?
- How to use native api.
- How to program in Win32 subsystem.
- How to use .NET
- DirectX
- Network related stuff.
- Boot related information's.

XP Embedded is what you make it to be by using XPe tools. All information's relevant to OS itself are contained in various articles,
XP Pro books. DDK, IFS, various SDKs.

If you want engineer point of view on things you should forget about XPe component and look at what each component will bring into
your image.
First thing that you should look is direct files and registry entries that this component will bring to your image. Concentrate on
figuring out if this is driver, service or application like component.
Then look at other components that this component depend on and analyze them. For most files you can search trough net and news
groups so you can see what they are used for and how to use them.

Download tools from this site and read articles you will find some useful info there about XP.
http://www.systeminternals.com/

Regards,
Slobodan

"Argus T" <argus.t@actek.com.au(no_spam_thanks)> wrote in message news:B514C65D-17C5-48A0-B133-1A202FC3F497@microsoft.com...
> Hello again Slobodan,
>
> I guess there is a philosophical difference in so much as some of us need to
> know that something works and some of us also need to know why it works.
> I guess it is, in part, the difference between the software and hardware
> engineering mindsets.
>
> However, I do appreciate your assistance
> Many thanks.
>
> Argus
>
> "Slobodan Brcin (eMVP)" wrote:
>
> > Hi Argus,
> >
> > I can't imagine how you feel, since I only needed to get accustomed to the tools not the OS itself.
> >
> > Basically you should know what things your target application will need like: "DirectX, Sound, Printer, Network, .NET, update
way,
> > etc" and from this you can figure out what to add so you can have all these things.
> > Now when you do have them and if there are problem then you treat and solve each problem separately.
> >
> > I do not know what else to say.
> >
> > Regards,
> > Slobodan
> >
> >
> >
> > "Argus T" <argus.t@actek.com.au(no_spam_thanks)> wrote in message news:DFFFE382-8283-465E-B612-6FED9B0A0665@microsoft.com...
> > > Hello Slobodan,
> > >
> > > Many thanks for your response, it was quite helpful but I do need more.
> > > I'd like to clarify the following;
> > >
> > > 1 I can happily handle the hardware related components using TAP, .ini
> > > files, manufacturers doco and the like.
> > > 2 What I'm seeking is a detailed listing and functional description of
> > > the "OS" components and how they fit into the big XP jigsaw. Maybe there is
> > > a book out there somewhere that gets right into the bowels of XP and that
> > > could give me the information I need
> > > 2 After checking the reviews I did order Sean's book but don't expect to
> > > receive it for some time yet (No stocks in Oz)
> > > 3 I've clipped the complete eXP help pages/tutorials/MSDN stuff into a
> > > (370 page) Word document because, being of the old school, I find fiddling
> > > round with 10~20 line help pages frustrating. They are also hard to read
> > > whilst sitting on the dunny.
> > > 4 I've also spent considerable time roaming around the web and, although
> > > I've found an occasional diamond, there's an enormous amount of sand to sift.
> > > 5 So if I'm to avoid the "brave amateur" syndrome I need to achieve a
> > > solid understanding of the core XP system components prior to launching my
> > > efforts on the world. And I haven't even started thinking about testing.
> > > Gulp!
> > >
> > > Sorry this became so wordy
> > >
> > > Best wishes
> > > Argus
> > >
> > >
> > > "Slobodan Brcin (eMVP)" wrote:
> > >
> > > > Hi Argus,
> > > >
> > > > Do you have Sean's book others say that it is excellent:
> > > > http://www.seanliming.com/books.html
> > > >
> > > > If you have time and understanding the online MSDN articles and documentation,
> > > > This News Group: http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded
> > > > And product documentation should be enough to do most things.
> > > >
> > > > Regards,
> > > > Slobodan
> > > >
> > > > PS: "Wet finger" is usually also required :-)
> > > >
> > > >
> > > > "Argus T" <argus.t@actek.com.au(no_spam_thanks)> wrote in message news:1EB54C19-DFC7-4976-A513-8AF400B11C81@microsoft.com...
> > > > > I'm coming to the eXP world with an electronic engineers mindset.
> > > > > You know the type; we want everything arranged in neat little boxes and
> > > > > compartments.
> > > > > Although eXP contains literally thousands of individual components, thus far
> > > > > I've been unable to find any meaningful reference documentation - as books,
> > > > > web resources or read-me material - that gives more than a very superficial
> > > > > treatment to odd bits and pieces of componentry. It seems that one is either
> > > > > born with a complete understanding of each component or one is destined to
> > > > > spend ones life using "wet finger" (as in which way is the wind blowing?)
> > > > > design methods.
> > > > >
> > > > > Please tell me I'm wrong and that I'm just looking in the wrong places.
> > > > >
> > > > > Many thanks
> > > >
> > > >
> > > >
> >
> >
> >

Quantcast