Jump to content











Photo
- - - - -

VHD_W7_Compact - Make Mini 7 -

win7 vhd usb mini7

  • Please log in to reply
86 replies to this topic

#1 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 02 June 2013 - 04:33 PM

Posted Image

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

VHD_W7_Compact - Program to make Mini 7

Download and Run VHD_W7C.exe and Extract to simple path

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

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

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



Support topic - http://reboot.pro/to...ct-make-mini-7/

Download VHD_W7C - http://reboot.pro/fi...ct-make-mini-7/

More Info - http://www.911cd.net...showtopic=25357

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

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

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

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

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

VHD filename W732USP1.vhd contains Architecture 64/32 + Distribution Language + Version P/M/C + Number 1-9

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

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

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

Windows 7 Source VHD preparation

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

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

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

powercfg -h OFF


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

Open Command Prompt as Administrator:

bcdedit /set testsigning on


Reboot to activate testsigning - Info http://msdn.microsof...y/ff553484.aspx

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

Credits and Thanks to:
JFX for making WinNTSetup3 to Install Windows 2k/XP/2003/Vista/7/8 x86/x64 - http://www.msfn.org/...612-winntsetup-
ChrisR for making Win8.1SE - http://www.msfn.org/...170546-win81se/
chenall, tinybit and Bean for making Grub4dos - http://code.google.c.../downloads/list
karyonix for making FiraDisk driver- http://reboot.pro/to...k-latest-00130/
Sha0 for making WinVBlock driver - http://reboot.pro/to...8168-winvblock/
Olof Lagerkvist for ImDisk virtual disk driver - http://www.ltr-data....ode.html#ImDisk and http://reboot.pro/in...hp?showforum=59
Uwe Sieber for making ListUsbDrives - http://www.uwe-sieber.de/english.html
Dariusz Stanislawek for the DS File Ops Kit (DSFOK) - http://members.ozema...eezip/freeware/
cdob and maanu to Fix Win7 for booting from USB - http://reboot.pro/to...-windows-7-sp1/
marv for making UsbBootWatcher - https://github.com/v...sb-boot-watcher and http://www.911cd.net...showtopic=22473
Pauly for making Bootice - http://bbs.ipauly.co...06e07ab6f3b01cb
NeoSmart for making EasyBCD - https://neosmart.net/EasyBCD/
-
More Info on booting Win 7 VHD from grub4dos menu by using FiraDisk Or WinVBlock driver:
http://reboot.pro/to...-and-windows-7/ Or http://www.911cd.net...showtopic=23553
Boot Windows 7 from USB - http://reboot.pro/in...hp?showforum=77
Boot Windows 7 from USB - karyonix - http://reboot.pro/in...?showtopic=9196

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

Grub4dos Menu to Boot W732USP1.vhd as FILEDISK or as RAMDISK by using FiraDisk driver

VHD filename W732USP1.vhd contains Architecture 64/32 + Distribution Language + Version P/M/C + Number 1-9

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

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


Grub4dos Menu to Boot W732USP2.vhd as FILEDISK or as RAMDISK by using WinVBlock driver

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

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


Click here to download this file
  • ReTokener likes this

#2 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 02 June 2013 - 04:52 PM

VHD_W7_Compact.exe  - Portable 7 VHD  ====> Mini 7 VHD

 

VHD_W7C.png =========> VHD_W7-4.png ===> Mini7_VHD.png

 

:cheers:

 

Here is a Video on How to use VHD_W7_Compact.exe :)
 


#3 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 06 June 2013 - 09:02 AM

Install of Win7 x64 in VHD mounted as drive Z: where VHD file is located on internal harddisk and by using booting from USB-Stick drive I:

 

SetupW7x64-VHD.png

 

In this way you boot from USB and Install in VHD located on primary NTFS partition of internal harddisk.

USB-Stick can be FAT32 or NTFS and has only Boot files so that normal booting of internal harddisk does NOT change.

