BetaArchive Logo
Navigation Home Database Screenshots Gallery Image Uploader Server Info FTP Servers Wiki Forum RSS Feed Rules Please Donate
UP: 59d, 23h, 6m | CPU: 8% | MEM: 5062MB of 11975MB used
{The community for beta collectors}

Post new topic Reply to topic  [ 9 posts ] 
Author Message
 PostPost subject: Trying to Fix Longhorn 4011's PE        Posted: Sun Nov 18, 2018 2:10 am 
Reply with quote
User avatar
Offline

Joined
Mon Sep 04, 2017 7:29 pm

Posts
60

Location
Temmie Village

Favourite OS
Windows Longhorn Build 4074
For a couple days, I've been trying to figure out ways of making both Longhorn Build 4011 and 4015 bootable, while making as less changes to the ISO as possible in hopes of keeping it as original as I could. As known to most people, each time you try to boot off of the 4015 iso, you get "CDBOOT: NTLDR not found". Searching through the forums, there were a number of people that gave the solution of replacing the files from another build's ISO with 4011's, which gave me the idea of just replacing the boot image with 4011's, so I opened 4011's ISO with 7-zip, went to the [BOOT] folder, and copied the boot image to my hard drive folder, before using it on the 4015 ISO. When I tried booting it off of the ISO, I was greeted with the same "Debug Assertion Failed" error as the one seen on 4011, which made me wonder if I could fix 4011's PE as well, if I figured out a way to fix 4015's. So, I did some digging both online and on the forums, again, and found that there were several copies of the ISO, a size-reduced version missing all the folders except for the 'SOURCES' and 'BOOT' from OSBA with a non-working PE that was a labeled as a 'farewell release' for when the site shut down, the same ISO but with a corrupted INSTALL.WIM (aka the ISO that's hugely circulated), and the original that doesn't cause any problems. Unfortunately, I cannot find the original anywhere, although I was able to find the OSBA iso on a torrent. I'm unsure if I can link the torrent, or just the ISO itself on here, since I was able to download the whole torrent successfully, but if anyone wants it, PM me and I'll be sure to give it to you. So, with the OSBA 4011 iso in hand, I still tried to figure out a way of fixing 4015's PE in hopes that I can do the same for 4011, so the first thing I did was look over the files, and compared it with the PE from INSTALL.WIM. The first thing I noticed was that everything in the WinSXS folder wass named poorly, presumably when the leaker made the ISO, so I decided to figure out which file was which by comparing sizes and hashes, and renamed everything I was supposed to back to their original names. I made a list of everything that I renamed on the 4015 ISO, which I'll put here:
Quote:
BOOT\WINSXS
X86_MICROS000.WINDOWS.COMMON-CO > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C
X86_MICROS000.WINDOWS.CPLUSPLUS > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB
X86_MICROS000.WINDOWS.GDIPLUS_6 > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94
X86_MICROS000.WINDOWS.ISOLATION > X86_MICROSOFT.WINDOWS.ISOLATION_6595B64144CCF1DF_5.1.0.0_X-WW_2DE005A7
X86_MICROS000.WINDOWS.NETWORKIN > X86_MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.1.0.0_X-WW_91D50D8F
X86_MICROS001.WINDOWS.COMMON-CO > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A
X86_MICROS001.WINDOWS.ISOLATION > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872
X86_MICROSOFT.TOOLS.VISUALCPLUS > X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7
X86_MICROSOFT.WINDOWS.COMMON-CO > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05
X86_MICROSOFT.WINDOWS.CPLUSPLUS > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A
X86_MICROSOFT.WINDOWS.GDIPLUS_6 > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13
X86_MICROSOFT.WINDOWS.ISOLATION > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880
X86_MICROSOFT.WINDOWS.NETWORKIN > X86_MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.1.0.0_X-WW_019BE8A1
X86_MICROSOFT.WINDOWS.WINHTTP_6 > X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936

