Jump to content











Photo
* * * * * 7 votes

FiraDisk (latest = 0.0.1.30)


  • Please log in to reply
624 replies to this topic

#126 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 27 September 2009 - 05:56 PM

http://www.911cd.net...showtopic=17504 :whistling:

;)

jaclaz

#127 diddy

diddy

    Member

  • Tutorial Writer
  • 78 posts

Posted 27 September 2009 - 06:10 PM

http://www.911cd.net...showtopic=17504 :whistling:

Thanks Jaclaz - will try this out later. ;)

diddy

#128 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2862 posts
  • Location:Nantes - France
  •  
    France

Posted 27 September 2009 - 07:52 PM

Hello There,
About disk signature, is not is easier to simply delete the dosdevice\c: registry key?
This way, next time windows boots, it has to redetect it?

Regards,
Erwan

#129 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 29 September 2009 - 02:34 PM

Does Windows always re-detect it correctly if there are many disks and many partitions ?

#130 diddy

diddy

    Member

  • Tutorial Writer
  • 78 posts

Posted 29 September 2009 - 03:43 PM

Does Windows always re-detect it correctly if there are many disks and many partitions ?

In my experience if the MountedDevices entry for the C: drive is deleted the booted systemdrive will be mounted as C:

diddy

#131 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 29 September 2009 - 04:50 PM

In my experience if the MountedDevices entry for the C: drive is deleted the booted systemdrive will be mounted as C:

diddy


Actually, it should depend on the hd passed on by the BIOS, it is possible that by exchanging drives in grub4dos one can suceed in assigning a different order, but probably it is not a dependable way.

As said before, exchanging drive letters should be the easiest, with less possibilities of making mistakes, but I guess that one could put together a small batch to create a a .inf or .reg file taking the info from the MBR, but how would one "load" this info in the Registry? ;)

@karyonix
Unless there is a duplicate drive (i.e. two drives with same signature) windows should detect everything properly.

Data is detailed here, if there is a way to load a mkmigrate.inf file when booting, we also have the batch to get the .inf from a running system:
http://www.911cd.net...showtopic=19663
or one could adapt easily part of the MBRBATCH.

:whistling:

jaclaz

#132 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 30 September 2009 - 02:03 AM

This batch file adjusts SYSTEM\MountedDevices \DosDevices\(systemdrive) of offline Windows
It can be used with target Windows that is in real disk or in disk image mounted with FiraDisk 0.0.1.12.
adjsysmd.bat
[codebox]@echo offif not "%~1"=="" if exist "%~1\system32\config" goto :beginecho Adjust target SYSTEM\MountedDevices \DosDevices\(systemdrive) valueecho Usage:echo %~nx0 target_windows_directoryecho.echo Example: %~nx0 T:\Windowsgoto :eof:beginsetlocalset targetdir=%~f1%set targetdrive=%~d1%set signature=for /f "skip=2 tokens=1,2,*" %%I in ('reg query HKLM\SYSTEM\MountedDevices /v \DosDevices\%targetdrive%') do set signature=%%Kif .%signature%==. ( echo Target drive signature and offset not found goto :end)echo Target drive signature and partition offset = %signature%reg load HKLM\TargetSoftware "%targetdir%\system32\config\software"for /f "skip=2 tokens=1,2,*" %%I in ('reg query "HKLM\TargetSoftware\Microsoft\Windows NT\CurrentVersion" /v SystemRoot') do set targetsystemroot=%%Kreg unload HKLM\TargetSoftwareset targetsystemdrive=%targetsystemroot:~0,2%if "%targetsystemdrive%"=="" ( echo Cannot determine target system drive letter goto :end)echo Target system drive = %targetsystemdrive%reg load HKLM\TargetSystem "%targetdir%\system32\config\system"reg add HKLM\TargetSystem\MountedDevices /v \DosDevices\%targetsystemdrive% /t REG_BINARY /d %signature% /freg query HKLM\TargetSystem\MountedDevices /v \DosDevices\%targetsystemdrive%reg unload HKLM\TargetSystemgoto :end:endendlocal[/codebox]1. Mount image with firadisk 0.0.1.12 (in Windows in real disk)1.1 In key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk, create value StartOptions type REG_SZ data "disk,vmem=[i]image-file-path[/i]"[code]reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "disk,vmem=H:\image1.img"[/code]1.2 Disable and re-enable FiraDisk Virtual Disk Enumerator device in Device Manager or devcon.[code]devcon disable root\firadiskdevcon enable root\firadisk[/code]1.3 Delete value StartOptions from key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FiraDisk
reg delete HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions
2. Run adjsysmd.bat target-windows-directory
adjsysmd.bat T:\Windows
3. Unmount image
3.1 Disable FiraDisk Virtual Disk Enumerator device in Device Manager or devcon.
devcon disable root\firadisk


