Generally UltraEdit will show "End of file, searching from top" when it reach end of file while searching text by F3 key.
But in guest os(Windows 10 LTSC 2019 and Windows 10 20H2) it cause BSOD.
I have tried on my desktop and laptop. Both of them have the same problem.
UltraEdit version I tested: 25.10.0.62 / 27.10.0.108
Normal:
Minidump on Windows 10 LTSC 2019:
Minidump on Windows 10 20H2:
thanks for reporting scott0122. We managed to reproduce this in-house with UtralEdit. There is a workaround if you're willing to try.
The workaround is:
Power off the VM and add
guestInfo.svga.wddm.enableGDIHW=FALSE
to your .vmx file, then power it back on.
This will disable GDI HW acceleration only and have no larger effect.
Update:
Guest hardware compatibility: W16.x/ESXI7 + Accelerate 3D graphics: on -> BSOD
Guest hardware compatibility: W16.x/ESXI7 + Accelerate 3D graphics: off -> fine
Guest hardware compatibility: W15.x/ESXI 6.7 + Accelerate 3D graphics: on -> fine
Guest hardware compatibility: W15.x/ESXI 6.7 + Accelerate 3D graphics: off -> fine
Guest hardware compatibility: W16.x/ESXI7 + Accelerate 3D graphics: on + guestInfo.svga.wddm.enableGDIHW=FALSE
There is another issue.
Left application is PrusaSlicer 2.3.0 alpha2(OpenGL app). You can download here: Releases · prusa3d/PrusaSlicer · GitHub
Right application is Chrome.
Their correct behavior should look like the picture.
Here are the results of my cross-test.
Guest hardware compatibility: W16.x/ESXI 7 + Accelerate 3D graphics: on
Guest hardware compatibility: W16.x/ESXI 7 + Accelerate 3D graphics: off
Guest hardware compatibility: W15.x + Accelerate 3D graphics: on
Guest hardware compatibility: W15.x + Accelerate 3D graphics: off
Guest hardware compatibility: ESXI 6.7 + Accelerate 3D graphics: on
Guest hardware compatibility: ESXI 6.7 + Accelerate 3D graphics: off
Hi,
Can you try setting an environment variable SVGA_MSAA=0 before invoking PrusaSlicer?
Do you still see blank screen in the PrusaSlicer window?
VMX:
virtualHW.version = "18"
mks.enable3d = "TRUE"
guestInfo.svga.wddm.enableGDIHW="FALSE"
Windows 10 global environment variable:
SVGA_MSAA=0
*UltraEdit cause BSOD: no
VMX:
virtualHW.version = "18"
mks.enable3d = "TRUE"
guestInfo.svga.wddm.enableGDIHW="TRUE"
Windows 10 global environment variable:
SVGA_MSAA=0
*UltraEdit cause BSOD: yes
VMX:
virtualHW.version = "18"
mks.enable3d = "FALSE"
guestInfo.svga.wddm.enableGDIHW="FALSE"
Windows 10 global environment variable:
SVGA_MSAA=0
*UltraEdit cause BSOD: no
VMX:
virtualHW.version = "18"
mks.enable3d = "FALSE"
guestInfo.svga.wddm.enableGDIHW="TRUE"
Windows 10 global environment variable:
SVGA_MSAA=0
*UltraEdit cause BSOD: no
VMX:
virtualHW.version = "16"
mks.enable3d = "TRUE"
guestInfo.svga.wddm.enableGDIHW="FALSE"
Windows 10 global environment variable:
SVGA_MSAA=0
*UltraEdit cause BSOD: no
VMX:
virtualHW.version = "16"
mks.enable3d = "TRUE"
guestInfo.svga.wddm.enableGDIHW="TRUE"
Windows 10 global environment variable:
SVGA_MSAA=0
*UltraEdit cause BSOD: no
VMX:
virtualHW.version = "16"
mks.enable3d = "FALSE"
guestInfo.svga.wddm.enableGDIHW="FALSE"
Windows 10 global environment variable:
SVGA_MSAA=0
*UltraEdit cause BSOD: no
VMX:
virtualHW.version = "16"
mks.enable3d = "FALSE"
guestInfo.svga.wddm.enableGDIHW="TRUE"
Windows 10 global environment variable:
SVGA_MSAA=0
*UltraEdit cause BSOD: no