• Tiny PXE Server post #285
• http://reboot.pro/topic/20596-windows-7-aoe-what-does-ccboot-do/
• http://reboot.pro/topic/20598-clone-existing-windows-7-to-iscsi/

#!ipxe
dhcp net0
set keep-san 1
sanboot aoe:e0.0
boot

Maybe this can help some members:

http://www.easeus.com/system-go-back

Peter

Ref:

LINUX-VHD for UBUNTU, ARCH, Fedora, OpenSuse, Mageia. (Chinese)
[教程] LINUX-VHD 系统的制作方法 UBUNTU, ARCH, Fedora, OpenSuse, Mageia 五种
http://bbs.wuyou.net/forum.php?mod=v...ead&tid=336079 [MANGLED URL, IRRETRIEVABLE!]

\[WUBI\] KLOOP: boot UBUNTU from img and vhd
http://newscentral.exsees.com/item/a46992226f192c4b3769c62900455d3d-091e70613bc596ffb78691a65750d9f8

Hi, Everyone.

KLOOP is a new method to boot UBUNTU (Fedora, ARCH, OpenSuse, Mageia) from fixed img and fixed vhd.

It is based on the command 'kpartx' and using loop device as /, so I named it KLOOP (Kpartx+LOOP).
 
If you want to try it, click on the following :
http://pan.baidu.com/s/1bnnjBXX

download and decompress the file 'mydracut-English.zip', and read the file 'mydracut/ubuntu-kloop/readme-KLOOP-UBUNTU.txt' or 'mydracut/fedora-kloop/readme-KLOOP-FEDORA.txt'.[/font]

As far as I understood right now, Win10 can be installed over a running OS replacing win7 or win8 (maybe depending on starter, ... enterprise).

Are there any informations, how to get the win10cd contents, and install without to "destroy" the running win7/8 system?

Peter

BTW: A patch to running XP to let upgrade to win10 would be an valuable hack!

I thought I would point out one for you guys, I ordered 4 of them and they all appear functional (even with UASP support for SSDs). They are based on the ASM1053 chipset.

International Purchase

