It's been some time since I last used winbuilder and all the other tools referenced here in the forum.

But I am facing a difficult task and I remembered reboot.pro could have the solution to my problem.

VMware used to have a BootCD for their vCenter Converter tool but unfortunately it was discontinued since version 4.3 (current is v5.x).

I know that vCenter Converter Standalone can be installed on the any system that I wish to convert to virtual but somehow our credentials don't allow us to install software on this particular server (not even Windows updates).

Worse than that, we've been told that if we find a way to install anything on this server we will void the maintenance contract. Accounting software server. We reeeeally don't want to mess with our accounting software.

So we checked with them and they don't see any problem in converting the system to virtual.

So our only hope is to build a BootCD with network support that could run vCenter Converter 5.x.

Does anyone know how we could do that?

Thanks in advance.

Cheers

In practice, nearly every file in the WinSxS directory is a hard link to the physical files elsewhere on the system meaning that the files are not actually in this directory.

\Winsxs\Backup: Backups of the manifest files in case the copy in \Winsxs\Manifests becomes corrupted

\Windows\winsxs\amd64_microsoft-windows-wimgapi_31bf3856ad364e35_6.1.7600.16385_none_e4f094112e8f905d\wimmount.sys
\Windows\System32\drivers\wimmount.sys

\Windows\System32\drivers\wmiacpi.sys

\Windows\winsxs\amd64_microsoft-windows-wmilib_31bf3856ad364e35_6.1.7600.16385_none_b549ebfe1dddb7f1\wmilib.sys
\Windows\System32\drivers\wmilib.sys

rem find double files
rem http://www.sentex.net/~mwandel/finddupe/
finddupe.exe -bat hl.txt -hardlink f:\

findstr.exe /I "winsxs" hl.txt > hl.cmd

rem joakim http://reboot.pro/files/file/237-runassystem-and-runfromtoken/
net.exe start trustedinstaller
runassystem64.exe "runfromtoken64.exe trustedinstaller.exe 1 cmd.exe"
hl.cmd

findstr /I "boot.sdi .mui .nls DriverStore WindowsPowerShell .cat .rtf dlmanifests drivers DriverStore assembly MediaCenter ehome .inf RemoteAccess servicing winsxs" hl.txt > hl2.cmd
hl2.cmd

• Automatically downloads latest version
• Automatically update definitions at build time
• Multi-language support

• Definitions updated at build time appear as missing or corrupt in PE [See This Post] and [this post]

{B05566AC-FE9C-4368-BE02-7A4CBB7CBE11} Windows Firewall with Advanced Security

imdisk -a -s 60M -m #:

• FAT32 format support for >32GB drives, based on fat32format, from Ridgecrop Consultants Ltd:
• Automated update check
• Relax ISO9660 compliance for Arch Linux images
• Add support for VMWare ESXi 5.1 ISO images
• Update Syslinux to v4.0.6 and libcdio to v0.90
• Miscellaneous UI improvements and fixes

I am using wINBUILD 082

Thanks

Josh

Along the way, they use something called "chocolatey" which aims to be an apt-get for Windows. Details at http://chocolatey.github.io/

I use Windows 7 64, cmd as Administrator and rawcopy:

Version 1.3.2. Copyright (C) Olof Lagerkvist 1997-2014. 

I start with the smaller image, to make the attempts faster.

First I discover the name:

c:\tmp>wmic diskdrive get Name,Caption | find "USB"
USB DISK 2.0 USB Device \\.\PHYSICALDRIVE3

I want to experiment with 4 MB

Copying from the stick works:
 

C:\tmp>rawcopy -m -v 4M \\.\PHYSICALDRIVE3 t.bin
Copying 4194304 bytes.
Buffering 524288 bytes.
Source device locked and dismounted.
Reading block 84288 bytes...
4 MB copied.

Now trying to copy back, I experimented adding even more different flags but eventually came only to:

C:\tmp>rawcopy -i -w -x -v -d -m:32K t.bin \\.\PHYSICALDRIVE3
Buffering 32768 bytes.
Target device locked and dismounted.
Ignoring write error at block 0: Access is denied.

32 KB copied.

C:\tmp>rawcopy -i -w -x -v -d -m:32k t.bin \\.\PHYSICALDRIVE3
Buffering 32000 bytes.
Target device locked and dismounted.
Writing block 0
31.25 KB copied.

So even 32K (32768) is too much, and after ignoring it still doesn't copy more and 32k (that is 32000) isn't too much, it doesn't complain but then it stops???

So does anybody know how to copy everything that's inside t.bin back to the usb stick with the RawCopy? Is it even something that should be attempted at all?

Thanks.

"Designed to cut any diameter glass bottle super easy, fast and precisely at home. Create glasses, vases, lamps, etc."

https://www.kickstarter.com/projects/1968590924/candc-the-bottle-cutter

http://www.indiegogo.com/projects/urb-e-the-world-s-most-compact-e-vehicle

"Please go to the supermarket and buy a package of milk. If they have eggs, bring ten."

The programmer came back with 10 packages of milk.

Wife: "Why did you get 10 packages of milk?"

Programmer: "Because they have eggs!"

We're preparing the next winbuilder edition. Whenever the end-user starts the program, winbuilder will display a memorable quote from a reboot member.

Since the new version is close to ready, we'd like to add more quotes. If you have any suggestions, please reply back with the quote and link on reboot.pro where it was posted.

Good chance to highlight quotes that should be passed onto next generations.

Thanks!

File Name: CCleaner for Win8PE and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 16 Mar 2014
File Updated: 16 Mar 2014
File Category: App scripts

Homepage and info:
https://www.piriform.com/ccleaner/features

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html


____________________________________________________

Click here to download this file

File Name: Defraggler for Win8PE LiveXP and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 15 Mar 2014
File Category: App scripts

Homepage and info:
https://www.piriform.com/defraggler/features

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
http://al-jo.net46.net/livexp/livexp2.html
____________________________________________________

Click here to download this file

The project has met its goal.

https://www.kickstarter.com/projects/1925492980/plinth-the-worlds-best-stand-for-your-tablet-ipad

Website

http://myplinth.co.uk/

A demo review by Geek Beat of the 3D printed model of the Plinth - a universal tablet stand.

Meet Plinth, the Pocketable Tablet Stand

Also posted in the Dell Venue 8 Pro thread. Been looking for something like this.

http://reboot.pro/topic/19557-dell-venue-pro-8-tablet-windows-81-hard-reset-and-stuff/

post11

Sorry for my very bad english ...

I have compiled a 32 bits version of win8pese with succes .

Now i've started the same but with 64 bits source of Windows 8 .

All seems ok but the 32 bits programs are place in Program Files instead of Program Files (x86).

Is there any way to force Programs Files to be converted in Programs Files (x86) when use 64 bits source ?

Thanks a lot for any help for solve this issue .

quand j'ouvre son interface en haut a gauche il y a un bouton Downloader

je clic dessus on peut sélectionné téléchargement complé mais une foi télécharger 

quand je reviens sur la première interface je ne vois pas ce que j'ai télécharger comment

faut il faire pour pouvoir avoir ce que j'ai télécharger dans l'arborésense de la première 

interface ? je sais pas si j'ai été très claire !!!

Merci de votre aide

I wanted to be able to inject the Symantec PGP encryption recovery commands into a prebuilt Win7PE disk that I created using WinBuilder. I have referenced David Cowen's instructions on creating a Win7PE disk.

http://hackingexposedcomputerforensicsblog.blogspot.com/2014/02/daily-blog-242-how-to-build-winfe-to.html

Do I need to inject the PGP stuff into the boot.wim before or after the Win7PE ISO is created?

Any help with this topic would be much appreciated.

-KP

File Name: CrystalDiskMark for Win8PE and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 12 Mar 2014
File Category: App scripts

Homepage and info:
http://crystalmark.info/software/CrystalDiskMark/index-e.html

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
___________________________________________________

Click here to download this file

I like to know how to make iso boot in UEFI(efi)

and how to add scripts


Maybe in Windows 8 64-bit it's best

Big thank you to you

@ + Christs

Can we partition USB drive in such a way that both partitions show up in Windows but 1 of them is locked and cannot be deleted/ formatted and the 2nd partition is available to the User as normal Flash drive.

Basically we want to give some presentation pre-loaded in the drive to Users but don't want them to remove the contents from the USB drive.

Thanks in advance.

