32 replies to this topic

[sara - pmedia]

Hello everyone
I asked a few months ago but no reply what steps required to run xp directly from an .img without ram maping?

what steps needs to run from standard hard disk?
what steps needs to run from usb hard disk?

(I already have an .img that I built with wimb's tool and updated it on many different computers so it is very universal What should I do to use it directly)?

[L A M A]

Follow from below (if you're using karyonix's driver)




http://www.boot-land...ndpost&p=102349

[sara - pmedia]

ok, tanks
I understand we need to add firadisk parameter line to boot.ini
(or add 2 seperet lines with/without the firadisk parameter if i want use same img in ram&img mode In parallel)

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Normal" /fastdetect /NoExecute=OptIn

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="+IMG" /fastdetect /NoExecute=OptIn /firadisk=disk,vmem=x:\win.vhd



title RAM

map --mem /win.vhd (hd0)

map --hook

root (hd0,0)

chainloader /ntldr



title IMG

map /win.vhd (hd0)

map --hook

root (hd0,0)

chainloader /ntldr

If use select "RAM" then "Normal", Windows should be able to boot from RAM.
If use select "IMG" then "+IMG", Windows should be able to boot from win.vhd (if all other conditions are met).

whats all other conditions?

[sambul61]

I guess he's talking about general conditions of direct mapping vhd images with Grub4DOS. One condition is it must be continuous (defraged with Contig). Its interesting to learn the other... Not sure though, the above explanation is equally relevant to .VHD and .IMG image types.

[ireneuszp]

Hello everyone
I asked a few months ago but no reply what steps required to run xp directly from an .img without ram maping?

what steps needs to run from standard hard disk?
what steps needs to run from usb hard disk?

(I already have an .img that I built with wimb's tool and updated it on many different computers so it is very universal What should I do to use it directly)?

where I can find this "wimb's tool"

[Wonko the Sane]

where I can find this "wimb's tool"

Maybe here?
http://reboot.pro/9830/

(sticky or "pinned") in the FileDisks/RamDisks: Firadisk, etc. (this very) forum.....
http://reboot.pro/forum/94/
(first topic)


Wonko

[ireneuszp]

Maybe here?
http://reboot.pro/9830/

(sticky or "pinned") in the FileDisks/RamDisks: Firadisk, etc. (this very) forum.....
http://reboot.pro/forum/94/
(first topic)


Wonko

many thanks
After change of look of forum I can not find my self

[agni]

Read this
http://reboot.pro/11731/

Uses winvblock and Wimb's tool to boot and run xp from disk image

[Wonko the Sane]

many thanks
After change of look of forum I can not find my self

Hint:
GO on bottom right and select "911CD" instead of "Vader" as skin.
http://reboot.pro/13403/




Wonko

[L A M A]

where I can find this "wimb's tool"

Hint:
GO on bottom right and select "911CD" unstead of "Vader" as skin.
http://reboot.pro/13403/




Wonko

Someone got to put this 911CD as default!

[Wonko the Sane]

Someone got to put this 911CD as default!

Naah.

We were extremely lucky that our Emperor and Leader allowed Mikorist (aka HAL9000) to actually load the alternate skin and permit that we, subjects of boot-land reboot.pro, make use of it freely.

The Light Blue Ribbon Campaign for Freedom of Skin - this time - did not work - at least initially.

Asking to have the "right" skin as default may represent a too hard push - even if supported by a large number of subjects, I wouldn't dare to ask as much.

Look at your half full glass and at your green grass, and leave the empty half and his own (only seemingly greener from a distance) grass to your neighbour.


Wonko

[ireneuszp]

Read this
http://reboot.pro/11731/

Uses winvblock and Wimb's tool to boot and run xp from disk image

Beautifully, almost as from VMLite VBoot Loader

[wimb]

Read this
http://reboot.pro/11731/

Uses winvblock and Wimb's tool to boot and run xp from disk image

Thanks to WinVBlock as made by Sha0

Yes I think that is the way to go, if you want to boot XP image file direct from location on HDD

As described by DooDoo, referred to by agni and confirmed by ireneuszp

[wimb]

How to Install WinVBlock driver ?

It took me several manual steps (filecopy + creating and start of service) and reboots to succeed,
but is there a simple way to install WinVBlock driver ?

EDIT:
I found some more interesting info here
http://reboot.pro/11642/

[sara - pmedia]

1. thnks ireneuszp but i'm dont like vmlite i prefer grub4dos method...

2. dear wimb! ,Would you agree and you can add to your wonderful tool the /firadisk parameters to boot.ini for direct img booting?
or maby you can replace firadisk with winvblock driver in your tool so we can boot from img?

3. Before I try ... Did someone successed to boot directly make_xp_img
tool in this way?

4. Can anyone upload winvblock.ima for me? I'm looking it for long time

[ireneuszp]

1. thnks ireneuszp but i'm dont like vmlite i prefer grub4dos method...

This screenshot http://fotosy.google...s/xpram_1-1.jpg
is from WinXP via GRUB4DOS + firadisk + WinVblock [ map /xpmode/XPRAM_1.img (hd0) || map --mem /xpmode/XPRAM_1.img ]

title 1 Load /xpmode/XPRAM_1.img and Boot Windows Image via G4D inside XPRAM_1.img

	find --set-root --ignore-floppies /xpmode/XPRAM_1.img

	uuid ()

	map /xpmode/XPRAM_1.img (hd0) || map --mem /xpmode/XPRAM_1.img

	map --hook

	root (hd0,0)

	echo %@TIME%

	root

	uuid ()

	pause --wait=10 Uruchamianie GRand Unified Bootloader...

	## chainloader (hd0,0)/ntldr || chainloader (hd0,0)/NTLDR

	chainloader --force (hd0,0)/grldr  || chainloader --force (hd0,0)/GRLDR

	boot



title 2 Load /xpmode/XPRAM_1.img and Boot Windows Image via G4D inside XPRAM_1.img via MBR

	find --set-root --ignore-floppies /xpmode/XPRAM_1.img

	uuid ()

	map /xpmode/XPRAM_1.img (hd0) || map --mem /xpmode/XPRAM_1.img

	map --hook

	root (hd0,0)

	echo %@TIME%

	root

	uuid ()

	pause --wait=10 Uruchamianie GRand Unified Bootloader...

	rootnoverify (hd0)

	chainloader +1

	boot



title 3 Load /xpmode/XPRAM_1.img in FiraDisk RAMDISK and Boot Windows Image

	uuid ()

	find --set-root --ignore-floppies /xpmode/XPRAM_1.img

	map /xpmode/XPRAM_1.img (hd0) || map --mem /xpmode/XPRAM_1.img (hd0)

	map --hook

	root (hd0,0)

	uuid ()

	configfile (hd0,0)/menu.lst

	### chainloader /ntldr

and my menu.lst inside XPRAM_1.img

# This is a sample menu.lst file. You should make some changes to it.

# The old install method of booting via the stage-files has been removed.

# Please install GRLDR boot strap code to MBR with the bootlace.com

# utility under DOS/Win9x or Linux.



splashimage=/whistler.gz

color cyan/black black/light-gray green/black yellow/black

## splashimage=/2003r2.gz

foreground=F0F8FF

background=FF0000

timeout 30

default 0



title Microsoft Windows XP Professional Edition \n Microsoft Windows XP Professional Edition SP3...

	uuid ()

	chainloader /ntldr



title Konsola Odzyskiwania Systemu (/./setupldr.bin)\n Uruchamia Konsole Odzyskiwania Systemu Microsoft Windows.

	uuid ()

	pause --wait=0  Uruchamianie Konsoli Odzyskiwania Systemu Microsoft Windows...

	chainloader /cmdcons/setupldr.bin

	#####################################################################

	# write string "cmdcons" to memory 0000:7C03 in 2 steps:

	#####################################################################

	# step 1. Write 4 chars "cmdc" at 0000:7C03

	write 0x7C03 0x63646D63

	# step 2. Write 3 chars "ons" and an ending null at 0000:7C07

	write 0x7C07 0x00736E6F



title 

	root



title Wiersz Polecenia\n Uruchamia Wiersz Polecenia...

	uuid ()

	pause --wait=0  Uruchamianie Wiersza Polecen ...

	commandline



title Restart Komputera\n Uruchamia ponownie Komputer...

	clear

	pause --wait=0  Uruchamianie Ponownie Systemu ...

	reboot



title Zamknij Komputer\n Zamyka Komputer...

	clear

	pause --wait=0  Zamykanie Systemu ...

	halt





title Start Windows XP Image from FiraDisk RAMDISK

root (hd0,0)

chainloader /ntldr

[ireneuszp]

How to Install WinVBlock driver ?

It took me several manual steps (filecopy + creating and start of service) and reboots to succeed,
but is there a simple way to install WinVBlock driver ?

EDIT:
I found some more interesting info here
http://reboot.pro/11642/

I installed in this way WinVBlock
http://grub4dos-iren...s/WinVBlock.avi
in the same way I installed firadisk or

rundll32.exe advpack.dll,LaunchINFSection WinVBlk.INF,WinVBlock

rundll32.exe advpack.dll,LaunchINFSection firadisk.inf,FiraDiskDevice.NTx86

[L A M A]

somehow right clicking INF and clicking install worked for me... (for firadisk) so, I'm assuming this is what works for winvblock aswell

[sambul61]

Does this method allow to boot a non-continuous XP image by dynamically reading & parsing data to RAM & caching to disk as needed, as is planned in Vboot to handle large boot images with limited RAM?

[L A M A]

I read it three times... lately i i've become slow in understanding (or its a bad day) but i still can't understand what you're asking. Maybe wonko will answer?




Good night all... I'm out

[wimb]

I installed in this way WinVBlock
http://grub4dos-iren...s/WinVBlock.avi
in the same way I installed firadisk or

rundll32.exe advpack.dll,LaunchINFSection WinVBlk.INF,WinVBlock

rundll32.exe advpack.dll,LaunchINFSection firadisk.inf,FiraDiskDevice.NTx86

Thanks ireneuszp for interesting video and code for install of WinVBlock driver.
What is the SCSI controller - Unknown device ?

I did slightly different and obtain then that WinVBlock driver is occurring twice in device manager.

1. copy wvblk32.sys to C:\WINDOWS\system32\drivers
2. open cmd prompt at C:\WINDOWS\system32
3. give commands

sc create WinVBlock binPath= c:\windows\system32\drivers\wvblk32.sys type= kernel start= boot group= "SCSI miniport"

net start winvblock

4. Device Manager > Action Scan Hardware > Wizard New Hardware > Browse to C:\WinVBlock_0.0.1.8\bin
5. Device Manager select comp > Action Scan Hardware > Wizard New Hardware > Automatic Install

Installed are ROOT\WINVBLOCK\0000 and ROOT\WINVBLOCK\0001

==
=

Reboot to Install the driver properly in registry.

Then IMG_XP_Create.exe was used by reboot with other OS e.g. PE to create XPRAM_2.img
For booting XPRAM_2.img with WinVBlock driver I have used as Grub4dos entries outside in menu.lst

title Load XPRAM_2.img in WinVBlock RAMDISK and Boot XP 

find --set-root --ignore-floppies /XPRAM_2.img

map --mem /XPRAM_2.img (hd0)

map --hook

root (hd0,0)

chainloader /ntldr



title Boot XP Image - XPRAM_2.img on disk - WinVBlock FILEDISK

map /XPRAM_2.img (hd0)

map --hook

root (hd0,0)

chainloader /ntldr

My XP of Image file XPRAM_2.img is booting as normal with NTLDR and boot.ini

[wimb]

2. dear wimb! ,Would you agree and you can add to your wonderful tool the /firadisk parameters to boot.ini for direct img booting?
or maby you can replace firadisk with winvblock driver in your tool so we can boot from img?

Hi Sara,

You can dowload WinVBlock driver 0.0.1.8 from
http://reboot.pro/81...308#entry101308

Instead of install of FiraDisk driver, you can install WinVBlock driver as described in previous post.

For me the performance of WinVBlock driver was better for booting direct XP Image file on disk.
Also you can keep boot.ini in XP Image as installed and can use simple grub4dos entries outside as given above
so that you can select to boot either from RAMDISK or direct from Image file on disk (FILEDISK)

I will add in future WinVBlock to IMG_XP package, but for now you can follow the given procedure.

Nice to hear from you that you managed already to make very Universal XP Image file.

I wish you lots of succes in the next step, where you also will be able to acquire reg info of computers with less RAM

[sambul61]

I wish you lots of success in the next step, where you also will be able to acquire reg info of computers with less RAM

Could you elaborate on that - what do you mean exactly? With what tools and how?

[Sha0]

...I did slightly different and obtain then that WinVBlock driver is occurring twice in device manager...

That was a design flaw in WinVBlock 0.0.1.8. The next release (as well as currently available development binaries) will certainly avoid the two (or more) devices in Device Manager. Sorry about that, wimb (and others)!

[wimb]

Could you elaborate on that - what do you mean exactly? With what tools and how?

Booting full XP Image file from RAMDISK will need at least about 2 GB RAM

This technique was used to create Universal XP Image files.
In the learning process you acquire registry info of installed drivers on a lot of computers.
http://www.911cd.net...showtopic=23553
http://reboot.pro/13618/

WinVBlock driver allows to boot XP Image file as FILEDISK directly from location on HDD
In that case you don't need so much RAM
You can use then such computers also to make XP Image more Universal

@Sha0
Thanks for explanation, no problem.