BetaArchive Logo
Navigation Home Screenshots Image Uploader Server Info FTP Servers Wiki Forum RSS Feed Rules Please Donate
UP: 50d, 4h, 50m | CPU: 15% | MEM: 6580MB of 11126MB used
{The community for beta collectors}

Post new topic Reply to topic  [ 8 posts ] 
Author Message
 PostPost subject: Creating a WIM-repack of Windows Longhorn Build 4039        Posted: Mon May 19, 2008 1:07 pm 
Reply with quote
FTP Access
User avatar
Offline

Joined
Thu Feb 07, 2008 1:35 pm

Posts
571

Location
United Kingdom
I read an article I found on Google that says how to do a WIM repack of Windows Longhorn so that it uses the traditional i386 installation like Windows XP does. Is it possible to do it with this build (4039)? I know the WIM repack is not recommended, but at least it gives me more flexibility when add customizations so I can just simply use the makecab command on the customized files and drop them into the i386 folder.

What does any of you people think to this?

PS: 4039 is one of my favourite builds because it reminds me of the Longhorn concept on Youtube.


Top  Profile  WWW
 PostPost subject:        Posted: Mon May 19, 2008 1:22 pm 
Reply with quote
Donator
Offline

Joined
Fri Oct 20, 2006 11:39 pm

Posts
61

Location
Lab06
It is possible, right now they are working on doing this with 3718, it will be mostly the same process. I will help you if you like. just need ximage and sys prep. Take a look on the forums and see how they did it with 3718.

_________________
MSN: svfusion@(nospam)gmail.com


Top  Profile
 PostPost subject:        Posted: Mon May 19, 2008 2:53 pm 
Reply with quote
Donator
Offline

Joined
Sat Feb 24, 2007 4:14 pm

Posts
6612

Location
United Kingdom

Favourite OS
Server 2012 R2
No, for some strange reason, he wants to take 4039 from WIM to i386. We are taking 3718 from i386 to WIM.
Why would you abandon a much better format (WIM) for an out-dated over-rated format (i386)?

WIMs are much, much simpler to modify if you know what you are doing. I suggest you return to google, and check out how to work with WIMs, and do something more worthwhile than try to repack 4039 into an i386 setup.

Microsoft moved to WIMs for a reason, and it was something that Microsoft had been working on a number of years, and it's got so many advantages over the old-style i386 setup. Moving backwards just brings it's own problems, you just have to have to look at the repack, and the fact that it is a shadow of the proper build, and less stable and functional.

Longhorn was built for WIMs. It is simply not designed for i386. The reason why going to WIMs works so much better than from WIMs is simply because Microsoft knew that WIMs were on their way. Since NT4, Microsoft have provided Sysprep, knowing that corporate people had already realised image-based setups were the way forward.

Now Microsoft would hardly see any reason for making Longhorn work well with i386. i386 is a dead system, it drove even Microsoft insane with it's slow speed. Why would anyone want to return to it? WIMs are really fantastically simple to manipulate. What I'm doing with 3718 is taking me no more than 2 hours to produce a build, by installing it using the i386 setup, modifying 3718 as I want (ie Activation cracks, soon UI modifications), then sysprepping, resealing, capturing a WIM image, and installing the new WIM based installer and let it run the mini-setup (or not, as the case may be).

Why would anyone want to resort to i386?

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


Top  Profile  WWW
 PostPost subject:        Posted: Mon May 19, 2008 3:43 pm 
Reply with quote
FTP Access
User avatar
Offline

Joined
Thu Feb 07, 2008 1:35 pm

Posts
571

Location
United Kingdom
Well, what I have done is installed 4039 onto a second hard drive, but only let the setup run at the first part, and not at the second part where it attempts to install the drivers for devices. Should I copy my customized files, shell32.dll etc.... cracked winlogon.exe etc, then use ximage to make a new install.wim file. If so, which version of ximage.exe should I use?


Top  Profile  WWW
 PostPost subject:        Posted: Mon May 19, 2008 4:56 pm 
Reply with quote
Donator
Offline

Joined
Sat Feb 24, 2007 4:14 pm

Posts
6612

Location
United Kingdom

Favourite OS
Server 2012 R2
squidward_ wrote:
Well, what I have done is installed 4039 onto a second hard drive, but only let the setup run at the first part, and not at the second part where it attempts to install the drivers for devices. Should I copy my customized files, shell32.dll etc.... cracked winlogon.exe etc, then use ximage to make a new install.wim file. If so, which version of ximage.exe should I use?


You'd have to use the installer from a different build, since there is no leaked ximage that works with the 4039 installer, but simply delete the sources folder, copy in the 4074 sources folder without the install.wim, and capture a wim with the Build 4059 ximage, and use a hex editor to change the image index to 3, since the 4074 installer automatically uses the index 3 part of the WIM ;)

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


Top  Profile  WWW
 PostPost subject:        Posted: Mon May 19, 2008 7:14 pm 
Reply with quote
FTP Access
User avatar
Offline

Joined
Thu Feb 07, 2008 1:35 pm

Posts
571

Location
United Kingdom
Its OK if you can't tell me, but where can I get an appropriate hexedit program and XIMAGE 4059?


Top  Profile  WWW
 PostPost subject:        Posted: Tue May 20, 2008 10:56 pm 
Reply with quote
Donator
Offline

Joined
Sat Sep 09, 2006 6:43 am

Posts
736

Favourite OS
Win10/Debian Linux
As for a free hex editor that will fit the bill, you can use HxD. Just use the built-in Tools->open Disk image feature, and you'll be set. As for Ximage, there's a few sites that may or may not have it still - http://www.tacobeta.com/longhorn.html or http://www.aldatillian.be/


Top  Profile  WWW
 PostPost subject:        Posted: Tue Jul 29, 2008 7:05 am 
Reply with quote
I've repacked some versions of windows this way. 8)


Hello all. :)

3718 had no sysprep but you can use newsid from sysinternals.

I successfully made a reduced 3718 in a 4015 panther engine like this and it works well enough.

Longhorn 4053 is the one best suited to the task imo,

which is what I use for xp/03.

Of course a few tricks are tucked away that include realtime cpu detection which overcomes the limitation claim by MS that xp cannot be used for image based deployment across multiple cpu types.

The project was dubbed 'PantherXP' a few months ago.

But everyone thinks it's an OSX mod. :P


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




Who is online

Users browsing this forum: No registered users and 5 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-2018

 

Sitemap | XML | RSS