Jump to content











Photo

Windows Embedded Standard 7 - Add packages on a live image

wes7 live image package driver

  • Please log in to reply
9 replies to this topic

#1 ericgl

ericgl

    Frequent Member

  • Expert
  • 314 posts
  •  
    Israel

Posted 24 February 2012 - 10:05 AM

The problem:
Let's say you've installed Windows Embedded Standard 7 with SP1 (from here on: WES7), and added only the Feature Packs and Drivers that you thought were enough.
After installation, when you start configuring WES7, and adding applications - you suddenly realize that some things don't work or are entirely missing!
That is a bit frustrating, as usually it means that you'd need to start from scratch, and manually inspect each Feature Pack and Driver that you forgot to add in the first build.

The solution:
You don't need to re-build the WES7 image from scratch.
Using 7-zip and the original WES7 ISO, you can extract only the CAB files that you want to add to the currently running WES7 OS (the live image).
All the Feature Packs and Drivers are located under DSpackages inside the WES7 ISO.

Some of the CAB files have a descriptive name that you may understand what feature-pack or driver they contain, but most names are more cryptic.
Opening the INF file inside the CAB can give you a better hint of what the package actually contains.

1. Extract the needed CAB files from the ISO and the place them on the live image, for example in C:Temp.

2. Open CMD with admin rights, and type:
DISM.exe /online /Add-Package /PackagePath:C:\Temp /NoRestart

3. All the CAB packages in C:\Temp will be installed. As you can see from the command syntax, there's no need to type each package name. It automatically searches for CAB files in the given path.

4. Now restart the machine and allow WES7 to perform the updates during shut-down and restart.

That's it.

NOTE: DISM.exe should already exist in C:\Windows\System32 and C:\Windows\SysWOW64 (on the live image), so you can run the command directly from wherever the CMD window opened.

For example:
I wanted to use my USB2.0 webcam with Skype and WLM that I installed on WES7, but it didn't work even-though it showed up correctly in Device Manager.
After searching around, I found out that I forgot to add a few necessary drivers for the webcam to function correctly.
So I used dism.exe to add the following driver packages:
WinEmb-INF-hdaudss.cab
WinEmb-INF-image.cab
WinEmb-INF-ks.cab
WinEmb-INF-kscaptur.cab
WinEmb-INF-ksfilter.cab
winemb-inf-usbvideo.cab
WinEmb-INF-wdmaudio.cab


After restart, the webcam worked fine! :-)


Edited by ericgl, 06 July 2015 - 03:52 PM.

  • Nuno Brito and wimb like this

#2 sambul61

sambul61

    Gold Member

  • Advanced user
  • 1568 posts
  •  
    American Samoa

Posted 24 February 2012 - 03:05 PM

Thanks for interesting Tutorial! It would help to clarify, how one would usually build WES7 image in the first place. :)

What ways would you suggest to find out, why a particular device or feature aren't working as expected, and what exactly is missing and must be added to the image? :dubbio:

#3 Tripredacus

Tripredacus

    Frequent Member

  • Expert
  • 234 posts
  • Interests:K-Mart-ian Legend
  •  
    United States

Posted 24 February 2012 - 04:37 PM

Sometimes that isn't too easy! The documentation for 7E is quite lacking... its as if they want you to call your Embedded Partner. Anyways, I may end up trying out this method at some point... however do you also think you can install packages offline in a 7E image too?

#4 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 24 February 2012 - 08:48 PM

This is very interesting.

If we would create for each package a script, which mimiks the behavior but with a Win7 iso, we should be able to build a way more perfect PE.

:cheers:

#5 ericgl

ericgl

    Frequent Member

  • Expert
  • 314 posts
  •  
    Israel

Posted 25 February 2012 - 05:10 AM

Thanks for interesting Tutorial! It would help to clarify, how one would usually build WES7 image in the first place. :)

What ways would you suggest to find out, why a particular device or feature aren't working as expected, and what exactly is missing and must be added to the image? :dubbio:

sambul61,

The regular versions of Win7 use the "Turn Winodws Features On or Off" to check/uncheck features, and then Win7 adds/removes those features.
If you run Turn Winodws Features On or Off in WES7, you'll find-out that the window is empty and you have no regular GUI way to add/remove features.
So using DISM.exe seems to be the only option of adding missing features on a live running WES7.

