Jump to content

- - - - -

SVBus Virtual SCSI Host Adapter for GRUB4DOS

svbus virtual scsi host adapter grub4dos

  • Please log in to reply
5 replies to this topic

#1 schtrom

  • Members
  • 6 posts

Posted A week ago

Download-Link: https://sourceforge....projects/svbus/



SVBus Virtual SCSI Host Adapter for GRUB4DOS

Today we present a new virtual SCSI driver for use with GRUB4DOS named SVBus. The
driver is used like WinVBlock and FiraDisk to access GRUB4DOS mapped drives from
Windows. At the moment VHD file disk and RAM boot are supported. The supported OS
platforms are Windows 2000 up to the newest Windows 10 on x86 and x64 architectures.
For interested developers the source code is included and licensed under the GPL.

Many thanks and much respect go out to the authors of WinAoE, WinVBlock (Shao Miller),
FiraDisk (Panot Joonkhiaw), DSEFix and of course to the reboot community, which made
the VHD RAM and disk boots in Windows possible!

Kai Schtrom

  • blackbalfur and alacran like this

#2 blackbalfur



  • Members
  • 38 posts

Posted A week ago

Thanks i will test this one for sure!!!

#3 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted A week ago

Interesting. :)


Care to list which differences/features it has (as compared to Firadisk and/or Winvblock)? :unsure:




#4 erwan.l


    Gold Member

  • Developer
  • 2278 posts
  • Location:Nantes - France

Posted A week ago

Very interesting to see some testings and more details around how it compares with winvblock/firadisk.

#5 Vortex


    Frequent Member

  • Advanced user
  • 235 posts

Posted A week ago

Hi schtrom,


Thanks for your SVBus Virtual SCSI Host Adapter for Grub4dos. Here is my report.


Booting off  from Win7PE 32-bit :

title Windows 7

chainloader /bootmgr7

title Win7PE 32-bit

map --mem (hd0,1)/Win7PESE_x86.ISO (hd32)
map --hook
chainloader (hd32)

C:\bootmgr7 is the renamed Windows 7 boot loader.  bootmgr is the grubdos loader grldr extracted from grub4dos-0.4.5c-2016-01-18.7z  : grldr is renamed to bootmgr


I have a Windows 7 installation on my root partition. 


After attaching my VHD disk in the Win7PE environment, the installation starts like the following :

C:\Win7-32bit>sources\setup.exe /noreboot

All the setup files were copied to the root partition of my drive. Since the Windows installer overwrites the C:\boot folder and the C:\bootmgr file, I backed up them to another folder.


The attached VHD file Win7.vhd is associated with the drive letter F


Adding the SVBus driver to the Windows 
C:\Svbus\bin>dism /add-driver /driver:svbus.inf /image:F:\

Deployment Image Servicing and Management tool
Version: 6.1.7601.17514

Image Version: 6.1.7601.23403

Found 1 driver package(s) to install.
Installing 1 of 1 - C:\Svbus\bin\svbus.inf: The driver package was successfully
The operation completed successfully.

Creating the BCD record :

C:\Svbus\bin>bcdboot F:\Windows /s F:
Boot files successfully created.

After detaching the virtual drive F, I restored the folder C:\boot  and the file C:\bootmgr file as they were modified by setup.exe


Booting the Windows 7 instance stored in the VHD file :


title Windows 7 - FILEDISK
find --set-root --ignore-floppies /win7.vhd
map /Win7.vhd (hd0)
map --hook
root (hd0,0)
chainloader /bootmgr

Everything worked fine and the installation completed successfully. schtrom, the procedure you described in the Readme file worked too.


Thanks again for this nice driver.

#6 Vortex


    Frequent Member

  • Advanced user
  • 235 posts

Posted A week ago



A quicker setup experiment. Again, booted off from Win7PE 32-bit. I attached the virtual disk Win7.vhd using the disk management console.


The index number 4 represents the Professional version of Windows 7. F indicates the virtual partition F hosted by Win7.vhd

X:\Windows\System32\Tools\imagex2>imagex.exe /apply C:\Win7-32bit\sources\install.wim 4 F:

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385

[ 100% ] Applying progress

Successfully applied image.

Total elapsed time: 6 min 6 sec

Creating the BCD store :

X:\Windows\System32\Tools\imagex2>bcdboot F:\Windows /s F:
Boot files successfully created.

Injecting the SVBus driver :

X:\Windows\System32\Tools\imagex2>reg LOAD Hklm\sys F:\Windows\System32\config\SYSTEM
The operation completed successfully.

X:\Windows\System32\Tools\imagex2>reg IMPORT D:\SvBus.reg
The operation completed successfully.

X:\Windows\System32\Tools\imagex2>reg unload HKLM\sys
The operation completed successfully.

C:\Svbus\bin>copy svbus.inf F:\Windows\inf
        1 file(s) copied.

C:\Svbus\bin>copy svbusx86.sys F:\Windows\System32\drivers
        1 file(s) copied.
SvBus.reg :
Windows Registry Editor Version 5.00



"Group"="SCSI Miniport"

Two registry shots before and after the driver installation with the dism command were enough to produce the .reg file above.

<First registry capture>
dism /add-driver /driver:svbus.inf /image:F:\
<Second registry capture>

Edit : Using this second method, the remark unknow device can appear in the device manager. Reinstalling the driver is solving this issue.

Also tagged with one or more of these keywords: svbus, virtual scsi host adapter, grub4dos

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users