echo some_file_1       %@time%
find --ignore-floppies --ignore-cd /some_file_1.tag

echo some_file_2       %@time%
find --ignore-floppies --ignore-cd /some_file_2.tag

echo some_file_3       %@time%
find --ignore-floppies --ignore-cd /some_file_3.tag

echo some_file_4       %@time%
find --ignore-floppies --ignore-cd /some_file_4.tag

echo end               %@time%

The displayed times look like this
13:07:14
13:07:47
13:08:18
13:08:50
13:09:23

2 minutes 9 secondes every time i boot is a long delay in my book.
The delay for each find instruction has a "constant" average time of 32 secondes.

The places where i expect to find the tags are on:
USB stick    8 GB
HDD        931 GB
HDD        931 GB
HDD         78 GB

To reduce this waiting/wasting time, i will make loops with
if exist (hdx,y)/some_file_z.tag
Unless someone has a better alternative

good day

p.s.
set /a grub_version = *0x8278 & 0xFF && echo gv %grub_version%
gives
gv 157

i tried running a program i downloaded (my kaspersky scans showed that the exe and all related files were clean. kaspersky was wrong.) then, my computer stalled and became extremly laggy. kaspersky reported infection in my temp files. 

parts of the kaspersky GUI where not responsive. mouseover and clicking on the tools i needed were not responsive, however i was i able to move back and forth between pages. by now kaspersky had started an "advanced disinfection", and reported that it detected an infection in temp

folder. as usual, the infected file didnt exist at the specified location.

the "advanced disinfection" finished.

pc then began to reboot.

now it is booting into "grub4dos".

how do i get it to boot into windows normally?

thanks in advance

jenson

I am trying to add some drivers to WIn8 PE4 image when I add the driver offline using the method:

Dism /Mount-WIM /WimFile:c:\winpe_x86\winpe.wim /index:1 /MountDir:c:\mount
Dism /image:C:\mount /Add-Driver /Driver:"....inf"
dism /unmount-wim /Mountdir:c:\mount /commit

and it give me a success message but when I boot the image the driver are not installed !

once I add them online using

drvload.exe "path.inf"

The system can see them,

Am I missing something here how can I add them offline and find them ready to be used when boot?

Thanks

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!

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.

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.

Y:.
|   bootmgr
|   
+---boot
|       BCD
|       BOOT.SDI
|       
+---isolinux
|   |   boot.msg
|   |   chain.c32
|   |   isolinux.bin
|   |   isolinux.cfg
|   |   ldlinux.c32
|   |   libcom32.c32
|   |   libutil.c32
|   |   memdisk
|   |   vesamenu.c32
|   |   
|           
\---sources
        boot.wim

label re
menu label <^5> Boot Recovery Environment
com32 chain.c32
append fs ntldr=/bootmgr

I have also tried

append fs ntdlr=bootmgr

Which gives the same error.  However if I try

append boot ntldr=\bootmgr

I get the following screen:

No MBR magic.
WARNING: Treating disk as raw.
BPB detection (sect): unknown
Booting...

And then it sits there forever.  I'm using the latest version of isolinux (5.01).  Any help is greatly appreciated!

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!)

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/

I want to enter the amount of RAM to allocate.

I want to assign a drive letter.

Then click OKAY.

Then I want to see the RAM Drive in My Computer.

Pretty simple, eh?  But maybe the GUI isn't there yet?

So, I'm a dummy.  What are the step by step instructions to do this.

Here's the idea:

Download the software from here:   _(url)________

Place it on your hard drive here:  _____________

Run it by doing the following:  _____(double click icon?)___________

Enter the amount of RAM to allocate:   __GB

Enter the Drive letter to assign:  __

Click Okay.

Now look in My Computer to see your new RAM drive.

(Windows 7 Professional, 64-bit)

Here is another option:  Click this button to completely deallocate / remove the RAM Drive.

The simpler it is the more people will use it and recommend it to others and hopefully donate to the cause.

Thanks.

title Start Linux
root (hd0,n)
kernel /boot/kernel_name root=UUID=[...] [other kernel parameters]
initrd /boot/initrd_name

The problem is that it's very "static" (instead of "dynamic"). If I change the Linux kernel I have to modify it manually. It's not a big issue to change some numbers (most of the times) but still...
Another thing: if there is more than one kernel to be able to show options to boot with each one (a menu entry for each one).

What I've done so far:

In menu.lst I add:
 

title Start Linux from USB drive
set FOUNDS=0
set FOUNDM=0
call /findkrnl.g4b
if "%FOUNDS%"=="1" kernel /boot/%KERNEL% root=UUID=[...] [kernel parameters] && initrd /boot/initramfs-%KERVER%.fc18.i686.img && boot
if "%FOUNDM%"=="1" write (md)0x220+8 %FK1%%FK2%%FK3%%FK4%%FK5%%FK6%%FK7%%FK8%%FK9%%FK10%title\r\nroot\r\ntitle Return to main menu...\r\nroot (bd)\r\nconfigfile /menu.lst\r\n\0 > nul && configfile (md)0x220+8
root (bd)
configfile /menu.lst

Adding "configfile /menu.lst" to the end seems redundant but it is necessary so the menu entry should be selected with the up/down keys. Without this line you can't select it; you'll have to use left/right keys.
Is there a better "workaround"?

Also, adding "&& boot" seems redundant since it's not usually needed but in this case Linux won't boot because of the "configfile /menu.lst" line...

findkrnl.g4b:

!BAT
clear
find --set-root --ignore-floppies --ignore-cd uuid () [...] > nul || echo Linux partition not found! Returning to main menu... && pause --wait=5 && goto :finish
ls /boot/ > (md)0x220+8 || echo /boot not found! Returning to main menu... && pause --wait=5 && root (bd) && goto :finish
cat --locate=" vmlinuz-" (md)0x220+8 > (md)0x300+1 || echo kernel not found! Returning to main menu... && pause --wait=5 && root (bd) && goto :finish
cat --skip=1 --locate=" " (md)0x300+1 > nul && goto :multi
cat --skip=1 (md)0x300+1 | set VMPOSB=
debug -1
set /a VMPOSB=0x%VMPOSB%+1
debug normal
cat --skip=%VMPOSB% --locate=".fc18.i686" --number=1 (md)0x220+8 | set VMPOSE=
if "%VMPOSE%"=="" echo kernel not found! Returning to main menu... && pause --wait=5 && root (bd) && goto :finish
debug -1
set /a VMLEN=0x%VMPOSE%+10-%VMPOSB%
debug normal
cat --skip=%VMPOSB% --length=%VMLEN% (md)0x220+8 | set KERNEL=
if not exist /boot/%KERNEL% echo kernel not found! Returning to main menu... && pause --wait=5 && root (bd) && goto :finish
debug -1
set /a KERVERB=%VMPOSB%+8
set /a KERVERL=0x%VMPOSE%-%KERVERB%
debug normal
cat --skip=%KERVERB% --length=%KERVERL% (md)0x220+8 | set KERVER=
if not exist /boot/initramfs-%KERVER%.fc18.i686.img echo initrd not found! Returning to main menu... && pause --wait=5 && root (bd) && goto :finish
set FOUNDS=1
goto :finish
:multi
set SKIPPED=1
set ENDPOS=0
set N=1
:loop
cat --skip=%SKIPPED% --locate=" " --number=1 (md)0x300+1 | set LE=
if "%LE%"=="" goto :le0
debug -1
set /a ORGLE=%LE%
set /a LE=0x%LE%-%SKIPPED%
debug normal
cat --skip=%SKIPPED% --length=%LE% (md)0x300+1 | set VMPOSB=
debug -1
set /a SKIPPED=0x%ORGLE%+1
debug normal
goto :endle
:le0
cat --skip=%SKIPPED% (md)0x300+1 | set VMPOSB=
set ENDPOS=1
:endle
debug -1
set /a VMPOSB=0x%VMPOSB%+1
debug normal
cat --skip=%VMPOSB% --locate=".fc18.i686" --number=1 (md)0x220+8 | set VMPOSE=
if "%VMPOSE%"=="" goto :finish
debug -1
set /a VMLEN=0x%VMPOSE%+10-%VMPOSB%
debug normal
cat --skip=%VMPOSB% --length=%VMLEN% (md)0x220+8 | set KERNEL=
if exist /boot/%KERNEL% goto :ifkerx
if "%ENDPOS%"=="1" goto :endloop
cat --skip=%SKIPPED% (md)0x300+1 > nul || goto :endloop
goto :loop
:ifkerx
debug -1
set /a KERVERB=%VMPOSB%+8
set /a KERVERL=0x%VMPOSE%-%KERVERB%
debug normal
cat --skip=%KERVERB% --length=%KERVERL% (md)0x220+8 | set KERVER=
if exist /boot/initramfs-%KERVER%.fc18.i686.img goto :ifintx
if "%ENDPOS%"=="1" goto :endloop
cat --skip=%SKIPPED% (md)0x300+1 > nul || goto :endloop
goto :loop
:ifintx
set FK%N%=title start Linux with %KERVER% kernel\r\nkernel /boot/%KERNEL% root=UUID=[...] [kernel parameters]\r\ninitrd /boot/initramfs-%KERVER%.fc18.i686.img\r\n
set FKV%N%=%KERVER%
debug -1
set FOUNDM=1
set /a N=%N%+1
debug normal
if "%N%"=="11" goto :endloop
if "%ENDPOS%"=="1" goto :endloop
cat --skip=%SKIPPED% (md)0x300+1 > nul || goto :endloop
goto :loop
:endloop
if "%FOUNDM%"=="0" echo No valid boot files found! Returning to main menu... && pause --wait=5 && root (bd) && goto :finish
if "%N%"=="2" set FOUNDM=0 && set FOUNDS=1 && set KERNEL=vmlinuz-%FKV1%.fc18.i686 && set KERVER=%FKV1%
:finish

It works almost fine.
I would appreciate any tip to help me improve speed, accuracy, memory usage and so on.
Also I'm trying to find a way to show the menu entries in ascending order, from the oldest kernel to the newest.
I know how to do a "bubble sort" but the problem is comparing the strings (FK%N%).
First I will have to divide them into "parts":
3.9.2-200 >> 3 9 2 200
But I couldn't find a function to search for a character or a substring in a string. "cat" would of been great but it works only with files...
After that I will have to compare each of the corresponding "parts". The problem is that I don't know a way to find if a value is higher or lower than other value, only to know if they are equal or not.

Could you please help me with these...?
Thank you.

Regards, David

• Format USB-stick like a Bootable Harddisk Drive with NTLDR BootSector
  using PeToUSB or HP USB Format Tool
  
• Select from the Main Menu of USB_MultiBoot.cmd
    1 - Give XP Setup Source Folder and give UserData for XP Setup
    2 - Give USB-Drive Target
    3 - Make Bootable USB-Drive with XP Setup Folders

• P) - PeToUSB - FAT Format - Max 2 GB
  To Format USB-Drive  : Enable Disk Format with LBA FAT16X
  Do NOT Select "Enable File Copy" of BartPE File Copy Options.
  FAT Format Supports Direct Booting with MS-DOS using MULTI_CONTENT
  Installing XP from USB takes 30 minutes - Buffalo FireStix 2 GB
  
• H) - HP USB Disk Storage Format Tool V2.0.6 - NTFS Format - use X_CONTENT
  NTFS Format Supports DOS Boot Floppy Images via GRUB4DOS Menu
  Installing XP from USB takes 16 minutes - Corsair Flash Voyager 4 GB
  Do NOT use the HP Tool for USB-Harddisks having more than 1 Partition
  WARNING -  HP Tool Formats whole Disk - Second Partition is Lost
  
• N) - No Format - Use USB-Drive with FAT or NTFS formatted by Windows XP
  Or Update Existing Bootable USB-Drive having NTLDR Bootsector

• Remove all other Removable Drives, like USB Backup Harddisks and Memory Cards
  This will enable that your Computer Harddisk in XP Setup gets DriveLetter C
  
• Boot with the USB-Drive plugged in and Press [Delete] key or F2 to Enter BIOS Setup
  Your BIOS may use a different key for starting BIOS Setup.
  
• Change BIOS Boot Priority Settings: (your USB device is listed as Harddisk)
  Make First Boot Device Type is Harddisk and give your USB device the First Priority of Harddisks
  
• Boot from USB-Drive and Select  1. Begin TXT Mode Setup Windows XP
  Use Only C: Drive of Computer Harddisk as Partition for Installing Windows XP
  and then Select Quick Format with NTFS FileSystem, XP Install is Automatic
  
  ***** NEVER UNPLUG USB-Drive ***** Until After First Logon of Windows XP
  
• New Harddisk and Creating Partitions after Booting from USB-Drive:
  Direct after Deleting and Creating New partitions, Quit XP Setup with F3
  OR Switch OFF your Computer and Boot in any case from USB-Drive again and
  Run 1. TXT Mode Setup again so that DriveLetters get their Correct Value
  So in this case one Boots ** TWICE ** in the TXT-mode Setup XP
  
• USB_MultiBoot.cmd can make USB-stick to be seen in XP Setup as Boot Drive U:
  In this preferred case the driveletters of Harddisk Partitions and Optical Drives
  will get there desired normal value.
  Otherwise the USB-stick will get Drive Letter D: and other drives will get shifted drive letters.
  
  The same shifting of drive letters  occurs for Installing from USB-Harddisk,
  for which it is not possible to make it seen as Boot Drive U: by changing migrate.inf
  After First Logon there is only 1 USB-Harddisk partition visible as a Removable Drive.
  After Reboot for Second Logon then all partitions of USB-Harddisk will become visible
  as Fixed Local Drives and the highest partition number of USB-Harddisk will get DriveLetter D:
  This reversal and use of DriveLetters might be unwanted and consequently
  the use of USB-stick for XP Setup is Preferred
  
