Hello dear guest!

Why not join our boot disk community? So do it. Life's short!

  - You get free access to our newsletter with all the interesting buzz about boot disks
  - We share publicity revenue with everyone who wishes to participate at the forums
  - Publicity is never, never, never displayed to members (along with many other cool things)
http://boot-land.net/register

2 Pages V   1 2 >  
Reply to this topic
 Full XP on Multi-Partitioned USB Flash Drive, Tutorial
post Mar 18 2009, 03:54 PM
Post #1
online
Silver Member   ****
Group: Advanced user

  Joined: 28-July 07
Posts: 745
Thank(s): 33


Having made your most bootable USB Flash Drive performing the tutorial described here http://www.boot-land.net/forums/index.php?...ost&p=63162 now you can build your UFD either with a single (active) partition ("Format-it-&-Forget-it" way) or with a multi-partitioned configuration ("Format-it-&-Boot-it" way).

In both cases you will be able to run Full XP from your USB Flash Drive (UFD) with some different features and capabilities.

Performing the "Format-it-&-Forget-it" way then you can run Full XP from your UFD (from the single working partition) even without any external boot loader, or you can also install "grub4dos" as boot manager in order to load all supported applications too (as ISO, IMA, IMG, etc) selecting from its Menu screen at startup which you want to load.


Format-it-&-Forget-it (Full XP in Single-Booting, running without any boot loader except its own "ntldr")



Performing the "Format-it-&-Boot-it" way then you can run Multiple XP, as well as "Full XP in Single-Booting", "Full XP in Dual-Booting", "Full XP in Multi-Booting", indifferently from the 1st, 2nd, 3rd and/or 4th Active Partition of your UFD selecting through "grub4dos" Menu screen at startup which you want to load (included all supported applications as ISO, IMA, IMG, etc, if existing).


Format-it-&-Boot-it (Full XP in Dual Booting, running from the 3rd Active Partition)



Please note that the following way in order to build your "Full XP from your UFD" is the same for any mentioned partitioning configuration and then you can restore either your XP installation or your UFD partition's image-backups to every new UFD and to every partition without ANY modification (except two lines in your "boot.ini" AFTER the restoring on a different numbered partition) and WITHOUT both to pre-install your new UFD or to create a new partition's image-backup (or to modify your XP installation).
You can select in "grub4dos" Menu screen which you want to load at startup (included all supported applications as ISO, IMA, IMG, etc, if existing).


I am literally enthusiastic about the synergy of "grub4dos + dummydisk" that I've experienced: "grub4dos" is GREAT and "dummydisk" is GREAT too and they together are wondeful for me: so absolutely synergistic and so absolutely effective!

Particularly, "dummydisk.sys" has been able to filter ON-THE-FLY the install of all NEW (so never previously recognized) and pre-partitioned USB Flash Drives without the need to PRE-RECOGNIZE them: so it has appeared as the best candidate for this job and most of all for the creation of either your XP installation or your partition's image-backups as well as UNIVERSALLY restorable without modifications (except two lines in your "boot.ini" AFTER the restoring on a different numbered partition) on every new UFD, and on every partition of your UFD you want to boot from (1st, 2nd, 3rd and/or 4th).

This fact means that you will NOT need to re-create (or to modify) your partition's image-backups (or your XP installation) for every new UFD you want to use: so the same backup will be working either for all partitions and/or for all your USB Flash Drives: also for those that you have not yet purchased!

Furthermore, "dummydisk" Filter Driver can be integrate in your customized (with nLite, as an example, just as I did) XP Installation CD-ROM with the same above results, that's with a full POST-COMPATIBILITY with every new UFD, and then ensuring a high-grade of versatility.

"You cannot have your cake and eat it",
then you have to pay the price of a compromise: however in my opinion it will be a (relatively) small price to pay considering the reached advantages.

The price to pay:
1. Only ONE partition will be accessible under Windows when you will attach NOT FOR BOOTING (as if you boot with your UFD all its partitions will be regularly allowed) your UFD under those machines where is NOT already installed a Filter Driver.

The benefits:
1. You can boot your UFD from (reasonably) the most machines with a high-grade of success: as already said now my UFD is able to boot even from a machine that refuses to boot ANYTHING that is not as a Fixed Disk!
2. Simple "newbie-proof" procedure.
3. No special tweaking or physical hacking of your UFD will be needed and no special tool or utility will be used in order to make your UFD bootable, neither "HP USB Disk Storage Format Tool" nor "PeToUSB" utility, nor "Lexar BootIt", nor other ones: this procedure implies both the widest (reasonable) compatibility and the simplest usage.
4. You can easily "translate" your current "Windows XP Professional SP3" running from your current PC into "Full XP from your UFD" with the minimal tweaking possible.
5. You can restore either your "Full XP" installation or your UFD partition's image-backups to every new UFD without ANY modification (except two lines in your "boot.ini" AFTER the restoring on a different numbered partition) and WITHOUT both to pre-install your new UFD or to create a new partition's image-backup (or to modify your XP installation).
6. You can encrypt (with TrueCrypt) your UFD System Drive with no issue.
7. You can restore a RAW image-backup of your UFD encrypted System Partition to every new UFD without any modification (except a quick and easy TrueCrypt "key data/volume header" restoring from its Menu screen).


Full XP (Generic) on Multi-Partitioned USB Flash Drive

