BetaArchive Logo
Navigation Home Database Screenshots Gallery Image Uploader Server Info FTP Servers Wiki Forum RSS Feed Rules Please Donate
UP: 75d, 9h, 55m | CPU: 68% | MEM: 6482MB of 12287MB used
{The community for beta collectors}

Post new topic Reply to topic  [ 13 posts ] 
Author Message
 PostPost subject: [GUIDE] How to convert WIM to i386 installation form        Posted: Thu Sep 06, 2012 2:17 pm 
Reply with quote
Donator
User avatar
Offline

Joined
Thu Mar 31, 2011 8:24 am

Posts
776

Favourite OS
6001
Last days many people ask me for this - How to convert this or that build from install.wim to be installed via old i386 technology.

So I decide to write a guide, and put some tips and hints in it, detailed GUIDE STEP-BY-STEP.

So lets begin.

This guide will be based for Re-packing of Longhorn build 4051


0) Requirements: Build 4051 32 and 64-bit ISO images, VMware Workstation 8 or 9.

1) Get Longhorn build 4051 PDC Disk, select install Longhorn (clean install).

2) Installation:
Quote:
- section 1: Windows setup will copy all setup files needed (WinPE files and Longhorn system img - install.wim)

- section 2: Windows PE will copy all Longhorn system files to target drive.

- When automatically restart come, turn off your Virtual Machine - you must stop here! - before setup section 3 started.

(section 3: Windows Longhorn use sysprep setupmode to detect hadrware ,install drivers and signhash CD-KEY)
(end-section: boot to normal mode)


3) Create this directories:
Quote:
\LH4051
\LH4051\i386
\LH4051\i386\system32
\LH4051\temp


4) Mount VHD of your VM and copy all files
Quote:
from
\windows\i386
to
\LH4051\i386


copy all files
Quote:
from
\windows\Microsoft.NET\Framework
to your work dir
\LH4051\temp


When I said all files I think out of their directories, to make this, search in this folder for dot, just put simbol "." (without quotes) and you will get all files and folders listed. This list order by "type" so select all files but no folders.
And copy them all like I said in \LH4051\temp

5) Make this dir \LH4051\temp\i386\lang

6) This files should be in in your work dir \LH4051\i386

asms01.cab (you can use LH4051 x64 version files)
autochk.exe
autofmt.exe
bootfix.bin
cabinet.dll
clfs.sys
dbgeng.dll
dbghelp.dll
docs.cab
dosnet.inf
dotnetpe.cab (you can find it in LH4051 DVD \source)
driver.cab
drvindex.inf
drvmain.sdb
eula.txt
expand.exe
fp50ext.cab
gpscript.exe
helpcab.cab