#133 fxscrpt

fxscrpt

    Frequent Member

  • .script developer
  • 328 posts
  •  
    Germany

Posted 02 October 2009 - 09:33 AM

Hi karyonix,
first of all thanks for your wonderful work.

I tried to use firadisk on WinXp x64 SP2 as conventional ramdisk
(no grub, no boot.ini option)

What i did is:

installed firadisk
added HKLM\System\CurrentControlSet\Control\FiraDisk\StartOptions = "disk,vmem,size=16450560"
disabled 'FiraDisk Virtual Disk Enumerator' device
reenabled 'FiraDisk Virtual Disk Enumerator' device

> BSOD 0x00000023

what's wrong? Thank you.

:D
Peter

#134 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 02 October 2009 - 11:08 AM

@Peter (fxscrpt)
Probably bug in FiraDisk.
I will look into it when I have time. Please wait for next version.

#135 fxscrpt

fxscrpt

    Frequent Member

  • .script developer
  • 328 posts
  •  
    Germany

Posted 02 October 2009 - 06:09 PM

@Peter (fxscrpt)
Probably bug in FiraDisk.
I will look into it when I have time. Please wait for next version.

Thanks karyonix!

#136 bardlet

bardlet
  • Members
  • 3 posts
  •  
    China

Posted 04 October 2009 - 01:24 AM

i tried to boot from a 800 Mb image (Windows XP Professional x64 Edition)
it works!
actually,firadisk v0.0.1.12 can run in Windows XP 64-bit

#137 Icecube

Icecube

    Gold Member

  • Team Reboot
  • 1063 posts
  •  
    Belgium

Posted 06 October 2009 - 07:04 PM

@ karyonix
A new GRUB4DOS is out: 2009-10-06
http://nufans.net/grub4dos/

2009-10-06 Turned off int13/AX=4B01/DL=7F cdrom query which may hang on some machines. Commented out DMA code related to running via KEXEC. Implemented 64-bit int13 memdrive block moving code.

It might be possible that GRUB4DOS can overcome the 4GB limit now. I have less than 4GB oF RAM, so I can't test.

#138 diddy

diddy

    Member

  • Tutorial Writer
  • 78 posts

Posted 20 October 2009 - 08:20 PM

@karyonix
It will come as no great surprise that firadisk also works with Vista 32-bit and 64-bit - virtual floppy and virtual hard disks are mounted, virtual CD is not. Disable Driver Signature Enforcement is required when using Vista 64-bit.

I have also tested the driver with a non ram loading build of WinPE 3.0 (the image was applied to a hard disk and does not boot from a .wim image). This functioned similarly to Windows 7 and Vista with virtual floppy and virtual hard disks being detected correctly - virtual CD's are not. With some messing around I was able to boot non ram loading versions of WinPE 3.0 (x86 and amd64) from a disk image. The steps taken were as follows -

1) Mounted a disk image as drive R:

2) Applied the contents of a .wim image to drive R: using command syntax imagex.exe /apply my.wim 1 R:

3) Copied boot folder and bootmgr to R:

4) Deleted R:\boot\BCD

