XP Embedded

[whumphrey]

Originally Posted by midiwall

I understand this side and I agree with it as well. But... As an example, someone asked if the next step in the process after verifying on a VM was to recreate for the target hardware - you jumped him pretty hard and that spun into the spoon-feeding rant. The guy asked a straight question, he was basically asking if the XPe image had to be re-genned; it was clear to me that he didn't understand the core process and needed one small line connected.

Well if he had done one simple google he would have had his answer and not needed to ask the question! Thats the reason he got a slating, because it was the first thing i did, just to check if someone had already covered that! If he had done any research on XPe he would have known the answer.....

Originally Posted by midiwall

Well, it depends on what you were looking to accomplish with the docs. Is it a tutorial, an overview, a conceptual bullet list, etc?

If you look at my post Windows XP Embedded - HOWTO
it states :

I quickly whipped up my yesterdays findings on using Windows XP Embedded and VMware.

I would like to keep this one and the XPe and Centrafuse tuts separate as they not really the same thing. One is how to use XPe and the other would be how to get CF to work with XPe.

Originally Posted by midiwall

If it's a tutorial then it really should be step-by-step through the process explaining the WHY along the way - "WHY are you using a VM?" "WHY XPe?", along with a good dose of WHERE - "WHERE do I get the tools?", "WHERE do I get the core XPe image?", and finally HOW - "HOW do I determine what drivers I need for _MY_ hardware?".

Well, if no one gives me feedback in that forum or in PM how am I meant to know?

Originally Posted by midiwall

As it stands now, the document spends more time explaining how to create a VM than anything else.

Thats all that the document is meant to do, hence the title "How to use Windows XP Embedded using Vmware Workstation 6.pdf"

Originally Posted by midiwall

If you don't mean for this to be a tutorial, then declare it as just a high-level overview - in the document itself - and clearly state that it's only meant to be a starting point, _and_ state that you don't really have the time/patience to answer questions. It's okay if you take that line, but as it is now, no one here knows that about you.

I do have the time and patience to answer any questions as long as the person asking them is asking relevant questions that are not already been answered.

I always used to say to people that came to me with "I need to ask you a stupid question" that there is no such thing as a stupid question, over the past years I have noticed the M$ community asking stupid questions..... I now do be leave people ask pathetic idiotic questions as its there right in front of them!!! When i lived in a third world country and not everyone had access to the net or limited access I could understand. But asking a question on a forum because you to bloody lazy to research it is no excuse. You asking on a forum so you have internet access, you just to bloody lazy to research your ****.......

Originally Posted by midiwall

The overall effect right now is that you've tossed folks a large bone, asked them to come feed off of it, and are then kicking them in the face when they show you how hungry they are.

Originally Posted by midiwall

Thanks for being open to talking about this side of your efforts.

Who said i was open for talking? Just kidding, yea if i was such a prick as most people make out I guess i would not be open about it.... My main thing is people don't spend anytime before asking questions is what gets my beef.......

--me
P.S. One just to stir things up

[MrBean]

No that would be more like illegal warez, which I can guarantee you is not allowed on this forum.....

Nope, it won't be.

If you have a legal full XPE developers kit, you had to sign an OEM agreement with MS, and that also entitles you to buy and supply runtime licenses for your XPE images

So, if he asks you for an image, you can gladly provide him one, with a runtime license, at approximate cost of $100.

And, if you don't provide a license (which you'e not allowed to do), the image will anyway expire between 120-180 days from first init.

Have fun.

[whumphrey]

Originally Posted by MrBean

If you have a legal full XPE developers kit, you had to sign an OEM agreement with MS, and that also entitles you to buy and supply runtime licenses for your XPE images

I am using the Microsoft Windows XP Embedded, SP2 Update Evaluation Edition, but have just started on Windows Embedded Standard 2009 Evaluation now...

Originally Posted by MrBean

So, if he asks you for an image, you can gladly provide him one, with a runtime license, at approximate cost of $100.

I cant!!!

Originally Posted by MrBean

And, if you don't provide a license (which you'e not allowed to do), the image will anyway expire between 120-180 days from first init.

Yes I could, but i ain't building images for everyone....