Quote:
hivecls.inf (you can use XP/2003/LH4008/LH4015/LH4029 version files)
hivedef.inf (you can use XP/2003/LH4008/LH4015/LH4029 version files)
hivesft.inf (you can use LH4051 x64 version files by replace "wow6432node\" with "")
hivesxs.inf (you can use LH4051 x64 version files by cut half lines within "amd64", but keep all lines within "x86" and replace "amd64" with "i386")
hivesys.inf (you can use LH4051 x64 version files by replace "wow6432node\" with "")
hiveusd.inf (you can use XP/2003/LH4008/LH4015/LH4029 version files)
hivewin.inf (you can use LH4051 x64 version files, it's really null)


hwdb.dll
imagehlp.dll
ims.cab
ims.cat
intl.inf
kbd101.dll
kbd101a.dll
kbd106n.dll
kbda1.dll
kbda2.dll
kbda3.dll
kbdal.dll
kbdarme.dll
kbdarmw.dll
kbdax2.dll
kbdaze.dll
kbdazel.dll
kbdbe.dll
kbdbene.dll
kbdblr.dll
kbdbr.dll
kbdbu.dll
kbdca.dll
kbdcan.dll
kbdcr.dll
kbdcz.dll
kbdcz1.dll
kbdcz2.dll
kbdda.dll
kbddiv1.dll
kbddiv2.dll
kbddv.dll
kbdes.dll
kbdest.dll
kbdfa.dll
kbdfc.dll
kbdfi.dll
kbdfo.dll
kbdfr.dll
kbdgae.dll
kbdgeo.dll
kbdgkl.dll
kbdgr.dll
kbdgr1.dll
kbdhe.dll
kbdhe220.dll
kbdhe319.dll
kbdheb.dll
kbdhela2.dll
kbdhela3.dll
kbdhept.dll
kbdhu.dll
kbdhu1.dll
kbdibm02.dll
kbdic.dll
kbdindev.dll
kbdinguj.dll
kbdinhin.dll
kbdinkan.dll
kbdinmar.dll
kbdinpun.dll
kbdintam.dll
kbdintel.dll
kbdir.dll
kbdit.dll
kbdit142.dll
kbdkaz.dll
kbdkyr.dll
kbdla.dll
kbdlk41a.dll
kbdlk41j.dll
kbdlt.dll
kbdlt1.dll
kbdlv.dll
kbdlv1.dll
kbdmac.dll
kbdmon.dll
kbdne.dll
kbdnec.dll
kbdnec95.dll
kbdnecat.dll
kbdnecnt.dll
kbdno.dll
kbdpl.dll
kbdpl1.dll
kbdpo.dll
kbdro.dll
kbdru.dll
kbdru1.dll
kbdsf.dll
kbdsg.dll
kbdsl.dll
kbdsl1.dll
kbdsp.dll
kbdsw.dll
kbdsyr1.dll
kbdsyr2.dll
kbdtat.dll
kbdth0.dll
kbdth1.dll
kbdth2.dll
kbdth3.dll
kbdtuf.dll
kbdtuq.dll
kbduk.dll
kbdur.dll
kbdurdu.dll
kbdus.dll
kbdusa.dll
kbdusl.dll
kbdusr.dll
kbdusx.dll
kbduzb.dll
kbdvntc.dll
kbdycc.dll
kbdycl.dll
ksecdd.sys
layout.inf
mglegacy.cab
mmssetup.cab
monsrv.cab
msrdp.cab

Go in your temp folder where are all files from NetFramework folder and from command prompt (CMD) run this command
Quote:
cabarc -m lzx:21 n netfx.cab *
And you will get netfx.cab, so put it in \i386 like other files. If you don't have CabArc you can download from here build 4074

netsetup.exe
noise.chs
noise.cht
noise.eng
noise.enu
ntdetect.com
ntdll.dll
ntfs.sys
ntldr
ntoskrnl.exe
ntprint.cat
ntprint.inf
ntsd.exe
osc.cab
pidgen.dll
prodspec.ini
progs.cab
progsx86.cab
regedit.exe
rmclient.cab
setupacc.txt
setupldr.bin
setupp.ini
setupreg.hiv - changing this file via regedit can resolve with removing timebomb (PM me for this)
smss.exe
spcmdcon.sys
sysparse.exe
telnet.exe
txtsetup.sif
usetup.exe

Quote:
windows.cab (you can use LH4051 x64 version files,) - this file contains files from winsxs - and sometimes maybe so problematic to give you a fatal error

winnt.exe (you can use XP/2003/ LH4008/4015/4029 version files)
winnt32.exe (you can use XP/2003/ LH4008/4015/4029 version files)
winnt32.hlp (you can use XP/2003/ LH4008/4015/4029 version files)
winnt32.msi (you can use XP/2003/ LH4008/4015/4029 version files)
winnt32a.dll (you can use XP/2003/ LH4008/4015/4029 version files)
winnt32U.dll (you can use XP/2003/ LH4008/4015/4029 version files)
winntbba.dll (you can use XP/2003/ LH4008/4015/4029 version files)
winntbbu.dll (you can use XP/2003/ LH4008/4015/4029 version files)

wsdu.dll
wsdueng.dll

NOTE: some longname files must be renamed, these files can be found in txtsetup.sif, look like:
This is the hardest part, so I can make easier for you - just use this script put it in LH4051\i386 and run it from there. The script will rename almost all files (on the end check for some long name maybe is still there if yes check his short name in txtsetup.sif and rename it)
Quote:
System.Collaboration.dll -> rtcapi.dll
Microsoft.Collaboration.dll -> rtcprov.dll
Interop.RtcDll.dll -> rtcint.dll
Interop.RtcDll.dll.manifest -> rtcint.man
Location.SvcWrap.exe -> locsvcwp.exe
...etc


7)
Quote:
copy from XP/2003 CD
\i386\daw
\i386\compdata
\i386\winntupg
\i386\winntmig
to \LH4051\i386

8)
copy \LH4051\i386\ntdll.dll to \LH4051\i386\system32
copy \LH4051\i386\usetup.exe to \LH4051\i386\system32, and then rename it to "smss.exe "

9)copy Longhorn For PDC DVD disk1
\x86\docs
\x86\support
\x86\valueadd
\x86\ setup.exe
(you need to rehack it's install path, with PE Explorer)
\x86\autorun.inf
\x86\win51
\x86\win51ip
\x86\readme.htm
to \LH4051\

Optional Compressing:
You can compress all files for example from .exe to get .ex_
Move all: DLL, EXE, MAN, files to other folder
and put there two makecab files and run the cmd file
after that sort all files by date and move back only files with "_" in end of their names.

Optional Adding: SATA drivers in TXT (F6) Mode
Image


10)
Remove all temp folder and files.
Use nLite to build ISO file