BOOT\WINSXS\MANIFESTS
X86_MICROSOFT.TOOLS.VI.MANI > X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7.MANIFEST
X86_MICROSOFT.TOOLS.VISUALC > X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7.CAT
X86_MICROSOFT.WINDOWS..MANI > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880.MANIFEST
X86_MICROSOFT.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05.MANIFEST
X86_MICROSOFT.WINDOWS.COMMO. > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05.CAT
X86_MICROSOFT.WINDOWS.CPLUS. > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A.CAT
X86_MICROSOFT.WINDOWS.GDIPL. > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13.CAT
X86_MICROSOFT.WINDOWS.ISOLA > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880.CAT
X86_MICROSOFT.WINDOWS.ISOLA. > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872.CAT
X86_MICROSOFT.WINDOWS.NETWO > X86_MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.1.0.0_X-WW_019BE8A1.CAT
X86_MICROSOFT.WINDOWS.SYSTE. > X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.0.0_X-WW_FC342B0B.CAT
X86_MICROSOFT.WINDOWS.WINHT. > X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936.CAT
X86_MICROSOFT000.WINDOWS..MANI > X86_MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.1.0.0_X-WW_91D50D8F.MANIFEST
X86_MICROSOFT000.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936.MANIFEST
X86_MICROSOFT000.WINDOWS.COMMO. > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C.CAT
X86_MICROSOFT000.WINDOWS.CPLUS. > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB.CAT
X86_MICROSOFT000.WINDOWS.GDIPL. > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94.CAT
X86_MICROSOFT000.WINDOWS.ISOLA. > X86_MICROSOFT.WINDOWS.ISOLATION_6595B64144CCF1DF_5.1.0.0_X-WW_2DE005A7.CAT
X86_MICROSOFT000.WINDOWS.NETWO > X86_MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.1.0.0_X-WW_91D50D8F.CAT
X86_MICROSOFT000.WINDOWS.SYSTE. > X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.2.0.0_X-WW_40208A0C.CAT
X86_MICROSOFT001.WINDOWS..MANI > X86_MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.1.0.0_X-WW_019BE8A1.MANIFEST
X86_MICROSOFT001.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.2.0.0_X-WW_40208A0C.MANIFEST
X86_MICROSOFT001.WINDOWS.COMMO. > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A.CAT
X86_MICROSOFT002.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.0.0_X-WW_FC342B0B.MANIFEST
X86_MICROSOFT003.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.ISOLATION_6595B64144CCF1DF_5.1.0.0_X-WW_2DE005A7.MANIFEST
X86_MICROSOFT004.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872.MANIFEST
X86_MICROSOFT005.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94.MANIFEST
X86_MICROSOFT006.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13.MANIFEST
X86_MICROSOFT007.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB.MANIFEST
X86_MICROSOFT008.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A.MANIFEST
X86_MICROSOFT009.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C.MANIFEST
X86_MICROSOFT00A.WINDOWS..MANIF > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A.MANIFEST

BOOT\WINSXS\SETUPPOLICIES
X86_POLICY.1.0.MICROSOFT.WINDOW > X86_POLICY.1.0.MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_X-WW_4E8510AC
X86_POLICY.5.2.MICROSOFT.WINDOW > X86_POLICY.5.2.MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_X-WW_92C6FB91
X86_POLICY.6.0.MICROSOFT.WINDOW > X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_X-WW_5DDAD775
X86_POLICY.7.0.MICROSOFT.WINDOW > X86_POLICY.7.0.MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_X-WW_A317E4B3

After I renamed everything, I saved the ISO and tried to test it. After I did that, it worked flawlessly. So, I tried doing the same with 4011, using the PE from the INSTALL.WIM in the OSBA ISO, since it didn't have any corruption near the PE portion of INSTALL.WIM, unlike the other ISO's. Here's a list of what I renamed, as well:
Quote:
BOOT\WINSXS
X86_MICROSOFT.TOO > X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7
X86_MICROSOFT.WIN > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05
X86_MICROSOFT.WIO > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A
X86_MICROSOFT.WIP > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C
X86_MICROSOFT.WIQ > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A
X86_MICROSOFT.WIR > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB
X86_MICROSOFT.WIS > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13
X86_MICROSOFT.WIT > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94
X86_MICROSOFT.WIU > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880
X86_MICROSOFT.WIV > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872
X86_MICROSOFT.WIW > X86_MICROSOFT.WINDOWS.ISOLATION_6595B64144CCF1DF_5.1.0.0_X-WW_2DE005A7
X86_MICROSOFT.WIX > X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936

