Saturday, January 10, 2026

Install Windows 11 on ProxMox

This is a possible method to install Windows11 onto ProxMox.  

It is using a bootable USB key from the Microsoft site, mounted onto the ProxMox server, and then the guest VM is built from that.

  1. Download the Windows 11 ISO Download Windows 11 (search for "Windows 11 Media Creation Tool")

    Create a bootable Image USB stick.  You can use this link on this site as a reference how to mount it in Proxmox

  2. Download VirtIO Drivers ISO  VirtIO Drivers This link is from the Wikipedia page 
  3. Upload the VirtIO iso to ProxMax repository.
  4. In Proxmox, select Create VM to start creating a new virtual machine.
  5. Assign a VM ID and Name, then click Next.



  6. Under GUEST OS, select the uploaded Windows 11 ISO
  7. Set the TYPE to Microsoft Windows.  At time of writing the version was 11/2022/2025.
  8. Select "Add Additional Drive for VIrtIO drivers"
  9. Select the ISO image of the virtio iso.
  10. Click Next



  11. Select: QEMU Agent.
  12. Set BIOS to OVMF (UEFI)
  13. Select "ADD TPM" and set TP storage
  14. Select q35 for machine
  15. Set an EFI Storage location



    In the Disks section: 
  16. Set the disk size to at least 64GB. 
  17. Set Cache to Write back 
  18. Select Discard option (for reclaiming unused storage space on thin-provisioned storage).



  19. In this example show below, 2 sockets and 2 cores have been configured. 
    Everything else in this screen shot were default settings.



  20. Assign ram.  In this example, 8 Gig has been assigned.



  21. The networking was left at their default settings



  22. Confirm everything is right and click "FINISH"


  23. Start the VM and open the console to begin the Windows 11 installation.



  24. You'll be prompted to press a key during the boot for windows to start the installation.



  25. Go through the installation process of windows, 



  26. Follow the Windows installer steps until you reach the Custom (advanced) installation type. At time of writing the screen to watch for is the one below.
  27. Click Load driver 



  28. Click BROWSE and go to the drive that has the ISO "virtio-win-0.1.285.iso" mounted.



  29. Browse to \amd64\w11 and select "Red Hat VirtIO SCSI pass-through controller"
  30. Select "INSTALL"



  31. After installation completes successfully you will be brought back to this screen.
    In my example, after loading those drivers I could pick the local storage where I needed to install the Guest OS onto.
  32. Select "LOAD DRIVER" again.



  33. Browse to \NetKVM\w11\amd64 and install the "Red Hat VirtIO Ethernet Adapter"



  34. Select "LOAD DRIVER" again
  35. Browse to \balloon\w11\amd64 and install the "VirtIO Balloon Driver



  36. After loading the drivers, select the drive to install Windows on and continue with the Windows installation.
  37. Once Windows is installed, install the QEMU Guest Agent from the VirtIO ISO (guest-agent\qemu-ga-x86_64.msi) to fix mouse pointer issues and enable advanced features.
  38. Install all remaining drivers using the virtio-win-gt-x64.msi file on the VirtIO ISO. Restart the VM after installation.
  39. Complete the Windows 11 setup by configuring regional settings, user accounts, and privacy preferences.
  40. Verify that all drivers are installed in Device Manager.

Friday, January 9, 2026

Install a guest using a bootable USB key with ProxMox

Create a guest VM in Proxmox using a bootable USB key

  1. Plug in your key into your ProxMax Server

  2. Click on the "HARDWARE" section in your Windows guest summary and click on ADD



  3. Select USB DEVICE


  4. Select "Use USB port" -> Passthrough a full port -> then select your device


    You should see your device in the hardware list

  5. "power on" your virtual guest and you should be good to go with installation.

Some new OS installations you many need to make the USB key boot first, so if Under summary, go to OPTIONS - >BOOT ORDER

Set the USB key to boot first and press OK

Monday, January 5, 2026

Configure an XTOUCH with an X32

