PLEASE NOTE: I highly recommend Win8ToGo instead of running Windows 7 from a USB drive. To boot Windows 8 from USB - please see. Win8ToGo is designed to run from a USB drive and supports USB 3.0 booting - it will be far more 'stable' than Win7ToGo. Introduction Please note: This tutorial enables you to prepare a USB drive so that you can boot directly to Windows 7 from the USB drive. So now you can try Windows 7 without needing to install it onto your internal hard disk!
IT WILL ONLY WORK ON A USB 2.0 PORT (see instructions at the end of this page for instructions on how to add USB 3 drivers). This tutorial as based on fujianabc's Reboot.pro forum post and his excellent scripts (now with reg tweak by 'cdob' from reboot.pro -USBBootWatcher is no longer required). The instructions in that forum post #1 & #2 and some of the prompts in the installer.cmd file that fujianabc provides were however confusing and potentially dangerous (you could accidentally corrupt your system drive) - so I have slightly modified his script to make it clearer and easier to use. It also now automatically finds and uses the 3 files that are needed from the MS WAIK, so you don't need to manually copy them first. The instructions below assume that you have a USB drive (USB Hard Disk - recommended, or USB Flash drive - slow!) and you want to install Windows 7 onto it using a Windows 7 install DVD (or ISO file) as the source. You can use any 32/64-bit mix - e.g.
Use a Windows 7 64-bit PC to install say Vista 32-bit OS from a Vista 32-bit installation DVD onto a USB drive, or use a Windows XP system to install Windows 7 64-bit onto a USB drive using this method. Note that some CPUs' (e.g. Some netbook Atom 32-bit CPUs) won't run a 64-bit OS, so a 32-bit version of Windows 7 is usually best for these. You will need to activate Windows using a valid Product Key (which will be locked to the hardware you booted it on) if you want a fully functional version of Windows for over 30 days. You cannot just plug the USB drive into another system. If you want to move it to another system (once you have booted it on one system) then you need to sysprep it (see ADDENDUM at the end of this page). This is because on first boot, a fresh copy of Windows will detect what hardware is on the system and install the correct drivers (including the drivers for the boot drive).
If you try to boot that USB drive on another system without running Sysprep, you may just get a BSOD (0x0000007B blue screen of death error). No drivers are included in the image if a plain Windows installation DVD is used as the source DVD. You will need to install drivers once Win7 is booting. A USB Flash drive will be quite slow (1-2 hours!) to install and run Windows from, unless you use a fast USB 3 Flash drive, such as BUSBI Boost USB 3 (even on a USB 2 port, USB 3 Flash drives are usually faster than USB 2 drives, but not, of course, as fast as a standard USB hard drive or USB 3 drives on USB 3 ports).
I highly recommend you use a USB hard drive or a USB 3 Flash drive. Windows 7 does not contain many USB 3 compatible drivers - so if you try to boot from a USB 3.0 port it will probably crash!. A USB hard drive of at least 10GB NTFS formatted (which may be wiped during this process). A Flash drive can be used but it will be slow!. The whole installed (or at least the files bootsect.exe, bcdboot.exe and imagex.exe) or see for a method of obtaining these files in about 30 seconds without needing to download and install the whole WAIK (Note: Download the Windows 8 WAIK files, the Win 7 WAIK download does not contain bootsect.exe).
The download from the page. A Windows 7 installation DVD (or ISO file which you can mount as a drive letter) - see to download a copy of Windows 7.
(optional) RMPrepUSB to partition the USB hard drive. One word of caution: Disable antivirus during this process. It blocked Dism from making the changes it needed to do. I then was able to install to the USB HDD and it booted fine from USB 2.0 port. Unfortunately, Trying to boot from USB 3.0 port would still bluescreen. I went into the registry after booting from USB 2.0 and changed: HKEYLOCALMACHINE - SYSTEM - ControlSet001 - services - iusb3hub and HKEYLOCALMACHINE - SYSTEM - ControlSet001 - services - iusb3xhc for both of those entries, I changed 'Start' to '0' and 'Group' to 'Boot Bus Extender' This will vary based on the USB3 driver in use, but this worked for the Intel USB3 drivers.
Thank you for your suggesttion. But this is not a good idea. My current installer can install vista and win7, but there is no wimmount.sys or wimserv.exe in vista's install.wim.
On the other hand, even you only install win7, when you install x64 win7 under x86 windows/winpe or install x86 win7 under x64 windows, wimmount.sys cannot be used. I simply did not consider Vista as an OS system worth to be installed (actually as an OS at all). Really cannot say anything about x64, I got from Lancelot that wimcaptex (and my batches) worked on x64 as well: jaclaz. Ehm, lets clean the dust in ears. Wow64 available on LiveXP (thanks to JFX) and I guess will be available on multi7pe and vistapeleopard this year.
Thank you for giving me the news. I'll try the livexp with wow64 these days. Thank you for sharing this idea! Keep it upI have one question fujianabc. I want to convert an already working XP partition with applications to VHD using HD to VHD tool found here. Then, I can convert the VHD using GImageX to.wim file. Now after this, can I add it into your setup and install Windows XP using the wim image that I created?
Thanks!First, I think you can directly capture the xp partition to wim with imagex or gimagex. You needn't convert it to vhd. Secondly, I think my current installer cannot directly install the xp wim image. But it is very easy for you to install the xp wim image with imagex. You only need to imagex/apply the wim to a partition and then edit the boot.ini. I'm in a situation where we need to deploy Windows7.
I used this tool to install Windows onto a SATA HDD which was attached with a usb adapter. When I took the drive out of the adapter and placed into the machine we were trying to deploy, it wouldn't boot. I took the drive and hooked it back up to my machine via USB and noticed that it wasn't set as active in Drive Management. Once I set it as active, I was able to boot it successfully in the other machine.
Is booting from USB different from booting internally, as far as active partitions go? I don't see anywhere in the code where the partition is set active. I'm in a situation where we need to deploy Windows7. I used this tool to install Windows onto a SATA HDD which was attached with a usb adapter.
When I took the drive out of the adapter and placed into the machine we were trying to deploy, it wouldn't boot. I took the drive and hooked it back up to my machine via USB and noticed that it wasn't set as active in Drive Management. Once I set it as active, I was able to boot it successfully in the other machine. Is booting from USB different from booting internally, as far as active partitions go?
I don't see anywhere in the code where the partition is set active.I did't include any process of a partition in this installer. You need to create the partition, set active and format before you start this installer. Hi fujianabc 1.I have tested your nt6.x in several situations,it's ok most of the times, but some times it gives error that 'Can not copy install.wim and boot.wim' and even i copy that files to needed folder it does not cntinue.
I could not understand what is the problem (i have tested and i am sure my source files are OK). 2.It is really very good prgramming and very useful application.Can you update it so to be able to run from DVD?
Shirin zabanI have even no prompt 'Can not copy install.wim and boot.wim' in the script, can you give a plot? The WIM (Windows imaging format) is interesting: but there is a speed problem being file-based, in comparison with other sector-based imaging solution like Symantec Ghost or Acronis True Image.
Edit (add): there is an advantage though, using the WIM/imagex method. This allows installing dual boot system, for example by installing to D: partition where C: already contains an old XP. The dual boot does not destroy current data in D: (good), which is not the case by restoring image sector-based as with Ghost/True Image. Fujianabc Very interesting and Thanks a lot. Tested with no success.
Windows is looping as following state: 'Setup is preparing your computer for first use' and after a while restart. Build environment = xp pro sp3. Source = Win 7 ultimate 32bit. Destination = slim usb hdd 300gb, 40Gb first primary partition active Gigabyte GA73PVM mobo, p4 3.0, 2 gb ram Here, attached some reg files (runonce, setup) after looping.
3.59KB 2622 downloads B Regards, YahooUKVery strange, some problems happen during oobe? No problem at oobe running. Formating several times and tested with partition or whole disk. Not succeeded at all.
I think it would be my buggy mobo. So I retested at work with DELL Optiplex 760 mini PC.
First time, not working with first primary partition active mode. Second time, not working with whole volume active mode.
Third time, it did work with first primary partition active mode. Flawlessly working but not working with other type of PCs at all. (when trying, sysprep sysprep.exe /oobe /generalize /shutdown, fatal error occurs and never worked for me.) Experienced with some errors as follows. Depends on the USB ports.
(if not working with front ports, try with back ports as mostly working with back ports) 2. Depends on mobos. (some not working and black screen and freezing. Many thanks, YahooUK. Experienced with some errors as follows. Depends on the USB ports.
(if not working with front ports, try with back ports as mostly working with back ports) 2. Depends on mobos. (some not working and black screen and freezing. I would phrase #1 as ' ALWAYS use the back ports when experimenting, ONLY try the front ones AFTER you managed to succeed with the back ones'. About #2, it is possible that the 'correspondent' to the Dietmar's modified NTDETECT.COM is needed, that single little file has proved to solve problems on a multitude of Motherboards for XP/2003 (strangely enough being at the time DELL motherboards the most common troublemakers).
Windows Nt 6 Download
Distributing, installing, updating and uninstalling software applications are common tasks in all enterprises. These tasks include a lot of processes and usually take up a lot of administrators' time and resources. Each of these tasks has to be completed in individual computers. The Software Deployment feature in Desktop Central enables administrators to distribute, install, update and uninstall software applications remotely as well as automatically. Features The Software Deployment feature in Desktop Central enables you to complete the following tasks:.
QuarkXPress for Mac: Free Download - Desktop publishing solution. Download the latest versions of the best Mac apps at MacUpdate. QuarkXPress for Mac, free and safe download. QuarkXPress latest version: Industry-leading package for design and layout. 10 years ago, if you'd asked anyone in the. QuarkXPress 6.5 makes it easier to retain a powerful presence in the world of art and publishing! Full-resolution previews lets artists scale or magnify images with. Find great deals for QuarkXPress 6 for Mac. Shop with confidence on eBay!
Create a repository of packages. This enables administrators to re-use packages any number of times to install or uninstall the software applications.
Deploy both MSI and EXE-based software applications. Use the set of predefined templates to deploy software applications. Perform pre-deployment activities for software installation/ uninstallation. Install software applications as a specific user using the Run As option.
Copy the installables to computers before installing software applications. Schedule deployment of software applications.
Uninstall MSI and EXE-based software applications. Desktop Central's Windows Installer feature improves the administrator's productivity by supporting remote MSI & EXE software/application deployment.
Desktop Central can automatically install MSI & EXE software to users or computers at a scheduled time. Desktop Central supports software installation to users and computers or mass installation to OUs, Domains and Sites.
Creating Software Repositories Software repositories are used to store software packages. These packages can either be for MSI-based software applications or EXE-based software applications. A software package added in Desktop Central will have the location of the installation files along with the installation and uninstallation commands. A package once added can be used to deploy the software any number of times by just defining a configuration. Pre-Deployment Activities For ensuring a smooth and successful software deployment, Desktop Central provides the option to validate a set of conditions before a software installation/ uninstallation.
Windows Nt 6.1 Download
The pre-deployment activities include checking for previous software versions, running processes of dependant executables, free disk space etc. Upon validation of each of these conditions, you can decide on proceeding with or skipping the installation/ uninstallation. Scheduled Software Deployment Desktop Central allows administrators to schedule a software deployment to users and computers after a specified time. This is very useful in deploying the software after business hours to ensure users/computers are not affected due to this deployment. The network traffic will also be minimum at off hours. Visibility on Software Installation Status Desktop Central does not stop with just installing MSI/EXE software in the user machines; it also provides the status of the installation for the administrator to check whether the installation was successful in all the configured systems.
The software installation status is made available in the Desktop Central client, which can be accessed from anywhere in the network through a web browser. Uninstalling MSI and EXE-based Software In addition to installation of Windows software, Desktop Central also provides an ability to uninstall the MSI software applications that have been installed using Desktop Central. The details of the installed software are maintained under the configurations. The administrator can just open the configuration, edit it and choose to remove the software that was previously installed. For more details, refer to the topic in the online help. Deploying Software Applications Using Templates The Templates tab in the Software Deployment section comprises of predefined applications that you can use to create packages automatically.
This functionality downloads binaries from the respective vendors' websites to create packages automatically. You can create a single package or multiple packages from the Templates tab and deploy them to target computers.
Distributing, installing, updating and uninstalling software applications are common tasks in all enterprises. These tasks include a lot of processes and usually take up a lot of administrators' time and resources. Each of these tasks has to be completed in individual computers.
The Software Deployment feature in Desktop Central enables administrators to distribute, install, update and uninstall software applications remotely as well as automatically. Features The Software Deployment feature in Desktop Central enables you to complete the following tasks:. Create a repository of packages. This enables administrators to re-use packages any number of times to install or uninstall the software applications. Deploy both MSI and EXE-based software applications. Use the set of predefined templates to deploy software applications.
Perform pre-deployment activities for software installation/ uninstallation. Install software applications as a specific user using the Run As option.
Copy the installables to computers before installing software applications. Schedule deployment of software applications.
Uninstall MSI and EXE-based software applications. Desktop Central's Windows Installer feature improves the administrator's productivity by supporting remote MSI & EXE software/application deployment. Desktop Central can automatically install MSI & EXE software to users or computers at a scheduled time.
Desktop Central supports software installation to users and computers or mass installation to OUs, Domains and Sites. Creating Software Repositories Software repositories are used to store software packages. These packages can either be for MSI-based software applications or EXE-based software applications.
A software package added in Desktop Central will have the location of the installation files along with the installation and uninstallation commands. A package once added can be used to deploy the software any number of times by just defining a configuration. Pre-Deployment Activities For ensuring a smooth and successful software deployment, Desktop Central provides the option to validate a set of conditions before a software installation/ uninstallation. The pre-deployment activities include checking for previous software versions, running processes of dependant executables, free disk space etc. Upon validation of each of these conditions, you can decide on proceeding with or skipping the installation/ uninstallation. Scheduled Software Deployment Desktop Central allows administrators to schedule a software deployment to users and computers after a specified time. This is very useful in deploying the software after business hours to ensure users/computers are not affected due to this deployment.
The network traffic will also be minimum at off hours. Visibility on Software Installation Status Desktop Central does not stop with just installing MSI/EXE software in the user machines; it also provides the status of the installation for the administrator to check whether the installation was successful in all the configured systems. The software installation status is made available in the Desktop Central client, which can be accessed from anywhere in the network through a web browser. Uninstalling MSI and EXE-based Software In addition to installation of Windows software, Desktop Central also provides an ability to uninstall the MSI software applications that have been installed using Desktop Central. The details of the installed software are maintained under the configurations.
The administrator can just open the configuration, edit it and choose to remove the software that was previously installed. For more details, refer to the topic in the online help. Deploying Software Applications Using Templates The Templates tab in the Software Deployment section comprises of predefined applications that you can use to create packages automatically. This functionality downloads binaries from the respective vendors' websites to create packages automatically.
You can create a single package or multiple packages from the Templates tab and deploy them to target computers.