BOOT\WINSXS\MANIFESTS
X86_MICROSOFT.TOO > X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7.CAT
X86_MICROSOFT.TOP > X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7.MANIFEST
X86_MICROSOFT.WI0 > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94.MANIFEST
X86_MICROSOFT.WI1 > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880.CAT
X86_MICROSOFT.WI2 > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880.MANIFEST
X86_MICROSOFT.WI3 > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872.CAT
X86_MICROSOFT.WI4 > X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872.MANIFEST
X86_MICROSOFT.WI5 > X86_MICROSOFT.WINDOWS.ISOLATION_6595B64144CCF1DF_5.1.0.0_X-WW_2DE005A7.CAT
X86_MICROSOFT.WI6 > X86_MICROSOFT.WINDOWS.ISOLATION_6595B64144CCF1DF_5.1.0.0_X-WW_2DE005A7.MANIFEST
X86_MICROSOFT.WI7 > X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.0.0_X-WW_FC342B0B.CAT
X86_MICROSOFT.WI8 > X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.0.0_X-WW_FC342B0B.MANIFEST
X86_MICROSOFT.WI9 > X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.2.0.0_X-WW_40208A0C.CAT
X86_MICROSOFT.WIA > X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.2.0.0_X-WW_40208A0C.MANIFEST
X86_MICROSOFT.WIB > X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936.CAT
X86_MICROSOFT.WIC > X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936.MANIFEST
X86_MICROSOFT.WIN > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05.CAT
X86_MICROSOFT.WIO > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05.MANIFEST
X86_MICROSOFT.WIP > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A.CAT
X86_MICROSOFT.WIQ > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A.MANIFEST
X86_MICROSOFT.WIR > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C.CAT
X86_MICROSOFT.WIS > X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C.MANIFEST
X86_MICROSOFT.WIT > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A.CAT
X86_MICROSOFT.WIU > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A.MANIFEST
X86_MICROSOFT.WIV > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB.CAT
X86_MICROSOFT.WIW > X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB.MANIFEST
X86_MICROSOFT.WIX > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13.CAT
X86_MICROSOFT.WIY > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13.MANIFEST
X86_MICROSOFT.WIZ > X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94.CAT

BOOT\WINSXS\SETUPPOLICIES
X86_POLICY.1.0 > X86_POLICY.1.0.MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_X-WW_4E8510AC
X86_POLICY.5.2 > X86_POLICY.5.2.MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_X-WW_92C6FB91
X86_POLICY.6.0 > X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_X-WW_5DDAD775
X86_POLICY.7.0 > X86_POLICY.7.0.MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_X-WW_A317E4B3

So, as usual, I saved the ISO and tried to test it, but now there's another odd problem that was evident even before I swapped the names. The setup runs, but it doesn't let you type anything into the serial bar, and when you press on SHIFT+F10 to launch the command prompt, it bluescreens. I have tried everything I could to fix it, even going as far as to replace the PE with the one from the INSTALL.WIM which works just fine after running setup through Windows, although the problem still remains. I even tried replacing the PE in $WIN_NT$.~BT with the one from the ISO, which also worked, which proves that there is nothing wrong with the PE. So, I made a copy of the 4015 ISO, erased everything inside, and replaced it with everything from the 4011 ISO, yet it still happens.
I am not posting my findings to get something like FTP access (I could care less for it), but in hopes that it gives a headstart to anyone more experienced than me who wants to try and fix the PE on these builds.

_________________
hOI!!!!! i'm tEMMIE!!!!


Top  Profile
 PostPost subject: Re: Trying to Fix Longhorn 4011's PE        Posted: Sun Nov 18, 2018 6:37 am 
Reply with quote
Donator
User avatar
Offline

Joined
Fri Sep 28, 2018 9:29 pm

Posts
84

Location
Dell land

Favourite OS
Windows XP Media Center Edition
The issue has been worked around by doing an i386 setup.

_________________
Dell Latitude collector and hoarder


Top  Profile
 PostPost subject: Re: Trying to Fix Longhorn 4011's PE        Posted: Sun Nov 18, 2018 8:48 am 
Reply with quote
FTP Access
Offline

Joined
Fri Apr 25, 2014 6:19 pm

Posts
1057
I believe the 4011 iso on the FTP is the OSBA one, since the install.wim can be extracted via ximage 4007, but the WinPE itself is corrupt.

_________________
Image