(also posted on following threads, Post 9  and originally by reedsutton post #636 )

Power you're tablet while using USB devices at the same time

https://www.kickstarter.com/projects/1094775787/port-power-usb-at-the-same-time/

Creator Mobile Design Labs on Feb 23

Hi Jeff,

The tablet in the video is a Dell Venue 8 Pro. It is running Windows.

Thank you

Jeff Lerner-Powers on Feb 23

Hi, I'm very excited about your product and campaign. What is the name of the tablet that is on the stand in your video? I'm sorry for not knowing, but it looks as though it is running windows. Thank you in advance, and good luck moving forward. Jeff

 

 
3. Now 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 par primary
select par 1
active
format quick fs=fat32
assign
exit

Here's an example screenshot:

 
4. Go to: [ADK Install DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media
 
5. Copy the entire "Media" folder to C:\Temp\PE5 (so now you should have C:\Temp\PE5\Media).
 
6. Copy [ADK Install DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim into: C:\Temp\PE5\Media\Sources (create this new "Sources" folder).
 
7. Rename the file you copied, from “winpe.wim” to “boot.wim“.
 
8. From the Start Menu -> All Programs -> Windows Kits -> Windows ADK, open the Deployment and Imaging Tools Environment, and type:
 

cd C:\Temp\PE5
C:

 
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:C:\Temp\PE5\Media\Sources\boot.wim /Index:1 /MountDir:C:\MOUNT

11. We’re now going to modify the boot.wim file by inserting some optional components, which can be found here:
      [ADK INSTALL DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs
 
      Copy the "WinPE_OCs" folder to C:\Temp\PE5 (so now you should have C:\Temp\PE5\WinPE_OCs).
 
12. ATTENTION: After adding each component, we must also add its corresponding language file, otherwise the component you add won’t work!!
      I recommend adding the following components, in the order they appear:
 

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

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

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-NetFx.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-NetFx_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-SecureStartup.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-SecureStartup_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-PowerShell.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-PowerShell_en-us.cab"

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

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-StorageWMI.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-StorageWMI_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-EnhancedStorage.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-EnhancedStorage_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-SecureBootCmdlets.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-DismCmdlets.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-DismCmdlets_en-us.cab"

* The SecureBootCmdlets package doesn't have a language file associated with it.

* 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 WinPE5.0.
First, you'll need to extract the driver so that its CAT, SYS and INF files are accessible, i.e. not in ZIP file.
 
To add a (single) driver, type for example:

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

     Preferably, if you have a folder containing several drivers (each in its own folder), you can add them all in one go by typing:

dism /image:C:\MOUNT /add-driver /driver:[PATH TO DRIVERS FOLDER] /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, Ghost64, 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:Qdir set w=%%p
call %w%:Qdir\Q-dir.exe

      The code below is based on Microsoft's own documentation; it does pretty much the same as above.
      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’re now going to commit our changes and unmount the WIM file. Close ALL file explorers, or the unmount process will give you an error!!
      Then type the following command:

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

When this process is finished, the C:\MOUNT folder will be empty.

18. It is advised to optimize the WIM file, so run the command:

DISM.exe /export-image /sourceimagefile:C:\Temp\PE5\Media\Sources\boot.wim /sourceindex:1 /destinationimagefile:C:\Temp\PE5\Media\Sources\boot_optimized.wim

   The optimized file should be a little smaller. It is safe to delete the boot.wim file, and then rename the boot_optimized.wim to boot.wim.

 
19. Now copy the contents of the folder C:\Temp\PE5\Media to your flash drive (To clarify: Copy what's inside the folder, not including the folder itself).
      The WinPE5.0 flash drive is now bootable.   

20. Grab Q-Dir portable x64 from here, and extract the files to your bootable flash drive. Make sure the folder is named "QDir" and resides on the root of the drive.
 
21. Eject the flash drive, and boot from it by selecting it from the BIOS Boot Menu.

      The exact key  to get to the Boot menu depends on which motherboard you have.

      On Dell computers it's usually F12. On Gigabyte motherboards it's also F12.

      Other manufacturers use a different key to get to the boot menu. Please check yours.

      Once you are in the boot menu, you'll probably see something like this (I'm using a Gigabyte motherboard, and SanDisk flash drive):

      You can choose to boot in legacy mode, or in UEFI mode. Both should work just fine.

22. Once it's done loading, QDir should appear and you can pretty much do anything from here on.

I don't know if there is a way to use ImDisk without install.

It is better if I can just extract imdiskinst.exe and use ImDisk without installl ? Can I manual install ImDisk driver and manual uninstall without ImDisk Uninstaller ? I think if I can do that, it is possible to use ImDisk as Portable software.

But I don't know if after install ImDisk still left some registry key or not ? I want to know that because if this happen, I will manual clean it.

Some good information that I found:

Command line to install/uninstal ImDisk: lhttp://reboot.pro/topic/12467-imdisk-command-line-installuninstall-revised/

ImDisk commandline: http://diddy.boot-land.net/firadisk/files/imdisk.htm

Hope I will have a choice, because no other RAMDisk software as portable as ImDisk, other RAMDisk software write a bunch of registry key to my system, still need restart to use, but ImDisk no need restart my system, very cool.

And I can use ImDisk without control panel, only command line is enough.

Thank!

mail password viewer (Nir soft) not working for outlook 2013.

This includes the ImDisk Virtual Disk Driver, the DiscUtils library for managing the formats of image files like VHD, VDI, VMDK, etc., the RamDisk Configuration Tool (RamDiskUI), and some new GUI to use the capabilities of DiscUtils directly from Explorer and add some features.

Please note that RamDiskUI is no longer available alone, but can be used exactly like before. It has no dependency (except, of course, the ImDisk Virtual Disk Driver) and uses the same parameters than the previous versions.

You can download the installer of the ImDisk Toolkit and the sources here:

http://reboot.pro/files/file/284-imdisk-toolkit/

This is just for info.I have a Kingston 8GB class 4 SDHC card.  When I try to write to the card under windows 7 or linux the device dissappears.  In linux the dmesg output is:

[  262.976043] usb 1-9: new high-speed USB device number 5 using ehci_hcd
[  263.110678] usb 1-9: New USB device found, idVendor=25bf, idProduct=0001
[  263.110684] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  263.110689] usb 1-9: Product: isostick
[  263.110693] usb 1-9: Manufacturer: Elegant Invention
[  263.110696] usb 1-9: SerialNumber: A7D219613953343836332020FF0813
[  263.180294] Initializing USB Mass Storage driver...
[  263.180514] scsi6 : usb-storage 1-9:1.0
[  263.180671] usbcore: registered new interface driver usb-storage
[  263.180676] USB Mass Storage support registered.
[  264.180865] scsi 6:0:0:0: CD-ROM            ELEGANT  ISOSTICK CDROM   1.30 PQ: 0 ANSI: 5
[  264.181967] scsi 6:0:0:1: Direct-Access     ELEGANT  ISOSTICK FLASH   1.30 PQ: 0 ANSI: 5
[  264.185710] sr2: scsi-1 drive
[  264.185961] sr 6:0:0:0: Attached scsi CD-ROM sr2
[  264.187482] sr 6:0:0:0: Attached scsi generic sg5 type 5
[  264.188375] sd 6:0:0:1: Attached scsi generic sg6 type 0
[  264.191463] sd 6:0:0:1: [sdd] 15572992 512-byte logical blocks: (7.97 GB/7.42 GiB)
[  264.193215] sd 6:0:0:1: [sdd] Write Protect is off
[  264.193222] sd 6:0:0:1: [sdd] Mode Sense: 23 00 00 00
[  264.194333] sd 6:0:0:1: [sdd] No Caching mode page found
[  264.194339] sd 6:0:0:1: [sdd] Assuming drive cache: write through
[  264.200709] sd 6:0:0:1: [sdd] No Caching mode page found
[  264.200716] sd 6:0:0:1: [sdd] Assuming drive cache: write through
[  264.202975]  sdd: sdd1
[  264.208084] sd 6:0:0:1: [sdd] No Caching mode page found
[  264.208091] sd 6:0:0:1: [sdd] Assuming drive cache: write through
[  264.208096] sd 6:0:0:1: [sdd] Attached SCSI removable disk
[  264.362601] ISO 9660 Extensions: Microsoft Joliet Level 3
[  264.368997] ISO 9660 Extensions: RRIP_1991A
[  264.681958] FAT-fs (sdd1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[  310.168872] usb 1-9: USB disconnect, device number 5
[  310.188072] sd 6:0:0:1: [sdd] Unhandled error code
[  310.188079] sd 6:0:0:1: [sdd]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  310.188085] sd 6:0:0:1: [sdd] CDB: Write(10): 2a 20 00 3c 87 68 00 00 f0 00
[  310.188098] end_request: I/O error, dev sdd, sector 3966824
[  310.724040] usb 6-1: new full-speed USB device number 2 using ohci_hcd
[  310.897059] usb 6-1: New USB device found, idVendor=25bf, idProduct=0002
[  310.897067] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  310.897072] usb 6-1: Product: isostick emergency recovery
[  310.897076] usb 6-1: Manufacturer: Elegant Invention
[  310.945526] cdc_acm 6-1:1.0: ttyACM0: USB ACM device
[  310.948210] usbcore: registered new interface driver cdc_acm
[  310.948215] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

The iso stick is brand new with the latest firmware. Writes work with a 1GB micro SD card and I've seen one ISO file load.  I have a class 10 32GB card coming this week so hopefully it will work better with that.

Chris

• A successful build every time!
• Clean and simple user interface
• Good quality instructions

We could have a new topic called 'mnu files for sambul's Multiboot disk', and rebooter's could post their mnu donations on it. So a standard expert's post would be a URL to the download for the 'image' file plus the mnu as an attachment. So we could build up a library of mnu files (instead of users having to add a menu entry to their menu.lst).

Instructions for a user would be:
1. Create a multiboot basic drive following instructions (e.g. use RMPrepUSB ...)
2. Download your ISO (or whatever and copy to your drive)
3. Download mnu file and copy it to the same folder

Some images will need special instructions (like extract folder xyz from the iso and copy it to xyz on the USB drive for some 'special' ISOs that won't boot from an ISO file!)

There would be multiple partitions on the flash drive, with one partition having Windows XP installer, another having Windows 7 installer, another with YUMI for linux distributions, another for Hiren. 

Can the Windows boot sector (or whatever it is called) on the CD/DVD, be used on the PBR rather than the MBR?

When one selects the partition one wants to boot into, from the Grub menu, then by a series of Grub commands:

1) one would set the default partition Grub would boot into after an X second timeout ( see https://www.gnu.org/...avedefault.html )

2) one would set the first partition on the USB flash drive (so Windows installer can find it's files) through Grub commands ( see http://www.rmprepusb...ls/multipartufd )

Possible?

Not that it's impossible or too difficult, but why all the mess?

WinSetupFromUSB and Easy2boot can handle just about any mix of sources in a single partition, why would you need to go into way more complicated setup with multiple partitions on a removable drive?

Because I want to keep the files of different Windows installers from mixing all together: it makes it easier to use folder comparison programs.

Because I don't want the files in an ISO.  I have to keep recreating an ISO for no particular reason.

When you decide to edit contents of the disk, you'd have to switch visible partition to Windows as well. Of course a filter driver or flipping the removable bit so Windows works with a fixed disk and all partitions is a way around, but again, is it really worth, unless you have something else in mind?

I am already using the driver that shows all the partitions on the flash drive.  Why not have this driver?  It appears to be superior.

From http://www.winsetupfromusb.com/faq/

"" 6. Are customized Windows sources supported?

Generally speaking- yes. Due to the numerous ways to customize XP for example, it’s hard to test every kind of customization, hence severely modified sources may not install properly. In case of NT6 (Vista and above) customized source, as long as updates or hotfixes are integrated into install.wim and using postsetup.cmd script, which seeks for files on the system drive, rather than the source DVD, there should be no issues. ""

I have this in setupcomplete.cmd:

FOR %%i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %%i:\$oem$\UnattendedOOBE.xml SET DVDRoot=%%i

ilko, on 14 Feb 2014, said:

Not a perfect world...

Manufacturer has some basic guidelines, $OEM$ goes to <DVD>(USB)\sources\$OEM$. Setup, in PE phase, copies contents to destination drive. First reboot. $OEM$ is not needed and used any more, nor should be other folders/files on the DVD/USB. Custom scripts search their things in the already copied contents of $OEM$ to the destination drive, not on the DVD/USB. Nothing is broken, everyone is happy, there are some rules followed.

Of course, there are sources which are customized in a different way with different needs. One may not want to copy OEM content to the destination drive for some reason, shared OEM folder for several sources, big sized contents, place it elsewhere as in your case and explicitly search for it etc.  Can such sources be easily added programatically in a multiboot scenario?

Unfortunately there has to be some trade off, a little user intervention and understanding what is what and how it works, second boot from USB, no multiboot, or some other limitation.

Thanks.  I changed that part of my install method to copy contents to the drive (via $oem$ folders), and invoke from there, instead of the flash drive.  Later I delete what was copied over.  Now my custom windows installer is compatible with WinSetupFromUSB, and probably a lot of other multi-boot utilities.

For now I will live with having to create and copy an ISO every time I make a small change, rather than copying a couple small files over

...or I may go with Rufus for one OS per USB flash drive

...or I may go with Rufus in combination with multiple partitions, LOL.

Update: Found out another drawback to using $oem$ folders as opposed to "FOR %%i IN (C D E F G H I ...".  For mbr multipartitioned drives (destination for the Windows install), the drive letters are different during the first stage and the last stage of the Windows install.  [primary1] [primary2] [primary3] [extended [logical-data]]

This is deal breaker, so I am again wanting to multi-partition a flash drive for the different OS installers.  Any tips on how to set up Grub, etc?

http://www.youtube.com/watch?feature=player_embedded&v=MBKh_jDyTmQ

This thread is to discuss how the Easy2Boot (as it is currently called) grub4dos multiboot USB drive project can be developed, enhanced and improved.
The idea (from sambul61) is to create a multiboot USB drive to which the novice user can easily and quickly add any boot image he or she wants to their multiboot USB drive.
All that is needed is the correct grub4dos menu mnu file and the 'payload' file (an ISO in most cases). We, at reboot.pro can easily provide the required grub4dos menu file (called xxxxx.mnu for Easy2Boot) and so can provide a bank of these mnu files which can be kept up to date.

This project is similar to the grub4dos grub4dos, .iso images and (hd32) or (0xFF) mapping topic, but Easy2Boot will apply to any type of bootable binary that can be booted via grub4dos (or possible from grub4dos via syslinux) and will provide a .mnu file which the user simply copies to his Easy2Boot USB drive (no editing of their menu.lst required).
The user can delete the 'payload' files and leave the mnu files on the drive - the relevant menu entries will NOT appear on the user menu until the user chooses to add back on the payload file.

There is an embryo tutorial at http://www.rmprepusb...asy-to-maintain

Working and tested .mnu files can be posted at http://reboot.pro/16426/ (note that it is NOT a discussion thread - please use this thread for any any discussion).

Some points for discussion are (amongst others):

1. Is the name Easy2Boot OK? (if not we need to change it quickly)?
2. Do you think the idea will catch on and encourage multiboot newbies to have a go (and will you contribute mnu files with a few instructions for your favourite bootable binary?) - or is cut and paste and editing a menu.lst file not really that hard (even for a newbie)?
3. Is the choice of /_ISO for the main folder OK (again if not we need to change it quickly)?
4. What would make the best, generic, foolproof (multi-national) USER.mnu (the default menu settings) - currently I have this set to a UK kbd and a 'borrowed' background image just for test purposes.
5. Would someone like to donate a royalty free splashimage (maybe with Easy2Boot printed across it and reboot.pro?)

Please try out this tutorial and see how this process works (or doesn't) and report back!

quand j'ouvre son interface en haut a gauche il y a un bouton Downloader

je clic dessus on peut sélectionné téléchargement complé mais une foi télécharger 

quand je reviens sur la première interface je ne vois pas ce que j'ai télécharger comment

faut il faire pour pouvoir avoir ce que j'ai télécharger dans l'arborésense de la première 

interface ? je sais pas si j'ai été très claire !!!

Merci de votre aide

J'ai une clé USB Verbatine 32 GO

Je l'ai formater en NTFS sen aucune partition

J'ai installer grudd4dos avec RMPrepUSB pui j'ai copier Easy2Boot_v1.17

Puis j'ai ajouter dans le dossier ISO/WINPE/

WinPEx86 bits,isope01

WINPE7x64 bits,isope01

Je les ai fais avec (Win7PE_SE_2013-10-03)

voilà mon souci quand je lance le demarrage Windows monte bien lettre X mais tous ce qui correspond a Y ne monte pas resulta pas de logiciel portable et pas de pilote que j'ai intergrer

comment pourrais -je faire pour faire monter en Y

J'ai regarder plusieurs tutos mais j'avoue que je ne comprend pas vraiment quel fichier je doix modifier j'ai essayer de modifier le fichier unattend,xml mais rien a part qu'il se réinitialise a chaque démarrage

Ma cle USB et reconnu dans l'explorateur Windows comme un supports de stockage amovible

et mon bios en détection AUTO

Merci de votre aide  

I have been developing wimlib, which is WIM library similar to Microsoft's WIMGAPI.  It comes with an ImageX tool similar to Microsoft's imagex.exe.  Previously, wimlib has only been available on UNIX (mainly Linux).  However, I have just released version 1.3.0, which comes with support for Windows.

wimlib is free and open source software (GPLv3+) and does not depend on Microsoft's wimgapi.dll, unlike some other tools that have been released.  You can simply download my ZIP file, which is under 2 MB, and have an ImageX implementation ready to use on Windows Vista, 7, or 8.

wimlib for Windows comes with an ImageX implementation that supports the following subcommands, which are similar to but not always exactly the same as the subcommands to Microsoft's ImageX:

imagex append - Append a directory tree to a WIM file as a new image

imagex apply - Apply a WIM image to a directory or drive

imagex capture - Create a new WIM file from a directory

imagex delete - Delete an image from a WIM image

imagex dir - List files contained in a WIM image

imagex export - Export an image from one WIM file to another

imagex info - Display information about a WIM image, or change image names/descriptions

imagex join - Join the parts of a split WIM into the original standalone WIM

imagex optimize - Remove wasted space in a WIM

imagex split - Split a WIM into parts

Additional notes:

- XPRESS and LZX compression are fully supported.  The XPRESS compressor is better than Microsoft's, while the LZX compressor is almost as good as Microsoft's.  Compression is done with multiple threads by default, so this should make it much faster to create WIM files.

- Capturing and restoring alternate data streams, security descriptors, reparse points, and file attributes is supported and on Windows is done by default.  In principle you should be able to back up and restore an entire Windows operating system, although I have not yet tried this with the Windows version.  Creating Windows PE images should work even if this doesn't, though.

- Mounting WIM images is supported on UNIX but not on Windows.  This is also the only way to modify the files contained in a WIM image, so this means that you cannot add or remove files from a WIM image with the Windows version.  (I realize this may be a significant limitation.)

- I think you have to run wimlib's imagex.exe as an Administrator because it requests permission to read files' SACLs (System Access Control List), which requires the SE_SECURITY_NAME privilege, which only the administrator account has.  I may be able to remove this restriction if there is interest.

- The ZIP file containing the Windows binaries comes with the UNIX man pages for imagex in the 'doc' subdirectory, converted to plain text.

- wimlib's 'imagex.exe' currently cannot be used as a "drop-in" replacement for Microsoft's 'imagex.exe' because the command-line syntax is different and in some cases the supported options and subcommands differ.  It should be apparent that they are quite similar, though.

WARNING:  The Windows version of wimlib and imagex (and even the UNIX version, to some extent) is experimental.  You use it at your own risk.  If you find bugs or have any suggestions, please let me know, but I am NOT responsible if something goes wrong.

The download link for the Windows binaries, which should work on both 32 and 64-bit versions of Windows Vista, 7, and 8, is:

http://downloads.sourceforge.net/wimlib/wimlib-1.3.0-windows-i686-bin.zip

Note: The ZIP file also contains precompiled DLLs for libiconv, libxml2, and winpthreads.  These are also free and open source libraries, and you can easily obtain their source code if desired.

Note:  I have not released 64-bit binaries yet, although I can do this if there is interest.

The main SourceForge page for wimlib is http://sourceforge.net/projects/wimlib (go there if you want the source code).

In the (perhaps unlikely) event that you would like to write your own program that uses my API, the documentation for wimlib's API is at http://wimlib.sourceforge.net.

Chapter 2 - Creating a new app script

• Text Editors
• Internal wb Tools

[main]

Title=Notepad++

Description=Open source text editor

Selected=True

Level=5

Version=1

• Title is the name that will be displayed on the WinBuilder script list - it doesn't need to be the same as the filename.
• Description is a small explanation to provide more informations.
• Selected value is a way to specify if whether this script should run or not when you build the project.
• Level - each project will execute scripts based on the number of their level (1..10), app scripts use 5 as default
• Version is the current version of this script to help other users to know when a new version is available.

• WinBuilder.exe - the script engine will add variables containing information about your machine
• WinBuilder.ini [variables] - variables placed here will affect all projects and all scripts
• script.project [variables] - variables on the project file will be available on all scripts inside the project
• Test.script [variables] - variables inside the script will be available inside the script

[variables]

%ProgramTitle%=Notepad++

%ProgramEXE%=notepad++.exe

%ProgramFolder%=Notepad++

• %ProgramTitle% is the variable that will define how the program should be named (used on shortcut title)
• %ProgramEXE% will point to the filename that will be launched by the shortcut
• %ProgramFolder% is the folder name where your program files will be placed

[process]

Add_Shortcut

unpack

• [Type] - can be Desktop, StartMenu, QuickLaunch, SendTo
• [Folder] - fill this value if you want to force the shortcut to be placed on a specific folder
• [FullFilename] - this switch is used if you want to create a shortcut different of %program_exe%
• [Title] - set your own title for this shortcut
• [Work folder] - decide the value for the work folder
• [Parameters] - if you want to launch the exe with command line parameters, write them here
• [Iconfile] - you can specify what the icon to be used on the shortcut
• [StartMode] - Value to set how the window of the launched program should be. 1=Show; 2=Show_Minimized; 3=Show_Maximized; 4=Hide

Parameter		   Replace With	   Read as in english



,						  #$c				Commma

space					  #$s				Space

"						  #$q				Quote

%						  #$p				Percentage

break line				 #$x			   Starts a new line

unpack,AnotherFolder

unpack,folder,myCompressedFile.zip

unpack,folder,asquared_free.exe,"-y"

By simply copying bootable ISOs and images to the Easy2Boot USB Flash drive you can then boot from the USB drive and boot directly from those ISOs or images. No menu editing or other fiddling about required. No special s/w needed. Just copy your payload files and go! Watch the YouTube video below. It even shows how to boot directly from linux ISO files with persistence!

Easy2Boot should work with 99% of all linux ISOs (even those that need cheat codes or don't have any cheat codes for ISO booting and so could not be booted by grub4dos before Easy2Boot!) and many other live CD images such as BartPE, Win7PE, WIn8PE, Hirens, UBCD4Win, UBCD, Plop!, memdisk, etc. etc. . Also, works with XP and later Windows install ISOs too. Apart from Windows ISO files, the action taken is based on the file extension. For instance, a Hirens ISO will boot more successfully if you rename the extension to .isowinvH.

You can also add a .mnu file for the more difficult ISOs/images (sample .mnu files are included in the \docs folder of the download and more can be downloaded from the Easy2Boot Tutorial page - each file contains instructions). More information can be found on the RMPrepUSB site Easy2Boot V1 page. This also has instructions on how to make a grub4dos bootable USB flash drive using RMPrepUSB (though you can use bootice or grubinst or anything else you like).

 Easy2Boot does not care about the version or name of the linux ISOs (unless you use a .mnu file) and so will work with linux ISOs that come out in the future.

I would like to ask for volunteers to test the Windows install from ISO part of Easy2Boot V1 BETA and feedback with suggestions (or bugs!).

Easy2Boot is designed for a FAT32 USB Flash drive (the first partition in the partition table must contain Easy2Boot files) and to work on real systems (Windows installs and some ISOs don't work using VMs) and so must be tested on real systems. You can use Easy2Boot V1 from a USB hard disk too (FAT32 or NTFS), but to use the Windows Install ISOs, you also need to plug in a USB flash drive which contains two small files in the root of the drive - see the web page for more info.

Standard MS Windows Install ISOs can  currently be added to an Easy2Boot USB flash drive and they should automatically work (as long as the filename is correct): See HERE for a list of Windows ISOs that should 'just work'. You can have 16 or more Windows install ISOs on the same USB drive and they will all work.

If you always want to use the same Win 8/SVR2012 Product Keys, you can edit the appropriate grub4dos menu in the \grub folder to add in your Product Keys.

and

after copy it

paste by right click by cursor.

copy director with all data ??????

I want to install PC's remotely by booting over PXE +FTPT from .ISO files *netboot, nfsroot*.

i have running, working and configured Synology diskstation with PXE, DHCP boot.

I can Load and install Ubuntu or SuSe...., but it require connection to internet, also I can load of course .iso to memdisk, but some clients can have 512RAM so than I cant use memdisk.

This lines in txt.cfg - MENU for PXE boot works well as I described.
 

LABEL XP
KERNEL memdisk
APPEND raw iso initrd=images/WindowsXPSP3.iso
TEXT HELP
    Windows XP SP3 install
ENDTEXT

label Ubuntu 13.1 WWW OK
kernel ubuntu-installer/i386/linux
append vga=788 initrd=ubuntu-installer/i386/initrd.gz
 

LABEL Parition Magic OK
KERNEL memdisk
APPEND iso initrd=images/pmagic_2013_05_01.iso
TEXT HELP
    Parition Magic
ENDTEXT
 

LABEL Netlinux.boo SuSee
kernel linux.boo
append shtowopts install=/suse-net/net panic=20 ip=dhcp initrd=initrd.boo
TEXT HELP
    UNIVERSAL BOOT
ENDTEXT
 

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

I need to load such Initrd., so it can accept NFS /netboot/ in fact TFTP as a source.

Theoreticly I need to explain to LOADER that TFT is like CD-ROM cause from principe it should work like that.

I had read MAN pages, forums but no one lead to use the .iso file directly. I had also try to unpack /.iso file

but also w/o result - using FTPT as a source/repository.

Here some combinations which I tried - some of them are mismatched, cause mixing of SuSe ubuntu and who knows what distribution - it seems they use little different paramteters. For example seems that SuSe accept "install=" and Ubuntu "nfsroot=" - maybe I'm wrong so thats why it does not work... anyway I try many combinations with result of booting to some level of instalation who does not accept repository,iso.. /nfs...

- UNPACKED IMAGE FILES -

LABEL UBUNTU 13.1 LIVE
kernel ubuntu-installer/casper/vmlinuz
append INSTALL=192.168.2.150:/volume1/install/PXE/ubuntu-installer panic=20 netboot=nfs boot=casper ip=dhcp

** alternative for suse

kernel suse-installer/linux
install=nfsroot initrd=suse-installer/boot/i386/loader/initrd ramdisk_size=512000 ramdisk_blocksize=4096 root=/dev/nfs rw nfsroot=192.168.2.150:/volume1/install/PXE/suse-installer panic=20 ip=dhcp
**

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

Here simple example as it should work :-D   //of course it does not work but it explain maybe more than prev. lines.

LABEL SUSE KDE-Live
kernel linux
APPEND iso raw initrd nfsroot=192.168.2.150:/volume1/install/PXE/images/openSUSE-13.1-KDE-Live-i686.iso

Anybody have that issue solved ?

i need correctly wroten lines in txt.cfg and probably updated kernel and initrd - not original from liveCD or NETBOOT. //Cause netboot use www repository :-)

RMPrepUSB is similar to the HP Format utility, but much more flexible and should be better at creating a USB Flash memory drive that will boot on most systems successfully. See below for details of these utilities. It is mainly a 'roll-you-own' tool for people who want to make or modify a multiboot/multipass USB drive. Over 14 languages are supported. See here for more details or watch some YouTube Videos.

What are the utilities?
RMPrepUSB's main components are RMPrepUSB.exe and RMPartUSB.exe.

RMPartUSB.exe - a command line Windows app used by RMPrepUSB - allows you to partition and format any USB storage device as FAT16, FAT32 or NTFS from Windows XP,2K3,Vista,Win7,2K8. Can be used in scripts/batch files.

RMPrepUSB.exe - a user friendly front-end Windows x86 (32-bit, 64-bit compatible) GUI for the command line tool RMPartUSB.exe. When you set the options in RMPrepUSb and click the Prepare Drive button, it will display the command line that it is going to use to run RMPartUSB and then run RMPartUSB. If you have selected a folder, it will then copy the entire contents of that folder over to the new partition when RMPartUSB has finished formatting the USB Flash Drive (UFD). You can then use the Eject button and disconnect the UFD when you have finished.

Details on RMPartUSB and RMPrepUSB





RMPrepUSB calls RMPartUSB which makes a single user partition of any size and is primarily intended for USB Flash Drive (UFD) memory sticks although it can be used on USB hard drives to create a single partition. The utility also places boot code on the USB device for either XP/WinPEv1 (ntldr), Vista/WinPEv2/Win7 (bootmgr), MS-DOS (io.sys) or FreeDos (kernel.sys). RMPartUSB does not place any files on the UFD - you must copy these over yourself or set the option in RMPrepUSB to copy over the contents of a folder of your choice.

There are some options that allow the UFD to boot either as a super-floppy (ZIP) drive or a Fixed disk (HDD). Thus DOS or FreeDos can boot from a UFD as either the A: drive or the C: drive depending on how you partition and format it using the options available (and if your BIOS supports booting as Floppy or ZIP).

Please visit the home website for over 80 tutorials.

RMPrepUSB and RMPartUSB are free for private use only for anyone. Commercial use however is forbidden and you need to contact RM for licensing costs if you wish to use it or re-distribute it as part of a commercial solution - contact support@rm.com and ask for Classroom Technolgies - RMPrepUSB licensing department.

DOWNLOAD

Visit www.rmprepusb.com Beta Downloads page for latest version (recommended)

Version 2.1.648 is available here
For users who have Google sites blocked by their ISP, download v2.1.620 from MediaFire here.

RMPrepUSB Version History

I know xBoot supports *.ISO files, but is there a way to use bootable *.img file instead of *.ISO files.

Thank you for your help.

I've been using Symantec Ghost over a home grown PE for years.  I ran across this somewhere and gave it a try.  It actually seems pretty decent.

I was wondering if anyone else had any real world experience with it?  Successfully restored from a hosed OS or hardware failure?

It also comes with a PE generator, the basics are there in a PE.ISO that it has from the start, it adds what I assume are the missing MS licensed pieces and creates a stripped down PE that can run it's own software for recovery.  I'd love to add this to my own PE but don't know where to start, it won't run from another version of PE, so things are obviously missing that it needs.  I'd like to add it to my own PE to get the fuller assortment of tools and a desktop environment.

• I want a RAM disk to be automatically created and formatted when Windows starts up.
  
  
  Spoiler

  You could for example use Windows Scheduler (look in Control Panel) to schedule a command to run at system startup. Command should be something like:
  
  imdisk -a -s 400M -m R: -p "/fs:ntfs /q /y"
  
  This will create a 400 MB RAM disk as drive R: and format it as NTFS during system startup.
  
  
   
• I want my auto-created RAM disk to be pre-loaded with a disk image file.
  
  
  Spoiler

  Change command line above and remove -p parameter (no need to format in this case) and include -f parameter with an image file name. For example:
  
  imdisk -a -t vm -f C:\ramdisk.img -m R:
  
  This will create a RAM disk and load contents of C:\ramdisk.img onto it.
  
  
   
• Image file for my auto-created RAM disk is small and I want RAM disk expanded to larger size automatically.
  
  
  Spoiler

  Just add another command to be scheduled:
  
  imdisk -e -s 400M -m R:
  
  This will add 400 MB to RAM disk drive R:
  
  You could of course put both commands in a batch file and schedule that batch file instead. This will make sure that they run in correct order:
  
  imdisk -a -t vm -f C:\ramdisk.img -m R:
  
  imdisk -e -s 400M -m R:
  
  
   
• How do I save a RAM disk as a disk image file from command line?
  
  
  Spoiler

  rawcopy -mld \\.\R: C:\ramdisk.img
  
  The rawcopy program is available on web site: http://www.ltr-data.se/opencode.html
  
  
   
• I want a RAM disk that uses memory above 4 GB in 32 bit Windows. Can ImDisk do that?
  
  
  Spoiler

  If your 32 bit Windows version supports memory access above 4 GB through address window extension (AWE) and with physical address extension (PAE) turned on, it could be done through an additional memory allocation driver called awealloc.
  
  Create the RAM disk with the awe option (schedule this command with Windows Scheduler if you want it to happen automatically at system startup):
  
  imdisk -a -s 400M -o awe -m R: -p "/fs:ntfs /q /y"
  
  This will ask awealloc driver to allocate 400 MB and then create a RAM disk drive R: within that memory and format it with NTFS. The 400 MB will primarily be allocated from as high memory addresses as possible, but parts of it could be allocated at lower addresses if not enough memory is free or otherwise accessible at high ranges. Check Windows Event Log to see error messages during memory allocation.
  
  
   
• When I delete files from my RAM disk memory still seems to be used. What is wrong?
  
  
  Spoiler

  ImDisk allocates memory for whole of RAM disk when RAM disk is created. Due to the way memory management works in Windows it might look like memory is not allocated until you put files on your RAM disk, but that is actually just a delay in committing memory pages and not a feature of ImDisk. When you delete files there is no way for ImDisk to tell Windows to "decommit" pages because all of RAM disk is allocated in one chunk.
  
  Some of these problems could be partially solved with awealloc driver as discussed above, because with awealloc not all of RAM disk memory needs to be in virtual address space at all times. But apart from that, there is sadly no good solution in sight as it looks right now.
  
  
   
• I would like to mount a vhd file from Microsoft Virtual PC, Virtual Server, Hyper-V etc. Can ImDisk do that?
  
  
  Spoiler

  Fixed size vhd files could be mounted without any special tweaks. Dynamically sized vhd files could be mounted through proxy mode with a program called devio. Download devio here: http://www.ltr-data.se/files/devio.exe
  
  Open a command prompt and type:
  
  devio shm:vhd1 C:\harddisk.vhd
  
  It will automatically find out that it is a vhd file and select first partition. There are various parameters available to devio if you want to mount as plain image or want another partition from the image file.
  
  Then, create the virtual disk:
  
  imdisk -a -t proxy -o shm -f vhd1 -m V:
  
  Make sure you leave devio running while virtual disk is mounted. You will get all sorts of disk I/O error messages and trouble if you kill it before dismounting the virtual disk. The devio process will automatically exit when you dismount the virtual disk.
  
  imdisk -d -m V:
  
  You can change devio command line to open image file in read-only mode:
  
  devio -r shm:vhd1 C:\harddisk.vhd
  
  The vhd1 name here is just an example. It is the name of shared memory and synchronization objects used to communicate between ImDIsk and devio. You can use any name you want but remember that it needs to be unique in case you mount many files simultanously.
  
  
   
• I would like to mount an image file of another format, for example vmdk or vdi. Could ImDisk do that?
  
  
  Spoiler

  ImDisk can not mount these formats natively, but it can interact with the DiscUtils library and that way mount them. You need to download a program called DiscUtilsDevio.
  Download DiscUtilsDevio.exe, ImDiskNet.dll and DevioNet.dll.
  
  You also need DiscUtils.dll, it is available on DiscUtils project pages or here: DiscUtils.dll
  
  Put downloaded exe and dlll files in same directory. Please note that .NET Framework 4.0 is needed for this to work.
  
  Open a command prompt, change to directory where you put DiscUtilsDevio.exe and DiscUtils.dll and type:
  
  DiscUtilsDevio /mount=V: /filename=C:\harddisk.vdi
  
  It will automatically find out that it is a vdi file and select first partition. There are various parameters available to DiscUtilsDevio if you want to mount as plain image or want another partition from the image file.
  
  Make sure you leave DiscUtilsDevio running while virtual disk is mounted. You will get all sorts of disk I/O error messages and trouble if you kill it before dismounting the virtual disk. The DiscUtilsDevio process will automatically exit when you dismount the virtual disk.
  
  imdisk -d -m V:
  
  You can change DiscUtilsDevio command line to open image file in read-only mode:
  
  DiscUtilsDevio /mount=V: /filename=C:\harddisk.vdi /readonly
  
  
   
• I try to mount an image file named something.bin and it does not work. What could be wrong?
  
  
  Spoiler

  If the image file has .bin suffix it is automatically treated as a CD/DVD image. If it is actually a disk volume image try to manually select "Harddisk volume" in Control Panel applet or specify -o hd at command line.
  
  
   
• My image file has a master boot record with partition table. When I mount it using Control Panel applet it asks me which partition to mount, but this does not seem to work from command line.
  
  
  Spoiler

  You need to add -v partitionnumber to imdisk.exe command line to automatically find offset etc for mounting a specific partition with image file. You could also use the multipurpose -b switch with -b auto to mount first specified partition in partition table. The -b auto argument also works with other kind of known image file formats with headers that must be skipped to find the actual disk data.
  
  
   
• I would like to mount a virtual disk to a subdirectory on my hard disk instead of using a drive letter. How to do that?
  
  
  Spoiler

  The subdirectory where the virtual disk will be mounted need to be on an NTFS volume and it needs to be empty (not even any hidden files or directories in it). This feature also requires Windows 2000 or later, it does not work on Windows NT 3.51 or 4.0.
  
  First, create an empty directory where you want to mount your virtual disk:
  
  md C:\vdisk
  
  Then, mount your virtual disk. In this example we use type "vm" to copy image file C:vdisk.img to memory and thus create a RAM disk.
  
  imdisk -a -t vm -f C:\vdisk.img -m C:\vdisk
  
  Now C:vdisk will point to your ImDisk drive, for example DeviceImDisk0 (drive number could be other than 0 if you have other virtual disks mounted, correct drive number will be shown on console).
  
  When you want to dismount, type:
  
  imdisk -d -m C:\vdisk
  
  This will remove the reparse point at C:vdisk and turn it back to an empty directory. If you instead type for example imdisk -d -u 0 you will just dismount the virtual disk but not remove the reparse point. In this case C:vdisk directory will automatically point to the next ImDisk drive you create, and you do not need to specify that directory as mount point in that case.
  
  imdisk -a -t vm -f C:\vdisk.img
  
  
   
• When I try to use the rawcopy program to save disk contents as image file, I get corrupt image files that cannot be mounted later. What is wrong?
  
  
  Spoiler

  To make sure that filesystem drivers or filesystem filter drivers do not interfere with rawcopy, use the -d flag:
  
  rawcopy -mld \\.\R: C:\ramdisk.img
  
  
   
• I would like to script a silent install of ImDisk, but when I try imdiskinst.exe -y it still shows a message box at end of setup. Is there a way to avoid all kind of user interaction during setup?
  
  
  Spoiler

  If you are calling imdiskinst.exe from a script or similar, define the environment variable IMDISK_SILENT_SETUP to the value of 1 before running imdiskinst.exe. This makes the install script skip message boxes and similar.
  
  For completely non-interactive setup, for example included in other setup packages, it is recommended that you extract the contents of imdiskinst.exe (use 7-zip) to a temporary setup directory. Then, run rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 path-to-setup-filesimdisk.inf or similar.
  
  It is also possible to edit install.cmd in the setup package and remove all calls to msgbox.exe utility. That utility is only used to display message boxes.
  
  
   
• Is there any step-by-step guide to creating a RAM disk at system startup?
  
  
  Spoiler

  Yes, "Bad_Machine" created one here: http://thessdreview....ftware/1834.htm

(SBJ) Password for "Backup & Recovery" and "Rescue Kit" tools?

  Do I have the qualification for receiving gratis support about the following
contents?
  If so, how can I avoid the following problem and make them operable?


  I have "br_free.msi" and "rk_free.exe" obtained by the step shown below.

Paragon Backup & Recovery, version 10.1.19.16240 (22.11.12) Free

Paragon Rescue Kit Free Edition (2011-04-28 15:03:47)


-------------------------------------------------------------------------
  Some plural bootable CDs should be integrated into a single bootable CD
for the improvement of operational and economic efficiency.
-------------------------------------------------------------------------

  So, I tried to integrate the above plural I.S.O. files into a single I.S.O. file
with XBOOT shown below.

XBOOT
https://sites.google.com/site/shamurxboot/
Download - XBOOT
https://sites.google.com/site/shamurxboot/download
-> XBootv1.0beta14.zip (5,516,740 bytes)


  I burned the above integrated I.S.O. file to a CD (up to 700MB) and tried it.
  But both of "Backup & Recovery" and "Rescue Kit" tools have been inoperable
on some kind of PC.
  Because "Password" dialog box was poped up on the screen and any operations
were rejected.

PC: Toshiba dynabook EX/522PDET3 (OS: Windows XP HE V2002 SP3 32bit)
dynabook EX Series
ttp://dynabook.com/pc/catalog/dynabook/030912ex/spec.htm


  I confirmed for each of the nonintegrated bootable CDs on the above same PC.
Both of "Backup & Recovery" CD and "Rescue Kit" CD are operable normally.

  I confirmed for a different kind of PC with the above integrated bootable CD.
"Backup & Recovery" and "Rescue Kit" CD is operable normally.


  Both of "Backup & Recovery" and "Rescue Kit" tools have been inoperable.
And the other tools are operable normally.
  How can I avoid the problem and make the Paragon tools operable?

-------------------------------------------------------------------------
  Some plural bootable CDs should be integrated into a single bootable CD
for the improvement of operational and economic efficiency.
-------------------------------------------------------------------------

  I tried to integrate the following plural I.S.O. files into a single I.S.O. file
with XBOOT.

MiniTool Partition Wizard Home Edition 7.8

AOMEI Partition Assistant Standard Edition 5.2

AOMEI Backupper 1.6 for Windows PE

AOMEI Backupper 1.6 for Linux

EaseUS Todo Backup Free 6
(But "Agent.exe" was detected as a spyware.)

Paragon Backup & Recovery, version 10.1.19.16240 (22.11.12) Free

Paragon Rescue Kit Free Edition (2011-04-28 15:03:47)


  I burned the above integrated I.S.O. file to a CD (up to 700MB).
  I confirmed for the above integrated bootable CD on the same PC
which I had described.
  Both of "Backup & Recovery" and "Rescue Kit" tools have been inoperable.
And the other tools are operable normally.
  How can I avoid the problem and make the Paragon tools operable?

(To be continued)

- Boot DOS 7.1

- Boot FreeDOS ISOs

Currently I manage a bootable USB key that uses DOS 7.1. Recently we've been given BIOS updates in the form of ISO files that work exclusively on FreeDOS. The USB key uses DOS 7.1 for program compatibility reasons and we can't just abandon it. I know there are a bunch of different methods to multiboot but I have no real experience with any of them. So I was hoping that there was a way I can retain the existing system and add the ability to alternatively choose to boot the FreeDOS ISOs.

I saw in the tutorials about booting WinPE based ISOs but I don't know if would be the same. Unfortunately I am unable to redistribute the FreeDOS ISO files.

Oh one more thing, I need a solution that allows for business use, as this isn't for personal/home use.

Greetings all. I am new to this community so I hope I am in the right place and am asking in the right way.

I am trying to make a USB bootable windows 8.1 vhd that I can use on my work windows laptop via virtual box, then boot natively when plugged into my Mac Mini via Grub4Dos

I had created a windows to go installation which behaves exactly as I want on my Mac, but I can't use it on my work laptop (which has access to the bios disabled so I can't set it to boot) hence the need for a Virtual PC of some kind.

I created a .VDH of windows with a fixed disk.

I used RMPrepUSB to create a bootable USB with Grub4dos

I copied over the easy2boot files

I create a copied my vhd to _ISO\VPC\USBBoot.vhd

I defragged the USB and ensured all files are contiguous

Under MAINMENU folder I created a menu file ZZZF4BootVPC.MNU

in that folder I have the following:

http://techcrunch.com/2013/09/12/will-the-eye-tribe-99-eye-tracker-make-gaming-easier-or-give-you-eye-strain/

http://theeyetribe.com/

The Eye Tribe Gaze Suite on an Android

The Eye Tribe demoed live during CNET panel

I try to install xp to image with firadisk. I use floppy image and load it from grub4dos:

map --mem /firadisk.img (fd0)

map --mem /firadisk.img (fd1)

map /xp.vhd (hd0)

map --mem /setup.iso (0xff)

map --hook

chainlader (0xff)

The setup starts, but cant see the mappes image. Alsp tried to integrate firadisk driver to setup iso, but it results that the installation breaks with reboot at the beginning.

Thanks for advices.

imagex f:\sources\install.wim 5 c:

bcdboot c:\windows /s c:

bootsect /nt60 c:

powercfg -h OFF

bcdedit /set testsigning on

title Portable Win8-1.vhd - FiraDisk FILEDISK - 2.5 GB
find --set-root --ignore-floppies /Win8-1.vhd
map --heads=2 --sectors-per-track=18 --mem (md)0x800+4 (99)
map /Win8-1.vhd (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=disk,vmem=find:/Win8-1.vhd,boot;\n\0
rootnoverify (hd0,0)
chainloader /bootmgr
map --status
pause Press any key . . .

title Portable Win8-1.vhd - FiraDisk RAMDISK - 2.5 GB
find --set-root --ignore-floppies /Win8-1.vhd
map --mem /Win8-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

Now my client wants me to make it print... I did my search and found some topics:

• http://reboot.pro/topic/16803-net-framework-v4-and-print-feature-script/
• http://reboot.pro/topic/14910-printer-and-win7pe/
• http://reboot.pro/topic/15394-need-help-to-translate-chinese-to-english-print-spooler-evolution/

but ludovici's script failed for me.

I even tried BartPE as it seems that back in 2005 they managed to get it printing but unfortunately it was only for LPT printers.

Do you guys know of any live windows capable of printing? I'm posting in Win7PE section as I've already done most of my job on this and would be the perfect solution.

Thanks!

File Name: Avira free Antivirus Update for Win8PE, LiveXP and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 28 Feb 2014
File Category: App scripts

Homepage and info:
http://www.avira.com/en/avira-free-antivirus

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://al-jo.net46.net/livexp/livexp2.html
http://aljo.comeze.com/win8pe/Win8PEguide.html

______________________________________________________________

Click here to download this file

http://hackingexposedcomputerforensicsblog.blogspot.com/2014/02/daily-blog-248-adding-winfe-image-to.html

• Install Windows 7/8/2003/2008 on a Virtual Machine ( create a disk type .vhd with fixed size )

• open a cmd as administrator and type two commands:

C:>bcdedit  -set  TESTSIGNING ON



C:>bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS

• reboot the virtual machine
• Download and Install WinAoE Driver as Storage Controller
• Download and Install CCBoot Client without options
• Shutdown Virtual Machine

• Install a DHCP Server with option bootfilename grldr
• Install a TFTP Server and set tftp-root folder
• Download grub4dos and extract 'grldr' and 'menu.lst' files to the tftp-root folder
• Edit menu.lst file only with this content:

title === MENU BOOTS ===

()

title

()



title Windows 7 Diskless

map --mem (pd)/ipxe.iso (0xff)

map --hook

chainloader (0xff)

• Create a text file 'conf.ipxe' with this content:

#!ipxe

dhcp net0

set keep-san 1

sanboot aoe:e0.0

• Download ipxe.iso and with UltraISO, open the ipxe.iso with UltraISO and edit ISOLINUX.CFG with this content:

SAY iPXE ISO boot image

TIMEOUT 30

DEFAULT ipxe.lkrn

LABEL ipxe.lkrn

KERNEL ipxe.krn

INITRD conf.ipxe

• Update the ISOLINUX.CFG on UltraISO with new content
• Drag the file 'conf.ipxe' to inside UltraISO and save the file.
• Put ipxe.iso on the tftp-root folder
• Start DHCP Server
• Start TFTP Server
• Download and install WinPCAP and vBlade Target System ( AoE ) and export the target of .vhd.
• Open vblade from Icon on Program Group
• First find the Device Name of your Network Card with bogus caracters (xxx).

vblade -b 65 0 0 xxx “d:path_to_you_vhdwindows.vhd”

• after copy and paste the Device{value}

vblade -b 65 0 0 “Device{value}” “d:path_to_you_vhdwindows.vhd”   <ENTER>

• Ready ! Boot one machine by LAN Boot, or create a VirtualBox/Vmware Virtual Machine without Disks !
• You can boot a lot of Machines creating a specific ipxe.iso for each one, dont forget to edit 'conf.ipxe' with diferent targets ( e0.0, e0.1, e0.01), create respective ipxe-e0.0.iso for each workstation, add the menu.lst entry too for each ipxe-e0.x.iso, export each .vhd with vblade changing slots ( 0 1 , 0 2 etc..)

Using the current versions of Easy2Boot (1.25_DPMS) and RMPrepUSB (2.1.716).  create the USB stick (4gb) have added many tools that all work fine.  Have CDs and have made iso of each for 23 and 64bit windows 7 erd with D.A.R.T. incorporated.

The CDs work fine but when I boot the USB and select the proper version of erd after it boots it does not detect the installed OS  :/

After its up I can use the DART tools and see the local drive and files but if its not detected at the beginning many of the tools will not work (like the locksmith, reg editor and such)

Can anyone help me out?
Thanks
 

IntegrateDrv /usbboot /driver=..\Drivers\Wait4UFD /target=D:\XPSOURCE\

title Continue GUI-mode XP Setup on XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP3_1210W.iso
map /XP3_1210W.iso (0xff)
map --rd-size=2048
map --mem (rd)+4 (0x55)
map --hook
write (0x55) #!GRUB4DOS\x00v=1\x00/XP3_1210W.iso\x00\xff\x00
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --rehook
root (hd0,0)
chainloader /ntldr

title Start - TXT-mode XP Setup on XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP3_1210W.iso
map /XP3_1210W.iso (0xff)
map --rd-size=2048
map --mem (rd)+4 (0x55)
map --e820cycles=0
map --hook
write (0x55) #!GRUB4DOS\x00v=1\x00/XP3_1210W.iso\x00\xff\x00
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --e820cycles=0
map --rehook
chainloader (0xff)

title Boot Windows XP from Image - XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP-1.vhd
map /XP-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr

title Start - TXT-mode XP Setup on XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --e820cycles=0
map --hook
chainloader /ntldr

title Boot Windows XP from Image - XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP-1.vhd
map /XP-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr

I used winbuilder_2013.09.01 to create Win7 live CD, it was my first time using this program and it's absolutely amazing. It did everything and I've got a CD Live that works perfectly.

But I need to use it on a laptop without optical disc reader, so I have to make a usb drive version of Win7 live.

I read the forum, but I still have no clue about how to do it.

Thank you in advance.

I've used the xBOOT program to create a multi-boot disk of 8 GB that has Hiren's Boot CD 12.0, Ubuntu 12.04 and Windows 7 (all versions) installation successfully. After testing on my VMWare machine, this was successful and all seemed to work fine.

Now I wanted to add a Windows XP Pro SP2 install to it. I started Xboot again and tried to add Windows XP to it. (Note: possible as suggesstion, it did not showed what was already on the disk). I did not created a new Bootloader, but decided to edit the current one (Syslinux).

This caused two issues.

1: When scanning from Grub with the PXE scan, it's scanning 578 MB, which is the ISO size. But it scans every 10 seconds only 8 MB. Ubuntu and Windows 7 iso is much bigger (Win 7 being 3.3 GB), but they start up immediately.

2: As this takes already quite long, when the installation does proceed and tries to start the installation, I get the STOP error 0x0000007B, probably because it receives a time-out to access the ISO.

Am I doing something wrong here?

I unchecked them all when i built my PE the first time, then i simply rechecked some of the start menu pins i wanted and they refuse to show up...

whats the secret!?!?

This is with the latest Win7pe SE

Thanks!

http://hackingexposedcomputerforensicsblog.blogspot.com/2014/02/daily-blog-242-how-to-build-winfe-to.html

I may have said that WinFE is nearly the perfect forensic boot system before, but actually, when WinFE is on a multiboot media, I would have to change it to the multiboot thumbdrive with WinFE being the perfect forensic boot system.  Very very cool.

e.g. under Windows or linux, we can list these files:

AA

bb

Cc

CCC.txt

ddd.TXT

ANTIVIRUS

ANTIVIRU

but the same files are listed by grub4dos in the console as:

aa

bb

Cc

ccc.txt

ddd.txt

ANTIVIRUS

antiviru

It turns out this is because grub4dos does not support VFAT. This was a special enhancement in NT4 and later OS's which would allow you to have either all uppercase or all lowercase filenames, extension names and folder names as long as they were 8.3 in format. This was before long file names (LFN) was introduced.  Cc and ANTIVIRUS are displayed correctly because they are either not 8.3 or they are of mixed case in the filename base part.

Byte 12 in the directory entry can have two bits set in VFAT to indicate all lower case:

#define LCASE_BASE        0x08            // filename base in lower case
#define LCASE_EXT         0x10            // filename extension in lower case

I have proposed a fix for this to chenall - see issue log here.

If grub4dos scripting is used to obtain the names of files and folders using current versions, the case will be incorrect and may fail if the path+filename is used to automatically specify a kernel parameter cheat code.

At the moment, a path might appear in Windows on a FAT32 drive as \_ISO\MAINMENU\Ubuntu.iso.

But if you list this under grub4dos, it will be listed as \_iso\mainmenu\Ubuntu.iso.

This may cause problems if you use the path in a kernel parameter when booting to linux:

e.g.

kernel /vmlinuz  from=/_ISO/MAINMENU/Ubuntu.iso

or

kernel /vmlinuz  from=/_iso/mainmenu/ubuntu.iso

or
kernel /vmlinuz  from=/_ISO/MAINMENU/UBUNTU.ISO

Which is correct?

Well it would depend on whether that particular distro of linux (at that boot stage) is case-sensitive AND if it used FAT or VFAT for directory name interpretation.

As most people would see the path as \_ISO\MAINMENU\Ubuntu.iso (in Windows Explorer) or /_ISO/MAINMENU/Ubuntu.iso (in linux), most people would use the same case when constructing a menu.lst file. Has anyone found that they needed to specify all lowercase or all capital letters with grub4dos+linux in order to get something to work correctly? Of course, the folders and filename would have to be 8.3 and all uppercase to show the problem.

I don't think that changing grub4dos to correctly display VFAT filenames correctly would cause any problems.

I have a 32g usb and have got most of my payloads working just fine with Steve's excellent tutorials and reading around here on this forum, thanks.

My problem is I can NOT get kon-boot to work from my usb.

I originally worked through other issues where my hiren's stuff would not detect my HDDs at all. That was all fixed with settings in my bios with IDE, legacy and even took out boot from CD/DVD and USB to boot first. I just hit F10 on my intel MOBO and now all my Hiren's utils work, DOS, etc.

I went through Steve's tutorial on the RMPrepUSB site to a tee, but kon-boot won't work.

What I get after the menu selection is just a black screen that is stuck. I do see the first couple of commands go by, then I'm dead in the water. I originally thought this was due to the USB not seeing all my HDD sata drives, but now I have the other tools seeing them just fine, like the partition tools in the DOS utils.

My drive where my Windows 7 install is Loc 0(Chan 0, Target 0, Lun 0), Steve, wondering based on that if I need to modify your example menu list file for that???

I've tried with kon-boot USB img and the Kon Floppy img, but no luck. I also tried the example in your tutorial included from this site, but no luck either.

Can someone please help me? not that I really have to have that tool working, but it's driving me crazy and now I have to make it work.

Thanks!

http://reboot.pro/topic/18488-tiny-pxe-server/

http://reboot.pro/topic/18962-bug-reports-requests-howtos-about-tiny-pxe-server/

Thanks to erwan.l for making Tiny PXE Server and for help in using ipxe  

Info on iPXE -  http://ipxe.org/start

The Mini Windows VHD's of 1.2 - 2 GB are loaded from Network into RAMDISK and were made according to

http://reboot.pro/topic/18547-vhd-xp-setup-install-xp-in-vhd/

http://reboot.pro/topic/18657-vhd-xp-compact-make-mini-xp/

http://reboot.pro/topic/18593-vhd-w7-compact-make-mini-7/

http://reboot.pro/topic/18467-vhd-w8-compact-make-mini-8/

After booting via iPXE with the server then in iPXE Menu we can select grub4dos option and make use of these working entries in menu.lst

Loading ISO or VHD into RAMDISK is going with a speed of about 500 MB/min which corresponds to about 65 Mbps

VHD Size max = 2 GB (abobe then file not found error)

I get a specific kind of error with each plugin I try to install:

11:03:10 [COMMAND] install imgburn
11:03:10 [RUNNING] Downloading and installing "ImgBurn", please wait..
11:03:12 [ERROR] Error while interpreting d:\Tools\WinBuilder\downloads\445-ImgBurn\main.bsh, the error message is: Sourced file: inline evaluation of: ``install();'' : Method Invocation control.write
11:03:12 [COMPLETED] "ImgBurn" was installed
11:03:34 [COMMAND] install t
11:03:34 [NOT FOUND] No results found for: t
11:03:48 [COMMAND] install cpuz
11:03:48 [RUNNING] Downloading and installing "CPUZ", please wait..
11:03:49 [ERROR] Error while interpreting d:\Tools\WinBuilder\downloads\444-CPUZ\main.bsh, the error message is: Sourced file: inline evaluation of: ``install();'' : Method Invocation control.write
11:03:49 [COMPLETED] "CPUZ" was installed
11:12:32 [COMMAND] install cd-opera
11:12:32 [RUNNING] Downloading and installing "CD-Opera", please wait..
11:12:35 [ERROR] Error while interpreting d:\Tools\WinBuilder\downloads\308-CD-Opera\main.bsh, the error message is: Sourced file: inline evaluation of: ``install();'' : Method Invocation control.write
11:12:35 [COMPLETED] "CD-Opera" was installed

Why is this happening and how can I fix it?

First many thanks to AHCI OSDev Wiki which helped me a lot to develop this patch. Keep in mind
that I am a noob when it comes down to coding and I need much assistance by code reuse. So try
not to laugh by looking at my sources. Better try to improve them!

The AHCI support can be enabled by using the additional grub menu command "ahci". We can set the
following parameters with the new command:

ahci --set-controller=CONTR --set-port=PORT [--showall] [--showselected]

Using this command searches PCI configuration space for all present AHCI controllers and
implemented ports. After setting this option every read to drive 0x80 with a block size of 32 MB
is redirected to the selected AHCI controller and port. This can speed up transfer rates if an
image file is mapped to RAM and may be loaded from an SSD. This option transfers a 32 MB block
per read command by using the ATA command READ DMA EXT. CONTR and PORT arguments start at zero,
where 0 corresponds to the 1st present AHCI controller / port found. If the option --showall is
used all AHCI controllers, ports and connected devices are displayed. If the option --showselected
is used the selected AHCI controller, port and connected device is displayed.

The AHCI support can be disabled during compile by using the configure command with the parameter
"--disable-ahci".

I increased the read block size from 8 MB to 32 MB, because this is the maximum data transfer size
we can get from an AHCI harddisk device at issuing one read command. This way we can read 65536
sectors at once. This patch was tested with a SSD connected to a SATA 300 motherboard. The normal
standard BIOS read took around 50 seconds when reading 3.5 GB to RAM with mem map. When using the
AHCI patch the same file from the same SSD was mapped to memory in around 12 seconds. I think SATA
600 should give even better results.

Pay attention that this AHCI addition is only useful if you load the images from SSD to RAM.
Loading a disk image directly or using a normal platter HDD does not increase the read speed much.
Use this patch with care on your own risk, there was no extensive testing!

Another note to the maintainers of the Grub4DOS project namely tinybit and chenall. If you think
the AHCI support is worth being implemented into the productive code, feel free to include it in
any future builds. I am not sure how many users have the need for an AHCI patch at all. Keep up
the good work on the loader!

Many thanks to all the developers and forum members of reboot pro for making it possible to boot
a full-sized Windows from RAM and harddisk image. WinvBlock and Firadisk are working like a charm!

Greets
Kai Schtrom

• sufficient RAM > 1 GB if you want to use Flash or additional extensions
• Flash installed on host system if you want to add the Flash plugin to your build
• Internet connection for fetching the Mozilla installer (optional)
• additionally my script Sumatra PDF universal if you want to equip Firefox with the ability to display PDF files

Ich arbeite mich gerade in Winbuilder ein und versuche eine Live DVD mit dem Win7PESE Paket zu erstellen. Klappt soweit auch ganz gut, aber bei dem besagten Acronis True Image Home 2012/2013 scheitert es...

Ich habe gelesen man braucht, um das einbauen zu können, die "Plus Pack" Version, ich habe aber nur die "standard" 2013er Version. Ist das auch irgendwie ohne möglich? Ich möchte ungern das nochmal kaufen...

Vielen Dank im Vorraus!

Grüße

Saw your document attached and http://inctf.in/

It seems it is only for indian students.

So, who are you competting with?

Thanks 

I'm getting this issue on a new HP laptop ( Zbook15 ) that came with an on-chip integrated Intel HD Graphics 4600 plus the discrete nVidia Quadro K1100M.
When the CPU-Integrated graphic card is enabled ( by default in BIOS settings ) I can't boot with the Win7PE bootkey I've prepared, and, if it starts, soon it become unusable. Seems like the integrated graphic card overwrites the boot env RamDisk space.

Not to say, if I disable the integrated graphic, the key works like a charm.

Someone else got the same issue? 
Some ideas and solutions?

thanks in advance.

I have collected all the required files, packed them in a 7Zip file with the 4 inf files in an inf folder and attached them to the script.
When I run the scrip I get the error:

FileCopy - Failed to copy [inf\bda.inf] to: [%BaseDir%\Target\Win8PESE\Windows\inf\bda.inf]: The system cannot find the path specified.

I really don't know where or how to put the files.

Also, the variables are empty:

[Variables]
%ProgramEXE%=
%ProgramFolder%=
%RegeditexeFolder%=

Should I be adding locations?

Something I found very strange. When I mount C:\Win8PE_SE_2013-10-03\ISO\WIM\sources\boot.wim to C:\mount , I found some files in C:\mount\windows\system32 , they are :

     winpeshl.ini , startnet.cmd , start.cmd

I know I can place the abc.exe in one of them and can be autorun. But when I boot up the win8pe , all the above 3 files are disappear.

In the mounted C:\mount\windows\system32 , the 3 files do exist. How come when boot win8pe , they disappear ?

So I can't find a way to place the abc.exe to autorun.

Please help

I'm new here, so I hope this is the right place to post.

I recently got a new Dell machine, and it has the option to make a recovery usb drive which can restore the factory image. I made a recovery drive on my 16GB USB drive. I'd like to back it up to a file somehow so I can use the drive for other things.

I tried using dd to dump the entire drive to an image file. Although this worked, it isn't ideal because the recovery data only takes 7GB out of the 16GB on my drive, but if I use dd, the backup uses a full 16GB. Also, I don't think it would be compatible with other size drives (for example if I wanted to use an 8GB drive for recovery.)

If I do something more simple like just copying the files to a backup location, the drive wouldn't be bootable. 

Can someone recommend a good way to do this? I would prefer open source/free linux tools to get the job done, but I'm open to others.

Thanks so much!

Demo explaining how its suppose to work

http://www.nytimes.com/2014/02/19/technology/wireless-system-could-offer-a-private-fast-lane.html?_r=0

will give mobile users far faster cellular network speeds, with fewer dropped phone calls and other annoyances, even in stadiums and other places where thousands of people use mobile phones at the same time.

 

• Windows version (e.g. XP, Vista, 7)
• Service pack (e.g. SP0, SP1)
• Architecture (e.g. 32-bit/64-bit)
• msv1_0.dll version (e.g. 6.1.7600.16525) along with MD5 checksum, if possible

Technical details: The script tries to locate all existing Windows installations and corresponding Windows editions as well. Thereafter, it replaces the CMP instruction responsible for password verification with a 'benign' sequence of bytes. For reverting back the changes, the process is just the opposite. The whole idea is derived from WindowsGate and Astr0baby's tutorial.

Usage:

• Install Grub4DOS. You may prefer using RMPrepUSB. Script tested with Grub4DOS v0.4.5c-2013-03-03.
• Download grubutils and copy WENV binary on the root of the boot media. Script tested with grubutils-2011-06-27.
• Copy PassPass, PassPass.bak and menu.lst on the root of the boot volume.
• Boot
• Ideally 'Autodetect' mode should be able to list out all existing Windows installation. For buggy BIOS-es, try appropriate <Disk#> and <Partition#> to 'Forcedetect' Windows installations.
• Choose either 'Patch' or 'Unpatch' respectively for disabling/re-enabling password verification.
• Reboot and boot into target Windows.

Beta Testing:

1. Download latest version of the script.
2. Backup /<Windows directory>/system32/msv1_0.dll of target installation.
3. Patch it.
4. Test whether the patch is working by being able to log on with arbitrary password.
5. Record the MD5.
6. Unpatch it.
7. Test whether whether unpatch is working by being not able to log in with all but correct password.
8. Record the MD5.
9. Compare the MD5 hashes.
10. Success is defined by the patch working at step #4, unpatch working at step #6 and hashes matching at step #9.
11. Report success/failure in the format mentioned above.

Credits:

• Wonko the sane - For ideas, code snippets, information. The script embeds his DLL version detection script.
• Ectomorph a.k.a. Damian Bakowski - For his 'unannounced' patch for 32-bit version of msv1_0.dll.
• Astr0baby - For his reversing tutorial
• Steve Si – For including support for PassPass in his wonderful tool Easy2Boot.

Download: http://www.sherlock.reboot.pro/passpass-bypass-the-password/

Development: https://code.google.com/p/g4scripts/source/list

I'm trying to setup the tftpd32 program as ftp server so that other user can deposit files to it from over the internet.

I'm able to set it up to put/get files from within the local network.

But when i try to put/get files from outside the local network, it retry few times and fail.

Do i need to setup port forwarding or any other setting to put/get files from over the internet..?

Please advice.. Thanks.

As you all know, windows supports only booting from a GPT disk in UEFI, but not in BIOS. But GPT is definitely a lot better, and cleaner. So can we do something about that?

The sequence of booting in Windows 7 (for now, later we can look at 8) : is 

MBR -> System volume (100MB) VBR ->bootmgr (with bcd) -> winload.exe -> ntoskrnl.exe -> others

We already have syslinux MBR which can setup a GPT reading MBR code... after which the VBR code need not be touched.... and then we come to bootmgr.

Is it not possible to modify bootmgr to be able to read GPT? Windows can certainly understand GPT, just that it hasn't shipped with a compatible bootloader. I checked winload.exe, and it does check for "EFI PART" GPT header signature, but dunno if it's positive or negative match it's checking for. winload might be difficult to patch, but maybe it won't mind it....?

I'm a noob at system programming, but have a fairly good idea about the process... But I defer to the experts here.... What say?

• Download rufus from here
• Plug in your USB Flash drive
• to make a Windows bootdisk (Windows XP/7) select NTFS as file system
• then click on the buttons that looks like a DVD drive, that one near to the checkbox that says "Create bootable disk usng:"
• Choose the XP ISO
• Click Start

title Gparted Gnome Partition Editor (version 0.4.5-2) 

find --set-root /gparted/live/vmlinuz1 

kernel /gparted/live/vmlinuz1 boot=live  username=casper   noswap vga=788 toram ip=frommedia 

initrd /gparted/live/initrd1.img





title GParted live

root (hd0,0)

kernel /gparted/live/vmlinuz1 boot=live config union=aufs noswap noprompt vga=788 ip=frommedia live-media-path=/live-hd bootfrom=/dev/hda4 toram=filesystem.squashfs

initrd /gparted/live/initrd1.img

#boot



#Boot to gparted

title gparted

map (hd0,0)/gparted.iso (hd32)

map --hook

chainloader (hd32)

Dose some one here Know How to do This?

This is what i Have:

title Live Windows 98
map /iso/Win98.iso (0xff) || map --mem /iso/Win98.iso (0xff)
map --hook
root (0xFF)
chainloader (0xFF)

It Boots to DOS but Fails Some how to find files

Here is the menu.lst entry in the ISO

find --set-root /BOOT.IMA
map --mem /BOOT.IMA (fd0)
map --hook
chainloader (fd0)+1
rootnoverify (fd0)
map --floppies=2

Thanks

TFTPD service edition, version 4.50 (build Nov 28 2013).

I noticed the following:

If there is multiple drives with grub4dos installed in MBR, and we want to boot the secont from the first like this

chainloader (hd1)+1

rootnoverify (hd1)

boot

Then the first disks MBR code will load, and the firsst disks menu.lst will be used.

I wanted to create a disk which can be used to boot from the available disks' MBR. How sould i do?

Thanks.

http://al-jo.net46.net/Win7PEnvda-guide.html

or here:

http://aljo.comeze.com/Win7PEnvda-guide.html

Note:

Use the form or email address here if any questions, problems with building or downloads.

Note2:

The Winbuilder.exe program is not very ”blind” friendly concerning some screen readers software,

so an assistance from a ”non blind” friend is probably needed on first Win7PE_nvda build.

Ps

From the authors of NVDA:

"it enables blind and vision impaired people to access computers running Windows"

ATTRIB.EXE      E.EX            FIND.EXE        MORE.COM        RXDINFO.RX

CHKDSK.COM      E.EXE           HIMEM.SYS       MOUSE.COM       SMARTDRV.EXE

CHOICE.COM      E.INI           KEYB.COM        MOVE.EXE        SUBST.EXE

COUNTRY.SYS     EGA.CPI         KEYBOARD.SYS    MSCDEX.EXE      SYS.COM

DELTREE.EXE     EHELP.HLP       LABEL.COM       RAMDRIVE.SYS    TREE.COM

DISPLAY.SYS     FC.EXE          MEM.EXE         REXX.EXE        XCOPY.EXE

DOSKEY.COM      FDISK.COM       MODE.COM

1] Created a bootable Windows PE disc – this must be built using the Windows 7 beta version of the Windows Automated Installation Kit (download here).

2] Copied Windows 7 files from DVD source to "(hd0,0)\Win7" directory (beta build 7000 used)

3] Booted into WinPE and identified (hd0,0) as c: drive and (hd0,1) as d: drive

4] Started diskpart and entered the following commands to create a 10GB .vhd file -

Windows Boot Manager--------------------identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}device                  partition=C:description             Windows Boot Managerlocale                  en-USinherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}default                 {f4b899d5-0f9a-11de-bffa-bb5aec14052c}resumeobject            {f4b899d4-0f9a-11de-bffa-bb5aec14052c}displayorder            {f4b899d5-0f9a-11de-bffa-bb5aec14052c}toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}timeout                 30Windows Boot Loader-------------------identifier              {f4b899d5-0f9a-11de-bffa-bb5aec14052c}device                  file=[D:]\win7.vhdpath                    \Windows\system32\winload.exedescription             Windows 7locale                  en-USinherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}recoverysequence        {f4b899d6-0f9a-11de-bffa-bb5aec14052c}recoveryenabled         Yesosdevice                file=[D:]\win7.vhdsystemroot              \Windowsresumeobject            {f4b899d4-0f9a-11de-bffa-bb5aec14052c}nx                      OptIn

]]> Fri, 14 Feb 2014 16:14:44 +0000 http://reboot.pro/topic/7453-native-boot-vhd/ http://reboot.pro/topic/16033-vhd-bcd-store-challenge-chainload-bootmgr/
The challenge is: how to change parameters of Win7 BCD Store installed on a host drive to make Bootmgr on the host chainload Bootmgr on a VHD saved on that host? Or chainload any other bootloader inside that VHD?

