u/anotherworldcomputer

I've made a Virtual Console that works for my setup, but is there a way to make it appear in fullscreen mode without the window sliders and extra controls on the side for a cleaner look?

Zooming in/out only changes the magnification, clicking the Actions/FullScreen Mode only removes the Windows title bar, but the up/down and left/right sliders still appear in the bottom and right side of the workspace.

Thanks in advance.

My machine has a backlight keyboard, I can see the sensor next to the capslock/numlock LED above the keyboard.

I've downloaded the Vaio Control Center software and it SHOULD have the keyboard option to turn it on or off, but I can't see it in the software:

https://preview.redd.it/gfu3cswohgnh1.png?width=774&format=png&auto=webp&s=e789d9d7cf7de8432e99a89fb7041b1a819dab87

The software is supposed to look like this according to things I see on the internet:

https://preview.redd.it/9mnd1swshgnh1.png?width=350&format=png&auto=webp&s=3645f8ac09752d01307e025fe0e31c17ca3622df

Is there a reason for this? Does anyone have a link to either more up-to-date software or drivers that might fix the problem? Thanks in advance!

edit: Picture added.

https://preview.redd.it/tc60t1uf3inh1.jpg?width=4592&format=pjpg&auto=webp&s=d4ff48f4b51efe20fe46e891b3a205cbfab3a554

Hi, I'm new to the DMX scene so I have some questions about the controllers.

I have a particular moving head lighting fixture that I can't get working with my Chauvet 4.

This fixture has 7 channel or 15 channel modes. but I'm really only interested in turning it on and off remotely rather than individual colours, motors etc.

In 7 Channel Mode:

Channel	Function	Value	Instruction
1	Motor 1 Route	0-255	0-135 degrees
2	Motor 2 Route	0-255	0-135 degrees
3	Sum Dimmer	0-255	0-100%
4	Strobe	0-255	0-100%
5	Effect	0-255	No Effect to 1-25
6	Effect Speed	0-255	Slow - Fast
7	Reset	241-250	5 Seconds To Reset

Currently I can get the heads to move only, the dimmer on CH3 does nothing as I'm guessing there is no effect on CH5 yet. So if I want to access Channel 5 in order make it light up, I'm going to need a 5th slider yes? Will I need to upgrade to a minimum Obey 6 or 10?

Thanks!

Putting this solution out there as it was a pain for me to figure out it and get it working properly. If you are receiving the above error. It could mean multiple things. Do the recommended troubleshooting 1st before moving to this fix. (google search for bootrec fixes, start up repair etc...)

This is the actual fix which involves replacing the EFI partitions GUID to the correct one that Windows can see and know where is the boot EFI records are.

1. MBR vs GPT Partitions:

First thing to do is check if your boot records and disk is set to GPT. Open Disk Management, select the disk you are troubleshooting with, right click >Properties>Volumes. It should say "Partition Style GPT" if it does. Go ahead and move to Step# 5, if it says MBR continue through all steps in order.

>Notes:
A lot of newer systems dont even allow MBR anymore and/or UEFI bios with GPT\EFI partition booting. So if you ever cloned a system or recreated the EFI partition or running in MBR CMS\Mixed booting mode, this is most likely where your issues start and we need to convert it over.

2. Converting MBR to GPT:

Use a functional system with a USB Dock or Disk Enclosure and plug in the disk we are having issues with. (you can also use a Windows Recovery bootable iso, or a Recuse disk from programs like DiskGenius or Macrium Reflect) but for this we are assuming its plugged into a secondary functional system via a USB dock.

Now install Disk Genius. Open Disk Genius and select the disk we are working with (we will call this disk#5). Verify it states "Partition Table Style MBR"

Right click on Disk#5 and "Convert to GUID" This will convert the whole disk from MBR to GPT style.

Hit "Save All" to commit the changes and we are done here.

3. Fixing Boot Partition Files:

Now because the boot partition still has MBR files on it, it wont be bootable at this point. We need to delete the MBR partition, recreate it and copy over EFI files. This is how we are going to do it.

This can be done with CLI or Disk Management. I'm going to explain how to do it in Disk Management to make it simpler.

Open Disk Management, find Disk #5. Find the MBR partition (typically the "reserved unlabeled partition roughly round 100mb-500mb in size) and delete it. Make sure NOT to delete the partition that contains Windows and your data. Only the MBR\boot partition!

>Note: If you have multiple reserved partitions. Feel free to delete them all since we are recreating a fresh one now.

Now right click the unallocated space we just made, create new Fat32 partition, label it "EFI" and feel free to assign a drive letter. Here we are going to call it drive letter S:

4. Rebuilding EFI Boot Records:

Next is to rebuild/copy EFI files from the existing installation to EFI partition using this CMD command:

bcdboot J:\Windows /s S: /f UEFI

>Note: This assumes your Windows Partition on disk we are working on is drive Letter J: and the EFI Partition is S: Replace with your drive letters if need be.

Done. Now MBR has been converted to GPT. This should allow you to boot back into Windows but you will still receiving error 8x80070003 - 0x40008 when trying to apply the update/upgrade to Windows 11, so continue with step 5 before reinstalling the disk into your other system.

5. Now continue to resolve 8x80070003 - 0x40008 error:

Go back into DiskPart

Select Disk 5 (disk with OS we are working on)
Select Part 1 (newly recreated EFI partition)

Run the following command:

set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b override

This changes the EFI partition GUID to something that is findable by Windows subsystems.

Install the disk back into the original PC. It should now boot properly and allow for you to continue with the upgrade/update that was previously failing!

Important Notes:

• Before doing any of this make sure you have a VALID BACKUP of your disk so you can revert back if need be. I personally cloned my original hard drive and did this all on the cloned disk, than once it was working I replaced my original disk with the cloned one. This makes it way easier to deal with instead of having to restore from a backup if things fail.

• The reason we HAVE TO convert to GPT is because the command "set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b override" only works with GPT style disks. If its not a GPT style disk you will run into an execution error when you try to run the command.

• Thirdly yes this GUID fix is the resolution to this issue. Why does it work? Well it converts the existing GUID into one that Windows understands by default and can easily find. Its mostly used for things like Firmware and Windows Upgrades. This explains why your old disk may still be "bootable" but not "upgradable". As the boot process doesnt really care about GUIDs but for upgrades and firmware do care!

• If you can't boot after doing this. Make sure your bios boot is changed from MBR to GPT mode. AKA Legacy boot to UEFI.

And last but not least. This whole process assumes you are not dual booting on the disk we are working on. That is a process might be different and you may have more reserved partitions that if deleted could break your dual booting. So be careful with that and know what partitions you are deleting before you delete them!