[eangulus]

Hi everyone.

Just wanted to get a firm answer. Been looking for something for a week now and I can't get a clear answer.

Can someone tell me how to customize Windows 7 using RT7Lite (or something else if I need to) and still have a AIO x86/x64 set.

I have tried so far to directly use the AIO WIM and run RT7Lite on each edition but I then go to test and I can only select the x86 or x64 version of the last edition I customized.

Do I have to customize the separate WIM's first then combine or what?

Also in relation to this were are integrated drivers kept? Are they in the WIM itself?

[eangulus]

Can anyone give me some insight?

Just tried with 7Customizer and same issue.

Has the unattended xml got anything to do with edition selection?

[myselfidem]

This can be done ONLY on a computer 32 bit with RT Se7en Lite 1.7.0 RC x86 to customize an Windows 7 AIO (x86 and amd64)!

You can read my post #1699 here:

http://www.msfn.org/.../page__st__1680

[Yzöwl]

Please note, do not post another message when you haven't received a response after only forty minutes, it's rude.

[eangulus]

Not quite sure I understand.

I have to do this on a 32Bit install using 32bit RT7Lite

Do I use the already combined WIM which has x86 and x64 images? And if so do I run RT7Lite twice, one for x86 drivers and updates and again for x64 or do I run once with both x86 and x64 Drivers and updates?

Or do I have to run on 2 WIM's a x86 and then a x64 WIM, then combine afterwards?

Also what do I do about the Autounattended.xml file? how do I combine them?

[myselfidem]

I think the best way is to use images install.wim already merged (x86 and amd64) with RT Se7en Lte 1.7.0 RC.
Of course it's needed to launch twice the program: one time to customize Windows 7 x86 and after to customize Windows 7 x64.
But you can also do separatly the process and merge the images install.wim after (example for Ultimate images x86 and x64).

About Autounattend.xml for Windows 7 All-In-One, you can find help here (post # 116 and later):
http://www.msfn.org/...post__p__963334

This post has been edited by myselfidem: 16 July 2011 - 10:57 AM

[eangulus]

OK thanks. I think I can nut out the Autounattended.xml file.

Now I just want to be extra clear I have it right in my head. Takes a while to run RT7Lite so I want to at least be close to getting it right before my next attempt.


Correct me if I am wrong:

Run x86 RT7Lite on 32Bit 7. x64 on 64Bit 7 doesn't work.
I can run 2 seperate WIM's (x86 + x64) thru RT7Lite making appropriate changes, or I can run a single combined WIM but run it thru twice for each Architecture.
Choose Ultimate for each and apply to all images.

Now only think I am not 100% clear on is, if I run 1 combined WIM thru RT7Lite twice will it overwrite the autounattened (so I have to back it up first to combine later) or will it do the combining itself?

[myselfidem]

eangulus, on 29 April 2011 - 10:37 AM, said:

Run x86 RT7Lite on 32Bit 7. x64 on 64Bit 7 doesn't work.

You can use RT Se7en Lite 1.7.0 RC x86 ONLY on a computer 32 bit!

You can use RT Se7en Lite 1.7.0 RC x64 ONLY on a computer 64 bit!

But If you want you can use RT Se7en Lite 1.7.0 RC x86 on a computer 32 bit to customize Windows 7 32 bit and Windows 7 64 bit.

But you can't customize Windows 7 32 bit and Windows 7 64 bit with RT Se7en Lite 1.7.0 RC x64 on a computer 64 bit.

http://www.rtwincust...32-bit-machine/

Quote

I can run 2 seperate WIM's (x86 + x64) thru RT7Lite making appropriate changes, or I can run a single combined WIM but run it thru twice for each Architecture.

You can try the two methods, works - only with a computer 32 bit with RT Se7en Lite 1.7.0 RC x86!

Quote

Now only think I am not 100% clear on is, if I run 1 combined WIM thru RT7Lite twice will it overwrite the autounattened (so I have to back it up first to combine later) or will it do the combining itself?

Don't create an Autounattend.xml with RT Se7en Lite, but use your customized one for the two images x86 and amd64.

http://www.windowsvalley.com/create-windows-7-aio-all-in-one-dvd-or-merge-all-editions-of-windows-7-in-single-dvd/

This post has been edited by myselfidem: 29 April 2011 - 11:07 AM

[eangulus]

OK. I think I have got it.

I'll give you guys an update after my next attempt. Hopefully with success and not more questions LOL.

Thanks heaps everyone for the help very much appreciated.

[eangulus]

So Far so good.

My only issue atm is the unattended xml.

Still unsure on how to combine and to allow me to still select all editions in my WIM.

I have kep a copy of the file from the first RT7Lite run, and I have the second file (so one for x86 and another x64).

I know you said not to use them, but why not? I have made my customisations and they are in these files. I don't want to have to learn a great deal regarding the unattended files.

Basically I just want to combine my x86 version with my x64 version but have it apply to all editions for each.

[myselfidem]

This can be done, like this for your Autounattend.xml file (AIO x86 and x64):

1) Delete the file ei.cfg inside %DVD%\sources\ie.cfg