That way one would be able to use native Bootmgr support for all VHD types, while also overcoming OS version restrictions, since when OS is booted by a boot device located inside the VHD, it considers that drive to be a Hard Drive, and not a VHD, hence boot restrictions are lifted.

Of course, a separate challenge would be to teach a 3rd party VHD driver installed to the OS on VHD to hot-swap the virtual drive, mapped by Bootmgr, or to port native VHD drivers to Legacy OSs, but at least all Win7 versions will get supported for native boot that way without any restrictions. Keep in mind so, this is a learning challenge, not intended to bypass any OS licensing terms, but to improve your knowledge and skills in the OS Boot subject. Don't use any such method for daily computing tasks!

To help, there are several tools available to manipulate BCD Store content, some more convenient are EasyBCD and Visual BCD Editor. Of course, Virtual Hard Disk Format Specification and BCDEdit Commands for Boot Environment can help, also BCD WMI Provider Reference. Don't forget to also look through Diddy's BCDEdit Notes as well, and use Boot Configuration Data Tutorial if not satisfied. Some extra info is also found in How to edit BCD with Editor forum thread, and plentiful other sources on the web.





When playing with VHDs, one can accidentally mount 2 of them with the same OS cloned, thus prompting the system to change Disk Signature on one of the VHDs. EasyBCD can fix that with BCD Deployment feature, once you open a suitable BCD Store in it from any running OS. Another way of Fixing Disk Signature Collisions outcome, blocking OS boot from VHD, would be manually reverting back its original Sig. Keep in mind however, Disk Signature seems to be only verified when chainloading control to a bootloader inside the VHD, i.e. when treating it as a Hard disk rather than Filedisk.