5) Created new BCD store by running the following batch -
@echo offBCDEDIT.EXE /createstore R:\boot\BCD BCDEDIT.EXE /store R:\boot\BCD /create {bootmgr} /d "Boot Manager"BCDEDIT.EXE /store R:\boot\BCD /set {bootmgr} device bootfor /f "tokens=3" %%A in ('BCDEDIT.EXE /store R:\boot\BCD /create /d "WINPE" /application osloader') do set guid=%%Aecho guid=%guid%echo.BCDEDIT.EXE /store R:\boot\BCD /set %guid% osdevice bootBCDEDIT.EXE /store R:\boot\BCD /set %guid% device bootBCDEDIT.EXE /store R:\boot\BCD /set %guid% path \Windows\system32\boot\winload.exeBCDEDIT.EXE /store R:\boot\BCD /set %guid% systemroot \WindowsBCDEDIT.EXE /store R:\boot\BCD /set %guid% winpe yesBCDEDIT.EXE /store R:\boot\BCD /set %guid% detecthal yesBCDEDIT.EXE /store R:\boot\BCD /displayorder %guid% /addlastpause
6) Mounted R:\windows\system32\config\system as HKLM\_WinPE_SYSTEM7) Merged one of the following .reg files - x86 registry file
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0001]"InfPath"="firadisk.inf""InfSection"="FiraDiskDevice""InfSectionExt"=".NTx86""ProviderName"="Karyonix""DriverDateData"=hex(3):00,40,19,FA,84,2E,CA,01"DriverDate"="9-6-2009""DriverVersion"="0.0.1.12""MatchingDeviceId"="root\\firadisk""DriverDesc"="FiraDisk Virtual Disk Enumerator"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\LEGACY_FASTFAT\0000\Control]"ActiveService"="Fastfat"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000]"Capabilities"=dword:00000000"Class"="SCSIAdapter""ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}""ConfigFlags"=dword:00000004"DeviceDesc"="FiraDisk Virtual Disk Enumerator""Driver"="{4D36E97B-E325-11CE-BFC1-08002BE10318}\\0001""HardwareID"=hex(07):72,00,6f,00,6f,00,74,00,5c,00,66,00,69,00,72,00,61,00,\64,00,69,00,73,00,6b,00,00,00,00,00"Mfg"="Karyonix""Service"="firadisk"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\Control]"ActiveService"="firadisk"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\LogConf][HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Services\firadisk\Enum]"0"="ROOT\\SCSIADAPTER\\0000""Count"=dword:00000001"NextInstance"=dword:00000001[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\root#firadisk]"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}""Service"="firadisk""DriverPackageId"="firadisk.inf_x86_neutral_094ec26a72ff2a56"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\GroupOrderList]"SCSI Miniport"=hex:3f,00,00,00,00,01,00,00,01,01,00,00,19,00,00,00,01,00,00,\  00,02,00,00,00,03,00,00,00,04,00,00,00,05,00,00,00,06,00,00,00,07,00,00,00,\  08,00,00,00,09,00,00,00,0a,00,00,00,0b,00,00,00,0c,00,00,00,0d,00,00,00,0e,\  00,00,00,0f,00,00,00,10,00,00,00,11,00,00,00,12,00,00,00,13,00,00,00,14,00,\  00,00,15,00,00,00,16,00,00,00,17,00,00,00,1a,00,00,00,18,00,00,00,1b,00,00,\  00,1c,00,00,00,1d,00,00,00,1e,00,00,00,1f,00,00,00,20,00,00,00,23,00,00,00,\  24,00,00,00,25,00,00,00,26,00,00,00,27,00,00,00,28,00,00,00,29,00,00,00,2a,\  00,00,00,2b,00,00,00,2c,00,00,00,2d,00,00,00,2e,00,00,00,2f,00,00,00,30,00,\  00,00,31,00,00,00,32,00,00,00,33,00,00,00,34,00,00,00,35,00,00,00,36,00,00,\  00,37,00,00,00,38,00,00,00,39,00,00,00,3a,00,00,00,3b,00,00,00,3c,00,00,00,\  3d,00,00,00,3e,00,00,00,3f,00,00,00[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\services\firadisk]"Start"=dword:00000000"Type"=dword:00000001"ErrorControl"=dword:00000001"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,66,00,69,00,72,00,61,00,64,00,69,\  00,73,00,6b,00,2e,00,73,00,79,00,73,00,00,00"DisplayName"="FiraDisk Virtual Disk Driver""Group"="SCSI miniport""DriverPackageId"="firadisk.inf_x86_neutral_094ec26a72ff2a56"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\detected#firadisk]"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}""Service"="firadisk""DriverPackageId"="firadisk.inf_x86_neutral_094ec26a72ff2a56"
amd64 registry file
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0001]"InfPath"="firadisk.inf""InfSection"="FiraDiskDevice""InfSectionExt"=".NTAMD64""ProviderName"="Karyonix""DriverDateData"=hex:00,40,19,fa,84,2e,ca,01"DriverDate"="9-6-2009""DriverVersion"="0.0.1.12""MatchingDeviceId"="root\\firadisk""DriverDesc"="FiraDisk Virtual Disk Enumerator"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\LEGACY_FASTFAT\0000\Control]"ActiveService"="Fastfat"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000]"ClassGUID"="{4d36e97b-e325-11ce-bfc1-08002be10318}""Class"="SCSIAdapter""Driver"="{4d36e97b-e325-11ce-bfc1-08002be10318}\\0001""Mfg"="@firadisk.inf,%mfakaryonix%;Karyonix""HardwareID"=hex(7):72,00,6f,00,6f,00,74,00,5c,00,66,00,69,00,72,00,61,00,64,\  00,69,00,73,00,6b,00,00,00,00,00"CompatibleIDs"=hex(7):64,00,65,00,74,00,65,00,63,00,74,00,65,00,64,00,5c,00,\  66,00,69,00,72,00,61,00,64,00,69,00,73,00,6b,00,00,00,00,00"Service"="firadisk""DeviceDesc"="@firadisk.inf,%firadiskdevice%;FiraDisk Virtual Disk Enumerator""ConfigFlags"=dword:00000000"Capabilities"=dword:00000000"ContainerID"="{00000000-0000-0000-FFFF-FFFFFFFFFFFF}""ParentIdPrefix"="1&2afd7d61&0"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\Control]"ActiveService"="firadisk"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\LogConf][HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Services\firadisk\Enum]"0"="ROOT\\SCSIADAPTER\\0000""Count"=dword:00000001"NextInstance"=dword:00000001[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\root#firadisk]"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}""Service"="firadisk""DriverPackageId"="firadisk.inf_amd64_neutral_094ec26a72ff2a56"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\GroupOrderList]"SCSI Miniport"=hex:3f,00,00,00,00,01,00,00,01,01,00,00,19,00,00,00,01,00,00,\  00,02,00,00,00,03,00,00,00,04,00,00,00,05,00,00,00,06,00,00,00,07,00,00,00,\  08,00,00,00,09,00,00,00,0a,00,00,00,0b,00,00,00,0c,00,00,00,0d,00,00,00,0e,\  00,00,00,0f,00,00,00,10,00,00,00,11,00,00,00,12,00,00,00,13,00,00,00,14,00,\  00,00,15,00,00,00,16,00,00,00,17,00,00,00,1a,00,00,00,18,00,00,00,1b,00,00,\  00,1c,00,00,00,1d,00,00,00,1e,00,00,00,1f,00,00,00,20,00,00,00,23,00,00,00,\  24,00,00,00,25,00,00,00,26,00,00,00,27,00,00,00,28,00,00,00,29,00,00,00,2a,\  00,00,00,2b,00,00,00,2c,00,00,00,2d,00,00,00,2e,00,00,00,2f,00,00,00,30,00,\  00,00,31,00,00,00,32,00,00,00,33,00,00,00,34,00,00,00,35,00,00,00,36,00,00,\  00,37,00,00,00,38,00,00,00,39,00,00,00,3a,00,00,00,3b,00,00,00,3c,00,00,00,\  3d,00,00,00,3e,00,00,00,3f,00,00,00[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Services\firadisk]"Start"=dword:00000000"Type"=dword:00000001"ErrorControl"=dword:00000001"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,66,00,69,00,72,00,61,00,64,00,69,\  00,73,00,6b,00,2e,00,73,00,79,00,73,00,00,00"DisplayName"="FiraDisk Virtual Disk Driver""Group"="SCSI miniport""DriverPackageId"="firadisk.inf_amd64_neutral_094ec26a72ff2a56"[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\detected#firadisk]"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}""Service"="firadisk""DriverPackageId"="firadisk.inf_amd64_neutral_094ec26a72ff2a56"

8) Copied firadisk.sys/firadisk64.sys as R:\Windows\System32\Drivers\firadisk.sys

