New
#90
Have it here
I also have seperate SSD's for Linux (4 distros) and 1 for Windows Insider. All OS's have approx 250GB but the details of each OS filesystem differ (I mostly use the distro default). Windows and openSUSE are secure boot. Although I am using GRUB I often use the BIOS itself to multiboot.
Hi folks
Not sure if it's this build but SMBV1 isn't (apparently) working any more for me now.
Not real issue any more since the only time I really needed SMBV1 was when running KODI on a remote amazon fire TV box (you can sideload Android apps on an amazon tv box). The latest release of KODI (Leia 18.5) now supports SMBV3 or whatever and works fine -- However some people still needing SMBV1 might find this release seems to not like it.
I'm not saying this is a definite defect --I just can't get it working on my system. I've learned enough about networking in Windows though people often with seemingly identical hardware / software get different results when using networking. !!!!
Cheers
jimbo
Hi,
I installed this build on my windows 10 pro laptop this morning, I already had the 'stable' version of the browser installed, but since I'm running the 'beta' version on my desktop and have had good lick with it so far I decided to go ahead and install it on my laptop. It installed without any issues, so then I decided to go ahead an uninstall the stable version. That's when strange things started happening, everything synced correctly from my google account to the new browser, but when I went into settings under the default apps in the web browser area, chrome beta wasn't listed. So far I've ran the sfc /scannow command while logged in as the administrator, as well as the dism system image repair command while I was still logged in as the administrator, they both completed without finding any issues. Microsoft doesn't like google chrome browser, even though the new edge browser is chromium based. Has anyone else had the same issue, and if so how did you correct it ?
Thanks,
David
35 minutes to desktop.
Lost Grub on first restart, never seen it even after shutdown. I don't remember seeing an issue like this one in the pass during or after an upgrade. Loosing the boot menu is usually a Linux problem.
Minitool partition wizard shows the Manjaro Zeta-alpha partition.
To recover Grub when dual boot in cmd admin for Manjaro:C:\WINDOWS\system32>bcdedit /set {bootmgr} path \EFI\Manjaro\grubx64.efiCode:bcdedit /set {bootmgr} path \EFI\Manjaro\grubx64.efi
The operation completed successfully.
To recover Grub in cmd admin for Ubuntu's (not tested with the new Mint Debian):Don't see other problems. Upgrade Adrenalin to build 20.3.1 without a glitch. We do not have any bugs with the Radeon app since a very long time now.Code:bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi
Edit: For LMDE-4 Mint Debian Base
Code:bcdedit /set {bootmgr} path \EFI\debian\grubx64.efi
Last edited by MikeMecanic; 25 Mar 2020 at 00:16.
For those having problems with the dual boot menu not showing up anymore, NeoSmart iReboot still works perfectly, and is even faster... Or you can fix it with your Macrium Reflex rescue boot disk.