Good luck with your efforts, and keep members posted on your success. ]]> Thu, 13 Feb 2014 18:14:09 +0000 http://reboot.pro/topic/16033-vhd-bcd-store-challenge-chainload-bootmgr/ http://reboot.pro/topic/19565-windows-boot-question/ Let me first tell something about history:

 

I still(!) use XP x86 as the primary platform for my developments. I do not like, when e.g. in Win7 Billy the Door always knows better than me, what I want to do.

 

For some test reasons I had to install XP x64 in a different partition. That brought no issue, in the boot menu I could do my choice.

 

For some other test reasons I had to install Win7. After that, in the boot menu, I had the choice between "previous" XP x86 and Win7.

That has been also no problem, because I usually wanted to boot XP x86, not to use x64.

 

Now, in the WinBuilder development, I wanted to check some x64 issues, and tried to reanimate the sleeping XP x64 partition.

 

I used EasyBcd 2.2 to add XP x64 to the boot menu. Result: BSOD

Then I added XP x64 manally to boot.ini. Result: othing new happened.

After some "fishing in the dark", which I cannot exactly remember (sorry !!!) , suddenly my PC booted into XP x64 !!!

 

But it was not longer possible to boot into XP x86.

 

Checking the file system, I found in my primary boot disk a new file ebcd.001 with the contents:

; This boot.ini was automatically generated by NeoSmart Technologies' BootGrabber.exe
; Use EasyBCD from http://neosmart.net/dl.php?id=1 to manage your bootloader

[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows XP on H:\" /fastdetect

And now my current procdere:

When I want to boot into XP x64, I let ebcd.001 untouched.

When I want to boot into XP x86, I rename this file to _ebcd.001.

 

Is there any way to use BCD or an editor to bring the x86 / x64 option into the boot menu?

 

For experts, here some contents:

BCD:

Spoiler

Windows Registry Editor Version 5.00

[BCD]

[BCD\Description]
"KeyName"="BCD00000000"
"System"=dword:00000001
"TreatAsSystem"=dword:00000001
"GuidCache"=hex:61,32,55,01,6f,36,cc,01,ff,26,00,00,d5,ce,cb,de,73,0d,fe,9c,90,\
  01,00,00

[BCD\Objects]

[BCD\Objects\{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}]

[BCD\Objects\{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}\Description]
"Type"=dword:20100000

[BCD\Objects\{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}\Elements]

[BCD\Objects\{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}\Elements\16000020]
"Element"=hex:01

[BCD\Objects\{1afa9c49-16ab-4a5c-901b-212802da9460}]

[BCD\Objects\{1afa9c49-16ab-4a5c-901b-212802da9460}\Description]
"Type"=dword:20200004

[BCD\Objects\{1afa9c49-16ab-4a5c-901b-212802da9460}\Elements]

[BCD\Objects\{1afa9c49-16ab-4a5c-901b-212802da9460}\Elements\14000006]
"Element"=hex(7):7b,00,37,00,65,00,61,00,32,00,65,00,31,00,61,00,63,00,2d,00,\
  32,00,65,00,36,00,31,00,2d,00,34,00,37,00,32,00,38,00,2d,00,61,00,61,00,61,\
  00,33,00,2d,00,38,00,39,00,36,00,64,00,39,00,64,00,30,00,61,00,39,00,66,00,\
  30,00,65,00,7d,00,00,00,00,00

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}]

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Description]
"Type"=dword:10200003

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements]

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\11000001]
"Element"=hex:54,cb,97,3f,62,a2,e0,11,8e,d5,cb,de,73,0d,fe,9c,00,00,00,00,01,\
  00,00,00,ee,00,00,00,00,00,00,00,03,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,01,00,00,00,c6,00,00,00,05,00,00,00,06,00,00,\
  00,00,00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,5c,00,52,00,65,00,\
  63,00,6f,00,76,00,65,00,72,00,79,00,5c,00,33,00,66,00,39,00,37,00,63,00,62,\
  00,35,00,33,00,2d,00,61,00,32,00,36,00,32,00,2d,00,31,00,31,00,65,00,30,00,\
  2d,00,38,00,65,00,64,00,35,00,2d,00,63,00,62,00,64,00,65,00,37,00,33,00,30,\
  00,64,00,66,00,65,00,39,00,63,00,5c,00,57,00,69,00,6e,00,72,00,65,00,2e,00,\
  77,00,69,00,6d,00,00,00

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000002]
"Element"="\windows\system32\winload.exe"

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000004]
"Element"="Windows Recovery Environment"

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\14000006]
"Element"=hex(7):7b,00,36,00,65,00,66,00,62,00,35,00,32,00,62,00,66,00,2d,00,\
  31,00,37,00,36,00,36,00,2d,00,34,00,31,00,64,00,62,00,2d,00,61,00,36,00,62,\
  00,33,00,2d,00,30,00,65,00,65,00,35,00,65,00,66,00,66,00,37,00,32,00,62,00,\
  64,00,37,00,7d,00,00,00,00,00

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\21000001]
"Element"=hex:54,cb,97,3f,62,a2,e0,11,8e,d5,cb,de,73,0d,fe,9c,00,00,00,00,01,\
  00,00,00,ee,00,00,00,00,00,00,00,03,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,01,00,00,00,c6,00,00,00,05,00,00,00,06,00,00,\
  00,00,00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,5c,00,52,00,65,00,\
  63,00,6f,00,76,00,65,00,72,00,79,00,5c,00,33,00,66,00,39,00,37,00,63,00,62,\
  00,35,00,33,00,2d,00,61,00,32,00,36,00,32,00,2d,00,31,00,31,00,65,00,30,00,\
  2d,00,38,00,65,00,64,00,35,00,2d,00,63,00,62,00,64,00,65,00,37,00,33,00,30,\
  00,64,00,66,00,65,00,39,00,63,00,5c,00,57,00,69,00,6e,00,72,00,65,00,2e,00,\
  77,00,69,00,6d,00,00,00

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\22000002]
"Element"="\windows"

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\25000020]
"Element"=hex:00,00,00,00,00,00,00,00

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\26000022]
"Element"=hex:01

[BCD\Objects\{3f97cb53-a262-11e0-8ed5-cbde730dfe9c}\Elements\46000010]
"Element"=hex:01

[BCD\Objects\{3f97cb54-a262-11e0-8ed5-cbde730dfe9c}]

[BCD\Objects\{3f97cb54-a262-11e0-8ed5-cbde730dfe9c}\Description]
"Type"=dword:30000000

[BCD\Objects\{3f97cb54-a262-11e0-8ed5-cbde730dfe9c}\Elements]

[BCD\Objects\{3f97cb54-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000004]
"Element"="Ramdisk Options"

[BCD\Objects\{3f97cb54-a262-11e0-8ed5-cbde730dfe9c}\Elements\31000003]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{3f97cb54-a262-11e0-8ed5-cbde730dfe9c}\Elements\32000004]
"Element"="\Recovery\3f97cb53-a262-11e0-8ed5-cbde730dfe9c\boot.sdi"

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}]

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Description]
"Type"=dword:10200003

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements]

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\11000001]
"Element"=hex:58,cb,97,3f,62,a2,e0,11,8e,d5,cb,de,73,0d,fe,9c,00,00,00,00,01,\
  00,00,00,ee,00,00,00,00,00,00,00,03,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,01,00,00,00,c6,00,00,00,05,00,00,00,06,00,00,\
  00,00,00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,5c,00,52,00,65,00,\
  63,00,6f,00,76,00,65,00,72,00,79,00,5c,00,33,00,66,00,39,00,37,00,63,00,62,\
  00,35,00,37,00,2d,00,61,00,32,00,36,00,32,00,2d,00,31,00,31,00,65,00,30,00,\
  2d,00,38,00,65,00,64,00,35,00,2d,00,63,00,62,00,64,00,65,00,37,00,33,00,30,\
  00,64,00,66,00,65,00,39,00,63,00,5c,00,57,00,69,00,6e,00,72,00,65,00,2e,00,\
  77,00,69,00,6d,00,00,00

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000002]
"Element"="\windows\system32\winload.exe"

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000004]
"Element"="Windows Recovery Environment"

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\14000006]
"Element"=hex(7):7b,00,36,00,65,00,66,00,62,00,35,00,32,00,62,00,66,00,2d,00,\
  31,00,37,00,36,00,36,00,2d,00,34,00,31,00,64,00,62,00,2d,00,61,00,36,00,62,\
  00,33,00,2d,00,30,00,65,00,65,00,35,00,65,00,66,00,66,00,37,00,32,00,62,00,\
  64,00,37,00,7d,00,00,00,00,00

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\21000001]
"Element"=hex:58,cb,97,3f,62,a2,e0,11,8e,d5,cb,de,73,0d,fe,9c,00,00,00,00,01,\
  00,00,00,ee,00,00,00,00,00,00,00,03,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,01,00,00,00,c6,00,00,00,05,00,00,00,06,00,00,\
  00,00,00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,5c,00,52,00,65,00,\
  63,00,6f,00,76,00,65,00,72,00,79,00,5c,00,33,00,66,00,39,00,37,00,63,00,62,\
  00,35,00,37,00,2d,00,61,00,32,00,36,00,32,00,2d,00,31,00,31,00,65,00,30,00,\
  2d,00,38,00,65,00,64,00,35,00,2d,00,63,00,62,00,64,00,65,00,37,00,33,00,30,\
  00,64,00,66,00,65,00,39,00,63,00,5c,00,57,00,69,00,6e,00,72,00,65,00,2e,00,\
  77,00,69,00,6d,00,00,00

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\22000002]
"Element"="\windows"

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\25000020]
"Element"=hex:00,00,00,00,00,00,00,00

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\26000022]
"Element"=hex:01

[BCD\Objects\{3f97cb57-a262-11e0-8ed5-cbde730dfe9c}\Elements\46000010]
"Element"=hex:01

[BCD\Objects\{3f97cb58-a262-11e0-8ed5-cbde730dfe9c}]

[BCD\Objects\{3f97cb58-a262-11e0-8ed5-cbde730dfe9c}\Description]
"Type"=dword:30000000

[BCD\Objects\{3f97cb58-a262-11e0-8ed5-cbde730dfe9c}\Elements]

[BCD\Objects\{3f97cb58-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000004]
"Element"="Ramdisk Options"

[BCD\Objects\{3f97cb58-a262-11e0-8ed5-cbde730dfe9c}\Elements\31000003]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{3f97cb58-a262-11e0-8ed5-cbde730dfe9c}\Elements\32000004]
"Element"="\Recovery\3f97cb57-a262-11e0-8ed5-cbde730dfe9c\boot.sdi"

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}]

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Description]
"Type"=dword:10200003

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements]

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\11000001]
"Element"=hex:5c,cb,97,3f,62,a2,e0,11,8e,d5,cb,de,73,0d,fe,9c,00,00,00,00,01,\
  00,00,00,ee,00,00,00,00,00,00,00,03,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,01,00,00,00,c6,00,00,00,05,00,00,00,06,00,00,\
  00,00,00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,5c,00,52,00,65,00,\
  63,00,6f,00,76,00,65,00,72,00,79,00,5c,00,33,00,66,00,39,00,37,00,63,00,62,\
  00,35,00,62,00,2d,00,61,00,32,00,36,00,32,00,2d,00,31,00,31,00,65,00,30,00,\
  2d,00,38,00,65,00,64,00,35,00,2d,00,63,00,62,00,64,00,65,00,37,00,33,00,30,\
  00,64,00,66,00,65,00,39,00,63,00,5c,00,57,00,69,00,6e,00,72,00,65,00,2e,00,\
  77,00,69,00,6d,00,00,00

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000002]
"Element"="\windows\system32\winload.exe"

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000004]
"Element"="Windows Recovery Environment"

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\14000006]
"Element"=hex(7):7b,00,36,00,65,00,66,00,62,00,35,00,32,00,62,00,66,00,2d,00,\
  31,00,37,00,36,00,36,00,2d,00,34,00,31,00,64,00,62,00,2d,00,61,00,36,00,62,\
  00,33,00,2d,00,30,00,65,00,65,00,35,00,65,00,66,00,66,00,37,00,32,00,62,00,\
  64,00,37,00,7d,00,00,00,00,00

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\21000001]
"Element"=hex:5c,cb,97,3f,62,a2,e0,11,8e,d5,cb,de,73,0d,fe,9c,00,00,00,00,01,\
  00,00,00,ee,00,00,00,00,00,00,00,03,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,01,00,00,00,c6,00,00,00,05,00,00,00,06,00,00,\
  00,00,00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,5c,00,52,00,65,00,\
  63,00,6f,00,76,00,65,00,72,00,79,00,5c,00,33,00,66,00,39,00,37,00,63,00,62,\
  00,35,00,62,00,2d,00,61,00,32,00,36,00,32,00,2d,00,31,00,31,00,65,00,30,00,\
  2d,00,38,00,65,00,64,00,35,00,2d,00,63,00,62,00,64,00,65,00,37,00,33,00,30,\
  00,64,00,66,00,65,00,39,00,63,00,5c,00,57,00,69,00,6e,00,72,00,65,00,2e,00,\
  77,00,69,00,6d,00,00,00

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\22000002]
"Element"="\windows"

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\25000020]
"Element"=hex:00,00,00,00,00,00,00,00

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\26000022]
"Element"=hex:01

[BCD\Objects\{3f97cb5b-a262-11e0-8ed5-cbde730dfe9c}\Elements\46000010]
"Element"=hex:01

[BCD\Objects\{3f97cb5c-a262-11e0-8ed5-cbde730dfe9c}]

[BCD\Objects\{3f97cb5c-a262-11e0-8ed5-cbde730dfe9c}\Description]
"Type"=dword:30000000

[BCD\Objects\{3f97cb5c-a262-11e0-8ed5-cbde730dfe9c}\Elements]

[BCD\Objects\{3f97cb5c-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000004]
"Element"="Ramdisk Options"

[BCD\Objects\{3f97cb5c-a262-11e0-8ed5-cbde730dfe9c}\Elements\31000003]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{3f97cb5c-a262-11e0-8ed5-cbde730dfe9c}\Elements\32000004]
"Element"="\Recovery\3f97cb5b-a262-11e0-8ed5-cbde730dfe9c\boot.sdi"

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}]

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}\Description]
"Type"=dword:10200003

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}\Elements]

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}\Elements\11000001]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000002]
"Element"="\Windows\system32\winload.exe"

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000004]
"Element"="Microsoft Windows 7"

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}\Elements\12000005]
"Element"="en-US"

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}\Elements\21000001]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,ee,c1,2d,22,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,7f,b0,7f,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{3f97cb5f-a262-11e0-8ed5-cbde730dfe9c}\Elements\22000002]
"Element"="\Windows"

[BCD\Objects\{4636856e-540f-4170-a130-a84776f4c654}]

[BCD\Objects\{4636856e-540f-4170-a130-a84776f4c654}\Description]
"Type"=dword:20100000

[BCD\Objects\{4636856e-540f-4170-a130-a84776f4c654}\Elements]

[BCD\Objects\{4636856e-540f-4170-a130-a84776f4c654}\Elements\15000011]
"Element"=hex:00,00,00,00,00,00,00,00

[BCD\Objects\{4636856e-540f-4170-a130-a84776f4c654}\Elements\15000013]
"Element"=hex:01,00,00,00,00,00,00,00

[BCD\Objects\{4636856e-540f-4170-a130-a84776f4c654}\Elements\15000014]
"Element"=hex:00,c2,01,00,00,00,00,00

[BCD\Objects\{466f5a88-0af2-4f76-9038-095b170dc21c}]

[BCD\Objects\{466f5a88-0af2-4f76-9038-095b170dc21c}\Description]
"Type"=dword:10300006

[BCD\Objects\{466f5a88-0af2-4f76-9038-095b170dc21c}\Elements]

[BCD\Objects\{466f5a88-0af2-4f76-9038-095b170dc21c}\Elements\11000001]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,7e,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,2e,b0,2e,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{466f5a88-0af2-4f76-9038-095b170dc21c}\Elements\12000002]
"Element"="\ntldr"

[BCD\Objects\{466f5a88-0af2-4f76-9038-095b170dc21c}\Elements\12000004]
"Element"="Frühere Windows-Version"

[BCD\Objects\{5189b25c-5558-4bf2-bca4-289b11bd29e2}]

[BCD\Objects\{5189b25c-5558-4bf2-bca4-289b11bd29e2}\Description]
"Type"=dword:20100000

[BCD\Objects\{5189b25c-5558-4bf2-bca4-289b11bd29e2}\Elements]

[BCD\Objects\{6efb52bf-1766-41db-a6b3-0ee5eff72bd7}]

[BCD\Objects\{6efb52bf-1766-41db-a6b3-0ee5eff72bd7}\Description]
"Type"=dword:20200003

[BCD\Objects\{6efb52bf-1766-41db-a6b3-0ee5eff72bd7}\Elements]

[BCD\Objects\{6efb52bf-1766-41db-a6b3-0ee5eff72bd7}\Elements\14000006]
"Element"=hex(7):7b,00,37,00,65,00,61,00,32,00,65,00,31,00,61,00,63,00,2d,00,\
  32,00,65,00,36,00,31,00,2d,00,34,00,37,00,32,00,38,00,2d,00,61,00,61,00,61,\
  00,33,00,2d,00,38,00,39,00,36,00,64,00,39,00,64,00,30,00,61,00,39,00,66,00,\
  30,00,65,00,7d,00,00,00,7b,00,37,00,66,00,66,00,36,00,30,00,37,00,65,00,30,\
  00,2d,00,34,00,33,00,39,00,35,00,2d,00,31,00,31,00,64,00,62,00,2d,00,62,00,\
  30,00,64,00,65,00,2d,00,30,00,38,00,30,00,30,00,32,00,30,00,30,00,63,00,39,\
  00,61,00,36,00,36,00,7d,00,00,00,00,00

[BCD\Objects\{7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}]

[BCD\Objects\{7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}\Description]
"Type"=dword:20100000

[BCD\Objects\{7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}\Elements]

[BCD\Objects\{7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}\Elements\14000006]
"Element"=hex(7):7b,00,34,00,36,00,33,00,36,00,38,00,35,00,36,00,65,00,2d,00,\
  35,00,34,00,30,00,66,00,2d,00,34,00,31,00,37,00,30,00,2d,00,61,00,31,00,33,\
  00,30,00,2d,00,61,00,38,00,34,00,37,00,37,00,36,00,66,00,34,00,63,00,36,00,\
  35,00,34,00,7d,00,00,00,7b,00,30,00,63,00,65,00,34,00,39,00,39,00,31,00,62,\
  00,2d,00,65,00,36,00,62,00,33,00,2d,00,34,00,62,00,31,00,36,00,2d,00,62,00,\
  32,00,33,00,63,00,2d,00,35,00,65,00,30,00,64,00,39,00,32,00,35,00,30,00,65,\
  00,35,00,64,00,39,00,7d,00,00,00,7b,00,35,00,31,00,38,00,39,00,62,00,32,00,\
  35,00,63,00,2d,00,35,00,35,00,35,00,38,00,2d,00,34,00,62,00,66,00,32,00,2d,\
  00,62,00,63,00,61,00,34,00,2d,00,32,00,38,00,39,00,62,00,31,00,31,00,62,00,\
  64,00,32,00,39,00,65,00,32,00,7d,00,00,00,00,00