Please, note that "Generic" term means that your will set the Standard drivers (that's not the specific ones just of your machine) for some critical devices in order to run your Full XP from your UFD not only just from your machine, but from the most even different machines without issues drivers-related.

If you want to run a Full XP from your UFD then you will need the following (I suggest to create a folder containing all needed files and to copy it in the 1st FAT partition of your UFD):

01. Your Windows PC running from your hard disk (I've used for all my tests "Windows XP Professional SP3", fully updated).

02. Your USB Flash Drive (I've used almost all sizes: 2GB, 4GB, 8GB, 16GB and 32GB ones, depending on both the final purpose and use; of course Full XP runs better if more space is available on your UFD. In my opinion and until now it seems to me that 8GB in size is a good compromise between space and costs. However you can choose almost every size).
Please note that your UFD must be directly attached to a USB port of your PC and NOT through a USB-HUB.

03. The Anton Bassov's "dummydisk.sys" Filter Driver; http://www.codeproject.com/KB/system/sovie...ct_hooking.aspx
(Download source files - 5.22 Kb)

04. The "grub4dos" Boot Manager. http://nufans.net/grub4dos/

05. Any PE environment.

06. 3 INF files ("usb.inf", "usbport.inf" and "usbstor.inf") modified by Dietmar or, now it seems better (thanks to marv) in order to solve some issues digital-signature related, "UsbBootWatcher" Service (I've used this service and it works so fine).
http://www.911cd.net/forums//index.php?showtopic=22473

07. A copy of "NTDETECT.COM" modified by Dietmar (however under "XP SP3" I have not used it and until now no issue is occurred; sure, it higly increases the compatibility under "strange" machines).
http://www.msfn.org/board/index.php?showto...mp;#entry738009

08. To partially follow a Dietmar's tutorial in order to make your Full XP as a "Generic" one.

09. Optionally the Enhanced Write Filter (EWF) environment (strictly needed if you run Full XP from your UFD formatted as NTFS file-system and you do not want to BURN your UFD! However it could be useful to run your Full XP as Write Protect System Volume for many reasons, not last that it will run much faster (from RAM);
http://www.911cd.net/forums//index.php?showtopic=16482
Please, note: in the EWF installation you must care that your "boot.ini" file now has the "partition(2)" modified lines (not "1", as the default one), then you have to modify the needed install commands accordingly.
I've just found this great web-page where EWF installation (and download for 2.0.1024 version) is perfectly described with further add-on as an install folder with batch file that works fine.
http://www.saunalahti.fi/pesonpa/projects/...ws_embedded.php

10. Optionally, TrueCrypt software if you want to encrypt your UFD System Drive.http://www.truecrypt.org/downloads.php

11. Optionally (and NOT needed in order to build your UFD following the complete tutorial), "any" cloning-software (for the record, in all my tests I've used Symantec Ghost): useful if you want to create image-backups of your UFD's working partitions (the RAW mode will be needed only if the partition is encrypted) that then you want to restore to any your new UFD (without any pre-modification of any kind).
Please, note that if you do not want to create image-backups of your UFD partitions then you can however transfer your partition contents (even if encrypted) with cloning-software that allows the drive-to-drive copy (that's without image-backups creation).

About freeware cloning programs that are able to create RAW backups I've already used in the past a great piece of software (in my opinion) named "SelfImage" with excellent results.
http://selfimage.excelcia.org/

However there is also "ODIN (Open Disk Imager in a Nutshell)" of which I read here and that seems very promising (I have not tried it yet).
http://sourceforge.net/projects/odin-win/


How To:

01. You can start from a XP SP3 Clean Install or also from your current Windows PC (running your XP SP3 even with all your settings, drivers, programs and preferences too) and simply to bring it on your UFD.
However, starting (as an example) from your running XP SP3 Clean Install the first thing to do is to install "dummydisk" Filter Driver.

02. From your Windows PC Desktop (of your XP SP3 Clean Install that you want to bring on your UFD) create a folder named "dummy" and copy into it the following files (please, store this folder, it will be useful afterwards):
"dummydisk.sys" renamed "dummy.sys" and "dummy.reg"; then install "dummy.sys" copying it in "\system32\drivers\" folder of your Windows PC and adding "dummy.reg" to the Registry, then restart Windows.

dummy.reg
CODE
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dummy]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,64,00,75,00,6d,00,6d,00,79,00,2e,\
  00,73,00,79,00,73,00,00,00
"DisplayName"="USB Mass Storage Filter Driver"
"Group"="System Reserved"
"Tag"=dword:00000001

Please, note: during his tests of the past Dietmar really suggested to add also another registry key [Enum], but at least in my configuration then a BSOD always occurred... so I've tried to remove the [Enum] key from "dummy.reg", and now it works so fine!
http://www.911cd.net/forums//index.php?sho...mp;#entry123472

03. After restarting Windows (in order to finalize "dummydisk" install) then insert 1 (one) your UFD (any UFD is the same, it's enough that at least only ONE is recognized and installed under "USBSTOR.SYS" filtered by "dummydisk") then let Windows just to install it and then disconnect it (> Safely Remove Hardware).

04. Now I prefer to use the following service against the replacing of the 3 INF files due to its solved digital-signature annoying issue then, on your Desktop create a folder named "UsbBootWatcher" (or as you want) and copy into it "UsbBootWatcher.conf" and "UsbBootWatcher.exe"
http://www.911cd.net/forums//index.php?sho...mp;#entry152574
Edit your "UsbBootWatcher.conf" as following;

(thanks to cdob)
http://www.911cd.net/forums//index.php?sho...mp;#entry152936

"UsbBootWatcher.conf"
CODE
[usbehci]
Start@REG_DWORD=0
Group@REG_SZ="Boot Bus Extender"
[usbohci]
Start@REG_DWORD=0
Group@REG_SZ="Boot Bus Extender"
[usbuhci]
Start@REG_DWORD=0
Group@REG_SZ="Boot Bus Extender"
[usbhub]
Start@REG_DWORD=0
Group@REG_SZ="System Bus Extender"
[usbstor]
Start@REG_DWORD=0
Group@REG_SZ="System Bus Extender"
[processor]
Start@REG_DWORD=3
[intelppm]
Start@REG_DWORD=3
[AmdK6]
Start@REG_DWORD=3
[AmdK7]
Start@REG_DWORD=3
[AmdK8]
Start@REG_DWORD=3
[agp440]
Start@REG_DWORD=3

5. Always on your desktop create a ".reg" file with the following content and rename it as "Embed.reg".

"Embed.reg"
CODE
Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\Embed\MountedDevices]

[HKEY_LOCAL_MACHINE\Embed\MountedDevices]

[-HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase]

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase]

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*aui0200]
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0000]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0100]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0200]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0303]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0a03]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
"Service"="pci"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0b00]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0c01]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0c02]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0c04]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\*pnp0f0e]
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\acpi#processor]
"ClassGUID"="{50127DC3-0F36-415e-A6CC-4CB3BE910B65}"
"Service"="Processor"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0600]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0601]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
"Service"="isapnp"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0604]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
"Service"="pci"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0c0320]
"Service"="usbehci"
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1033&dev_00e0&rev_01]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1033&dev_00e0&rev_02]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_24cd]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\PS2_KEYBOARD]
"ClassGUID"="{4D36E96B-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\PS2_MOUSE]
"ClassGUID"="{4D36E96F-E325-11CE-BFC1-08002BE10318}"
"Service"="i8042prt"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\root#swenum]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
"Service"="swenum"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\usb#class_08]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="USBSTOR"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\usb#root_hub]
"Service"="usbhub"
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\usb#root_hub20]
"Service"="usbhub"
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\usbstor#disksony____msc-u01n________]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Control\CriticalDeviceDatabase\usbstor#disksony____msc-u01_________]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Services]

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Services\usbehci]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,75,00,73,00,62,00,65,00,68,00,63,\
00,69,00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="Microsoft USB 2.0 Enhanced Host Controller Miniport Driver"
"Group"="Boot Bus Extender"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Services\usbhub]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"DisplayName"="Microsoft USB Standard Hub Driver"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,75,00,73,00,62,00,68,00,75,00,62,\
00,2e,00,73,00,79,00,73,00,00,00
"Group"="System Bus Extender"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Services\USBSTOR]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,55,00,53,00,42,00,53,00,54,00,4f,\
00,52,00,2e,00,53,00,59,00,53,00,00,00
"DisplayName"="USB Mass Storage Driver"
"Group"="System Bus Extender"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Services\usbohci]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,75,00,73,00,62,00,6f,00,68,00,63,\
00,69,00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="Microsoft USB Open Host Controller Miniport Driver"
"Group"="Boot Bus Extender"

