TWO WORDS: TOTAL DISASSTER

THE DEFAULT FONT RENDERING IS COMPLETELY FUCKED UP.

EVERYTHING IS SMALL, VAGUE AND WASHED OUT, HARD TO READ.

THE CRISPINESS OF WINDOWS 7 IS COMPLETELY GONE.

I CAN EVEN FEEL A SLIGHT HEADACHE... COULD BE FROM TOO LITTLE SLEEP.

I NOTICED THIS VAGUENESS FROM THE START BUT DISMISSED IT AS SOME KIND OF SCALING ISSUE IN VMWARE OR LACK OF SCREEN RESOLUTION BUT NOW THAT I HAVE UPPED THE SCREEN RESOLUTION TO HIGHER SETTINGS IT'S BEING APPERENT TO ME THAT WINDOWS 11 HAS A GIGANTIC FLAW/ISSUE.

MY SPECULATION ABOUT THIS IS THE WAY THE OS RENDERS THE ENTIRE GUI, IT MAY BE RENDERING IT/UPSCALING IT TO WORK ON 4K SCREENS.

THIS DOESN'T WORK ON LOWER SCREEN RESOLUTIONS AND IS A COMPLETE DISASSISTER..

I NOTICED THE VGA ADAPTER OF VMWARE IS STILL AT 8 BIT, I HOPE THAT MAYBE CHANGING IT TO 32 BIT OR SOMETHING ELSE MIGHT WORK BETTER...

MAYBE CHANGING THEMES MIGHT HELP.

BUT SO FAR IF THIS IS THE FUTURE OF WINDOWS, THEN WINDOWS ENDS RIGHT HERE.

I WOULD NEVER EVER USE SUCH A HORRIBLE LOOKING OPERATING SYSTEM.

HAHAHAHAHAHAHAHA\HAHAHAHAHAHA BILLIONS OF DOLLARS DOWN THE TUBE.

I HOPE ON REAL HARDWARE IT WORKS BETTER, OTHERWISE SOMEBODY DEEP IN MICROSOFT SCREWED THEM/BILL OVER REAL HARD.

PERHAPS PAYBACK FOR CORONA CRISIS.

SEE YA !

BYE,
SKYBUCK.

On 11/2/2021 2:38 AM, skybuck2000 wrote:
> TWO WORDS: TOTAL DISASSTER
>
> THE DEFAULT FONT RENDERING IS COMPLETELY FUCKED UP.
>
> EVERYTHING IS SMALL, VAGUE AND WASHED OUT, HARD TO READ.
>
> THE CRISPINESS OF WINDOWS 7 IS COMPLETELY GONE.
>
> I CAN EVEN FEEL A SLIGHT HEADACHE... COULD BE FROM TOO LITTLE SLEEP.
>
> I NOTICED THIS VAGUENESS FROM THE START BUT DISMISSED IT AS SOME KIND OF SCALING ISSUE IN VMWARE OR LACK OF SCREEN RESOLUTION BUT NOW THAT I HAVE UPPED THE SCREEN RESOLUTION TO HIGHER SETTINGS IT'S BEING APPERENT TO ME THAT WINDOWS 11 HAS A GIGANTIC FLAW/ISSUE.
>
> MY SPECULATION ABOUT THIS IS THE WAY THE OS RENDERS THE ENTIRE GUI, IT MAY BE RENDERING IT/UPSCALING IT TO WORK ON 4K SCREENS.
>
> THIS DOESN'T WORK ON LOWER SCREEN RESOLUTIONS AND IS A COMPLETE DISASSISTER.
>
> I NOTICED THE VGA ADAPTER OF VMWARE IS STILL AT 8 BIT, I HOPE THAT MAYBE CHANGING IT TO 32 BIT OR SOMETHING ELSE MIGHT WORK BETTER...
>
> MAYBE CHANGING THEMES MIGHT HELP.
>
> BUT SO FAR IF THIS IS THE FUTURE OF WINDOWS, THEN WINDOWS ENDS RIGHT HERE.
>
> I WOULD NEVER EVER USE SUCH A HORRIBLE LOOKING OPERATING SYSTEM.
>
> HAHAHAHAHAHAHAHA\HAHAHAHAHAHA BILLIONS OF DOLLARS DOWN THE TUBE.
>
> I HOPE ON REAL HARDWARE IT WORKS BETTER, OTHERWISE SOMEBODY DEEP IN MICROSOFT SCREWED THEM/BILL OVER REAL HARD.
>
> PERHAPS PAYBACK FOR CORONA CRISIS.
>
> SEE YA !
>
> BYE,
> SKYBUCK.

