Author Topic: Editing local qb.conf files  (Read 3725 times)


  • Full Member
  • ***
  • Posts: 10
Editing local qb.conf files
« on: January 31, 2013, 06:15:39 PM »
Ok, so I don't know if I'm crazy, missing something, or otherwise, but when I attempt to modify the qb.conf file located here: C:\ProgramData\Pfx\Qube (I'm on Windows 7), the qb.conf file won't save properly.

All I'm trying to do is add a group to my local workstation (as a test so I can add groups to the other machines on our render farm), by modifying the qb.conf file in a simple text editor (I'm using Notepad). Here is what I am changing in the qb.conf file:

# (OPTIONAL) worker groups

#worker_groups =

Changing to:

# (OPTIONAL) worker groups
worker_groups = Light_Render

When I finished my changes, I attempt to save over the existing qb.conf file. Because I opened this in Notepad, it obviously wanted me to save it as a .txt right away, so I changed the "Save as type:" from .txt to All Files, leaving the file name as qb.conf.

However, that created an additional qb.conf that was actually a txt file. The original qb.conf remained unchanged, still in CONF format.

This may seem like a simple problem, but I can't figure out how to make this work. The qb.conf is not set to "read only". I tried turning off the qubeworker service before doing this. The administrative guide does not give instructions on how to make sure that the qb.conf modifies correctly, nor does it tell me if there is a specific program I must open for this to work. I have been unable to find instructions for how to do this anywhere else.

Please help as soon as possible.


  • Administrator
  • *****
  • Posts: 493
Re: Editing local qb.conf files
« Reply #1 on: February 01, 2013, 01:25:56 AM »
You need to be a Windows administrator to overwrite the qb.conf file.  Windows security does some funny things sometimes, and files under C:\ProgramData seem to receive special restrictive handling from the Windows security policy.

The most certain way to do this is to open a cmd prompt with "Run as Administrator", and then launch notepad from there.