[HKEY_LOCAL_MACHINE\Embed\ControlSet001\Services\usbuhci]
"Type"=dword:00000001
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"DisplayName"="Microsoft USB Universal Host Controller Miniport Driver"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,75,00,73,00,62,00,75,00,68,00,63,\
00,69,00,2e,00,73,00,79,00,73,00,00,00
"Group"="Boot Bus Extender"

05. Shutdown Windows.

06. Now boot from your PC running your PE environment.

07. Reach your PE Desktop and browse to your Hard Disk (C:) Drive: I will assume that you currently have Windows installed on your (C:) Drive.

08. Under your PE environment set all files and folders as unhidden (also SuperHidden ones, that's your Protected Operating System Files) and copy all (C:) drive content (that's "Documents and Settings", "Program Files" and "WINDOWS" folders, and all other system files (that's "AUTOEXEC.BAT", "boot.ini", "CONFIG.SYS", "IO.SYS", "MSDOS.SYS", "NTDETECT.COM" and "ntldr" - do NOT copy "Recycled" and "System Volume Information" folders) in a folder on your PC named "USB_XP_MOD" (or as you want): it will be your working folder.
Make a copy of just created "USB_XP_MOD" folder in the same location and rename it as "USB_XP_BAK" (or as you want): it will be useful as possible future reference.

09. Now reboot your machine, but this time from your Windows PC (not from your PE environment, that will not be more useful) and reach your Windows PC Desktop.
Now browse to "boot.ini" existing in your "USB_XP_MOD" folder and edit its two lines as following:

from
CODE
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

to
CODE
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

and from
CODE
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

to
CODE
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

10. Replace existing "NTDETECT.COM" in your "USB_XP_MOD" folder with Dietmar's modified one (not strictly needed, but it's safer so).

11. Launch your Registry Editor ("regedit.exe") and highlight the "HKEY_LOCAL_MACHINE" key; then reach the "File" flag and click on "Load Hive...", browse to your "SYSTEM" hive existing in your "USB_XP_MOD\WINDOWS\system32\config\" folder and at prompt name it as "Embed".
Delete in the same folder "SYSTEM.LOG" (it will be automatically re-create) and "system.sav" files.
After loading "SYSTEM" hive then highlight in your Registry Editor the key named "Embed", reach the "File" flag again and click on "Import...", then browse to "Embed.reg" that you have on your desktop. Click OK the times are required, then select again the "HKEY_LOCAL_MACHINE" key, reach the "File" flag again and then click on "Unload Hive...".
Now you are just modified your "SYSTEM" hive in order to boot your Windows XP SP3 from your UFD!
In your "USB_XP_MOD\WINDOWS\system32\config\" folder create a further copy of the just modified (and just unloaded) "SYSTEM" file (right-click > Copy Here): the result will be a file named "Copy of STSTEM", rename it as "system.sav" (thanks to NK!).

12. Now remember that you have already installed "dummydisk" Filter Driver on your current Windows PC, so insert any UFD (at least of 4GB in size, better results running XP with a 8GB one, or even more) and then launch Disk Management (Start > Run > diskmgmt.msc) and delete existing partition in your UFD itself; then create a 1st Primary FAT partition on your UFD of 2047MB in size (or as you want, > max 2047MB - clusters 32Kb, by design).

13. Then create a 2nd Primary FAT32 or NTFS partition of 5GB in size (or of the size that is useful for you).
You can set the size almost as you want: I've just tested a system partition of less than 2GB (1750MB) and a complete XP SP3 fully updated, with all drivers installed and even with .NET Frameworks 3.5 and DirectX included (1,5GB), runs "almost" fine!
I've preferred the FAT32 file-system: however, keep in mind that if you want to run your Full XP from your UFD formatted as NTFS file-system, then the Enhanced Write Filter environment will be STRICTLY needed in order to not BURN (!) your UFD (really it never occurred for me... but at least until now I never used NTFS file-system for my UFD partitions!).
Then mark the 2nd partition as Active.

14. Install "grub4dos" latest version on the MBR of your UFD (using "grubinst" is easier) as following:

CODE
A. Download latest release of "grub4dos" from here   http://nufans.net/grub4dos/
B. Download latest release of "grubinst-bin-w32" from here   http://nufans.net/grub4dos/grubutil/
C. Unzip both folders on your desktop and merge all their contained files in a single folder named as you want ("COPYING" file will be overwrtitten).
D. Copy that folder in your system drive root, assuming (C:\).
E. Insert your UFD, launch Disk Management (Start > Run > diskmgmt.msc) and keep note of which drive number Windows has assigned to your UFD, then close Disk Management.
F. Open the above created folder in your (C:\) drive and run "grubinst_gui.exe", then select "Device Name" > Disk.
G. Now choose your UFD - something like "(hd4) [7899M]" - in "Disk" flag (be VERY sure that it is just your UFD) and push the "Install" button, then push the Enter key on your keyboard after reading in the related Command Prompt screen that "grub4dos" has been successfully installed.

"menu.lst" example
CODE
color black/cyan yellow/cyan
timeout 30
default 0

title Active@ Partition Recovery
map --mem /boot/apr.ima (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title Linux Parted Magic
kernel /boot/pmagic/bzImage noapic root=/dev/ram0 init=/linuxrc keymap=us
liveusb vga=791 sleep=0 quiet xvesa tmpfs_size=350M ramdisk_size=25000 directory=/boot
initrd /boot/pmagic/initrd

title Norton Partition Magic
map --mem /boot/npm.ima (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title Paragon Total Defrag
find --set-root /boot/ptd.iso
map --mem /boot/ptd.iso (hd32)
map --hook
chainloader (hd32)
boot

title RecoverSoft Media Tools Pro
map --mem /boot/mtl.img (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title Symantec Ghost
map --mem /boot/gho.ima (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)

title TeraByte BootIt NG
map (hd0,0)/boot/bng.iso (hd32)
map --hook
chainloader (hd32)

title VistaPE
map (hd0,0)/boot/vpe.iso (hd32)
map --hook
chainloader (hd32)

title Windows XP Professional
map (hd0,0) (hd0,1)
map (hd0,1) (hd0,0)
rootnoverify (hd0,1)
chainloader (hd0,1)/ntldr

To add/replace in "menu.lst" example for Full XP in Dual-Booting (very simplified, thanks to jaclaz and tinybit)
CODE
title Windows XP Professional (from the 2nd partition)
unhide (hd0,1)
hide (hd0,2)
root (hd0,1)
chainloader /ntldr

title Windows XP Professional (from the 3rd partition)
unhide (hd0,2)
hide (hd0,1)
root (hd0,2)
chainloader /ntldr

15. Copy "grldr" file, your customized "menu.lst" file, the "dummy" folder above created and the "UsbBootWatcher" folder just created in the root of the 1st Primary FAT partition.

16. Copy the whole "USB_XP_MOD" folder content (just modified) into your 2nd Active Partition of your UFD as following:
at first copy all booting-related files, that's first "NTDETECT.COM", then "boot.ini", then "ntldr", then all other files and folders (do not copy "Recycled" and "System Volume Information" folders if existing).

17. Now shutdown Windows, disconnect all HDs connected within your machine and boot for the first time from your UFD just prepared.

18. Reaching for the first time your UFD Desktop then wait for "Windows has finished installing new devices..." UNTIL it prompts for "Do you want to restart your computer now?" and answer "NO".

19. Now browse to 1st FAT partition and open the "UsbBootWatcher\x86\" subfolder, then copy the two files that it contains in your "C:\WINDOWS\system32\" folder that is in the 2nd partition of your UFD.

After copying the two files then open a Command Prompt from "system32" folder and install "UsbBootWatcher" Service entering the following line

CODE
usbbootwatcher.exe /install

then verify that "usbbootwatcher.exe" is in Task Manager Processes and restart Windows.

20. Reaching for the second time your UFD Desktop then go in Device Manager and "update" all the following drivers against the already existing and related "Standard" ones (that's the "Generic" ones)

CODE
A.) IDE ATA/ATAPI Controllers \ Primary IDE Channel and Secondary IDE Channel > Standard (All)

B.) Universal Serial Bus Controllers > Standard (All)

C.) Computer > Advanced Configuration and Power Interface (ACPI) PC > Restart Windows Now > YES

After next reboot: Restart Windows Now (again) > YES

proceeding as following: in every respective device Properties click on the "Driver" flag and push the "Update Driver..." button > Then > "Install from a list or specific location" > Next > "Don't search. I will choose the driver to install" > Next > Choose "Standard Dual Channel PCI IDE Controller" (it's just an example for "IDE ATA/ATAPI Controllers": really the important thing is to always choose the "Standard" choice for every already cited drivers).
Do the above for all other already cited drivers (always choosing the "Standard" option).

21. After having completed the standard-drivers-procedure following the EXACT order, Windows will ask to you to "Restart Now" your machine (due to ACPI drivers just changed) and after the restarting Windows will ask to you again to "Restart Now" your machine: you will answer always "YES" (then 2 times).
After the two restarting and after reaching your UFD Desktop again then shutdown Windows, connect all your existing HDs within your PC and boot again from your UFD.

22. Done!
Reaching for the third time your UFD Desktop then it means that all is gone right and that finally you have your "Full (Generic) XP" on your UFD, capable to boot and to run on the most machines!


Encryption Notes

You can smoothly encrypt with TrueCrypt your UFD System Drive - that's just the (C:) Drive where your Windows currently resides - and at the same time to preserve your grub4dos Menu screen at booting (that's you will can choose at every booting if to load "Windows XP SP3, or your "VistaPE", or your "Ghost", etc, if existing).
One of my UFDs contains just a Full XP Encrypted and I've modified my "menu.lst" in order to not choose anything at booting, so that grub4dos automatically load it without any user's input.
Furthermore you can create a partition's image-backup (in default mode; or in RAW mode if the partition is encrypted) of your UFD partitions and then to restore it on every new UFD with both no pre-modification and no issue!


TrueCrypt System Drive Encryption

If you want to encrypt with TrueCrypt your UFD System Drive (that's the partition where your XP currently resides) you have to start and to complete the whole encryption process from your UFD, so copy at first "TrueCrypt Setup 6.1a.exe" from your Windows PC to the root of the 1st FAT Partition of your UFD.
Then boot from your "Full XP" and install TrueCrypt.
After TrueCrypt installation completion open a Command Prompt from "C:\Program Files\TrueCrypt" folder and enter the following line
(thanks to mr_)

CODE
TrueCrypt Format /noisocheck

it will encrypt your System Drive partition with no "TrueCrypt Rescue Disk.iso" verification.
Wait for encryption process completion then reboot your machine.
In this phase you can not see any grub4dos Menu screen at booting because TrueCrypt will have overwritten the existing one with its own one, but really it will be not an issue.
Repeat a reboot in order to further test that all is gone right and that your encrypted Full XP boots with neither password issue nor any other one.
Now rename the "TrueCrypt Recue Disk.iso" just created by process in "tc.iso" and copy it in your "boot" folder existing in your 1st FAT partition of your UFD.
Then you have to re-install "grub4dos" in the MBR of your UFD.
Now you have to add (really to replace) in your "menu.lst" the following lines

"menu.lst" example

CODE
title TrueCrypt-ed XP
map (hd0,0)/boot/tc.iso (hd32)
map --hook
chainloader (hd32)

Please, note that you cannot place the "tc.iso" in your just encrypted drive (because it cannot be read from disk BEFORE the drive has been un-encrypted!) and then you MUST copy it in the 1st FAT partition or in any other one (not encrypted) if existing.

Now you can reboot your machine and at "grub4dos" Menu screen at startup you can choose "TrueCrypt-ed XP", or any supported application (as ISO, IMA, IMG, etc) you have placed in your "boot" folder (and in your "menu.lst").

Also, you can create a partition's image-backup of your encrypted System Drive partition (in RAW mode, because really does not exist a different way to backup an encrypted partition) and then to restore it on any new UFD performing one of the two following options:

1. Create with Disk Management (Start > Run > diskmgmt.msc) on your new UFD the same disk's configuration of your just backupped UFD configuration: that's a 1st FAT partition, and a 2nd FAT32 Partition with EXACTLY the same size of the original (just encrypted as well) partition.

2. Or, create the 1st FAT Partition of 2047MB in size and let ALL the remaining space of your UFD as Unallocated: your cloning-software would be to restore the RAW backup of your encrypted partition creating at the same time a "new" partition of the same size of the restored partition itself letting the remaining space as Unallocated.
Then if you want you will can create/format a 3rd partition as you want (and most of all, IF you really need that).

Please, note that when you will boot from your UFD for the first time a restored backup of your encrypted partition and you will be on your TrueCrypt's first prompt for password from your new UFD just "restored" you will must use the "[F8] Repair Options" feature of TrueCrypt and will must restore the "key data/volume header" choosing the option "#3", then when TrueCrypt will ask you: "Modify drive 0?", then you will answer "y".
Then you will have to press Enter, then Enter again and then to enter your password: so it will boot!
If you do not do so, then TrueCrypt prompt will always say to you that your password is incorrect and you will cannot boot at all.

Please, note that:
when you have just restored an encrypted partition on a new UFD proceding as above described then you have to do as following in order to boot your UFD - with System Drive Encrypted and with EWF enabled - with or without your Hard Disk(s) connected:

1. Restore both the 1st and the 2nd partitions as above described and installing "grub4dos" in MBR of your new UFD.

2. Copy "MountedDevices_Remove.reg" in your UFD 1st FAT partition.


"MountedDevices_Remove.reg"
CODE
Windows Registry Editor Version 5.00

[-HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]

3. Boot from your just restored device WITH your Hard Disk(s) connected within your PC.

4. At "grub4dos" Menu screen choose "TrueCrypt-ed XP": it will load the TrueCrypt ISO image.

5. At TrueCrypt Menu screen choose "[F8] Repair Options" and then the option "#3" (> restore "key data/volume header") then when TrueCrypt will ask you: "Modify drive 0?", you will answer "y".

6. Then wait for both your UFD Desktop AND Windows installing New Devices (it always will occur the first time you will boot a new UFD just restored): please, note that the whole process will complete between about 8 to 16 minutes (depending on some variables).
At Windows prompt for "Reboot Now?" you answer "NO".

7. Please, note: at the first reboot after partition restoring then the EWF environment will result NOT ENABLED.

8. Add in the Registry "MountedDevices_Remove.reg" that you have copied. Please, note that your Floppy Drive (if existing) could have in some circumstances the (B:) letter assigned.

9. Now shutdown Windows, disconnect all Hard Disk(s) within your PC and boot from your UFD again.

10. Done!
Please, note that now your "Full XP (Generic)" will boot from (reasonably) the most machines out there WITH or WITHOUT Hard Disk(s) connected within your PC, the System Drive have the (C:) letter assigned (however it already had it so!), the Floppy Disk Drive (if existing) will have the (A:) letter assigned and the EWF environment will result ENABLED!


After you restore your partition's image-backups of your Encrypted and EWF-ed Drive then if you do not do as above described then you could receive some kind of Stop Error Screen (BSOD) then is better if you do so.

Hint: deleting "MountedDevices" key in the Registry with "MountedDevices_Remove.reg" before to create an image backup of your system drive partition is a good practice.

Good luck!


Full XP, Encrypted, Enhanced Write Filter (EWF) enabled, running from the 2nd Active Partition



--------------------


3 user(s) said "Thank you!" to online for this fantastic post:
Lancelot, Nuno Brito, Smith
+Quote Post
post Mar 18 2009, 05:34 PM
Post #2
mr_
Frequent Member   ***
Group: Members

  Joined: 19-June 08
Posts: 357
Thank(s): 9


Germany


Very nice guide.

1) Unfortunately you haven't said any word about bootablity of real USB-HDD's. Did you ever test it with one? I think it's the same with the only difference that you do not need a filter driver?

2) What about maximum compatiblity with most possible simplicity? http://www.boot-land.net/forums/index.php?...ost&p=52981 mentions lots of techniques to further improve bootablity.

3)
QUOTE
Then mark the just created 2nd FAT32 partition as Active;

Why? Shouldn't be the first FAT16 partition active to improve compatibility?
Or does the BIOS never care about active partition?

4) I still don't get that the filesystem FAT, FAT32 or NTFS matters. Normally the job of the BIOS is to read MBR into memory and jump into it. PLoP Bootmanager author explained me that he does the same and the filesystem really doesn't matter. Did you reproduce booting once with FAT16, but now with FAT32?
+Quote Post
post Mar 19 2009, 02:40 AM
Post #3
TheHive
Platinum Member   ******
Group: .script developer

  Joined: 14-July 06