Device Manager, check to see if "Microsoft Basic Display Adapter"
driver is running the virtual video card. That's the "no driver
is present" driver.

Use the VMWare Additions, install it, and that will define a driver
for the virtual video card.

That should come closer to driving at native resolution.

I did have some trouble with VMWare, with window resizing of the Win11
overall OS window. This causes the res to be slightly off and leads
to fuzzy fonts.

Summary: It's hard to do well (poor indicators), but try to get the
frame buffer running at native resolution. It doesn't
have to fill the screen, to do that. a 1440x900 can run a
1024x768 session.

Paul

On Tuesday, November 2, 2021 at 8:29:53 AM UTC+1, Paul wrote:
> On 11/2/2021 2:38 AM, skybuck2000 wrote:
> > TWO WORDS: TOTAL DISASSTER
> >
> > THE DEFAULT FONT RENDERING IS COMPLETELY FUCKED UP.
> >
> > EVERYTHING IS SMALL, VAGUE AND WASHED OUT, HARD TO READ.
> >
> > THE CRISPINESS OF WINDOWS 7 IS COMPLETELY GONE.
> >
> > I CAN EVEN FEEL A SLIGHT HEADACHE... COULD BE FROM TOO LITTLE SLEEP.
> >
> > I NOTICED THIS VAGUENESS FROM THE START BUT DISMISSED IT AS SOME KIND OF SCALING ISSUE IN VMWARE OR LACK OF SCREEN RESOLUTION BUT NOW THAT I HAVE UPPED THE SCREEN RESOLUTION TO HIGHER SETTINGS IT'S BEING APPERENT TO ME THAT WINDOWS 11 HAS A GIGANTIC FLAW/ISSUE.
> >
> > MY SPECULATION ABOUT THIS IS THE WAY THE OS RENDERS THE ENTIRE GUI, IT MAY BE RENDERING IT/UPSCALING IT TO WORK ON 4K SCREENS.
> >
> > THIS DOESN'T WORK ON LOWER SCREEN RESOLUTIONS AND IS A COMPLETE DISASSISTER.
> >
> > I NOTICED THE VGA ADAPTER OF VMWARE IS STILL AT 8 BIT, I HOPE THAT MAYBE CHANGING IT TO 32 BIT OR SOMETHING ELSE MIGHT WORK BETTER...
> >
> > MAYBE CHANGING THEMES MIGHT HELP.
> >
> > BUT SO FAR IF THIS IS THE FUTURE OF WINDOWS, THEN WINDOWS ENDS RIGHT HERE.
> >
> > I WOULD NEVER EVER USE SUCH A HORRIBLE LOOKING OPERATING SYSTEM.
> >
> > HAHAHAHAHAHAHAHA\HAHAHAHAHAHA BILLIONS OF DOLLARS DOWN THE TUBE.
> >
> > I HOPE ON REAL HARDWARE IT WORKS BETTER, OTHERWISE SOMEBODY DEEP IN MICROSOFT SCREWED THEM/BILL OVER REAL HARD.
> >
> > PERHAPS PAYBACK FOR CORONA CRISIS.
> >
> > SEE YA !
> >
> > BYE,
> > SKYBUCK.
> Device Manager, check to see if "Microsoft Basic Display Adapter"
> driver is running the virtual video card. That's the "no driver
> is present" driver.
>
> Use the VMWare Additions, install it, and that will define a driver
> for the virtual video card.
>
> That should come closer to driving at native resolution.
>
> I did have some trouble with VMWare, with window resizing of the Win11
> overall OS window. This causes the res to be slightly off and leads
> to fuzzy fonts.
>
> Summary: It's hard to do well (poor indicators), but try to get the
> frame buffer running at native resolution. It doesn't
> have to fill the screen, to do that. a 1440x900 can run a
> 1024x768 session.

