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.com/tutorials/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.

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.

I am in the process of acquiring non-SP1 images to attempt this again. I will follow everything to the letter, no changes. I had only seen one question from him, and I thought I'd answered it, but apparently I missed the second half. 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.

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?

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. 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.

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. I meant, like in the tutorial Point #10: 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/board/forum/157-install-windows-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. Not entirely buddy, it did resolve one other issue I'd been having, and the 'cosmetic' issues are of no consequence. 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? 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.

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, 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. 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.

This is starting to get very annoying... heh. I did the above in the RMPrep tutorial almost exactly, the only thing I changed was their section on the two runiso.cmd edits. Being that I had no need for multiple ISO prompts, I changed it just to automap my single ISO. Now comes the funny part. Even having two separate and external boot.wims and two separate grub4dos enteries, it still didn't load it when I went to choose the 64-bit option, and yet, as almost predicted, the 32-bit continued to function correctly. Here is the code snippet from the grub enteries. title Windows 32-bit OS Install Menu (bc1)\nIf you want to install a 32-bit OS 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)\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 () As well as my RUNISO.cmds. TITLE WINDOWS 32-BIT OS INSTALL @echo off cls echo. echo. SET MYISO=\ISO\Win7.iso call \imdisk\MountDrive.cmd %MYISO% TITLE WINDOWS 64-BIT OS INSTALL @echo off cls echo. echo. SET MYISO=\ISO\Win7.iso call \imdisk\MountDrive.cmd %MYISO% 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?

Very well... I'll try this again. Coupled with the above, this is my current Firadisk map, as well as the Windows boot manager readout. title Install Windows 7 SP1 AIO set MYISO=Win7.iso dd if=()/firadisk/au.xml of=()/AutoUnattend.xml map --mem (md)0x800+4 (99) map /ISO/%MYISO% (0xff) map (hd0) (hd1) map (hd1) (hd0) map --hook write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/ISO/%MYISO%;\n\0 chainloader (0xff)/BOOTMGR || chainloader (0xff) Windows Boot Manager -------------------- identifier {bootmgr} description Windows Boot Manager locale en-US inherit {globalsettings} default {default} displayorder {default} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {default} device ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description 32-Bit Bootloader locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot32.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes Windows Boot Loader ------------------- identifier {613fe2f0-2356-11de-bf6a-001e4cdc40b1} device ramdisk=[boot]\sources\boot64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} path \windows\system32\boot\winload.exe description 64-Bit Bootloader locale en-US inherit {bootloadersettings} osdevice ramdisk=[boot]\sources\boot64.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} systemroot \windows detecthal Yes winpe Yes ems Yes The methodology I use here seems to be nearly identical to the Firadisk link you sent me, with a few minor alterations on my end. This map has never failed me, and should be noted, does have 64 bit drivers to map with, as I've used this method to map two separate Vista iso's for repair purposes, as for some reason when their archs are combined, the setup slows to an absolute crawl. The IMDISK method I used was copied and pasted exactly from the page you linked me. Since taking the steps I did above with the boot.wims, my attempts so far have been to first boot from the Firadisk method. I get, as was hopefully expected, the boot Windows boot manager, asking me to choose which bootloader I want. I chose 64 for the attempted install, and each time, regardless of Firadisk, Imdisk, or direct emulation from Grub4dos, it still resulted in a missing CD/DVD driver error, yet whenever I booted into the 32-bit bootloader (also regardless of method) it worked fine. I am baffled. So, my reason for leaving out the above is that again, it seems to be an issue with the images themselves and not how they're mapped, but.. I could very well be wrong. The USB drive from which I am booting is NTFS as well, not sure if that matters, but I don't want to leave out any information again.

Yep , I had guessed that (since you completely failed to mention firadisk, as well as any actual detail on how you have currently setup your iso ), the suggestion was to try using IMDISK instead (as it comes in 64 bit version and signed) but the not-so-hidden attached strings was YMMV . jaclaz My apologies, I hadn't thought it relevant because the issue seemed to persist regardless of mapping, I will be sure to include such details next time. I did, however, attempt the IMDISK method, and the results were the same. So. It appears to be something on the image's end. [quote name=bphlpt' timestamp='1339182152' post='1000536] Of course not. WinPE (boot.wim) doesn't support WoW, so you need to match archs for either build. I use x64 boot.wim to do everything nowadays tho. Tripredacus, if RickRollNW is anything like me, I'm sure he's just as confused. Could you please clarify the apparent contradiction? Cheers and Regards Yes, I was indeed a tad confused by this at first, but I had figured out what he'd meant later. My attempts thus far have been unsuccessful, does anyone else have anything that can shed some light? Should I attempt to do it the other way around, using a 64-bit image and adding in the 32 images and boot.wim after?