Last edited by ovctvct on Sun Nov 18, 2018 6:20 pm, edited 1 time in total.

Top  Profile
 PostPost subject: Re: Trying to Fix Longhorn 4011's PE        Posted: Sun Nov 18, 2018 2:45 pm 
Reply with quote
Offline

Joined
Thu Oct 01, 2015 7:09 am

Posts
76
YourAverageJoe wrote:
For a couple days, I've been trying to figure out ways of making both Longhorn Build 4011 and 4015 bootable, while making as less changes to the ISO as possible in hopes of keeping it as original as I could.

I went down this road a few years ago, between checking imports / exports / setup routine compared to builds before & after, I soon began to realize that the build should have been used as an upgrade only.
Certain files responsible for the formatting & text input {eg:product key} are missing functions that are present in all other builds.

YourAverageJoe wrote:
The first thing I noticed was that everything in the WinSXS folder wass named poorly, presumably when the leaker made the ISO, so I decided to figure out which file was which by comparing sizes and hashes, and renamed everything I was supposed to back to their original names. I made a list of everything that I renamed on the 4015 ISO, which I'll put here:
Quote:
whole-bunch-O-lost-time

After I renamed everything, I saved the ISO and tried to test it. After I did that, it worked flawlessly. So, I tried doing the same with 4011, using the PE from the INSTALL.WIM in the OSBA ISO, since it didn't have any corruption near the PE portion of INSTALL.WIM, unlike the other ISO's. Here's a list of what I renamed, as well:
Quote:
more-lost-time

You did that the hard way, :P there's an untouched copy of the assemblies in "install.wim/windows/i386/asms01.cab", with original file dates & folder layout..

YourAverageJoe wrote:
I am not posting my findings to get something like FTP access (I could care less for it), but in hopes that it gives a headstart to anyone more experienced than me who wants to try and fix the PE on these builds.

I'll post one of many instances of what I mean by certain files responsible for the setup routine that are missing functions needed to work..

The difference between the screen on the left & the screen on the right..

Image

Is a missing export..

Image

When I still had the fixed files responsible for making the original 4011 ISO work, I tried giving them to 2 other members of this forum, one never replied to my emails, 2 of them, the other said "hey yeah love to try it out, send them too me, I did, the email bounced back twice, so I sent it via another mail client & changed attachment format, again it bounced back stating the recipients mail server had blocked me, I gave up trying..
I have a few pics saved on a flash drive, though anything beta related has long been scrubbed from my systems..


Top  Profile
 PostPost subject: Re: Trying to Fix Longhorn 4011's PE        Posted: Sun Nov 18, 2018 4:04 pm 
Reply with quote
User avatar
Offline

Joined
Mon Sep 04, 2017 7:29 pm

Posts
60

Location
Temmie Village

Favourite OS
Windows Longhorn Build 4074
ovctvct wrote:
You could try this i386 repack instead: https://drive.google.com/file/d/1qmhCzA ... sp=sharing

Also I believe the 4011 iso on the FTP is the OSBA one, since the install.wim can be extracted via ximage 4007, but the WinPE itself is corrupt.

The WinPE in the BOOT folder, or the PE in the INSTALL.WIM? Because neither of them are corrupt in the OSBA copy, as proven by me trying out the PE's, although there is SOMETHING that's causing problems which prevents it from booting from ISO, although I can't tell what.

_Ken_ wrote:
YourAverageJoe wrote:
For a couple days, I've been trying to figure out ways of making both Longhorn Build 4011 and 4015 bootable, while making as less changes to the ISO as possible in hopes of keeping it as original as I could.

I went down this road a few years ago, between checking imports / exports / setup routine compared to builds before & after, I soon began to realize that the build should have been used as an upgrade only.
Certain files responsible for the formatting & text input {eg:product key} are missing functions that are present in all other builds.

YourAverageJoe wrote:
The first thing I noticed was that everything in the WinSXS folder wass named poorly, presumably when the leaker made the ISO, so I decided to figure out which file was which by comparing sizes and hashes, and renamed everything I was supposed to back to their original names. I made a list of everything that I renamed on the 4015 ISO, which I'll put here:
Quote:
whole-bunch-O-lost-time