Good luck!


Last edited by maxtorix on Fri Dec 28, 2012 11:30 pm, edited 2 times in total.

Top  Profile  WWW
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Thu Sep 06, 2012 7:09 pm 
Reply with quote
FTP Access
Offline

Joined
Wed Jun 11, 2008 11:32 pm

Posts
126

Favourite OS
Windows Server 2003 SP2 x64
What are the benefits of an i386 install over WIM? I'm genuinely curious as I've seen it mentioned once or twice now but as I have no interest in it I've never particularly bothered finding it out.

_________________
2012 13" MacBook Pro - 2.5GHz i5, 16GB 1600MHz RAM, 512GB Vertex 4 SSD.


Top  Profile
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Thu Sep 06, 2012 9:03 pm 
Reply with quote
Donator
Offline

Joined
Sat Feb 24, 2007 4:14 pm

Posts
6612

Location
United Kingdom

Favourite OS
Server 2012 R2
There aren't any.

_________________
BuildFeed - the ultimate collaborative NT build list - Windows Longhorn - a look at a defining Microsoft project


Top  Profile  WWW
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Fri Sep 07, 2012 11:13 am 
Reply with quote
Donator
User avatar
Offline

Joined
Thu Mar 31, 2011 8:24 am

Posts
776

Favourite OS
6001
Hounsell that is only a type of installation process, that is a way or possibility to transform some thing in another thing.
We can say this, integration of driverpacks via driver packs Base is more easily then integrating any driver in Longhorn WIM.
Other thing, I made LDB on WIM technology because WIM is better, but some of us just want to install even and vista like xp, I don't know why.
Sincerely from the collectors reasons I want to have all LH builds in WIM and in i386 form, but I doubt even with this guide that I'll get it them all ever.


Top  Profile  WWW
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Fri Sep 07, 2012 11:23 am 
Reply with quote
Donator
Offline

Joined
Sat Feb 24, 2007 4:14 pm

Posts
6612

Location
United Kingdom

Favourite OS
Server 2012 R2
maxtorix wrote:
We can say this, integration of driverpacks via driver packs Base is more easily then integrating any driver in Longhorn WIM.
Other thing, I made LDB on WIM technology because WIM is better, but some of us just want to install even and vista like xp, I don't know why.
Sincerely from the collectors reasons I want to have all LH builds in WIM and in i386 form, but I doubt even with this guide that I'll get it them all ever.


False. You find integration of drivers easier with i386. This is simply because you don't understand WIMs well enough.

I'm confused as to why collectors would want poorly-built hackjobs, as opposed to untouched builds.

_________________
BuildFeed - the ultimate collaborative NT build list - Windows Longhorn - a look at a defining Microsoft project


Top  Profile  WWW
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Fri Sep 07, 2012 11:45 am 
Reply with quote
Donator
User avatar
Offline

Joined
Sat May 12, 2007 1:05 pm

Posts
5271

Location
The Collection Book

Favourite OS
Windows & Phone
I prefer the builds how they are.
Not custom hackjobs including branding to the max of the maker (prime example is the OP), which makes it ugly.
And with custom hackjobs, you lose the ''genuine'' and ''untouched'' parts, also, they were not meant to install that way.

Microsoft created the WIM for easy and fast installation, saves a lot of time using WIM.
With WIM, it boots first into a Windows PE where you provide drivers if necessary, but I have yet to come a cross a machine that doesn't work with the default drivers (even in the XP era).

_________________
Image
http://www.thecollectionbook.info
Subscribe to our Image for updates and like us on Image.

Reading Mode only, PM's possible.


Top  Profile  WWW
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Fri Sep 07, 2012 11:57 am 
Reply with quote
Donator
User avatar
Offline

Joined
Thu Mar 31, 2011 8:24 am

Posts
776

Favourite OS
6001
Rob Jansen wrote:
I prefer the builds how they are.
Not custom hackjobs including branding to the max of the maker (prime example is the OP), which makes it ugly.
And with custom hackjobs, you lose the ''genuine'' and ''untouched'' parts, also, they were not meant to install that way.

Microsoft created the WIM for easy and fast installation, saves a lot of time using WIM.
With WIM, it boots first into a Windows PE where you provide drivers if necessary, but I have yet to come a cross a machine that doesn't work with the default drivers (even in the XP era).


Re-branding is like a commercial made for promotion nothing more, today I don't use it to much like before - see my signature :)
For everything else you are right, except for the drivers for old machine, - here I allude to machines that are built on a motherboard with a VIA chipset.


Top  Profile  WWW
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Fri Sep 07, 2012 1:02 pm 
Reply with quote
Donator
Offline

