[Mitch]

D.Konieczny, on Dec 6 2008, 08:52 PM, said:

You can find it on my download server

Thanks man, much appreciated

[segobi]

NetRoller3D I found these two which might be interesting (sysprep -pnp -clean) -
Do you have a test machine to test your prepped iso ?
Especially one that did not boot 6956 before...

[pjc007]

Well - I found the VHD, got it to part-boot, and had the often-seen problem that it crashes.

Tried the registry edit fix, but it still crashes, so I'm stumped. Unless someone can point me to a post that has a fix other than the registry edit?

Guess I'm going to have to wait for an installable ISO or even the real Beta 1 - lol...

PJC

[segobi]

Hmm sysprep on vista has no -pnp and no -clean... only oobe and generalize...im not sure if this will work.. At least it does not look like there is a command line to have the Hardware setup to restart...

[segobi]

segobi, on Dec 6 2008, 12:11 PM, said:

Hmm sysprep on vista has no -pnp and no -clean... only oobe and generalize...im not sure if this will work.. At least it does not look like there is a command line to have the Hardware setup to restart...

* When you copy Windows images between computers, the reference and destination computers do not need to have compatible hardware abstraction layers (HALs). The /detecthal option in the Boot Configuration Data (BCD) will enable a system that has already run Sysprep to install the correct HAL.
* The Plug and Play devices on the reference and destination computers, such as modems, sound cards, network adapters, and video cards, do not have to be from the same manufacturer. However, the drivers for these devices must be included in the installation.

[NetRolller 3D]

loopster: I know, but I intentionally recommended using imagex, as I am not sure whether 7zip can correctly extract a WIM that contains symlinks, junctions and mount points.

[rvbcrs]

NetRolller 3D, on Dec 6 2008, 12:31 PM, said:

loopster: I know, but I intentionally recommended using imagex, as I am not sure whether 7zip can correctly extract a WIM that contains symlinks, junctions and mount points.

Hi NetRoller, I use this commandline, can you please tell me if that is correct: IMAGEX.EXE /norpfix /capture /boot H: D:\6956.wim "Windows 7"
Where H: is the mounted .VHD

Thanks

[loopster]

NetRolller 3D, on Dec 6 2008, 05:31 AM, said:

loopster: I know, but I intentionally recommended using imagex, as I am not sure whether 7zip can correctly extract a WIM that contains symlinks, junctions and mount points.

you right netroller,the integrity is broken with 7zip plus using 7zip is read only

[loopster]

is this build hardcoded to timebomb in 22 days? looking at some of these screenshots ppl are making makes me thing so

[IsaacD]

(My post from another forum you asked)

You have to keep in mind that the timebomb is still continuing off from the Demo System that the VHD was originally on.

[NetRolller 3D]

Success! (This time really.)

I am capturing the sysprep-generalized system into an install.wim right now. I'll be building (and possibly releasing) an ISO today!

Until then, some instructions:

1. Have Windows 7 build 6801 (32-bit) installed. (Let's assume it's on C: when 6801 is booted - this is usually the case. Replace C: with your drive letter if it isn't.) Also have at least 10 gigabytes of free space on one of your partitions other than the one you are installing 6956 to.
2. Create a second partition (at least 20 gigabytes recommended) for 6956, and format it as NTFS. I'll call this D:, replace the drive letter with yours if it's different.
3. Extract the VHD from its RAR, and mount it. It will get a drive letter, which I will refer to as "E:", again replace in the commands as needed.
4. Download Imagex (x86) and extract the archive contents to C:\Windows\system32. Do NOT overwrite the already present files!
5. Fire up a command prompt (as admin/elevated, otherwise bcdedit will fail), and run this command to create a temporary WIM:

imagex /norpfix /compress none /capture E: C:\temp.wim "win7temp"

"Win7temp" is an arbitrary image name for the WIM, you can use anything here. You can also use image names other than "C:\temp.wim", but be sure to replace "C:\temp.wim" with the correct name in other commands as well if you do so.
6. Once the image is ready, extract it to the target partition:

imagex /apply C:\temp.wim 1 D:

Once this finishes, you can delete C:\temp.wim, we will no longer need it. You can also unmount the VHD at this point. Keep the command line open, we will need it later.
7. Open regedit, click "HKEY_LOCAL_MACHINE", go to the File menu, and click "Load Hive...".
8. Browse to D:\Windows\system32\config, and load "SYSTEM". When it prompts for a name, enter one (I used "SYSTEM.6956", but this is completely up to you).
9. Navigate to HKEY_LOCAL_MACHINE\SYSTEM.6956\ControlSet001\Services (replace SYSTEM.6956 with what you used in the previous step as the hive name).
10. Open the subkey "msahci".
11. In the right pane, double-click the "Start" DWORD, enter "0" as the value, and click OK.
12. Do the same for subkey "pciide". (You might also need to do the same for other mass storage drivers depending on your motherboard, such as "aliide", "amdide", "adpahci", "iaStorV", etc. - if unsure, check which driver 6801 is using for your mass storage controller.)
13. Navigate to HKEY_LOCAL_MACHINE\SYSTEM.6956, go to the File menu, and click "Unload Hive...". Answer Yes to the question that pops up. You can now close Regedit, you are done here.
14. Go back to your command line, and enter the following commands:

BCDedit /copy {current} /d "Microsoft Windows 7, build 6956"
BCdedit /set <guid result of previous command> device partition=D:
Bcdedit /set <guid result of previous command> osdevice partition=D:

15. Reboot. At the boot menu, go to "Microsoft Windows 7, build 6956", press F8, and select "Safe Mode with Networking". It will look like it has locked up at CRCDISK.SYS, but it is actually working on finding the root drive, and it will continue booting once it is found (for me, finding the root drive took about a minute the first time I booted). If it reboots after CRCDISK.SYS, you need to enable more mass storage drivers using the Regedit "load hive" method.
16. Windows should boot into Safe Mode. Close the Help screen that appears.
17. Wait until Windows recognizes your hardware. Once done, it will ask for a reboot - do so.
18. At the boot menu, select build 6956, and boot into normal mode. You should see the new boot screen - if you get the Vista boot screen, something went wrong.
19. Windows will recognize the remaining drivers. Reboot, and you are done!

Worked for me on an Asus P5K Premium on a SATA drive (or an IDE one with a SATA->IDE converter, but NOT with an IDE drive connected to the JMicron controller) with SATA set to either IDE or AHCI mode (but NOT RAID). You might need to enable different mass storage driver services depending on your motherboard.

rvbcrs: Read the guide for the correct command.

[IsaacD]

You're the best, bro.

Thank you so much for all your hard work and dedication in doing all of this, thank you.

[Swift]

Thanks a ton, NetRoller.

I appreciate all your effort into doing this.

[loopster]

damn hes so close to an iso no i bet he can smell it

[consume]

Nice work netroller. Hopefully everyone who got left in the dust can try it out now.