Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Mr Jinje DISM Tool™


  • Please log in to reply
114 replies to this topic

#51
Alpha_95

Alpha_95

    Newbie

  • Member
  • 20 posts

Hello

i found out why... so now it works again..


Could you explain what you did to solve this problem?
I'm in the same situation as you now ...


How to remove advertisement from MSFN

#52
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,032 posts
  • OS:none specified
  • Country: Country Flag

Hello

i found out why... so now it works again..


Could you explain what you did to solve this problem?
I'm in the same situation as you now ...

i have now add packages in the dismtool. and i have too install Danish packages..

but how do i make to it install danish instead of english.

I'll assume you are referring to this MitsuMan post. He never posted how he fixed the issue, so I can only guess.

Probably need to use an unattend.xml and specify the language. Report back.

These are the settings I use for english (obviously it is not a complete unattend.xml - that would be beyond the scope of this thread)

<InputLocale>en-us</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UserLocale>en-us</UserLocale>


Otherwise, there has been some chatter about lang.ini, but I never took the time to google it. That would be the second place I would look.

The Lang.ini file

If you deploy Windows using Windows Setup and you have added or removed language packs from the distribution share, you must recreate the Lang.ini file. Windows Setup uses the Lang.ini file to identify the language packs inside the image and within the Windows distribution share. The Lang.ini file is also used to identify the language that will be displayed during Windows Setup. Regenerating the Lang.ini file is also necessary if you plan to create recovery media for images that contain multiple languages.

You can use DISM international servicing command-line options to recreate the Lang.ini file based on any language-pack updates. Do not modify the Lang.ini file manually. For more information, see Languages and International Servicing Command-Line Options.

EDIT: On second look, probably just need run the Gen-LangINI command.

/Gen-LangINI:

Generates a new Lang.ini file, which is used by Setup to define the language packs inside the image and outside in the distribution. It also defines the default UI language for Setup.

The new Lang.ini file will be added to the Sources folder of the Windows distribution.
noteNote
You will not be prompted for permission to overwrite an existing Lang.ini file. The existing Lang.ini file will be overwritten automatically.