See: - Windows XP Embedded Licensing Requirements and Guidelines

[guybrush]

Originally Posted by whumphrey

just use google and see how much documentation will point you at Target Analyzer Probe (TAP) and your question would have been answered.

I've searched for hours now in google with keywords "centrafuse+xp+embedded+components" and couln't find any _relevant_ documentation, about what components I need to integrate into the image to get centrafuse with bluetooth dongle, gps, etc. running... :?

I would like to keep this one and the XPe and Centrafuse tuts separate as they not really the same thing. One is how to use XPe and the other would be how to get CF to work with XPe.

I've got XPe working from your first tutorial, now I wanted to move on to the next (getting CF running with XPe), but couldn't find your second tutorial: "XPe and Centrafuse" on the net...

[MrBean]

@ Guybrush:

Have a looky here, there's tonnes of links and info you're after - this is what I'm using to guide me if I get stuck, so you might wanna bookmark this thread.

There's a fair bit of work involved in componentizing drivers and apps, but well worth it.

Have fun, and keep us posted of your progress.

Br,
MrBean.

[guybrush]

Originally Posted by MrBean

@ Guybrush:

Have a looky here, there's tonnes of links and info you're after - this is what I'm using to guide me if I get stuck, so you might wanna bookmark this thread.

There's a fair bit of work involved in componentizing drivers and apps, but well worth it.

Before I even can find out what components to compontize I would have to know ALL the dependencies a fully working centrafuse with bluetooth and gps is having.

As this is _a lot of a hassle_ I would be very glad to not have to invent the wheel from the beginning and rather use the components others have already created.

[whumphrey]

Originally Posted by guybrush

Before I even can find out what components to compontize I would have to know ALL the dependencies a fully working centrafuse with bluetooth and gps is having.

As this is _a lot of a hassle_ I would be very glad to not have to invent the wheel from the beginning and rather use the components others have already created.

Look at the component's I used which is attached to this thread!

[MrBean]

@ Guybrush: Mmm...use TAP.exe as a start, and componentize your hardware to your liking, to get a basic system working, and be able to get to desktop.

Then, you can start adding on all the required software, like .net etc.....it's a lot of trial and error, but fun too

As Whumphrey has mentioned, look at the comonents he have used.

You can then trim to your liking.....

edit: Anyway, when you start componentizing the applications, you will use various tools to capture all the dll's, paths, registry-entires, etc, required to make a specific application work.

When you build your image, it will check dependencies, and notify you of missing components or dll's etc.....then you would know what to add, ie .net, or JET or whatever.

Same is true for both Centrafuse and GPS application, or system drivers.....it's a repetitive process, and obviously the applications will require a lot more work than drivers.

Dave from Fluxmedia: Maybe a good thing if you guys can use your software connections to do a component for Embedded XP I am sure it will be worth your while.......hehe

[David]

we are hoping that some great users like yourself will help us get the official dependency list with the wording from the XPe kit so we can keep it posted and update for future users

david

[Ryan711]

I have a list of all registry key changes and files that are used when CF is installed. Though it may not be complete, it might be a start for someone willing to decipher it.

I acomplished it through a program called thinstall, which basically is used to make any application portable. It does so by do a prescan of all files/registry on the machine, then you install the program and run the postscan and it detects any new files/registry values created. So I just used it for that.

Like I said i'm not sure if the list is complete. I chose not to install the speech or bluetooth so those are not in the included files/registry values I will post.

Most of the registry stuff is indecipherable to me, The thinstall program spits it out in a weird format. I tried renaming it to a .reg file and importing it into XPe component designer, but was unsucessful.

Well here is the stuff I have so far. Since there are many files to list individually, I've used a program called primitive disk indexer which can be downloaded free right here(Primitive Disk Indexer - Software for indexing CDs, DVDs and any other types of disks). This allows me to take a snap shot of a directory including all subfolders and files. All you need to do is open the program and open the file I will attach and you will see all the files in the directory.

The reg files.zip I will attach are the registry keys that changed.

I'm working on creating a CF component, but haven't had the time to really delve into it. So hopefully someone can make better use of this information than I can.