9) Copied firadisk.inf to R:\Windows\inf

The fact that the Windows 7 based PE booted successfully makes me optimistic that a full Windows 7 (and probably Vista) can be booted from a disk image IF the source can be reduced to fit in a small enough disk image.

@Everyone.
Having to use Disable Driver Signature Enforcement for 64-bit operating systems is a pain in the a$$ - can anyone create a test certificate.

#139 karyonix

karyonix

    Frequent Member

  • Advanced user
  • 473 posts
  •  
    Thailand

Posted 21 October 2009 - 12:32 AM

@Everyone.
Having to use Disable Driver Signature Enforcement for 64-bit operating systems is a pain in the a$$ - can anyone create a test certificate.

Test-signed firadisk 0.0.1.12
http://www.mediafire...r-0.0.1.12a.zip

Sorry for slow development in previous mount and this month. My computer is not stable with 8GB RAM.
I spent a lot of time trying to find appropriate voltage and memory timing settings, reinstall Windows and all programs.

#140 diddy

diddy

    Member

  • Tutorial Writer
  • 78 posts

Posted 21 October 2009 - 05:48 AM

Test-signed firadisk 0.0.1.12...

Thank you for the fast response. 10 out of 10 for service. ;)

BTW, don't know what you mean about development having slowed down. Version 0.0.1.12 is rock solid stable on my system. I look forward to testing whatever you add with the next build.

