Eric,
Thank for replying. I use this ISO file to insert into a multiboot USB, besides other: Win 7 PE, Mini XP...
Posted 23 November 2013 - 02:53 AM
Eric,
Thank for replying. I use this ISO file to insert into a multiboot USB, besides other: Win 7 PE, Mini XP...
Posted 23 November 2013 - 07:54 AM
ok, I got it working, I followed the tutorial exactly except I topped at step 12 and picked back up at 14. so I didnot add drivers or components. I put it on a fat32 formated pny 8gig usb stick and it booted on my quad amd just fine, I am planning on trying the build again and just putting the drivers with out the components to see if it still works and then narrowing them down one at a time.
but yes with out either it works just fine.
thanks for the help
Taylor
Posted 23 November 2013 - 09:41 AM
Sure thing, Taylor.
Glad your got it working.
Posted 03 February 2014 - 03:33 AM
By the way, there's also a much faster way to create a WinPE 5.0 USB drive, for those who have Windows 8.1 installed, using the command RecoveryDrive.exe.
Would you write tutorial about this? Or may be some link out of this forum? I would be very appriciate.
Thanks any way for your tutorials.
Edited by cepbl4, 03 February 2014 - 03:35 AM.
Posted 03 February 2014 - 07:31 AM
cepbl4,
It's really simple: insert a USB drive, run the command and follow the on-screen instructions.
I haven't tried it yet, as I'm currently sticking to Windows 7...but it should work.
Posted 03 February 2014 - 10:04 AM
Hi Eric
I haven't tried this but in Step 16 you have two code alternatives for startnet.cmd. It looks to me like the MS code will only work if the Flash drive is of the 'Removable' type - many flash drives are not these days, so I would suggest that you recommend using the other code instead (except maybe remove the a b as the USB flash drive is unlikely to be drive A: or B:!).
Posted 03 February 2014 - 10:40 AM
steve6375,
According to Microsoft, the 2nd code should do just fine with USB hard-drives, not just USB flash drives:
"During the Windows PE startup sequence, this command will block startup until the removable storage devices, such as USB hard drives, are initialized"
Posted 03 February 2014 - 10:46 AM
ah, OK. Either should be fine then.
Posted 11 February 2014 - 09:40 PM
Eric,
what is your experience booting EFI? I am trying to follow your usb drive creation and added formatted the drive per
http://technet.micro...y/hh825109.aspx
which creates the FAT32 partition and then an NTFS partition. I found that I needed to make the FAT32 partition 8gb rather than the 2gb used in the example so that all of the drivers would fit. Granted, I have included drivers for several motherboards which most people would not have to deal with.
I am trying to use it on an Intel DQ67SW motherboard. I added the chipset drivers to the files as you outlined. The bios for the motherboard has uefi enabled. I can not get the external hard drive to boot directly even though it is enabled and set in the bios boot options. Instead, I have to hit F10 (one time boot sequence) and then select the drive. The windows 8 logo appears and after a while errors out complaining about EFI being enabled. The drive is EFI if I disable EFI in the bios the system will not find a boot device.
I do not see much about being able to boot and image UEFI and Bios computers using the same boot and imaging system and yet Microsoft says that the setup should work for either or both.
I am trying to find what I am missing. Have you had any experience with UEFI imaging?
Thank you.
Posted 12 February 2014 - 07:52 AM
Southerner,
There are two boot files in WinPE (assuming X is your USB flash drive letter):
X:\boot\bcd (Legacy BIOS)
X:\EFI\Microsoft\boot\bcd (EFI)
The only difference between these two files (besides their location) is that the former points its entries to winload.exe, and the latter to winload.efi.
These bcd files have no extension.
You can view and edit them using bcdedit.exe, through the command line (CMD).
Here's a link to some useful commands for editing these bcd files (please read through the entire post before making changes to your files):
http://reboot.pro/to...e-8#entry169704
Posted 12 February 2014 - 09:09 AM
UEFI_MULTI.exe can make BIOS + UEFI entry in Boot Manager Menu on Target Boot Drive
for WIM Boot Image file to enable booting from RAMDISK.
http://reboot.pro/to...boot-usb-drive/
Posted 11 March 2014 - 11:54 PM
Created my WinPE 5 boot USB without any issues. But I also included a DOS program called Spinrite. This is a great disk repair program, but needs direct access to BIOS for disk access. When I try and launch Spinrite I get an error message "The subsystem needed to support the image type is not present." Is there a way to include the necessary subsystem?
Thanks
Posted 12 March 2014 - 08:09 AM
garryweil,
Glad to hear you've managed to go through the guide without problems.
If Spinrite is a DOS program (16bit), it cannot work on a Windows environment.
Besides, if you've created a 64bit WinPE5, only 64bit apps will run on it.
I haven't included WoW64, which enables 32bit apps to run in a 64bit OS.
So, you'll see that message when you try to run a 32bit app in WinPE5 x64.
With that said, you could try to create a WIM file, which contains the DOS environment & Spinrite, and boot from that.
This is out of the scope of this tutorial, so please try to follow these leads, maybe you'll get lucky:
http://social.techne...=winserversetup
http://www.deployvis...US/Default.aspx
Posted 04 April 2014 - 09:00 PM
Hello
Good tutorial. Thanks. A question though: am I the only one having problems with Q-Dir? I added it to my winpe drive, it starts up ok, no errors, but when I try to create a folder for example, the folder shows up only after I hit "refresh". Also, I tried to copy some files from a drive to another and nothing happens. It seems that Q-Dir relies on the system default copy method which is missing from winpe.
Also, other commands from Q-Dir menus don't work (like shoutdown or restart). Are there any dlls that should be added?
P.S. I created the 64 bit win pe 5.1 version
Edited by AndreiV, 04 April 2014 - 09:00 PM.
Posted 04 April 2014 - 10:26 PM
AndreiV,
You're right. After creating a folder/file with Q-Dir, you need to press F5 to refresh the view.
Copying works fine, you just need to refresh the view. A little annoying, but it works.
I don't know about any DLL files that should be added. It hasn't bothered me too much, so I haven't looked for a solution.
Maybe the latest version of Q-Dir fixes this behavior?
The shut-down and restart commands from Q-Dir will not work. They rely on functionality that is missing from the basic WinPE.
If you need a more robust WinPE solution, perhaps you should try Win8.1_SE.
Posted 04 April 2014 - 10:37 PM
I just did some tests. Q-Dir relies too much on system functions. A much better solution is Total Commander:
http://www.ghisler.com/download.htm
It has 32 and 64 bit versions, can be made portable and it implements its own functions (for copy, etc) so it works just fine (with progress dialog and all)
I am switching to total commander. It is shareware but it isn't limited. You just have to press a button at startup...
Posted 04 April 2014 - 10:42 PM
Yep, Total Commander is a viable option.
Just be sure to change the StartNet.cmd script accordingly.
Best of luck.
Posted 06 April 2014 - 02:07 PM
Done.
Something else that works very well in WinPE environment is AutoIt. The scripts created with it use basic system functions so they all work, with GUI and all. I created a few scripts in Autoit and I use them successfully in WinPE.
For example, the shutdown function from AutoIt works perfectly in WinPE (as opposed to the shutdown function from Q-Dir that does not work).
Posted 06 April 2014 - 02:13 PM
Thanks AndreiV,
Good to know that AutoIt scripts are working with a basic WinPE.
Posted 06 April 2014 - 02:15 PM
Glad to contribute.
Posted 21 October 2014 - 08:28 AM
I've followed your tutorial from start to end.
The pc boots up, but it will not find the USB that is has booted from.
It seems that the usb drivers are not loaded. I have added the correct drivers to the boot image With the dism-command, but they don't load. Nor can I start the driver With drvload.exe.
I'm using a USB 3.0 Device, and my pc has only USB 3.0 ports.
What can be wrong??
If I use a USB 2.0 Device, everything Works great. Because of speed I want to use USB 3.0 Device.
Posted 21 October 2014 - 08:52 AM
I've followed your tutorial from start to end.
The pc boots up, but it will not find the USB that is has booted from.
It seems that the usb drivers are not loaded. I have added the correct drivers to the boot image With the dism-command, but they don't load. Nor can I start the driver With drvload.exe.
I'm using a USB 3.0 Device, and my pc has only USB 3.0 ports.
What can be wrong??
If I use a USB 2.0 Device, everything Works great. Because of speed I want to use USB 3.0 Device.
Well, I can boot from a USB3.0 port without any problems.
I get a choice or "regular" boot and UEFI boot. I usually select "regular" boot.
First, you should try without adding any USB3.0 driver. See how it goes.
It that fails, please make sure that:
1. You load the correct drivers (Intel, Via, NEC/Renesas).
2. The architecture is correct (x86, x64).
3. The driver is compatible with Windows 8 / 8.1.
There's no need to use drvload.exe. I haven't used it in my tutorial.
EDIT:
Please make sure that your BIOS is configured properly. The problem might be there.
If you have the following options in your BIOS, make sure they are as mentioned here:
Legacy USB support: Enabled
XHCI pre-boot mode: Auto (or Enabled)
Posted 22 October 2014 - 05:13 AM
Thanks for quick response.
I've tried now without the drivers in the image, and there is no difference.
The pc boots up, and can not see the USB Device.
I have the correct drivers (amdxhc), for the correct architecture (x86).
The BIOS have the correct settings:
Legacy USB support: Enabled
USB 3.0 (XHCI): Enabled
My goal is to boot on the USB Device and install my own modified image to several pc's.
Posted 22 October 2014 - 06:39 AM
Thanks for quick response.
I've tried now without the drivers in the image, and there is no difference.
The pc boots up, and can not see the USB Device.
I have the correct drivers (amdxhc), for the correct architecture (x86).
The BIOS have the correct settings:
Legacy USB support: Enabled
USB 3.0 (XHCI): Enabled
My goal is to boot on the USB Device and install my own modified image to several pc's.
Just a hunch:
Try creating a 64bit version, and boot from that. See what happens.
Posted 22 October 2014 - 08:34 AM
Tried 64-bits, but nothing changes.
It seems that these drivere don't like to start in WinPE.
Boot methods & tools →
Boot from USB / Boot anywhere →
WinPe 2024 LazesoftStarted by fi-zilal , 4 weeks ago winpe, boot.wim, iso, ventoy and 5 more... |
|
|
||
Boot methods & tools →
Boot from USB / Boot anywhere →
USBDualPartStarted by rradjab , 14 Jun 2023 dualpart, usb dual part and 7 more... |
|
|
||
Groups →
Windows Extreme →
Windows PE →
Windows 11 PE AudioStarted by MetallicWheat , 05 Mar 2023 winpe, winpe11, audio |
|
|
||
Groups →
Windows Extreme →
Windows PE →
Windows 11 PE AudioStarted by MetallicWheat , 05 Mar 2023 winpe, winpe11, audio |
|
|
||
Groups →
Windows Extreme →
Windows PE →
Windows PE 11 - 22621.1 WOW64 SupportStarted by MetallicWheat , 17 Feb 2023 winpe, windows pe, windows 11 pe and 1 more... |
|
|
0 members, 0 guests, 0 anonymous users