Quantcast
Channel: Reboot.pro
Viewing all 6812 articles
Browse latest View live

Windows 7 install from iso in hard disk

$
0
0

I have a Windows Seven ISO in hard disk.

Do it is possible to install it from hard disk with grub4dos?

I'm not able to a clear howtodo.


Proxy-mounted disks and FILE_FLAG_NO_BUFFERING writing

$
0
0

Just double-checked, that it is not my code problem. I see it on both 1.8.x and 1.9.4.

When I mount something like this as a disk:

using (var stream = new MemoryStream(checked((int)size)))
using (var provider = new DevioProviderFromStream(stream, ownsStream: false))
using (var service = new DevioShmService(provider, OwnsProvider: false))
{
  service.StartServiceThreadAndMountImDisk(ImDiskFlags.Auto, mountPoint);
  wait for key...
}

Then format disk, and try to write to a file on it with FILE_FLAG_NO_BUFFERING option set (file already exists, and has non-zero size by the time I do that). It always fails, complaining about something like System.ArgumentException: Handle does not support synchronous operations, which deep inside appears to be unaligned access, just like in this topic: http://reboot.pro/topic/4112-imdisk-proxy-type-mount-cant-work-with-winhex/?hl=file_flag_no_buffering

 

The same test with FILE_FLAG_NO_BUFFERING works perfectly on real disks, and ImDisk-mounted disks, mounted directly (e.g. not via proxy).

 

This problem appears on the very first write, where I try to write 1MiB of data at file offset 0, so I assume alignment should not be a problem.

Speed of tools installed in WinFE

$
0
0

Hi

I have created a bootable external Hdd with WinFE image and added a disk hash software utility in it. While testing,I found that the speed of this hash utility running in normal windows platform is higher than in Windows FE environment(Same machine). Why this happen?

Is there any method to improve the speed of this utility? do I have to add/ set any cab/parameters to WinPE image to increase the execution speed of the added tools ?

Graphicsmode syntax

$
0
0
What's the correct syntax for graphicsmode in latest builds?

README_GRUB4DOS.txt suggests
graphicsmode 0x6A
This results in a tiny little unreadable line on the top of the screen on a typically troublesome Dell Latitude E6400.

From latest stock menu.lst
## set vbe mode

graphicsmode -1 640 480:800
This works fine on that laptop. Now can use longer lines in menu titles, thanks.

How to interpret this syntax "-1 640 480:800" ?

What is real world experience about properly displayed and supported modes?

Over $50 in Paid Apps & Games FREE at Amazon 6-25-2015 (Offer ends July 1, 2015)

Help me. Please !

OpenBSD vs Windows 7 Dual boot

$
0
0

Hi every body,

I installed windows 7 on my HDD and then install OpenBSD to a free partition of my HDD.

Now, I can boot only to Windows 7.

I did the steps of http://cromwell-intl.com/linux/multiboot-windows-openbsd/but nothing changed and I can not boot to my OpenBSD by bcdedit.

Also when I boot from a live cd I can boot forward to my OpenBSD but I want to create a boot menu to select which OS booting.

So, Which tools can install on my HDD to perform the boot selection menu?

Thanks.

[script]PENetwork

$
0
0

Hi everybody,

here you can find the current information about my "PENetwork"-manager project - primary for LiveXP and Win7PE systems.

The current version you can always download from 'my' personal WinBuilder-website (http://holger.winbuilder.net).

At the moment the most time I'm writing on PENM itself.
However, some older WinBuilder scripts for LiveXP and VistaPE you can still find there.

If you have any questions, suggestions or problems just let me know.

Tested by others and me with Win7 / Vista / XP / W2K3-source and VMWare / VirtualBox / QEmu / RealWorld - thank you all very much :)

Greets...
Holger

 

Current state:
31.01.2014 (PENM 0.58.2):

- Changed: Recompiled with AutoIt3.3.0.0 to better work with virus scanners
No functional change!

 

08.10.2013 (PENM v0.58.1):
- Fixed: GUIDisable mask option missing

 

