Jump to content











Photo
- - - - -

SVBus Virtual SCSI Host Adapter for GRUB4DOS

svbus virtual scsi host adapter grub4dos

  • Please log in to reply
130 replies to this topic

#126 alacran

alacran

    Gold Member

  • .script developer
  • 1939 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
  • 1059 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

    Gold Member

  • .script developer
  • 1939 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
  • 1059 posts
  •  
    Italy

Posted 12 December 2020 - 09:03 PM

exactly what I did.



#130 liuzhaoyzz

liuzhaoyzz

    Member

  • Members
  • 46 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 AnonVendetta

AnonVendetta

    Silver Member

  • Advanced user
  • 836 posts
  • Location:A new beginning.....
  • Interests:Self-development, computing

Posted 3 weeks ago

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?





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