Windows 7 Live CD?

krokousdan · krokousdan's Computer Specs

My question was:
Can someone via the command line to control a mount registry?

Otherwise, there is both promise script and documentation.
Documentation for the Windows AIK is available for download here.
http://www.microsoft.com/downloads/d...displaylang=en
Here you will find many answers to your questions.
Or use the Wiki
http://en.wikipedia.org/wiki/Windows...stallation_Kit

Here is a script drawn from Help Windows AIK. I added only the variable "Set", I did not write a long path to folders.

Code:

@Echo off
%SystemDrive%

Set PEWAIK=%ProgramFiles%\WAIK
Set PETools=%PEWaik%\Tools\PETools
Set Architecture=x86
Set PEDest=%SystemDrive%\winpe_x86
Set ISOName=winpe_x86.iso

CD %PETools%

pushd %PETools%

call copype.cmd %Architecture% %PEDest%

Set PEISO=%PEDest%\ISO
Set PEMount=%PEDest%\mount
Set PEIBoot=%PEISO%\boot
Set PEISrc=%PEISO%\sources
Set PEFps=%PETools%\%Architecture%\WinPe_FPs
Set PEImageX=%PEWAIK%\Tools\%Architecture%

Dism /Mount-Wim /WimFile:%PEDest%\winpe.wim /index:1 /MountDir:%PEDest%\mount

Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-hta.cab"

Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-legacysetup.cab"

Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-mdac.cab"

Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-pppoe.cab"

Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-scripting.cab"

REM Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-setup.cab"

REM Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-setup-client.cab"

REM Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-setup-server.cab"

Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\winpe-wmi.cab"

Dism /image:%PEDest%\mount /Add-Package /PackagePath:"%PEFps%\cs-cz\lp_cs-cz.cab"
//Locale package

Dism /image:%PEDest%\mount /Set-AllIntl:cs-cz
//Setting  locale

copy "%PEImageX%\imagex.exe" "%PEMount%\Windows\System32\"

Dism /Unmount-Wim /MountDir:%PEDest%\mount /Commit

copy %PEDest%\winpe.wim %PEDest%\ISO\sources\boot.wim

del /q %PEDest%\ISO\boot\bootfix.bin

oscdimg -n -b%PEDest%\etfsboot.com %PEDest%\ISO %PEDest%\%ISOName%

Cls
DTCZ
Exit

Here are the promised tree two projects.

I still do not understand. what do you see fraudulent!
I note that this is not a fully functional OS. 100% functional as the command line.
If you want to get into the Explorer environment, so just enter CMD in the "notepad" and select "open all types. Then you can use the right mouse button as a normal OS.

You need to delete a protected folder or file? Need to remove a virus? You need to partition? Need to deploy CHKDSK? ...... So this is the right solution?

**Core** · Core's Computer Specs

You know what, I think this is on the level. There's no reverse engineering from what I see...just a customized WinPE environment.

Having access to Windows recovery tools and CLI without having to boot into an infected system would definitely be useful. Particularly if you could edit the registry...that would be cool.

I think this shows a lot of promise, Krokousdan.

krokousdan · krokousdan's Computer Specs

Quote:

Originally Posted by Core

You know what, I think this is on the level. There's no reverse engineering from what I see...just a customized WinPE environment.

Having access to Windows recovery tools and CLI without having to boot into an infected system would definitely be useful. Particularly if you could edit the registry...that would be cool.

I think this shows a lot of promise, Krokousdan.

Thank you for your consideration.
Just working on the registry. I hope that I can decipher it, and certainly with you so I will share.

voodew2u · voodew2u's Computer Specs

Quote:

Originally Posted by Core

I'm still not convinced that this doesn't break the EULA.

I know the virtualization bit in the EULA states that you can run 7 in a virtualized environment on a machine for which you have a license, so long as you do not run both at the same time. In other words, if you're running XP and buy a copy of 7 for your PC, you can run the copy of 7 in Virtualbox without breaking the EULA. But as I understand it, you're not allowed to use the one license to run Windows 7 simultaneously both on the hardware AND in a virtual environment.

