[RickRollNW]

jaclaz, on 11 June 2012 - 02:18 AM, said:

Hmmm.
Steve6375's instructions/tutorials are usually VERY accurate.

Ideas :

• Try replicating it EXACTLY without introducing ANY change
  
• Try manually.
  
• Have you changed the startnet.cmd in both .wims?
  
• Did you experiment - like in the tutorial - with boot1.wim and boot2.wim or did you use directly the files inside the .iso?

jaclaz

The changes I made were solely in the run commands, I could forego them but I don't see why they'd make a difference, everything else was down to the finest detail.
Elaborate on what you mean by Manual?
Yes, I did.
Yes, I used the WinPE boot1 and boot 2 wims outside of the iso itself, laid out in my flash drive exactly as it was in the tutorial.

Tripredacus, on 11 June 2012 - 09:30 AM, said:

johnhc, on 09 June 2012 - 05:43 PM, said:

Quote

My 64bit boot images do not use Setup.exe.

Tripredacus, I am curious how you do this. Is it the 32/64 nature of setup.exe that is causing the 'Load driver' function to fail to find a mass storage driver? Is this a work around for that problem? Thanks and enjoy, John.

I use Imagex. I do have normal DVDs that use setup.exe, but their install.wim only have 1 image in them. The only time I used one with multiple in the install.wim was with WDS which was I saw this issue where the Setup boot.wim from 7PRO64 would not display 32bit images.

From my understanding, setup.exe uses drvload to install the mass storage drivers. As far as drivers not being found, I've encountered this before, but usually to do with either a corrupted ISO or with poorly written drivers.

Quote

When I selected the 64-bit option, it booted, came up, and when it went to map the ISO, I kid you not... it said 'The subsystem needed to support the image type is not present.'

What's going on with the image? Should I try the inverse of starting with 64-bit and adding 32?

Either the 32bit or 64bit boot.wim does not support WoW. So if you got that error while running a program on the 64bit boot.wim, then your program or required libraries were not 64bit.

If that is the case then it's falling back to what I've been thinking, which is, the image is flawed somehow and I'm missing what I need to truly combine 32 and 64 bit in one ISO. Is there a way to resolve that so that I don't have to split the ISO? Or is my quest buggered. I'm open to different methods of installation that could over what I want, much like the above.

[Kelsenellenelvian]

Materials required:
Windows 7 x32 install media
Windows 7 x64 install media
Hex editor with search-and-replace, and support for unicode strings.
WAIK 2.0

Optional materials:
Windows 7 Enterprise x32 & x64 install media
(only required if you wish to have these editions available)

Stage 1: arranging files

Okay, in this guide we shall be working on the D: drive, but any drive letter you have available shall do.

In this stage we set up a directory structure to be used for the rest of the stages.

Firstly, create the folders:
D:\AIO\DVD

and

D:\AIO\WIMs

Next, extract contents of the x86 DVD into D:\AIO\DVD

Delete all .clg files from D:\AIO\DVD\sources

delete ei.cfg from D:\AIO\DVD\sources

Then move install.wim from D:\AIO\DVD\sources to D:\AIO\WIMs, and rename it ULTx86.wim
Then extract install. wim from the x64 DVD to WIMs, and rename it ULTx64.wim

And optionally, extract the install.wim from the x86 and x64 Enterprise DVDs, renaming them ENTx86.wim and ENTx64.wim respectively.

Finally, extract the content of the sources directory (except install.wim and ei.cfg) from the x64 DVD to D:\AIO\DVD\sourc64,
and copy the setup.exe from the x64 DVD to D:\AIO\DVD as setup64.exe

Stage 2: Building the WIM

Now we must build the install.wim (that's the file that contains the different versions of windows, if you didn't know), by exporting images from the .WIMS we have.

Assuming you've done exactly as I've said, open the deployment tools command prompt (from WAIK), and enter these commands:

Quote