[BCD\Objects\{7ff607e0-4395-11db-b0de-0800200c9a66}]

[BCD\Objects\{7ff607e0-4395-11db-b0de-0800200c9a66}\Description]
"Type"=dword:20200003

[BCD\Objects\{7ff607e0-4395-11db-b0de-0800200c9a66}\Elements]

[BCD\Objects\{7ff607e0-4395-11db-b0de-0800200c9a66}\Elements\250000f3]
"Element"=hex:00,00,00,00,00,00,00,00

[BCD\Objects\{7ff607e0-4395-11db-b0de-0800200c9a66}\Elements\250000f4]
"Element"=hex:01,00,00,00,00,00,00,00

[BCD\Objects\{7ff607e0-4395-11db-b0de-0800200c9a66}\Elements\250000f5]
"Element"=hex:00,c2,01,00,00,00,00,00

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}]

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Description]
"Type"=dword:10100002

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements]

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\11000001]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,7e,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,2e,b0,2e,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\12000004]
"Element"="Windows Boot Manager"

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\12000005]
"Element"="de-DE"

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\14000006]
"Element"=hex(7):7b,00,37,00,65,00,61,00,32,00,65,00,31,00,61,00,63,00,2d,00,\
  32,00,65,00,36,00,31,00,2d,00,34,00,37,00,32,00,38,00,2d,00,61,00,61,00,61,\
  00,33,00,2d,00,38,00,39,00,36,00,64,00,39,00,64,00,30,00,61,00,39,00,66,00,\
  30,00,65,00,7d,00,00,00,00,00

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\23000003]
"Element"="{466f5a88-0af2-4f76-9038-095b170dc21c}"

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\23000006]
"Element"="{3f97cb59-a262-11e0-8ed5-cbde730dfe9c}"

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\24000001]
"Element"=hex(7):7b,00,34,00,36,00,36,00,66,00,35,00,61,00,38,00,38,00,2d,00,\
  30,00,61,00,66,00,32,00,2d,00,34,00,66,00,37,00,36,00,2d,00,39,00,30,00,33,\
  00,38,00,2d,00,30,00,39,00,35,00,62,00,31,00,37,00,30,00,64,00,63,00,32,00,\
  31,00,63,00,7d,00,00,00,7b,00,33,00,66,00,39,00,37,00,63,00,62,00,35,00,66,\
  00,2d,00,61,00,32,00,36,00,32,00,2d,00,31,00,31,00,65,00,30,00,2d,00,38,00,\
  65,00,64,00,35,00,2d,00,63,00,62,00,64,00,65,00,37,00,33,00,30,00,64,00,66,\
  00,65,00,39,00,63,00,7d,00,00,00,00,00

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\24000010]
"Element"=hex(7):7b,00,62,00,32,00,37,00,32,00,31,00,64,00,37,00,33,00,2d,00,\
  31,00,64,00,62,00,34,00,2d,00,34,00,63,00,36,00,32,00,2d,00,62,00,66,00,37,\
  00,38,00,2d,00,63,00,35,00,34,00,38,00,61,00,38,00,38,00,30,00,31,00,34,00,\
  32,00,64,00,7d,00,00,00,00,00

[BCD\Objects\{9dea862c-5cdd-4e70-acc1-f32b344d4795}\Elements\25000004]
"Element"=hex:0a,00,00,00,00,00,00,00

[BCD\Objects\{ae5534e0-a924-466c-b836-758539a3ee3a}]

[BCD\Objects\{ae5534e0-a924-466c-b836-758539a3ee3a}\Description]
"Type"=dword:30000000

[BCD\Objects\{ae5534e0-a924-466c-b836-758539a3ee3a}\Elements]

[BCD\Objects\{ae5534e0-a924-466c-b836-758539a3ee3a}\Elements\12000004]
"Element"="Macrium Reflect System Recovery"

[BCD\Objects\{ae5534e0-a924-466c-b836-758539a3ee3a}\Elements\31000003]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,7e,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,2e,b0,2e,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{ae5534e0-a924-466c-b836-758539a3ee3a}\Elements\32000004]
"Element"="\boot\Macrium\boot.sdi"

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}]

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}\Description]
"Type"=dword:10200005

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}\Elements]

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}\Elements\11000001]
"Element"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,06,00,00,00,00,\
  00,00,00,48,00,00,00,00,00,00,00,00,7e,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,01,00,00,00,2e,b0,2e,b0,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}\Elements\12000002]
"Element"="\boot\memtest.exe"

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}\Elements\12000004]
"Element"="Windows-Speicherdiagnose"

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}\Elements\12000005]
"Element"="de-DE"

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}\Elements\14000006]
"Element"=hex(7):7b,00,37,00,65,00,61,00,32,00,65,00,31,00,61,00,63,00,2d,00,\
  32,00,65,00,36,00,31,00,2d,00,34,00,37,00,32,00,38,00,2d,00,61,00,61,00,61,\
  00,33,00,2d,00,38,00,39,00,36,00,64,00,39,00,64,00,30,00,61,00,39,00,66,00,\
  30,00,65,00,7d,00,00,00,00,00

[BCD\Objects\{b2721d73-1db4-4c62-bf78-c548a880142d}\Elements\1600000b]
"Element"=hex:01

C:\Boot.ini:

Spoiler

; This boot.ini was automatically generated by NeoSmart Technologies' BootGrabber.exe
; Use EasyBCD from http://neosmart.net/dl.php?id=1 to manage your bootloader

[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP on C:\" /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Windows XP on H:\" /fastdetect

 

Peter

]]> Thu, 13 Feb 2014 11:34:02 +0000 http://reboot.pro/topic/19565-windows-boot-question/ http://reboot.pro/topic/18098-ffmpeg-for-dos/ Ffmpeg for dos .

http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Blog.Ffmpeg

Great!

]]> Thu, 13 Feb 2014 11:17:41 +0000 http://reboot.pro/topic/18098-ffmpeg-for-dos/ http://reboot.pro/topic/19140-ufd-format/

File Name: UFD_FORMAT
File Submitter: wimb
File Submitted: 08 Nov 2013
File Updated: 10 Dec 2013
File Category: Boot tools

UFD_FORMAT - Tool to format USB Flash Drives for booting with Boot Manager menu

After UFD_FORMAT then UEFI_MULTI is used to make Multi-Boot USB-Stick booting with WIM ISO and VHD Boot Image files

Download and Run UFD_FORMAT_80.exe and Extract to simple path
In Win 7/8 OS Set User Account Control Off and Reboot

UFD_FORMAT.exe - Tool to format USB-stick for Booting with Boot Manager Menu on BIOS or UEFI computer and
Tool to make USB-Stick having two partitions - FAT32 Boot partition for WIM or ISO and NTFS System partition for VHD.
Option to Install Grub4dos in MBR BootCode, which allows BIOS computer to boot directly from USB with Grub4dos Menu.
Option to make Boot Manager and Grub4dos Menu on UFD to boot UEFI + BIOS directly from USB with Boot Manager Menu.
Windows 7/8 or 7PE is needed to make Boot Manager Menu.

Download - http://reboot.pro/files/file/415-ufd-format/

UFD_FORMAT - In XP Format USB-Stick for booting with Grub4dos Menu


=

UFD_FORMAT - In 7/8 Format USB-Stick for booting with Boot Manager Menu


=
USB_Part_Flip.exe to Exchange Partition Table Entries in MBR of USB-Stick -
allows to change which primary partition of the USB-stick is visible in Windows

UEFI_MULTI.exe will make Multi-Boot USB-drives by using Boot Image Files (VHD IMG ISO or WIM)
http://reboot.pro/topic/18182-uefi-multi-make-multi-boot-usb-harddisk/
http://reboot.pro/topic/17877-uefi-windows-8-bios-grub4dos-multiboot-usb-harddisk/

Boot UEFI - F12 - BIOS - Grub4dos - Win8 VHD - Ramdisk - Win 8x32
http://reboot.pro/topic/18182-uefi-multi-make-multi-boot-usb-harddisk/page-2#entry179107

Win- XP/7/8 VHD on NTFS System partition is loaded fast from USB-Stick into RAMDISK and then booting from RAMDISK occurs

Credits and Thanks to:
Uwe Sieber for making ListUsbDrives - http://www.uwe-sieber.de/english.html
Dariusz Stanislawek for the DS File Ops Kit (DSFOK) - http://members.ozemail.com.au/~nulifetv/freezip/freeware/
Roger Layton for making MBRwizard - http://mbrwizard.com/ and http://firesage.com/mbrwizard.php
ktp for using two partition USB-Stick with UEFI_MULTI - http://reboot.pro/topic/18182-uefi-multi-make-multi-boot-usb-harddisk/page-2#entry177216

Click here to download this file]]> Thu, 13 Feb 2014 06:27:31 +0000 http://reboot.pro/topic/19140-ufd-format/ http://reboot.pro/topic/17742-problem-save-setting/ ]]> Wed, 12 Feb 2014 10:48:55 +0000 http://reboot.pro/topic/17742-problem-save-setting/ http://reboot.pro/topic/18593-vhd-w7-compact-make-mini-7/

File Name: VHD_W7_Compact - Make Mini 7 -
File Submitter: wimb
File Submitted: 02 Jun 2013
File Updated: 08 Feb 2014
File Category: Tools

VHD_W7_Compact - Program to make Mini 7

Download and Run VHD_W7C.exe and Extract to simple path

In Win 7/8 OS Set User Account Control Off and Reboot

VHD_W7_Compact.exe - Make Portable Win 7 in 2 GB VHD booting from USB or HDD
x64 version needs 3 GB VHD because of extra 1 GB SysWOW64 folder

Source is Windows 7 x86 or x64 fresh installed in 10-15 GB VHD Or Install on primary active partition of internal harddisk.
Target Boot Drive can be FAT32 or NTFS USB-drive used only for Boot files so that there are no changes for booting of internal harrddisk .
Target System Drive must be NTFS and is the drive where the Win7 VHD file is created and this can be your internal harddisk drive.



Support topic - http://reboot.pro/topic/18593-vhd-w7-compact-make-mini-7/

Download VHD_W7C - http://reboot.pro/files/file/321-vhd-w7-compact-make-mini-7/

More Info - http://www.911cd.net/forums//index.php?showtopic=25357

Ultimate Windows 7 VHD files make use of Microsoft VHD HBA driver which allows in Boot Manager Menu to boot VHD as FILEDISK.
Booting VHD files from Grub4dos Menu as FILEDISK or as RAMDISK requires to Install in Source VHD either FiraDisk Or WinVBlock driver.
Additinally Installed Programs and Drivers and Settings are remembered in FILEDISK just like in normal Windows OS.
Loading the VHD into RAMDISK is much faster when the VHD file is located on the internal NTFS harddisk drive.

Add Drivers from makebt\drivers to system32\DriverStore\FileRepository is applied for Portable version by using Dism.exe
Run first VHD_W7C_drivers.exe plugin to add useful extra drivers to makebt\drivers folder.
Download VHD_W7C_drivers from http://reboot.pro/files/file/322-vhd-w7c-driversexe-plugin/

Let Portable version boot on different hardware to make it Universal by Install of Drivers.
Use Universal Portable Win7 VHD as Source to make Mini 7 VHD that can boot in any case on all experienced hardware.
Mini 7 has smallest Size of about 600 MB by removing Windows Media Player and by further reduction of system32 and DriverStore.
Mini 7 is very useful to Boot from RAMDISK on known hardware, since servicing for Adding Driver Packages has also been removed.

Build-in Defraggler is useful (really needed) to Defrag files within the Win7 VHD, but post processing is also possible after mounting the Win7 VHD.
NTFS Compression results in high fragmentation e.g. 85% so that it is advised to use Defrag VHD option.

VHD_W7_Compact.exe can create Boot Menu entry on HDD or USB Boot Drive for the Win7 VHD on NTFS Target System Drive.
VHD entry is added to Boot Manager Menu and Grub4dos Menu is made when FiraDisk or WinVBlock driver is found.

Program UEFI_MULTI can be used in Win 7/8/7PE OS to make other HDD or USB drives bootable with the created Win 7 VHD.
http://reboot.pro/topic/18182-uefi-multi/ Or http://www.911cd.net/forums//index.php?showtopic=25269

BOOT_IMG.exe makes Grub4dos Boot Menu on Target Boot Drive for VHD on NTFS Target System Drive (FileCopy of VHD occurs if not yet present)

================================================================================

Windows 7 Source VHD preparation

Boot with Windows 7/8 or 7 PE and then use WinNTSetup2_x86.exe
to Install Windows 7 x86 or x64 in NTFS 10-15 GB VHD or to Install on primary NTFS partition of internal harddisk
Boot Drive can be FAT32 or NTFS USB-drive so that normal booting of the internal harddisk is not changed.

Win 7 Setup ISO file was mounted via R-mouse in ImDisk Virtual drive
In WinNTSetup2 - Tweaks - Select all System Tweaks so that UAC is off etc.
http://www.msfn.org/board/topic/149612-winntsetup-v23/

After booting with Windows 7 then Check to have Switched Off :
UAC + Defender + pagefile + System Restore + Hibernate + Windows Update + Action Center settings Disable ALL options
Hibernate OFF is needed via cmd window with

powercfg -h OFF

Install FiraDisk driver with R-mouse on firadisk.inf in makebt\firadisk-driver- folder
The 64-bit FiraDisk driver requires to boot with testsigning switched on

Open Command Prompt as Administrator:

bcdedit /set testsigning on

Reboot to activate testsigning - Info http://msdn.microsoft.com/en-us/library/ff553484.aspx

================================================================================

Credits and Thanks to:
JFX for making WinNTSetup2 to Install Windows 2k/XP/2003/Vista/7/8 x86/x64 - http://www.msfn.org/board/topic/149612-winntsetup-v2/
chenall, tinybit and Bean for making Grub4dos - http://code.google.com/p/grub4dos-chenall/downloads/list
karyonix for making FiraDisk driver- http://reboot.pro/topic/8804-firadisk-latest-00130/
Sha0 for making WinVBlock driver - http://reboot.pro/topic/8168-winvblock/
Olof Lagerkvist for ImDisk virtual disk driver - http://www.ltr-data.se/opencode.html#ImDisk and http://reboot.pro/index.php?showforum=59
Uwe Sieber for making ListUsbDrives - http://www.uwe-sieber.de/english.html
Dariusz Stanislawek for the DS File Ops Kit (DSFOK) - http://members.ozemail.com.au/~nulifetv/freezip/freeware/
cdob and maanu to Fix Win7 for booting from USB - http://reboot.pro/topic/14186-usb-hdd-boot-and-windows-7-sp1/
marv for making UsbBootWatcher - https://github.com/vavrecan/usb-boot-watcher and http://www.911cd.net/forums//index.php?showtopic=22473
Pauly for making Bootice - http://bbs.ipauly.com/viewtopic.php?f=2&t=2&sid=ebc27aec23a8eb21006e07ab6f3b01cb
NeoSmart for making EasyBCD - https://neosmart.net/EasyBCD/
-
More Info on booting Win 7 VHD from grub4dos menu by using FiraDisk Or WinVBlock driver:
http://reboot.pro/topic/9830-universal-hdd-image-files-for-xp-and-windows-7/ Or http://www.911cd.net/forums//index.php?showtopic=23553
Boot Windows 7 from USB - http://reboot.pro/index.php?showforum=77
Boot Windows 7 from USB - karyonix - http://reboot.pro/index.php?showtopic=9196

================================================================================

Grub4dos Menu to Boot Win7-1.vhd as FILEDISK or as RAMDISK by using FiraDisk driver

title Portable Win7-1.vhd - FiraDisk FILEDISK - 2.0 GB
find --set-root --ignore-floppies /Win7-1.vhd
map --heads=2 --sectors-per-track=18 --mem (md)0x800+4 (99)
map /Win7-1.vhd (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=disk,vmem=find:/Win7-1.vhd,boot;\n\0
rootnoverify (hd0,0)
chainloader /bootmgr
map --status
pause Press any key . . .

title Portable Win7-1.vhd - FiraDisk RAMDISK - 2.0 GB
find --set-root --ignore-floppies /Win7-1.vhd
map --mem /Win7-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

================================================================================

Grub4dos Menu to Boot Win7-5.vhd as FILEDISK or as RAMDISK by using WinVBlock driver

title Portable Win7-5.vhd - WinVBlock FILEDISK - 2.0 GB
# Sector-mapped disk
find --set-root --ignore-floppies /Win7-5.vhd
map /Win7-5.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

title Portable Win7-5.vhd - WinVBlock RAMDISK - 2.0 GB
# Sector-mapped disk
find --set-root --ignore-floppies /Win7-5.vhd
map --mem /Win7-5.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

================================================================================

Click here to download this file]]> Wed, 12 Feb 2014 08:44:17 +0000 http://reboot.pro/topic/18593-vhd-w7-compact-make-mini-7/ http://reboot.pro/topic/19564-undelete-navigator-for-livexp-and-win7pe-winbuilder-82/

File Name: Undelete Navigator for LiveXP and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 11 Feb 2014
File Category: App scripts

Homepage and info:
http://www.4r-soft.com/undelete-navigator/

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://al-jo.net46.net/livexp/livexp2.html
__________________________________________________

Click here to download this file]]> Tue, 11 Feb 2014 15:56:45 +0000 http://reboot.pro/topic/19564-undelete-navigator-for-livexp-and-win7pe-winbuilder-82/ http://reboot.pro/topic/14823-resize-a-partition-without-moving-its-content/
This makes very little sense to me. When you look at any Defragmenter's work, they can move data around the partition in any direction, driven by their optimization algorithm (different for each). Again, looking at disk structure in Degragmenter, the File System data (MFT / MFT Zone) can be at any place around the disk, not nesessarely at its beginning. So why Partitioning tools can't do the same? Leave MFT and all other data where it is (at least on a user demand for non-bootable partitions), or move merely MBR & MFT to the beginning of a resized partition, but leave data (which takes a lot more space than MFT) untouched.

Its hard to comprehend the logic of moving 500Gb around the same partition, putting a hard drive to totally useless severe stress, loosing time, and risking to loose data along the way as the drive heats up. The problem was somewhat addressed in this thread on Gparted Forum, but without any solution, citing no objective reasons for lack of such feature apart from "extra programming required". Given how many people refrain from repartitioning and can't use disk space efficiently due to this very reason - to avoid senselessly moving huge amount of data to the left, the extra effort required appears well justified.

Hence a question: is there any free & non-free partitioning tool that allows to extend a partition to the LEFT without moving its data to the LEFT (except possibly boot or MFT related data)?]]> Tue, 11 Feb 2014 08:47:50 +0000 http://reboot.pro/topic/14823-resize-a-partition-without-moving-its-content/ http://reboot.pro/topic/18952-fix-the-missing-ntldr/ Have you ever tried to boot your computer when the message said that NTLDR is missing? If you have activated your hard drive partition/volume on your computer, then you have made a big mistake. I did this and I didn't know what will happen.

You need to repair your missing NTLDR by inserting your Windows CD. You can also insert your USB flash drive instead of CD. To repair this, follow instructions:

Windows 7

1. Insert your Windows 7 CD/USB.
2. When Windows loads up, select your language, and click next.
3. When the "Install Windows" window appears, click "Repair your computer".
4. When the System Recovery Options appears, choose an operating system which is located on the hard drive.
5. Click Command Prompt.

Windows 8/8.1

1. Insert your Windows 8/8.1 CD/USB
2. When Windows loads up, select your language, and click next.
3. When the "Install Windows" window appears, click "Repair your computer".
4. Click Troubleshoot.
5. Click Advanced Options.
6. Click Command Prompt.

Command Prompt

1. In Command Prompt, type:
DISKPART
2. When Diskpart loads up, there are two ways to activate:

A. Disk Partition

1. If you have a disk partition, you can type the following command:
list partition
This will show you how many partitions you have.
2. If your first partition is 1, type in:
select partition 1
3. Then type:
active
4. This will activate your partition. When it succeeds, type:
exit
5. This will bring you back to the Command Prompt. Type exit, or close this program, and reboot your computer.

B. Disk Volume

1. If you have a disk volume, type the following command:
list volume
This shows you how many volumes you have.
2. If your first volume is 1, type the following command:
select volume 1
3. When the volume is selected, type:
active
4. When your volume is successfully activated, you can leave the Diskpart by entering:
exit
5. It will return back to the Command Prompt. Type exit, or close this program, and reboot your computer.

There you go! Now you can boot your computer! If it isn't working, you can activate another volume/partition and boot again. I hope that helps.

Vasja Stojkovic

]]> Tue, 11 Feb 2014 05:19:49 +0000 http://reboot.pro/topic/18952-fix-the-missing-ntldr/ http://reboot.pro/topic/19556-disque-ssd-non-reconnu/ Bonjour à tous

J' utilise UBCD4 depuis plusieurs années mais sur dernière machine sur laquelle j' ai un disque SSDSC2180A3 avec Windows 7 pro ce disque n' esp pas reconnu au Boot de UBCD

Y a t il  une possibilité d' intégrer dans UBCD les drivers de type de disque

Merci à vous

]]> Mon, 10 Feb 2014 18:41:34 +0000 http://reboot.pro/topic/19556-disque-ssd-non-reconnu/ http://reboot.pro/topic/19523-alcor-micro-chip-of-fake-pen-drive/ I have a bunch of drive that were listed as 256GB when I bought them.

The first one appears to be 8GB.

 

I am not sure of the process to go through to make it useable.

 

 

Description: [H:]USB Mass Storage Device(Generic Flash Disk)
Device Type:        Mass Storage Device

Protocal Version: USB 2.00
Current Speed: High Speed
Max Current: 200mA

USB Device ID: VID = 0011 PID = 7788
Serial Number: 55D1F200

Device Vendor: Generic
Device Name: Mass Storage
Device Revision: 010B

Manufacturer: Generic
Product Model: Flash Disk
Product Revision: 8.00

Controller Vendor: Alcor Micro
Controller Part-Number: SC908SN/AU6989SN - F/W FF03
Flash ID code:      ADDE94EB - Hynix - 1CE/Single Channel [MLC] -> Total Capacity = 8GB

Tools on web:       http://dl.mydigit.net/special/up/alcor.html

 

 

FAKEFLASHTEST v1.0.9  [SSi]
DRIVE 10 - 249.9GiB General UDisk                  
FFT - Quick Size Test (destructive)
M:     (no label)    DRIVE 10 - 249.9GiB General UDisk                  

Writing marker blocks to drive 10
5% complete  - 37 min 41 sec  remaining
10% complete  - 36 min 45 sec  remaining
15% complete  - 34 min 57 sec  remaining
20% complete  - 33 min 0 sec  remaining
25% complete  - 31 min 0 sec  remaining
30% complete  - 28 min 59 sec  remaining
35% complete  - 26 min 56 sec  remaining
40% complete  - 24 min 53 sec  remaining
45% complete  - 22 min 49 sec  remaining
50% complete  - 20 min 45 sec  remaining
55% complete  - 18 min 41 sec  remaining
60% complete  - 16 min 37 sec  remaining
65% complete  - 14 min 33 sec  remaining
70% complete  - 12 min 28 sec  remaining
75% complete  - 10 min 24 sec  remaining
80% complete  - 8 min 19 sec  remaining
85% complete  - 6 min 14 sec  remaining
90% complete  - 4 min 10 sec  remaining
95% complete  - 2 min 5 sec  remaining
100% complete  - 0 min 1 sec remaining
Reading back marker blocks...
5% complete - 11 min 5 sec  remaining
10% complete - 10 min 39 sec  remaining
15% complete - 10 min 1 sec  remaining
20% complete - 9 min 24 sec  remaining
25% complete - 8 min 48 sec  remaining
30% complete - 8 min 13 sec  remaining
35% complete - 7 min 37 sec  remaining
40% complete - 7 min 2 sec  remaining
45% complete - 6 min 27 sec  remaining
50% complete - 5 min 52 sec  remaining
55% complete - 5 min 17 sec  remaining
60% complete - 4 min 42 sec  remaining
65% complete - 4 min 7 sec  remaining
70% complete - 3 min 32 sec  remaining
75% complete - 2 min 57 sec  remaining
80% complete - 2 min 22 sec  remaining
85% complete - 1 min 46 sec  remaining
90% complete - 1 min 11 sec  remaining
95% complete - 0 min 36 sec  remaining
Memory tested in blocks of 25600 sectors.

BAD MEMORY from sector 33862074 (16,534.2158MiB) to sector 524281274 (255,996.7158Mib)

WARNING: no memory detected at one or more locations.
Test took 3402 seconds.

                         *** FAILED ***

DEVICE HAS DUPLICATE OR BAD BLOCKS!

Recommended maximum usable partition size: 16,521.7158Mib (approx. Last good Sector=33862074)

Unplug and re-connect the drive, then reformat it using Windows or RMPrepUSB.

 