I don't think installing vmware tools will change anything. Not going to do it to this installation.

But I may try it on a new windows installment to see if it changes anything..

As far as I am concerned it's already running native and the problem seems to be and could be much deeper inside windows 10 and 11.

Google is full of complaints about bad fonts.

My guess is the people that write the code died or left Microsoft and now Microsoft does not know how to fix/apply the code properly.

Or they tried to re-write the old code for various reasons and they failed miserably to get all the great functionality out of it.

Or indeed scaling issues deep inside the microsoft code/sloppyness.

To see the bad fonts you must compare windows 7 vs windows 11, otherwise you'll miss it ! ;)

Plus turn off clear text on windows 7.

Bye for now,
Skybuck.

On 11/2/2021 3:59 PM, skybuck2000 wrote:
> On Tuesday, November 2, 2021 at 8:29:53 AM UTC+1, Paul wrote:
>> On 11/2/2021 2:38 AM, skybuck2000 wrote:
>>> TWO WORDS: TOTAL DISASSTER
>>>
>>> THE DEFAULT FONT RENDERING IS COMPLETELY FUCKED UP.
>>>
>>> EVERYTHING IS SMALL, VAGUE AND WASHED OUT, HARD TO READ.
>>>
>>> THE CRISPINESS OF WINDOWS 7 IS COMPLETELY GONE.
>>>
>>> I CAN EVEN FEEL A SLIGHT HEADACHE... COULD BE FROM TOO LITTLE SLEEP.
>>>
>>> I NOTICED THIS VAGUENESS FROM THE START BUT DISMISSED IT AS SOME KIND OF SCALING ISSUE IN VMWARE OR LACK OF SCREEN RESOLUTION BUT NOW THAT I HAVE UPPED THE SCREEN RESOLUTION TO HIGHER SETTINGS IT'S BEING APPERENT TO ME THAT WINDOWS 11 HAS A GIGANTIC FLAW/ISSUE.
>>>
>>> MY SPECULATION ABOUT THIS IS THE WAY THE OS RENDERS THE ENTIRE GUI, IT MAY BE RENDERING IT/UPSCALING IT TO WORK ON 4K SCREENS.
>>>
>>> THIS DOESN'T WORK ON LOWER SCREEN RESOLUTIONS AND IS A COMPLETE DISASSISTER.
>>>
>>> I NOTICED THE VGA ADAPTER OF VMWARE IS STILL AT 8 BIT, I HOPE THAT MAYBE CHANGING IT TO 32 BIT OR SOMETHING ELSE MIGHT WORK BETTER...
>>>
>>> MAYBE CHANGING THEMES MIGHT HELP.
>>>
>>> BUT SO FAR IF THIS IS THE FUTURE OF WINDOWS, THEN WINDOWS ENDS RIGHT HERE.
>>>
>>> I WOULD NEVER EVER USE SUCH A HORRIBLE LOOKING OPERATING SYSTEM.
>>>
>>> HAHAHAHAHAHAHAHA\HAHAHAHAHAHA BILLIONS OF DOLLARS DOWN THE TUBE.
>>>
>>> I HOPE ON REAL HARDWARE IT WORKS BETTER, OTHERWISE SOMEBODY DEEP IN MICROSOFT SCREWED THEM/BILL OVER REAL HARD.
>>>
>>> PERHAPS PAYBACK FOR CORONA CRISIS.
>>>
>>> SEE YA !
>>>
>>> BYE,
>>> SKYBUCK.
>> Device Manager, check to see if "Microsoft Basic Display Adapter"
>> driver is running the virtual video card. That's the "no driver
>> is present" driver.
>>
>> Use the VMWare Additions, install it, and that will define a driver
>> for the virtual video card.
>>
>> That should come closer to driving at native resolution.
>>
>> I did have some trouble with VMWare, with window resizing of the Win11
>> overall OS window. This causes the res to be slightly off and leads
>> to fuzzy fonts.
>>
>> Summary: It's hard to do well (poor indicators), but try to get the
>> frame buffer running at native resolution. It doesn't
>> have to fill the screen, to do that. a 1440x900 can run a
>> 1024x768 session.
>
> I don't think installing vmware tools will change anything. Not going to do it to this installation.
>
> But I may try it on a new windows installment to see if it changes anything.
>
> As far as I am concerned it's already running native and the problem seems to be and could be much deeper inside windows 10 and 11.
>
> Google is full of complaints about bad fonts.
>
> My guess is the people that write the code died or left Microsoft and now Microsoft does not know how to fix/apply the code properly.
>
> Or they tried to re-write the old code for various reasons and they failed miserably to get all the great functionality out of it.
>
> Or indeed scaling issues deep inside the microsoft code/sloppyness.
>
> To see the bad fonts you must compare windows 7 vs windows 11, otherwise you'll miss it ! ;)
>
> Plus turn off clear text on windows 7.
>
> Bye for now,
> Skybuck.
>