Having the VHD located on NTFS drive of internal harddisk gives highest speed for booting Win7 VHD from Boot Manager menu 

and also for loading Mini 7 VHD in RAMDISK by using FiraDisk driver and Grub4dos boot menu.

 

I think this is the most favourite configuration :)

 

:cheers:



#4 doveman

doveman

    Frequent Member

  • Advanced user
  • 414 posts
  • Location:Surrey
  •  
    United Kingdom

Posted 10 June 2013 - 09:53 PM

Hi

 

Following on from my post in the other thread, I created a new Full with v75 from here and then a new Portable (from the original source, not from the Full copy).

 

Strangely, the Full doesn't boot properly. It gets past the boot animation fairly quickly but then I'm left with a blank screen and a movable cursor. I left it for about 10mins and no change and it was the same on the next boot attempt as well.

 

However the Portable works fine and boots normally without any long delays, which I had before for some reason, so that's cool as I'm more interested in being able to use this than a Full copy anyway  :clap:

I did attempt to use the in-built defragger (I used NTFS compression for both builds) but unfortunately it doesn't seem to register as activity to Windows and it went to sleep at around 33%, so I had to scrap that build and make a new one in case it was corrupted. I defragged manually with defraggler by mounting the VHD afterwards from then on.

 

I left waitbt unticked and I think also USB Tweaks (as I don't intend to use this build from USB) on all builds.

 

I'll try making another Full build sometime. I'm sure it was just a weird glitch that resulted in my non-booting build ;)



#5 doveman

doveman

    Frequent Member

  • Advanced user
  • 414 posts
  • Location:Surrey
  •  
    United Kingdom

Posted 13 June 2013 - 04:34 AM

Having compared booting the (Portable) VHD from HDD and CF now, they both boot pretty much just as quickly. Where the slowdown comes in is once it's booted and starts installing drivers, due to the much slower write speeds of the CF, such that it becomes quite unresponsive and the Device Manager redraws quite slowly. This also accounts for the slow shutdown of about 10s with the HDD and 130s with the CF!

 

Once the drivers are installed though, it should be quite usable as a RDP station, particularly if I install the EWF filter but I wonder if there's any way to eliminate a lot of the writing at shutdown in order to make it a lot quicker when using the CF? I can't really imagine what it tends to write at shutdown but no doubt someone will know.



#6 doveman

doveman

    Frequent Member

  • Advanced user
  • 414 posts
  • Location:Surrey
  •  
    United Kingdom

Posted 19 June 2013 - 11:55 PM