Posts: 3,052
Thank(s): 72


Where can one get this filter driver you write about.


--------------------
+Quote Post
post Mar 19 2009, 07:46 AM
Post #4
jaclaz
Finder   ******
Group: Advanced user

  Joined: 14-July 06
Posts: 6,305
Thank(s): 452


Italy


QUOTE (TheHive @ Mar 19 2009, 04:40 AM) *
Where can one get this filter driver you write about.


Searching? unsure.gif

http://www.codeproject.com/KB/system/sovie...ct_hooking.aspx?
http://www.boot-land.net/forums/index.php?showtopic=4900

QUOTE (mr_ @ Mar 18 2009, 07:34 PM) *
Very nice guide.

1) Unfortunately you haven't said any word about bootablity of real USB-HDD's. Did you ever test it with one? I think it's the same with the only difference that you do not need a filter driver?


Since the topic title is:
QUOTE
USB-Stick Highest Bootability (Tutorial), Full XP on 2nd Active Partition


it seems to me only too normal...happy22.gif

jaclaz


--------------------

Light Blue Ribbon Campaign for Freedom of Skin
+Quote Post
post Mar 19 2009, 01:42 PM
Post #5
online
Silver Member   ****
Group: Advanced user

  Joined: 28-July 07
Posts: 745
Thank(s): 33