Imagex /export "D:\AIO\WIMs\ULTx86.wim" 1 "D:\AIO\DVD\sources\install.wim" "Windows 7 STARTER"
Imagex /export "D:\AIO\WIMs\ULTx86.wim" 2 "D:\AIO\DVD\sources\install.wim" "Windows 7 HOME BASIC"
Imagex /export "D:\AIO\WIMs\ULTx86.wim" 3 "D:\AIO\DVD\sources\install.wim" "Windows 7 HOME PREMIUM"
Imagex /export "D:\AIO\WIMs\ULTx86.wim" 4 "D:\AIO\DVD\sources\install.wim" "Windows 7 PROFESSIONAL"
Imagex /export "D:\AIO\WIMs\ENTx86.wim" 1 "D:\AIO\DVD\sources\install.wim" "Windows 7 ENTERPRISE"
Imagex /export "D:\AIO\WIMs\ULTx86.wim" 5 "D:\AIO\DVD\sources\install.wim" "Windows 7 ULTIMATE"

Imagex /export "D:\AIO\WIMs\ULTx64.wim" 1 "D:\AIO\DVD\sources\install.wim" "Windows 7 HOME BASIC (x64)"
Imagex /export "D:\AIO\WIMs\ULTx64.wim" 2 "D:\AIO\DVD\sources\install.wim" "Windows 7 HOME PREMIUM (x64)"
Imagex /export "D:\AIO\WIMs\ULTx64.wim" 3 "D:\AIO\DVD\sources\install.wim" "Windows 7 PROFESSIONAL (x64)"
Imagex /export "D:\AIO\WIMs\ENTx64.wim" 1 "D:\AIO\DVD\sources\install.wim" "Windows 7 ENTERPRISE (x64)"
Imagex /export "D:\AIO\WIMs\ULTx64.wim" 4 "D:\AIO\DVD\sources\install.wim" "Windows 7 ULTIMATE (x64)"

You can skip the Enterprise ones if you chose not to include Enterprise. Well, you could skip any of them, but I reccommend including all you can,
as it does not take up much additional room (I assume WIM automatically reuses files), and you never know when you might need to do a clean install for someone!

Sage 3: Modifying the BCD

Here we modify the DVD's BCD, so as to add an x64 recovery option. The recovery option is just that: it cannot install.
To improve user transparency, the boot timeout shall be set to 3 sec, so as to be almost unnoticeable if not needed.

Ok, open an administative command prompt.

Navigate to D:\AIO\DVD

Now make a copy of the default loader by executing:

Quote

bcdedit /store boot\bcd /copy {default} /d "x64 Recovery Mode"

This command shall tell you the GUID of the copy made, make a note of it.

Next set the new loader to load the 64 bit PE by executing:

Quote

bcdedit /store boot\bcd /set {GUID} device ramdisk=[boot]\sourc64\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
bcdedit /store boot\bcd /set {GUID} osdevice ramdisk=[boot]\sourc64\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}

Replace {GUID} with the GUID you noted down)

Finally, alter the boot timeout by executing:

Quote

bcdedit /store boot\bcd /timeout 3

Stage 4: getting upgrade to work

Now, the one problem left is upgrade installs on 64 bit. This involves hex editing files, and so breaks the digital signature,
causing the ugly yellow UAC prompt. This is, I am almost ashamed to say, the first of two such cosmetic glitches.

Now first open D:\AIO\DVD\setup64.exe in your hex editor. Search and replace all instances of the unicode string "sources\" with "sourc64\".
Although this breaks the signature, it does not break the program, because both strings are the same length.

Now, open D:\AIO\DVD\sourc64\autorun.dll, and replace all instances of the unicode string "sources\setup.exe" with "sourc64\lunch.cmd"

(in case you were wondering, it was going to be launch.cmd, but I had to drop one letter...)

Now, create a file in D:\AIO\DVD\sourc64 called lunch.cmd containing exactly this:

Quote

setup.exe /m:sourc64 /installfrom:\sources\install.wim

NOTE: If you are using a SP1 slipstreamed image, lunch.cmd should instead contain exactly this:

Quote

setup.exe /installfrom:\sources\install.wim

This is the cause of the second cosmetic glitch. A command prompt is briefly visible before setup is launched.

Now, the autorun.inf must be modified so that it runs setup64 on x64 systems. Modify it so it contains:

Quote

[Autorun.Amd64]
open=setup64.exe
icon=setup64.exe,0

[Autorun]
open=setup.exe
icon=setup.exe,0

Now, finally, we're ready to master a DVD. Open up the deployment tools command prompt, and enter:

Quote

oscdimg.exe -l7_AIO -t10/22/2009:00:00 -m -u2 -bD:\AIO\DVD\Boot\etfsboot.com D:\AIO\DVD D:\7_AIO.ISO