If you want to create it bootable, I suggest an active fat-32 partition at the beginning of the drive, smaller then 100GB (some computers can't handle booting from a partition larger then 100-someGB). Really a 20GB partition is tons of space. fat-32 to conform to UEFI specs.

When I plug in my isoStick, it simply shows as a microSD card. I've reinstalled the firmware, tried different SD cards, tried different isos. No clue why this is happening. Any help would be greatly appreciated.

yes it does...

removing it seems impossible even for Malwarebytes Anti-Malware or latest panda [that is listed as one of the best antivirus.. ] or the other new recommended HitmanPro_x64 ..

i have the pricegotlower tag on all new tab...when i launch chrome it complains about developer mode of extentions...as you can see some extention listed in ram are not shown in others tab for settings...

plus there is some auto-loading of others extentions...

http://imgur.com/a/ciIna

sorry if images are very large ..but it is cool to have 3 screens to see all the tabs at once

so google when you will read that : you should better not try to kick kickass-torrent from the web but more the virus and bugs in your browser [ that is no longer the fast one...]

by now i use a lot more firefox x64 that is very fast despite few bugs like with mega website and extention..

Tried creating a multiboot using windows XP, Se7en, Eight, and 10 TP.

Started xboot dragged OS's on and identified each as _Add using Grub4dos ISO image Emulation.

Clicked Create USB, selected USB Drive and Grub4dos Bootloader.

Started to extract OS's, when I got error...

ERROR REPORT ( 07/27/2015 15:26:11 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.1.7601 Service Pack 1
.NET Framework version    :4.0.30319.34209
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.KB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

So I posted a couple days ago about the write protect enclosure, and now I have some hard figures on it.

Where to purchase

I purchased mine from miniinthebox. There appear to be some other suppliers, but miniiinthebox works (just make sure to opt out of the spam they send you, I had to log back in later and find the checkbox buried in account settings).

Pictures

So for my initial purchase, I bought 4 of them (at ~$20 per enclosure, it isn't a bad purchase). Gave one to a fellow techie, the other three are present in this review. I have them used with three different drives:

• 
  
• Samsung Evo 240 1TB msata drive (in a 2.5" adapter)
• 
  
• WD Blue 1TB mechanical drive
• 
  
• Toshiba 750GB mechanical drive
• 
  

Both mechanical drives are 5400RPM. I tried a 7200RPM drive, but there wasn't quite enough juice to run it (would probably work with a Y cable).

Here is the three drives, along with a zalman zm-ve400 enclosure for comparison

Cat for scale

End of the drive, has a OTB button (which will never be used), and also an additional DC Jack for extra power if needed. The LED is also quite bright when in use.

Enclosure when apart. The two sides slide onto the enclosure, and each is held in with two *very* tiny screws (4 total). requires a PH00 screwdriver to properly screw in (none provided). Four additional screws hold the drive in the enclosure.

Picture of the chipset being used. the ASM1053 identification is barely visible, couldn't get the camera to zoom close enough for that detail. The same chipset is used in all four drives received.

SSD being used for testing:

Does it work?

Short answer, yes. The write protect switch does indeed work as expected. It is worth noting that flipping the switch while in use doesn't do anything, so if you want to protect a drive, flip the switch *before* plugging in.

Performance

Performance is quite decent, especially with UASP support for SSDs.

UASP?

UASP is a feature built into new chipsets (new being anything with a 3rd generation intel or later). Note that UASP *only* works if the device, the USB chipset, *and* the software support it (windows 8 or linux only for the most part). It allows USB to emulate a SCSI device, and dramatically increase the IOPS (input output per second) of the device. For a mechanical drive, this isn't really anything interesting. For an SSD, this does make a difference.

Here we see a zalman drive alongside two of the SSK enclosures. The zalman drive (which does not support UASP) only shows up as a "USB Mass Storage Device". The two SSK enclosures show up as "USB Attached SCSI"

Benchmarks

First, for the baseline, we will test the internal 250GB SSD (inside the computer). That gets around 500MBps read/write, which is about what we expect

Now we test the SSD in the enclosure. We are getting around 250MBPS both read and write, which is not too shabby and about what we can hope for out of USB 3.0

Now it's time to show how UASP really shines. I re-ran the test on my older 2nd gen i5 computer, which does not support UASP. Read is approximately the same, but you can see how the write performance suffers dramatically. The max IOPS also goes *way* down. Ouch.

Finally, lets test a mechanical drive. Wow, look at that IOPS. Why does anyone use mechanical drives as their system drive anymore?

Bootability

Not much to say here, I have booted about three dozen computers from these drives, and they appear to work just fine as boot media. There has been an odd computer here or there that doesn't supply enough power to the mechanical drives, but the solid state drive seems to work every time.

Conclusion

If you want a cheap and reliable enclosure with a write protect switch, this is the way to go. I like my zalman drive, and still use it for the ISO capabilities, but you can't really beat a physical switch to make sure nothing nasty gets on your tools.

.... but somehow connected to it.

Let's see if someone can recognize this snippet (or guess who might have written it) WITHOUT opening the Spoiler

We worked six days a week and did not even complain about rough working conditions.
When we started working in the trailers, there were no steps to the entrance.
The entrance was about four feet off the ground.
We found some cinder blocks and empty spools that had contained mesh wire to help us enter the trailer.
Eventually we got steps, phones, and air conditioning, and life improved.

 

And no, it's not about abusing of third-world workers or such and the same cited person later concludes:

..., I could easily have missed it. I am glad that I saw it. I certainly was delighted with the $5,000 cash award.

 

Wonko

I would like to convert my Windows factory recovery discs, which consists of 2 DVDs, into a single bootable USB. I have tried formatting both USBs as either NTFS or FAT32, creating a single partition and marking it as bootable, then copying the contents of disc 1 then disc 2 (in that order) to the partition. No files from disc 2 overwrite the contents of disc 1, except autorun.inf, which I dont think matters for booting. Trying to boot the USB results in a blinking cursor on a black screen, booting from the discs works fine but it's just too slow. And discs are too prone to scratches, and yet another physical item I have to keep with we, as well as a USB DVD drive. The integrity of the ISOs the discs are burned from/copied from isnt in question, I've individually checksummed the files from the ISOs against the files on disc/USB, everything matched. And the ISOs themselves are checksummed, with a 2nd copy of each disc having been uploaded to Dropbox.

I've also tried mounting each ISO on my Zalman, I just get the blinking cursor. I've also tried mounting the ISOs in DriveDroid (Android app), connecting to PC via USB, but my BIOS either doesnt recognize it as bootable, or does see it as bootable but fails to actually boot it (same blinking cursor as before).

Is there a way to tell Grub4dos to just switch which boot loader is in the MBR & PBR? For compatibility reasons I'd like to switch between booting straight to Grub4dos and booting to the Windows Boot Loader (which can then boot to grub.mbr); I've had some myriad BIOS-controlled OEM systems which refuse to boot off of Easy2Boot but do still boot off the Windows Boot Loader (bootmgr).

I was also planning on making up a batch file to do it, too.

Hi,

I have created a windows 8 PE  64 bit image using WinADK. I wanted to run some 32bit applications in this image. By googling I find out 64 bit windows needs a 32bit subsystem to support 32bit application. How can I add this 32bit subsystem to my winpe boot image using WinADK ?. Please help

I ask this because I have had several USB cables 'burn out' on me in the past few months, and all were relatively new. Certainly there is some variation in the quality of cables by various manufacturers. I'm specifically referring to USB 3.0 cables, since these can serve a dual purpose for use with my external drives, as well as charging my phones and letting me copy data from them to PC and vice versa.

It is common knowledge that gold is an excellent conductor of electricity, and I figure that it may also be better for maintaining a consistent and stable data transfer rates. Or is the qualiity of the cord itself (not the tip) the main factor, since that is where the data must 'flow'?

If gold is indeed better, who are the best manufacturers/suppliers? 3 feet is the minumum I'd need, but 5 feet is a better length.

I need a network boot solution for an internet cafe . 

Can something like CCboot be accomplished with open source software?

I mean, booting from LAN, storing temporary changes made by users in separate place, without altering the main windows image and loading drivers for different computer configurations . 

Before I begin with the guide, I'd like to mention that the information here has been gathered from these sources, and I give all the credit to them:
http://4sysops.com/a...e-tools-part-1/
http://stealthfield....e-4-0-boot-iso/

1. First you need a PC with Windows 7 (or higher) installed on it. You obviously need a flash drive, 4GB should be enough.

2. You'll also need to download the Windows ADK for Windows 8 from Microsoft, and install it (the actual download is 1.95GB).

3. We're going to make your flash drive bootable. Make sure it doesn't contain important files. Open CMD with admin rights, and type:
[ATTENTION: Replace ‘#’ with the DISK number of your flash drive as it appears after typing LIST DISK]
 

diskpart
list disk
select disk #
clean
create partition primary
select partition 1
active
format quick fs=fat32
assign
exit

Here's an example screenshot:


ATTENTION! If you're building a 64bit WinPE4.0, use amd64 instead of x86 in the following steps.

4. Go to: [ADK Install DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\Media

5. Copy the entire "Media" folder to C:\Temp\PE4 (so now you should have C:\Temp\PE4\Media).

6. Copy [ADK Install DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim into: C:\Temp\PE4\Media\Sources (create this new "Sources" folder).

7. Rename the file “winpe.wim” to “boot.wim“.

8. From the Start Menu -> All Programs -> ADK folder, open the Deployment Tools Command Prompt, and type:
 
 

cd C:\Temp\PE4

9. We now need to create a new folder which will act as a mount point for the WIM file, so type:
 
 

md C:\MOUNT

10. To mount the WIM file, type:
 

DISM /Mount-Wim /WimFile:Media\Sources\boot.wim /Index:1 /MountDir:C:\MOUNT

11. We are now going to modify the boot.wim file by adding some optional components.

The additional components can be found in the following folder:
[ADK INSTALL DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs

Copy the "WinPE_OCs" folder to C:\Temp\PE4 (so now you should have C:\Temp\PE4\WinPE_OCs).

12. ATTENTION: After adding each component, you must also add its corresponding language file, otherwise the component you add won’t work!!
Adding a component takes a while, depending on its size. I recommend adding the following components by typing:
 

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\WinPE-Scripting.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\en-us\WinPE-Scripting_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\WinPE-WMI.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\en-us\WinPE-WMI_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\WinPE-NetFx4.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\en-us\WinPE-NetFx4_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\WinPE-PowerShell3.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\en-us\WinPE-PowerShell3_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\WinPE-Dot3Svc.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE4\WinPE_OCs\en-us\WinPE-Dot3Svc_en-us.cab"

      *You can put this code in a .bat file and run it to add all these packages in one go.

13. Now let's see how to add some drivers to your WinPE4.0.

ATTENTION: If you're building a 32bit WinPE - use 32bit drivers. For 64bit WinPE, use 64bit drivers!!
 

First, you'll need to extract the driver so that its CAT, SYS and INF files are accessible.
To add a (single) driver, type for example:
 

dism /image:C:\MOUNT /add-driver /driver:"C:\PathToDriver\drivername.inf"

DriverPacks are a good source for getting a lot of updated drivers in a single download (divided by categories).

For example, I added the LAN driver pack and the WLAN driver pack to my WinPE4.0.

ATTENTION: After downloading and extracting the driver packs, make sure to delete all the XP, Vista, NDIS5x, and NDIS61 folders, as they are not needed (WinPE4.0 is basically 6.2).
Also, I don't recommend adding the Chipset driver pack, as it contains drivers that might crash your WinPE4.0 on certain machines, and prevent it from booting normally.
Always test, test and test some more until your'e absolutely sure you have a good set of drivers.

You can add multiple drivers by typing:
 

dism /image:C:\MOUNT /add-driver /driver:[PATH TO DRIVERS] /Recurse /ForceUnsigned

This will take a while depending on the quantity and size of the drivers.

14. At this point, prior to committing your changes and unmounting the WIM file, you can copy certain portable standalone applications (such as Process Explorer, Ghost32, etc) into C:MOUNT so that they will reside inside the WIM file. However, I discourage you from doing so, as there's a better way, so bare with me.

15. Go into C:\MOUNT\Windows\System32 and open the file StartNet.cmd with Notepad (right-click on it and select "Edit").

16. By default, it only contains a single line (wpeinit). Replace its contents with the following, then save the file:
 

wpeinit
@echo off
for %%p in (a b c d e f g h i j k l m n o p q r s t u v w x y z) do if exist %%p:PStart set w=%%p
call %w%:PStart\PStart.exe

      Basically, it's looking for a folder named PStart in the root of all of the drives. When it finds it, it will attempt to run Pstart.exe inside that folder.

      NOTE for people building a 64bit WinPE4.0:

      You should use some other launcher or file explorer. For example, here I want the WinPE4.0 to launch directly into Q-dir 64bit, located in the folder Qdir:

wpeinit
@echo off
for %%p in (a b c d e f g h i j k l m n o p q r s t u v w x y z) do if exist %%p:Qdir set w=%%p
call %w%:Qdir\Q-dir.exe

      EDIT (as suggested by cdob): The code below does pretty much the same as above. I'm adding here this code which is based on Microsoft's own documentation. I've tried it, and it works just as well, so use one or the other:

wpeinit
@echo off
@color 1F
:: sets bg color to blue, and text to white

wpeutil.exe WaitForRemovableStorage
wpeutil.exe UpdateBootInfo

set PEBootRamdiskSourceDrive=
for /f "tokens=1-3 delims== " %%a in ('reg.exe query "HKLM\SYSTEM\CurrentControlSet\Control" /v "PEBootRamdiskSourceDrive" 2^>nul') do (
if %%a.==PEBootRamdiskSourceDrive. @set PEBootRamdiskSourceDrive=%%~dc
)
if Defined PEBootRamdiskSourceDrive (
echo PEBootRamdiskSourceDrive is %PEBootRamdiskSourceDrive%
)

@call %PEBootRamdiskSourceDrive%\QDir\Q-Dir.exe

17. ATTENTION: We are now going to commit our changes and unmount the WIM file. Close ALL file explorers, or the unmount process will give you an error!!

if you leave a Windows Explorer instance open, the unmounting process won't be able to cleanup the C:\MOUNT folder, and you'll see an error in the CMD window.
 

Type the following command:
 

DISM /Unmount-Wim /MountDir:C:\MOUNT /Commit

This process takes a while (a minute or so), so let it finish without interruption. When this process is finished, the C:\MOUNT folder will be empty.

18. Now copy the contents of the folder C:\Temp\PE4\Media to your flash drive. [EDITED 2012-03-21, thanks Wimb]

19. ATTENTION: This step is for WinPE 4.0 x86 ONLY. PSTART will not work on WinPE 4.0 x64, unless you manually add WoW64.
The WinPE4.0 flash drive is now bootable. However, since WinPE doesn’t have a GUI interface like a regular Windows, you have to launch your tools from the command prompt, which is too inconvenient.
That is why we're going to add PStart to the flash drive. PStart is a simple and free standalone menu which allows to start user-defined applications. Download PStart from here.
When you run the PStartSetup211.exe, choose "Portable Setup"->Select your flash drive -> Next -> Browse -> Make new folder ->type: PStart and click OK -> Install Now -> Finish.

Here's an example of my PStart menu:


20. Just to remove any doubt, this is how the root of the flash drive should be at this moment (ignore the WINPEX64 name on top):

     The boot.wim file should be in the Sources folder, and PStart.exe should be in the PStart folder.

      

21. Double-click the pstart.exe to open the menu (from the flash drive).
Copy any utilities or applications that you like to the flash drive, and drag-n-drop their executable to the PStart menu.
I highly recommend adding some sort of file explorer, for example: Q-Dir, Explorer++, XYplorer, etc.

22. Once you're done adding all your favorite apps, close PStart by clicking File->Exit Application (clicking on the X button doesn't close it!!).

23. Eject the flash drive, and boot from it by selecting it from the BIOS Boot Menu. Once it's done loading, PStart should appear and you can pretty much do anything from here on. The great thing about adding files through PSart is that whenever you want to add a new app or update an existing one, it's as simple as drag-n-drop. Simply connect your WinPE4.0 flash drive to your Windows machine, run PStart, and perform all the necessary changes.

Here's a screenshot I took from one WinPE4.0 I've created:

Hello,

seems like this page describes how to add +4 GB files on FAT32 drives but I don't know which method should I use (the entire page looks really chaotic for me). Therefore I want to ask you which method should I use.

• I've downloaded a Windows 10 Pro x86 + x64 ISO which size is 5.6GB
• My drive is formatted as FAT32 for compatibility reasons (I had multiple PC's which couldn't boot a NTFS drive) so I can't just copy the ISO on it
• I want to install Windows 10 using the VHD method for testing, and then maybe install it as a main OS
• Currently I have Windows 8.1 installed in non-UEFI mode, I'm mentioning it because I think it might be important

So how do I copy the Windows 10 ISO file on my drive?