After I renamed everything, I saved the ISO and tried to test it. After I did that, it worked flawlessly. So, I tried doing the same with 4011, using the PE from the INSTALL.WIM in the OSBA ISO, since it didn't have any corruption near the PE portion of INSTALL.WIM, unlike the other ISO's. Here's a list of what I renamed, as well:
Quote:
more-lost-time

You did that the hard way, :P there's an untouched copy of the assemblies in "install.wim/windows/i386/asms01.cab", with original file dates & folder layout..

YourAverageJoe wrote:
I am not posting my findings to get something like FTP access (I could care less for it), but in hopes that it gives a headstart to anyone more experienced than me who wants to try and fix the PE on these builds.

I'll post one of many instances of what I mean by certain files responsible for the setup routine that are missing functions needed to work..

The difference between the screen on the left & the screen on the right..

Image

Is a missing export..

Image

When I still had the fixed files responsible for making the original 4011 ISO work, I tried giving them to 2 other members of this forum, one never replied to my emails, 2 of them, the other said "hey yeah love to try it out, send them too me, I did, the email bounced back twice, so I sent it via another mail client & changed attachment format, again it bounced back stating the recipients mail server had blocked me, I gave up trying..
I have a few pics saved on a flash drive, though anything beta related has long been scrubbed from my systems..

Yeah, I did do it the hard way, but only because I didn't want to replace files in WinSXS if they already still had the files intact. Call me crazy if you want, but when I said 'as original as possible', I meant it. Well, away from that, thank you for the information. It sucks to hear that no one appreciated your efforts of fixing the PE enough to try it out, but I do hope that if this topic gets some more light shed onto it, and if you (doubt it though, seeing how you kinda distanced yourself from the beta scene) or someone else decides to remake the fix using the information you posted, that more people will be willing to try it out and be able to finally make a working copy.

_________________
hOI!!!!! i'm tEMMIE!!!!


Top  Profile
 PostPost subject: Re: Trying to Fix Longhorn 4011's PE        Posted: Sun Nov 18, 2018 4:09 pm 
Reply with quote
Offline

Joined
Thu Oct 01, 2015 7:09 am

Posts
76
YourAverageJoe wrote:
Yeah, I did do it the hard way, but only because I didn't want to replace files in WinSXS if they already still had the files intact. Call me crazy if you want, but when I said 'as original as possible', I meant it.

The asms01.cab files in the "sources\install.wim\Windows\I386\asms01.cab" are actually in the 4011 ISO, same checksums as the one's in the WinSxS folder, just all properly named, & file dated with folders that have correct names as well..
Though the cab may have an extra folder of assemblies not in the WINSxS folder, been a while since the fix, though it's a quick original fix nonetheless..


Top  Profile
 PostPost subject: Re: Trying to Fix Longhorn 4011's PE        Posted: Sun Nov 18, 2018 7:04 pm 
Reply with quote
User avatar
Offline

Joined
Mon Sep 04, 2017 7:29 pm

Posts
60

Location
Temmie Village

Favourite OS
Windows Longhorn Build 4074
_Ken_ wrote:
YourAverageJoe wrote:
Yeah, I did do it the hard way, but only because I didn't want to replace files in WinSXS if they already still had the files intact. Call me crazy if you want, but when I said 'as original as possible', I meant it.

The asms01.cab files in the "sources\install.wim\Windows\I386\asms01.cab" are actually in the 4011 ISO, same checksums as the one's in the WinSxS folder, just all properly named, & file dated with folders that have correct names as well..
Though the cab may have an extra folder of assemblies not in the WINSxS folder, been a while since the fix, though it's a quick original fix nonetheless..

Hmm, true. Welp, thanks for the tip at least.

_________________
hOI!!!!! i'm tEMMIE!!!!


Top  Profile
 PostPost subject: Re: Trying to Fix Longhorn 4011's PE        Posted: Wed Jan 15, 2020 3:47 am 
Reply with quote
User avatar
Offline

Joined
Mon Sep 04, 2017 7:29 pm

Posts
60

Location
Temmie Village

