Skip to content

After all these years working on Linux in the server environment, I was finally able to configure the console resolution upon booting from an auto-size screen to a custom-size screen. It is simply by adding two lines of GRUB environment values to /etc/default/grub and altering a variable called GRUB_COMMAND_LINUX to include at the end vga=0x0342.


As you can see, line 2 and line 3 were added as well as line 8 was altered to include vga=0x0342 or vga=ask. If you wish to have the system display the availability of screen size resolution upon reboot, you should say vga=ask, otherwise, vga=0x0342 will work upon reboot. So, our next phase will be to compile a new grub boot. on Vmware Workstation on windows v16.x.x and VMFusion on Mac, they both will take this configuration since I've tested on both systems.

As root:

sudo su -
grub2-mkconfig -o /boot/grub2/grub.cfg

now, Your linux boot loader Framebuffer should be larger. In a matter of fact, it should now be with a resolution of 1152 by 864 with 24 bit.

Continuing after we've compiled Python on Windows 11 from source code, we would then need to package this using the MSIX package manager tool to build and installer. Thankfully, the Python source code will include such tools for us to build our custom package by using the build script provided to us in the following location.

Python Package Build Location

We can then Follow some basic instructions to compile additional source code and find out how to build this installer package by executing the build.bat file.

Package builder Script

Now we have learned how to use this build.bat file, we can issue this command along with three parameters to build this deliverable package for the masses.

Building Documentations, where there might be some warnings or errors

Building Documentations.

Done building Package w/Warning

The Final Phrase will be to check whether we have 100% completed this package Building Phrase using this build.bat tool provided to us from

the final Image will be the location for us to find this Python Installer package. It is not the Installer package from since their version is digitally signed and verified.

Our Custom version of Python v3.9.11-7750


I was extremely curious about how to build a version of Python 3.9.x {x64/x86} on a Windows 10/11 machine for the longest time. Finally, I've found an hour to learn how to pursue this system engineering topic (System build process aka Build Engineering) on compiling my unique version of Python 3.9.x on windows.

Thanks to All the Opensource Contributors on writing scripts to automate most of this process, I was able to follow instructions when building a version of Python 3.9.x.

First, one must install the following tools from Microsoft: Visual Studio 2019.

Visual Studio

We then would require the necessary packages in our VS 2019.

VS Packages

After installing Additional Packages for VS 2019, we would now need to use the CMD Prompt to generate some additional files after downloading the tgz compressed file python v.3.9.10 source code from After decompressing this tarball file, we now have Python-3.9.10 Directory, where all the files have been extruded from this tarball.

compiling AMD x64 bit version

There are options when comes to compiling, I took the recommended approach. It is likely not to follow recommended instructions when compiling initially, but on generating a debug version first to test a custom compiled version of Python v3.9.10 is appropriate. The goal was to test whether SSL was included upon compiling.

build.bat -e -d -p x64
build.bat -e -d -p x86
build.bat -e -p x86
build.bat -e -p x64

As shown above, one can certainly build the debug version to test then build the actual non-debug version of Python.

Once the above process has been completed, we must then look for a file called pcbuild.sln to compile either the 32 or 64 bit version of our python software once we had executed the build.bat configuration file.

BInary python Debug

Once the final process has been completed, we can execute the python_d.exe file in our CMD prompt to see if it was compiled successfully. it is now working perfectly, we can then reconfigure the build.bat switch to remove the -d switch and recompiled a final product of python.exe.