diddy

#141 Marietto

Marietto

    Frequent Member

  • Advanced user
  • 268 posts
  • Location:Italy
  • Interests:Computers,movies,read/write,talking about philosophy and religion.
  •  
    Italy

Posted 24 October 2009 - 11:28 AM

I've loaded a full version of windows xp home SP3 into my RAM. As soon as Windows Xp is booted,an error is displayed. I would like to know why it happens and how to fix it.

Attached Files



#142 Marietto

Marietto

    Frequent Member

  • Advanced user
  • 268 posts
  • Location:Italy
  • Interests:Computers,movies,read/write,talking about philosophy and religion.
  •  
    Italy

Posted 24 October 2009 - 04:18 PM

On my computer I have 4 GB of RAM,but only 2947 MB are free. The hddimage script is able to make only 2 GB or 3 GB image size. I can't make a 3 GB image size because I have only 2947 MB free and I can't make a 2 GB image size because my installation of Windows takes 2600 mb. For this reason I would like to know if it is possibile to modify the hddimage script,so it can build images between 2 GB and 3 GB,or if I can resize the image in some way. Thanks.

update : sorry my mistake : I didn't understand that it was possible to make images with fractionated sizes.

#143 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 24 October 2009 - 05:44 PM

For this reason I would like to know if it is possibile to modify the hddimage script,so it can build images between 2 GB and 3 GB,or if I can resize the image in some way.


The idea of hddimage is of simplifying what in the original is too complex/normally unneeded, but it should give you an image size the way you specify it. :cheers::
http://www.boot-land...?showtopic=9033

D:\MBR Batch>hddimage

Usage: hddimage.cmd targetfile diskimagesize [round-to-cylinder=/R

targetfile is the path of the Disk Image File to be created

diskimagesize is the image size in bytes - add a suffix K, M or G for Kilo, Mega or Giga


If needed, try using the "original" MBRBATCH/MKIMG from which hddimage was originated ;):
http://www.boot-land...?showtopic=3191
http://www.boot-land...?showtopic=5000

;)

jaclaz

#144 joakim

joakim

    Silver Member

  • Team Reboot
  • 912 posts
  • Location:Bergen
  •  
    Norway

Posted 24 October 2009 - 05:58 PM

I am wondering how it is possible to make XP not fit on a 2 Gb image..

Follow diddy's guide http://www.boot-land...?showtopic=9328 and the tips given in answering posts. You should be able to make XP run with almost all services on an image at just 500 Mb. You must have the image NTFS compressed though, otherwise you should add a few hundred Mb's to the size to make it fit.

Joakim

#145 Marietto

Marietto

    Frequent Member

  • Advanced user
  • 268 posts
  • Location:Italy
  • Interests:Computers,movies,read/write,talking about philosophy and religion.
  •  
    Italy

Posted 25 October 2009 - 10:20 AM

done : I've loaded windows 7 totally into my ram. It's going very well,it is able to boot in 5 seconds. I've built an image of 2600 mb with the hddimage script and I copied the installation of windows 7 inside it. It takes 2500 mb,so I have 100 mb of free disk space.