• NON-STANDARD INSTALLS OF WINDOWS XP AND INSTALL OF WIN2003
  Install of Windows XP from bootable USB-Drive
  next to WINDOWS on the same or on a different partition of the harddisk,
  is possible by proper manually adjustment in advance of the BOOT.INI file on the USB-Drive.
  
  Adjust BOOT.INI on USB-Drive: ( Or Select Correct boot.ini Using Option B in Menu Screen )
  For Install on the Second Partition,  change partition(1) in partition(2)
  For Install Next to WINDOWS,  change WINDOWS to
  what will be used as Install FolderName, e.g. WINDOWS.51
  Windows Install Folder Name required according to MS-DOS 8.3 format
  
  So these non-standard installs are still possible,
  but require only small changes in the BOOT.INI on the USB-Drive in advance.
  Otherwise an ERROR Message for Setup of WINDOWS XP:  WINDOWS\system32\hal.dll file missing
  will orccur on Reboot for GUI Mode.

[Boot Loader]

timeout=20

Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS

[operating systems]

C:\btsec\XPSTP.bs="1. Begin TXT Mode Setup Windows XP, Never unplug USB-Drive Until Logon"

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 0 - Part 1" /FASTDETECT

multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 1" /FASTDETECT

multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 2" /FASTDETECT

multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 3" /FASTDETECT

multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 2 - Part 1" /FASTDETECT

I'm stumped.

Rogstern

• 
  Fixed error caused by tails and android
  
• fixed internet problem connections
  
• fixed others various errors
  
• fixed others graphic errors
  
• Update support to new Panda
  
• Change the name of Macrium reflect from Rescue.iso to MacriumRescue.iso
  
• Added Anvi Rescue CD

    I started using PStart as a start-menu replacement in windows 8. I have a lot of portable programs. Generating the PStart.XML file for all of them was a bit tedious. I decided to write a cmd script. Then I decided to make a more general purpose program.

    Basically, fn2txt allows the user to select files using a mask; for each file found, a number of text lines can be generated in a file. The text line can contain the name  (and/or directory, path, extension) of the selected file. The format of the text lines is provided in a ini file.

    More information & download : https://sites.google.com/site/gbrtools/home/software/fn2txt/fn2txt

    Comments & suggestions welcome.

AviraAntivir, VipreRescue, Clamwin, SpybotSD, Malwarebytes, AVZ + some other small utilities is here:

http://al-jo.zxq.net/avir/Win7PEavirguide.html

I´m new to imdisk and I´m trying to create a virtual drive with VB.NET.

I tried something with the following code:

Imports LTR.IO.ImDisk.ImDiskAPI

Public Class Form1
    Private Sub Button1_Click(sender As System.Object, e As System.EventArgs) ...
        Dim deviceID As UInt32 = UInt32.MaxValue
        CreateDevice(10485760, "L:", deviceID)
        CreateMountPoint("L:", deviceID)
    End Sub
End Class

The drive was created and Windows detected it and informs me that I have to format the drive. But if I want to do that an error occurs: "The drive can not be formatted. Make sure that the disk is properly inserted and is not write-protected and try it again."

I think that my code is not complete.

The drive letter L: is not used of course...

Or rather: I need a little tutorial how to create a virtual drive via VB.NET.

Thank you all for your suggestions! Please ask if you have questions.

This bug seems to be caused by the ISO file getting saved twice while xboot is copying the files, what I'm going to say next is the simplest way I have found to get the file size back to where you thought it should be.

I simply use MagicISO maker, though you can use any program that lets you make/edit ISOs.

Simple open the new multiboot ISO you made with xboot in the program you have chosen to use.

Simply delete the extra "images" folder in "/images" (i.e. /images/images).

Save the ISO, verify the size of the ISO and make sure it is still marked as bootable.

Now your ready to burn the ISO to the media of your choice!

If this helps you out let me know.

I'm not profession Soft-Ware Engineer in computer filed.My English is Poor I.m sorry,.

My brother running computers Import/Export business,.I make may software for my Elder brother,.

There are may computers  who have faults,there is no time for instillation windows driver instillation  etc,.computer have common problems which occurred after instillation or driver instillation or stacking or wifi device or sound not in speakers or bios or ram etc,.I search on internet but i cnt find any topic.

It makes big  loss if computers have faults,.

This is reason that I think portable windows for computer checking.,.

We need

1)Windows 8 or 7or vista ISO 2) v mare (rec) or V box 3) disk copy of   Ease-US companies HOME edition

4)USB data traveler 16-GB or SSD 80/256 USB drive (rec)

1)Install  vmare create VHDD partition capacity of USB not less than 8GB

2)load Windows 8 and install on vmare VHDD but first make partition of v mare VHDD before instillation.

3) Enter windows key click next

4) New instillation 

5)                                                 Warning             ,.Do not delete created partition

6)Make only one partition do not delete  and create windows system 350 MB partition. 

7)Click next 

8) Progress goes 1 to 100

9) Change the Windows ISO to Copy Disk ISO

10)After booting click vmare USB enable your requited.which USB you want install windows 

11)System boot make sure you enable usb vmare to detected.

12)Copy ISO boot select Copy Image first option

13)a window open click next

14)if you usb detected than copy partition option enabled

15) click next

16) ask for source drive its always up in the list

17)select first than click next

18)ask for destination drive select usb click Next

19)it say warning overwrite data on drive click next

20) Its begin USB 16 GB take 58 MINTs and SSD USB take 12Mint if Vmare drive 16-GB

21)reboot and run pc from usb Boot it working

22) USB of take 5 hour to install win8 SSD take 30 mints,.

Every computers drivers windows detected Install it.If not than driver pack solution with keyboard n mouse recorder programmed auto install it,. 

I add driver solution pack,hard ware checking tool,bios checking,youcom,. 

It makes check each computer only in few mints,. A portable windows 8 ready for all pc,.

If my pc had deep freeze progam and I forget password for deepfreeze.IS there any way to remove deepfreze password by using WIN7PE????

In advance apologize for my English.

I am just about to finding the best solution for my goal which is to build a multiboot ISO toolkit on usb stick.

So far I used Sardu and it does the job but it is little bit complex.

Yesterday I tried to test Xboot  v1.0beta14 and I was very impressed with its easy to use interface.

Unfortunately I have encountered on  few problems and I hope someone from the Xboot experts could help me and deal with these problems very easily.

Please see details of my testing with XBoot.

USB stick was formatted as a fat32 and selected bootloader was Syslinux (Recommended)

At the end of creating on my local PC (Win 7 Ultimate 32-bit) Multiboot USB I got the final confirmation that USB was created successfully and I could check my compilation in QEMU emulator. Also checked in real mode on that PC and all worked excellent.

But….

Thereafter I tried to start up my new magic usb stick from my both laptops  (64-bit operating systems (win7 and xp)) and my luck has ended up on  “SYSLINUX 4.04 EDD 2011-04-18  H. Peter Anvin et al”

I found on the internet that formatting usb a as fat instead of fat32 should resolve this problem. So I did it but after booting up usb stick my luck has stopped (frozen) again but this time on the Xboot menu with no options to do anything except power off my laptop. Exactly the same happen on my second laptop.

I thought that the problem is related to 32 or 64-bit platform, so I did the same procedure on my 64bit laptop but unfortunately the same problem persists.

So, if someone kind had experienced similar issues or know how to fix these problems and joy the power of Xboot I would be very grateful for help.

Regards,

Kristof

What I am able to get is my computer to boot to the iso specified in the iso_filename.txt  But no matter how many times I reboot there it just boots back to that iso never to a selection menu.  When booted into windows, I can change the iso named in iso_filename.txt and the virtual CD drive will switch to it.

I've tried both the 1677 and 1658 firmware. And have followed several FAT32 formatting tools mentioned here in the forums.

I feel I must be missing something obvious, but I'm apparently too dense to see it!

i used Indisk since years with out any problem. It worked suprep.

But now, on my new Win7/64 16GB machine...

Some time it worked too the, but since a few days:

I always run into BSOD since some days when trying to mount any iso,img,vdi (does not matter what i do and use using the GUI do not work either)

To my surprise: the BSOD says it is writing a dump, but there is no minidump or dump.

Got

early BSODs with

0x000000D3

