Jump to content











Photo
- - - - -

How does WinVBlock work?


  • Please log in to reply
1 reply to this topic

#1 wean_irdeh

wean_irdeh

    Newbie

  • Members
  • 16 posts
  •  
    Vietnam

Posted 25 July 2016 - 03:51 AM

Asking this question because when protection mode is entered, all mapped drive by grub4dos is ignored by Windows OS, but when this driver applied, the mapped drive is detected by windows.

 

How does this work?

Is this possible with the linux version (since linux has module system that can be loaded on boot)?

What is the difference with 'loopback booting' in GRUB 2 (like this)?

 

 

 



#2 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 25 July 2016 - 08:17 AM

1) Winvblock can be passed some parameters telling it how/what to mount, you need to add these parameters to grub4dos line mapping the image.

Example:

http://reboot.pro/to...ot-os-from-vhd/

write (0x55) #!GRUB4DOSx00v=1x00Win7Pro.vhdx00x80Win7Pro.isox00xFFx00

what grub4dos does is to write some strings in RAM where Winvblock looks for them

 

2) WHICH "Linux version"?

 

3) No real difference, the loopback device in GRUB2 allows to (temporarily and within the GRUB2 environment) access the contents of a disk image, just like grub4dos mapping does, what happens when the Windows HAL or the Linux kernel "takes command" is another thing, independent.

 

And this is I believe more or less the same issue as:

http://reboot.pro/to...istro-antix-15/

 

:duff:

Wonko






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users