QUOTE (TheHive @ Mar 19 2009, 03:40 AM) *
Where can one get this filter driver you write about.

If you read (even with more attention?) you will find what you're looking for. wink.gif

QUOTE (online @ Mar 18 2009, 04:54 PM) *
3. The Anton Bassov's "dummydisk.sys" Filter Driver; http://www.codeproject.com/KB/system/sovie...ct_hooking.aspx (> Download source files - 5.22 Kb)


Btw: the download requires your registration, but I've noticed that really then it proceeds however with any e-mail address.


--------------------
+Quote Post
post Mar 19 2009, 04:06 PM
Post #6
online
Silver Member   ****
Group: Advanced user

  Joined: 28-July 07
Posts: 745
Thank(s): 33


QUOTE (mr_ @ Mar 18 2009, 06:34 PM) *
Very nice guide.

I'm glad you like it. smile.gif
QUOTE
1) Unfortunately you haven't said any word about bootablity of real USB-HDD's. Did you ever test it with one? I think it's the same with the only difference that you do not need a filter driver?

I own more than one USB-HDD, but I'm not really interested about that other topic; so I've not tried with any ones (just as the topic indicates, as already kindly said by jaclaz).
Nevertheless, if you're interested about "your" topic why do you not do some trials and then tell us about your results even in a specific thread? smile.gif

