Pwboot 3.0.2.exe
A Facebook page dedicated for PWBoot project. PWBoot Project added 5 new photos to the album: Special Case. PWBoot 3.0.2.exe.
This software was tested by.Objects to scan: 'PWBoot+3.0.2.exe' Enable=Yes Recursive=No - ScanObjects$1197119 running 50% PWBoot+3.0.2.exe - OK ScanObjects$1197119 completed - Statistics - Time Start: 2014-04-11 09:25:50 Time Finish: 2014-04-11 09:25:50 Completion: 100% Processed objects: 1 Total detected: 0 Detected exact: 0 Suspicions: 0 Treats detected: 0 Untreated: 0 Disinfected: 0 Quarantined: 0 Deleted: 0 Skipped: 0 Archived: 0 Packed: 0 Password protected: 0 Corrupted: 0 Errors: 0 Last object.
Pwboot 3.0.2 (no-upx).exe
Introduction What is PWBoot project? PWBoot stands for Portable Windows Boot project, this project aims to be make your Windows operating system to boot from USB storage media easily. Tested storage list. USB Flash.
Kingston DataTraveler 100 (8GB). Sandisk Cruzer Extreme (16GB). Apacer Handy Steno AH328 (8GB). USB HDD. Standard 2.5 inch IDE HDD (60GB). Standard 2.5 inch SATA HDD (120GB).
Standard 3.5 inch IDE HDD (40GB). Seagate FreeAgent Go (320GB) Supported boot methods. Virtual hard disk (VHD). Windows 7 (Ultimate, Enterprise). Windows Server 2008 R2. Windows 8. Physical drive (Native).
Windows Vista. Windows Server 2008.
Windows 7. Windows Server 2008 R2.
Pwboot 3.0.2.exe
Windows 8 Important!. You do not have to use other USB booting program such as USB Watcher. Remember to re-patch after a new service pack updates installed. Optimization Tips. Use HDD instead of FDD. Turn off indexing service.
Use for enable pagefile on USB (Windows 7+). Defragment the disk. NTFS compression. Changelogs Version 1.0 - Initial release. The best way to transfer: disk cloningAnd I'll need no other changes?
Besides, will the cloned windows installation detect the portable partition with the same drive letter as teh original windows partition? Meaning, if my org. Windows drive was C, when booting from the cloned portable partition, will windows still recognize the boot partition as C - or will it use the portable partition's default drive letter? And in teh same note, will the drive letters of the other drives be shuffled as well. I'm asking this question because something similar happened to me while booting of my port.
HDD ( usign XPE ). And I'll need no other changes? Besides, will the cloned windows installation detect the portable partition with the same drive letter as teh original windows partition?
Meaning, if my org. Windows drive was C, when booting from the cloned portable partition, will windows still recognize the boot partition as C - or will it use the portable partition's default drive letter? And in teh same note, will the drive letters of the other drives be shuffled as well. I'm asking this question because something similar happened to me while booting of my port.
HDD ( usign XPE ) I think it doesn't require changes to make it work, since I never tested this method. Windows Vista will assign system drive as C: by default.
Pwboot 3.0.2
If BSOD happened, try to unplug the HDD that you clone from. In any case, will the patching cause any issues with my current installation?
No, I'm using it as my main OS for very long time without any issues. Do you mind tell me the inner-workings of the patching process - AS in what files were patched and the like? 1.checkispatchable - true (enable patchbutton), false (disable patchbutton) 2.patch - patch usb related setup information (.inf), update registry, copy required driver file if doesn't exist. 3.patchsuccess - true (success msg), false (error msg). A question: How is it possible to avoid the problem of different CPU's on the computers, especially the thing with drivers and not to get a BSOD? Another question: Is it possible to automatic clean the current hardware configuration, so there are no problems at the next reboot?
And how can this be done WITHOUT destroy software with drivers for virtual hardware (VirtualCD, Daemon Tools, the most VPN software, and so on)? I ask this because my 'dream' is to have an universal rescue system which is based on an 'installed' Windows.
And this needs not to have any trouble with the different hardware on the customer's computers. A question: How is it possible to avoid the problem of different CPU's on the computers, especially the thing with drivers and not to get a BSOD? So far, I booted my Vista from USB on differences of machines (from Intel P4 to Quad CPU, Desktop to Laptop) without any BSOD issues. Except Boot Manager throw 0xc000000e error with some older machine (BIOS has poor support for USB booting?) Another question: Is it possible to automatic clean the current hardware configuration, so there are no problems at the next reboot? And how can this be done WITHOUT destroy software with drivers for virtual hardware (VirtualCD, Daemon Tools, the most VPN software, and so on)? No, I don't have any idea to clean the hardware configuration, but I think that Windows will unload the unneeded drivers on different machine.