Hi all, Thank you for the replies, was surprised to see so many. Let me lead in with a comment in regards to the raid drivers. This happened on two different controllers; An LSI 9260-8i in a server I was building for a customer, what first shed light on the flaw, as I would load the 32-bit driver and it would show the raid's VD's fine. But when I loaded the 64-bit, they'd disappear from the drive selection screen. I was forced to load with a 64-bit dvd, where the 64-bit drivers worked as expected. Otherwise, when attempting to install with the 32-bit drivers, when it came time to boot to continue the installation, I got the notification about the corrupt drivers. The same results happened on a lower end video editing system another customer had purchased on the 2011 platform, ASUS P9X79 Deluxe motherboard with an Intel raid controller, went to load 64 bit drivers, nothing appeared, 32 bit, drives appeared, finished first half of install, boot, iastor.sys is corrupt and/or missing, just as the above. In regards to the links provided to resolve the CD/DVD issue, I actually do map the iso in question with Firadisk already, but I've also tried just a straight iso emulation without it, and the result is the same either way, the x86 half works as it always has, but the added x64 does not, so the provided links may or may not be all that helpful. I am not against switching out of an ISO format either, I am fine with working with a raw directory install as I've seen some configurations where grub4dos can chainload certain images within .wim files. I will separate the 32 and 64-bit install.wims too if necessary, as that in itself doesn't take up that much more space, it's having to duplicate everything else along with them that does. My end goal is to have 32 and 64 bit bootloaders so I can select the appropriate drivers, doesn't matter if install.wim's have to be separated, though I don't know how to point each setup file to the different install.wim's if I do. I don't know if 32-bit really can load 64-bit drivers, but my experiences so far tells me that isn't the case. I'll keep attempting to tear into this, see if I come up with anything, hope to hear some more from you guys soon. Edit: Also, it should be noted that while attempting to troubleshoot this, I removed the original install.wim and replaced it with a straight 64-bit install.wim. The same error occurred. I also copied the entire 64-bit sources folder over when doing this, though kept the 64-bit boot.wim labeled as boot64. The 32-bit end still continued to function correctly, the 64-bit remains nonfunctional. Not sure what I am missing to bridge the gap, as it were.

Greetings, Let me start off by saying what a pain in my backside this project has been, I am by no means the smartest person in the world but I cannot for the life of me figure this out. I have created multiple iso's over the past year that have combined 32 and 64-bit editions of Windows 7, all worked fine. But as of a week ago I noticed they had a fundamental flaw. They're loaded using the 32-bit boot.wim. Meaning, if/when the time comes specific drivers have to be installed (RAID drivers specifically in this case) the proper version won't work. Example. I can load the 32-bit raid driver, and it will see the raid volume, and install just fine. But when it comes time to boot, it says the driver is corrupt. When attempting to use the proper driver, it won't see any of the volumes. I was baffled at first, until it hit me what the problem was, and I used and actual plain 64-bit disc to install and everything went fine. So. My undertaking has been to try to create a menu within my iso that will let me choose either the 32-bit or 64-bit boot.wim so I can load the proper drivers. I've searched for days with only pieces of anything even related to my case. Here is where I sit: Renamed boot.wim to boot32.wim and added 64-bit boot.wim labeled boot64.wim. Used BCDedit to edit boot\bcd to seek 32-bit wim properly and added option for 64.bit. Upon testing via VM, works fine on 32-bit end, doesn't work on 64-bit, get prompt for missing CD/DVD driver. I use the ISO on my thumbdrive via grub4dos emulation on a regular basis, being that I work as a technician in a retail outlet and I am always either installing Windows or using it to do repairs on others. It worked great until I figured this out, so, my goal now is to buff out the last (hopefully) remaining dent in this theory. If ANYONE could PLEASE shed some light on this process or on what I'd have to do, I'd appreciate it. I am open to any suggestions at this point (short of splitting the versions into two isos, takes up too much room.) I will also provide any information as needed. Thank you.