Favourite OS
Windows Longhorn Build 4074
Year later update:
Yes, this thread is dead, I'm aware of that. Because of that, no one will likely see this; but I am not going to clutter the forums with something I already made a topic on. Anyways, onto why I'm writing this. I became aware, a year after being leaked, that both 4020 and 4032 also were non-bootable. 4032's case is similar to 4011, as it seems to be a developer fault as it'll freeze at a blank bright blue screen with no cursor whenever given a boot image to start off from. Slipping the PE that is extracted by the setup program produces the same result both on the ISO for 4032, and the ISO for any other build. 4020 on the other hand, visibly has the same problem as with 4015 and 4011 in terms of shortened WinSxS names, although there is other things wrong with it as you will see shortly. I was unable to effectively view the contents of INSTALL.WIM unfortunately, but I have used the setup program to extract the PE, which should be good enough for my case for the base. The name changes goes as follows, since it'll be easier to repair that way than to replace files:
Quote:
BOOT\WINSXS
X86_MICROSOFTTOOLSVISUALCPLUSP -> X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7
X86_MICROSOFTWINDOWSCOMMON_CON -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05
X86_MICROSOFTWINDOWSCOMMON_CON2 -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A
X86_MICROSOFTWINDOWSCOMMON_CON3 -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C
X86_MICROSOFTWINDOWSCPLUSPLUSR -> X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A
X86_MICROSOFTWINDOWSCPLUSPLUSR2 -> X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB
X86_MICROSOFTWINDOWSGDIPLUS_65 -> X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13
X86_MICROSOFTWINDOWSGDIPLUS_652 -> X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94
X86_MICROSOFTWINDOWSISOLATIONA -> X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880
X86_MICROSOFTWINDOWSISOLATIONA2 -> X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872
X86_MICROSOFTWINDOWSNETWORKING -> X86_MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.1.0.0_X-WW_019BE8A1
X86_MICROSOFTWINDOWSNETWORKING2 -> X86_MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.1.0.0_X-WW_91D50D8F
X86_MICROSOFTWINDOWSWINHTTP_65 -> X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936

BOOT\WINSXS\MANIFESTS
X86_MICROSOFTTOOLSVISU.MAN -> X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7.MANIFEST
X86_MICROSOFTTOOLSVISUALCPL.CAT -> X86_MICROSOFT.TOOLS.VISUALCPLUSPLUS.RUNTIME-LIBRARIES_6595B64144CCF1DF_6.0.0.0_X-WW_FF9986D7.CAT
X86_MICROSOFTWINDOWSCO.MAN -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05.MANIFEST
X86_MICROSOFTWINDOWSCO2.MAN -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A.MANIFEST
X86_MICROSOFTWINDOWSCO3.MAN -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C.MANIFEST
X86_MICROSOFTWINDOWSCOMMON_.CAT -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_5.82.0.0_X-WW_8A69BA05.CAT
X86_MICROSOFTWINDOWSCOMMON_2.CAT -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.0.0_X-WW_1382D70A.CAT
X86_MICROSOFTWINDOWSCOMMON_3.CAT -> X86_MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_6.0.200.0_X-WW_C803A40C.CAT
X86_MICROSOFTWINDOWSCP.MAN -> X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A.MANIFEST
X86_MICROSOFTWINDOWSCP2.MAN -> X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB.MANIFEST
X86_MICROSOFTWINDOWSCPLUSPL.CAT -> X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.0.0_X-WW_2726E76A.CAT
X86_MICROSOFTWINDOWSCPLUSPL2.CAT -> X86_MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_7.0.100.0_X-WW_94AA24EB.CAT
X86_MICROSOFTWINDOWSGD.MAN -> X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13.MANIFEST
X86_MICROSOFTWINDOWSGD2.MAN -> X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94.MANIFEST
X86_MICROSOFTWINDOWSGDIPLUS.CAT -> X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.0.0_X-WW_8D353F13.CAT
X86_MICROSOFTWINDOWSGDIPLUS2.CAT -> X86_MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_1.0.100.0_X-WW_0D1F9F94.CAT
X86_MICROSOFTWINDOWSIS.MAN -> X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880.MANIFEST
X86_MICROSOFTWINDOWSIS2.MAN -> X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872.MANIFEST
X86_MICROSOFTWINDOWSISOLATI.CAT -> X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION.PROXYSTUB_6595B64144CCF1DF_1.0.0.0_X-WW_7CFAC880.CAT
X86_MICROSOFTWINDOWSISOLATI2.CAT -> X86_MICROSOFT.WINDOWS.ISOLATIONAUTOMATION_6595B64144CCF1DF_1.0.0.0_X-WW_FD9DA872.CAT
X86_MICROSOFTWINDOWSNE.MAN -> X86_MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.1.0.0_X-WW_019BE8A1.MANIFEST
X86_MICROSOFTWINDOWSNE2.MAN -> X86_MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.1.0.0_X-WW_91D50D8F.MANIFEST
X86_MICROSOFTWINDOWSNETWORK.CAT -> X86_MICROSOFT.WINDOWS.NETWORKING.DXMRTP_6595B64144CCF1DF_5.1.0.0_X-WW_019BE8A1.CAT
X86_MICROSOFTWINDOWSNETWORK2.CAT -> X86_MICROSOFT.WINDOWS.NETWORKING.RTCDLL_6595B64144CCF1DF_5.1.0.0_X-WW_91D50D8F.CAT
X86_MICROSOFTWINDOWSSY.MAN -> X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.0.0_X-WW_FC342B0B.MANIFEST
X86_MICROSOFTWINDOWSSY2.MAN -> X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.2.0.0_X-WW_40208A0C.MANIFEST
X86_MICROSOFTWINDOWSSYSTEMC.CAT -> X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.1.0.0_X-WW_FC342B0B.CAT
X86_MICROSOFTWINDOWSSYSTEMC2.CAT -> X86_MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_5.2.0.0_X-WW_40208A0C.CAT
X86_MICROSOFTWINDOWSWI.MAN -> X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936.MANIFEST
X86_MICROSOFTWINDOWSWINHTTP.CAT -> X86_MICROSOFT.WINDOWS.WINHTTP_6595B64144CCF1DF_5.1.0.0_X-WW_E0651936.CAT

BOOT\WINSXS\SETUPPOLICIES
X86_POLICY10MICROSOFTWINDOWSGD -> X86_POLICY.1.0.MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_X-WW_4E8510AC
X86_POLICY52MICROSOFTWINDOWSSY -> X86_POLICY.5.2.MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_X-WW_92C6FB91
X86_POLICY60MICROSOFTWINDOWSCO -> X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_X-WW_5DDAD775
X86_POLICY70MICROSOFTWINDOWSCP -> X86_POLICY.7.0.MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_X-WW_A317E4B3

In the folders inside SETUPPOLICIES, there are numerous files in which need periods added as they are missing. Here is that list:
Quote:
BOOT\WINSXS\SETUPPOLICIES\X86_POLICY.1.0.MICROSOFT.WINDOWS.GDIPLUS_6595B64144CCF1DF_X-WW_4E8510AC
511000.POLICY -> 5.1.100.0.POLICY

BOOT\WINSXS\SETUPPOLICIES\X86_POLICY.5.2.MICROSOFT.WINDOWS.SYSTEMCOMPATIBLE_6595B64144CCF1DF_X-WW_92C6FB91
5200.POLICY -> 5.2.0.0.POLICY

BOOT\WINSXS\SETUPPOLICIES\X86_POLICY.6.0.MICROSOFT.WINDOWS.COMMON-CONTROLS_6595B64144CCF1DF_X-WW_5DDAD775
602000.POLICY -> 6.0.200.0.POLICY

BOOT\WINSXS\SETUPPOLICIES\X86_POLICY.7.0.MICROSOFT.WINDOWS.CPLUSPLUSRUNTIME_6595B64144CCF1DF_X-WW_A317E4B3
5100.POLICY -> 5.1.0.0.POLICY

There are also missing periods in the files inside the folder BOOT\MUI\FALLBACK\0409. Since the list would be VERY extensive for something so simple, I will not waste my time in that regard. It should be obvious where they should be placed. If anyone wishes, I can provide a fix that automates this process, or to make it as original as possible, my own Longhorn 4020 ISO that does all of this renaming for you.

_________________
hOI!!!!! i'm tEMMIE!!!!


Top  Profile
 PostPost subject: Re: Trying to Fix Longhorn 4011's PE        Posted: Sat Jan 18, 2020 12:56 am 
Reply with quote
Donator
User avatar
Offline

Joined
Mon Jul 23, 2012 9:40 pm

Posts
1143

Location
Flying high in a DC10

Favourite OS
NT3.X Family
Image
Image
Image

_________________
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  [ 9 posts ] 




Who is online

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

 

Sitemap | XML | RSS