Jump to content











Photo
- - - - -

SVBus Virtual SCSI Host Adapter for GRUB4DOS

svbus virtual scsi host adapter grub4dos

  • Please log in to reply
137 replies to this topic

#126 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 12 December 2020 - 05:01 PM

It is UEFI only, still on first stages of development, the first version was released on 2020-11-19, so in your case, that you use your RamOS for everyday use, I suggest to wait a few more time to let the developer(s) fix certain details that are still under test.

 

This is IMHO the best place to look for the officially released versions: http://grub4dos.chen...-4-6a-for-UEFI/

 

I will add this link to post No. 121 too.

 

alacran



#127 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 12 December 2020 - 07:47 PM

the same goes for me - the best place, but all I see now ahead of the rest is a sequence of for-uefi ones, shall I ignore all of these? for the time being, I have the 2020-08-09 one.



#128 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 12 December 2020 - 08:12 PM

Yes, you are using the usuall MBR version, then go to this page: http://grub4dos.chen...ries/downloads/

 

Select 0.4.6a, and on next page just select the year 2020 and you will find there all 0.4.6a releases made on 2020, where 2020-08-09 is the more recent version.

 

By the way I'm still using for MBR the 0.4.6a from 2020-03-04 and haven't noticed it is even not listed anymore, it may have some bug and was removed, but so far it has being working fine for me.

 

alacran


  • antonino61 likes this

#129 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 12 December 2020 - 09:03 PM

exactly what I did.



#130 liuzhaoyzz

liuzhaoyzz

    Member

  • Members
  • 51 posts
  •  
    China

Posted 01 January 2021 - 05:47 AM

schtrom,
You have done a great job. Now, the developer of grub4dos_UEFI (2011yaya2007777) and the developer of grub2 (Wintoflash) have updated their codes so that they can adapt to svbus. After a period of exploration, they have been able to successfully start UEFI-RAMOS based on svbus by using g4e/grub2 map or grub2 ntboot module. Thank you for your dedication of open source svbus!
 
I seldom go to reboot.pro, so I offer my belated thanks. Happy New Year! @schtrom
 
 
Thanks for alacran.

Edited by liuzhaoyzz, 01 January 2021 - 05:56 AM.

  • wimb and alacran like this

#131 Guest_AnonVendetta_*

Guest_AnonVendetta_*
  • Guests

Posted 23 March 2021 - 01:56 AM

So, I'm prepping Windows 10 Enterprise 20H2 for a ramdisk test. I had originally wanted to use LTSC, but decided against it, since it doesn't quite fit all my needs. I use Xbox Live Game Pass to play the latest AAA titles from the Windows Store. That works fine with non LTSC versions, but not LTSC. It is something about many of them only wanting to install on the most recent Windows 10 versions. There are also other reasons that I've moved away from LTSC, but won't go into detail.