WES7 is available directly from Microsoft in ISO format. Both x86 and x64 version are available. Microsoft also provides a 180-day free trial key.
The installation procedure is the same as a regular Windows 7. However, the beauty of WES7 is that it allows you to choose exactly which Features/Drivers should get installed.

There is a Help icon for each package/driver which explains what that package contains.
The same exact package descriptions are also available online here: http://msdn.microsof...bedded.60).aspx

NOTE: There is another way to install WES7. Besides x86 and x64 versions, there is also a WES7 Toolkit. This Toolkit allows, among other things, adding more drivers to the DataStore (DS), and creating an Answer File.
The Toolkit can be installed on another computer that's running Windows 7, and it contains Image Configuration Editor (ICE).
Using ICE, you can add even more drivers, and create an Answer File in XML format.
Then, when you want to actually install WES7, you can simply use this Answer File, instead of selecting features & drivers manually each time you deploy it.
You can also use the Answer File to pre-select the partitioning of the HDD, insert Product Key (if you purchased one), pre-select country/language/keyboard, etc.
So consider creating an Answer File with ICE (which simply acts as a GUI for adding/removing features from WES7) if you need to deploy many machines with the same configuration.

I simply installed WES7 the regular way, selected which packages I need, and went off with the rest of the installation.
I found-out that I was missing the webcam driver(s), so I added them with DISM.
I also found out that a certain app needed .NET Framework 3, which I also forgot to add to my image during installation. DISM took care of that as well.

Edited by ericgl, 25 February 2012 - 05:50 AM.

  • Nuno Brito likes this

#6 Tripredacus

Tripredacus

    Frequent Member

  • Expert
  • 234 posts
  • Interests:K-Mart-ian Legend
  •  
    United States

Posted 29 February 2012 - 08:26 PM

I was about to test using DISM to do an offline service of a WES7 image but I need to get more info. However, it is nice to know that using the /GET-PACKAGES switch on a mounted (offline) image does indeed work and return them all. You may need to use a redict to .txt since when I ran it I got a 100KB+ file. ;)

#7 ghosty

ghosty
  • Members
  • 1 posts
  • Location:Slovakia
  •  
    Slovakia

Posted 01 March 2012 - 10:05 PM

You can use DISMUI app created by Wolfgang Unger. In case I'm missing some packages or drivers I'll simly use DISMUI and add them to already running system (or offline system image, it doesn't matter :good: ).

http://www.elbacom.c...dismui/overview
  • ericgl likes this

#8 ericgl

ericgl

    Frequent Member

  • Expert
  • 314 posts
  •  
    Israel

Posted 02 March 2012 - 07:11 AM

Thanks for the heads-up, ghosty. Very good find.

Edited by ericgl, 02 March 2012 - 07:12 AM.


#9 lenmangmienphi

lenmangmienphi
  • Members
  • 1 posts
  •  
    United States

Posted 18 May 2013 - 04:24 PM

Hey Eric,

I came to this site when searching for WES7.  I have a question hopefully you or someone in the forum can help.

At work, I received this workstation w/ WES7 pre-installed.  I added the workstation to the domain and all users are able to logon using their domain usernames/passwords fine.  The work place will eventually going toward smartcard login.  The smartcard reader driver is installed and the software we use is ActivClient.  But when I try to login using smartcard, I receive this error "An untrusted certificate authority was detected while processing the smart card certificate used for authentication".  The same error with other smartcard users.

I think a package under "Security Credential" wasn't install when the vendor shipped the workstation.  So I plan to add the package/packages to this workstation (live image).

Any thoughts?  Thanks



#10 ericgl

ericgl

    Frequent Member

  • Expert
  • 314 posts
  •  
    Israel

Posted 18 May 2013 - 07:58 PM

lenmangmienphi,

Perhaps it's not something missing from your WES7 image.

 

Read this, and take note of the suggestion made by David Beach, from Microsoft:

http://social.techne...2b-4978d51b7c43







Also tagged with one or more of these keywords: wes7, live image, package, driver

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users