#146 Marietto

Marietto

    Frequent Member

  • Advanced user
  • 268 posts
  • Location:Italy
  • Interests:Computers,movies,read/write,talking about philosophy and religion.
  •  
    Italy

Posted 25 October 2009 - 12:57 PM

thinking to new ideas ... :)

#147 joakim

joakim

    Silver Member

  • Team Reboot
  • 912 posts
  • Location:Bergen
  •  
    Norway

Posted 25 October 2009 - 01:10 PM

Hehe I guess I missed XP vs Win7. Nevermind.

Could you post your complete BCD store?

Joakim

#148 Marietto

Marietto

    Frequent Member

  • Advanced user
  • 268 posts
  • Location:Italy
  • Interests:Computers,movies,read/write,talking about philosophy and religion.
  •  
    Italy

Posted 25 October 2009 - 02:20 PM

This is the structure of the drives on my pc :

(hd 0,0) --> \ --> windows vista
(hd 1,0) --> g: --> windows flp
(hd 1,1) --> h: --> windows xp home sp3
(hd 0,1) --> n: --> debian lenny

the bcd store of disk (hd0) hasn't been touched
on the logical drive (hd1,1) there is no bcd store

this is the situation of the drive (hd1,0) :

boot.ini

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows FLP" /noexecute=optin /fastdetect

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect
c:\grldr="Grub4Dos"

menu.lst :

title Boot 7 from RAMDisk
find --set-root /7-ram.img
map --mem /7-ram.img (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

on the \ of the disk (hd1,0) there are the following files :

7-ram.img
boot.ini
grldr
grldr.mbr
menu.lst
ntdlr

the virtual image has been mounted on the R drive.
To make it bootable,I've used the Karyonix commands :

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

#149 joakim

joakim

    Silver Member

  • Team Reboot
  • 912 posts
  • Location:Bergen
  •  
    Norway

Posted 25 October 2009 - 02:47 PM

I meant the output of;

bcdedit /store r:\boot\bcd /enum all /v

Joakim

#150 Marietto

Marietto

    Frequent Member

  • Advanced user
  • 268 posts
  • Location:Italy
  • Interests:Computers,movies,read/write,talking about philosophy and religion.
  •  
    Italy

Posted 25 October 2009 - 05:14 PM

C:\>bcdedit /store r:\boot\bcd /enum all /v

Windows Boot Manager
--------------------
identificatore {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device boot
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {b4d91693-bae7-11de-be91-876037d6a2b5}
resumeobject {b4d91692-bae7-11de-be91-876037d6a2b5}
displayorder {b4d91693-bae7-11de-be91-876037d6a2b5}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Caricatore di avvio di Windows
-------------------
identificatore {b4d91693-bae7-11de-be91-876037d6a2b5}
device boot
path \Windows\system32\winload.exe
description Windows 7
locale it-IT
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
testsigning Yes
osdevice boot
systemroot \Windows
resumeobject {b4d91692-bae7-11de-be91-876037d6a2b5}
nx AlwaysOff
detecthal Yes

Ripresa da modalità di ibernazione
---------------------
identificatore {b4d91692-bae7-11de-be91-876037d6a2b5}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {1afa9c49-16ab-4a5c-901b-212802da9460}
filedevice unknown
filepath \hiberfil.sys
pae No
debugoptionenabled No

Tester memoria di Windows
---------------------
identificatore {b2721d73-1db4-4c62-bf78-c548a880142d}
device unknown
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess Yes

Impostazioni Servizi di gestione emergenze
------------
identificatore {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems Yes

Impostazioni debugger
-----------------
identificatore {4636856e-540f-4170-a130-a84776f4c654}
debugtype Serial
debugport 1
baudrate 115200

Problemi RAM
-----------
identificatore {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Impostazioni globali
---------------
identificatore {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit {4636856e-540f-4170-a130-a84776f4c654}
{0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
{5189b25c-5558-4bf2-bca4-289b11bd29e2}

Impostazioni caricatore di avvio
-------------------
identificatore {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
{7ff607e0-4395-11db-b0de-0800200c9a66}

Impostazioni hypervisor
-------------------
identificatore {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Impostazioni Resume Loader
----------------------
identificatore {1afa9c49-16ab-4a5c-901b-212802da9460}
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users