Problems with Firadisk
#1
Posted 20 October 2009 - 09:58 AM
these are the drives present on my pc :
(hd0,0) --> Windows Vista (C:)
(hd1,0) --> Windows FLP (F:)
(hd2,0) --> Windows 7 lite USB (G:)
(hd0,2) --> Debian Lenny (N:)
(hd3,0) --> Virtual RAM disk (R:)
I'm trying to load Windows 7 into RAM (I have 4 GB of RAM). This is what I did :
1) installed the firadisk driver on (hd0,0)
2) downloaded these files :
http://public.winbui.../hddimage05.zip
and
modified the hddimage.cmd script,like this :
rem IF %FREEBYTENUM% leq %Filesize% GOTO :NO-SPACE
Because if I don't do it,I can create 1 GB disk image only.
3) created the empty virtual image of 3 GB named 7.img using the hddimage.cmd script
4) created virtual RAM drive (R:) mounting 7.img :
imdisk.exe -a -f F:\7.img -m R: -b 32256
5) created file exlude.txt and copied to c:\
:\Users
:\Documents and Settings
:\ProgramData
:\RECYCLER
:\$Recycle.Bin
:\bootstat.dat
:\hiberfil.sys
:\pagefile.sys
:\PerfLogs
:\System Volume Information
\Temp\
\Temporary Internet Files\
6) copied by hand to (R:) the following folders :
:\Users
:\Documents and Settings
:\ProgramData
7) copied files from disk USB (G:) to drive (R:) :
xcopy G:\ R:\ /exclude:C:\exclude.txt /e /c /i /h /k /x /y
8) created the virtual image of the (R:) drive and named 77.img
9) devcon install firadisk.inf root\firadisk
10) started REGEDT32
11) highlighted the HKEY_LOCAL_MACHINE key
12) File / Load Hive
13) opened file R:\windows\system32\config\system
14) named the new key test1
15) reg delete HKLM\test1\MountedDevices /f
16) reg unload HKLM\test1
17) copied file grldr.mbr to to c:\
18) bcdedit /store \boot\bcd /create /d "Start GRUB4DOS" /application bootsector
{df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5} has been created correctly.
19) BCDEDIT.EXE /store \boot\bcd /set {df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5} device boot
20) BCDEDIT.EXE /store \boot\bcd /set {df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5} path \grldr.mbr
21) BCDEDIT.EXE /store \boot\bcd /displayorder {df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5} /addlast
22) edited file menu.lst
title Boot Windows 7 from RAMDisk
find --set-root /77.img
map -mem /77.img (hd0)
map --hook
root (hd0,0)
chainloader /ntlr
when I restart my pc,I see that GRUB4DOS has been installed. It says : try (hd0,0) on NTFS5. I press enter,but nothing happens. Can you help me ? Thanks.
#2
Posted 20 October 2009 - 10:28 AM
chainloader /ntlr
There is no ntldr since ntldr is the loader of XP. You need bootmgr like
chainloader /bootmgr
Loading 3GB RAMBOOT Image will take longer, about 3 min from HDD
At flashing cursor just wait.
Is your image named 7.img as stated previously or 77.img ?
#3
Posted 20 October 2009 - 11:24 AM
this is menu.lst :
title Boot Windows 7 from RAMDisk
find --set-root /77.img
map -mem /77.img (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr
and this is boot.ini
[operating systems]
C:\grldr="grub4dos"
7.img was the empty image file,77 is the Windows 7 image file and it is placed on (hd1,0).
#4
Posted 20 October 2009 - 11:41 AM
I edited the menu.lst like you said and waited 1 hour,but nothing happened.
this is menu.lst :
title Boot Windows 7 from RAMDisk
find --set-root /77.img
map -mem /77.img (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr
and this is boot.ini
[operating systems]
C:\grldr="grub4dos"
7.img was the empty image file,77 is the Windows 7 image file and it is placed on (hd1,0).
if the img file is at hd1,0 then why are you using root (hd0,0) ?
eliminate this line and just go through command line one by one ? after map -- mem . hook it . and chainloader the bootmgr
#5
Posted 20 October 2009 - 11:59 AM
Because he mapped it as (hd0).if the img file is at hd1,0 then why are you using root (hd0,0) ?
@Marietto2009
I have not tried booting Windows 7 in RAM.
You might have to change BCD entry to point to partition inside image.
#6
Posted 20 October 2009 - 12:12 PM
Because he mapped it as (hd0).
oops my bad.
#7
Posted 20 October 2009 - 12:21 PM
can you explain what should I do ? 10x.
these are my bcd entries :
Windows Boot Manager
--------------------
identificatore {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {293c4ff5-ad3e-11dd-9a8c-f6ff9a89ae66}
displayorder {current}
{df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5}
toolsdisplayorder {memdiag}
timeout 12
resume No
Caricatore di avvio di Windows
-------------------
identificatore {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
osdevice partition=C:
systemroot \Windows
resumeobject {b65bed93-a774-11de-8517-806e6f6e6963}
Settore di avvio in modalità reale
---------------------
identificatore {df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5}
device boot
path \grldr.mbr
description Start GRUB4DOS
#8
Posted 20 October 2009 - 02:39 PM
Please try.
bcdedit /store r:\boot\bcd /set {bootmgr} device boot
bcdedit /store r:\boot\bcd /set {default} device boot
bcdedit /store r:\boot\bcd /set {default} osdevice boot
How do you reduce Windows 7 size to just 3GB ?
#9
Posted 20 October 2009 - 07:46 PM
Good question - I've not found any way of getting close to this.@Marietto2009
How do you reduce Windows 7 size to just 3GB ?
@Marietto2009
I'm confused by your system setup. Why manually copy the files (in step 6) when you can edit exclude.txt and use the following entries instead.
:\RECYCLER :\$Recycle.Bin :\bootstat.dat :\hiberfil.sys :\pagefile.sys :\PerfLogs :\System Volume Information \Temp\ \Temporary Internet Files\
You mention that the RAM disk files are copied from Windows 7 lite USB - what is this.
In step 9 devcon is used to install firadisk - firadisk should have been installed in the operating system you copied - before copying it to the disk image. BTW - does devcon work in Windows 7?
You appear to have added a grub4dos entry to boot.ini and a BCD store - which one are you booting.
You mentioned having copied grldr.mbr to drive C: - did you also copy grldr to any of your drives.
If grub4dos has been installed correctly then you should be able to use the command line by pressing C. Try entering your commands from the command line (check link to grub4dos guide in my signature if you are unsure how to use the command line).
If you want to test this I'd suggest temporarily removing some of your hard disks as your setup is confusing even by my standards.
diddy
#10
Posted 20 October 2009 - 07:49 PM
try (hd0,0) : ntfs5 : _
no keys are working,only ctrl + alt + canc keys works.
Windows = 2.295.680.429
Users = 87.695.361
ProgramData = 28.399.302
Program Files = 92.956.101
Boot = 2.545.388
bootmgr = 562.944
grldr
autoexec.bat
config.sys
BOOTSECT.BAK
Total = 2.682.662.912 byte
A good idea can be cutting 295.680.429 byte to Windows folder,so it can go entirely inside 2 GB or RAM. Other folders can be kept on the hard disk. In this way there will be more free memory to run applications. My question is : what happens if only the Windows folder goes inside RAM and the other folders are kept outside ?
#11
Posted 20 October 2009 - 08:15 PM
2) the first thing I did has been to install Windows 7 on the Sata disk. After this,I cloned it on the USB disk,following the Karyonix tutorial.
3) I copied manually \Users,\Documents and Settings and \ProgramData from
the USB disk (G:) to the RAM drive (R:) because this command :
xcopy G:\ R:\ /exclude:C:\exclude.txt /e /c /i /h /k /x /y
took them from the main drive (C:) , not from (G:)
4) When I ran this command :
devcon install firadisk.inf root\firadisk
I did it on the main drive (C:)
5) I think that the grub4dos entry has been added automatically to boot.ini when I wrote these commands :
a) bcdedit /store \boot\bcd /create /d "Start GRUB4DOS" /application bootsector
b) BCDEDIT.EXE /store \boot\bcd /set {df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5} device boot
c) BCDEDIT.EXE /store \boot\bcd /set {df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5} path \grldr.mbr
d) BCDEDIT.EXE /store \boot\bcd /displayorder {df0b0a3a-bcf3-11de-8ab1-dfb27ed173d5} /addlast
#12
Posted 20 October 2009 - 08:37 PM
No offence - I wouldn't trust a torrent download for testing purposes as you have no idea what might have been added or removed.1) I found a very good version of Windows 7 lite from the torrent websites.
Fair enough - this shouldn't be the case however strange things can happen in windows3) I copied manually \Users,\Documents and Settings and \ProgramData from...
The firadisk driver must be installed on the operating system you plan to copy to the disk image (in your case the Windows 7 lite install)- it's no use running this command on a windows installation you are not copying to the RAM disk.4) When I ran this command...
It shouldn't have been.5) I think that the grub4dos entry has been added automatically to boot.ini when I wrote these commands...
No offence but if I was you I'd test booting a full XP or 2003 first as these systems are known to work. Once you have spent the time learning the steps involved then try imaging your Windows 7 install. I'm not even sure that you have managed to boot Grub4dos yet and this step must be completed first.
diddy
#13
Posted 20 October 2009 - 09:49 PM
EDIT by jaclaz
Torrent downloads are WAREZ.
We won't talk about them on this Board.
Check attentively Rule #1:
http://www.boot-land...?act=boardrules
#14
Posted 21 October 2009 - 08:47 AM
This is the boot structure of my pc
(hd0,0) --> Windows Vista (C:)
(hd0,1) --> Debian Lenny Swap Partition
(hd0,2) --> Debian Lenny (N:)
(hd1,0) --> Windows FLP (F:)
(hd1,1) --> unpartitioned space
-> Windows Vista can boot because grub is installed on (hd0)
-> (hd 1) can boot even if (hd 0) is not attached
1) removed old GRUB4DOS entries with easybcd (and checked if it has been removed succesfully)
2) deleted boot.ini,menu.lst,grldr.mbr from (hd0,0)
3) copied grldr.mbr to (hd0,0)
4) installed again GRUB4DOS
a) BCDEDIT.EXE /store \boot\BCD /create /d "Start GRUB4DOS" /application bootsector
entry {372f8faa-be19-11de-9926-cca05a9773d0} has been created succesfully.
b) BCDEDIT.EXE /store \boot\BCD /set {372f8faa-be19-11de-9926-cca05a9773d0} device boot
c) BCDEDIT.EXE /store \boot\BCD /set {372f8faa-be19-11de-9926-cca05a9773d0} path \grldr.mbr
d) BCDEDIT.EXE /store \boot\BCD /displayorder {372f8faa-be19-11de-9926-cca05a9773d0} /addlast
grdr is already present on (hd0,0)
and now this is the situation :
C:\Users\marietto>bcdedit
Windows Boot Manager
--------------------
identificatore {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {293c4ff5-ad3e-11dd-9a8c-f6ff9a89ae66}
displayorder {current}
{372f8faa-be19-11de-9926-cca05a9773d0}
toolsdisplayorder {memdiag}
timeout 12
resume No
Caricatore di avvio di Windows
-------------------
identificatore {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
osdevice partition=C:
systemroot \Windows
resumeobject {b65bed93-a774-11de-8517-806e6f6e6963}
Settore di avvio in modalità reale
---------------------
identificatore {372f8faa-be19-11de-9926-cca05a9773d0}
device boot
path \grldr.mbr
description Start GRUB4DOS
5) created menu.lst on (hd0,0)
title Boot Windows 7 from RAMDisk
find --set-root /S1.img
map --mem /S1.img (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr
S1.img is located on (hd1,0)
When my pc restarts I see 2 booting stages. On the first I can choose between Debian and Vista and on the second one between Vista and "Start GRUB4DOS". When I choose the last option,it happens the same thing as before,I see : try (hd0,0): ntfs5 : _ and no key works.
#15
Posted 24 October 2009 - 06:49 AM
NO SUPPORT WHATEVER is GIVEN for WAREZ. on this Board.
jaclaz
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users