Hmm, well my plans to use Portable Win7 as an RDP station on my Mum's PC aren't working out :(

 

I bought a s/h Nvidia FX5200 for £8 as her onboard graphics (i815 I think) didn't appear to have a WIn7 driver available. I also put a spare NIC card I had lying around in as the onboard didn't have a driver either. I managed to find a driver for the onboard sound.

 

So it's all working well enough, except the odd pause when doing certain things, like opening Control Panel and the long shutdown delay, which I might be able to eliminate by installing the EWF filter and there's between 100-200MB free RAM at most times (I'm booting from CF Card so enabled the swapfile on the HDD to avoid running out of RAM and crashing) but when I RDP to the Win7 machine in the next room, it's unusably laggy and unresponsive half the time.

 

Using my Portable XP (updated with drivers for the new hardware) and the RDP works fine there. I expected RDP to work better if anything using Win7, considering all the improvements and patches that have been added.

 

Even more sad, the FX5200 has not improved the ability of the machine to play online video one bit, with even 360p clips in a small window dropping half the frames and running at something like 11fps. It seems it's unable to use the card to hardware accelerate the decoding, as with that enabled it still shows software decoding in the info box, so I guess it's having to still use the CPU (P3 833Mhz I think) to play the video and obviously that's not up to the job. It actually worked better over RDP, as I guess then the server is doing a lot of the work and it starts off at 25fps but after about 10-15s this drops down to about 16fps and it gets stuttery (both audio and video), so either the server can serve the data quick enough or the client can't cope with the incoming data (it's nowhere near saturating the 100Mbps link though, under 25% I think).

 

It's strange as I gave my brother an identical PC, except it's got a P3 933Mhz and a FX5600 and he's able to play online videos as far as I know (I'm sure he'd have complained to me if he couldn't!)

 

I was using Thinstation originally but moved to Portable XP for better video playback (either over RDP or locally) and it does at least tend to play audio OK, which Thinstation didn't but apparently when using RDP it keeps freezing up (which Thinstation never did), hence why I decided to try Portable WIn7 in the hope it might be more stable. Locally it does seem to be somewhat snappier but if the RDP doesn't work it's no use :(



#7 Zoso

Zoso

    Silver Member

  • Advanced user
  • 612 posts
  •  
    Isle of Man

Posted 28 June 2013 - 02:57 PM

moved quoted from: http://reboot.pro/to...ll-xp-from-usb/

/> />/>/>/>can I make w7 pro VLK booting from VHD or must it be ultimate or enterprise editions?

also what virtual machine software can boot .VHD? I am only familiar with VMware which uses .vdmk and Qemu which uses .raw and I want to boot the .vhd created with your tool in a VM also.


#8 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 28 June 2013 - 05:44 PM

Win7 Professional can be used as Source, but you have to Install to NTFS primary partition instead of using VHD.

Only Ultimate and Enterprise Edition can be Installed direct to VHD by using WinNTSetup2.

 

After Install of Win7 then this Source can be used by VHD_W7_Compact to make New VHD of reduced size.

 

I have no experience with Virtual Machines.

 

Possible scenario's for VHD_W7_Compact.exe

- Target Boot Drive can be FAT32 or NTFS USB-drive used only for Boot files so that there are no changes for booting of internal harrddisk .
- Target System Drive must be NTFS and is the drive where the Win7 VHD file is created and this can be your internal harddisk drive.

 

:cheers:



#9 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 28 June 2013 - 09:22 PM

Microsoft VirtualPC uses *.vhd files. :cheers:
  • wimb likes this

#10 Zoso

Zoso

    Silver Member

  • Advanced user
  • 612 posts
  •  
    Isle of Man

Posted 13 July 2013 - 01:07 AM

hi Wimb, 1st boot after compact in new 2gb vhd I get error "RunDLL There was a problem starting C:\Windows\ehome\ehssetup.dll The specified module could not be found."

OS is x86 Enterprise edition. how can I correct this error? also, activation status now says "Not Available"?



And how do I utilize this:

"VHD_W7C_drivers.exe - Plugin with drivers for VHD_W7C to make Universal Portable 7 VHD

Run and Extract results in folder VHD_W7C\makebt\drivers\WIN7_x86 with extra Win7 drivers

Intel USB 3.0 + Ivy Bridge + Realtek RTL8192C WLAN
NVIDIA HDMI Audio + IASTOR + Realtek PCIe GBE Family Controller and more .....

More Info http://reboot.pro/to...to-make-mini-7/"


links to here but I dont see more info here?

Thanks Wimb

edit: RunDLL error does not reoccur after reboot.

#11 Zoso

Zoso

    Silver Member

  • Advanced user
  • 612 posts
  •  
    Isle of Man

Posted 17 July 2013 - 02:44 PM

hi Wimb, now I use 7 Ultimate as source with WinNTSetup_x86.

after I run VHD_W7_Compact Event Viewer no longer works, gives error "MMC could not create the snap-in"

is this expected or is something wrong? If it is expected then how can I make event viewer working again?

the other snap-ins device manager and services are working and the eventviewer .exe, .mmc, & .dll are present.


and I still dont understand how VHD_W7C_drivers.exe works.
thanks

#12 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 18 July 2013 - 03:59 AM

Did you Uncheck the NetFrame Checkbox ?

Some MMC snap-ins require NetFrame, so you should keep it checked.

 

 

Add Drivers from makebt\drivers to system32\DriverStore\FileRepository is applied for Portable version by using Dism.exe

Run first VHD_W7C_drivers.exe plugin to add useful extra drivers to makebt\drivers folder.
Download VHD_W7C_drivers from http://reboot.pro/fi...versexe-plugin/
 

 

Windows 7 has a lot of drivers build-in, but more recent hardware like Intel i5 Ivy bridge processor and Intel USB 3.0 require extra drivers.

Dism can add such extra drivers when they are supplied in makebt\drivers\WIN7_x86 folder.

 

See what the VHD_W7C_drivers.exe selfextractor is doing and you will understand ..... :unsure:

 

:cheers:



#13 Zoso

Zoso

    Silver Member

  • Advanced user
  • 612 posts
  •  
    Isle of Man

Posted 18 July 2013 - 07:34 PM

I did not check .net4 so I retry and check it. now with it checked I get errors: "FileCopy Error - Overflow" and then "OVERFLOW - Not enough Space in VHD Drive"

so I try larger size setting 3.5gb and same errors, the next size offered in your program to try is larger than my source VHD.

also, when defrag is checked it stops with pop-up "Defrag Ready - Inspect VHD Drive" says to inspect and modify as needed including "Wipe Free Space using CCLeaner Tools"

how important is this "CCleaner Tools", I dont have it so I skipped that and clicked OK and it consinues progress untill I get the not enough space error.

#14 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 19 July 2013 - 06:31 AM

I did not check .net4 so I retry and check it. now with it checked I get errors: "FileCopy Error - Overflow" and then "OVERFLOW - Not enough Space in VHD Drive"

so I try larger size setting 3.5gb and same errors, the next size offered in your program to try is larger than my source VHD.

also, when defrag is checked it stops with pop-up "Defrag Ready - Inspect VHD Drive" says to inspect and modify as needed including "Wipe Free Space using CCLeaner Tools"

how important is this "CCleaner Tools", I dont have it so I skipped that and clicked OK and it consinues progress untill I get the not enough space error.

 

The FileCopy Error occurs when both NetFrame and 4 are checked, but that is not due to OVERFLOW so larger VHD size will not help.

Thanks for reporting this error for FileCopy of assembly\pubpol4.dat . I will try to find solution.

 

I meant to have NetFrame checked and 4 Unchecked which is the default case.

The NetFrame will be needed for some MMC snap-ins.

 

The Defrag Ready pop-up is normal and serves to offer the user Manual inspection / modifycation of the created VHD.

CCleaner is useful to wipe FreeSpace. In that case gzip file will load faster into RAMDISK.

In general you don't need to do anything at the Defrag Ready pop-up and can simply press OK.



#15 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 343 posts
  •  
    India

Posted 19 July 2013 - 07:09 AM

read only flag as i had reported earlier.

 

edit : here http://reboot.pro/to...ndpost&p=159871

 

The FileCopy Error occurs when both NetFrame and 4 are checked, but that is not due to OVERFLOW so larger VHD size will not help.

Thanks for reporting this error for FileCopy of assembly\pubpol4.dat . I will try to find solution.

 

 



#16 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 19 July 2013 - 08:13 AM

read only flag as i had reported earlier.

 

edit : here http://reboot.pro/to...ndpost&p=159871

 

Thanks :)

Indeed I must try to remove read only flag in case of FileCopy error.

That will solve such problems.

 

:cheers:



#17 Zoso

Zoso

    Silver Member

  • Advanced user
  • 612 posts
  •  
    Isle of Man

Posted 19 July 2013 - 05:31 PM

Ive been searching for solutions to slim down W7 and only find this program for post installs. just need event viewer and easyBCD working and .net4 is required for easyBCD.

how can I transfer w7 installed in original .vhd by winntsetup to direct booting from USB HDD? one of your tools?

also I think you should put readme txt with function and instruction in root of extracted directory in your tools.

also I extract some tools you have only to find it was already included in another tool. I think you really should combine all tools in one. this will lessen confusions some.

#18 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 20 July 2013 - 04:25 AM

Program UEFI_MULTI can be used in Win 7/8/7PE OS to make other HDD or USB drives bootable with the created Win 7 VHD.

http://reboot.pro/to...182-uefi-multi/ Or http://www.911cd.net...showtopic=25269
 

 

event viewer and the supplied EasyBCD in folder IMG_XP\makebt are working for me and require NetFrame but NOT.Net 4

 

Using Default Settings in VHD_W7_Compact.exe is working OK.

 

IMG_XP is All in One package of 27 MB, but it is also convenient to have small packages like VHD_XPC and VHD_W7C 

The small packages of about 4 MB can be downloaded from reboot.pro and are dedicated to specific task of e.g. Install XP in VHD or making Mini XP or Mini 7

 

It is often preferred  to keep the download small and NOT to mix everything which might give confusion ....

 

 

:cheers:

 

EasyEvent2.png == reboot-downloads.png



#19 Zoso

Zoso

    Silver Member

  • Advanced user
  • 612 posts
  •  
    Isle of Man

Posted 20 July 2013 - 06:03 AM

default settings... I did not use them because the tweaks are grouped together, should be separated with own check boxes for each, maybe put them on a pop-up screen like winntsetup does? just suggesting. and more info like what is "Add Drivers using DISM" do? to be honest.. What does Everything do? (no need to answer here but somewhere at some point would help)

the UEFI_MULTI tool to tranfer direct to USB HDD, OK

I dont need .vhd booting right now, only compact w7 but if I can reconvert the vhd to RHD (Real Hard Disk) I can still use your tools for that (no other options for post sliming w7 otherwise at this point) probably could use your tools for alot more but figuring them out (how to use, what they do, etc.) is very very difficult.

#20 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 20 July 2013 - 06:18 AM

First use Default Settings (they are mostly required) and only make changes when you know what you are doing ....

 

Each Checkbox has Tool Tip (move your mouse) e.g.

 

Add Drivers from makebt\drivers by using Dism.exe
Dism will Add Drivers to DriverStore\FileRepository

 

 



#21 Zoso

Zoso

    Silver Member

  • Advanced user
  • 612 posts
  •  
    Isle of Man

Posted 20 July 2013 - 06:29 AM

" and only make changes when you know what you are doing ...."

thats what I am trying to learn "what you are doing" so I can know what "I" am doing.


I have noticed the mouse over pops (could stay up a little longer on some of them) but "Dism will Add Drivers to DriverStore\FileRepository" is not enough info. what drivers does it add?

I look in each folder and read each registry bat and try each .exe separately so I can get an idea what is going on but I would rather read documentation about it.

anyway, your tools are as impressive as they are confusing LOL, keep up the good work!

#22 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 20 July 2013 - 06:49 AM

Dism can add such extra drivers when they are supplied in makebt\drivers\WIN7_x86 folder.

 

See what the VHD_W7C_drivers.exe selfextractor is doing and you will understand .....

 

 

The reg files given in VHD_W7C\makebt\registry_tweaks can be studied by using an Editor like Notepad (use right-click to Edit)

In that case it is just readable text and some explanations are given there as well as in the IMG_XP Tutorial.



#23 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 343 posts
  •  
    India

Posted 20 July 2013 - 08:28 AM

Hi,

I created a VHD with VHD_W7_Compact.exe and just copied the files from vhd to a hdd partition. You may need to add bootmgr & boot folder.

It works. Very well in fact. I use it on a old P4 DDR1 PC. If booting from HDD, I would advise you to use portable instead of compact. If you are booting from HDD on one system only, afaik you need not use any of the tweaks - that's what I do. I also re-copy the entire .NET folders (from the full W7 install), they seem to exist in 3 places. On a HDD space is not much of a problem.

 

Be careful, wimb's tools are very addictive. These days I cannot bear to boot from HDD ( after experiencing boot from memory ). ;-)

 

EDIT : I use a SATA HDD not a USB HD.

 

I dont need .vhd booting right now, only compact w7 but if I can reconvert the vhd to RHD (Real Hard Disk) I can still use your tools for that (no other options for post sliming w7 otherwise at this point) probably could use your tools for alot more but figuring them out (how to use, what they do, etc.) is very very difficult.



#24 GBossN4eVr

GBossN4eVr

    Newbie

  • Members
  • 14 posts
  •  
    United States

Posted 23 July 2013 - 11:32 PM

Hi I am a new member and first of all I have to say thanks for these wonderful and very handy programs and methods/tutorials that you have shared with the world endless Thanks.  I have found these most useful since I can create, customize and store VHD's for varying tasks and never have to go through installing and customizing each time I want to do a fresh install.  I have a VHD portable to be exact which I recently made I have been reading about the different programs to integrate drivers and such but I don't really quite understand that much. 

 

I was trying to use a program on my already customized Portable VHD (i.e drivers for my hardware, programs and settings as I want) but when I run the program (SimpleTv Player the installed or portable version) I get :

"Microsoft Visual C++ Runtime Library
Runtime Error!
This application has requested the Runtime to terminate it in an unusual way.
Please contact the applications support team for more information."

 

I have been googling searching for methods to troubleshoot this error but when I install "Microsoft Visual C++ 2005 Redistributable 5.8.0.59183" (vcredist_x64/x86) they don't seem to install or work and doesn't show up in programs installed as it does in the Full Copy VHD.  I mentioned this specific version (I also tried the newer ones) because when I look in my Full Copy VHD I see it is the only MVC++ installed and the program works flawlessly.

 

My question is if there is a proven fix or what can I do before making the Portable VHD so that I wouldn't get this error or if you or anyone here knows how to extract and transfer the said program from either the Full Copy VHD or the Windows 7 Ultimate x86x64 iso to the Portable VHD if it is possible?

 

Thank You!   [Sorry about the long post btw]



#25 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 24 July 2013 - 03:14 AM

My question is if there is a proven fix or what can I do before making the Portable VHD so that I wouldn't get this error or if you or anyone here knows how to extract and transfer the said program from either the Full Copy VHD or the Windows 7 Ultimate x86x64 iso to the Portable VHD if it is possible?

 

 

First get everything working in your fresh full Win7 VHD and then use that VHD as Source to make Portable Win7- VHD

I don't remember the details about vcredist 2005 but there was something special which makes it needed to have it installed already in the source VHD

 

Hope this helps :)

 