I plan to trim out most of the unwanted Metro apps from the Enterprise image, but otherwise it will remain as near stock. It doesn't do much good to remove most other components, since Windows Update will just try to reinstall them. But it won't restore removed Metro apps (in my recent VM test, it didn't).

So far I've integrated the signed SVBus driver into the wim file with dism. I've did a real, live install from that wim. In Device Management, SVBus is initially shown as being loaded fine.

And here's the issue:

Not long after I boot up this cleanly installed OS, Windows Defender does a scan. It sees svbusx64.sys and deletes it, claiming it's a trojan. So I tried to restore it from quarantine, that worked, but it deletes it again and again. I tried adding an exclusion, but it still deletes the file.

So I reboot, Windows boots fine. But of course this file is gone, and SVBus shows as not loaded in DM.

So I extract this file from the archive, place it in the right directory, set admins group as owner and grant full access to all user groups, reboot. At this point I've already disabled Defender with the Group Policy editor. But DM still shows the driver as not loaded.

The only permanent solution I've found for this is to mount the wim, edit its' Registry offline, adding entries that permanently set Defender as disabled even before the first boot. If I clean install from that image, SVBus loads fine and stays loaded, Defender isn't active at all.

Is there a way to work around this, without disabling Defender?

#132 Alexd025

Alexd025
  • Members
  • 1 posts
  •  
    France

Posted 26 April 2021 - 02:02 PM

since I was updating a w7 x86 ultimate ram image, I decided to try SVBus and it booted up with no problems here.
 
menu.lst I used:  
title RAM W7
find --set-root /w7.img
map --mem /w7.img (hd0)
map --hook
find --set-root /bootmgr
chainloader /bootmgr
 
thanks schtrom for another great Grub4Dos tool!

Your WIM files are of type install.wim and not PE boot.wim



#133 r18nix

r18nix
  • Members
  • 1 posts
  •  
    China

Posted 29 April 2021 - 12:10 PM

How to get svbus support  windows virtual memory ?



#134 Guest_AnonVendetta_*

Guest_AnonVendetta_*
  • Guests

Posted 21 May 2021 - 09:29 PM

Can someone say why SVBus works on a "live"/real Windows, but not in a VM? In both VirtualBox and VMWare, i get "resource not available" (or similar, cant remember the exact wording, but it's the same in both), when checking SVBus's properties in Device Management. It doesnt matter whether i integrate the driver into the wim, or install it after Windows is set up. My VM doesnt have Grub4Dos installed, and no image is being loaded at boot, but i'm pretty sure that those have nothing to do with this message. It would be useful to test SVBus in a VM before testing in a real install, but that doesnt seem possible.

#135 schtrom

schtrom

    Newbie

  • Members
  • 20 posts
  •  
    Germany

Posted 11 October 2022 - 02:30 PM

SVBus V1.3 Virtual SCSI Host Adapter for GRUB4DOS

 

Today we present the new virtual SCSI driver SVBus version 1.3 for use with GRUB4DOS. The code was already stable in daily use and was not changed at all. SVBus V1.3 driver files are now fully signed and can be used on Windows Vista x64 and later without disabling Driver Signature Enforcement. Therefore we do not have to enable TESTSIGNING or DISABLE_INTEGRITY_CHECKS like shown in the included tutorial. Be aware that 10 out of 70 virus scanners on virustotal.com report the driver as some malware like usual. If unsure check the source code and compile your own copy!

 

To download the newest version use the link in my first post.

 

Greets
Kai Schtrom


Edited by schtrom, 11 October 2022 - 02:31 PM.

  • alacran and antonino61 like this

#136 antonino61

antonino61

    Gold Member

  • Advanced user
  • 1525 posts
  •  
    Italy

Posted 11 October 2022 - 05:16 PM

My dear Schtrom, thank u ever so much for the update. btw, do u find it any faster than the previous version or is it just my wishful thinking?



#137 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 12 October 2022 - 06:24 AM

The code was already stable in daily use and was not changed at all. SVBus V1.3 driver files are now fully signed and can be used on Windows Vista x64 and later....

 

It seems only change is driver files are now signed.

 

alacran



#138 schtrom

schtrom

    Newbie

  • Members
  • 20 posts
  •  
    Germany

Posted 13 October 2022 - 01:39 PM

Dear ladies and gentlemen,

 

sorry we had to do another update today. We added an additional feature with Build 20221013 for the driver installer instx86 and instx64. It is now possible to update an existing SVBus adapter driver with the installer. We also did a new tutorial for Windows 11 x64 Build 22H2 install. See the changes below.

 

SVBus V1.3 Virtual SCSI Host Adapter for GRUB4DOS

Today we present the new virtual SCSI driver SVBus version 1.3 for use with GRUB4DOS. The code was already stable in daily use and was not changed at all. SVBus V1.3 driver files are now fully signed and can be used on Windows Vista x64 and later without disabling Driver Signature Enforcement. We do not have to enable TESTSIGNING or DISABLE_INTEGRITY_CHECKS like shown in some tutorials of the included ReadMe.txt file. Be aware that 10 out of 70 virus scanners on virustotal.com report the driver as some malware like usual. If unsure check the source code and compile your own copy!

We made the following changes in version 1.3:

  • the driver files svbus.cat, svbusx86.sys and svbusx64.sys are now fully signed
    We use a leaked Atheros certificate by Dell to sign all driver files and make the x64 driver load without the need to disable Driver Signature Enforcement on Windows Vista x64 and later. We do not have to enable TESTSIGNING or DISABLE_INTEGRITY_CHECKS like shown in some tutorials of the included ReadMe.txt file.
  • SVBus driver installer updated
    The driver installer can now update the SVBus driver on a running system. At the installer start the system date is set to 03/31/2013. This way we can install the SVBus driver with enabled Driver Signature Enforcement based on the leaked Atheros certificate. After installation is finished the original system date prior to installation is restored.
  • removed an unused REG_DWORD value in the INF [Strings] section
  • tutorial for Windows 11 x64 Build 22H2 install added to ReadMe.txt file

To download the newest version use the link in my first post.

 

Greets
Kai Schtrom


 


Edited by schtrom, 13 October 2022 - 01:39 PM.


#139 386

386

    Newbie

  • Members
  • 11 posts

Posted 01 February 2023 - 07:31 PM

Many thanks for this very good quality driver!

 

I have a question: is it possible to boot from SYSLINUX MEMDISK ram drives?







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

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users