One of the things that activation does is prevents copies of Windows from being installed on several different machines. That's why you run into problems with activation when you install it on one PC, then a different one, and another, and another...

So if you create a live CD of Windows 7 for purposes of using it to "help fix PCs when they don't boot," does that not imply that the same copy will be used, even if not simultaneously, on multiple different computers with various hardware configurations? You would not be able to normally install Windows and activate it on all those machines; sooner or later you'd fail activation.

Therefore you would probably have to find a way to bypass activation, yes? Or use that copy of Windows without activating it.

I'm just not sure this is what Microsoft had in mind when they adjusted the Windows EULA to include virtualization.

Don't get me wrong - I don't really give a crap about the EULA. But I also don't want people to think that this is on the level if it in fact is not.

Your thoughts?

I think you just reasoned away Windows PE. If you are using 1 installation per key at a time then there is no problem. Even if you installed your original Windows CD to one computer at a time, (no booting from the previous installation) and had to call M$ to install on different hardware configurations, they'd still validate the installation. Why? M$ welcomes migration and you're not violating their EULA by migrating from system to system.
If you have a valid m$ OS, it can be run on any system but only 1 instance can be running at a time since that's what you paid for. That's why M$ made Windows PE. M$ didn't create the PE to violate their EULA. It was made to satisfy developers and technicians.

**Core** · Core's Computer Specs

Quote:

Originally Posted by voodew2u

I think you just reasoned away Windows PE. If you are using 1 installation per key at a time then there is no problem. Even if you installed your original Windows CD to one computer at a time, (no booting from the previous installation) and had to call M$ to install on different hardware configurations, they'd still validate the installation. Why? M$ welcomes migration and you're not violating their EULA by migrating from system to system.
If you have a valid m$ OS, it can be run on any system but only 1 instance can be running at a time since that's what you paid for. That's why M$ made Windows PE. M$ didn't create the PE to violate their EULA. It was made to satisfy developers and technicians.

I had changed my position by the end of the thread, but I assume you didn't get that far before you decided to necro it.

iTpHo3NIX · iTpHo3NIX's Computer Specs

I read this looking up information about creating a Live CD disk because they can do much more then that. I'm not sure if any of you are familiar with the Geek Squad MRI disk.

It contains a list of diagnostic software, then also includes a VLC copy of windows vista for the LiveOS which has tools and scripts to help Geek Squad employees fix your computer (although they aren't real technicians since all thye do is point and click with a tool)

HOWEVER, I would like to make one, and there is a way to mount the registry as password reset tools and others (such as the Trinity Rescue Kit)

Also I wanted to create my own LiveCD using WinPE from the WAIK.

For system technicians, imagine a USB, this USB (we'll say an 8GB) has several memory, hardware debugging, harddrive diag, recovery software, etc. Plus a Windows Live environment where you can browse files on the hard drive easily, add/remove startup stuff (on the host machine)

I remember working on this lady's computer that she had set up for her kids, her kids are grown and old but she couldn't remember the password to get past the OS loading (the second the OS loaded it would lock out and require a password. What I ended up doing was popping in the MRI disk and then I was able to locate the startup registry entry from the application and was able to manually remove it from the system (deleting registry information and files) then ran a cleanup (pretty much an embedded ccleaner)

Pretty much what I'm saying is M$ added the ability to do this with the WAIK and they document step by step on how to accomplish it. What I know is I'm going to create a boot disk with several tools so I just keep it updated

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to Install Windows 7	davehc	Software	0	08-16-2010 02:50 PM
Windows 7 Annoyances	Nibiru2012	General Discussion	6	03-17-2010 06:17 PM
Clean Install Windows 7 with Upgrade Media	Nibiru2012	Installation, Setup and Updates	0	12-22-2009 07:03 PM
Clean Install Windows 7 with Upgrade Media	Nibiru2012	Installation, Setup and Updates	2	12-04-2009 06:30 PM
Important Issues in This Release Candidate of Windows 7	Ian	News	0	05-05-2009 03:25 PM