[jaclaz]

RickRollNW, on 11 June 2012 - 10:38 AM, said:

Elaborate on what you mean by Manual?

I meant, like in the tutorial Point #10:

Quote

Option: If you want to leave this bit until after you have tested your USB drive, you can skip the next two steps (skip step 10 and 11)

I am still perplexed, because - as said - Steve6375's instructions were always proven to be very detailed, exact and tested.
I dropped him a line via PM to alert him about the present thread, let's see if he happens to "pass by" and can have a look/give some advice.

I know that it may sound like "queer" , but the possibility that - somehow - you have a corrupt source does exist, can you try again "from scratch" (unmodified, original DVD)?


@Kel
I guess that the issue is not actually the .iso in itself, but the .iso on USB stick mapped as CD/DVD.
If you prefer this topic is possibly more suitable here:
http://www.msfn.org/...ndows-from-usb/

jaclaz

[Kelsenellenelvian]

... and as usual I am a day late and a dollor short with too much information in the wrong place. :S

[johnhc]

Quote

I use Imagex. I do have normal DVDs that use setup.exe, but their install.wim only have 1 image in them. The only time I used one with multiple in the install.wim was with WDS which was I saw this issue where the Setup boot.wim from 7PRO64 would not display 32bit images.

From my understanding, setup.exe uses drvload to install the mass storage drivers. As far as drivers not being found, I've encountered this before, but usually to do with either a corrupted ISO or with poorly written drivers.

Thanks, Tripredacus. I will do some research and see if I can use this method. Enjoy, John.

[steve6375]

Not to sure what is going wrong but this menu makes bootmgr load BC2 not BCD. I can't see any mention of making a BC2 in your posts?

title Windows 64-bit OS Install Menu (bc2)\nIf you want to install a 64-bit OS
map --mem /bootmgr (rd)
write --offset=0x105E (rd)+1 \xEB\x08
write --offset=0x54696 (rd)+1 2
chainloader (rd)+1
root ()

Once you are booted to WInPE, can you detect whether you have booted to a 32-bit OS or a 64-bit OS (look at SET variables?).

[RickRollNW]

Hey all, sorry for taking awhile to get back to you all. My flash drive ended up breaking and I've been out of town. Just got back. So, going down the line.

jaclaz, on 11 June 2012 - 12:23 PM, said:

RickRollNW, on 11 June 2012 - 10:38 AM, said:

Elaborate on what you mean by Manual?

I meant, like in the tutorial Point #10:

Quote

Option: If you want to leave this bit until after you have tested your USB drive, you can skip the next two steps (skip step 10 and 11)

I am still perplexed, because - as said - Steve6375's instructions were always proven to be very detailed, exact and tested.
I dropped him a line via PM to alert him about the present thread, let's see if he happens to "pass by" and can have a look/give some advice.

I know that it may sound like "queer" , but the possibility that - somehow - you have a corrupt source does exist, can you try again "from scratch" (unmodified, original DVD)?


@Kel
I guess that the issue is not actually the .iso in itself, but the .iso on USB stick mapped as CD/DVD.
If you prefer this topic is possibly more suitable here:
http://www.msfn.org/...ndows-from-usb/

jaclaz

I had been entertaining this thought for awhile, and since Kel's method 'was' a tad different than what I had done, I followed his instructions to the T in making my new ISO. I mapped this one using my traditional firadisk map, and the end result was the same, still got a missing cd/dvd driver error on the 64-bit portion, but not the 32.

Kelsenellenelvian, on 11 June 2012 - 04:27 PM, said:

... and as usual I am a day late and a dollor short with too much information in the wrong place. :S

Not entirely buddy, it did resolve one other issue I'd been having, and the 'cosmetic' issues are of no consequence.

johnhc, on 11 June 2012 - 07:16 PM, said:

Quote

I use Imagex. I do have normal DVDs that use setup.exe, but their install.wim only have 1 image in them. The only time I used one with multiple in the install.wim was with WDS which was I saw this issue where the Setup boot.wim from 7PRO64 would not display 32bit images.

From my understanding, setup.exe uses drvload to install the mass storage drivers. As far as drivers not being found, I've encountered this before, but usually to do with either a corrupted ISO or with poorly written drivers.