07.10.2013 (PENM v0.58):
- Fixed: Missing translation applying after language change for connect menuitem in network browser
- Fixed: After saving new color scheme in profile editor it was not applied to the list of the existing schemes
- Fixed: Window focus on profile deleting in profile editor
- Fixed: Profile deleting in profile editor
- Fixed: Wrong label length calculation in network startup dialog
- Fixed: IP address was not deleted if last item in network browser window was removed
- Fixed: Missing color scheme apply on checkboxes if Windows styles are enabled
- Changed: Profile editor reworked
- Changed: Detailed PE version in debug log
- Changed: Position of tray info window now near the tray icon
- Added: Cmdline parameters /ini= for loading a specified ini file
- Added: Cmdline parameters /profile= for loading a specified profile directly from file
- Added: 'GUIDisable' mask parameter (ini, reg, cmdline) to show only some specific tabs ("Config"/"IP" & "About" are always shown)
- Added: Version infos for WIN_8.1/WIN_2012R2 (WinPE5.0)
- Added: Icon for AC wireless networks in available wireless networks
- Added: More ini options are changable via profile editor
- Added: Simple preview window in profile editor
- Added: Simple check for entered addresses (IP, SM, DG, DNS, WINS) in profile editor
- Added: Simple check for entered MAC address
- Added: Some more visible options to color schemes tab in profile editor
- Added: Key accelerators for profile editor
- Added: Tooltip for profiles file cause file path can be larger to display
- Added: Frame color for diabled buttons now changable via schemes/profile editor

 

Note!: network browsing doesn't work in QEMU by default cause of the buildin firewall

History:

Spoiler


Script-screenshot:
PENMScript-Mini.jpg

Screenshots of PENM at work:

Latest version:

PENMCurrent.gif

Dark color scheme:
PENM09-Mini.jpg
 


Boosted Board - Electric Skateboard hitting 22mph

Universal HDD Image files for XP and Windows 7

$
0
0

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

*** IMG_XP package ***

Make XP and Win7 Universal Image files booting with Grub4dos Menu on HDD or USB

Download -  IMG_XP_85 - mirror

 

In Win7 OS Set User Account Control Off and Reboot

First Prepare XP Setup ISO file with integrated UpdatePack and DriverPacks as described below in section 2.
and Copy XP Setup ISO file to the root of internal harddisk drive of your computer.

1. VHD_XP_Create.exe - Make VHD file and Install XP in VHD by using Grub4dos Boot Menu on HDD

VHD_XP_Setup.png

0. Run IMG_XP.exe and Extract to simple path on your Local Harddisk - gives folder IMG_XP
1. Use IMX_XPmakebtimdiskinst.exe to Install ImDisk driver (if not present)
- Imdisk is used by USB_XP_Fix.exe to mount VHD and HDD Image files in a virtual drive
2. Run VHD_XP_Create.exe to create XP-1.vhd and Grub4dos Boot Menu for Install of XP in VHD

- Boot Drive - FAT32 or NTFS - can be USB-stick so that there are no changes needed in the Windows installation on the internal harddisk
- System Drive - NTFS - where VHD file is created e.g your internal harddisk drive
- XP Setup ISO file - located on internal harddisk drive so that fast loading into RAM is enabled
3. Reboot and in Grub4dos menu select Start XP Setup on XP-1.vhd - WinVBlock driver

- XP-1.vhd has already NTFS compressed format, so you should NOT format at Setup, just keep settings
- Format XP-1.img inside XP Setup cannot be used, it results in corrupt message
4. After Reboot select Continue XP Setup and then Reboot to Start XP from Image XP-1.vhd
5. Reduce size and improve settings as usual and Install missing Drivers but NOT the specific large Video driver
- Reduce size to get rid of pagefile.sys and hiberfil.sys via:
- right click My Computer > select Properties > Advanced > Change Virtual memory > select No pagefile and Set
- right click on Desktop > Screen Protection > Energy > Uncheck Sleep settings to get rid of hiberfil.sys
- Set System Restore and Windows Update Off and delete 350 MB of dllcache folder via cmd SFC /purgecache (or Run PURGE_DLLCACHE.BAT)
- In Device Manager Install missing Drivers but NOT the specific large Video driver
- For Universal XP don't Install the Video driver. You can Uninstall the Video driver so that you still have high resolution on any hardware.
- Set Screen Resolution to 1024 x 768 useful on all monitors (right click on Desktop)
7. Connect USB-HDD where you want to use XP Image, so that USB-HDD settings are known in XP registry, and Reboot
8. Reboot with other OS and copy XP-1.vhd to bootable USB-drive and create entry in Grub4dos menu.lst
- BOOT_USB.exe can be used to make USB-drive bootable with Grub4dos Menu - http://www.911cd.net...showtopic=24424
- BOOT_IMG.exe can be used to make Grub4dos Boot Menu on existing bootable drives
9. Run USB_XP_Fix.exe and Select your XP-1.vhd file on USB-drive and click GO
10. Reboot from USB on the same computer and Select Boot XP Image - XP-1.vhd - WinVBlock FILEDISK
11. Reboot from USB on other computers and Select Boot XP Image - XP-1.vhd - WinVBlock FILEDISK - to make Universal

When booting on other unknown machine, then XP will auto adjust itself in about 3 min and install the required drivers.
In this learning process, the registry gets extra info on how to boot on that machine and will use it next time and so XP becomes Universal.
This process requires that you have the WINDOWS\DriverPacks folder of 135 MB available with Chipset + Processor + MassStorage + LAN drivers
and that DevicePath in the registry was properly set by the Keep The Drivers Option KTD (see below and in Picture).

Thanks to Sha0 for making WinVBlock driver - http://reboot.pro/8168/
Thanks to cdob for making usb_xp_init.cmd - http://www.911cd.net...o...22473&st=37
Thanks to sara - pmedia for her tutorial - http://reboot.pro/13731/

More Info on direct Install of XP by using grub4dos menu and WinVBlock or FiraDisk driver:
cdob - Install XP from a ISO file No RAM disk - http://www.msfn.org/...rom-a-iso-file/
Doodoo - http://reboot.pro/13...385#entry122385
sara - pnedia - http://reboot.pro/13731/
wimb - http://www.911cd.net...showtopic=23553
karyonix - http://reboot.pro/88...737#entry121737
karyonix - http://reboot.pro/13967/

 

In case of a hidden boot partition containing Boot folder and file bootmgr of Windows 7,

then Grub4dos Boot menu for Install of XP in VHD can be made  by using USB-Stick as Target Boot Drive.
 

Grub4dos Menu for Install of XP in VHD by using XP Setup ISO file and WinVBlock driver

 

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

 

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.

efb6ab99f77d04f8dc83bc2ed4588711b8886ea2

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

cheers.gif

 

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

 

Wait4UFD driver Enables Direct Install of XP in VHD on USB
Advantage of Direct Install of XP is that one does not need to make changes in the booting of the local harddisk,
where changes might be unwanted or difficult as in the case of a hidden Boot Manager partition e.g. Windows 7
 
First XP Setup ISO file was prepared as described in Section 2 here
DPsBase.exe was used to Integrate DriverPacks Chipset + Processor + MassStorage + LAN + WLAN
(settings Disc - Method 2 - GuiRunOnce - Enable KTD for the DriverPacks I will Select C+P+M+L)
 
 
1. IntegrateDrv was used to integrate Wait4UFD driver in the XP Setup Source directory containing folder i386
2. ImgBurn was used to make new XP Setup ISO file, that was copied to NTFS formatted active partition of USB-harddisk
3. VHD_XP_Create.exe was used to make 2 GB NTFS VHD on USB and to make Grub4dos Menu for WinVBlock driver
4. Boot with Grub4dos Menu from USB and Install XP in VHD using Start TXT-mode / Continue GUI-mode / Boot Windows XP VHD
5. After Install of XP then Run USB_XP_Fix.exe and Select your XP-1.vhd file on USB-drive and click GO
to make XP Universal for booting from USB connected to any computer.
 
================================================================================
 
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).
 
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. 
Download preferred version RVM Integrator 1.6.1 Beta 2.1
 
Windows XP UpdatePacks and Addons:
Onepiece XP Post-SP3 AIO Update Pack FINAL - http://www.ryanvm.net/forum/viewtopic.php?t=6438
Onepiece XP Post-SP3 AIO International Update Packs FINAL - http://www.ryanvm.net/forum/viewtopic.php?t=10445
 
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.
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.
(settings Disc - Method 2 - GuiRunOnce - Enable KTD for the DriverPacks I will Select)
 
Always first use RyanVM Integrator and then use DPsBase to Improve your XP-Source
DPsBase makes presetup.cmd in folder I386 and changes the I386\winnt.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 WINDOWS\DriverPacks 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_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion 
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
 
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/board/index.php?showtopic=110783
At end of TXT-mode XP Setup the folder $OEM$\$1\Drivers is copied to C:\Drivers
and $OEM$\$1\Install\DriverForge.v4.5.4.exe is copied to C:\Install
For Auto Use of DriverForge at T-9 add uncompressed driver folders in $OEM$\$1\Drivers
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"
 
Smart Driver Backup 2.12 of Jaque is very useful to Backup your drivers before install of XP
 
================================================================================
 
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
 
1. Remove 3 folders LANG  WIN9XMIG  WIN9XUPG - reduction in size = 135 MB
2. Run ImgBurn - Portable Tool in PStart Menu - IMG_XP\MULTI\PStart\Progs\ImgBurn
   - 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_USB\makebt>bbie M:\XP3_1201.iso
BBIE - Bart's Boot Image Extractor v1.0, © 2001, Bart Lagerweij
will make BOOT_USB\makebt\image1.bin that you can rename as bootsect.bin
 
================================================================================
 
POST_FIX Tools for XP - 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_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
is set to what DriverForge needs. 
It means that any previous settings are lost e.g. for making use of the KTP C:\WINDOWS\DriverPacks 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 to XP:
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_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
is set to subfolders of C:\D
 
================================================================================
 
Portable Windows HD Image files booting from USB 
 
================================================================================
 
The Apps VHD_XP_Compact.exe and VHD_W7_Compact.exe of IMG_XP package
can be used to make Portable Windows VHD Image files booting with Grub4dos Menu on HDD or USB
 
These Virtual Harddisk VHD files 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
 
Target Boot Drive can be FAT32 or NTFS USB-drive used only for Boot files so that booting of internal harrddisk is NOT changed.
Target System Drive must be NTFS and is the drive where the VHD file is created and this can be your internal harddisk drive.
 
Booting from USB on computers with UEFI-firmware requires that the Boot Drive has FAT32 format.
 
Possible Scenario's 
- Boot with Grub4dos Menu on NTFS or FAT32 USB-Stick with VHD located on NTFS Drive of Internal Harddisk
- Boot with Portable USB-harddisk and launch VHD located on NTFS System Drive of USB-Harddisk
 
Booting VHD files from Grub4dos Menu as FILEDISK or as RAMDISK requires to Install in Source VHD either FiraDisk Or WinVBlock driver.
Additinally Installed Programs and Drivers and Settings are remembered in FILEDISK just like in normal Windows OS.
Loading the VHD into RAMDISK is much faster when the VHD file is located on the internal NTFS harddisk drive.
 
Source can be drive where Windows is installed or full XP VHD 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_XP\Help_Info\WinVBlock_Install.txt
- Install FiraDisk driver with R-mouse on firadisk.inf in IMG_XP\makebt\firadisk-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 VHD_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 200 MB - including WLAN + Audio + Printer + 7-Zip + ImDisk and all installed drivers
Portable 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.2 GB and for Windows 7 VHD file is 2.0 GB.
 
VHD_XPC.png  == VHD_W7C.png
 
Grub4dos Menu for Win7-1.vhd and using FiraDisk driver

 

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

 

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

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

 

3. Boot Win7 VHD Image file from USB
 

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
 

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

Win_Restore.exe can be used to Restore XP or Win7 from VHD to HDD-partition.

For Restore of Win7 from VHD you need to run Win_Restore.exe in Win 7/8/7PE OS 

so that bcdboot.exe can be used to generate Boot Manager Menu required to boot Win 7 from HDD-partition.

- BOOT_IMG  makes GRUB4DOS Menu on Target Boot Drive for selected VHD File on NTFS Target System Drive (copy occurs if needed).

In general ImDisk must be installed in XP or Win 7/8 by using previously the provided imdiskinst.exe file.
ImDisk is used to mount VHD Image file in a virtual drive.
To Install ImDisk driver on Vista and Windows 7/8 you need to turn off UAC, User Account Control
http://www.ltr-data.se/opencode.html

The 64-bit FiraDisk driver requires in x64 Win7 to set  testsigning switched on.

Open Command Prompt as Administrator:

bcdedit /set testsigning on

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

Thanks to karyonix, more Info see:
FiraDisk - http://reboot.pro/index.php?showtopic=8804

Install FiraDisk driver in XP with R-mouse on firadisk.inf in IMG_XP\makebt\firadisk-driver- folder

 

Development and historical thread here:
Thanks to joakim for starting the subject
http://reboot.pro/index.php?showtopic=9227

Installing Windows Embedded Standard 7 SP1 on Panasonic CF-53 laptop.

$
0
0

Hello Everyone,

 

I'm pretty new with the Windows Embedded & installing windows from USB.

 

I'm trying to install Windows Embedded Standard 7 SP1 on Panasonic CF-53 laptop.

I've plugged my USB and made a bootable USB using rufus (https://rufus.akeo.ie/) and this ISO:

en_windows_embedded_standard_7_sp1_runtime_x64_dvd_651894.iso

 

When I've booted from the usb > Clicked "Build an Image", I get the following error message:

"A required CD\DVD drive device driver is missing".

 

So I've downloaded the Win PE x64 & x86 drivers from Panasonic's website:

kyPKEqA.png

And then used Microsoft's KB to add additional drivers to the boot.wim file:0

https://technet.microsoft.com/en-us/library/dd799289%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

 

Then I've replaced the boot.wim file (under the sources folder) in the bootable USB I've created with Rufus.

I've tried this procedure with x86 and x64 but I still get the "Load driver" message box.

 

What am I doing wrong?

 

I'll be very thankful for your assistance, thank you!

David.

Avengers of Oz: Age of Tin Man

$
0
0

 

What happens when you mix the Wizard of Oz and Avengers? maybe something like this.

 

 

 

I would watch it.

Looking for quick/painless way to overcome NTFS file/foldername restrictions

$
0
0

I am trying to download an approx 100GB megatorrent, consisting of rare/old/specialty occult materials. It is mostly ebooks, along with some videos and photos. The intent is to get and keep it available and shared between me and others of a like mind. All of the files are already available for free legally, or are out of copyright/in the public domain. However, the people who originally compiled these torrents saved some of the files with characters like :, ;, etc. Windows cant have these characters in filenames. Utorrent complains that quite a few of the files either cant be downloaded/written to disk due to this, or says that some arent accessible.

 

We have decided that it will be necessary to save these files in a filesystem that is more robust than NTFS, and allows for these characters. Said FS needs to be shareable between Windows/Linux. File permissions are of no concern, but I think that NTFS, FAT32, and exFAT simply wont be suitable. A few of us use Linux, with varying degrees of familiarity with said OS. I'm that maybe EXT4 would be the best FS to use. There is a driver called EXT2Fsd, that allows both read/write access to EXT4 volumes in Windows.

 

A few possibilities I'm thinking might work (but not sure) are:

 

1. Create an encrypted container in TrueCrypt/VeraCrypt (TC clone/fork but with improvements), format as ext4, then mount the container with a drive letter/mountpoint, and instruct our torrent clients to save the files there. However,this adds unnecessary encryption overhead.

 

2. Create a raw disk image, like a VHD, then create a 100GB partition within the VHD and format it as ext4. This can then be shared between both OSes.The files within can be renamed/moved to mert Windows filename standards, which Linux/OS X/Android have no issues with. Afterwards the collection can be recompiled and publicly distributed. The disk image can also be easily cloned, checksummed, and split into smaller chunks for distribution.

 

Ia there a better disk image type than VHD for this purpose? Perhaps there is a different and more common filesystem that meets our standards? Are encrypted containere feasible or simply too much effort? We will also need to use common/standard/free tools that arent overly complex.

 

Any ideas/suggestions are appreciated...........

FiraDisk and WinVBlock Performance

$
0
0
Inspired by this comparison of ramdisk drivers and the huge differences in the Random 4k performance, i was wondering, if anyone already tested the two drivers for performance, in this most important category for a system drive?

:cheers:

WinVBlock

$
0
0
WinVBlock is a free and open source Windows driver for using virtual disks. These disks appear in the Device Manager and Disk Management. It was originally derived from WinAoE, courtesy of V.

Currently supported are:
  • RAM disks
    • Supported for booting from
    • MEMDISK-established
      • Floppies
      • Hard disks
      • Optical discs
    • GRUB4DOS-established
      • Floppies
      • Hard disks
      • Optical discs
  • File-backed disks
    • Using the winvblk.exe command
    • Floppies
    • Hard disks
      • Supported for booting from via GRUB4DOS mapping
    • Optical discs
      • Supported for booting from via GRUB4DOS mapping
  • AoE disks
    • Supported for booting from as established by gPXE or another SAN-booting mechanism, or
    • Using the winvblk.exe command
    • Hard disks
You'll find the WinVBlock and AoE drivers attached to my most recent post.

Source code should be available at the Etherboot & gPXE projects, courtesy of their project leader, Marty Connor.

Work on this driver was and is prompted by the discussion found in this thread.

See also: FiraDisk by karyonix. Fine work.

Examples:

Using PXELINUX and the MEMDISK included in the .ZIP file to create a hard disk in RAM
Directory layout:
/tftpboot/

/tftpboot/pxelinux.cfg/

/tftpboot/pxelinux.cfg/default

/tftpboot/memdisk

/tftpboot/RamXP.HDD
/tftpboot/pxelinux.cfg/default file:
DEFAULT ramxp

LABEL ramxp

  KERNEL memdisk

  APPEND raw

  INITRD RamXP.HDD

SYSLINUX, EXTLINUX, and ISOLINUX config-files could be the same as above

Using GRUB4DOS to create a hard disk in RAM
Directory layout:
/menu.lst

/RamXP.HDD
MENU.LST file:
default 0



title RamXP

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

  map --hook

  root (hd0,0)

  chainloader /ntldr

Using WinVBlock in a Windows XP/2003 PE environment (such as BartPE)

Make sure you include:
  • \I386\System32\Drivers\WVBlk32.SYS (or WVBlk64.SYS)
Make sure TXTSETUP.SIF includes:
...

[SCSI.Load]

wvblk32 = wvblk32.sys,4

...

---ORIGINAL POST FOLLOWS---

I swear that I read something about this before, but I am really lame with searching Boot Land. Way, way, too many posts to sort through and never find what I'm looking for. Then again, maybe it's because I never really read it. ;) I guess I'll have to search on searching to find out what I'm doing incorrectly.

Anyway, yeah: Has anyone experimented with establishing a RAM disk from GRUB4DOS, booting that RAM disk to some flavour of XP (full/"PE") and having any version of RAMDISK.SYS pick up the GRUB4DOS-established RAM disk and provide it as the boot volume, thus avoiding our favourite friend STOP 0x...7B?

FYI, I'd really like to start working on an XP driver with just such support, but have to balance the time investment out with some practicality, meaning testing such equivalent functionality, if it already exists in another form.

I don't mean with ramdisk(0) and /rdpath= entries, thanks. ;)

As an aside, there appears to be a blend of .SDI users and others, but I find a plain partition image to be way easier.

Some other "words" for future searchers:

map --mem blah
map blah (rd)
RAMDISK.SYS
Unmountable Boot Volume Prevention

- Sha0 Miller

Multi-Wim

$
0
0
I have ported my MultiWim-script from VistaPE to Win7PE
What it does?

You can use multiple wimfiles in one ISO selected over Microsoft-Boot-Menu in addition to grub4dos startmenu.

An example:
1. WIM - Standard for machines with more then 1gb RAM (Explorer, IE, MMC and more Addons)
2. WIM - Minimal for Machines with lower then 1gb RAM (BSExplorer, no IE, no MMC and more)

How does it work?

At first compilation deselect MultiWim and deselect 'Create ISO' and enabled only addons for minimal version. If is finished copy the wim-file fom target\source\boot.wim to another dir (for example %BaseDir%\multi-wim) rename the file to boot2.wim.
At second compilation select MultiWim and ISO and all Addons and shell for standard-version. In MultiWim select the copied boot2.wim and set the caption for the Boot-Entry.
Thats all
At runtime you can select the two versions for WIN7PE.

Here you can download it:

Attached File  MultiWim.7z   8.13KB   222 downloads

Place it in Folder OtherOS.

regards
2aCD

grub commands on bootable USB to completely ignore a partition

$
0
0

I have spent some time reading around this forum but I need some help.  Be patient I am new and trying here.  I hope Steve6375 finds this post because his brains would come in handy about now.  There are many great folks here and I readily admit I am a newbie.  In fact I am using a "fossil" grub4dos but it is working great.

 