The same fix as used for making Portable Win8 might help

 

http://reboot.pro/to...-38#entry171238

 

You can Install VC++ 2005 and 2008 in Windows 7 Source VHD before using VHD_W7_Compact.exe
 
Some adjustments in VHD_W7\copy_7vhd.txt and mini_7vhd.txt are needed to get all related files
 
Instead of 

\Windows\winsxs\manifests\*_microsoft.vc80.crt*
\Windows\winsxs\manifests\*_microsoft.vc90.crt*
 
\Windows\winsxs\Manifests\x86_policy.8.0.microsoft.vc80.crt_*.manifest
\Windows\winsxs\Manifests\x86_policy.9.0.microsoft.vc90.crt_*.manifest
 
\Windows\winsxs\*_microsoft.vc80.crt*\*.*
\Windows\winsxs\*_microsoft.vc90.crt*\*.*
 

 

 

 
Use 

\Windows\winsxs\manifests\*_microsoft.vc80.*
\Windows\winsxs\manifests\*_microsoft.vc90.*
 
\Windows\winsxs\manifests\*_policy.*
 
\Windows\winsxs\*_microsoft.vc80.*\*.*
\Windows\winsxs\*_microsoft.vc90.*\*.*
 

 

 

Then use VHD_W7_Compact.exe and see if that is sufficient for you.
 
That fix is certainly needed and will appear in next version.
 
:cheers:






Also tagged with one or more of these keywords: win7, vhd, usb, mini7

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users