Announcement

Collapse
No announcement yet.

Windows XP Pro - Embedded or No?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows XP Pro - Embedded or No?

    I am currently evaluating XP Pro SP2 Embedded Ed. I was wondering if anyone else has thought of using this rathing than stripping down a "normal" XP install.

    What are the pros/cons of each?


    CarPuter
    ----------------------------
    Planning....[||||||||||]60%
    Parts.......[||||||||||]20%
    Construction[||||||||||]0%
    Software....[||||||||||]0%


  • #2
    Install it and we could compare with TinyXp wich I use and prefer over XP pro Normal Edition.

    Review this for us, that would be great!!
    VmtSquad - I sold my soul to Honda!
    Final Install
    CarPC progress: 95%

    Comment


    • #3
      This install fails under vista so I will need to set up a dev environment in a virtual pc running xp pro. Not sure I want to give up another 20 gigs of space for this... but I am considering it.

      What I have learned, however, is that is basically winxp pro sp2 but made modular. everything is removable, the shell, IE, directx, boot screens, everything.

      You can use any winxp driver/appliation
      You can also use any app as a shell.

      That is IF you make them a module package. Not quite sure yet what is all involved with this yet.

      Basically you develop on normal xp pro, set everything up and get everything ready, then you need 1) a second partition or 2) a second HD and you duel boot to test you install. Once your satisfied with everything, you boot back in to "normal" xp pro and create an image file for use one the target machine.

      There is also mention of using winPE for the installer but docs say it is only one of many install options.

      Minimum size of a "kernal only" install is 40mb, but M$ claims 3-10 second cold boot times with this, really usabale, install.

      The XP Pro embedded dev tools are also only good for 120 days then you need to pay (of course).


      CarPuter
      ----------------------------
      Planning....[||||||||||]60%
      Parts.......[||||||||||]20%
      Construction[||||||||||]0%
      Software....[||||||||||]0%

      Comment


      • #4
        any more on this? I'd be interested as well. I d/l a version of TinyXP (rev06?) and it won't install. no matter what option I chose, the install fails saying it can't find a file. gave up on it atm.

        Comment


        • #5
          Have a google for BulletXP. I was pointed at this, and it is the first cut down install I have tried that is fine with wireless drivers out of the box! It includes the nlite settings so you can tailor the build if needed. The only change I made was to swap the US Keyboard and locale for UK, but its working well so far.

          KPJUK
          M1000, 512MB, 512MB CF, 6GB Disk (4200rpm),
          DVD/RW, Dynamix 8" screen, M2-ATX, Custom case,Too many hours building and rebuilding and rebuild.......

          Comment


          • #6
            thanks for the tip, I'll look that up here shortly. right now I'm experimenting with an Nlite build I just made this morning. Cut my boot times down a LOT after removing a bunch of stuff. Down to about 20 seconds now after the bios screen...which is a huge improvement of about 1 minute before with a regular XP Pro install. Going to try the minlogon next and see if I can cut some times even more.

            Comment


            • #7
              I am actually a Windows XPembedded developer. It is very possible to make an embedded version of the OS for this. I *just* got into the hobby about a week ago, and am currently working on creating an embedded OS for my device, with RoadRunner as my shell. The benefit of this is that you have insanly fast boot times, with something they call HORM (Hibernate once resume many). Basically as fast as the computer can post, its there. Typically under a few seconds.

              I have a full version running now including windows media player and the .net framework that is under 200mb.

              You can visit the MS windows embedded homepage here for more info:
              http://msdn2.microsoft.com/en-us/embedded/default.aspx

              Comment


              • #8
                Would you mind sharing your .slx file? I've d/l the demo version of all the software, however it seems that no matter how I build it, I always end up missing something somewhere. Sometimes it's apparent right away, other times it's not until I'm almost done setting up everything from Wireless connections to RoadRunner and GPS apps.

                Comment


                • #9
                  Might be worth listing as well what services you can 'safeley' disable from bootup, ive been experimenting with nlite, using a TinyXP lastsession.ini, I know theres already alot of material on the web, but its hard to know which ones are essential for safe running on a car pc, i def disable these

                  - Printspooler
                  - Indexing service
                  - Fast user switching
                  CarPuter Progress:
                  Planning:-----> [||||||||||] 100%
                  Hardware Buying:-> [||||||||||] 100%
                  Software:-----> [||||||||||] 100%
                  Installing:-----> [||||||||||] 100%
                  Current Project= Making skins in photoshop...

                  Comment


                  • #10
                    sorry to hijack, but I am thinking of possibly going the embedded route, because of the boot times and possibly better power consumption. With the embedded systems, does it still opperate like a normal windows version? What are some limitations? Can VB.NET be used to develope the front end software for this still?

                    Thanks

                    Comment


                    • #11
                      if you use XP Embedded you can keep or remove whatever you want, so yes you could include the .NET Framework. it's just a matter of understanding what OS features you need and building the right image.
                      EWF, HORM, MinLogon on XP.

                      Zotac ION Atom N330, 2GB low-profile RAM, M3-ATX
                      Win Embedded Std 2011 RC
                      OCZ Vertex Turbo 30GB SSD
                      Lilliput 629 Transflective, WRX Screen Mount
                      BlueSoleil BT, i-Blue GM-2 GPS, DirectedHD Radio, Andrea Mic
                      VoomPC 2

                      Comment


                      • #12
                        Originally posted by jonessc View Post
                        Might be worth listing as well what services you can 'safeley' disable from bootup, ive been experimenting with nlite, using a TinyXP lastsession.ini, I know theres already alot of material on the web, but its hard to know which ones are essential for safe running on a car pc, i def disable these

                        - Printspooler
                        - Indexing service
                        - Fast user switching
                        +1
                        A computer helps you make more mistakes faster than any invention in human history
                        - with the possible exceptions of handguns and tequila.

                        Comment


                        • #13
                          I recently received some tools for embedded development (http://www.sjjmicro.com/XPES_Tools_R2.html) so hopefully I will have a working embedded installation soon

                          Comment


                          • #14
                            With the embedded systems, does it still opperate like a normal windows version?
                            It is exactly like normal, standard WinXP, you just componentize it to suit your application - one caveat though, there is a special method of "patching" or applying hotfixes, but this wouldn't be that essential in a carputer if not connected to the internet all the time.

                            If it is, then there is a fair bit of work involved in rolling out this runtime patches.

                            But, it is fun to play with, very, very flexible, and allows you to componentize each and every driver for your system, same with applications - it's a lot of work, and trial and error, capturing registry changes, importing them and creating components - but, once this is done for your system, roll-outs are so simple, quick, and clean!! To top it off, once the First Boot Agent (FBA) has done it's thing after startup, everything just works - all the drivers are there, no need for post-installation actions.....I told you it was nice...

                            I am at this point with my design, all drivers componentized, embedded, WiFi, Realtek sound, VGA, Chipset, but, the Realtek sound gave me the crap when componentizing, working now though.

                            Next on the agenda is the time-consuming application components-design/testing, ie Centrafuse, OBD-II interfaces, etc...

                            Enjoy, it's fun.
                            F6 Tornado Project Log ; HP Blackbird Watercooled Server

                            Beta Tester for Centrafuse and 3dConnexion (No business affiliation with either)

                            Comment


                            • #15
                              My problem with xp embedded has been deployment.

                              I've been unable to figure out a way to deploy the resulting image onto my laptop without having to use an annoying RIS server etc. I personally would like to just burn a cd and do a standard install

                              Anyone have insight to offer into this?

                              Comment

                              Working...
                              X