You must specify an offline Windows image (/Image:<path_to_offline_image.wim> and a distribution (/Distribution:<path_to_distribution_directory>).

Example:

Dism /image:C:\test\offline /Gen-LangINI /distribution:C:\windows_distribution


<Note To Self>add gen-langini to next version.</Note To Self>

Edited by MrJinje, 26 December 2009 - 03:46 PM.


#53
nice_guy75

nice_guy75

    Advanced Member

  • Member
  • PipPipPip
  • 406 posts
Not working in my case "error 87"

#54
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,032 posts
  • OS:none specified
  • Country: Country Flag

Not working in my case "error 87"

You have a space in your file path, rename your folder or move Install.WIM to the root of your drive.

A quick search would have turned up this.

Error87 is usually related to a space in the Install.WIM path. The fix has been to move the files to a space without path or the root of the drive.


Edited by MrJinje, 03 January 2010 - 11:58 AM.


#55
killalot

killalot
  • Member
  • 9 posts
I must be an id***,or I'm loosing the plot,probably an id*** my daughter did call me one the other night.I've copied my windows 7 disk to the hardrive I've got all the hot-fixes that i want to install but haven't a clue how you use Mr Jinje Tool.
When you say Click Mount Wim etc at a complete lose.Can someone give me a quick id*** guide on how you use this program cheers.

#56
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,032 posts
  • OS:none specified
  • Country: Country Flag
Posted Image

Mount WIM is in the Upper Left corner. To give you an idea of what each command might do, here is the M$ documentation that I followed.

When you click it, it will prompt you to choose both an empty folder (to mount the WIM inside) and your Install.wim from the sources folder. There can be no spaces in the path names. It will take the WIM about a minute or three to mount depending on your HDD speed.

Next, you will click the "Add-Packages" button and it will prompt you to choose your folder that is full of hotfixes. When you hit the final OK, they will be integrated into your WIM packages, it may take some time to complete so be patient.

Afterwards to save these changes, click Commit WIM button (below Mount WIM button).

Finally after the WIM is saved, hit the DisMount WIM button to remove the mount point.

#57
killalot

killalot
  • Member
  • 9 posts
Thanks for the help i think i'm getting there,after i've added what i need etc do i still need to use vlite to build the image?Also i got this error..
error 87 dism doesnt recognize the command line option "7" is it something i should be worried about.

Its ok worked out what the error was had spaces between the words,still not sure about the vlite.

Edited by killalot, 20 January 2010 - 02:36 AM.


#58
cluberti

cluberti

    Gustatus similis pullus

  • Supervisor
  • 11,250 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag
No need to use vLite if all you want to do is package up the image onto an installable medium (or make an ISO out of it for burning to DVD) - that's what oscdimg.exe from the WAIK is for.

To make a Win7 bootable ISO via oscdimg, you would execute the following command from a "Deployment Tools Command Prompt" under the Windows AIK folder in the start menu (where D:\Win7\ISO is the folder containing the Win7 source you've modified, and D:\Win7.iso is the ISO file you want to create - change as necessary/desired):
oscdimg -u2 -m -o -h -lWIN7 -b"C:\Program Files\Windows AIK\Tools\PETools\amd64\Boot\etfsboot.com" D:\Win7\ISO D:\Win7.iso
Note the above command assumes you're doing this to an x64 installation of Windows - if you're running the command on a 32bit (x86) installation source, replace "amd64" in the above command with "x86" (everything else is the same). This command takes the Windows 7 DVD source from "D:\Win7\ISO" and creates a bootable ISO image "D:\Win7.iso" that you can burn to DVD (or test in a VM, etc).
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
--------------------
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!

#59
killalot

killalot
  • Member
  • 9 posts

No need to use vLite if all you want to do is package up the image onto an installable medium (or make an ISO out of it for burning to DVD) - that's what oscdimg.exe from the WAIK is for.

To make a Win7 bootable ISO via oscdimg, you would execute the following command from a "Deployment Tools Command Prompt" under the Windows AIK folder in the start menu (where D:\Win7\ISO is the folder containing the Win7 source you've modified, and D:\Win7.iso is the ISO file you want to create - change as necessary/desired):

oscdimg -u2 -m -o -h -lWIN7 -b"C:\Program Files\Windows AIK\Tools\PETools\amd64\Boot\etfsboot.com" D:\Win7\ISO D:\Win7.iso
Note the above command assumes you're doing this to an x64 installation of Windows - if you're running the command on a 32bit (x86) installation source, replace "amd64" in the above command with "x86" (everything else is the same). This command takes the Windows 7 DVD source from "D:\Win7\ISO" and creates a bootable ISO image "D:\Win7.iso" that you can burn to DVD (or test in a VM, etc).


OK thanks,I've managed to create a windows 7 disk with the hotfixes,got no errors wile creating it with Mr je jins dism tool,great program, only problem after i installed the disk i created, i ran windows update just to see if any updates i needed it listed 10 but 6 in the 10 listed i already had installed when i did the disk?
Any suggestions.

#60
cluberti

cluberti

    Gustatus similis pullus

  • Supervisor
  • 11,250 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag
Well, I would suggest providing a list of the installers (package names) that were integrated, and then a list of the 6 of those 10 that still show up once installed is a start. Next, if you were able to run dism against the .WIM file (and image index) that these packages were integrated into showing a list of packages that are in the image, that'd be useful as well:

To mount the WIM:		 Dism /Mount-Wim /WimFile:D:\Win7\ISO\sources\install.wim /index:1 /MountDir:D:\mount
To get the package list:  Dism /image:D:\mount /Get-Packages /Format:Table
To unmount the WIM:	   Dism /Unmount-Wim /MountDir:D:\mount /discard

Again, replace "D:\Win7\ISO\sources\install.wim" with the path to the WIM file we're talking about, replace the # in "/index:#" with the index # of the instance inside the WIM you actually slipstreamed the packages into, and replace "D:\mount" with the folder you'd like to use to hold the WIM file while mounted.
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
--------------------
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!

#61
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,032 posts
  • OS:none specified
  • Country: Country Flag

replace the # in "/index:<#>" with the index # of the instance inside the WIM you actually packaged

In the past these were usually a case of mistaken image identity, one reader accidentally integrated his updates into image #1 not knowing that image #5 (#4 on x64) was actually the Ultimate he was looking for.

Ok what did i miss, cause I don't see any mention of which image Index is which, other then here that says 4 is Ultimate .

Didn't miss anything, I mistakenly assumed everyone was familiar with the WIM image format and never posted the list.

Here you go - These are the default images inside an untouched ISO - obviously vLite users who remove all images can disregard. they only have 1 image in their iso's

x86

1 - Starter
2 - Home Basic
3 - Home Premium
4 - Professional
5 - Ultimate

x64

1 - Home Basic
2 - Home Premium
3 - Professional
4 - Ultimate

Hope that helps.



#62
killalot

killalot
  • Member
  • 9 posts

replace the # in "/index:<#>" with the index # of the instance inside the WIM you actually packaged

In the past these were usually a case of mistaken image identity, one reader accidentally integrated his updates into image #1 not knowing that image #5 (#4 on x64) was actually the Ultimate he was looking for.

Ok what did i miss, cause I don't see any mention of which image Index is which, other then here that says 4 is Ultimate .

Didn't miss anything, I mistakenly assumed everyone was familiar with the WIM image format and never posted the list.

Here you go - These are the default images inside an untouched ISO - obviously vLite users who remove all images can disregard. they only have 1 image in their iso's

x86

1 - Starter
2 - Home Basic
3 - Home Premium
4 - Professional
5 - Ultimate

x64

1 - Home Basic
2 - Home Premium
3 - Professional
4 - Ultimate

Hope that helps.



I see,I didn't realise you had to do that I thought all the hotfixes etc where applied to all version.Do you just select which version with the drop down box,1-7.In my case x64 ultimate will be number 4

#63
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,032 posts
  • OS:none specified
  • Country: Country Flag

Do you just select which version with the drop down box,1-7.In my case x64 ultimate will be number 4

Yes

#64
killalot

killalot
  • Member
  • 9 posts

Do you just select which version with the drop down box,1-7.In my case x64 ultimate will be number 4

Yes


Cheers,i have done the disk now and applied what i needed,thanks for the help. :thumbup

#65
gotenks98

gotenks98

    Member

  • Member
  • PipPip
  • 162 posts
I am going to give this tool a try. Does anyone know if it will intergrate drivers that are unsigned in 64-bit or do I have to do all of those manually with the forced command?

#66
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,032 posts
  • OS:none specified
  • Country: Country Flag
This doesn't use the force command (run it separately if you need) but it seems to integrate them, because I get a pop up during installation asking permission to install an unsigned driver.

#67
gotenks98

gotenks98

    Member

  • Member
  • PipPip
  • 162 posts

This doesn't use the force command (run it separately if you need) but it seems to integrate them, because I get a pop up during installation asking permission to install an unsigned driver.

Any chance you can add this force command functionality in future revisions? Its pain to sort out which drivers need to be redone when you got like 200+ drivers.

#68
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,032 posts
  • OS:none specified
  • Country: Country Flag
I would try something like this first.

Dism /Image:D:\Mount /Add-Driver /Driver:D:\Drivers /Recurse /ForceUnsigned

report back if that allows you to force all 200 of your drivers in a single command.

#69
ricktendo

ricktendo

    Group: Banned Members

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,295 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Or use dir /b switch to get a list of the INF files

for /f %i in ('dir /b "X:\Unsigned\*.inf"') do dism /image:X:\mount /add-driver /driver:"X:\Unsigned\%i" /forceunsigned


#70
Gremo

Gremo

    Member

  • Member
  • PipPip
  • 101 posts
a (really really) stupid question: integrate cert/insert key is used to get windows 7 already activated on install? I'm trying to achieve this on my notebook but i don't know here to find the cert file...

Thanks

#71
MrJinje

MrJinje

    Tool™ Developer

  • Developer
  • 1,032 posts
  • OS:none specified
  • Country: Country Flag

a (really really) stupid question: integrate cert/insert key is used to get windows 7 already activated on install? I'm trying to achieve this on my notebook but i don't know here to find the cert file...

Thanks

That only works for OEM computers that came with Windows 7 originally.

See this article

If you have an Windows 7 OEM computer you might be able to find the proper certificate in your "C:\Windows\System32\OEM" folder. As for the OEM key, do not use the one on your sticker. That will not work because that key is retail COA not OEM:SLP. Run a product key checking tool on the machine to determine what Product Key your machine is really using, then use that key.

Otherwise, if you do not have a Windows 7 OEM machine, forget it, that method will not work for you (but driver integration still should).

#72
maxXPsoft

maxXPsoft

    MSFN Master

  • Developer
  • 2,880 posts
  • OS:Windows 7 x64
  • Country: Country Flag
open admin cmd prompt and type slmgr -dli
if OEM then then under description it will say OEM_SLP channel
or type this for more slmgr -dli | slmgr -xpr | slmgr -dlv
Download ++> Windows 7 + 8 Unattended DVD + App Installer + Services Disabler + Load All Button + XML Creator
Jump2Reg - Registry: - Oct 4, 2013 - Version 3.0.4 - 98, ME, NT, 2K, XP, VISTA, Seven, Windows 8+ and 32 or 64 bit

XP Unattended CD/DVD creator - Version 4.1.7
Sample xml + Setupcomplete + Add Right click .wim Windows 7 or Windows 8/8.1

#73
Gremo

Gremo

    Member

  • Member
  • PipPip
  • 101 posts

open admin cmd prompt and type slmgr -dli
if OEM then then under description it will say OEM_SLP channel
or type this for more slmgr -dli | slmgr -xpr | slmgr -dlv

This is what i get:


Posted Image

So what should i do if it's OEM?

#74
MagicAndre1981

MagicAndre1981

    after Windows 7 GA still Vista lover :)

  • Patrons
  • 5,940 posts
  • OS:Vista Ultimate x86
  • Country: Country Flag

Donator

You are using the Key from the Product Stocker (COA), not the generic SLP Key from OEM.
Posted Image

#75
Gremo

Gremo

    Member

  • Member
  • PipPip
  • 101 posts

You are using the Key from the Product Stocker (COA), not the generic SLP Key from OEM.


This is a clean install of windows 7 homepremium x64 retail, with product key on the laptop cover, phone activation. No chance to get the activation file and put them on dvd? :(




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN