Jump to content











Photo
- - - - -

[NT6] Dual boot x86/x64 with 1 partition


  • Please log in to reply
3 replies to this topic

#1 genetix

genetix

    Frequent Member

  • Advanced user
  • 132 posts
  •  
    Finland

Posted 01 December 2014 - 10:56 AM

Well, I bet this has been asked since Vista ever arrived, buthaving hard time finding any howto with good amoung of information what it actually takes to edit to make this happen.

 

Structure:

 

x86:

\winx86

\ProgramDatax86

\ProgramFilesx86

\Usersx86

 

x64:

\winx64

\ProgramFilesx64

\Program Files (x86)

\ProgramDatax64

\Usersx64

 

In other words I need to rename every single root path there is from both architectures (if I would be lazy only one, but afraid of mixups).

 

But any simpler way to do this than me writing every single thing in registry to point correct location?

 

At old v-lite I recall having choise while customizing the media to do this, but currently looking at Windows 7/8.1/10 and after testing from RT Seven-/NT-lite/WIM Toolkit to actual "export image"/Installation to target software having no luck of doing this easily.



#2 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 01 December 2014 - 11:35 AM

Hi

 

I am not an expert to say that what you are trying to do is either impossible or near impossible. I guess that it will be a challenge even for an expert. The question is who want to invest their precious time to experiments on something that has no real benefit ( other than for the fun and satisfaction in doing so ).  

 

Btw, NT5 family OS supports changing the root folder name of Windows. Instead of the standard "Windows", you can use your own custom name. I am not sure whether it is still possible with NT6. I think "Windows" is hard coded in "Bootmgr" and other OS loading components.


Edited by Agent47, 01 December 2014 - 11:51 AM.


#3 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 01 December 2014 - 11:54 AM

Another option might be using VHD files. You can create two VHD files on the same partition and install x86 and x64 versions to them. This way file/folder name conflicts can be avoided. 



#4 genetix

genetix

    Frequent Member

  • Advanced user
  • 132 posts
  •  
    Finland

Posted 01 December 2014 - 05:32 PM

Hi

 

I am not an expert to say that what you are trying to do is either impossible or near impossible. I guess that it will be a challenge even for an expert. The question is who want to invest their precious time to experiments on something that has no real benefit ( other than for the fun and satisfaction in doing so ).  

 

Btw, NT5 family OS supports changing the root folder name of Windows. Instead of the standard "Windows", you can use your own custom name. I am not sure whether it is still possible with NT6. I think "Windows" is hard coded in "Bootmgr" and other OS loading components.

 

Well, I consider myself as some sort of expert in bad in good and no I don't see it as impossible at all in fact I got this working at UAS USB 3rd partition currently. I am clad to invest my time to build this as you can imaging the idea of NT6.x being installed x64/ia32 EFI compatible and same time supporting x86 old systems live from any media don't see who wouldn't be.

I don't think you are correct about bootmgr having hardcoded "\Windows" and I believe it being only at registry after winload.exe/efi is directed by BCD (which, yes, is insanity level to be started to be modified because of so many microsoft misuses of %SystemRoot% and %WINDIR%). I even believe this might be able to be build by unattended.xml or autounattended.xml as an automated process,

 

Another option might be using VHD files. You can create two VHD files on the same partition and install x86 and x64 versions to them. This way file/folder name conflicts can be avoided. 

 

Yeah, VHD and basically 2 different partitions is of course a choice, but that again negates the whole idea of having hardlinked x86 content from x64 OS to remove duplicates from both OS, which reduces 2 OS size insanely and right kind of tweaking with NTFS compression brings this even further in size. I counted ideal system using around 11GB in full x86-x64 it could be half of that without .NET as live system.

 

Offtopic:

All above concepts should be in one hell of an interest to people who builds systems like 'Yumi', WINNTSETUP, RMprepUSB, WIM toolkik and other such software (only few to mention).

(In the end we are talking with current hardware All-OS flash media from DOS + 2xx Windows versions to about same amount of core linux distributions all compressed to single archive, differentially and mountable/bootable directly from archive at any environment. To archive this we are too early at both linux and windows side and probably neither never ever live peacefully together which says we need new WIM style standard to market from opensource capable of NTFS and EXT2-4).






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users