Thanks, Tripredacus. I will do some research and see if I can use this method. Enjoy, John.

How does one use imagex to 'install' Windows? How can I apply this to my flash drive to obtain the prize I seek of dual 32 and 64-bit bootloaders?

steve6375, on 12 June 2012 - 01:34 PM, said:

Not to sure what is going wrong but this menu makes bootmgr load BC2 not BCD. I can't see any mention of making a BC2 in your posts?

title Windows 64-bit OS Install Menu (bc2)\nIf you want to install a 64-bit OS
map --mem /bootmgr (rd)
write --offset=0x105E (rd)+1 \xEB\x08
write --offset=0x54696 (rd)+1 2
chainloader (rd)+1
root ()

Once you are booted to WInPE, can you detect whether you have booted to a 32-bit OS or a 64-bit OS (look at SET variables?).

I hadn't pasted the snippit because it was mentioned in the tutorial by Steve that jaclaz had linked me earlier to attempt to resolve the issue, but it is almost exactly the same, only difference is the offsets because the ISO in question is service pack 1 and it needed to be altered.

Still haven't made any progress on this sadly, anyone got any more ideas?

Edit: Also tried the ImDisk method, still failed there too. Perhaps it does lie in how it's mapped, as the ISO method above works by itself on a dvd, so.. not quite sure how to proceed.

This post has been edited by RickRollNW: 17 June 2012 - 03:26 PM

[jaclaz]

It doesn't seem to difficult to me.

Have you followed "to the T" the instructions by Steve6375?
That is a yes or a no (no other answer is allowed).

If you reply "no", then you are on your own .

As I see it, in order to "go ahead" we need a starting point:
get a NON SP1 source and try replicating EXACTLY the tutorial by Steve6375, if you succeed, you can later introduce a variation, if it doesn't then we must find where exactly *somehow* you deviated from the tutorial.


jaclaz

[johnhc]

Quote

How does one use imagex to 'install' Windows? How can I apply this to my flash drive to obtain the prize I seek of dual 32 and 64-bit bootloaders?

RickRollNW, I think you use the Apply switch to imagex. I decided that it was not useful for the way I install W7 in my system so I looked no further. There are a number of people here with much more knowledge than I who can help. I assume you capture an image with everything in it, then run imagex and 'apply' the image to your system. Open a 'Deployment Tools Command Prompt' and issue imagex /apply /?',no quotes, for details. Enjoy, John.

[RickRollNW]

jaclaz, on 18 June 2012 - 02:19 AM, said:

It doesn't seem to difficult to me.

Have you followed "to the T" the instructions by Steve6375?
That is a yes or a no (no other answer is allowed).

If you reply "no", then you are on your own .

As I see it, in order to "go ahead" we need a starting point:
get a NON SP1 source and try replicating EXACTLY the tutorial by Steve6375, if you succeed, you can later introduce a variation, if it doesn't then we must find where exactly *somehow* you deviated from the tutorial.


jaclaz

Short answer: Yes.

So as to eliminate all possibilities and comply with your wishes I did as you asked before you'd even posted it. When I got home I did exactly as the ImDisk tutorial said, did not edit anything I wasn't supposed to (Only thing I did was pointed it to the iso, as was instructed in the tutorial, and the grub enteries because the iso is SP1 and the offset had to be changed, also noted in the tutorial.) copy pasted everything as necessary. It 'still' gives me the same error.

As an update, apparently the iso 'doesn't' work on a DVD. I had trusted the original thread it the instructions were pasted from, but come to find out, even when running from a DVD, if you select the 64-bit bootloader option, and go to install, you get prompted with the SAME error. So, it appears to be a flaw within the image, and nothing I have or haven't done in terms of how it is mapped. So, the question is, as it has been from the start I suppose, is it impossible to combine functioning 32 and 64-bit bootloaders into one iso?

So as to clarify as to what I did, I followed the instructions laid out when making a new iso, merging of sources, everything. I mapped it originally using my firadisk method, nothing. My/Steve's ImDisk method, same thing. Steve's method to the T, same thing. I proceeded to burn the disc on a dvd and booted from it, selected x64 Recovery Mode, hit install, and bam, missing CD/DVD driver error. So, it would appear to be an image method as I originally thought. If you want, I will attempt to acquire non-SP1 images to combine, but I don't know if it will work.

