Jump to content











Photo
- - - - -

boot server 2003 vhd created with hyper-v with grub4dos

hyper-v grub4dos

  • Please log in to reply
7 replies to this topic

#1 administrator

administrator
  • Members
  • 5 posts
  •  
    Netherlands

Posted 08 June 2013 - 03:13 PM

hello.

 

i created a vhd containing server 2003 with hyper-v of 3gb and I can load it in RAM and then boot it with grub4dos {map --mem}.

Windows boots in just 4 seconds.

But when I do this without RAM {mem} I get BSOD.

I want to do this to install the GPU and maybe more.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 



#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 6557 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 08 June 2013 - 03:34 PM

I am not sure but maybe try firadisk floppy image or winvblock image?



#3 administrator

administrator
  • Members
  • 5 posts
  •  
    Netherlands

Posted 08 June 2013 - 04:40 PM

I have firadisk installed inside.

Other wise I could not load the vhd in ram and then boot it {map --mem}.

But what do you mean by firadisk floppy?

The vhd of 3gb will never fit inside.

 

Thanks anyway.



#4 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13480 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 08 June 2013 - 05:03 PM

There are two pretty much "exchangeable" drivers, Winvblock and Firadisk.

 

Both are somehow "experimental" and while in theory they can do the same things, for some unknown reasons :w00t: Firadisk appears to work more often with "mem mapped" images (and fail with "direct mapped" ones) whilst Winvblock appears to work more often with "direct mapped" ones and fail with "mem mapped" ones  :unsure:

 

The general idea is, if one fails, try the other. ;)

 

:cheers:

Wonko



#5 administrator

administrator
  • Members
  • 5 posts
  •  
    Netherlands

Posted 08 June 2013 - 06:20 PM

ok this might be helpfull.

I get on it right away.

where can I download the most recent winvblock driver?

 

thanks.



#6 steve6375

steve6375

    Platinum Member

  • Developer
  • 6557 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 08 June 2013 - 06:30 PM

Try tutorial 74 on my site - look also at the menu for how to load it as a floppy. I don't have any recent experience of Win2003 (!!!) so don't blame me if it doesn't work!



#7 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13480 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 08 June 2013 - 06:36 PM

ok this might be helpfull.

I get on it right away.

where can I download the most recent winvblock driver?

 

thanks.

That - strangely :w00t: -  is a good question as there is a dedicated thread but the actual releases on it is difficult to find :whistling::

http://reboot.pro/fo...s-firadisk-etc/

http://reboot.pro/to...8168-winvblock/

http://reboot.pro/to...e-9#entry101308

 

More seriously :unsure:, it is not that easy to find actual instrctions for use:

http://reboot.pro/to...block/?p=119816

http://reboot.pro/to...-10#entry101891

(remember to thank the good IP board guys for having messed with links and CODE and CODEBOXES again and again)

do check however the thingy by Wimb:

http://reboot.pro/to...7-vhd-xp-setup/

(which you already found :w00t:) that does use Winvblock and besides containing a valid floppy image with the driver can probably be useful as an example.

 

AFAIK Sha0 tested the thingy mainly with 2003, so unless something "queer" is in your particular install/image :dubbio:, it should work alright.

 

:cheers:

Wonko



#8 administrator

administrator
  • Members
  • 5 posts
  •  
    Netherlands

Posted 08 June 2013 - 07:23 PM

i tried winvblock next to firadisk both installed.

same effect.

when I boot with ahci the bsod comes directly.

when I boot with ide windows logo apears and then the very same bsod.

I think this is just a difference in speed.

 

Do I have to install the ahci driver in hyper-v.

my chipset package contains more ahci drivers.

wich one to choose?

 

can I upload screenshots or even bigger files like complete VHDs.

I can then upload the VHD because it boots on every machine in RAM or with hyper-v.

 

administrator







Also tagged with one or more of these keywords: hyper-v, grub4dos

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users