Joined
Sat Aug 22, 2009 4:28 pm

Posts
4268
hounsell wrote:
False. You find integration of drivers easier with i386. This is simply because you don't understand WIMs well enough.


Well, then how to do it on Longhorn, because we don't have the DISM tool for it? Unpacking a WIM is not a solution, because in I386 it's just one-click-wizard that does it (nLite).

_________________
Longhorn Packet 1.21 - Solves most of the problems with Longhorn Setup
[GUIDE] How to dump clean/untouched images from CD discs
Longhorn Music Album (FLAC) | 523.31 MB | 17 tracks | Donators Discussion Forum


Top  Profile
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Sat Sep 08, 2012 11:30 pm 
Reply with quote
Donator
User avatar
Offline

Joined
Mon Jul 23, 2012 9:40 pm

Posts
1070

Location
Flying high in a DC10

Favourite OS
NT3.X Family
Biohead wrote:
What are the benefits of an i386 install over WIM? I'm genuinely curious as I've seen it mentioned once or twice now but as I have no interest in it I've never particularly bothered finding it out.


With i386 setup, I think you can load up custom components and have it correctly installed. I really don't know.

_________________
Quote:
"C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off"


Top  Profile
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Mon Mar 16, 2015 5:13 pm 
Reply with quote
Permanently Banned
User avatar
Offline

Joined
Wed Aug 27, 2014 3:05 pm

Posts
516

Location
C:\Users\Archenemy

Favourite OS
Windows Betas
maxtorix wrote:
0) Requirements: Build 4051 32 and 64-bit ISO images, VMware Workstation 8 or 9.

And Windows XP or Server 2003 iso or dvd.
maxtorix wrote:
4) Mount VHD of your VM and copy all files
Quote:
from
\windows\i386
to
\LH4051\i386

No, you copy the \windows\i386 folder to \LH4051\temp.
maxtorix wrote:
5) Make this dir \LH4051\temp\i386\lang

No, you move the dir \LH4051\temp\i386\lang to \LH4051\i386.
maxtorix wrote:
6) This files should be in in your work dir \LH4051\i386
You move these files to \LH4051\i386.
maxtorix wrote:
Quote:
windows.cab (you can use LH4051 x64 version files,) - this file contains files from winsxs - and sometimes maybe so problematic to give you a fatal error

Files from winsxs don't give you a fatal error. asms01.cab and windows.cab both contain files from winsxs which are both required during setup.
maxtorix wrote:
Optional Adding: SATA drivers in TXT (F6) Mode
Image
[/color]

DriverPacks break Longhorn i386 repacks so don't use DriverPacks to add SATA drivers, just insert the SATA driver files into your repack and add them to txtsetup.sif and dosnet.inf.

maxtorix wrote:
10)
Use nLite to build ISO file

Use xpboot.bin and cdimage to create a bootable iso file the Microsoft way.
Sorry mods for bumping this topic from 2012 and any errors I made, I am just trying to correct a few things in this topic. BTW, here is the original source (credit to MSTest, gosh, and scp): http://www.web.archive.org/web/20120228 ... ser-guide/

_________________
@Archenemy betaarchive member

Last edited by Archenemy on Fri Dec 13, 2013 12:00 am, edited 6634564737338 times in total.


Top  Profile
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Fri Jul 10, 2015 4:04 pm 
Reply with quote
Offline

Joined
Wed Jan 22, 2014 5:59 pm

Posts
355

Favourite OS
Windows Neptune Build 5111
The script link is down, can someone please re-up it?


Top  Profile
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Fri Jul 10, 2015 6:16 pm 
Reply with quote
Permanently Banned
Offline

Joined
Tue Jun 10, 2014 5:09 pm

Posts
491

Favourite OS
Longhorn 3718
you can also speed up install process by 80% unlike broken lh wim's


Top  Profile
 PostPost subject: Re: [GUIDE] How to convert WIM to i386 installation form        Posted: Thu Jul 16, 2015 4:11 pm 
Reply with quote
Donator
User avatar
Offline

Joined
Mon Jul 23, 2012 9:40 pm

Posts
1070

Location
Flying high in a DC10

Favourite OS
NT3.X Family
Just putting it out there, tried pulling off drastic measure and attempted this with 4033 to try and kill a timebomb.
Can't boot from cd, so I ran from windows. File copy stage has a few hiccups, text-mode goes smoothly.
However, final stage (GUI) Hits 0xb4 VIDEO_DRIVER_INIT_FAILURE.

_________________
Quote:
"C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off"


Top  Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 13 posts ] 




Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  

All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.

Powered by phpBB® Forum Software © phpBB Group

Copyright © 2006-2019

 

Sitemap | XML | RSS