Thanks

 

 

]]> Mon, 10 Feb 2014 11:32:53 +0000 http://reboot.pro/topic/19523-alcor-micro-chip-of-fake-pen-drive/ http://reboot.pro/topic/19553-hdd-multi-boot-propely/ Hello everyone:
I want to make my hard drive can boot several things, now this so it succeeds using grub4dos manually, but the problem that I have is that rather than attempt've only managed to boot an installer of windows 7, and I could not boot anything more and want to be able to boot other things I need serious: an installer for windows 7, tinycore, ubuntu, Slacko, dsl, UBCD, hirens boot. and mainly because the method we use to make my bootable external dd is old and want to know what guidelines to follow.
Use my dd is 160gb in ntfs (not very big)
PS: sorry for my English is google translator I do better reading than writing. : P

]]> Sun, 09 Feb 2014 20:12:39 +0000 http://reboot.pro/topic/19553-hdd-multi-boot-propely/ http://reboot.pro/topic/19559-kaspersky-tdsskiller-and-win7pe-winbuilder-82/ This is my first script! ...and thankfully a simple one.

 

On first run the script downloads the free TDSSKiller executable from Kaspersky. Shortcuts for Start Menu and Desktop are added. Simply run and scan...

 

You can change the download location in case it moves, and set whether you want it to download a new copy with every project run. There is no new version checking going, so just use the check box next time you notice it needs updating.

 

I realise some of it's power with checking services and drivers won't work from a PE environment, but I've repaired quite a few MBR based rootkits this way and for that reason justifies the script.

 

http://reboot.pro/files/file/463-kaspersky-tdsskiller/

]]> Sun, 09 Feb 2014 19:12:45 +0000 http://reboot.pro/topic/19559-kaspersky-tdsskiller-and-win7pe-winbuilder-82/ http://reboot.pro/topic/19558-how-is-usb-bandwidth-shared/ One has 3 USB ports but just 1 USB 3.0, the other 3 USB ports too, but 2 USB 3.0 ports.
The crux with the second is, that the 2 USB 3.0 ports are on the same controller.

So there is no difference in transfer speed between using the first with a usb3 hub connected and the second straight, when i want to transfer data between two external USB 3.0 drives, right?

I'm a bit iffy on the whole USB topic. Maybe someone can clarify a few other things too.
- Bandwidth is share between devices connected to the same Root-Hub or is it the same Host-Controller?
- USB 2.0 devices connected to a USB3 port, can still only share 480MB/s?
- does a USB 2.0 device, dig into the available bandwidth to a USB3.0 divice on the same USB 3.0 port on the computer or run USB2 and USB3 completely independant even on the same cable?

Thanks and ]]> Sun, 09 Feb 2014 17:59:23 +0000 http://reboot.pro/topic/19558-how-is-usb-bandwidth-shared/ http://reboot.pro/topic/19552-how-to-create-password-for-exe/ How to Create Password For exe and then exe open without enter password ????????

]]> Sun, 09 Feb 2014 03:11:33 +0000 http://reboot.pro/topic/19552-how-to-create-password-for-exe/ http://reboot.pro/topic/19527-vmlite-workstation/ I have tested this virtual machine called "VMLite Workstation". You can see the results of testing if you like.

 

Here it is: http://www.youtube.com/watch?v=bhPOKdtpZQk

 

Vasja Stojkovic

]]> Sat, 08 Feb 2014 13:50:25 +0000 http://reboot.pro/topic/19527-vmlite-workstation/ http://reboot.pro/topic/19545-fbinst-not-showing-files-after-repartition/ i'm created second partition FAT32, the first one is NTFS, and after that when I open fbinst to edit the title or fbinst menu I ca'n see the 3 files that I see before, and can't edit the title before showing the grub4dos options.

I have a screenshot of the screen that I see:

 

http://oi62.tinypic.com/6qzamx.jpg

 

how to fix this issue without reformatting the usb stick?

 

thanks.

]]> Sat, 08 Feb 2014 07:44:36 +0000 http://reboot.pro/topic/19545-fbinst-not-showing-files-after-repartition/ http://reboot.pro/topic/19555-windows-8-product-key-viewer-for-win8pe-and-win7pe-winbuilder-82/

File Name: Windows 8 Product Key Viewer for Win8PE and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 08 Feb 2014
File Category: App scripts

Homepage and info:
http://forums.mydigitallife.info/members/204242-woot332

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html

Click here to download this file]]> Sat, 08 Feb 2014 07:23:50 +0000 http://reboot.pro/topic/19555-windows-8-product-key-viewer-for-win8pe-and-win7pe-winbuilder-82/ http://reboot.pro/topic/19554-touchmousepointer-excellent-virtual-touchpad-on-screen-mouse-windows-8/ Works great on Desktop side of windows 8. Real handy for those using tablets or touch screens.

http://www.lovesummertrue.com/touchmousepointer/en-us/

 

TouchMousePointer is desktop application for Windows 8, Windows 8.1 or later.
For tablet PC or convertibles PC slate mode.
Requires touch interface.

Like a touch pad(track pad) pointing device on screen by touch interface.
It's on-screen touchpad.(on-screen mouse)

 

 

 

 

Screenshots

http://www.lovesummertrue.com/touchmousepointer/en-us/screenshots_1.html

]]> Fri, 07 Feb 2014 23:00:49 +0000 http://reboot.pro/topic/19554-touchmousepointer-excellent-virtual-touchpad-on-screen-mouse-windows-8/ http://reboot.pro/topic/19487-virtual-machine/ Please leave a reply in this topic if you like. Thank you.

Vasja Stojkovic

]]> Fri, 07 Feb 2014 12:10:52 +0000 http://reboot.pro/topic/19487-virtual-machine/ http://reboot.pro/topic/19544-imdisk-to-read-log-file-while-another-process-writes/ Hello, I have a few applications that write log files while running (that I don't have the ability to change) and unfortunately the developers are locking the log file while it is being written (not sure why they would do this other than not knowing about windows file api perhaps). What I would like to do is similar to the bash command tail -f on each of these log files while they are being written to. I was thinking I could create some kind of symlink to a ram disk and then read them from the ram disk. I created a junction on the parent directory of the log files to a ImDisk ramdisk and then try opening them there but I still get the same problem with an error of "that file is in use by another process". Can ImDisk help me here? Is there a way to read a symbolic link to a log file from ram disk ? I would prefer an approach I can use programatically. Other ideas about how I could tail a log file that is locked while being written to?

 

v/r

 

-Tim

]]> Fri, 07 Feb 2014 08:36:43 +0000 http://reboot.pro/topic/19544-imdisk-to-read-log-file-while-another-process-writes/ http://reboot.pro/topic/16374-rufus-introduction-topic/
If you look in the Boot Tools section, you will see a new entry called Rufus. I am the author of this program.

Rufus, is a Windows utility that helps format and create bootable USB drives. It can do so using either DOS (embedded) or an user provided bootable ISO, such as Windows or Linux installation media.

Why would you want to use Rufus?

Rufus takes the approach compensating for a feature that should be enabled in every OS by default, which is the ability to quickly and easily create a bootable USB, either for DOS or from a bootable ISO.
With USB now being ubiquitous, we see little reason why, in 2012, the default Windows formatting dialog offers the option to create an obsolete bootable floppy, but not a more useful bootable USB.

As such we believe that, any Windows user, be them sysadmins or occasional users, should have the ability to quickly and painlessly create a bootable USB, and this is exactly what Rufus aims at providing.
- Need a DOS bootable USB to flash a BIOS or some other firmware? Launch Rufus, click the Start button, copy the ROM and flasher files and you're done.
- Have a bootable ISO that you'd like to convert to USB? Launch Rufus, select the ISO, click the Start button and that's it.
A bootable USB tool really shouldn't be more complicated than that!

Rufus Features

Now, while the above can be achieved with other tools (though we believe not as easily) this is what we think makes Rufus stand above the competition:
- Rufus is fast: It is usually quite a bit faster than the competition, especially because we use an internal ISO library (libcdio) while most other tools reuse 7z, which is actually slower than libcdio on extraction. For some speed comparison results, please see here.
- Rufus is small: Why should a bootable USB creation tool be more than 1 MB? Rufus is currently around 150 KB, and still offers ISO support.
- Rufus is simple to use: Its UI is very similar to the familiar Windows formatting dialog, and it doesn't bother the user with options that are confusing or unneeded.
- Rufus doesn't require an installer: An utility that does a simple task, that most users will only perform occasionally shouldn't require an installer. Just download, run it, and get done with it.
- Rufus keeps true to the original ISO content: Unlike other tools, Rufus does not override any of the config files that were set by the original creators - instead it just reuses them.
- Rufus is generic: A bootable USB creation tool should not have to ask its users about the type of ISO provided. This also ensures that the tool will support ISOs that have yet to be created. For a non exhaustive list of bootable ISOs Rufus is known to work with, please see here.
- Rufus can check devices for bad blocks: Up to 4 passes can be selected to find out if your media is defective. We believe that a formatting utility should always come with the ability to check for defects.
- Rufus will detect and set a non US locale (DOS): If the Windows version you use is set to a specific locale, you probably want DOS to use the same. Why should you be constrained to use DOS with an US keyboard? Rufus will detect and set the locale for you (while still providing the option to fall back to US keyboard during boot, if needed).
- Rufus can set an internationalized/extended label: If you format a disk to FAT, being constrained to 11 uppercase English characters for the label is very limiting. NTFS also has its limitations. Rufus can use the autorun/autoplay feature of Windows to display a label that contains any characters you like.
- There's a version of Rufus that comes with native FreeDOS: While slightly larger than the standard version of Rufus (~410 KB) it offers a more modern and much improved version of DOS. Check it out!
- Rufus is 100% Free Source: Rufus is released under GPLv3. If you're a developer and you really would like a new feature added, you very much can!

For additional info, you are invited to have a look at its entry in the downloads section or its official homepage.

For a more technical overview of how Rufus works, please read on.



The utility originally started as a replacement for the venerable HPUSBFW tool and basically offers all the features HPUSBFW has, apart from the ability to provide external DOS files. The reason behind that is that we provide a version of Rufus with FreeDOS embedded, therefore use for external DOS files would be very limited. Thus, Rufus should detect and formats USB drives in pretty much the same fashion as HPUSBFW, except it uses ms-sys to create the DOS or FreeDOS boot sectors.

For ISO9660 and UDF support, Rufus relies on libcdio (which seems much faster than 7zip for extraction) and syslinux. The way isolinux config files are handled is by creating a /syslinux.cfg on the target (if needed) that references an already existing config file. So far, this method seems work very well, apart from a small issue with distros that use obsolete versions of vesamenu.c32. The application will also attempt to update the existing isolinux/syslinux config file, if a disk label is required by the kernel.
With this, the produced USB is as close as possible to the original ISO, while most recent isolinux based bootable ISOs should be supported in a generic fashion.

With regards to Windows support (Vista or later), we simply format the drive as NTFS (which, btw, is the only filesystem that can properly handle the > 4GB install.wim from the x64 version of the Windows 8 developer preview) and use ms-sys to add the NTFS record, along with the bootmgr we pick from the ISO.

Finally, if requested (and if none exists) Rufus can also add an autorun.inf and icon, to set a customized/internationalized label as well as a drive icon.

If you have comments or ideas for improvement, feel free to do so, knowing that:
- I am not planning to create a commandline version of the utility, since I'd rather see features added to it than have it reused in another application.
- I am not planning to look into multiboot. I think multiboot is way too user specific and I don't see a generic solution for it that I could find acceptable. Also, if people need a tool to create a multiboot USB for them, I don't think they should be using multiboot in the first place. This is even more true if a program like Rufus can manage to make it quick and easy to switch between ISOs instead of having to create a multiboot USB.

Right now, the next thing I'd like to support would be BartPE and XP, though this may be a bit of a challenge. I'm hoping that either the ISO's existing SETUPLDR.BIN can be used (even if it needs to be patched) or that ReactOS's freeldr can help. Basically, I'd like Rufus to support anything WinPE based.
I'm also aware about grub4dos and iPXE, though I'm not currently sure whether anything specific should be done there. It looks to me like simply installing a blank syslinux and letting users do the chainloading would be acceptable, especially as I'd like to keep the utility small.

Again, please don't hesitate to give Rufus a try and let me know what you think.]]> Fri, 07 Feb 2014 08:14:39 +0000 http://reboot.pro/topic/16374-rufus-introduction-topic/ http://reboot.pro/topic/19519-winbuilder-20130901-questions/ I know this is not quite the right forum to post this question, but I'm not sure where to post.

 

I just downloaded WinBuilder 2013.09.01 and used the "Auto" command to build an iso.

3 Years ago I has build some Win7PE disks using a previous version of Winbuilder, so I am at a loss to figure out exactly what kind of animal WinBuilder 2013.09.01 is.  Maybe I should stick to WinPE7?

 

I am having trouble understanding a few things.  First of all, I have no idea what programs/utilities/tools the basic Windbuilder iso disk has, and can't seem to find that documented. I am also assuming that it builds a Win7PE disk, but I can't find that documented either.

 

I am primarily interested in a bootdisk that has basic utilities to repair and troubleshoot Win 7 and Win 8 64 bit installations.  However, on the download page, http://reboot.pro/files/file/342-winbuilder/   their is mention of the "INSTALL" command which states: 
"INSTALL - Download and install apps from http://reboot.pro/files"

however when I go to the files page, I have no clue how to use the syntax INSTALL ??? name of what.

 

I would also think that someone may have put together a package of programs to install for various usages, but can't find anything about that either.

 

I cannot find any tutorials on Winbuilder 2013.09.01 in the tutorials section, so maybe I am missing something???

 

One more issue.  I just downloaded Rufus and was trying to use Rufus to create a bootable usb stick with the bootdisk.iso image created when I ran AUTO with windbuilder.  

 

Unfortunately, RUFUS complains: "This version of Rufus only supports bootable ISO's based on bootmgr/WinPE, isolinux or EFI.  This ISO doesn't appear to use either..."

 

So what are you supposed to use to create a bootable USB stick with bootdisk.iso??

]]> Fri, 07 Feb 2014 04:27:22 +0000 http://reboot.pro/topic/19519-winbuilder-20130901-questions/ http://reboot.pro/topic/9959-how-to-make-liveusb-of-current-ubuntu-install/ . I do understand that unetbootin will take a standard iso and turn that into a bootable USB. I also understand that I can do that in Jaunty using System - Admin - USB Startup Disk Creator.

What I'm wondering is whether I can do the following: after making a standard bootable USB, can I then turn it into a duplicate of *my* install by just rsyncing (or using cp -a) all of /usr, /opt, /var, /home, and ??, over onto the USB?

So: make standard LiveUSB + copy over a bunch of dirs = custom bootable USB that would recreate my current install with all the changes and settings I've made?

Compared to the real instructions for making a custom bootable iso, that would be way too easy, so the answer is probably "no"? ]]> Thu, 06 Feb 2014 18:02:08 +0000 http://reboot.pro/topic/9959-how-to-make-liveusb-of-current-ubuntu-install/ http://reboot.pro/topic/19551-rw-everything-for-win8pe-and-win7pe-winbuilder-82/

File Name: RW-Everything for Win8PE and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 06 Feb 2014
File Category: App scripts

Homepage and info:
http://rweverything.com/

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
__________________________________________________

Click here to download this file]]> Thu, 06 Feb 2014 09:07:06 +0000 http://reboot.pro/topic/19551-rw-everything-for-win8pe-and-win7pe-winbuilder-82/ http://reboot.pro/topic/19528-printer-support-in-winpe/ Hi,

 

How can we give the support for printer in winPE?

If i need to add any package or any script at the time when I prepare the .wim file?

 

Details-

I am creating a .wim file with which I boot the pc on network using wds. For particular client I need to print some docs when it boots with my winpe. I have the CD of the printer that is connected to this client(with usb).

If the client is booting with winpe and I have its console on which I can execute the commands, then what should I need to do here for installing the printer drivers.

 

I know the only thing that drvload command is used to install the drives online that takes .inf file path.

 

But its not working. // confused why

 

 

Please help me someway.

 

 

Thanks

MChauhan

]]> Thu, 06 Feb 2014 08:29:29 +0000 http://reboot.pro/topic/19528-printer-support-in-winpe/ http://reboot.pro/topic/19550-chainloading-different-version-of-syslinux-isolinux/ Hi all,

 

This is my first post on reboot.pro. I have been invloved in multibootusb development project quite some time. The project source code is here https://github.com/mbusb/multibootusb. Recently the project has been updated/ migrated to python to make it true cross platform utility. The other download details of older (and new) binaries  can be found https://sourceforge.net/projects/multibootusb/. The project web page is http://multibootusb.org.

 

Enough of the project info.

 

Coming to the real issue. The major plus point of the project is that the dynamic update of syslinux.cfg/ isolinux.cfg files depending on distro type and provide proper link to those files from main syslinux.cfg like this 

CONFIG /multibootusb/slitaz-4.0/boot/isolinux/isolinux.cfg
APPEND /multibootusb/slitaz-4.0/boot/isolinux

This way the boot menu and option of the original iso are kep intact.

 

MultiBootUSB currently uses syslinu version 4 as default boot loader. However, the issue comes when the isos are created with different version of syslinux. As I can see from the syslinux project website, there are currently 3 major versions are maintained 4, 5 and 6. Is there a way to chainload different syslinux/ isolinux (isolinux.bin) version? so we need not have to worry about syslinux version incompatabilities.

 

]]> Thu, 06 Feb 2014 03:05:24 +0000 http://reboot.pro/topic/19550-chainloading-different-version-of-syslinux-isolinux/ http://reboot.pro/topic/17283-re7zip/

File Name: re7zip
File Submitter: Nuno Brito
File Submitted: 24 Jul 2012
File Updated: 11 Feb 2014
File Category: Tools

This tools allows to extract files directly from an archive hosted at a remote HTTP server.

Underneath the hood we use 7-Zip-JBinding library (based on 7-zip) to extract files. This tool was made with the purpose of (for example) extracting a file from a big ISO files somewhere on the Internet without need to download the whole ISO file.

All the archives supported by 7-zip are supported by this tool, this includes:

7z, arj, bzip2, cab, chm, cpio, deb, gzip, hfs, iso, lzh, lzma, nsis, rar, rpm, split, tar, udf, wim, xar, z and zip

Here is the syntax and examples:

Usage:    java -jar re7zip.jar [OPTIONS]

Options:
		  /t  -t    archive filetype:
					  zip, tar, split, rar, lzma, iso, hfs, gzip, cpio, bzip2,
					  7z, z, arj, cab, lzh, chm, nsis, deb, rpm, udf, wim, xar,
		  /a  -a    archive filename or URL location of archive
		  /e  -e    filename to extract out of the archive
		  /l  -l    list content of archive
		  /o  -o    output filename for the extracted file
		  /v  -v    show version info

Example:
		  java -jar re7zip.jar /t=iso
				       /a=http://test.com/test.iso
				       /e=some\file.txt
				       /o=file.txt

		  java -jar re7zip.jar /t=iso
				       /a=http://test.com/test.iso
				       /l

		  java -jar re7zip.jar -t=iso
				       -a=http://test.com/test.iso
				       -e=some/file.txt
				       -o=file.txt

		  java -jar re7zip.jar -t=iso
				       -a=http://test.com/test.iso
				       -l

The tool will run on 32-bit (x86) and 64-bit (x64) version of Windows, MacOS and Linux.

Just to clarify, re7zip does not need administrative permissions and does not need to be installed. It is a single file, just run and have fun!

Source code

The source code can be found at: https://code.google.com/p/re7zip/source/checkout


Credits

Big thanks to Peter Schlang and IceCube for helping so much in making the most recent version possible.



Licensing
This tool is licensed under the LGPL license.


Discussion
http://reboot.pro/topic/17283-re7zip/

Click here to download this file]]> Wed, 05 Feb 2014 17:47:35 +0000 http://reboot.pro/topic/17283-re7zip/ http://reboot.pro/topic/19548-how-to-automatically-batch-extract-multiple-archives-with-passwords/ how To Automatically Batch Extract Multiple Archives with Passwords Link this  http://www.mediafire.com/download/hgtdxjh62xx3c26/Acrobat+Reader+11.7z

]]> Wed, 05 Feb 2014 16:16:16 +0000 http://reboot.pro/topic/19548-how-to-automatically-batch-extract-multiple-archives-with-passwords/ http://reboot.pro/topic/19511-how-to-hide-files-and-folder-in-cddvd/ How to Hide files and folder in cd/dvd

]]> Wed, 05 Feb 2014 14:37:16 +0000 http://reboot.pro/topic/19511-how-to-hide-files-and-folder-in-cddvd/ http://reboot.pro/topic/19546-how-to-boot-vhd-via-pxe/ How to boot windows 7 vhd from pxe network boot.

 

 

i want boot pc from vhd via network. PC has no hdd.

 

 

]]> Tue, 04 Feb 2014 11:43:24 +0000 http://reboot.pro/topic/19546-how-to-boot-vhd-via-pxe/ http://reboot.pro/topic/19529-windows-7-and-81-bootable-usb-problem/ Hello

 

i have a windows 7 enterprise x86 iso with size 2.26 GB

 

and a windows 8.1 enterprise x64 custom iso with size 5.2 GB

 

and a flash memory with size 32gb

 

how can i create bootable usb with those 2 windows ?

 

my flash must ntfs ?

 

i give error when windows start installing ! about driver not found etc...

 

 

thanks in advance

]]> Tue, 04 Feb 2014 10:18:17 +0000 http://reboot.pro/topic/19529-windows-7-and-81-bootable-usb-problem/ http://reboot.pro/topic/18840-isostick-randomly-disconnects/ My ISOSTICK has been serving me well for the past 6 months. I tried using it a few days ago and half way though imaging a computer with it, it disconnected, then a few seconds later it reconnected (as if I had unplugged it and plugged it back in).

 

I figured it was a fluke and tried again.. same thing. Tried it in 4 other computers, same thing, and it's getting more frequent. Now I get about a minute, tops, before it disconnects.

 

I have tried another micro SD card, and tested my normally installed card in another reader -- problem stays with the ISOSTICK (my cards are fine).

 

I am on the latest stable firmware. I suspect I already know the answer (that my ISOSTICK is bad), but was hoping someone might be able to give me a hint/fix.

 

 

The "Warranty" section of the FAQ is vague. It's wording does not actually imply a warranty, but rather a 30-day "happiness guarantee." Is there a warranty? (I have not heard back from support on my trouble ticket yet, and I don't want to have to carry around a stack of CDs again!)

]]> Tue, 04 Feb 2014 00:50:55 +0000 http://reboot.pro/topic/18840-isostick-randomly-disconnects/ http://reboot.pro/topic/19535-repair-win-7/ How to repair windows 7 without lossing data on boot partition ex.  "c drive" .

 

Like windows xp when we press "R " button windows is repaired without lossing data. whats trick to repair win 7.......

]]> Mon, 03 Feb 2014 20:08:02 +0000 http://reboot.pro/topic/19535-repair-win-7/ http://reboot.pro/topic/19532-how-to-true-hide-a-partition/ Is it possible to "true hide" partitions with Grub4Dos?

I've been using Boot-US boot manager for a while and they recommend "true hiding" on multiboot systems with Windows XP, Vista, 7 and 8. Windows will see "true hidden" partition as unformatted (unless you remove the drive letter before "true hiding"):

 

http://www.boot-us.com/gloss08.htm

 

Here are a few screenshots from my system:
 

(hd0,0) - NTFS 3.1, true hidden: http://img38.imageshack.us/img38/9140/08xf.png

(hd0,1) - NTFS 3.1, active: http://img811.imageshack.us/img811/2798/p889.png

(hd0,2) - NTFS 3.1, true hidden: http://img854.imageshack.us/img854/6218/t5t2.png

]]> Mon, 03 Feb 2014 13:28:41 +0000 http://reboot.pro/topic/19532-how-to-true-hide-a-partition/ http://reboot.pro/topic/19533-help-win-xp-on-usb-with-virtual-box/ Hi, I'm on Linux, but I need a Win system, so I trying to make a bootable VHD with Win XP on a external usb-drive with no success...

 

Here my process:

 

1- I started a virtual machine with Win XP on Virtual Box, this VM has 3 partition: A is that for Win XP system, B for the setup of the VHD and C for the VHD and the ISO of Win XP Setup disk.

2- I run VHD_XP_Create and i set as boot drive B and as system drive C;

3- I reboot the VM and I did all the process for the setup of Win XP on the WHD and it worked with no error;

4- When the setup is finished, I copied the VHD on the USB drive and run USB_XP_Fix on the VHD copied and i set the boot drive as the USB drive, no error here.

5- I reboot my real pc and I boot on USB.

6- I load the VHD, but all I have is a black screen;

 

I repeat the process a lot of times, but I have always the same result: a black screen.

 

 

 

]]> Mon, 03 Feb 2014 11:39:45 +0000 http://reboot.pro/topic/19533-help-win-xp-on-usb-with-virtual-box/ http://reboot.pro/topic/19543-graphics-driver/ i made mini 7 and now i boot it via pxe over lan for quality check.

 

i integrate burn test for all testing but here is no sleep option highlight in mini 7 burn test send error no video interface found.

 

Please help me

 

I add many driver following this

 