2) Inside your Autounattend.xml file (AIO) change to:
Example given at the link above!

<ImageInstall> 
    <OSImage> 
        <WillShowUI>Always</WillShowUI>     
    </OSImage> 
</ImageInstall>

All availables images will be displayed and the user can choose the one he wants to install!

*Edit: Remember that each Windows 7 version has it's own key, but you can also inject the default keys and don't write the keys inside your Autounattend.xml.

I think, only one key is valid for one version. The valid product key is on the sticky!

The default keys are inside %DVD%\sources\product.ini to install silently each Windows 7 version you have inside the install.wim image.

You can read my post #28 here and read how to inject the default keys.

http://www.msfn.org/...ry/page__st__20

This post has been edited by myselfidem: 01 May 2011 - 06:20 AM

[eangulus]

Its still not very clear. Very vague information.

First the example given earlier shows errors when opened in WAIK.

Secondly I grabbed one of the files that RT7Lite generated and put in your sample above, and now shows an error saying "Cannot find Windows Image information in Answer file".

I have all the settings I want in 2 separate files, x86 and a x64. I can see there are references to amd64 and x86 within these files so I know at least something is different between the 2 even thou I have the same settings.

Now do I simple copy and past both file into one file one after the other or do I have to put in key and image information for each image I want access to?

Also is there a way to not put the key in the image and keep all keys in the xml?

PS: I already know about combining by integrating all into same WIM and deleting the ie.cfg file. That's what I have had for some time know, I am only trying to integrate some more updates and getting some of it automated now with RT7Lite.

This post has been edited by eangulus: 01 May 2011 - 07:11 AM

[eangulus]

In regards to the keys, if there is really no way of putting them into the xml then I htink I understand the batch file to intergrate the keys.

My question on this is, is it a different run to set for x86 and x64 or will that one batch file be valid for both? And seeing I don't want to delete the starter and basic, I can see the lines I need to REM out, but how do I findout my current index of all the images, so I can assign the correct key to the correct index, and finally by intergrating the keys is it no different than skipping the key during the setup (as in will windows still ask for a key when we go to Validate, or will it think it already has a key)

[myselfidem]

Updated: I'm not Moderator (read post #4)! Thanks

*Edit: the best way, is to edit your last post!
I will take a look about your questions and try to give you an answer!

This post has been edited by myselfidem: 07 May 2011 - 04:45 AM

[myselfidem]

OK!
After testing, I see that the valid key match only the Windows 7 version you have bought!
That means if you install Windows 7 PROFESSIONAL and you have bought Windows 7 UTLIMATE the valid key doesn't match your Windows 7 version and you need a new valid key!!!

You can install silently Windows 7 with the default keys with Windows 7 versions you want with the default keys, but each version needs a different valid key!!