And most often(always now

0x000000C1 “Special_Pool_Detected_Memory_Corruption”

I installed (and removed) MUTT (Microsoft USB Test Tool) and drivers for Renesas 2.x and 3.x USB3.0-Cards

(drivers are removed and cards are unplugged from PCIe slots)

Memory is reduced to 4GB, CPU ist still a Xeon with 4x2 kernels.

Installed 1.7.2, remove it, reinstalled 1.6: No change.

(Removed driver by manually renaming then as the uninstaller signals only an error....)

Event log is clear. Nothing except that it was shutdown unexpectetly...

Using WinCDemu to mount iso works, but i need to mount a floppy image...

I have no other problems with the box (Intel D3067-A1 mother board with Xeon)

Steps to reproduce:

To cause th BSOD immediately a

imdisk.exe -a -t vm -m X: -s 640M -p "/fs:ntfs /v:RamDisk /q/c/y"

is sufficient. (Found that line somewhere in the www)

To do it with delay:

DiscUtilsDevio gives after some time (approx. one or two minute)  a BSOD.

c:\>cd “c:\Program Files (x86)\ImDisk “

c:\Program Files (x86)\ImDisk>DiscUtilsDevio.exe /mount=q: /filename="O:\ISO\Arconis2013.iso"

Opening image O:\ISO\Arconis2013.iso

Image type class: DiscUtils.Optical.Disc

Unknown partition table format or partition table not found.

Image virtual size is 309592064 bytes

Image sector size is 2048 bytes

Partition table not found.

Using entire image file: O:\ISO\Arconis2013.iso

Used size is 309592064 bytes

Read/write mode.

[“hangs” until CNTL-C]

Other shell i can’t asccess the drive:

C:\Windows\System32>dir q:

Auf dem Datenträger befindet sich kein erkanntes Dateisystem.

Stellen Sie sicher, dass alle benötigten Dateisystemtreiber geladen sind und das

s der Datenträger nicht beschädigt ist.

After terminating the mount command with cnd-c the shell with

C:\Windows\System32>dir q:

hangs.

       My question is--and I know this is overly broad--what are the differences between LiveXp and a full install of the operating system? Also is it possible to modify the build to make these porable programs work?

       My other thought was that if I can't run Portable OUtlook in LiveXP, what about running it in Portable VirtualBox under LiveXP? What adjustments would I need to make to get PortableVirtualBox to run?

       Basically what I'm trying to do is create OUtlook on a key that will run on any PC without depending on the native OS.

Thanks in advance for any suggestions.

Rogstern

Here is one, did you know that grub4dos can prompt for a string with a timeout...

set name=
set /p:3 name=Please enter your name within 3 seconds : 
if "%name%"=="" pause --wait=2 Sorry - not quick enough && halt
echo Well done %name%!

I think this has been in the chenall build for quite a while (I have not checked older builds).

powercfg -h OFF

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

Here's an example screenshot:


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

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

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

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

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

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

cd C:\Temp\PE4

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

md C:\MOUNT

10. To mount the WIM file, type:
 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You can add multiple drivers by typing:
 

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

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

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

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

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

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

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

      NOTE for people building a 64bit WinPE4.0:

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

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

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

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

wpeutil.exe WaitForRemovableStorage
wpeutil.exe UpdateBootInfo

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

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

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

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

Type the following command:
 

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

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

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

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

Here's an example of my PStart menu:


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

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

      

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

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

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

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

I noticed that, if I enable the UEFI in a virtual machine in VMware Workstation 9.x, the Plop Boot Manager 5.0.15-test (plpbt.iso) does not start. How come?

Thanks

Bye

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 --mem /XP3_1210W.iso (0xff)
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
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 /XP3_1210W.iso
map --mem /XP3_1210W.iso (0xff)
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --hook
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

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?

Here are some ports of common GNU utilities to native Win32. In this context, native means the executables do only depend on the Microsoft C-runtime (msvcrt.dll) and not an emulation layer like that provided by Cygwin tools.

Of course it simply works for the simple chore that it works for .

Not a highly sophisticated detect engine tested for years on any possible .dll, only tested some 15 minutes on a few example ones .

dll_ver.g4b

!BAT
# String is "FileV" in Unicode
if "%1"=="" goto :usage
set file=%~dpnx1
set string=\x01\x00\x46\x00\x69\x00\x6C\x00\x65\x00\x56\x00
set version=
set char=

debug off
cat --hex --locate=%string% %file% > nul
set /a offbase = %?% + 27

set /a counter=1
:loop
set /a figure=0
set /a offset=%offbase%+%counter%
cat --skip=%offset% --length=1 %file% | set char=

:floop
if "%char%"=="%figure%" set version=%version%%%char%
set /a figure=%figure%+1
if "%figure%"=="10" goto :fnext
goto :floop

:fnext
if "%char%"=="." set version=%version%%%char%
set /a counter=%counter%+1
if "%counter%"=="30" goto :next
goto :loop

:next
set majmin=%version:~0,3%
set os=Unknown Operating System
if "%majmin%"=="5.0" set os=Windows 2000
if "%majmin%"=="5.1" set os=Windows XP
if "%majmin%"=="5.2" set os=Windows XP 64-bit or Server 2003
if "%majmin%"=="6.0" set os=Windows Vista or Server 2008
if "%majmin%"=="6.1" set os=Windows 7 or Server 2008 R2
if "%majmin%"=="6.2" set os=Windows 8 or Server 2012

echo File %file%
echo appears being part of %os%
set version


goto :EOF


:usage
echo This batch should print the version of .dll's
echo tested on 32-bit ONLY
echo You must provide a fully qualified path as parameter.
echo Example:
echo (hd0,0)/Windows/System32/aaaamon.dll
echo or a valid relative path from current ROOT:
echo /Windows/System32/aaaamon.dll

Wonko

It has been less than 2 months since the launch of Windows 8 and I recieved tons of emails from Boot-Landers /members and
guests also friends and collegues asking me if there's a way to reset a forgotten Windows 8 password the easiest way ? The
answer was yes and as usual without the need for any third party software to unlock or remove or reset the user or admin
account password. Here I will try to make an easy to follow tutorial that will be usefull for novice users as well as professionals when they get stuck behind the logon screen of a Windows 8 because they lost or forgotten their password. So here's how to do it in 10 minutes or less :

1- You need a Windows 8 PC to make a System Recovery Disk .

2- You need a CD Burner + Blanck CD.

3- If you have a tablet or a netbook and you don't have a CD burner then You need a 512 MB USB thumb drive to make a System Recovery USB instead.

4- To make a system recovery CD, Go to control panel and navigate to Windows 7  File Recovery, click on that icon, and
from the next screen choose from the top left ( Create a System Recovery Disk ) and follow the on-screen instructions to make
that CD.

5- To make a System Recovery USB thumb drive go to control panel and navigate to ( Recovery ), click on that icon and from
the next screen choose ( Create a recovery drive ) and follow the instructions to make a bootable System Recovery USB.

6- When you are ready, boot the locked PC that needs to be unlocked with that CD or USB you just made, and follow the
pictures below :







7- The command prompt screen will open, type : diskpart and hit Enter key



8- Type :  list vol and hit Enter key (watch for spaces)



9- locate your Windows partition letter ( in our case here the letter will be C drive)

10- Type : Exit and hit Enter key.



11- Type:  c:   and hit Enter key  (your Windows drive maybe different so change it accordingly to the drive letter you have)



12- Type: cd windows (watch for spaces ) and hit Enter key



13- Type: cd system32 (watch for spaces) and hit Enter key



14- Type: copy  cmd.exe cmd.exe.original (watch for spaces) and hit Enter key.



15- Type: copy Utilman.exe Utilman.exe.original (watch for spaces) and hit Enter key.



16- Type: del Utilman.exe  (watch for spaces)  and hit Enter key.



17- Type: ren cmd.exe Utilman.exe  (watch for spaces)  and hit Enter key.



18- Type: Shutdown  -r  -t  00 (watch for spaces) and hit Enter key, the PC will restart.



19 – When you reach the Logon screen click on the Ease of Access Center icon on the left bottom side of the screen.



20 – The command prompt window will open



21- Type: net user  (watch for spaces)  and hit Enter key.



22- Type: net user  Reboot.Pro *  ( replace Reboot.Pro with the name you find in your pc)  and hit Enter key



23- now type the new password you want and hit Enter key( when you type the cursor will not move and you will not see what you
type, so be carefull what you type, because you are typing blindly the new password)



24- confirm the new password when prompted and hit Enter key when done:



25- Type exit and hit the Enter key to close the command window.


 

26- Logon now to the locked account with the new password you just created.

27- After successfully unlocking  your account and resetting the account password now you need to roll back the changes you
made to Utilman.exe and cmd.exe, so go ahead and boot your pc with the System Recovery CD or USB you made earlier in this
tutorial and repeat steps in # 6 so you open the command prompt window :

28- Type: c: and hit Enter key(your Windows drive maybe different so change it accordingly to the drive letter you have) [see picture below]

29- Type:  cd windows  (watch for spaces) and hit Enter key [see picture below]

30- Type:  cd system32 (watch for spaces) and hit Enter key [see picture below]

31- Type:  del  Utilman.exe  (watch for spaces) and hit Enter key [see picture below]

32- Type: ren  Utilman.exe.original Utilman.exe  (watch for spaces) and hit Enter key [see picture below]

33- Type: ren cmd.exe.original cmd.exe  (watch for spaces) and hit Enter key [see picture below]

34- Type: shutdown  -r  -t  00  (watch for spaces) and hit Enter key to reboot your pc [see picture below]



35- Now when the pc reboots and reaches the logon screen, check to see if the Utilman is fixed and returned back to place by
clicking on its icon on the bottom left side of the screen, if the Ease of Access list pops up then you succeeded in your work.
See picture below.




PS: some of you might have a Windows 8 Installation DVD, he can use it also in this process, boot with this Windows  DVD and
when you reach the first screen where you have to click next - stop there and hit SHIFT key + F 10 , the command prompt window
will pop up and you can use it as we did in steps 7 onward to the end. see picture below





Done !  best regards / Jamal

===============
other useful topics :
===============
1- Reset a forgotten Windows 7 Password without using any third party software /

http://reboot.pro/topic/15751-reset-a-forgotten-windows-7-password-without-using-any-third-party-software-how-to-tutorial/

2- Image your system and forget about formatting -period /
http://reboot.pro/topic/13044-image-your-system-and-forget-about-formatting-%E2%80%93-period/

3- Encrypt your sensitive data before wiping it !

http://reboot.pro/topic/12862-encrypt-your-sensitive-data-before-wiping-it/

4- Is your Anti-Virus healthy and responding right, Check that out !

http://reboot.pro/topic/12991-is-your-anti-virus-healthy-and-responding-right-check-that-out/

5- Hacking for the Humanity

http://reboot.pro/topic/14563-hacking-for-humanity/

6- TuneUp your IT skills with Microsoft Technologies !

http://reboot.pro/topic/13263-tune-up-your-it-skills/

Fatal error: Call to undefined method han_login::validateAccount() in /home/reboot/public_html/admin/sources/base/core.php on line 2270

Account validates ok though as you can see (im logged in)

Thanks

pat

not only to map it or read the iso, actually to mount it in ram.

When editing scripts the macro context menu is added multiple times depending on how many scripts have been opened for editing. This can lead to WinBuilder exhausting all resources and crashing.

After Install of XP then you need to fix XP-1.vhd for booting from USB-drive by using USB_XP_Fix.exe
The fix will prevent BSOD 7B and will help to allow the XP VHD to boot on various hardware and so become Universal.



menu.lst on USB drive

title XP-2.vhd - WinVBlock FILEDISK - 2000 MB
# Sector-mapped disk
map /XP-2.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr

title XP-2.vhd - WinVBlock RAMDISK - 2000 MB
# Sector-mapped disk
map --mem /XP-2.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr

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

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

2. How to prepare XP Setup Source ? - Prepare XP Setup ISO file with integrated UpdatePack and DriverPacks

Take care that your XPSOURCE Folder is located on your Harddisk in a simple Path without SPACES.
Copy the Content of your Windows XP Setup CD to your XPSOURCE Folder on Harddisk

First Integrate ServicePack SP3 in your XP-SP2 Source (don't use here nLite).
http://www.helpwithw...ice_Pack_3.html
Download from - http://www.microsoft...i...ng=en&id=24

In Command Window use for English version and XPSOURCE folder on drive E:

WindowsXP-KB936929-SP3-x86-ENU.exe /integrate:E:\XPSOURCE

Siginet's RyanVM Integrator 1.6 can then be used to Integrate Windows UpdatePacks in the XP-Source.
http://integrator.si...ex.php?download
Download preferred version RVM Integrator 1.6.1 Beta 2.1 - http://www.mediafire.com/?ynajonymmnz

Windows XP UpdatePacks and Addons:
http://www.ryanvm.net/msfn/
http://www.ryanvm.ne...tepack-sp3.html
http://integrator.si...ndex.php?addons
http://www.ryanvm.net/forum/

Work according to Section 2 in - http://www.911cd.net...showtopic=21883

For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE DriverPack Massstorage with TXT Mode Enabled.
http://driverpacks.net/downloads
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the
XP Setup BootFolder $WIN_NT$.~BT on Install-Drive and can prevent a lot of XP Install Boot Problems.
Use DPsBase.exe to Integrate DriverPacks Chipset + Processor + MassStorage + LAN + WLAN DriverPacks
which will then be located in OEM Folder in your XPSOURCE folder
Always first use RyanVM Integrator and then use DPsBase to Improve your XP-Source
DPsBase makes presetup.cmd in folder I386 and changes the I386winnt.sif file for use of DriverPacks

presetup.cmd in folder I386 will start decompression of DriverPacks located in OEM folder
at the beginning of GUI-mode of XP Setup, which does NOT take to much time for the 5 DriverPacks

You should select to Keep The Drivers for Chipset + Processor + MassStorage + LAN
Then WINDOWSDriverPacks is about 135 MB which is acceptable and provides a lot of extra driver support
which is useful to make XP Universal and adapt easily to very different hardware.
In that case the DevicePath is set accordingly in key
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersion
so that XP can automatically make use of these drivers for adjusting to New Hardware

When you don't use nLite, you can copy the supplied $OEM$ folder to your XP Source folder
Change $OEM$ folder to your needs for UserAccounts and Registry Tweaks and Adding Drivers
CMDLINES.TXT is used for making UserAccounts and install of Registry Tweaks at T-12
Info see: http://unattended.ms.../unattended.xp/

Use DriverForge.v4.5.4.exe to Install from C:Drivers at T-9 of GUI XP Setup (just for the last Reboot).
DriverForge.v4.5.4.exe was made by kickarse http://www.msfn.org/...howtopic=110783
At end of TXT-mode XP Setup the folder $OEM$$1Drivers is copied to C:Drivers
and $OEM$$1InstallDriverForge.v4.5.4.exe is copied to C:Install
For Auto Use of DriverForge at T-9 add uncompressed driver folders in $OEM$$1Drivers
and Uncomment two rules by removing ; in winnt.sif file copied from winnt_sif to your I386 folder
This is very useful for Install of your well known Audio and Video driver during GUI-mode of XP Setup.

[SetupParams]
UserExecute = "%SystemDrive%\INSTALL\SetupPar.cmd"

Next alinea is not needed when DriverPacks are integrated as described above but given here as useful info.

PnP Drivers specified in winnt.sif can be added to $OEM$$1Drivers
http://unattended.ms...xp/view/web/34/
TEXTMODE Drivers defined in winnt.sif and located in $OEM$TEXTMODE folder of the XP Source
can be used instead of using F6 floppy for MassStorage Drivers.
The content of the $OEM$TEXTMODE folder is copied to XP Setup BootFolder $WIN_NT$.~BT$OEM$
See cdob and allanf in http://www.boot-land...?...5306&st=180

Smart Driver Backup 2.12 of Jaque is very useful to Backup your drivers before install of XP
http://www.911cd.net...showtopic=20555

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

How to make XP Setup ISO File ?

- Use BBIE (see below) or Isobuster to Extract Boot Image bootsect.bin from Original bootable XP Setup CD
bbie will make image1.bin that you can copy as bootsect.bin to XP Setup source folder
- Reduce Size of XP Setup Source folder (if needed to fit on CD then remove folders LANG WIN9XMIG WIN9XUPG)
- Use ImgBurn and bootsect.bin to make Bootable CD

In detail:
1. Remove 3 folders LANG WIN9XMIG WIN9XUPG - reduction in size = 135 MB
2. Run ImgBurn - Portable Tool in PStart Menu - IMG_XPMULTIPStartProgsImgBurn
- Select Write files/folders to disc
- Output - Select Image File
- Browse Source folder and Select your XP Setup Source folder
- Browse Destination file - Give Name e.g. XP-Setup.iso
- Labels ISO 9660 - Give Name e.g. XP-Setup
- Advanced Restrictions - ISO9660 - Select Level X and DOS CharSet with 4x Checkbox On (allow ...)
- Bootable Disc - Make Image bootable - Checkbox On - Browse Boot Image - Select bootsect.bin file
- Bootable Disc - Emulation Type = None
Load Segment = 07C0
Sectors to Load = 4

BOOT_USBmakebt>bbie M:XP3_1201.iso
BBIE - Bart's Boot Image Extractor v1.0, © 2001, Bart Lagerweij
http://www.nu2.nu
will make BOOT_USBmakebtimage1.bin that you can rename as bootsect.bin

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

POST_FIX Tools - Readme

You can use DriverForge.v4.5.4.exe to Install any missing driver (e.g. video audio or WLAN)
by selecting Path to Uncompressed Driver Files e.g. S:D
In that case DevicePath in HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersion
is set to what DriverForge needs.
It means that any previous settings are lost e.g. for making use of the KTP C:WINDOWSDriverPacks store.
If you have selected in DPsBase.exe to Keep The Drivers by using KTP Option,
then after using DriverForge you need to run DevicePath_Reset_KTP.reg to Reset DevicePath to the KTD settings.

If you have Installed XP on AMD machine and then boot XP Image file on Intel machine,
then intelppm Service will have Start=1 value, which will give BSOD 7 E when booting on AMD machine.
This problem can be overcome by running the intelppm_Start3.reg registry tweak.
In that case intelppm Service will get Start=3 and everything will be OK for AMD and Intel.

Post Install Add DriverPacks:
1. Boot with Universal XP Image file
2. Extract 3 DriverPacks to C: e.g. Chipset + CPU + MassStorage - will give C:D folder
3. Use R-mouse to Open command prompt at C:POST_FIX and run command

DevPath.exe %SystemDrive%\D

DevicePath in HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersion
is set to subfolders of C:D

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

Portable Windows HD Image files booting from USB

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

The Apps IMG_XP_Compact.exe and VHD_W7_Compact.exe of IMG_XP package
can be used to make Portable Windows HD Image files booting with Grub4dos Menu on HDD or USB

These Virtual Harddisk files are of type IMG or VHD and require WinVBlock or FiraDisk driver to boot them as FILEDISK or as RAMDISK
The Ultimate Windows 7 VHD files make use of Microsoft VHD HBA driver which allows to boot them as FILEDISK
Additinally Installed Programs and Drivers and Settings are remembered in FILEDISK just like in normal Windows OS

Source can be drive where Windows is installed or full XP Image file Or Windows 7 VHD file
In case of using existing Installed XP as source, it is handy to first create a NEW user in XP,
so that this NEW user folder is small in size e.g. only contains very few Documents and Pictures.

Also Install either WinVBlock or FiraDisk driver:
- Install WinVBlock driver see - IMG_XPHelp_InfoWinVBlock_Install.txt
- Install FiraDisk driver with R-mouse on firadisk.inf in IMG_XPmakebtfiradisk-driver- folder

Reduce size and connect USB-harddisk as described in point 5 and 6 given above
to get rid of pagefile.sys and hiberfil.sys and to get USB-HDD settings are known in XP registry

After booting with other OS e.g. Portable 7 PE, then you can run IMG_XP_Compact.exe and Select the NEW user
to make XP Image file that can boot from grub4dos menu on HDD or USB

Mini XP = OS Size 400 MB - including IE8 + WLAN + Audio + Printer + 7-Zip + ImDisk and all installed drivers
Port XP = OS Size 600 MB - extra system32 complete + Windows Media Player - Multimedia support

In case of Mini XP then external VLC portable player can be used for MultiMedia support

Advised size of XP Image file is 1.0 GB and for Windows 7 VHD file is 1.6 GB

==

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

Boot Win7 VHD Image file from USB

- Direct Install Windows 7 in a VHD file on local harddisk created by WinNTSetup2_x86.exe with Ctrl + Shift + V
- Copy Win7 VHD file to USB and use USB_W7_Fix.exe to fix for booting from USB-drive
- Make Boot Manager menu on USB for Win7 VHD Image file

Thanks to JFX for creating the very handy WinNTSetup2 tool to Install Windows 2k/XP/2003/Vista/7 x86/x64

Info in folder IMG_XPWinNTSetup2_x86_x64 and here http://www.msfn.org/...-winntsetup-v2/


WARNING: Boot menu of your computer and your USB-drive will change needed for booting with Win7 VHD file.
WinNTSetup2_x86.exe will create or change Boot Manager menu (folder Boot and file bootmgr)


Details of Procedure to create Win7 VHD file for booting from USB-drive
1. Boot with Windows 7 or 7PE
2. Use R-mouse menu to Mount Windows 7 Setup ISO file in ImDisk virtual drive (if needed first Install imdiskinst.exe)
3. Run WinNTSetup2_x86.exe and use Ctrl + Shift + V to create Win7 VHD file on local Harddisk (or use Disk Management)
4. In WinNTSetup2_x86.exe adjust Windows 7 Tweaks and Select install.wim and Bootdrive and your attached Win7 VHD
Select all System-Only Tweaks except Turn OFF USB and select other tweaks that you like
Select Checkbox to Mount Installation drive as C:
5. Use Setup to prepare Win7 VHD file and Boot drive menu and Reboot to Start Install of Windows 7
6. Reboot 2x with Win7 VHD to finish Install of Windows 7 in VHD
7. Check that System Protection and UserAccount Control are set Off and Reduce Size
If needed e.g. Change settings to get rid of pagefile.sys and hiberfil.sys
No pagefile.sys - Run as Administrator in cmd window: sysdm.cpl
and Change Advanced Performance Virtual memory Settings - Set to use No paging file
No hiberfil.sys - Run as Administrator in cmd window: powercfg.exe -H off
- Install Missing Drivers and Install Standard Controllers for IDE and USB and VGA
- In Device Manager instead of Hardware specific Controllers you must Install Standard Controllers for IDE and USB and Install Standard VGA Adapter
Install anything you need like ImDisk and 7Zip and connect your USB-harddisk to Update registry
Use Computer Properties and Set System Protection for Win7 VHD drive Off and Reboot Win7 VHD
8. Reboot with Windows 7 or 7 PE
9. Copy Win7 VHD to bootable USB-drive and use Disk Management to Attach Win 7 VHD located on USB
10. Open cmd prompt and create Boot Manager menu on USB-drive by running

bcdboot N:\Windows /s P:

where N: is your attached Win7 VHD and P: is your USB-drive

11. In Disk Management Detach Win7 VHD
12. If your USB-drive was NOT formatted in Windows 7 OS, then you need to fix the Bootsector of USB-drive P: with

bootsect.exe /nt60 P: /force

13. Run USB_W7_Fix.exe of IMG_XP package to fix the registry of Win7 VHD file on USB
14. Reboot with Win7 VHD from USB

Instead of points 9-13 you can make use of VHD_W7_Compact.exe to make Portable Windows 7 VHD file of 2 GB booting from USB-harddisk.

Procedure for booting with 1.6 GB Portable Windows 7 VHD file on USB-harddisk
Step 1. - Direct Install Windows 7 in a 10 GB VHD file on local harddisk and created by WinNTSetup2_x86.exe with Ctrl + Shift + V
Step 2. - Run VHD_W7_Compact.exe to Copy Win7 VHD content in 10 min to New VHD file of Reduced Size on USB-harddisk
Step 3. - Reboot with 1.6 GB Win7 VHD file from USB

On Running VHD_W7_Compact.exe you need to Select your User Folder in folder Users of the Win7 VHD Source file
The program takes care of Attach and Detach of VHD files by using diskpart.exe of your Windows 7 or 7 PE Operating System.

The program is suitable for 32-bits Windows 7 and was tested with en-US Ultimate version,
but may work with other distributions as well.


VHD_W7_Compact.exe - makes 2.0 GB Win7 VHD file for booting from USB-harddisk

=




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

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

4. Universal Image Compact and Restore - Details
 

5. Solutions to prevent BSOD 7B - Run USB_XP_Fix.exe

6. Universal XP - Support in boot.ini menu for Multiple Hal and Kernel
 

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

Summary

Universal XP is reality now:

- The same VHD Image File made with VHD_XP_Create.exe can be used for booting XP
from FILEDISK on HDD or USB or from RAMDISK, on computers having quite different Hardware architecture.

- IMG_XP_Restore.exe can be used to Install on HDD partition in 3 min XP including Office + PRGS + Updates
using 1.6 GB Universal XP HDD Image as source.

- BOOT_IMG copies Universal VHD Image File to Target Drive and makes GRUB4DOS Boot Menu.
Use this e.g. on a laptop running Vista or Windows 7 to make a boot option in BOOTMGR menu for Grub4dos.
Without the need to make new partition for XP, one can now simply use BOOT_IMG.exe
to install 1.6 GB Universal XP Image file booting in 1 min from WinVBlock or FiraDisk RAMDISK.

- IMG_XP_Update.exe is used after booting with XP Image file from RAMDISK, to Update the Image file that you just booted from.
Boot with full XP Image file in RAMDISK and Update Drivers using DriverForge with Drivers folder that you supply.
Then run IMG_XP_Update.exe to improve full XP Image file in 1 minute with drivers for New Hardware.

- Most computers nowadays are ACPI Multiprocessor PC and we can use the corresponding HAL.
If you need for XP to support computers using a different HAL then you can use Add Hal and Kernel files and
let modify by IMG_XP programs your boot.ini as described in Section 6.
http://www.vernalex....sprep/hal.shtml
http://www.etherboot...t_winnt_sanboot

- IMG_XP_Compact.exe and IMG_XP_Restore.exe have been tested running in 32-bits XP and Windows 7
and can also be used from LiveXP PE Environment.
In all cases ImDisk must be installed in XP or Win7 by using previously the provided imdiskinst.exe file.
ImDisk is used to mount the full XP HDD Image file in a virtual drive.

To Install ImDisk driver on Vista and Windows 7 you need to turn off UAC, User Account Control
http://www.ltr-data.se/opencode.html

The 64-bit ImDisk driver files included in the install package will not load on 64-bit Vista or 64-bit Windows 7
unless the machine is running with testsigning switched on.

Open Command Prompt as Administrator:

bcdedit /set testsigning on

Reboot to activate this.
http://msdn.microsof...y/dd419910.aspx

Thanks to karyonix, more Info see:
FiraDisk - http://www.boot-land...?showtopic=8804
Install FiraDisk driver in XP with R-mouse on firadisk.inf in IMG_XPmakebtfiradisk-driver- folder
Forum FiraDisk - http://www.boot-land...hp?showforum=94
Windows 7 - http://www.boot-land...hp?showforum=77
Windows 7 on USB-HDD - http://www.boot-land...?showtopic=9196

Thanks to jaclaz for pointing me to strarc.exe of Olof Lagerkvist ,
which is used in IMG_XP_Update.exe to Update the XP Image File on HDD after booting from RAMDISK.
Updating Registry and Drivers in Image file is done in only 5 sec, a Total Update of the Image requires 1 min.



Development and historical thread here:
Thanks to joakim for starting the subject
http://www.boot-land...?showtopic=9227

A Boy and His Atom is a 2013 stop-motion animated short film released on YouTube by IBM Research. It depicts a boy playing with an atom that takes various forms. One minute in length, it was made by moving carbon monoxide molecules viewed through a scanning tunneling microscope, magnifying them 100 million times. The molecules were manipulated to create images, which were then saved as individual frames to animate them.

It has been recognized by the Guinness Book of World Records as the smallest movie ever created. The scientists at IBM's Almaden Research Center who created the film had been developing ways to improve data storage efficiency by magnetizing smaller groups of molecules than has previously been accomplished. They made the film in the hope that schoolchildren who see it will become aware of the possibilities of careers in science.

Reference: http://adf.ly/P0W7x

• 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

/tftpboot/

/tftpboot/pxelinux.cfg/

/tftpboot/pxelinux.cfg/default

/tftpboot/memdisk

/tftpboot/RamXP.HDD

DEFAULT ramxp

LABEL ramxp

  KERNEL memdisk

  APPEND raw

  INITRD RamXP.HDD

/menu.lst

/RamXP.HDD

default 0



title RamXP

  map --mem (hd0,0)/RamXP.HDD (hd0)

  map --hook

  root (hd0,0)

  chainloader /ntldr

• \I386\System32\Drivers\WVBlk32.SYS (or WVBlk64.SYS)

...

[SCSI.Load]

wvblk32 = wvblk32.sys,4

...

I have the following situation:

I'm new to the grub4dos, and will apppreciate any answer

Win 7 SP1 + IE10.

Plz Help For Fix Error

Plz Help For Error :

FileCopy - Failed to copy [C:\7\bootmgr.efi] to: [%BaseDir%\Target\Win7PESE\bootmgr.efi]: The system cannot find the file specified.

Log Error :

http://www.mediafire.com/view/?b95pi56fb9wqic3

map --mem /WIN_SETUP/2000.ISO (0xff)

map (hd0) (hd1)

map (hd1) (hd0)

map --hook

root (0xff)

chainloader /I386/SETUPLDR.BIN

map /WIN_SETUP/2000.ISO (0xff)

imdisk -a -s 60M -m #:

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

Minitools PartitionWizard, Easeus PartitionManager, PartitionRecovery, SavePartition, Victoria, MacriumReflect, Explorer++, Filecommander, Q-dir, Salamand, ChrystalDiskInfo, DiskMark, Hddscan, HDTune, WinDlg is here:

http://al-jo.zxq.net/Win7PEguide.html

Testing the ISO in Virtualbox, it shows a US flag in the systray and right-clicking on that and selecting Preferences it opens the "Text Services and Input Languages" window, which only contains "English (US)" (my Host system is UK and only has "English (UK)" listed).

Opening the Region and Language settings does show "English (UK)" under Formats and "UK" under Location, so it seems it's just the Keyboard setting that's not being properly imported from the Host system.

Whats the problem?

The problem you already know, Hirens Boot Cd Mini XP in USB doesnt load the programs. I understand that is becasue hirens look for HBCD folder in the root of the drive (ISO or USB), one way to fix this is what Steve told everyone. extract the HBCD folder to the root of the usb... But you will have the Hirens iso + HBCD thats almost as twice space in the drive.

In addition, I want to have different versions of Hiren boot cd... you know hiren only uses freeware since some time ago... and other hirens cd has nonfree softwares...

I cannot have 2 HBCD folders in the root of the usb, so what I did is this:

• Add my 2 or 3 or 8 ISOs to usb using XBoot
• Open Hirens boot cd, open Mini XP
• Load Mini XP without the HBCDmenu for the programs...
• Open explorer, explore the USB drive, right click hirens ISO and mount the iso with Imdisk as a virtual CD
• Then I run  X:\I386\System32\startup.cmd
• Now the HBCD programs are reloaded and found in the Virtual drive... (some programs works, and other ask for a DLL

Now the problem is that needs a DLL, the MSVBVM60.dll

I Wanted to reload all drivers and prograsm like MIniXP in the startup, but I only found startup.cmd, somebody knows what to do to load the MSVBVM60.dll, it should be installed by one program in hbcd but which?

What Im going to do is find the MSVBVM60.dll and keep it on root to copy it later... but maybe tomorrow and I will keep you informed.

I had a few monthes ago installed Hiren's boot CD on a USB key.

But after that, every time I have ran the computer without this USB key in my computer, I have had the following message:

Try (hd0,0): NTFS5: No GRLDR

Try (hd0,1): NTFS5: No GRLDR

Try (hd0,2): NTFS5: No GRLDR

Try (hd0,3): invalid or null

Cannot find GRLDR.

Press space bar to hold the screen, any other key to boot the previous MBR...

I only have to press a key to skip this screeen. But I would prefer not to have it at all. I guess the installation of Hiren's boot on the USB changed something on my MBR and the previous MBR seems to have been saved somewhere. Maybe I can watch out where. 

By the way, I happen to no more have this USB key. Was probably lost when I moved home in summer, isn't to be found again.

(As it is my first post, if for any reason it was to rejected please explain why. I hope I will not)

I need of a script di Seatools for windows for win7PE

the last version v1208 work only with .net 4

but old v1205 work with .net 2

please help me for this script

thanks

I apologise if this has already been covered on another thread however I was unable to locate it. At present I have created a bootable USB drive which contains 6 different versions of Windows 7, using the following tutorial:

02 - How to create a USB drive that will install one of many choices of Windows OS's (Vista/Win7/Server 2008/XP) - RMPrepUSB

What I would like to do is add Windows 8 Installation sources to the Drive in the same manner. I don't want to use the new method which uses iso's. If I have to create another partition to accomodate this then that is fine.

Is anyone able to help?

scanstate.exe is not compatible with the version of Windows you're running....".

I have tried both 32-bit and 64-bit versions of this file and get the same error message.  The USMT scanstate.exe file has come from the WAIK, I have tried both version of scanstate.exe (amd64 and x86) from inside the C:\Program Files\Windows AIK\Tools\USMT directory

Ive tried both of htem on WinPE that was built with a x86 source, and a x64 source, so im lost as to why its telling me this. Anyone?

I'm developing a app that's natively portable. Every time the app is run on a new OS, the app needs to do something (eg. display the license). Any ideas ? 

Even if the user has installed, say, Win 7-32 on two partitions, I would like to identify one from the other.

If the app is run from one directory and then moved to another directory or drive, the app should be able to tell that the OS has not changed.

btw, this is not really related to Win 7 - the app will run on any windows.

One way would be to get the volume id of the system drive. Any better way ?

I was able to boot only and actually when setup process should started get these errors:
Win7
"A required CD/DVD drive device is missing. If you have a driver floppy disk, CD,DVD, or USB flash drive, please insert it now.

It seems like you incorrectedly posted here:
http://www.boot-land.net/forums/index.php?...=5041&st=26
that Windows 7 install works, while it does not.

Please do confirm you actually booted it successfully WITHOUT the "missing" CD/DVD problem and/or start a new thread detailing HOW you did it.



jaclaz

Uhm thats so wierd, like 3 hours ago I installed it into the HDD of my school without any kind of problem. Also I formated my computer yesterday due to some problems I had with the HDD and reinstalled Windows 7 with that method.

So its actually working. Maybe it's working, because I have Windows XP installer there, on the root of the pen, so when its looking for X file or configuration, it takes the XP configuration and works anyway. Im not sure tho.
If you know surely that you get problems if you boot the .iso from grub4dos, you are free to delete it, as much more people might have problems with that too.

No , actually I would like to keep it AND provide a better solution instead of the "manual" command for IMDISK.

If you don't mind I'll start a new thread, citing what happened and your current confirmation. (can I cite verbatim your PM?)

As soon as you have an occasion to install 7 on some machine, are you willing to investigate (basically by deleting little by little anything BUT windows 7 .iso, grub4dos and menu.lst) which files may be responsible of it working?



jaclaz

yeah do it, np.
I will try to investigate about this; im a bit busy because of school right now, but I will check why it is working for me. I might be maybe just lucky? haha

The 90MB download is here.

Please use this ISO as source (Windows7 x86 sp0 english) & and a proper download manager when downloading.

If any building problems, try read this small guide first.

If any other problems/requests, send a message here.

If you like this project & find it useful it’s possible to donate a beer or two here: 

Good Luck!

Ps1.

From the authors of NVDA:

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

Ps2.

A “special” version where all applications will run from USB/CD instead of RAM is here.

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

default file:

title Win7PE
pxe keep
map (pd)/WIN7Pe_x64.iso (0xff) || map --mem (pd)/WIN7Pe_x64.iso (0xff)
map --hook
root (0xff)
chainloader /BOOTMGR

Quando eseguo il boot via pxe il client carica l'immagine ISO correttamente, ma quando mi trovo in ambiente WIN7PE non viene montata l'unità DVD (Y:), dove nella cartella driverpacks sono presenti i driver aggiuntivi relativi alle schede LAN e CTRL Sata che non possono essere installati per cui le relative periferiche non sono riconosciute. Sapreste indicarmi una soluzione per risolvere poichè ho diversi pc che hanno configurazioni hw differenti e l'integrazione dei driver tramite dr

I'm seeking after a way to get data from an external file into WB for parsing it there:

I detect how many files in a folder have to be processed, then in a loop I gather further info and write that into a text file.

This file will contain 1 to n lines with 2 values each (delimited by a colon):

abcdefghijk:1.0

lmnopqrstuv:1.1

...

Each line will be split (StrFormat) in %_1 and %_2 for dynamically writing registry data.

Is there any chance of retrieving the file's content, even if it's somewhat provisional...? Maybe with AutoIt or environment variables...?

I just can't imagine using the ini file structure for that purpose, that would be too cumbersome and error-prone...

There has to be another feasible option...

Any suggestions?

7z, XZ, BZIP2, GZIP, TAR, ZIP, WIM, ARJ, CAB, CHM, CPIO, CramFS, DEB, DMG, FAT, HFS, ISO, LZH, LZMA, MBR, MSI, NSIS, NTFS, RAR, RPM, SquashFS, UDF, VHD, WIM, XAR and Z.

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, xar

         /a -a archive filename or URL location of archive

         /e -e filename to extract out of the 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 -e=some/file.txt -o=file.txt

As it's only being used for RDP and occasionally running Opera or Iron Portable to play online videos that don't currently work over RDP (although they might using Win7 instead of XP), I don't really want to use a full bloated Win7 install so have been looking at Win7PESE, which is OK but I'd prefer to be able to make settings stick, so that PeNetwork doesn't have to run at each boot to setup the Network, hardware doesn't have to be detected and Visual and mouse/keyboard settings can be set.

I'm also not sure if it's advisable to use an unpatched Win7PE as the Host, even though it's mostly only being used as a RDP station, in case that leaves it vulnerable as an attack vector into the network. I certainly need to use the RDP patches at least.

I did look at Windows7 Embedded a while back but got a bit lost working out how to build it so if that would be suitable, maybe there's a guide someone could point me to that might help. Maybe Win7 ThinPC would be a possibility but it seems that has to be installed on the intended system and as that's not where I am, it's perhaps easier to use something I can build into an ISO/VHD here to then take there and boot with grub4dos. The system also only has a small (20GB) HDD which doesn't have much free space anyway, so it's tricky to install an OS on the system. I've got a 16GB CF card I could use but I'm not sure if Win7 will install to that, although it will probably be able to boot an ISO/VHD from it (Linux boots and runs fine from it but XP freezes unless I hide it with grub4dos before booting and if I unhide it after XP Portable has booted, it locks up straight away!)

• Registry
  • key HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk
    
    • value StartOptions type REG_SZ
      data = list of drive description to create separated by semicolon.
      Example: disk,vmem=find:\file1.img;cdrom,vmem=find:\file2.iso;floppy,vmem=c:\file3.img;disk,vmem=c:\file4.img,size=1052835840
        There are 3 types of virtual drive : disk, cdrom, floppy
        There are 3 main types of media/image :
      

      file=path  : File read/write.
      vmem=path  : Memory mapped file.
      vmem without path : Allocate from virtual memory (RAM+pagefile).

      Optional parameters
      

      offset=number
      size=number
      heads=number
      sectors-per-track=number
      ro : read-only
      boot : indicate that the virtual drive is required for booting Windows.

      If file does not exist and size is specified, new file will be created.
      If file exists but is smaller than offset+size, it will be extended.
      
    • value DisableDetectGrub4dos  type REG_DWORD
      
    • value DisableDetectMemdisk  type REG_DWORD
      
    • value DisableDetectedRAMDrives  type REG_DWORD
      0=enable 1=disable
  • key HKLM\SYSTEM\CurrentControlSet\services\FiraDisk\Parameters
    
    • value StartOptions  same format as above.
      You can write to this value at first stage of Windows XP setup by using TXTSETUP.OEM section [Config.FiraDisk].
      
    • value PnP  type REG_DWORD
      0=Create new FiraDisk Enumerator device at startup.  1=Don't create new FiraDisk Enumerator device.
• GRUB4DOS RAM drive
  Create a small RAM drive with drive number between 0-127 and write FiraDisk options to it.
  Begin with [FiraDisk] (case insensitive)
  followed by \n
  then StartOptions=data\n
  and end with \0.
  Backslash is escape character in write command.
  You can use / instead of \ in data field. When FiraDisk read this data, it will convert / to \ automatically.
  Example:
  

  map --mem (md)0x800+4 (99)map --hookwrite (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/file1.iso;floppy,vmem=find:/file2.img;\n\0

#Boot From HardDrive Menu



#splashimage /boot/face.gz

timeout 30

default 0



title Previous Menu

configfile /menu.lst



title     

root ()



iftitle [find --set-root --devices=h /bootmgr && call set bootmgr=%@root^%] Boot BOOTMGR of Windows VISTA/WIN7/WIN2008 on %bootmgr%

chainloader %bootmgr%/bootmgr



#title Boot NTLDR of Windows NT/2K/XP

iftitle [find --set-root --devices=h /NTLDR && call set bootmgr=%@root^%] Boot NTLDR of Windows NT/2K/XP on %bootmgr%

#find --set-root --ignore-floppies --ignore-cd /ntldr

map () %bootmgr%

map %bootmgr% ()

map --rehook

find --set-root --ignore-floppies --ignore-cd /ntldr

chainloader /ntldr



#title Boot The Recovery Console of Windows NT/2K/XP

iftitle [find --set-root --devices=h /cmldr && call set bootmgr=%@root^%] Boot The Recovery Console (cmldr) of Windows NT/2K/XP on %bootmgr%

fallback 3

find --set-root --ignore-floppies --ignore-cd /cmldr

map () %bootmgr%

map %bootmgr% ()

map --rehook

find --set-root --ignore-floppies --ignore-cd /cmldr

chainloader /cmldr

#####################################################################

# write string "cmdcons" to memory 0000:7C03 in 2 steps:

#####################################################################

# step 1. Write 4 chars "cmdc" at 0000:7C03

#write 0x7C03 0x63646D63

# step 2. Write 3 chars "ons" and an ending null at 0000:7C07

#write 0x7C07 0x00736E6F

#    or.

#write --offset=3 (md)0x3e+1 cmdcons

#    or

calc *0x7c03=0x00736E6F63646D63



#title Boot IO.SYS of Windows 9x/Me

iftitle [find --set-root --devices=h /IO.SYS && call set bootmgr=%@root^%] Boot IO.SYS of Windows 9x/Me on %bootmgr%

find --set-root %bootmgr%/io.sys

chainloader %bootmgr%/io.sys



#title Boot Linux with menu.lst already installed

iftitle [find --set-root --devices=h /menu.lst && call set bootmgr=%@root^%] Boot Linux with menu.lst already installed on %bootmgr%

find --set-root %bootmgr%/sbin/init

configfile %bootmgr%/boot/grub/menu.lst

 

title Boot Floppy (fd0)

chainloader (fd0)+1

rootnoverify (fd0)



title     

root ()



title Reboot

reboot

 

title Shutdown

halt

iftitle [if exist (hd0,0)/test.img] boot to (hd0,0)/test.img

    map --mem (hd0,0)/test.img (fd0)

    map --hook

    chainloader (fd0)+1

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

bcdboot c:\windows /s c:

bootsect /nt60 c:

1. Downloaded both 32-bit and 64-bit tools for Windows Defender Offline: http://windows.microsoft.com/en-US/windows/what-is-windows-defender-offline
2. Created ISOs for each one of the architectures (the third option labeled advanced)
3. I named these ISOs with todays date (every time you run the tool it embeds the latest maleware definitions)
4. Downloaded and ran https://sites.google.com/site/shamurxboot/download
5. Drag and dropped the ISOs into Xboot and created a USB drive using Grub4dos ISO image Emulation for each ISO (I used syslinux for the boot loader)

Result: I watched the USB drive as Xboot copied it, and it copied the first ISO which was named WDO_Media32-2013-02-21.iso but Xboot put it here:

/images/wdomedia.iso

Once it started copying WDO_Media64-2013-02-21.iso that one also was named the same wdomedia.iso so naturally it overwrite the first one.

I inspected the following config file:

/boot/syslinux/syslinux.cfg

The following entry was all that was there (relevant to these ISOs):

### MENU START
LABEL -
MENU LABEL WDO_Media64-2013-02-21
LINUX /boot/syslinux/grub.exe
APPEND --config-file="ls /images/wdomedia.iso || find --set-root /images/wdomedia.iso;map --heads=0 --sectors-per-track=0 /images/wdomedia.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/wdomedia.iso (0xff);map --hook;chainloader (0xff)"
TEXT HELP
ENDTEXT
### MENU END

To get this to work I renamed the copied file to wdomedia64.iso and manually copied the other ISO to /images/ and named it wdomedia32.iso. Then I edited syslinux.cfg and duplicated the entry and changed them both as follows:

### MENU START
LABEL -
MENU LABEL WDO_Media32-2013-02-21
LINUX /boot/syslinux/grub.exe
APPEND --config-file="ls /images/wdomedia32.iso || find --set-root /images/wdomedia32.iso;map --heads=0 --sectors-per-track=0 /images/wdomedia32.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/wdomedia32.iso (0xff);map --hook;chainloader (0xff)"
TEXT HELP
ENDTEXT
### MENU END

### MENU START
LABEL -
MENU LABEL WDO_Media64-2013-02-21
LINUX /boot/syslinux/grub.exe
APPEND --config-file="ls /images/wdomedia64.iso || find --set-root /images/wdomedia64.iso;map --heads=0 --sectors-per-track=0 /images/wdomedia64.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/wdomedia64.iso (0xff);map --hook;chainloader (0xff)"
TEXT HELP
ENDTEXT
### MENU END

Now I can boot and select either WDO ISO to boot from. I verified by trying to boot to the 64-bit version on a 32-bit machine and got the appropriate error message, but selecting 32-bit version worked.

Is this the appropriate place to submit reports such as these?

It sure is too bad that Microsoft can't reconcile this into a single tool. In my experience most users who need this don't even know what architecture they are running unfortunately.

Thanks.

PS: I've tried to start Inx (resolution until 1024x768 I get a black screen no errors, no nothing and just sits there) and DSL with different resolutions only to get the message: "Mode not supported".Also anyone knows how to make the text from the Grub4Dos menu (the title entries from menu.lst) smaller (it is kinda big).Thank you!

Bellow is my menu.lst :

title Ubuntu live straight to system console
find --set-root /ubuntu-10.04.3-desktop-amd64.iso
map /ubuntu-10.04.3-desktop-amd64.iso (0xff) || map --mem /ubuntu-10.04.3-desktop-amd64.iso (0xff)
map --hook root (0xff)
kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed noprompt boot=casper persistent iso-scan/filename=/ubuntu-10.04.3-desktop-amd64.iso text --
initrd /casper/initrd.lz

title Grml
find --set-root /grml64-small_2012.05.iso
map /grml64-small_2012.05.iso (0xff) || map --mem /grml64-small_2012.05.iso (0xff)
map --hook root (0xff)
chainloader (0xff)


title TTYlinux
map /ttylinux-x86_64-14.1.iso (0xff) || map --mem /ttylinux-x86_64-14.1.iso (0xff)
map --hook root (0xff)
chainloader (0xff)

title Slitaz 4.0
map /slitaz-4.0.iso (0xff) || map --mem /slitaz-4.0.iso (0xff)
map --hook root (0xff)
chainloader (0xff)

title Tiny Core
find --set-root /TinyCore-current.iso
map /TinyCore-current.iso (0xff) || map --mem /TinyCore-current.iso (0xff)
map --hook root (0xff)
chainloader (0xff)

title Inx
find --set-root /inx-1.1.iso
map /inx-1.1.iso (0xff) || map --mem /inx-1.1.iso (0xff)
map --hook root (0xff)
chainloader (0xff)

title DSL 4
find --set-root /dsl-4.4.10.iso
map /dsl-4.4.10.iso (0xff) || map --mem /dsl-4.4.10.iso (0xff)
map --hook root (0xff)
chainloader (0xff)

title Tiny Core Plus
find --set-root /CorePlus-current.iso
map /CorePlus-current.iso (0xff) || map --mem /CorePlus-current.iso (0xff)
map --hook root (0xff)
chainloader (0xff)

title reboot

reboot

Please understand how the present poll is completely UNofficial and definitely UNauthorized.

Wonko

Not good :-(. I use WinXP (32 bits). Is possible change .NET Framework 4 to .NET Framework 2.0 for DiscUtils ?

title XP setup from iso
find --set-root /xp.iso
map (hd0) (hd1)
map (hd1) (hd0)
map --mem /firadisk.ima (fd1)
map --mem (md)0x6000+800 (fd0)
map --mem /xp.iso (0xff)
map --hook
dd if=(fd1) of=(fd0) count=1
chainloader (0xff)


title Continue XP setup
find --set-root /xp.iso
map (hd0) (hd1)
map (hd1) (hd0)
map --mem /xp.iso (0xff)
map --hook
chainloader (hd0)+1

When booting into XP setup from iso, then this is a bug
http://i.imgur.com/APkQhKL.jpg

(I have not tried it on a real computer , is used to test virtual PC)
Highlights are the steps I have done any wrong step?
Looking forward to helping people
thanks

I am wondering if imdisk would be suitable for a very particular usage I have in mind.

I wrote a large C code to acquire and process images from a scientific instrument I built (all open source.. see https://github.com/blog/771-mind-control-with-frickin-lasers)

I use OpenCV's computer vision library to generate a video by adding a new frame to an open AVI file many times a second in a loop as the images arrive from the instrument. Writing to ramdisk speeds up my looping time, however, because everything is in ram, now if the computer crashes or if power goes out I will lose the entire AVI file.

One option would be to rewrite my code to change how I write to file. Another option though, ought to be to do periodic backups, every few seconds or so, using robocopy or strarc. This is what people seem to be calling "lazy-write." Robocopy, though, can't copy files that are currently being written, or "locked". Apparently windows shadow copy will do this, but it doesn't work with a commercial RAMDisk utility I tried from Dataram.

Would imdisk allow me to copy files  from ramdisk to disk using shadow copy or strarc and even files that are currently being written?

I can afford to lose the last few frames of video in my AVI file, and I have tools that can open a corrupted AVI file and recover everything else.

Thank you again.

Best,

Andy

the %grub% variable should be set to the folder where the batch file LstFext.g4b lives - e.g.

# set batch file folder
set grub=/
# %1 is folder %2 is extension 
/PickaFile.g4b /MYISOS .ISO
echo %FCOUNT% files found
if "%CHOSEN%"=="0" pause --wait=3 No Files found or User Aborted! && configfile /menu.lst
if "%CHOSEN%"=="" pause --wait=3 User Aborted! && configfile /menu.lst
echo File chosen was %CHOSEN%

This will then list all the .iso files in the /MYISO folder and allow the user to pick from a list

CHOOSE .ISO FILE

 

(ESC or 0 = Abort)

 

1 = Fred.iso

2 = Doris.iso

3 = Bill.iso

 

Choose a number (1-3) : 2

 

3 files found

File chosen was Doris.iso

Feel free to modify them for your own purposes!

UPDATED 18.04.2013
Covers installing Windows 7 to VHD, installing and configuring Grub4Dos, installing FiRaDisk driver.
Finally, describes loading VHD image into RAM and booting it.

New, refined videoguide... including x64 instructions and some corrections...

Combined with an updated guide here

http://tech.outcult.com/tutorials/winram/01/

it's now sort of interactive 

Download guide files here.

WinRAM 18.04.13

Category: Miscellaneous

Last Updated 4 weeks ago

is there any way of making USB stick bootable when it is write protected(by switch)? I have several sticks and tried several OS'es on them, but they all fail to boot when i write-protect my pendrive, while working perfectly fine when the drive is unlocked. It seems kinda awkward, when compared to bootable live CD's, which do not require to write anything.

The second thing I want to ask about - I am looking for a fast, small (max 2GB) bootable distro that will boot and work on as many computers as possible, ie. probably having lots of preinstalled drivers. It needs to automatically detect and config simple network, must have r/w access to NTFS drives, ability to detect printers, internet browser, office, and some basic tools. And it should be easy enough for pure-windows person to use it as OS/data backup.

As disscused before...

with ChipGenius v4.00  I found This:

All of them did nothing ......

OK so here the thing.

I have a SONY 13,3' LAPTOP , and two hard drives (2* SSD) , one is on the regular HDD slot > we will call it main OS (1* Samsung 840 256GB) and one is on the ODD-Bay slot > we will call it secondary ssd (replaced dvd drive with caddy).

I need to setup a dual boot for work, and for some security reason (integrity of main system etc) , doing pentest on the second OS.

The BIOS doesnt detect the secondary SSD in the ODD bay, seem like a bios lock or a lack, but the hard drive is detected without problem after one OS as boot (in windows i see it a secondary hard drive, can setup partition like i need to) and linux same.

After a lot of search arround, i have only find 2 way to boot on it

1 -/ Boot on the main OS (hard drive 1*) with vmware/or virtualbox using physical hard drive option

2 -/ Create linux stick with vmware/virtualbox to boot it (same as 1/ but with usb stick, no vmware install on the main os)

But i loose lot of performence by the way and GPU perf too (have geforce 640LE, usefull..)

So, can i made my second ssd bootable with VHD, or with a alternative boot manager ? (Like GRUB4DOS ..)

for example, can i put one VHD with all i need on the ssd, then made a sample script (in a 4GB small usb stick) for launch the booting sequence and boot the VHD on the ssd ?

Thanks for any help   !

http://al-jo.99k.org/iso/Iso.html

i made win7pe using winbuilder.  but i am suffering from installing driver to win7pe.

i get the Driverpack for win7 from driverpack.net and i tried to install driver on my pe..

it did work, but it's too many problem.  

i heard a script 'amalux' script Auto Driver Import W7   from this forum...

i tried to find it from google....,  it was difficult....

if you have this script, please send it to my e-mail.  or  attach below the reply.

my e-mail is anothersky@naver.com

Furthmore,   if you have a better idea which is able to install driverpack to win7pe, please let me know.

Thank you ,in advance

i'm currently using MultiPE to make an .iso win7 pe and boot it via PXE. It works very fine and makes me wins a lot of time

But there is two problems i'd like to solve :

1. During pe init a "host driver 1.6.0" window appear and stop the process until the user click on "Exit". In the "PE network manager" i've check the option "Autostart PEnetwork on PE startup" because i NEED lan connection. If i uncheck this option i need to use an "ipconfig /renew" to get an ip address.

How can i get a lan access an no "host driver" windows at startup ?

2. In the same way at startup the "easydriveletter" ask me to choose a drive letter...i'd like to let it do it by itself without asking. I've tried many differents options in the PEfactory / BootTasks but without effect.

So i put these lines under comments in PEFactory.script but i don't think this is the right way !

[CD_Support]
//If,%PEF_TargetType%,EQUAL,S,Begin
//If,Not,%PEF_ImageType%,EQUAL,X,IniWrite,%easyDriveLetterini%,Params,Newletter,%BootMedia%
//Else,IniDelete,%easyDriveLetterini%,Params,Newletter
//End
//Else,IniWrite,%easyDriveLetterini%,Params,Newletter,%BootMedia%

Thanks a lot for help

Tyler

We got a problem here, maybe you can solve it.

Here is what we did:

1. boot iPXE

2. attach iSCSI disk

3. boot WinPE4

4. install Win8 on SAN device through SMB-shared CD device

5. mandatory reboot while installing windows

6. boot iPXE

7. trying to boot from SAN device

8. nothing happens

Last messages:

Registerd SAN device 0x80

Booting from SAN device 0x80

Our setup:

8 identical computers (all having the same issues)

CPU Intel i7-2600k

VideoCard AMD/ATI Radeon HD 6800

Mainboard Gigabyte GA-H67MA-USB3-B3

with NIC Realtek RTL8111/8168 1Gbps

RAM 8GB

OnBoard-LAN boot ROM

iPXE

the Server:

DNSmasq as DHCP and DNS server

SCST as iSCSI target

TFTP-HPA as TFTP server

Samba3 as SMB server

How we already tried to fix it:

1. upgrade Win7 to win8 (same result after first reboot)

2. succesfully install Win8 on hdd, attach hdd to server, boot from hdd through iSCSI (fails at first boot)

3. replace NIC (same result after first reboot)

4. same procedure on other Computer (completely different HW) (Success!)

5. same procedure on VM (Success!)

6. use working VM image to boot through iSCSI (fails at first boot)

Now we need your help internet! Do your thing!

What is worse, it seems that activating certain functions makes USB flash stick also affected and I need to reformat.

Anyway after checking 3.8GB partition is actually sometimes reported as FAT32 bootable.

I don't think that it deleted anything from HDD because simply there was no time for that, as I plugged and uplaugged in few seconds...

This image shows a lot:

http://i.imgur.com/Zz6EjwF.jpg

XP: NAS negotiation delays explorer shell and takes 2 minutes to connect

I used, XP Lite, nLite, disabled plenty of services, tweaked, etc etc SO, can anyone tell me how to stablize negotiation assuming that I screwed up somewhere and brought Bill Gate's wrath upon me???

Win7 works great... could it be SMB version? Any way to upgrage or use third party SMB? something that exist on WinPE?

- clone your harddisk, create disk images

- disaster recovery for home computer

- mount MacriumReflect image files

- support for x86 and x64 sources

- container script with included program files (5.1 build 5870)
download: MacriumReflect FileContainer

- Win7PE_SE_2012_07_14

- screen resolution switch to 1024x768 (x64 only) on start macrium reflect (the starter switched it back to saved resolution)
- automatical autoassign driveletters on start macrium reflect (the starter switched back drive Y: [Win7PE_SE_2012_07_14 is needed])

Please use this ISO as source (Windows7 x86 sp0) & and a proper download manager when downloading.

If you like this project & find it useful it’s possible to donate a beer or two here:

Note1: This project needs a lot of CPU-power & Ram. Final ISO ≈ 700MB!
Note2: Only tested & working in/with real machines from UFD. No VM's!
Note3: If any problems read this small tutorial/guide first:
http://al-jo.net46.n...PEtutorial.html
 
 

Ps.

Want to make a Win8PE? Have a look here.

________________________________________________________________
Note4:

I’m "only" the maker of the application scripts & credits for the building tools goes to:
NightMan, YahooUK, Lancelot, JFX, sbaeder, ChrisR, Homes32, rpaz, Dera's, Rui Paz, Altorian, Paraglider, Pedro Le 15, Galapo, Ludovici, Vvurat, Max_Real_Qnx, 2aCD, Nikzzzz, Markus Debus, Holger Kotsch, JonF, Joshua, yamingw, Kwyjibo, NetFanTom, Peter Schlang, Amalux, Galapo, CTmag, Nuno Brito + many more...

Has anyone else ever encountered something like this? Thanks.

You have excellent projects for win7 & win8. You should put this topic as hidden link. If you want make win7pe or 8 you should pay money.

No thing to for test. If you want winbuilder without errors you should pay.

If I was rich man I will pay you more but our life is difficult.

• High detection rates for viruses and spyware;
  
• Scanning Scheduler;
  
• Automatic downloads of regularly updated Virus Database.
  
• Standalone virus scanner and right-click menu integration to Microsoft Windows Explorer;
  
• Addin to Microsoft Outlook to remove virus-infected attachments automatically.

G4D version: 0.4.5c 2013-03-03

WENV Compile time: Jan 21, 2011 17:02:23
 

----------

Nuno , 

would you mind if I call both you and Peter "Billy-Bob" in this new, altered perception, reality?

I will then refer to all the "old" Win7PE projects as "Billy-Bob's PE" as well to the new one as  "Billy-Bob's PE", or BBPE OK?

http://www.huffingtonpost.com/mark-c-miller/town-where-everyone-is-na_b_694206.html

Billy-Bob

Plugin for the new generation WinBuilder program.

From developer WEB site:

FreeCommander is an easy-to-use alternative to the standard windows file manager. The program helps you with daily work in Windows. Here you can find all the necessary functions to manage your data stock. You can take FreeCommander anywhere - just copy the installation directory on a CD or USB-Stick - and you can even work with this program on a foreign computer.

Main features in FreeCommander:

• Dual-panel technology - horizontal and vertical
  
• Tabbed interface

• Optional tree view for each panel
  
• Built in file viewer to view files in hex, binary, text or image format
  
• File viewer inside archives too
  
• Built in archive handling: ZIP (read, write), CAB (read, write), RAR (read)
  
• Nested archive handling
  
• Built in FTP client
  
• Easy access to system folders, control panel, desktop and start menu
  
• Copy, move, delete, rename files and folders
  
• Multi rename tool
  
• Wipe files
  
• Create and verify MD5 checksums
  
• File splitting
  
• File properties and context menu
  
• Calculation of folder size
  
• Folder comparison / synchronization
  
• Modification of file date and attributes
  
• Folder / program favorites
  
• File searching (inside archive too)
  
• File filters for display
  
• User defined columns for detailed view
  
• DOS command line
  
• Multiple language support

!!! You need the new WinBuilder program to run this plugin!

• 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

One some occasions when I boot Win7PE off a USB stick it gets as far as the desktop but there are no icons or taskbar and my autorun script does not launch. If I reboot and try again it will work perfectly and I get all of my desktop icons and the autorun script runs. This doesn't happen all of the time, just intermittently.

I have had the same problem with different models of USB stick and also different models of PC (all have 2GB of RAM).

Does anyone have any ideas why this would happen?

Thanks for making ImDisk available. I'm trying to introduce false delay for read/write for my project purpose. I traced the read command finally into the ImDiskSafeIOStream method. Here, I'm circumvented the windows DDK call by creating a dummy buffer and returned this with status success. I've additionally added code here to communicate a message with a user process through named pipe.

I ran an IoMeter read test over the virtual drive, but the message is not being passed to the user process. Have I missed anything? Is this the correct routine which interprets reads/writes to the virtual drive?

I appreciate any help.

Thanks

I want to make Multiboot dvd which contain windows 7 and windows 8 both using easyboot.again I want to make DVD not USB.

thank....

I could make win7pe but I can not make win8pe.

Please I need your help.

It's the first machine I'm trying it on and it didn't work no matter what I tried to change in the BIOS. GRUB4DOS also didn't pick up the CDROM, but in the booted Windows 7 x64 it shows up fine as CDROM plus flash drive. I've tried both with the switch set to r/o and r/w.

The sticks arrived just yesterday via the US. I cheated a bit to get them via Amazon, by asking a colleague located in Florida to forward two of those little things.

• No installation required.
  
• Can be run directly from a USB drive or any other storage device.
  
• Has all major Disk Defrag features, including disk optimization.
  
• Extremely compact, easy to use and fast.
  
• Absolutely FREE for home and commercial use.

It is not, rest assured.

Let's call it a "spin-off" from this thread/posts:

http://reboot.pro/topic/17406-not-booting-to-isosel/

http://reboot.pro/topic/17406-not-booting-to-isosel/?p=165006

Where (the HECK) is the "dirty bit"?

Is it a bit or a byte?

From the mouth of the wolf:

http://support.microsoft.com/kb/322275/en-us

The "dirty" bit is a bit in the boot sector (for FAT or FAT32 volumes), or in the MFT (for NTFS volumes), that is checked when Windows starts. This bit is checked to determine whether corruption has been detected in the file system. If the dirty bit is set on a volume, Autochk runs to correct any errors on the volume.

I strongly suspect that - as always - MS info is either misleading or wrong (or BOTH).

Here:

http://www.raymond.cc/blog/manually-reset-or-clear-dirty-bit-in-windows-without-chkdsk/

the "bit" (that in the meantime has misteriously grown to a WHOLE byte ) is clear enough for NTFS (the actual filesystem we are NOT interested in for matters related to ISOSEL/Isostick)

It is far less clear (and I suspect outright wrong ) for FAT32 (whilst FAT16 is not analyzed at all).

Anyway the identified byte (not bit), confusingly said as being "41" without specifiying if it is hex or dec offset in the bootsector, may correspond BOTH if hex or if dec (i.e. hex 29) to reserved bytes/part of reserved word according to the ONLY source I do actually trust, the Starman's pages:

http://thestarman.narod.ru/asm/mbr/MSWIN41.htm

Quite surprisingly some apparently more reasonable info can be gathered by reading some Apple source code:

http://www.opensource.apple.com/source/msdosfs/msdosfs-163/fsck_msdos.tproj/fat.c

/*
* Determine whether a volume is dirty, without reading the entire FAT.
*/
int isdirty(int fs, struct bootblock *boot, int fat)
{
int result;
u_char *buffer;
off_t offset;

result = 1; /* In case of error, assume volume was dirty */

/* FAT12 volumes don't have a "clean" bit, so always assume they are dirty */
if (boot->ClustMask == CLUST12_MASK)
return 1;

buffer = malloc(boot->BytesPerSec);
if (buffer == NULL) {
perr("No space for FAT sector");
return 1; /* Assume it was dirty */
}

offset = boot->ResSectors + fat * boot->FATsecs;
offset *= boot->BytesPerSec;

if (lseek(fs, offset, SEEK_SET) != offset) {
perr("Unable to read FAT");
goto ERROR;
}

if (deblock_read(fs, buffer, boot->BytesPerSec) != boot->BytesPerSec) {
perr("Unable to read FAT");
goto ERROR;
}

switch (boot->ClustMask) {
case CLUST32_MASK:
/* FAT32 uses bit 27 of FAT[1] */
if ((buffer[7] & 0x08) != 0)
result = 0; /* It's clean */
break;
case CLUST16_MASK:
/* FAT16 uses bit 15 of FAT[1] */
if ((buffer[3] & 0x80) != 0)
result = 0; /* It's clean */
break;
}

and 

/*
* Check the second (index 1) entry of the FAT. It should be set to an
* end of file mark. For FAT16 and FAT32, the upper two bits may be cleared
* to indicate "volume dirty" and "hard errors"; for FAT12, it must always
* be an EOF value.
*
* Also check the "clean" bit. If it is not set (i.e., the volume is dirty),
* set the FSDIRTY status.
*/
value = fat_get(1);
if (value == CLUST_ERROR)
return FSFATAL;
switch (boot->ClustMask)
{
case CLUST16_MASK:
if ((value & 0x8000) == 0)
mod |= FSDIRTY;
break;
case CLUST32_MASK:
if ((value & 0x08000000) == 0)
mod |= FSDIRTY;
break;
default:
break;
}
/*
* Figure out how many bits of the FAT[1] entry to compare. FAT16 and
* FAT32 use the upper two bits as flags, so we don't want to compare
* them. The >>2 part below leaves temp set to the cluster mask, but
* with the upper two bits zeroed. (Note that the cluster mask has
* the lower N bits set.) FAT12 has no flags, and uses all 12 bits.
*

Please note how the byte has suddenly reverted to a smaller bit BUT moved from the bootsector to the FAT.

Additionally it seems like TWO bits are involved

It would be much appreciated if some of the peeps with more C reading capabilities than myself could check the above source code and possibly also check the corresponding Freedos and Linux ones.

The "good" MS originated reference for FAT is if course NOT the half-@§§ed above mentioned KB but this document:

http://staff.washington.edu/dittrich/misc/fatgen103.pdf

which actually (page 18) does re-establish:

For FAT16 and
FAT32, the file system driver may use the high two bits of the FAT[1] entry for dirty volume flags (all
other bits, are always left set to 1). Note that the bit location is different for FAT16 and FAT32,
because they are the high 2 bits of the entry.

For FAT16:
ClnShutBitMask = 0x8000;
HrdErrBitMask = 0x4000;

For FAT32:
ClnShutBitMask = 0x08000000;
HrdErrBitMask = 0x04000000;

Bit ClnShutBitMask

– If bit is 1, volume is “clean”.
If bit is 0, volume is “dirty”. This indicates that the file system driver did not
Dismount the volume properly the last time it had the volume mounted. It
would be a good idea to run a Chkdsk/Scandisk disk repair utility on it,
because it may be damaged.
Bit HrdErrBitMask

– If this bit is 1, no disk read/write errors were encountered.
If this bit is 0, the file system driver encountered a disk I/O error on the
Volume the last time it was mounted, which is an indicator that some sectors
may have gone bad on the volume. It would be a good idea to run a
Chkdsk/Scandisk disk repair utility that does surface analysis on it to look
for new bad sectors.

that the bits are TWO and that they are NOT in the bootsector at all, but rather at the beginning of the FAT.

What is not (yet and to me) clear at all is how the second copy of the FAT is affected, and what happens when just one of the two copies have that bit changed.

Another question is now (reserved to ElegantInvention) WHICH of the two bits (or both) does ISOSEL check? Only the "first one", i.e. the "real" volume dirty one? Or both?

And another one (opened to everyone, but particularly aimed at bblaauw that originally had the idea to run a DOS to change ISO_FILENAME.TXT AND owns an actual Isostick AND usually knows where his towel is ):

How about testing the same ISO_FILENAME.TXT writing in grub4dos? (and if needed settign the stupid bit(s) programmatically from grub4dos)

Wonko

A new step on the winbuilder history is now close to arrive.

If you are interested in testing the new winbuilder before it is made generally available to public, just reply back to this topic until Friday, the 26th of April and provide a compelling reason to be selected.

The private edition will be made available to a maximum of 10 people.

Questions, feedback or feature requests are welcome on this topic too.

I have fixed this issue, and made the programme only report which removable media is available. I mean

you do not want to accidently overwrite your Windows hard drive do you??

Ok here is the the fix,

1. Copy all the text below the dotted line to your clipboard

2. Right mouse click on the "RunMe.bat" file which resides in your Gub4dos folder

3. Left mouse click on it select Edit

4. Press the "Ctrl" and "A" keys together. This highlights all the text

5. Press the "Ctrl" and "V" keys together. This replaces the text with the copied text from below the dotted

    line

6. Close Notepad and save changes

7. Run RunMe.bat

The program will list all available removable drives showing the drive letters. If none are found

the program will prompt you to close and plug one in :-)

Enjoy. CWU

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

@echo off
echo.
echo ===============================
echo WELCOME TO GRUB4DOS - Version 2
echo ===============================
echo = A Clockwork Utility Upgrade =
echo.
set udrv=
for %%x in (syslinux.cfg syslinux.exe grub.exe menu.lst) do if not exist files\%%x goto error

set usbs=
for /f "tokens=2 delims==" %%d in ('wmic logicaldisk where "drivetype=2" get name /format:value') do set usbs=%%d
if "%usbs%"=="" goto nousb
echo Your removable drives on your computer are:
wmic logicaldisk where drivetype=2 get description,name

set /p udrv=Enter the USB Drive (Example F:)
if "%udrv%"=="" goto nodrv
echo.
echo !! WARNING !!
echo.
echo this will install syslinux on %udrv%
echo Press any key to continue (or Close this window)
pause > nul
echo Copying files to USB Drive...
for %%x in (syslinux.cfg grub.exe menu.lst) do echo copy /y files\%%x %udrv%\ && copy /y files\%%x %udrv%\
for %%x in (syslinux.cfg grub.exe menu.lst) do if not exist %udrv%\%%x goto errcopy
echo Making USB Drive bootable...
echo files\syslinux.exe -ma %udrv%
files\syslinux.exe -ma %udrv%
if errorlevel 0 goto ok
echo syslinux.exe error
goto end

:nousb
echo Plugin the USB, and try again
goto end

:ok
echo done
goto end

:nodrv
echo nothing is selected
goto end

:errcopy
echo Error while copying
goto end

:error
echo file(s) missing (syslinux.cfg syslinux.exe grub.exe menu.lst)

:end
echo.
echo Grub4Dos complete. Press a key to quit
pause > nul
cls
exit

Menu.lst

#RAM Test
if "%RUN%"=="" echo Loading KGB Systems
debug off

Boot/bios int=0x15 eax=0x0000e801 > (md)0x300+1
cat --skip=24 --length=4 (md)0x300+1 | set n=
set /a MEMSIZE=0x%n%/16+16
if "%RUN%"=="" set RUN=0 && configfile /menu.lst

#if "%MEMSIZE%"=="2048" configfile /Boot/main.lst
if %MEMSIZE%<=700-1 configfile /Boot/main.lst

color border=7
splashimage /Boot/red.bmp
timeout 30
default 0

title Low RAM Warning:%MEMSIZE%MB Detected 700MB Required 
root ()

title Continue To Boot Acid_PE
configfile /Boot/main.lst

title
root ()

title Reboot
reboot
 
title Shutdown
halt

What i want to do here is to boot to the main.lst automatically if its found that their is sufficient RAM

If their is not then it will sty in this menu

Note that main.lst uses a GFX menu made by Win7PE_SE

With my tests, %MEMSIZE% dose not display a value in this GFX menu

Can You Please tell me what i am doing wrong?

ThanX

Ps: is their a way to find out what tipe of processor is being used?

Because socket 1155,1156 MB's seems to use a different tipe of  memory addressing method

where the script above shows a max of 512MB RAM available on these MB tipe, even if their is like 4GB installed

I would like to just give a warning that a sock 1155 is being used and that the Ram Check May be invalid

Is it just me or is repairing Windows XP easier than Windows 7

In 5.x sfc gets its Original files from a windows source disk,and a "In-place upgrade/Install-Repair" can be done from a non-booting system.

In Windows 6.x the source seems to be a repository on the HDD,this Repository itself can be corrupted by viruses and disk failures  alike.

Most of the time when i run a SFC scan on Windows 7 it ends up with :

Windows Resource Protection found corrupt files but was unable to fix some of them
Details are included in the CBS.Log windir\Logs\CBS\CBS.Log

Most blogs says that you must Run a "In-place upgrade" to repair that but you cant some times because you have to be booted inside a fully working windows to make it work

http://answers.microsoft.com/en-us/windows/forum/windows_vista-performance/sfc-scannow-found-but-could-not-fix-some-corrupt/26c51bfc-3405-46e1-b79b-afb596714e31

To fix files needed to boot windows just run(they say):

sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows

No, this dose not WORK because it gets the files from the same broken repository on the HDD

and now (thy say) FORMAT....

After hours of work i get stuck on lvl one again

One thing i did find to work is to boot in to a PE and Replace some critical files whit ones i copied from my PC

OR With Windows 6.x i have more success repairing it with Restore points than SFC scanning or In-place upgrades

Now for some Questions:

Dose anyone know of a batch-script/program that can Process the CBS.log and Copy needed files atomically from a installation disk?

Is their a better alternative to SFC?

Where is the repository on the HDD in windows 7 so that i can replace it with my PC's repository?

Is their a way to use SFC to get the source files from a Disk?

• Attach SATA disk to computer
     You can create a new partition and mark it as active partition before boot from Windows 7 DVD
  
• Boot from Windows 7 setup DVD (or other media),
  create a partition in SATA (if not already created),
  use diskpart to mark partition as active (if it is not the only partition in the computer),
  install Windows 7
  
• Boot from SATA disk into new Windows 7
  
• Run cmd as administrator
  

  reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v DisablePagingExecutive /t REG_DWORD /d 1

  This setting may help prevents USB drivers code from being paged out.
  Driver's data are not affected by this settings, so ther is still some possibility that USB drivers will fail when in low memory state.
  
• Run usbbootfix.bat
  
• (optional) Run StorageBootStart.bat .  It will set all known disk controller drivers to Start=0.
  Pro: Increase chance of successful boot when move to different machines.
  Con: Increase loading time, slower boot.
  
• Shut down Window.
  
• a. Disconnect SATA disk and put in USB disk enclosure.
  or
  b. Clone Windows to USB disk.
  
• Boot from USB.

• Create partition in USB disk (U:), format, make it active partition.
  
• Use Disk Management or Diskpart to Create VHD image, size 15GB or more.
  
• In Windows Virtual PC folder or VirtualBox, create virtual machine RAM 1GB or more
  
• Attach VHD and Windows 7 DVD or ISO to virtual machine
  
• Start virtual machine, boot from DVD, install Windows 7
  
• Copy usbbootfix.bat to VHD (by network share or mount VHD in host).
  
• In virtual machine, run usbbootfix.bat as administrator
  
• Shutdown virtual machine.
  
• In Disk Management in Windows 7 host, attach VHD.
  
• If you just want to use VHD as source for cloning to USB disk, skip the following steps and goto Cloning Windows 7 above.
  If you want to native-boot VHD, adjust BCD entry for native-boot VHD with the following steps.
  
• Let's assume USB disk partition is U: and Windows partition in U:\name.vhd is V: in host computer
  
• (modified 2009-12-24)
  Copy bootmgr and Boot directory from V:\ to U:\
  Run cmd as administrator in host
  bcdedit /store U:\Boot\BCD /set {default} device partition=V:
  bcdedit /store U:\Boot\BCD /set {default} osdevice partition=V:
  bcdedit /store U:\Boot\BCD /set {default} detecthal on
  Run cmd as administrator in host
  

  bcdboot V:\Windows /s U:

• detach VHD from host
  
• boot from VHD in USB

                       I want to make a bootable USB pen drive, with Easy2boot or Sardu utility. Apart from that I want to my

disk has an UN-formatable or UN-deletable partition which contains all by boot data, so that it cannot be deleted by other user during normal day to day operation.

      I have seen a relative post on write protected usb in rmprep site.

http://www.rmprepusb.com/tutorials/97---write-protect-or-make-a-cd-dvd-partition-on-a-flash-drive

My question is is it possible to create write protected bootable partition on usb with all boot files.

          Tell me is this possible. If yes, please guide me with a tutorial on the same

Thanking you

Kishore

!BAT

insmod %0 subRoutine > nul

WENV for /L %c in (1,1,5) do call :subRoutine %c

goto :EOF

:subRoutine
echo First parameter is %1

Also I tried the following:

1. WENV for /L %c in (1,1,5) do call subRoutine %c
2. WENV for /L %c in (1,1,5) do call :subRoutine
3. WENV for /L %c in (1,1,5) do wenv call :subRoutine %c
4. WENV for /L %c in (1,1,5) do wenv call :subRoutine %c
5. WENV for /L %c in (1,1,5) do call ${cmd} ..........with wenv set cmd=:subRoutine
6. WENV for /L %c in (1,1,5) do call ${cmd} ..........with wenv set cmd=subRoutine

But a statement like this is working perfectly fine outside the body of "for"

call :subRoutine 5

The output is: 5, as expected.

longer have the core.img, which seems to be replaced by x.cfg or something. Also, there seem to be some new sort of softlinks where you can.t even get the targets. Does anyone at least know how to grub4dos-boot the newer

stuff?(I suspect the new way has to do with UEFI compatibility)

How I can burn them in one cd and during boot show in boot screan two options like next

win7

win 8

and If I pressed win7 it will open win7pe

I want to know after making win7pe where there is MBR.FIX and what is advantage from this program

• Download WinBuilder 0.78 SP4 and extract the archive
  
• Run WinBuilder.exe
  
• In the Main windows (Download Center) enable any project (is it a bug that the icons on the right only appear when a project is selected)?)
  
• Deactivate the project you selected and instead click on the topmost icon to the right of the project list (Add new web server)
  
• Enter "joshua.winbuilder.net/Projects"
  
• Download all scripts you would like to use (note, if you're going to use my script set you might disable some large scripts like Apps/Net/opera, Apps/Security/Antispyware/SpybotSD, Apps/Security/AntiVirus/Avira and probably more) - if in doubt just download everything.

• Download and extract my script set provided in this thread (first post)
  
• Overwrite the contents of the "Projects/" folder with the content provided in my archive. Don't worry, it will not overwrite any scripts or files, it just adds some tools to the "Tools/" folder as well as a "Skybeam" sub-folder to the "Win7RescuePE/" folder.
  
• Now re-launch WinBuilder

• Click on the "Source" button on top
  
• Enter path to your Windows 7 32-bit DVD in "Source directory"
  
• Clickk on "Script" to get back to script mode
  
• Click on "Configuration", I just did small changes here:
  
  • Screen resolution: 1024x768 (well, your taste)
    
  • Disable the "Enable loader hidden menus" option (well, I don't like hidden stuff)
    
  • Hardware detect modus: 3 (I don't like to do this manually every time)
    
  • Don't forget to click "Save"

• Open "Build/PreConfig"
  
  • Click "Get Info"
    
  • Select your Install.wim image ("5: Windows 7 ULTIMATE" in my case)
    
  • Select your Boot.wim image ("2: Microsoft Windows Setup (x86)" in my case)
    
  • Click "Check Source" to verify your configuration

• Open "Build/Copy Files"
  
  • Enable "Addition fonts"
    
  • Enable "Some recovery tools (requesting MS Win7 DVD)" (there is a typo in "reguesting" ;-)
    
  • Enable "Other Language Files"

• I left the "Shell" Script disabled
  
• Enable the "Skybeam/Base" folder (all scripts)
  
  • You might customize the Grub4DOS script as you like
    
  • Change "Locale settings" as you like

• Keep the "Addons/MMC" script enabled
  
• Keep the "Net/Extra NIC Drivers script" enabled
  
• Keep the "PENetwork Beta V5t" enabled
  
  • I checked the "Check for newer version of PENM online" option and left the remaining options untouched

• All other "Net/*" were left disabled (I don't need them)
  
• I left all scripts in the "Tweaks/" folder enabled
  
• Disable all "Apps/" scripts of Win7RescuePE
  
• Re-enable Apps which you would like to use but are not part of my script collection. I've enabled the following only:
  
  • "Apps/Net/Remote Connect/Remote Desktop Connection"
    
  • "Apps/Security/Antispyware/HijakThis! V2.0.2" (not part of my script collection)
    
  • "Apps/KeyFinders" (all)  (not part of my script collection, no official download URL)
    
  • "Apps/System/Pserv V2.7" (not part of my script collection)
    
  • "Apps/System/Xchm 1.9" (not part of my script collection)

• Now enable all "Skybeam/App" scripts (or of course only the ones you would like to use)
  
• Now enable all "Skybeam/OtherOS" scripts  (or of course only the ones you would like to use)
  
• Make sure "OtherOS/Parted Magic Linux" is disabled if you're enabling my "Skybeam/OtherOS/Parted Magic Linux" script (they conflict)
  
• Now enable all "Skybeam/Finalize" script
  
• Make sure "Finalize/*" scripts are disabled - they will screw up the GRUB configuration written by my scripts
  
• If you would like to generate an ISO image use my "Skybeam/Finalize/Create ISO" script instead of the "Finalize/Create ISO" script included in Win7RescuePE
  
• I left the "VirtualTest" scripts disabled

• Unselected Expanded Folder
  
• Mandatory Script
  
• Unselectable Script
  
• etc.

• Select this Script
  
• Unselect this Script

• Select this Folder
  
• Unselect this Folder

The goal here is to have huge free space for the %SystemDrive%, less time to map on memory and, have less I/Os with physical disk.

- if run at startup, automatical search maximal supported resoution

- optional show message to break  the switch-process

- detect if PE is running as virtual machine and skipped the switching-process

- as an alternative can be set for virtual machines a maximum resolution

- not recommended for CRT-Monitors

- none

#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.

At the risk of looking like a spammer I'm using this space to announce the introduction of "BukerPXE" to the Goggle Play market for Android.

The description is regurgitated here for the forum consumption:

BukerPXE is a lightweight TFTP, FTP, HTTP, and proxyDHCP server suitable for hosting PXE payloads from your Android powered device over your local LAN using its built in WiFi adapter.

Originally devised as a portable diagnostic toolkit capable of booting a non-functional workstation into various diagnostic environments, BukerPXE runs on your Android phone to listen for network boot requests from machines configured with PXE network boot capability. (the vast majority of computers have this available in their BIOS
options).

The client computer then boots to display a simple menu consisting of various PXE payload options which can include diagnostic utilities, bootloaders, installers etc.

BukerPXE works with your existing LAN infrastructure, the main requirement being that the client computer and the Android Wifi device be on the same LAN subnet. The client computer typically plugs into the network via Ethernet cable, and your Android device connects via WiFi. Using its built in proxyDHCP service, BukerPXE is designed to work alongside the existing router or other DHCP server without modification. This makes it easy to deploy and does not interfere with normal network traffic.

The Lite version uses the TFTP protocal only to transport the payload to the target machine. Payloads can easily be added or removed using conventional syslinux based text menus. The default Lite version comes with MemTest86 for RAM testing, NTPSSWD a password reset utility for editing/removing Windows user passwords on target Windows PC's, MHDD a hard drive testing and reporting utility, and HDT a hardware detection tool that enumerates the hardware installed on the target machine. These are included as simple examples of PXE network booting,
demonstrates compatibility with your device and existing networks, and provides some usability straight out of the box even if you decide to not define your own payloads or move up to the full version of BukerPXE.

The full version of BukerPXE allows many more larger and practical payloads as it leverages the iPXE protocol with the speed of FTP and HTTP transfers.

I invite all you freindly Rebooters with Android devices to visit the link below and take it for a spin.  It *DOES REQUIRE ROOT ACCESS*.  So if you haven't rooted your device yet, now you have yet another reason.      

Currently only the LITE version is available to the public, and it is, and shall remain free of charge.  All I ask is for constructive feedback either here, on the project Website, http://bukerpxe.com (under construction) or via the conventional Google Play store reviews.

Due to the massive amount of devices out there, it is impossible for us to test even a small portion of them, so we are keenly interested your experiences.  

Keep in mind this is my first app idea, and the first of its kind on the market EVER!!!  It is currently very simple compared to what many of you are used to, but the full version is evolving quickly, and even the LITE version is still a work in progress.   So:

  PLEASE BE GENTLE!!!  

Click HERE---->  http://goo.gl/vigAn

And THANK YOU ALL!!  For being such an inspiration, honestly.  I mean that.

The script is here.

Note: You need to present your projects on this competition before the end of this year.
 

Note: To see who won this competition, please visit http://reboot.pro/17801/#168335