Try tpm.msc inside your virtual machine.

Does it say you have a TPM present ?

Now install the VMWare Tools.

Use tpm.msc panel again. Does it
say there is a TPM now ?

I don't know all the details, but I recommend for a Win11
install that you inspect the hardware facilities for flaws.
A missing TPM would be one of them. tpm.msc can help you
determine there is a VMWare software TPM or not. Fortunately,
VMWare does not do passthru for its TPM. It is possible when
VirtualBox releases their TPM support, it will be a passthru
version (not software, will depend on motherboard TPM). In
such a case then, VirtualBox might not be as good, on the
TPM topic.

Paul

On Tuesday, November 2, 2021 at 9:52:24 PM UTC+1, Paul wrote:
> On 11/2/2021 3:59 PM, skybuck2000 wrote:
> > On Tuesday, November 2, 2021 at 8:29:53 AM UTC+1, Paul wrote:
> >> On 11/2/2021 2:38 AM, skybuck2000 wrote:
> >>> TWO WORDS: TOTAL DISASSTER
> >>>
> >>> THE DEFAULT FONT RENDERING IS COMPLETELY FUCKED UP.
> >>>
> >>> EVERYTHING IS SMALL, VAGUE AND WASHED OUT, HARD TO READ.
> >>>
> >>> THE CRISPINESS OF WINDOWS 7 IS COMPLETELY GONE.
> >>>
> >>> I CAN EVEN FEEL A SLIGHT HEADACHE... COULD BE FROM TOO LITTLE SLEEP.
> >>>
> >>> I NOTICED THIS VAGUENESS FROM THE START BUT DISMISSED IT AS SOME KIND OF SCALING ISSUE IN VMWARE OR LACK OF SCREEN RESOLUTION BUT NOW THAT I HAVE UPPED THE SCREEN RESOLUTION TO HIGHER SETTINGS IT'S BEING APPERENT TO ME THAT WINDOWS 11 HAS A GIGANTIC FLAW/ISSUE.
> >>>
> >>> MY SPECULATION ABOUT THIS IS THE WAY THE OS RENDERS THE ENTIRE GUI, IT MAY BE RENDERING IT/UPSCALING IT TO WORK ON 4K SCREENS.
> >>>
> >>> THIS DOESN'T WORK ON LOWER SCREEN RESOLUTIONS AND IS A COMPLETE DISASSISTER.
> >>>
> >>> I NOTICED THE VGA ADAPTER OF VMWARE IS STILL AT 8 BIT, I HOPE THAT MAYBE CHANGING IT TO 32 BIT OR SOMETHING ELSE MIGHT WORK BETTER...
> >>>
> >>> MAYBE CHANGING THEMES MIGHT HELP.
> >>>
> >>> BUT SO FAR IF THIS IS THE FUTURE OF WINDOWS, THEN WINDOWS ENDS RIGHT HERE.
> >>>
> >>> I WOULD NEVER EVER USE SUCH A HORRIBLE LOOKING OPERATING SYSTEM.
> >>>
> >>> HAHAHAHAHAHAHAHA\HAHAHAHAHAHA BILLIONS OF DOLLARS DOWN THE TUBE.
> >>>
> >>> I HOPE ON REAL HARDWARE IT WORKS BETTER, OTHERWISE SOMEBODY DEEP IN MICROSOFT SCREWED THEM/BILL OVER REAL HARD.
> >>>
> >>> PERHAPS PAYBACK FOR CORONA CRISIS.
> >>>
> >>> SEE YA !
> >>>
> >>> BYE,
> >>> SKYBUCK.
> >> Device Manager, check to see if "Microsoft Basic Display Adapter"
> >> driver is running the virtual video card. That's the "no driver
> >> is present" driver.
> >>
> >> Use the VMWare Additions, install it, and that will define a driver
> >> for the virtual video card.
> >>
> >> That should come closer to driving at native resolution.
> >>
> >> I did have some trouble with VMWare, with window resizing of the Win11
> >> overall OS window. This causes the res to be slightly off and leads
> >> to fuzzy fonts.
> >>
> >> Summary: It's hard to do well (poor indicators), but try to get the
> >> frame buffer running at native resolution. It doesn't
> >> have to fill the screen, to do that. a 1440x900 can run a
> >> 1024x768 session.
> >
> > I don't think installing vmware tools will change anything. Not going to do it to this installation.
> >
> > But I may try it on a new windows installment to see if it changes anything.
> >
> > As far as I am concerned it's already running native and the problem seems to be and could be much deeper inside windows 10 and 11.
> >
> > Google is full of complaints about bad fonts.
> >
> > My guess is the people that write the code died or left Microsoft and now Microsoft does not know how to fix/apply the code properly.
> >
> > Or they tried to re-write the old code for various reasons and they failed miserably to get all the great functionality out of it.
> >
> > Or indeed scaling issues deep inside the microsoft code/sloppyness.
> >
> > To see the bad fonts you must compare windows 7 vs windows 11, otherwise you'll miss it ! ;)
> >
> > Plus turn off clear text on windows 7.
> >
> > Bye for now,
> > Skybuck.
> >
> Try tpm.msc inside your virtual machine.
>
> Does it say you have a TPM present ?
>
> Now install the VMWare Tools.
>
> Use tpm.msc panel again. Does it
> say there is a TPM now ?
>
> I don't know all the details, but I recommend for a Win11
> install that you inspect the hardware facilities for flaws.
> A missing TPM would be one of them. tpm.msc can help you
> determine there is a VMWare software TPM or not. Fortunately,
> VMWare does not do passthru for its TPM. It is possible when
> VirtualBox releases their TPM support, it will be a passthru
> version (not software, will depend on motherboard TPM). In
> such a case then, VirtualBox might not be as good, on the
> TPM topic.