http://www.windows-noob.com/forums/index.php?/topic/2349-guide-adding-drivers-to-a-custom-winpe-30/

]]> Mon, 03 Feb 2014 05:16:14 +0000 http://reboot.pro/topic/19543-graphics-driver/ http://reboot.pro/topic/19542-installation-problem/ I cleared my HDD and reinstalled Win 7 Ult x86 from scratch, so I got the 100MB system reserved partition as well as the Windows partition. During installation I took a system image with the Win 7 native imaging system and another one with Acronis.  Then I installed Grub4DOS to the MBR, no problem.  When I tried to do a test restore from the pre-Grub4DOS system image the system failed to boot and that is the subject of a thread elsewhere.  Undeterred I restored my Acronis pre-Grub4DOS image and that booted normally and I proceeded to install Grub4DOS for a second time.  Then I got this error -

 

Invalid partition table.  If you still want to install use the --skip-mbr-test

 

The Acronis image should of course have put the system partitions back in exactly the same state they were in at the time the image was created and we know the MBR was OK then.

 

At some point, and I'm not sure whether this was before the first install of Grub4DOS or afterwards, I shrank the Windows partition and created one other primary (intended for Win 8) and an extended logical partition for data.  I used Minitool Partition Wizard 8 for these operations as Disk Management could not achieve the shrinkage I needed.

 

I have deep checked the disk with SeaTools and no issues at all and apart frrom this error there are no indications at all of anything being amiss.  I could use EasyBCD for dual booting and ISO booting but would rather use Grub4DOS as I have done for years.  Any thoughts?

 

 

]]> Sun, 02 Feb 2014 21:41:52 +0000 http://reboot.pro/topic/19542-installation-problem/ http://reboot.pro/topic/19541-thoughts-about-vhds-with-disk-signature-zero/ It has come to my knowledge that at least some vhd files, created by Windows Backup, have all zeroes in the mbr disk signature field. When you attach such a vhd to DIsk Management in Windows (or using "diskpart" or Arsenal Image Mounter etc), you will see that Windows needs to initialize such images with a new disk signature before even reading the partition table.

 

Even though this might not itself corrupt the vhd file in any way, there are still cases where you would like to attach such a vhd file in read-only mode. Simply to read something from a backup without any risk of modifying anything. When mounted in read-only mode, Windows cannot initialize such disks with a valid disk signature and therefore refuses to do anything whatsoever with the vhd.

 

The obvious workaround I have used a couple of times is to create a differential vhd based on the original and mount the diff in read/write mode. But that's not obvious to people and there are sometimes quite a lot of support discussions around Windows Backup / Hyper-V / etc in various forums where people have tried to read things from such vhd files without success and without any clues why it would not work for them.

 

An idea I got was to modify Arsenal Image Mounter driver slightly so that when a disk is mounted in read-only mode, has disk signature = zero but in other respects contains an obviously valid partition table, expected 0xAA55 magic etc, it could fake a random disk signature "on-the-fly" when Windows reads the mbr. Would such a "fix" make sense? Would there be any risks involved, side-effects etc? Any thoughts, anyone?

 

]]> Sun, 02 Feb 2014 15:13:33 +0000 http://reboot.pro/topic/19541-thoughts-about-vhds-with-disk-signature-zero/ http://reboot.pro/topic/18443-uefi-pxe-win7pe-possible/ is it possible to

 

#1 uefi bios -> uefi boot -> SYSLINUX menu -> select win7pe (or maybe ?win8pe?) boot.wim -> install win7 uefi?

 

#2 in order for win7 uefi must the disk be GPT? can it be MBR?

 

#3 yeah that got me thinking, can i use win8pe legacy (pxeboot from syslinux) to install win 7 (legacy)? could possibly solve some of the broadcom driver issues i was having with win7pe.

]]> Sun, 02 Feb 2014 08:58:34 +0000 http://reboot.pro/topic/18443-uefi-pxe-win7pe-possible/ http://reboot.pro/topic/19540-microsoft-knocks-50-to-70-off-dell-lenovo-and-toshiba-windows-81-tablets/

Offer seems good and available till Feb 2,2014 and some till Feb 9

1 tablet sold for $229 , 2 others at $249 32Gb. dell pro 8inch tablet $299 64Gb]]> Sun, 02 Feb 2014 05:15:59 +0000 http://reboot.pro/topic/19540-microsoft-knocks-50-to-70-off-dell-lenovo-and-toshiba-windows-81-tablets/ http://reboot.pro/topic/19518-penetwork-full-of-worms/ What is with PENetwork guys?

 

 https://www.virustotal.com/en/file/00aa9a7bcb60b3f5b40001a61013483e1ce456452fbf06c774d2cb5434f73abd/analysis/1390917627/

 

I scanned the original PENetwork archive from Holger's website, after getting some complaints from an online virusscanner within my LiveXP ISO...

 

 

Can someone clear this? Is this false positive or should we worry about this?

If i read about the worm: W32/Tifaut.B .. it can remote control the LiveXP computer... correct?

 

 

 

 

 

]]> Sat, 01 Feb 2014 22:16:36 +0000 http://reboot.pro/topic/19518-penetwork-full-of-worms/ http://reboot.pro/topic/19537-how-to-enable-aero-glass-effect-in-windows-8x/ Aero Glass for Win8.x

 

http://glass8.berlios.de/

]]> Sat, 01 Feb 2014 19:02:31 +0000 http://reboot.pro/topic/19537-how-to-enable-aero-glass-effect-in-windows-8x/ http://reboot.pro/topic/19536-how-do-i-install-windows-8-metro-style-firefox/ Download firefox-29.0a1.en-US.win64-x86_64.installer
 
 
Metro Style feature is active on the Nightly channel with Windows 8 Touch feature.
 
 
]]> Sat, 01 Feb 2014 18:59:00 +0000 http://reboot.pro/topic/19536-how-do-i-install-windows-8-metro-style-firefox/ http://reboot.pro/topic/16669-multipe-leopard-v2-sp3/ Coming soon! Our group, continues to work for you. Best regards








]]> Sat, 01 Feb 2014 18:23:28 +0000 http://reboot.pro/topic/16669-multipe-leopard-v2-sp3/ http://reboot.pro/topic/19534-hdd-raw-copy-tool-for-win8pe-and-win7pe-winbuilder-82/

File Name: HDD Raw Copy Tool for Win8PE and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 01 Feb 2014
File Category: App scripts

Homepage and info:
http://hddguru.com/software/HDD-Raw-Copy-Tool/

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
______________________________________________

Click here to download this file]]> Sat, 01 Feb 2014 14:40:15 +0000 http://reboot.pro/topic/19534-hdd-raw-copy-tool-for-win8pe-and-win7pe-winbuilder-82/ http://reboot.pro/topic/19531-chenalls-builds-045c-or-046a/ All the latest Chenall's builds of Grub4dos are designated as either 0.4.5c or 0.4.6a. What's the difference between the two?

http://code.google.com/p/grub4dos-chenall/downloads/list


I have picked up the latest build "grub4dos-0.4.6a-2014-01-17.7z" and it seems to be working ok. Is it considered a stable release or a beta?

Grub4Dos project seems a bit confusing for new users. Chenall is listed as an "active member" on the original GNA website which is always picked up first by search engines (see the link below), but for some reason he keeps uploading the latest releases to another website.

https://gna.org/project/memberlist.php?group=grub4dos

 

]]> Sat, 01 Feb 2014 09:20:03 +0000 http://reboot.pro/topic/19531-chenalls-builds-045c-or-046a/ http://reboot.pro/topic/976-scriptpenetwork/ Hi everybody,

here you can find the current information about my "PENetwork"-manager project - primary for LiveXP and Win7PE systems.

The current version you can always download from 'my' personal WinBuilder-website (http://holger.winbuilder.net).

At the moment the most time I'm writing on PENM itself.
However, some older WinBuilder scripts for LiveXP and VistaPE you can still find there.

If you have any questions, suggestions or problems just let me know.

Tested by others and me with Win7 / Vista / XP / W2K3-source and VMWare / VirtualBox / QEmu / RealWorld - thank you all very much

Greets...
Holger

 

Current state:
31.01.2014 (PENM 0.58.2):

- Changed: Recompiled with AutoIt3.3.0.0 to better work with virus scanners
No functional change!

 

08.10.2013 (PENM v0.58.1):
- Fixed: GUIDisable mask option missing

 

07.10.2013 (PENM v0.58):
- Fixed: Missing translation applying after language change for connect menuitem in network browser
- Fixed: After saving new color scheme in profile editor it was not applied to the list of the existing schemes
- Fixed: Window focus on profile deleting in profile editor
- Fixed: Profile deleting in profile editor
- Fixed: Wrong label length calculation in network startup dialog
- Fixed: IP address was not deleted if last item in network browser window was removed
- Fixed: Missing color scheme apply on checkboxes if Windows styles are enabled
- Changed: Profile editor reworked
- Changed: Detailed PE version in debug log
- Changed: Position of tray info window now near the tray icon
- Added: Cmdline parameters /ini= for loading a specified ini file
- Added: Cmdline parameters /profile= for loading a specified profile directly from file
- Added: 'GUIDisable' mask parameter (ini, reg, cmdline) to show only some specific tabs ("Config"/"IP" & "About" are always shown)
- Added: Version infos for WIN_8.1/WIN_2012R2 (WinPE5.0)
- Added: Icon for AC wireless networks in available wireless networks
- Added: More ini options are changable via profile editor
- Added: Simple preview window in profile editor
- Added: Simple check for entered addresses (IP, SM, DG, DNS, WINS) in profile editor
- Added: Simple check for entered MAC address
- Added: Some more visible options to color schemes tab in profile editor
- Added: Key accelerators for profile editor
- Added: Tooltip for profiles file cause file path can be larger to display
- Added: Frame color for diabled buttons now changable via schemes/profile editor

 

Note!: network browsing doesn't work in QEMU by default cause of the buildin firewall

History:

Spoiler

02.01.2013 (PENM 0.58.B11):
- Fixed: Wrong button text for 'No' button if 'FocusNo' option is used
- Fixed: Wrong listing in profile selection dialog
- Fixed: Another drawing problem with tabs if no other program is open and another tab is selected
- Fixed: Profile description field not deleted when selected another ini file
- Fixed: Missing line for clipboard network adapters summary after WINS entry
- Changed: renamed cmdline parameter /autostart to /startprompt because autostart is already set to 'True' by default
- Changed: If a network card is deleted in profile editor the following adapter numbers are decreased automatically
- Added: Right click in network browser for direct connect network
- Added: Experimental simple filter for specific network adapter settings applying
- Added: Some more global ini options to profile editor

 

01.01.2012 (PENM 0.58.B10):
- Fixed: Problem with version string for driver copying process
 

31.12.2012 (PENM 0.58.B9):

- Fixed: Value "FirstRun" not being set correctly after first run
- Fixed: 63 chars limitation of DNS suffix -> 240 chars maximum
- Fixed: Error in subfunction to stop a service
- Fixed: Profiles: computername, workgroup and DNS suffix are not applied on first start under WinPE2.X/3.X (backchanged from Beta 1)
- Fixed: Description field in network browsing not clear on resetting
- Fixed: Wrong subnet mask automatically applied if no IP address was entered
- Fixed: CMDs executing after IP change were the same like after starting network, CMDs for executing after changes were ignored
- Fixed: Tab selected drawing problem if open last page option is used
- Changed: DrvCopy params, OS is ignored by default and used only if one of the CMD parameters is XP, /XP, 2003, /2003, Vista, /Vista, Win7, /Win7, Win8, /Win8
- Added: Keypressing 'Ctrl' + 'Alt' + 'c' OR 'a' in "IP settings GUI" -> copies infos of the selected OR all network adapter(s) (Device, MAC, IP, etc.) to clipboard
- Added: 'StartMode' to hide/show startup procedure - numeric value (0, 1, 2, 3, 4, 5, 6) -> 0 - Don't show, 1 - Center (default), 2 - TopLeft, 3 - TopRight, 4 - BottomLeft, 5 - BottomRight, 6 - Depends on systray position
- Added: Optional setting to save the last position of the main window on the Desktop
- Added: Version string to PENMDrvCopy.log, profile editor and wifi exporter for better detect which version is used in case of problems
- Added: Optional parameter /focusno or 'HKLM\SW\PENetwork\FocusNo' or in .ini to set the focus to the 'No' button on network startup dialog
- Added: Start 'Browser' service if not started for network browsing (needed for)
 

05.01.2012 (PENM 0.58.B8):
- Fixed: Problem with tray info window while reading DNS server string
- Fixed: 15 chars limitation of DNS suffix -> 63 chars maximum
 

15.04.2012 (PENM 0.58.B7):
- Fixed: Crash on 64bit while switching to 'Other' GUI
- Fixed: Missing internal change of an numeric value
 

14.04.2012 (PENM 0.58.B6):
- Fixed: Network adapter state icon not updated correctly if adapter selection was changed and state was the same like for the previous one
- Fixed: Language code detection problem cause of wrong comparing mode
- Fixed: Missing color applying for trace label/checkbox, hops label and result checkbox in Ident GUI
- Fixed: More than 1 DNS servers not shown correctly in different lines in Tray info window
- Fixed: Missing translations
- Changed: Maximum username length to UNLEN (256) and password length to PWLEN (256) in Shares GUI
- Changed: If a 'sharing' user could be added successfully then the password field is always filled with dots, on password input the dots are removed
- Removed: Unused stuff in 'Other' GUI (not finished cmdline things - will be maybe return in 'Profiles' GUI in a later version)
- Added: "LastPage" value to open specific or last used tab on startup
- Added: Using of WMI for applying IP settings (Experimental, needs working WMI under WinPE)
 

04.04.2012 (PENM 0.58.B5):
- Fixed: Wrong Subnetmask generating while changing directly IP in Properties GUI
- Fixed: Language file reading "MainTitle"
- Fixed: Again some more misbehaviour while using tray icon options
- Changed: Info dialog in tray replaced tooltip
- Changed: Old misbehaviour while changing IP adress in adress field
- Added: Network browsing items are now sorted
- Added: Network credentials dialog in network browsing if access to a resource item is restricted
- Added: Network browsing: workgroup/domain name is automatically added on first tab open
- Added: Deleting of created user for share access is possible now
- Added: Trace in 'Computer' tab
- Added: Last used ping/trace address is saved in registry and list is loaded on ping combo click
 

18.03.2012 (PENM 0.58.B4):
- Fixed: Empty IP address return if APIPA is set
- Fixed: Redraw error in editor for button frame color, was always reset to zero
- Fixed: Some misbehaviour while using tray icon options
- Fixed: Network drives tab: wrong connection display in list (state, count)
- Fixed: Network drives tab: connect to longer UNC paths failed
- Changed: WiFi services are only installed/started automatically if 1 wireless network card was detected
- Changed: Tray info, only 1st address on an interface is shown
- Added: Auto importing of WiFi XML files with preferred networks if min. 1 WiFi card was installed sucessfully
- Added: WiFi services are installed/started automatically if not installed yet and a new wireless network card

was inserted/detected (ie. USB adapter), also WiFi profiles are loaded if a network profile was loaded or WiFi XML files exist
- Added: Change WiFi profile position in preferred network list
 

24.01.2012 (PENM 0.58.B3):
- Fixed: Wrong detection of 'NDIS User I/O' driver installation state
 

22.01.2012 (PENM 0.58.B2):
- Fixed: Auto adding of WiFi WEP profile
- Fixed: Wrong profile reading/adding of WiFi autoconnect, hiddenconnect and adhoc type
- Changed: Internal WiFi start/end/install routine
- Removed: Debugging of changed network activity cause of too much lines in debug log file
 

05.01.2012 (PENM 0.58.B1 -> Beta 1):

A new beta version was published.
- Fixed: PE2.X/3.X - computername/workgroup was not set before starting 'wpeinit'
- Fixed: 'Ping' not stopped if you want to change the tab
- Fixed: Re-Applying of nonchanged WiFi profile under WinVista/7/PE2.X/3.X failed
- Fixed: Missing WiFi profile delete function in profile editor
- Fixed: 'NLA' service name now 'NLASVC' in newer OS
- Changed: Internal OS detection and debug infos for OS
- Added: Pressing 'ENTER' in Ping address input field starts/stops pinging and small info whil trying to ping
- Added: OS >= Win7/PE3.X allows showing of local saved WiFi keys
- Added: Logfile can be deleted easily now in 'Other' tab
- Added: 1 line for using bartpe.exe if used standalone under BartPE
- Added: Open profile file with PENM editor in 'Profiles' tab
- Added: Option to choose internal PENM or OS WiFi profile UI (reactivated) for editing
- Added: Some tooltips in 'Profiles' tab for small buttons
- Added: Doubleclick on shares or network drives list open folder with default file manager
 

06.01.2012 (PENM 0.57.2):
- Fixed: Alignment bug in structure SP_DRVINFO_DATA and SP_DRVINFO_DETAIL_DATA
 

05.01.2012 (PENM 0.57.1):
- Fixed: Only first DNS/WINS/DG address is shown DHCP info dialog
- Fixed: Wrong size of structure SP_DRVINFO_DATA and SP_DRVINFO_DETAIL_DATA
- Changed: Some small cosmetic changes (ie. input fields positions in Shares tab)
- Changed: 'Silver' scheme is default scheme and old grey one is 'Classic' now
 

03.01.2012 (PENM 0.57):

After a long time a new version arrived.
- Fixed: 64bit - current WiFi connection mark
- Fixed: Missing Adhoc profile in available WiFi network list
- Fixed: Listview column font misbehaviour
- Fixed: Missing non-broadcast flag on adding WiFi profile
- Fixed: Wrong type saving on adding WiFi adhoc profile
- Fixed: Wrong speed menu items on speed button for some network adapters
- Fixed: Wrong background color on MAC change dialog for current address
- Fixed: Network card detection/install on 64bit
- Fixed: Run commands after initializing network
- Fixed: 64bit - bug in shares GUI, user query
- Fixed: Autoloading of WiFi profiles
- Fixed: File sharing tab wrong type detection of special shares like IPC$, ADMIN$, etc.
- Fixed: GUI size while switching between full and small tabs
- Changed: WiFi profile changing behaviour
- Changed: Tab item behaviour on click
- Changed: Profile editor now saves last used config files
- Changed: Start of main GUI
- Changed: DHCP info dialog
- Changed: GUI refreshing to reduce a little bit only flickering
- Changed: Language strings are set to english defaults before loading another language
- Changed: Small changes for GUI frame colors (Main, Properties, WiFi)
- Changed: Language string now saved in HKCU
- Added: Profile copying in editor
- Added: Profile editor loading file with external editor
- Added: Network browsing in network drives tab
- Added: Profile loading file with external editor
- Added: Profile editor: possiblity to change the GUI frame colors (Main, Properties, WiFi)

 

05.08.2009 (PENM 0.56 / internal 0.55 was unpublished):
- Fixed: WiFi key - now '&', '<', '>' characters will be stored correctly
- Fixed: Internal script bug with some disabled controls - bug not in compiled mode
- Fixed: Missing 'Then' on StartWiFi function
- Added: Window position will be saved and loaded on GUI start
- Removed: Some unused not finished stuff
 

15.07.2009 (PENM 0.54):
- Changed: Internal handling of .icl-file - now using of "PENetwork.icl" in script dir
- Added: Registering of rsaenh.dll after WiFi service installing to connect to
  WPA-PSK/WPA2-PSK networks

 

11.07.2009 - v36 (PENM 0.53):
- Fixed: Wrong color values in profile editor
- Fixed: Missing color scheme elements combo in profile editor
- Fixed: Error while connecting to nonsecured wireless adhoc network
- Fixed: Case sensitive bug in WiFi available/prefered connections list
- Fixed: Wrong color value for WiFi connected list entry save
- Fixed: Case sensitive bug in WiFi direct connect
- Fixed: Wrong DNS/WINS button text after language switching
- Changed: Removed limitation for wireless adhoc network to only connect manually
- Changed: Some internal color handling if controls are disabled
- Changed: Internal color handling for some static controls
- Changed: Sub open/save dialogs parents
- Changed: Now more instances of profile editor/wifi exporter are allowed, also if editor/exporter is still opened WB script will run normally
- Added: Possibility of updating PENM itself in the script directly (similar to script for VPE/W7PE)
- Added: Sample profile ini file included with 2 profiles (DHCP, static) and 2 color schemes (Silver, Dark)

12.01.2009 (v34 - PENM 0.45):
- Changed: RegDelete command changed to RegWrite empty value

11.01.2009 (v33 - PENM 0.45):
- Fixed: Wrong close button text on main GUI after starting network
- Fixed: Missing status label on after minimizing main GUI
- Fixed: Missing icons under Win2003 based PE
- Fixed: Wrong parameter in driver copying process
- Fixed: GUI won't come up if minimized to tray and should restart by shortcut clicking- Fixed: Missing language string in computer ident GUI
- Changed: GUI- Added: GUI colors

16.11.2008 (v32 - PENM 0.44):
- Fixed: double function call with source XPSP3
- Fixed: fonts error after changing IP settings
- Fixed: wrong speed info sometimes in config GUI and wrong DNS in DHCP info GUI
- Changed: APIPA mode back to old behaviour (will later include an option in the profile editor)
- Added: profile reloading/changing GUI
- Added: option to set startup prompt to OnTop window

12.10.2008 (v30 - PENM 0.43):
- Fixed/Changed/Added: a lot of things since v25 (thanks to all for reporting bugs, suggestions and ideas )

01.10.2008 (v29 beta):
- Bugfixing release

20.08.2008 (v01 for VistaPE v11):
With VistaPEv12beta there are some problems I still try to solve so it just takes a little bit to make it also run with the new version.
So cause there are some internal changes there could be some other errors.
Also the WiFi-functions are again in developement - so they not much functional (it should be however possible to connect to aWEP/WPA-PSK private network - tried with Realtek USB stick).
For now you have to create at first a Wifi profile in the 'Prefered networks' tab.
After that you can also change it - in PE20 there is used then the Vista config dialog.
Others:
- Changed: again the driver copy function to work better now with VistaPE.
- Added: debug function now also available in the 'Others' tab to view easier the logfile.

12.08.2008 (v28 beta):
- Changed: some internal stuff to copy drivers (now using of SetupXXXXX-functions from setupapi.dll)

11.08.2008 (v28 beta):
- Fixed: Some things- Changed: Some internal things
- Added: Adapter advanced settings tab

26.07.2008 (v27 beta):
- Fixed: Some things
- Added:additional commands after starting network
- Added: network device speed setting
- Added: network drive mapping
- Added: starting of services even if not network card was found

09.03.2008 (v26 beta):
- Added: XP SP3 support
- Added: MAC changing
- Added: possibility to start sharing and adding users/accounts after starting network (only with using profiles)

18.11.2007 (v0.39):
- Fixed/Changed/Added: some things

18.07.2007 (v0.37):
- Changed: Only a few internal changes
- Added: Network startup countdown
- Added: IP Auto configuration - not set by default, you can set it in the script
-> if "IP Auto configuration" is enabled then if the network adapter could not getan IP from DHCP server the adapter will get the address from the class B network: 169.254.0.0(more infos here)

27.06.2007 (v0.36):
- Fixed: Stop service error
- Fixed: False service state after language switching
- Added: Logfile for processing driver copy -> a logfile is created as "%Temp%\PENMDrvCpy.txt"

22.06.2007 (v0.36):
- Fixed: Missing TABSTOP in profile selector dialog
- Fixed: Profile applying not working if TCP/IP is autostarted while installing
- Fixed: Some device detecting problems (no more other devices than network devices are tried to install)
- Changed: Some internal changes
- Changed: Removed blank password limitation for folder sharing
- Added: Autostart File Sharing- Added: Predefined network drive paths

31.05.2007 (v0.36):
- Fixed: Missed error string in folder sharing
- Fixed: Last selected language not reused after closing
- Changed: Font to DEFAULT_GUI_FONT
- Added: driver files are now also copied from subdirs of the selected driver folder
(- Added: WS_EX_TOOLWINDOW-Exstyle to inf-patching/drv-copying GUI to prevent taskbar entry)

26.05.2007 (v0.36):
- Fixed: IP changing/renewing - Unicode problems
- Fixed: Profile setting if more than 1 available network devices
- Fixed: Starting PENetwork Manager if TCPIP is already installed (i.e. manually or by other tool)
- Fixed: Language not rightly applied to adapter speed string
- Fixed: Removed initest.txt from creating while ini-patching (was just for debugging)
- Changed: Tab order in network drives dialog
- Changed: Some internal GUI stuff
- Added: Simple debug mode - file written to %Temp%\PENMDebug.txt
- Added: Buildin driver copy (cause of missing some additional driver files)

08.05.2007 (still v0.35):
- Fixed: "Profile Creator" Unicode support (also for Profile Selector on startup)
-> best is to create a new profile ini then it's automatically saved as Unicode
- Fixed: Countdown timer on profile selection doesn't stop
- Fixed: Adding of an address deletes 'Other'-tab
- Changed: DHCP-Info-GUI server entries layout- Changed: Some default values from inifile to registry cause of missing WB-unicode ini writing
- Open: "Workgroup" is not used from profile - will solve this bug later in the evening...

06.05.2007 - 2.Upd.:
- Fixed: MessageBox ANSI -> Unicode (i.e. DHCP-Info)
- Fixed: ListView controls with Unicode (tooks me half of the day;))
- Fixed: Error while shuttingdown Windows (enum network adapters false return) (thanks to thunn)
- Changed: Network drive lettes always A-Z

