How does VESA BIOS change the analog information.

[Artlu]

Because the school's software detects whether the graphics card has the word VBox or virtual box.

Please tell me how to do it, thank you.

I know the software detects VBOX, and it detects the manufacturer of the graphics card, the driver name, whether it has VM and other text. I know to change the VBOX graphics card information, but I didn't find how to change it in the document, so I asked for help.

[socratis]

I'm not sure what the question is, but let me try... You have a piece of software that detects that it runs under a VM in VirtualBox and it refuses to run? Is that the problem?

And you want to find out which parts of the BIOS are responsible for that? And possibly change them? So that it passes the checks of the software?

If that's the case, I'm pretty sure that the developers of said software want to make absolutely sure that their "baby" doesn't run inside a VM. And that's one of the ways to do it. But 1) you'd have to build your own VirtualBox from scratch, 2) you don't know if it's the only check, and 3) if someone wants to make sure that their software doesn't run inside a VM, they can always, always tell, no matter what you do...

[Artlu]

I know the software detects VBOX, and it detects the manufacturer of the graphics card, the driver name, whether it has VM and other text. I know to change the VBOX graphics card information, but I didn't find how to change it in the document, so I asked for help.

[socratis]

but I didn't find how to change it in the document

What document are you referring to exactly?

[mpack]

Because the school's software detects whether the graphics card has the word VBox or virtual box.

I gather that you are trying to install software which refuses to install because it detects that it's a VM.

We can't help you with that, one reason being that it isn't possible.

Detecting the graphics card type is only one minor way of detecting a VM, it will not be the only method used by the software. And, even if you changed the graphics card type all you'd have then is a graphics card and no compatible drivers. Hardly a useful result.

[Artlu]

Detecting the graphics card type is only one minor way of detecting a VM, it will not be the only method used by the software. And, even if you changed the graphics card type all you'd have then is a graphics card and no compatible drivers. Hardly a useful result.

But if you do not modify the name of the video card, you will not be able to use the software. Because the VM graphics card is virtual, so the driver problem is basically not necessarily linked, in many cases the detection is not the driver name of the graphics card, but the content of the graphics card bios, because this is more difficult to solve.

[Artlu]

What document are you referring to exactly?

It's not a document. Instead, the name of the graphics card BIOS under the virtual box is changed, because the name of the motherboard BIOS and other modification documents, but did not find the graphics card. The graphics card is virtual, so it can be modified, but it doesn't know the method.

[socratis]

The graphics card is virtual, so it can be modified, but it doesn't know the method.

I already told you the way; build your own custom VirtualBox from the source code. There's no provision to change that from a command line or a preference.

But, you don't seem to be listening to what both mpack and myself are trying to tell you. It won't work 99.999%.

[Artlu]

Thank you. I think I understand.