johnhc, on 18 June 2012 - 09:03 AM, said:

Quote

How does one use imagex to 'install' Windows? How can I apply this to my flash drive to obtain the prize I seek of dual 32 and 64-bit bootloaders?

RickRollNW, I think you use the Apply switch to imagex. I decided that it was not useful for the way I install W7 in my system so I looked no further. There are a number of people here with much more knowledge than I who can help. I assume you capture an image with everything in it, then run imagex and 'apply' the image to your system. Open a 'Deployment Tools Command Prompt' and issue imagex /apply /?',no quotes, for details. Enjoy, John.

Ah, I see, that does help me with plans for future builds all using the same hardware, thank you.

[johnhc]

RickRollNW, I found this tutorial on MS TechNet. I'm thinking of trying it on a VM. Enjoy, John.

[jaclaz]

@RickRollNW
I am not sure to understand your last report.

If I get it right you have discovered that the actual "base" .iso is "botched"? (it doesn't work also on DVD?)

Can you try with another source (possibly, in order to replicate, a SP0 one)?


jaclaz

[RickRollNW]

jaclaz, on 18 June 2012 - 08:55 PM, said:

@RickRollNW
I am not sure to understand your last report.

If I get it right you have discovered that the actual "base" .iso is "botched"? (it doesn't work also on DVD?)

Can you try with another source (possibly, in order to replicate, a SP0 one)?


jaclaz

The method behind it is botched. I burned the .iso in question to a DVD to test if it really worked as advertised. I booted from it in a computer. select the "x64 Recovery Mode" option, clicked Install (because that's my goal, to get a functioning 64-bit bootloader that actually manages to install) and it prompted me with the same missing CD/DVD driver error. Being that it's a DVD I can probably go into a VM and take snapshots if necessary.

In terms of source, I created two .iso's straight from OEM copies of Windows, the April batch. That's as untainted as possible, but if need be I can attempt again with other sources. So, my question is, what does a 64-bit dvd itself have that allows it to boot and load drivers correctly, that the bootloader we've made in this .iso not have?

[jaclaz]

RickRollNW, on 19 June 2012 - 11:34 AM, said:

In terms of source, I created two .iso's straight from OEM copies of Windows, the April batch. That's as untainted as possible, but if need be I can attempt again with other sources. So, my question is, what does a 64-bit dvd itself have that allows it to boot and load drivers correctly, that the bootloader we've made in this .iso not have?

I cannot say specifically, but it is not the first time that something that worked allright with a given "level" becomes non-working after a SP (or some particular update) is applied.

As an example we had this issue with fujianbc fast installer:
http://reboot.pro/10126/
http://reboot.pro/10...250#entry135150
http://reboot.pro/14186/

And, as another example, this issue with BOOTMGR and ramdisk entries:
http://reboot.pro/in...showtopic=11442

So, as already said, your next step should be to try replicating (hopefully successfully) what has been already tested (to the T, and this means WITHOUT *any* change of *any* type) with an older source, and from it check the differences when you re-do, still without any change with the "new" source.
If you insist of introducing a change, any one, even a teeny tiny one, there is simply no way to find what exactly the issue is.
What I always recommend is - when attempting to replicate a tutorial like the one linked to - to (temporarily) forget everything you know or learned from other sources and simply do what is written, if something is not clear, do not "invent" a way to overcome the difficulty, stop and ask for clarifications instead.
The primary quality of a tutorial is that it is (or should be) replicable exactly as it is.

Please also note how Steve6375 posted a couple of questions to which you have yet to reply .
Generally speaking questons and advice are posted in order to actually try and help you, and it would be nice if you could reply/comply to them .


jaclaz

[RickRollNW]

jaclaz, on 20 June 2012 - 02:53 AM, said:

I cannot say specifically, but it is not the first time that something that worked allright with a given "level" becomes non-working after a SP (or some particular update) is applied.

As an example we had this issue with fujianbc fast installer:
http://reboot.pro/10126/
http://reboot.pro/10...250#entry135150
http://reboot.pro/14186/

And, as another example, this issue with BOOTMGR and ramdisk entries:
http://reboot.pro/in...showtopic=11442

So, as already said, your next step should be to try replicating (hopefully successfully) what has been already tested (to the T, and this means WITHOUT *any* change of *any* type) with an older source, and from it check the differences when you re-do, still without any change with the "new" source.
If you insist of introducing a change, any one, even a teeny tiny one, there is simply no way to find what exactly the issue is.
What I always recommend is - when attempting to replicate a tutorial like the one linked to - to (temporarily) forget everything you know or learned from other sources and simply do what is written, if something is not clear, do not "invent" a way to overcome the difficulty, stop and ask for clarifications instead.
The primary quality of a tutorial is that it is (or should be) replicable exactly as it is.

I am in the process of acquiring non-SP1 images to attempt this again. I will follow everything to the letter, no changes.

jaclaz, on 20 June 2012 - 02:53 AM, said:

Please also note how Steve6375 posted a couple of questions to which you have yet to reply .
Generally speaking questons and advice are posted in order to actually try and help you, and it would be nice if you could reply/comply to them .

I had only seen one question from him, and I thought I'd answered it, but apparently I missed the second half.

steve6375, on 12 June 2012 - 01:34 PM, said:

Not to sure what is going wrong but this menu makes bootmgr load BC2 not BCD. I can't see any mention of making a BC2 in your posts?

title Windows 64-bit OS Install Menu (bc2)\nIf you want to install a 64-bit OS
map --mem /bootmgr (rd)
write --offset=0x105E (rd)+1 \xEB\x08
write --offset=0x54696 (rd)+1 2
chainloader (rd)+1
root ()

Once you are booted to WInPE, can you detect whether you have booted to a 32-bit OS or a 64-bit OS (look at SET variables?).

So as to be more clear, since it didn't 'click' you were the Steve in question, apologies.

title Windows 32-bit OS Install Menu (bc1)
map --mem /bootmgr (rd)
write --offset=0x105E (rd)+1 \xEB\x08
### write unicode BC1
write --offset=0x54735 (rd)+1 1
chainloader (rd)+1
root ()

title Windows 64-bit OS Install Menu (bc2)
map --mem /bootmgr (rd)
write --offset=0x105E (rd)+1 \xEB\x08
### write unicode BC2
write --offset=0x54735 (rd)+1 2
chainloader (rd)+1
root ()

That was taken exactly from the WinISO tutorial, and edited for the SP1 bootmgr, as also laid out in the tutorial. It covered the creation and implementation of the bc1 and bc2 files.

In regards to the second half of your question, I don't know how to check, if you could inform me as to how I will give you know the results.

[jaclaz]

RickRollNW, on 20 June 2012 - 10:58 AM, said:

In regards to the second half of your question, I don't know how to check, if you could inform me as to how I will give you know the results.

I presume it is "SHIFT+F10" -> get a command prompt
Type:

SET PROG

[ENTER]

You should get the values of
%PROGRAMDATA% %SystemDrive%\ProgramData
%PROGRAMFILES% %SystemDrive%\Program Files
%PROGRAMFILES(X86)% %SystemDrive%\Program Files (x86) (only in 64-bit version)

http://en.wikipedia....onment_variable
http://ss64.com/nt/s...-variables.html
or possibly running reg.exe:
http://support.micro...kb/556009/en-us

BTW NOT on the suggested:
HKLM\SYSTEM\CurrentCongtrolSet\Control\Session Manager\Envirornment.


More:
http://superuser.com...2-64-bit-in-cli


I don't think there is WMI available in the PE setup , but maybe this other way is handy:
http://social.techne...8f-da34346f1480
more:
http://superuser.com...using-a-command


jaclaz

[RickRollNW]

jaclaz, on 20 June 2012 - 11:18 AM, said:

Type:

SET PROG

[ENTER]

You should get the values of
%PROGRAMDATA% %SystemDrive%\ProgramData
%PROGRAMFILES% %SystemDrive%\Program Files
%PROGRAMFILES(X86)% %SystemDrive%\Program Files (x86) (only in 64-bit version)

http://en.wikipedia....onment_variable
http://ss64.com/nt/s...-variables.html
or possibly running reg.exe:
http://support.micro...kb/556009/en-us

BTW NOT on the suggested:
HKLM\SYSTEM\CurrentCongtrolSet\Control\Session Manager\Envirornment.


More:
http://superuser.com...2-64-bit-in-cli


I don't think there is WMI available in the PE setup , but maybe this other way is handy:
http://social.techne...8f-da34346f1480
more:
http://superuser.com...using-a-command


jaclaz

Apologies for the late reply, had a busy weekend. I ran the x64 recovery mode and did the following, and got these results.

X:\Sources>set prog
ProgramData=X:\ProgramData
ProgramFiles=X:\Program Files
ProgramFiles(x86)=X:\Program Files (x86)
ProgramW6432=X:\Program Files

When running in 32-bit, these were the results.

X:\Sources>set prog
ProgramData=X:\ProgramData
ProgramFiles=X:\Program Files

I didn't see you mention anything of a fourth entry, so, that threw me off a little. Downloaded and compiled a non-sp1 image last night, going to test it today and post the results when I can.

This post has been edited by RickRollNW: 25 June 2012 - 12:22 PM

[jaclaz]

RickRollNW, on 25 June 2012 - 12:17 PM, said:

I didn't see you mention anything of a fourth entry, so, that threw me off a little.

Yes, my bad, the suggestion was "generic" about 32/64, Windows 7 64 bit has the ProgramW6432 variable added allright (XP and Vista have it not):
http://msdn.microsof...4(v=vs.85).aspx

RickRollNW, on 25 June 2012 - 12:17 PM, said:

Downloaded and compiled a non-sp1 image last night, going to test it today and post the results when I can.

Good, let's see what happens.

jaclaz

[RickRollNW]

My attempts resulted in failure once more gentlemen.

I compiled non-SP1 images following the guideline posted earlier with zero deviation. My first attempt was through my standard firadisk map, resulted in failure.

My second was to use the winiso tutorial method seen here: http://www.rmprepusb...utorials/winiso

My menu.lst contained the following:

title Windows 32-bit OS Install Menu (bc1)
map --mem /BOOTMGR (rd)
write --offset=0x105E (rd)+1 \xEB\x08
write --offset=0x54696 (rd)+1 1
chainloader (rd)+1
root ()

title Windows 64-bit OS Install Menu (bc2)
map --mem /BOOTMGR (rd)
write --offset=0x105E (rd)+1 \xEB\x08
write --offset=0x54696 (rd)+1 2
chainloader (rd)+1
root ()

My RunISO's contained the following:

TITLE WINDOWS 32-BIT OS INSTALL
@echo off
cls
echo.
echo.
echo A = Win 7 SP1 64-bit Enterprise
echo B = Win 7 SP1 64-bit Starter\Home Premium\Professional\Ultimate

REM add more here




SET /P ANS="Which ISO do you want? : "




IF /I "%ANS%"=="A" SET MYISO=\ISO\en_windows_7_enterprise_with_sp1_x64_dvd_620201.iso
IF /I "%ANS%"=="B" SET MYISO=\ISO\7_AIO.iso


call \imdisk\MountDrive.cmd %MYISO%

TITLE WINDOWS 32-BIT OS INSTALL
@echo off
cls
echo.
echo.
echo A = Win 7 SP1 32-bit Enterprise
echo B = Win 7 SP1 32-bit Starter\Home Premium\Professional\Ultimate

REM add more here




SET /P ANS="Which ISO do you want? : "




IF /I "%ANS%"=="A" SET MYISO=\ISO\en_windows_7_enterprise_with_sp1_x32_dvd_620201.iso
IF /I "%ANS%"=="B" SET MYISO=\ISO\7_AIO.iso


call \imdisk\MountDrive.cmd %MYISO%

(Take note I didn't even edit the 32-Bit install title error in the 64-bit .cmd)

The firadisk map prompted me with a missing cd/dvd driver error (after loading x64 Recovery Mode and trying to install, standard setup still works but I ran the set prog in the command, and it returned with a 64-bit loadout. The Winiso map prompted me with the "The subsystem required to support the image type is not present." error. I also ran set prog there, and it returned 64-bit lines. Is it a signature in the iso/disc itself that cannot be overcome? I made absoloutely no deviations this time and it's still not working, even with a non-SP1 image.

[johnhc]

RickRollNW, I am really not qualified to reply to your problem, but have seen the CD/DVD driver missing message in another thread. This says simply that it is not a missing CD/DVD driver but a driver needed to locate an HDD to install Windows. It is just another example of bad MS Windows messaging. I was also curious what format of disk you are attempting to use - GPT or MBR? Will this affect your results? Enjoy, John.