93 replies to this topic

[Ten98]

I really love this solution, but it's very annoying to have to reboot from HDD whenever I make changes (install an app, save a spreasheet, etc)

 

Is there no way to write the .VHD to HDD once booted from it?

[iphoughton1979]

I really love this solution, but it's very annoying to have to reboot from HDD whenever I make changes (install an app, save a spreasheet, etc)
 
Is there no way to write the .VHD to HDD once booted from it?

I use Acronis to image the live system, then mount the .VHD file, then use Acronis again to write the image back to the mounted .VHD. I'm guessing you could script this to give a one click solution, but I haven't got round to it yet. Also for folders where data is going to change frequently, I would just put them onto a normal drive unless you need the amazing speed of the RAM disk.

[far.in.out]

uploaded new video, see first post

updated the guide on the website, now it's sort of interactive...

updated and cleaned up first post

[girotel]

Hello,

 

Great tutorial.

 

I have a question would it be possible instead of using the firadisk-driver-0.0.1.30 driver one could use the native windows Windows RAM Disk Device (VOLUME) driver or some other driver that is whql signed ?

 

Thank you.

Edited by girotel, 05 May 2013 - 09:37 AM.

[k2K2]

Damn Good Tutorial!!! Helped me a lot -> Thanks

[NonZenon]

Many many thanks @ far.in.out! Just got normal (not slimmed down) W7 x64 Ultimate installation to work, too bad I only made 10 Gig VHD in the first place). Without touching WinSxS and stuff, could free up 500 Meg off whole 10G, and I need it all for DAW, running audio apps from HDD - no way )) Just a small heads-up for those using full W7)

I think I'm gonna try W7 Embedded, BTW anybody try Tiny7 - It's a 700 M installer (fits in a CD)? 

[gbrao]

@far.in.out

I see posts here ( e.g. the one above by NonZenon ) mentioning booting W7 x64 from memory using VHDs more than 4GB in size. Would a 32 bit program work in such cases ? I faced problems.

See : http://reboot.pro/to...ed-from-memory/ .

[far.in.out]

I think this could only happen if your vhd is loaded into address space below 4GB. Try avoiding that and see what you get.

[gbrao]

^ I've been trying to find out how to do that. No luck so far.

http://reboot.pro/to...mory-above-4gb/

[epa]

heey farinfarout

tnx for this,it works great

i only had problems creating bcd using batfiles,so i used easybcd te create the grub entry ,and config manualy.

i have a 20gig of 32 for  ramdisk .

to bad i don't have ultimate license

[far.in.out]

Glad it worked out for you. You are welcome.

[epa]

i expand the vhd img a bit ,using diskpart ,but now it won't boot in ram?

after loading mem i get an error code 13 .

any ideers.

 

i can boot the vhd just fine,(and its bigger like it suppost to) .just not in ram?

Edited by epa, 01 November 2014 - 11:07 AM.

[epa]

i just did the whole thing over ,and created a 32 gig ramdisk.

so it only works wit ultimate and enterprice?

what about win 8.1 ?

[far.in.out]

google it, idk really...

[gbrao]

i just did the whole thing over ,and created a 32 gig ramdisk.
so it only works wit ultimate and enterprice?
what about win 8.1 ?

Do 32 bit programs work with the 32 GB vhd booted from memory ?
refer : http://reboot.pro/to...e-2#entry184215

I was able to boot Win 8.1 from memory using wimbs tool.
http://reboot.pro/to...ct-make-mini-8/

[farhan]

are you sure it will work

[epa]

Do 32 bit programs work with the 32 GB vhd booted from memory ?
refer : http://reboot.pro/to...e-2#entry184215

I was able to boot Win 8.1 from memory using wimbs tool.
http://reboot.pro/to...act-make-mini-8

from what i understand it should work with win 8.1 pro.

in time i wil give it a try,but for now i'm realy happy with 7.1 with ramdisk.

[vmk1007]

@far.in.out Great works, helped me a lot tks

but i have same

 

2. After booting in WES7 the system show that it installed RAM disk, and asks if I would like to restart system now, or later. Is there any solution to remove this pop-up window? Maybe to attach a grub4dos ram disk while native boot from VHD, so that WES7 could store information about new device, or anyhow disable this question in system?

 

and you explaned

 

Yes you can mount a small Ramdisk while booting from HDD and let system install that hardware, afterwards it shouldn't ask any questions.

I'm not clear that  how do detail

Can you help me, thks

[Nal1]

Hi all,

just one word : Wahoo !

I'm a french newbie, some questions :

- Does it work with Win 10 64B ? Same method ?

- Is it a good idea for gamers ? Install windows and some games on ramdisk will accelerate loading in games (maps, tracks, textures...) or not ?

Thanks

[Camiel]

- Does it work with Win 10 64B ? Same method ?

 

i'm trying hard for this myself too  but i am stuck upon all kinds of errors, especially boot\bcd related

if anyone comes up with any ideas, please share

[Uneitohr]

I've never used Windows Embedded. Is there any significant install size difference between Windows Embedded and a normal edition of Windows?

[Wonko the Sane]

I've never used Windows Embedded. Is there any significant install size difference between Windows Embedded and a normal edition of Windows?

I wonder what has your question to do with the topic.

 

Windows Embedded is however a "componentized" OS, you "assemble" it yourself adding to it the components you want/need in your final build, the more you add the more it will become similar to a "normal" edition of the correspondent Windows.

 

Imagine that instead of a pre-assembled Lego toy house you have just a set of Lego bricks, if you follow exactly the image on the box when assembling the pieces, at the end you will have exactly the same toy house.

 

Wonko

[Nal1]

i'm trying hard for this myself too  but i am stuck upon all kinds of errors, especially boot\bcd related

if anyone comes up with any ideas, please share

Hi, problem for me at 1"10,

this message appears :

Le type d’élément de données spécifié n’est pas reconnu ou ne s’applique pas à l’entrée spécifiée.

Exécutez « bcdedit /? » pour obtenir de l’aide sur la ligne de commande.

Élément introuvable.

Le type d’élément de données spécifié n’est pas reconnu ou ne s’applique pas à l’entrée spécifiée.

Exécutez « bcdedit /? » pour obtenir de l’aide sur la ligne de commande.

Élément introuvable.

Les données de liste d’entrée ne sont pas valides telles qu’elles sont spécifiées.

Exécutez « bcdedit /? » pour obtenir de l’aide sur la ligne de commande. Paramètre incorrect.

 

 

This message on 2 computers (W10 64b and Win7 64b), with the admin session.

With the user session, the message is : Acces refusé

I ve tried many manipulations, but no success.

Same error for you ?

[Wonko the Sane]

Nal1, please FORGET about the video and whatever happens at 1:10 inside it.

 

Download the documents containing the instructions:

http://reboot.pro/fi...ile/182-winram/

http://reboot.pro/fi...oad/182-winram/

Make sure you follow them EXACTLY.

Explain on which step do you get the error.

 

Wonko

[Camiel]

after much hair pulling i figured it out at last

it works just fine with win 10 x64 (14279)

i had to  [BCDBOOT C:\Windows /s G:] where C:\Windows is a live win10 system and G:  is the attached vhd

then followed the tutorial at [adding bootmgr and shrinking the vhd]

added the appropriate grub4dos entry and boot just fine

 

furthermore, and with the help of some windows installation customizing software and the amazing wimlib lzx compression

i managed to a tiny 2. 67gig (with drivers [nvidia] and net.framework included) full blown windows system running from ram.

 

thanks to this wonderful tutorial

misty wimboot tutorial

wimlib and others