HAHA.

I just had a brilliant idea.

I am going to copy the Virtual Machine to an experimental folder.

And then I will install VMWare Tools in the experimental copy to get to the bottom of this RRrrresolution issue ! ;)

I don't see what TPM has to do with it, but will check for it as well haha.

I added it myself manually so it should be there... but will check for you anyway =D

Bye for now,
Skybuck.

On Tuesday, November 2, 2021 at 8:29:53 AM UTC+1, Paul wrote:
> On 11/2/2021 2:38 AM, skybuck2000 wrote:
> > TWO WORDS: TOTAL DISASSTER
> >
> > THE DEFAULT FONT RENDERING IS COMPLETELY FUCKED UP.
> >
> > EVERYTHING IS SMALL, VAGUE AND WASHED OUT, HARD TO READ.
> >
> > THE CRISPINESS OF WINDOWS 7 IS COMPLETELY GONE.
> >
> > I CAN EVEN FEEL A SLIGHT HEADACHE... COULD BE FROM TOO LITTLE SLEEP.
> >
> > I NOTICED THIS VAGUENESS FROM THE START BUT DISMISSED IT AS SOME KIND OF SCALING ISSUE IN VMWARE OR LACK OF SCREEN RESOLUTION BUT NOW THAT I HAVE UPPED THE SCREEN RESOLUTION TO HIGHER SETTINGS IT'S BEING APPERENT TO ME THAT WINDOWS 11 HAS A GIGANTIC FLAW/ISSUE.
> >
> > MY SPECULATION ABOUT THIS IS THE WAY THE OS RENDERS THE ENTIRE GUI, IT MAY BE RENDERING IT/UPSCALING IT TO WORK ON 4K SCREENS.
> >
> > THIS DOESN'T WORK ON LOWER SCREEN RESOLUTIONS AND IS A COMPLETE DISASSISTER.
> >
> > I NOTICED THE VGA ADAPTER OF VMWARE IS STILL AT 8 BIT, I HOPE THAT MAYBE CHANGING IT TO 32 BIT OR SOMETHING ELSE MIGHT WORK BETTER...
> >
> > MAYBE CHANGING THEMES MIGHT HELP.
> >
> > BUT SO FAR IF THIS IS THE FUTURE OF WINDOWS, THEN WINDOWS ENDS RIGHT HERE.
> >
> > I WOULD NEVER EVER USE SUCH A HORRIBLE LOOKING OPERATING SYSTEM.
> >
> > HAHAHAHAHAHAHAHA\HAHAHAHAHAHA BILLIONS OF DOLLARS DOWN THE TUBE.
> >
> > I HOPE ON REAL HARDWARE IT WORKS BETTER, OTHERWISE SOMEBODY DEEP IN MICROSOFT SCREWED THEM/BILL OVER REAL HARD.
> >
> > PERHAPS PAYBACK FOR CORONA CRISIS.
> >
> > SEE YA !
> >
> > BYE,
> > SKYBUCK.
> Device Manager, check to see if "Microsoft Basic Display Adapter"
> driver is running the virtual video card. That's the "no driver
> is present" driver.
>
> Use the VMWare Additions, install it, and that will define a driver
> for the virtual video card.

