System Config

[tom]

C:\Users\Spa Pool\AppData\Roaming>set CQC
CQC_DATADIR=C:\Program Files (x86)\CQC\CQCData
cqc_password=9630
CQC_SYSTEMID=0A25184839C4D659-E089B5F964AD2BCA
cqc_username=Admin

C:\Users\Spa Pool\AppData\Roaming>

[Dean Roddey]

OK, so this error:

Code:

01/10 10:15:35-Officecomputer, CQCServer, CQCDrv_LitesThread9
{
  CIDLib, CIDLib_FileBase.cpp.352, Failed/Cannot Do, Error: 1414/625/3
  Could not open the file, name=C:\Program Files (x86)\CQC\CQCData\MacroFileRoot\Drivers\RadioRA2\Lites.Cfg
  The system cannot find the path specified.
  <CQCServer> CIDLib_BinaryFileStream.cpp - 355
  <CQCServer> CIDMacroEng_OutputStreamClasses.cpp - 1262
}

Is happening when the driver tries to save the file. It's operating system error 3, which is path not found. That means it couldn't write the file because the path that it's trying to write to doesn't exist. Not that the file doesn't exist, which wouldn't matter, because it's trying to create it, it's that the path the file is being written to doesn't. So, if you look in:

C:\Program Files (x86)\CQC\CQCData\MacroFileRoot\

is there a Drivers subdirectory? And inside that is there a RadioRA2 directory? If not, create them, flush the logs and try the above again.

I'm guessing that's it in this case. Originally you had to create the file by hand, so you had to have created those directories yourself. When I added the client side driver, I didn't add the code to make sure those paths were created. For all existing users, they would have already had the file there that they created themselves, so this wouldn't have affected them, and that's why I didn't catch it either on my system. The directories already existed.

So, for the moment just create them and it should work. But, after that, you shouldn't have any issues, at least on that machine. If you move it somewhere else, you'll have to make sure they exist there as well, at least until the next drop. I'll update the driver for the next drop to make sure those paths are created.

[Dean Roddey]

A failure to store the file was also not being correctly propagated back to the client side driver, so it didn't warn you when it failed to store the info. That's been fixed as well. That also let the AI think that the changes had been successfully stored, so any subsequent save wouldn't do anything until you made a change. So even if you went and created the directory after that and saved again, it wouldn't save it if there were now changes. So now if it fails you'll get an error and you'll still have the outstanding changes to save (and a warning when you try to close the tab to let you know that.)

Oh well, it's a brand new client side driver scheme, so these quirks are not unexpected I guess.

[Dean Roddey]

Did creating the directory make it happy?

[tom]

Haven't had a chance to mess with it yet, should be able to this weekend.
Thanks

[Dean Roddey]

I've already posted a new version (5.2.9) in which the driver correctly creates the directories if they don't exist.