This is not just another TrueCrypt thread.  I am currently using grub4dos on a bootable usb as needed.  I mount 7 Pro as a normal unencrypted system disk and a hidden encrypted 7 OS on half my machines using grub4dos.   On these machines I remove the TrueCrypt bootloader and run an unencrypted 7 OS in sda1.  I use a grub4dos bootable usb to mount the hidden OS when needed -- its in sda2.  Its basic stuff really but I'll paste here for reference:

 

title TRUECRYPT RESCUE DISK
find --set-root /tc.iso
map --mem /tc.iso (hd32)
map (hd0) (hd1)
map (hd1) (hd0)
map --hook
root (hd32)
chainloader (hd32)

 

 

 

I have used and helped scores of folks with TrueCrypt and now I want to take this to another level.  I made a sector by sector image of sda2.  I have acid tested the image by destroying sda2 in the original location and then replacing it with the saved image.  It works perfectly so its ready to go and accurate.

 

My project:  is to redeploy the sda2 image to somewhere else on the disk better concealing the fact that there is a hidden OS in play.  Then I can overwrite the current sda2 and put something else in its place.  The TC code goes to the following address to find the hidden OS:  For system encryption, bytes 65536–66047 of the first partition located behind the active partition* are read into RAM.  Since my image is exact when I redeploy it the header address will be the same (65536-66047).  By not changing the original size of the normal system disk, the cloned hidden OS will match size with the original donor, meeting many of the TC parameters so it should pass any crc tests.

 

Using Grub4dos how can I either hide,make active/inactive, etc  so that when the grub4dos usb is booting it will completely ignore sda2 and look at sda3 instead? (sda3 is an example so lets use it).  I don't need TC to see anything other than sda3 in this example and ignore sda2 completely.  Maybe a command line structure could make TC think that sda3 is sda2 (re-map?).  I am open to any combination that would accomplish this task.  In a perfect world this use of grub4dos won't change a single byte on the actual hard disk leaving no forensic loose ends!

 

From reading here I know that windows tends to find hidden partitions, but I am hoping that using grub4dos on a bootable usb, will allow me to hide them long enough to mount the hidden OS as positioned in my example above.  I don't think this method will mess with the partition table since all three partitions already exist on my drive and its working fine now.

 

I could really use some help here.  Thanks.
 

CDRWIN 10 (100% Discount) as of 6-30-15 Deal Expires in: 2 day(s) 20 hour(s)

$
0
0

CDRWIN 10 (100% Discount) Free

http://www.windowsdeal.com/w/cdrwin-10-discount-coupon-code/

 

 

 

CDRWIN 10 is concentrated and proven burning power for your CD-, DVD- and / or Blu-ray-writer with a new and modern interface, which offers the most important functions quickly and clearly arranged.

Equipped with a state-of-the-art technology, CDRWin 10 is providing those qualities, which already made the predecessors very successful: reliability, velocity, comprehensive functionality and a straightforwardness that directly leads to success.

Get now with CDRWIN 10 an ideal burning software package for starters and professionals. Now also compatible with Windows 8.

 

 