Try it, doesn't make much difference, besides from more resolutions available still no 1600x900 but 1600x1200 will do for now.

What is interesting is higher resolutions possible then monitor supports, this would allow me to scroll the desktop which is kinda cool ! =D

>
> That should come closer to driving at native resolution.
>
> I did have some trouble with VMWare, with window resizing of the Win11
> overall OS window. This causes the res to be slightly off and leads
> to fuzzy fonts.
>
> Summary: It's hard to do well (poor indicators), but try to get the
> frame buffer running at native resolution. It doesn't
> have to fill the screen, to do that. a 1440x900 can run a
> 1024x768 session.

Strange thing is it only seems to run at 8 bit, host is 32 bit colors, yet guess os is only in 8 bit mode ? weird.

There may be an additional font issue in Delphi 10.4 vs Delphi 11:

https://landgraf.dev/en/high-dpi-support-in-delphi-11-and-why-does-it-matter/

However other fonts in Windows 11 seem washed out as well like in Edge.

I may have to make some screenshots later to convince you and others ! ;)

Windows 7 vs Windows 11
Firefox vs Edge
Delphi 10.3 vs Delphi 10.4
Maybe I will even installed Delphi 10.3 in windows 11 and maybe even Delphi 11 just to get to the bottom of this.

For now I believe windows 11 has a washed out look/problem.

At first glance it looks ok, but after a few minutes it starts to get annoying and tiring on the eyes.

Bye for now,
Skybuck.

> Try tpm.msc inside your virtual machine.