QUOTE
2) What about maximum compatiblity with most possible simplicity? http://www.boot-land.net/forums/index.php?...ost&p=52981 mentions lots of techniques to further improve bootablity.

mr_, please note that the topic that you are linked has been already mentioned by myself in my first post
QUOTE (online @ Mar 18 2009, 04:54 PM) *
Furthermore if you read here
http://www.boot-land.net/forums/index.php?showtopic=6546#

and it does not seem to me that there are further procedures - at least "with most possible simplicity" as you say - in order to do what you kindly "suggest".
Really what is described in this topic is just what you are talking about, don't you? smile.gif
QUOTE (online @ Mar 18 2009, 04:54 PM) *
Reducing too many possible variables in a reasonable number-and/or-circumstances it seems that there are at least two "easily" practicable conditions that can ensure to your USB-Removable-Device a statistically high-grade of compatibility at USB-booting for the highest percentage of machines (that's of BIOSes), more or less modern:
1. FAT(16) file-system (as the first partition);
2. Fixed Disk (as USB-Stick behaving like USB-HDD).


Of course if you know or if you have experienced better and/or equally real "simple" ways in order to further improve - compared just with the two ways in topic - your USB-Stick booting you can do a nice thing reporting your applicable findings here. smile.gif
QUOTE (online @ Mar 18 2009, 04:54 PM) *
Of course I'm very interested in unknown and/or alternative ways equally and/or so widely simple-&-effective, thus if somebody knows or has been experienced similar high-bootability results following different and/or better ways please kindly report here in order to possibly redefine the State-of-the-Art about the USB-Removable-Drive Bootability.
Thank you!

Btw: I begin to have the impression that this topic not to be read with a minimum amount of attention if I do repeat many of those things already said! rolleyes.gif laugh.gif

QUOTE
3)Why?