But you can use the same valid key to validate Windows 7 ULTIMATE x86 or Windows 7 ULTIMATE x64 if the valid key match the Windows 7 version you have!!

Inside your Autounattend.xml you can use your valid key for Windows 7 matching ONLY the Windows 7 version you have!!!
I think it's interesting to only make an Windows 7 AIO with the valid key validating the versions we have bought: Windows 7 ULTIMATE x86 and x64 (example)!

This post has been edited by myselfidem: 01 May 2011 - 01:58 PM

[eangulus]

Not sure how I am being rude.

And even more unsure on were that answer is from or what question it revolves around.

Everyone knows that each version needs its own keys. I wasn't ever asking for 1 Key. I was asking if there was anyway that I can put all of them into the XML, instead of injecting them.

And at what point did I say I ONLY had ultimate? I have All versions except for enterprise for both x86 and x64 in my WIM.

And I still don't know how to combine the 2 files I have.

After reading the other post regarding the keys, if I can't have them all in the XML, then is my only other option (other than integrate) is to either have separate xml's for each version that I can swap around per install, or forget about skipping the key thru setup.

[myselfidem]

eangulus, on 01 May 2011 - 04:49 PM, said:

And at what point did I say I ONLY had ultimate? I have All versions except for enterprise for both x86 and x64 in my WIM.

Just to clarify a point, about Windows 7 keys.
We can read inside:

Unattended Windows setup Reference for Windows 7.chm

Quote

Key
The product key that you use to activate the installation must match the number on the Certificate of Authenticity (COA) sticker that accompanies the retail product or that is physically attached
to the computer case by the original equipment manufacturer (OEM).

Standard licensing agreements specify that you can use a product key only to activate one installation of Windows® on one computer.
Windows Product Activation enforces this requirement.

Windows 7 valid keys (or default keys) are edition specific!

All editions are inside the image install.wim and the default keys can be used for silent installation!
But there is ONLY ONE VALID KEY to activate the edition matching the specific Windows 7 edition you've bought!

That means you can't use only one valid key to activate all Windows 7 Editions you have on the image install.wim!
If you try to install Windows 7 HOMEPREMIUM with a valid key for Windows 7 Ultimate, you will see that you can only install Windows 7 Ultimate.

http://windows.microsoft.com/en-US/windows7/Windows-7-activation-error-invalid-product-key

About the Autounattend.xml file for Windows 7 x86 and x64, you can find help here (my post #116, link already given above):
http://www.msfn.org/...e/page__st__100

This post has been edited by myselfidem: 04 May 2011 - 10:47 AM

[eangulus]

I think you have misread me.

I don't want to be able to use 1 Key for all editions.

I don't even really want a key at all.

This setup is intended for me to use to reinstall customer computers, getting majority of the basic setup tasks and apps out of the way. What I do at this stage is either enter the real key (of the computer sticker) during install or skip key on install and enter it later.

What I would like to do ideally is just skip the key and activation parts in the setup.

I wasn't asking about putting 1 key in the xml but wondering if there was a way to add ALL default keys for all the editions in the xml rather than integrating them into the images.

If that's not possible is there a way to just skip the key entering altogether like one would do by manually clicking skip.

[jd976]

Check out product.ini in sources folder. It contains default trial keys. Then inject using Dism for each edition.

Dism /image:<mountdir> /Set-ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

[myselfidem]

eangulus, on 05 May 2011 - 04:30 PM, said:

I wasn't asking about putting 1 key in the xml but wondering if there was a way to add ALL default keys for all the editions in the xml rather than integrating them into the images.

NO! You can't set all the default keys or valid keys for all Windows 7 Edition inside Autounattend.xml file!

*Edit:
1) One method is to inject the keys inside the mounted images!
2) Second method is to create an Autounattend.xml like my example on the next post

This post has been edited by myselfidem: 06 May 2011 - 07:32 AM