Tried it.

> Does it say you have a TPM present ?

Yes it takes a while to load, multiple copies were loaded because I clicked so many times.

> Now install the VMWare Tools.
>
> Use tpm.msc panel again. Does it
> say there is a TPM now ?

Yes, I only checked after I installed VMWare tools.

I may check later on the other VM

Why does TPM interest you so much ?

The version was 2.something.
> I don't know all the details, but I recommend for a Win11
> install that you inspect the hardware facilities for flaws.
> A missing TPM would be one of them. tpm.msc can help you
> determine there is a VMWare software TPM or not. Fortunately,
> VMWare does not do passthru for its TPM. It is possible when
> VirtualBox releases their TPM support, it will be a passthru
> version (not software, will depend on motherboard TPM). In
> such a case then, VirtualBox might not be as good, on the
> TPM topic.

I dont see how a missing TPM would be graphics or font issue related ! Sometimes you weird Paul ! =D

Bye for now,
Skybuck

On 11/4/2021 2:32 PM, skybuck2000 wrote:

> I dont see how a missing TPM would be graphics or font issue related ! Sometimes you weird Paul ! =D

The reason I insist on this, is Microsoft cannot "turn down
updates" to your install, if you follow the rules. That's
what all this care and attention to detail is for. So
the Windows 11 you install, *lasts*.

That's what I noticed when I tested. It looked like a good
platform for a VM that would be sticking around.

VMWare seems to have a bit of trouble resizing the frame
around the desktop window, and if you thought the window was
running 1024x768, instead it is running at a weird value
close to those numbers. It has trouble precisely hitting
the required value. This can mess up the fonts.

If you can get Windows to cause the VMWare frame to adjust
itself, that increases the odds of getting a precise screen
setting. If instead you grab a corner of the VMWare window
and start pulling on it... you're doomed to a messy screen.
Use the Windows Display Resolution setting to try to get
VMWare to behave itself.

Installing the Additions that a hosting software comes with,
is intended to put a lame but operational driver in place.
And that may help with the appearance of the screen. You
don't really want to be running the Microsoft Basic Display Adapter
driver for the next five years. That would suck. The resolution
setting on that is jammed.

Paul

22 november 2021:

Yesterday I was in the virtual windows 11 again and trying to optimize performance a bit.

I discovered these performance settings and turned everything off, like font smoothing and shadows under fonts... that can't of thing.

Related to themes/visuals, I think I found it via right click start button, and then settings, or systems, and advanced settings and then peformance settings or something.

After clicking "optimize for performane".. everything was turned off and I NOTICED:

The TEXT/FONTS became much SHARPER/CRISPIER so this may HELP to avoid shaddyness and vagueness/anti-aliased look.

Thought it was worth mentioning it here.

I am considering installing Windows 11 to a USB drive, even though USB port 2.0 is slow and would make windows loading slow at least the CPU should run it faster because it's not in VMWare anymore...

However this laptop most likely does not have TPM 2.0 or any TPM ? very maybe TPM 1.0.

So then I would need a work around for TPM issue...

Not sure what I would run into...

Installing Windows 11 on machine without TPM ? Sounds hard, then again maybe not... I have seen some regedit work arounds.

I was not too impressed with Delphi 10.4 when it comes to GIT...

Akward usage, have to use pop-up menu and then click git and then click commit.

3 clicks at least... and then all it does is git add . and git commit.

Hmmm two little commands done automatic... mhoaw.. maybe not worth the trouble ! =D

But then at least I would have a good working Delphi IDE and maybe I can test windows 11 so more... not sure if I want too.

Another thing on my mind is the broken 3D chip... not sure if the installation of windows 11 will work with a broken 3D chip.

That would be an interesting TEST though.

But that reminds me... first I wanted to try and see if there is a special graphics driver for this build in INTEL GPU into the CPU...

Maybe that will give back some 3D possibilities like running 3D games again or at least get some visuals instead of just black screen in some games.

Bye for now,
Skybuck.