Simple: because it works so!
This is a strong evidence for me.
Really in this topic I was talking (EDIT: I've split the two topics in two different threads - just as in my signature - then some replies could seem unrelated) about two different arguments: improve your USB-Stick booting and "Full XP on Multi-Partitioned USB-Stick", but the two arguments are not necessarily co-related.
In other words: it was never told that to improve your USB-Stick booting you should run Windows from your USB-Stick.
Following this tutorial you can improve your USB-Stick booting for every need you want to boot.
QUOTE (online @ Mar 18 2009, 04:54 PM) *
So - about the USB booting - the simple partitioning of your UFD seems to succeed EXACTLY as the flipping of removable-bit does and then your UFD should boot (reasonably) from the most machines!

So, as already said, the results achieved following the "Format-it-&-Forget-it" way could be as an universal solution (with no price to pay) not just a workaround, because the partitioning on your USB-Stick is REAL and the most BIOSes are able to read it very well!
Furthermore in your quoted question you are referring to the way that uses "grub4dos" as Boot Loader, so the Active partition does not seem more a "restricted" matter beacuse however your USB-Stick will boot (with or without Windows).
At least I had not noticed any difference.
QUOTE
Shouldn't be the first FAT16 partition active to improve compatibility?
Or does the BIOS never care about active partition?

Really, and as already said, it seems to me that your second question is more likely, but it should be confirmed by many more tests on many more different machines (BIOSes) to achieve at least a minimum of reliability.
But, let me say the following - please don't take my question as a rude reply because it is not:
first you state that you do not BELIEVE that FAT file-system is matter in order to increase the hardware-compatibility and then you ask if Active condition is matter?
Really seems to me that it's Windows that "prefers" (really, requires) the booting partition as Active, not the BIOS (bootability)! smile.gif
Furthermore, here we are not talking about an EXACT science (unfortunely), here we are talking about EVIDENCES about USB-booting and about so many reports in which so many dudes describe just those evidences.
So if you are searching for a "mathematical model of USB-Stick booting" I'm afraid that you will still not find here; also because, as already mentioned above
QUOTE (online @ Mar 18 2009, 04:54 PM) *
The most relevant argument explaining why so many issues occur at the booting with USB Removable Devices seems essentially imputable to the lack of an industry-standard USB-oriented common protocol of BIOS manufacturers.

and we do not know quite what and how the various BIOS manufacturers "put" in their various BIOS semiconductors (CMOS) and then we do not yet have demonstrate and/or "certified" references for all different BIOSes.
Furthermore, paraphrasing jaclaz: maybe is there something of "magic" in the booting? smile.gif
Frankly, in this topic I would like to hear about successes or even about failures following at least one of the two described ways, and maybe then we could say about hypothesis.
QUOTE
4) I still don't get that the filesystem FAT, FAT32 or NTFS matters. Normally the job of the BIOS is to read MBR into memory and jump into it. PLoP Bootmanager author explained me that he does the same and the filesystem really doesn't matter. Did you reproduce booting once with FAT16, but now with FAT32?