Features:
  • Direct copy of data-CDs/DVDs (incl. computer games) and audio-CDs
  • Burning and creation of ISO-, BIN- and XMD-images as well as Cue-Files
  • Authoring of Orange Book-compatible data-CDs (CD-ROM, CD-ROM/XA) as well as data-DVDs and Blu-ray discs. Also suitable for creation of MP3- and h.264/MPEG-4-CDs/ DVDs & Blu-ray discs
  • Automatic setting of the platform-overlapping ISO 9660-file system and the Windows Joliet file system for display of long file names and complex directory structures
  • Authoring of Red Book-compatible audio-CDs (CD-DA) in Disc-at-Once-mode with manually adjustable track breaks and CD-Text
  • Support of Disc at Once (very important, e.g. for standard-compliant creation of audio-CDs and when copying from CDs/DVDs), Track at Once (important in case data-CDs are to be extended retroactively) and Session at Once (CD-extra)
  • Ripping of audio-CDs in MP3/WMA or WAV. Supports the reading of CD-Text, freedb.org and the manual input of title information
  • UDF support for burning DVD structures
  • freedb-data can be edited and are stored locally in a cache
  • Fast or complete deletion of re-writable media
  • Caching system for optimization of system configuration and guarantee of safe burning procedure
  • Multi-Session support for data discs
  • Support of all known blank CD sizes from 21 to 99 minutes length, CD-R, CD-RW, DVD+R, DVD-R, DVD+RW, DVD-RW, DVD DL, DVD-RAM, BD-R and BD-RW. Overburning of CD-Rs is also possible.
  • Support of various techniques for buffer underrun protection, e.g. BurnProof
  • Audio- and data projects can be stored and loaded
  • Retroactive finalizing of CD/DVDs/Blu-ray discs possible
  • Future-proof: automatic support for new burners. More than 1000 burners tested successfully, among others Acer, ACTIMA, AOpen, APACHI, ARTEC, ASUS, BTC, Compaq, CenDyne (Verbatim), Creative Labs, Cyberdrive, CyQ’ve, Delta, DynaTec, Dysan, Freecom, Fujitsu Siemens, Goldstar, Grundig, Hewlett-Packard (HP), Hightech, Hi-Val, Imation, Iomega, JVC, Kodak, LaCie, LG, Lifetec, Lite-On, Media FORM, Medion, Memorex, Mem-Up, Micro Solutions, Microboards of America, MicroNet Technology, Mitsubishi, Mitsumi, Mustek, Nec, Olympus, Optima, OTI, Pacific Digital, Panasonic (Matsushita), Philips, Pinnacle, Pioneer, Plasmon, Plextor, Procom Technology, QPS, R-Quest, Ricoh, Samsung, Sanyo, Smart & Friendly, Sony, Taiyo Yuden, TDK, Teac, Terratec, Tevion; That’s write, Toshiba, Traxdata, Turtle Beach, Waitec, Wearnes, Yamaha and more
  • Supports ATAPI-, SCSI-, SATA-, Firewire- and USB-drives
  • Includes an ASPI driver for Windows
  • Incl. ATIP and ADIP-display
  • Incl. sector viewer of discs
  • Support for Drag & Drop

Integrate Java/Directx/Visual Basic to project

$
0
0

I'm trying to integrate Java, Directx and all of the visual basic redistributes to the WinPE project

I see that there is already integration for .NET framework so that is taken care of.

Is there a way to do this without installing it on a already live version of WinPE 8 and then capturing the changes?

What I want to do is, boot up WinPE and be able to run anything on the system with all those tools installed, and not 

get any (fatal :) error messages. For example if there is a system that is infected, I can pop in my winPE USB and be able to run the system and programs on it without any hassle. Instead of getting a side by side configuration is incorrect error. 

Hope I"m making sense

Thanks in advance

You rock!

 

 

How To Apply Multiple WIM Files With ImageX?

$
0
0

I've been having issues with my laptop recently, and have decided that it would be best to just reflash an unlocked BIOS, then restore from recovery discs. I made clones of my friend's recovery discs, they're pretty much unscratched so I'm sure they'll work. And we have identical model laptops. But I've been having trouble making a bootable OEM recovery USB from the ISOs, I already tried once and the USB failed to boot, just got stuck on a blinking cursor. Using Dell's AlienRespawn utility failed, it wouldn't install because I dont have a factory recovery partition present on my SSD/HDD. I cant install using the actual discs because I no longer have a disc drive. I noted that in a subfolder on each disc there are 2 WIM files, BASE.WIM and BASE2.WIM. I know how to apply a single WIM file with ImageX, as well as split WIMs (*.SWM), but not 2 WIMs. Can anyone tell me what the command syntax is for applying 2 WIMs?

 

Currently I've tried:

 

imagex /apply F:\preload\BASE.WIM /ref F:\preload\BASE2.WIM 1 J:

 

But I'm not sure if it's actually applying *BOTH* WIMs.

 

Thanks!

 

EDIT: BASE.WIM appears to contain what should be the contents of C:\, but BASE2.WIM is around 2.5GB and only contains a [2].xml file and a [Files] folder with a gazillion files within that that are essentially nothing but a bunch of files with numberss in their names. Surely the data must be important for restoring.

 

EDIT #2:

 

I get the message "Image successfully applied" when using the command listed above, so I still can't be sure whether the BASE2.WIM is also being applied.

Viewing all 6812 articles
Browse latest View live