06.05.2007 (v0.35):
- Fixed: Missing network (dis)connect dialog in Explorer (WB-script)
- Fixed: Some missing translation
- Fixed: Missing error messages for network drive connect
- Fixed: Wrong GUI resizing while language changing
- Fixed: Wrong MRU-list number (changed from 16 to 30 max.)
- Fixed: Tray tooltip not updated on just minimizing to tray
- Fixed: Wrong limitation of username length for network drives connect
- Fixed: Profile selection countdown timer in QEMU (timer now using WM_TIMER)
- Open: String placement in DHCP-info dialog in other languages

03.05.2007 (v0.34):
- New: compiled in Unicode-Beta-Autoit-version
- Fixed: Some language depended control settings (GUI title, size, etc.)
- Fixed: Some missing translation
- Changed: Some language dependent control settings
- Added: inf-patching now buildin cause of Unicode-Autoit-version

01.05.2007 (v0.33):
- Fixed: Some wrong IP settings changings effects
- Changed: Main selection from Listview to Tabcontrol for better language support
- Added: Simple language support for the PENM (English/German included - inifiles with ".lng" extension);not profile editor yet

27.04.2007 (v0.32):
- Fixed: Selection of static DNS/WINS/DG with DHCP and static DNS/WINS/DG
- Fixed: False speed detection on disconnected device
- Fixed: Static IP selection in DHCP mode and false device restarting
- Fixed: Network drives MRU
- Changed: Share username inputbox to combobox
- Changed: GUI-redesign
- Changed: Replaced NetUserEnum by NetLocalGroupGetMembers
- Changed: Replaced selfcreated MRU procedure with CreateMRUListW, AddMRUStringW, etc.
- Changed: Profile Editor: Countdown/Default profile
- Added: Network drives used history
- Added: Mouse cursor wait icon while refreshing something (devices, shares, etc.)
- Added: Profile Editor/Profile Selector
- Added: GUI is restored if running in tray or mimized to taskbar - and starting another instance
- Open: Countdown timer doesnt work correctly in QEMU

14.02.2007 (v0.28):
- Fixed: stopping service only stopped dependend services (thanks to TheHive for info)
- Fixed: forcing/checking if "Computer Browser" is running- Removed: Msgbox for starting file sharing (username/password)
- Added: a label with info about username/password to use file sharing

11.02.2007 (v0.27):
- Fixed: missing listbox constants (exe)
- Fixed: shares -> autohiding of input fields (exe)
- Fixed: tray activities item -> checked state
- Changed: if starting "File Sharing" only just one info for putting in username/password (exe)
- Changed: server service stop message
- Changed: closing GUI with OK will not exit PENetwork if "activities showing" is activated/used
- Changed: rechanged tray icon on activities to look more like network activities icon;)
- Added: simple connection activity in tray (only 1 icon - same - like in vista) (exe/script)
- Added: small icon in shares list for reflecting hidden/normal visible shares (idea by "TheHive" - thanks )
- Added: optional "closing to tray" (not fully per script)
- Open: direct network browsing from ie. start -> run

07.02.2007 (v0.25):
- Fixed: network drives path limitation
- Fixed: network drives list too few entries
- Added: sharing of additional folders
- Added: small contextmenu to shares/drives-lists
- Added: browsing network
- Changed: automatically minimize to tray after loading

04.02.2007 (v0.23):
- Fixed: like everytime some small things, you know there is always something to fix;)
- Added: Listing of local shared drives (sharing of additional folders is in progress)
- Added: Network drives dialog (adding/deleting of network drive connections)
- Added: some ini-cmds (like i.e. enable minimizing to tray on GUI-start

31.01.2007 (v0.22):
- fast bugfix release
- Fixed: device detection should now work with LiveXP (only testes with XPSP2, W2K3SP1 crashes here)
- Fixed: registering of netcfgx.dll only if it is not registered (did the registering every time)
- Changed: only 1 instance of the GUI will be running

30.01.2007 (v0.22):- Fixed: some;)
- Fixed: only applying changes to the system if there are some
- Fixed: "workgroup" was reseted to "workgroup" on every start
- Added (script): extract-button to only extract the exe;for the future if there are more changes to the exe than the script itself
- Changed (script): moved automatically starting of PENetwork to Startmenu/Autostart-group- Added (exe): setting computername/workgroup should now work

27.01.2007 (v0.21):
- Published new version
- Fixed some bugs- Added File sharing and simple ping

22./23.01.2007 (v0.21):
- File sharing is finished, needs some minimal optimization but works.

21.01.2007 (v0.21):
- File sharing is working so far 'standalone' - ready to implement

20.01.2007 (v0.21):
- File sharing is in progress
- Ping() is finished so far

Script-screenshot:


Screenshots of PENM at work:

Latest version:

Dark color scheme:

 

]]> Fri, 31 Jan 2014 23:48:15 +0000 http://reboot.pro/topic/976-scriptpenetwork/ http://reboot.pro/topic/19524-overview-about-win8pe-projects/ Hallo,

 

is there any overview about Win8Pe Projects?

 

Please share

 

Xplod

]]> Fri, 31 Jan 2014 22:38:56 +0000 http://reboot.pro/topic/19524-overview-about-win8pe-projects/ http://reboot.pro/topic/19530-ramexpert-for-win8pe-and-win7pe-winbuilder-82/

File Name: RAMExpert for Win8PE and Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 31 Jan 2014
File Category: App scripts

Homepage and info:
http://www.kcsoftwares.com/?ramexpert

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
____________________________________________________

Click here to download this file]]> Fri, 31 Jan 2014 15:35:27 +0000 http://reboot.pro/topic/19530-ramexpert-for-win8pe-and-win7pe-winbuilder-82/ http://reboot.pro/topic/19517-hiderunexe-remove/ I would like to know if it is possible to remove hiderun from the WIN7PE project. I am having a major issue with it and would like to disable it from being installed

]]> Fri, 31 Jan 2014 07:45:04 +0000 http://reboot.pro/topic/19517-hiderunexe-remove/ http://reboot.pro/topic/8168-winvblock/ WinVBlock is a free and open source Windows driver for using virtual disks. These disks appear in the Device Manager and Disk Management. It was originally derived from WinAoE, courtesy of V.

Currently supported are:

• RAM disks
  • Supported for booting from
  • MEMDISK-established
    • Floppies
    • Hard disks
    • Optical discs
  • GRUB4DOS-established
    • Floppies
    • Hard disks
    • Optical discs
• File-backed disks
  • Using the winvblk.exe command
  • Floppies
  • Hard disks
    
    • Supported for booting from via GRUB4DOS mapping
  • Optical discs
    
    • Supported for booting from via GRUB4DOS mapping
• AoE disks
  • Supported for booting from as established by gPXE or another SAN-booting mechanism, or
  • Using the winvblk.exe command
  • Hard disks

You'll find the WinVBlock and AoE drivers attached to my most recent post.

Source code should be available at the Etherboot & gPXE projects, courtesy of their project leader, Marty Connor.

Work on this driver was and is prompted by the discussion found in this thread.

See also: FiraDisk by karyonix. Fine work.

Examples:

Using PXELINUX and the MEMDISK included in the .ZIP file to create a hard disk in RAM
Directory layout:

/tftpboot/

/tftpboot/pxelinux.cfg/

/tftpboot/pxelinux.cfg/default

/tftpboot/memdisk

/tftpboot/RamXP.HDD

/tftpboot/pxelinux.cfg/default file:

DEFAULT ramxp

LABEL ramxp

  KERNEL memdisk

  APPEND raw

  INITRD RamXP.HDD

SYSLINUX, EXTLINUX, and ISOLINUX config-files could be the same as above

Using GRUB4DOS to create a hard disk in RAM
Directory layout:

/menu.lst

/RamXP.HDD

MENU.LST file:

default 0



title RamXP

  map --mem (hd0,0)/RamXP.HDD (hd0)

  map --hook

  root (hd0,0)

  chainloader /ntldr

Using WinVBlock in a Windows XP/2003 PE environment (such as BartPE)

Make sure you include:

• \I386\System32\Drivers\WVBlk32.SYS (or WVBlk64.SYS)

Make sure TXTSETUP.SIF includes:

...

[SCSI.Load]

wvblk32 = wvblk32.sys,4

...

---ORIGINAL POST FOLLOWS---

I swear that I read something about this before, but I am really lame with searching Boot Land. Way, way, too many posts to sort through and never find what I'm looking for. Then again, maybe it's because I never really read it. I guess I'll have to search on searching to find out what I'm doing incorrectly.

Anyway, yeah: Has anyone experimented with establishing a RAM disk from GRUB4DOS, booting that RAM disk to some flavour of XP (full/"PE") and having any version of RAMDISK.SYS pick up the GRUB4DOS-established RAM disk and provide it as the boot volume, thus avoiding our favourite friend STOP 0x...7B?

FYI, I'd really like to start working on an XP driver with just such support, but have to balance the time investment out with some practicality, meaning testing such equivalent functionality, if it already exists in another form.

I don't mean with ramdisk(0) and /rdpath= entries, thanks.

As an aside, there appears to be a blend of .SDI users and others, but I find a plain partition image to be way easier.

Some other "words" for future searchers:

map --mem blah
map blah (rd)
RAMDISK.SYS
Unmountable Boot Volume Prevention

- Sha0 Miller]]> Fri, 31 Jan 2014 07:34:43 +0000 http://reboot.pro/topic/8168-winvblock/ http://reboot.pro/topic/19520-opera-presto-engine-petition/ I am breaking my new no-post Rule for an exception that I find important.

 

If you feel like Opera (the fastest browser on Earth) should deserve a different future from the current Chromium nonsense, or if you hope that a new good browser may come out of the ashes of the Presto engine, please consider signing this petition:

https://www.change.org/petitions/opera-software-open-sources-of-presto-engine

 

Whether it can have any practical effect is debatable, but it may be useful anyway to "send a signal" to the good Norwegian guys....

 

Wonko

]]> Fri, 31 Jan 2014 03:46:42 +0000 http://reboot.pro/topic/19520-opera-presto-engine-petition/ http://reboot.pro/topic/18844-how-to-add-entries-in-the-critical-device-database/ Hi,

 

How should I add entries inside CDDB given an .inf file?

Is there any tool/utility out there which accomplish this or all that is required is few changes in .inf? If yes what those changes should be?

 

Thanks.

]]> Fri, 31 Jan 2014 01:35:21 +0000 http://reboot.pro/topic/18844-how-to-add-entries-in-the-critical-device-database/ http://reboot.pro/topic/19526-what-is-run-between-runonceex-and-run-on-xp-based-pe/
A user reported a problem with my NaughtyPE project. Namely that a message box pops up stating "Installation failed".
Can't remember having this problem 2 years ago, when the project was uploaded. But now i can reproduce it.

The Installation in question happens after the end of RunOnceEx commands, but before the Run commands are executed.

Does anyone know what keys are processed between those two?




PS: There are no further DllInstall commands to be found in the registry outside of the two named Run keys.]]> Thu, 30 Jan 2014 23:09:32 +0000 http://reboot.pro/topic/19526-what-is-run-between-runonceex-and-run-on-xp-based-pe/ http://reboot.pro/topic/13534-when-does-windowsbootmgr-stop-using-bios-intterrupts/
I've got a curious question about how the Windows NT6 startup process works that doesn't seem to be explicitly stated in the docs I've read thus far. The most comprehensive one I've come across is here, and it's basically what I'm referring to.

I had used to think that "the big switch" from real to protected or long mode in the CPU was what prevented access to things like RAM disks created by bootloaders like GRUB4DOS or modules like MEMDISK and similarly invalidted BIOS INT handlers. However after reading that article, knowing that I've chainloaded bootmgr from RAM disks and from SAN via gPXE all via INT 13 hooks, and seeing that bootmgr itself contains code to switch the CPU out of real mode, I'm realizing that WINLOAD picks up an environment that's already in protected mode. From there, it uses BIOS INT 13 to drag things like the SYSTEM hive and HAL and the kernel up from the disk, and then it loads boot start drivers.

And then it enables paging (is this where drivers are required for further disk access?) and passes control to the kernel (and does the kernel require "protection" from a driver to not overwrite a RAM disk here?).

Once the kernel takes control, there's a small litany of processes that occur:

How Windows NT 6's kernel initializes

The Windows NT 6 kernel performs the usual Windows NT kernel initialization steps, that are largely unchanged from Windows NT version 3.1:

• Request the HAL to initialize the interrupt controller.
• Initialize the Memory Manager, the Object Manager, the Security Reference Monitor, and the Process Manager.
• Request the HAL to enable interrupts.
• Start all non-boot CPUs.
• Reinitialize the Object Manager.
• Initialize the "Executive".
• Initialize the "Microkernel".
• Reinitialize the Security Reference Monitor.
• Reinitialize the Memory Manager
• Initialize the Cache Manager.
• Initialize the Local Procedure Call system.
• Initialize the I/O Manager. Initialization of the I/O manager initializes all of the pre-loaded, "boot" class, device drivers.
• Initialize the Process Manager.

The operating system kernel then scans the registry, the in-memory copy passed to it by WINLOAD, for the configured device drivers. It loads and all of the device drivers that are in the "system" class.

The kernel checks the digital signatures of all of the image files from which it loads device drivers, using routines exported from ci.dll, the kernel-mode DLL that provides a set of "code integrity" library functions. (Much of the content of ci.dll is exactly the same cryptographic code that is statically linked into winload.exe, including the 8 hardwired Root Certification Authorities.)

The kernel finally invokes the first user process, the so-called Session Manager Subsystem (SMSS).

I'm assuming that at some point in here, if not before it, INT 13 access and non-driver-protected RAM disks become invalid. Was my earlier hypothesis correct, or is it when the HAL starts its own interrupt handling?

I'm super curious about this because I'm frankly fascinated by the way boot start drivers work and would like to start making a mess of some virtual machines with the Native API by pulling apart WinVBlock and Firadisk, but before I do, I'd like to get to know our good friend 0x7B a little better

Many thanks, and of course, to the New Year

-RulerOf]]> Wed, 29 Jan 2014 18:57:26 +0000 http://reboot.pro/topic/13534-when-does-windowsbootmgr-stop-using-bios-intterrupts/ http://reboot.pro/topic/19521-anyburn-for-win8pe-livexp-win7pe-winbuilder-82/

File Name: AnyBurn for Win8PE, LiveXP & Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 29 Jan 2014
File Category: App scripts

Homepage and info:
http://www.anyburn.com/

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
http://al-jo.net46.net/livexp/livexp2.html
___________________________________________________

Click here to download this file]]> Wed, 29 Jan 2014 17:46:08 +0000 http://reboot.pro/topic/19521-anyburn-for-win8pe-livexp-win7pe-winbuilder-82/ http://reboot.pro/topic/19500-hdd-reliability-study/ http://blog.backblaze.com/2014/01/21/what-hard-drive-should-i-buy/

 

http://techreport.com/news/25940/hard-drive-reliability-study-names-names

 

 

Hitachi does really well. There is an initial die-off of Western Digital drives, and then they are nice and stable. The Seagate drives start strong, but die off at a consistently higher rate, with a burst of deaths near the 20-month mark.

 

]]> Tue, 28 Jan 2014 16:55:21 +0000 http://reboot.pro/topic/19500-hdd-reliability-study/ http://reboot.pro/topic/19085-ext2-volume-manager/

File Name: Ext2 Volume Manager
File Submitter: al_jo
File Submitted: 24 Oct 2013
File Updated: 27 Jan 2014
File Category: App scripts

Homepage:
http://www.ext2fsd.com/

Script tested and working using this guide/project:
http://al-jo.99k.org/Win7PEguide.html
___________________________________________

Click here to download this file]]> Mon, 27 Jan 2014 22:44:47 +0000 http://reboot.pro/topic/19085-ext2-volume-manager/ http://reboot.pro/topic/19410-vss-to-capture-live-logical-disk/ So a little while ago I asked a few questions regarding cloning of a disk whilst it was active;

 

http://reboot.pro/topic/18763-capture-local-disk/

 

Some of these solutions were fine, but none were ideal (mostly either cost or image size).

 

A little more googling into VSS and I found this page;

 

http://blogs.msdn.com/b/adioltean/archive/2006/09/18/761515.aspx#comments

 

In essence what you do is instigate a NTBACKUP on your Windows XP box which in turns creates the shadow copy of your logical disk. Then you can use the Dosdev.exe to assign this a drive letter in the command prompt. When this is done you can use imagex to capture the shadow drive.

 

So far I have been able to create a image and in the process of applying this back to a new disk drive to replicate a bare metal restore.

 

Has anyone done this process before? Apart from the issues that can happen when writing to the disk whilst doing all this are there any other concerns i should be aware of?

 

I will let you know if i am able to use the wim i create as a full backup or not.

]]> Mon, 27 Jan 2014 19:37:12 +0000 http://reboot.pro/topic/19410-vss-to-capture-live-logical-disk/ http://reboot.pro/topic/19515-remove-explorer-icon-from-the-desktop/ I can not for the life of me find which script is creating the explorer icon on the desktop in win7pe se. I want to remove it as it is not necessary and adding clutter.

 

Thanks!

~ND4

]]> Mon, 27 Jan 2014 07:12:43 +0000 http://reboot.pro/topic/19515-remove-explorer-icon-from-the-desktop/ http://reboot.pro/topic/19491-auto-start-program/ Alright guys and gals... i am pulling my hair out....

 

It should not be this damn hard to literally run a little batch file on startup.... how in the world do i do this.

 

Ideally the batch file would run after the network has been setup. I have read the PENetwork has this ability but i cant find it anywhere in the win7pe SE winbuilder setup.

 

At the very least simply run a .bat file on startup thats ALL i need to do.

 

Thanks

 

]]> Mon, 27 Jan 2014 02:53:37 +0000 http://reboot.pro/topic/19491-auto-start-program/ http://reboot.pro/topic/19499-passpasslive/

File Name: PassPassLive
File Submitter: joakim
File Submitted: 20 Jan 2014
File Category: Security

This is a live version of PassPass: http://reboot.pro/topic/18588-passpass-bypass-the-password/

It attaches to lsass.exe and locates module msv1_0.dll and patches it in memory in order to bypass local password validation. No need for a reboot. Just execute it, and any password will be accepted after that for local logins. Domain logins not supported. No binaries on-disk are patched.

Tested on 6.1.7601.17514 and 6.3.9600.16384 both x86 and x64. That means latest version of both archs for Windows 7 / Server 2008 R2 and Windows 8 / Server 2012 R2.

Just for the fun of it

Click here to download this file]]> Sun, 26 Jan 2014 21:34:04 +0000 http://reboot.pro/topic/19499-passpasslive/ http://reboot.pro/topic/19513-µtorrent-for-win8pe-livexp-win7pe-winbuilder-82/

File Name: µTorrent for Win8PE, LiveXP & Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 26 Jan 2014
File Updated: 26 Jan 2014
File Category: App scripts

Homepage and info:
http://www.utorrent.com/

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
http://al-jo.net46.net/livexp/livexp2.html
__________________________________________________

Click here to download this file]]> Sun, 26 Jan 2014 17:22:10 +0000 http://reboot.pro/topic/19513-µtorrent-for-win8pe-livexp-win7pe-winbuilder-82/ http://reboot.pro/topic/19510-tales-of-a-reboot-in-space/ Interesting read about the reboot sequence in the rosetta spacecraft: http://www.newscientist.com/article/dn24910-snoozebutton-glitch-delayed-rosettas-wakeup.html#.UuPz60NwbVM

 

]]> Sat, 25 Jan 2014 17:30:52 +0000 http://reboot.pro/topic/19510-tales-of-a-reboot-in-space/ http://reboot.pro/topic/19509-slimpdfreader-for-win8pe-livexp-win7pe-winbuilder-82/

File Name: SlimPDFReader for Win8PE, LiveXP & Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 25 Jan 2014
File Updated: 25 Jan 2014
File Category: App scripts

Homepage and info:
http://www.investintech.com/resources/freetools/slimpdfreader/

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
http://al-jo.net46.net/livexp/livexp2.html

___________________________________________________

Click here to download this file]]> Sat, 25 Jan 2014 16:42:34 +0000 http://reboot.pro/topic/19509-slimpdfreader-for-win8pe-livexp-win7pe-winbuilder-82/ http://reboot.pro/topic/19376-notepad-universal/

File Name: Notepad++ universal
File Submitter: Mikka
File Submitted: 01 Dec 2013
File Updated: 12 Dec 2013
File Category: App scripts

Notepad++ is a free Notepad replacement that supports several languages. Based on Scintilla, Notepad++ is written in C++ and ensures a higher execution speed and smaller program size.

Confirmed working with both Win7PESE x86 and Win8PESE x86.
This is the best app script available for this program right now.

Best regards
Mikka

Click here to download this file]]> Sat, 25 Jan 2014 13:14:42 +0000 http://reboot.pro/topic/19376-notepad-universal/ http://reboot.pro/topic/19414-chainload-winpe-pxe-uefi/ Hello,
 
I’d like to know how can I chainload WinPE using GRUB2 in UEFI mode.
Let me explain better…
 
We have a PXE environment for BIOS Legacy and UEFI computers. The same server (WDS Windows 2012) is used for both Legacy and UEFI.
 
To boot different OS’s (WinPE, Linux, DOS) in Legacy Mode we’re using PXELinux. There is also a PXELinux Menu to the user choose which OS he wants. To boot WinPE in Legacy mode we use:

MENU LABEL WinPE
  KERNEL Boot/pxeboot.0
  APPEND –
 

Our Legacy PXE environment is working just fine.
 
For UEFI computers, we only use WinPE, so once the computer boots the WDS’s server sends WinPE (x64) without showing a menu to the user. However, now we want to start using Clonezilla in UEFI, therefore after the computer boots we need to show a menu to the user to choose (WinPE or Clonezilla).
I could make the menu work in UEFI with GRUB2. So after the UEFI PXE boot, it’s shown a menu and the user can boot Clonezilla. This is working OK.
 
To chainload WinPE in GRUB2 I’m using:

menuentry "WinPE" {
   insmod chain
   chainloader /Boot/x64/bootmgfw.efi
} 

 
WinPE starts to boot but fail with error code 0xc0000428 (The digital signature for this file couldn’t be verified).
 
Does anymore know how to chainload WinPE correctly in UEFI?
 
Thanks,
Leandro Paulin

]]> Sat, 25 Jan 2014 05:04:21 +0000 http://reboot.pro/topic/19414-chainload-winpe-pxe-uefi/ http://reboot.pro/topic/19507-peerblock-12-for-win8pe-win7pe-winbuilder-82/

File Name: PeerBlock 1.2 for Win8PE & Win7PE (Winbuilder 82)
File Submitter: al_jo
File Submitted: 24 Jan 2014
File Category: App scripts

Homepage and info:
http://www.peerblock.com/docs/faq#what_is_peerblock

Script tested and working using these Winbuilder projects/guides:
http://al-jo.net46.net/Win7PEguide.html
http://aljo.comeze.com/win8pe/Win8PEguide.html
___________________________________________________

Click here to download this file]]> Fri, 24 Jan 2014 13:13:30 +0000 http://reboot.pro/topic/19507-peerblock-12-for-win8pe-win7pe-winbuilder-82/ http://reboot.pro/topic/19489-unetbootin-cant-find-sandisk-cruzer-edge-16gb/ Hi there,

 

I bought a Sandisk Cruzer Edge USB-stick with 16GB.( http://www.sandisk.de/products/usb/drives/cruzer-edge/?capacity=16GB ) BIG MISTAKE..! 

 

Looks like (because of some weird Win8 compatibility) it got no removable media bit set and

it is detected as fixed harddrive.

 

Unetbootin can't detect the USB-stick neither under fixed disks and USB-drives and now I sit

here under Win7 x64 ultimate and can't prepare a stick to boot Ubuntu or similar distro.

 

Any idea what do to? I can't find any tool to set that removable media bit. It got VID: 0781 PID: 556B

 

regards

]]> Fri, 24 Jan 2014 10:21:03 +0000 http://reboot.pro/topic/19489-unetbootin-cant-find-sandisk-cruzer-edge-16gb/ http://reboot.pro/topic/19498-bsod-0x7b-when-changing-win-7-usb-installation-to-ahci/ I used the NT 6.x fast installer to install windows 7 ultimate 32-bit to an external hard drive. This all went fine, and it ran on my laptop fine (after I moved it to a USB 2.0 port rather than a USB 3.0 one).

 

Then, since I have 8GB RAM, I decided to re-install with the 64-bit version of Win7 ultimate. Then when I tried to boot from my laptop, I got BSOD 0x7B during boot. After much trial and error, I found out that I could boot it by changing the SATA mode to IDE. However I want to be able to leave my SATA mode on AHCI (for the other OS). So I tried many different methods (most only differing slightly) to change to AHCI. These methods mostly consisted of changing the msahci service to Start=0.

 

No matter what I do, I still get BSOD 0x7B when in AHCI mode. I have tried adding my device to CriticalDeviceDatabase, to no avail.

 

What could be causing this, and how do I fix it?

 

Note: I followed the exact same installation procedure for the 32 and 64 bit versions. It beats me as to why the 32-bit version worked.

]]> Fri, 24 Jan 2014 09:54:54 +0000 http://reboot.pro/topic/19498-bsod-0x7b-when-changing-win-7-usb-installation-to-ahci/