Following "Format-it-&-Forget-it" way you can improve your USB-Stick booting not only to boot "grub4dos" from 1st partition in FAT16, in FAT32 or in NTFS file-system, but even running "Full XP" on the 1st Active Partition of your USB-Stick without ANY boot loader (except just XP's "ntldr").
Also you can reach your "Full XP" running from FAT32 or from NTFS file-system on the 2nd, 3rd and/or 4th Active Partition of your USB-Stick. smile.gif
http://www.911cd.net/forums//index.php?sho...st&p=154653

Really, as I already said, I'm thinking that FAT(16) file-system could even not be matter, but on the other hands we can not ignore the great amount of reports about it.
So, if you want instantly improve your USB-Stick booting then please follow the "Format-it-&-Forget-it" way: it will improve your USB-Stick booting with NO price to pay; if you want to get even a better bootability then please follow the "Format-it-&-Boot-it" way. smile.gif








--------------------
+Quote Post
post Mar 21 2009, 08:44 AM
Post #7
online
Silver Member   ****
Group: Advanced user

  Joined: 28-July 07
Posts: 745
Thank(s): 33


EDIT:
I've edited this post because I had tried to partition a new USB-Stick replacing its MBR with a "MBR template" (or simply restoring an empty disk image) without to install "dummydisk.sys" Filter Driver (and without to format it with XP's Disk Management) and it seemed a good thing because then the resulting partitioning appeared as effective, but now I know that really it does NOT work about the booting.

So, nothing has changed in this tutorial and everything has remained as before. wink.gif
Thanks!


--------------------
+Quote Post
post Mar 21 2009, 10:01 AM
Post #8
jaclaz
Finder   ******
Group: Advanced user

  Joined: 14-July 06
Posts: 6,305
Thank(s): 452


Italy


Please note that this will make all your Sticks have the same Disk Signature, something that may (or may not ) be an advantage of some kind.

There are other ways.

Most notably you can use a Qemu virtual machine connecting the stick as "PhysicalDrive" then partition/format it from within the VM.
Since you only use FAT32 all you need is a DOS 7.x/8.0 floppy image with FDISK and FORMAT (or better with Ranish Partition Manager) to boot the VM from.

Or use MBRbatch and dsfo/dsfi:
http://www.boot-land.net/forums/?showtopic=3191
http://www.boot-land.net/forums/index.php?showtopic=5000
to make an image of the stick, partitin and format the image, then image it back to the stick.

This way you are not "linked" to "MBR templates".

To change Disk signature you can use MBRFIX allright, optionally with my pseudo-gui for it.

jaclaz




--------------------

Light Blue Ribbon Campaign for Freedom of Skin
+Quote Post
post Mar 21 2009, 11:08 AM
Post #9
online
Silver Member   ****
Group: Advanced user

  Joined: 28-July 07
Posts: 745
Thank(s): 33


@jaclaz
As always, VERY interesting: thank you for your extraordinary disposability and for your encyclopedic knowledge! cool.gif

Really following this tutorial then any file-system (FAT16, FAT32 or NTFS) can be used for your USB-Stick booting, but when running "Full XP SP3" - and not wanting to use the EWF environment in that phase of my trials - I've preferred the FAT32 file-system for the known reasons under NTFS of USB-Stick's burning.



EDIT:
please, read above.


--------------------
+Quote Post
post Mar 26 2009, 08:30 PM
Post #10
DSpider
Newbie   *
Group: Members

  Joined: 6-March 09
Posts: 22
Thank(s): 2


Romania


I have a silly question. smile.gif Why do you need a PE enivornment to copy the files ?

Why not just go to My Computer -> Tools -> Folder Options -> View -> "Show hidden files and folders" AND ALSO uncheck "Hide protected opertating system files (Recommended)" and just select all (Ctrl+A) and copy-paste everything from drive C: ?

Why use a PE environment ?


PS: You can also access "Folder Options" from the Control Panel (if you have Classic View switched on).
+Quote Post

2 Pages V   1 2 >
Reply to this topic
2 User(s) are reading this topic ()




Collapse

  Topic Replies Topic Starter Views Last Action
No new Topic has attachmentsXP styles in PE
173 MedEvil 10,480 Today, 08:38 AM
Last post by: JFX
No New Posts XPE Stardock for VistaPE and Win7PE
WindowBlinds 6.30 & ObjectDock 1.9.0536
8 ludovici 1,377 1st October 2009 - 01:19 PM
Last post by: ludovici
No New Posts Drivers
2 ctv99 484 26th September 2009 - 12:08 AM
Last post by: esgaroth
No New Posts USB devices doesn�t work
USB devices doesn�t work
2 tintinger 331 24th September 2009 - 08:41 AM
Last post by: JRColbert
No new Topic has attachmentsXP installing on Notebook without CD-ROM
14 mbzadegan 1,927 20th September 2009 - 12:04 AM
Last post by: ilko


Display Mode: Standard · Switch to: Linear+ · Switch to: Outline

Track this topic · Email this topic · Print this topic · Subscribe to this forum