To configure the X-Touch to control the X32 Rack mixer, follow these steps:

  1. Connect the X-Touch and the X32 Rack to your network. (Assuming DHCP enabled on network)

  2. Power up your x32

  3. Under "SETUP -> REMOTE" make sure "X-Touch over Ethernet" is check boxed

  4. With the X-Touch powered OFF, hold down "SETUP" button on Input 1 and then turn on the unit.

  5. On Fader 1, set the MODE in the screen to "XCTL"

  6. On Fader 2, set the mode to "NETWORK"

  7. On Fader 3, set the mode to "DHCP"

  8. An IP address should show up after 5-10 seconds.

  9. Select "SCAN" on fader 8.  (this will search for an x32 on the network)

  10. In a couple of seconds your Xtouch should light right up with all the settings that are in the X32 reflected on its surface.


Saturday, January 3, 2026

Setup a fixture in QLC+

 1>  Set your DMX adapter as an OUTPUT in the Input/Output tab

2>  Add your fixture.  

If you have to create your own, use the fixture definition editor that comes with QLC+.  

The Slimline 9Q8 definition is available on the QLC community forum page.  But this process will be similar to any fixture.




3> Create a basic scene for your fixture. 
 In this example below, we create a Scene called "RED" which, when activated will make the fixture go red when a button is pressed.

If you have the DMX adapter selected properly, your light connected with the matching DMX values, this step SHOULD trigger your light to respond to the changes as you move these faders.


4>  Assign a button to the scene you created.


5>  Go into "OPERATE" mode (pressing the green arrow) and then press the button you created in step 4 should make the light go red.



Tuesday, December 23, 2025

OBS Hotkey Buttons

 This is a program that I wrote to give me 9 buttons that, upon selection, would run a batch file.
You can use this for most anything, I use it in OBS to trigger camera recalls.

Here is the link


https://drive.google.com/drive/folders/1Ykz7O9Jtv8FseBUAVkGHXUBMF83hNtoo?usp=sharing


This is the application.


Put it in its own folder, and run the app.  It will create a few files:


It will create a .CONF file and it will create 9 test .bat files.


You can customize each button name

You can change the title of the window itself

You can customize the color of the background and the font size.


The Batch files are test and simply echo "This is a test" for 5 seconds.

If you don't want to use these, just delete them.  But the program itself, each button looks for a file name called "preset1.bat" or "preset2.bat", the number reflecting the button being pressed.


I use this in OBS to trigger events.  You can use "Window Dock" plugin to dock these right into the OBS screen.


Friday, December 19, 2025

Windows Route add and delete


ADD syntax:

route add LOCALIP mask SUBNET GATEWAY

EXAMPLE
route add 141.196.0.0 mask 255.255.0.0 192.168.129.248


DELETE syntax:

route delete IP

EXAMPLE;
route delete 141.196.0.0


Saturday, December 13, 2025

Send VISCA commands using windows batch file

Have a situation where I want to control some FOMAKO cameras using VISCA, but from a Windows command prompt.  These commands for VISCA are HEX values which are sent.

You'll need two programs

1:  NCAT  (this will send the actual HEX commands)

https://nmap.org/dist/nmap-7.98-setup.exe

2:  XXD   (This tool will translate HEX commands)

https://sourceforge.net/projects/xxd-for-windows/

Download and install these.

From a simplicity sake, drop XXD into a folder that will contain your batch files.  You can add it to your system path, there are lots of online tutorials already

The command syntax is as follows:

echo 'HEX VALUE' | xxd -r -p | ncat CAMERA_IP VISCA_PORT

So the example below will send the HEX to the camera at 192.168.0.11 port 52381 and change it to recall a set point #3 (substitute 03 in bold for 01 or 02 or whatever preset value you want to recall.

echo '8101043f0203ff' | xxd -r -p | ncat 192.168.0.11 52381
I incorporated it a batch file because I wanted to send some other commands.
This batch file example send command from one computer to another computer running OBS. 
So the first computer runs a .bat file and it looks like this:

echo '8101043f0203ff' | xxd -r -p | ncat 192.168.0.11 52381

timeout /T 3 /NOBREAK > NUL

C:\OBSCommand\OBSCommand.exe /server=192.168.0.10:4455 /password="password01" /scene="Slide1" /delay=1
So the above syntax contained in a BAT file to do the following:

Command camera @ 192.168.0.11 to move to Preset #3
Wait 3 seconds 
Sends a WebSocket command to OBS to change the scene called "Slide1".

Here are my camera network settings, just in case you run into issues with your camera, to help troubleshooting.