Zugg Software :: View topic

Wanderer Joined: 05 Sep 2008 Posts: 55

it seems that windows is up to it's old tricks...my laptop just went through a forced updated resulting in a broken #LOG directory...an there isn't even an enrty in the windows update update history :P

i have been using:

#LOG %concat("C:\Users\dudeman\Documents\My Games\CMUD\bob\logs/bob_", %time("yy-mm-dd"), ".txt"), and it has been logging fine for years.

the new the directory has become

C:\Users\dudeman\OneDrive\Documents\My Games\CMUD\bob\logs

for some reason when i try to ues that directory the space between My and Games, cmud treats is like a line break and i get:

ERROR creating log: C:\Users\dudeman\Documents\My
Games\CMUD\bob\logs/bob_25-10-13.txt

my temporary solution has been to move the log directory to a place with no name break in it, as i don't want to break anything else that is still workin by changing My Games to MyGames...but if anyone has any insights i would appreciate them. also...this sorta feels like a junction point of some sort...because the following use of #PLAY still works...

#play %concat("C:\Users\dudeman\Documents\My Games\CMUD\bob\sounds\chord.wav")

Posted: Mon Oct 13, 2025 6:38 pm

Are you using the same syntax? Cause with %concat it is treating the full path as a string, which is why the space gets preserved

Wanderer Joined: 05 Sep 2008 Posts: 55

i am using the exact same syntax. the error only occured after the OneDrive folder was added...

i moved all the folders out of the overdrive folder and back to their prior locations and that unbroke things. i still don't understand why a space would be treated as a line break when the direction goes to one place and then work fine when it is another.

Posted: Thu Oct 16, 2025 12:02 pm

It might be a permissions issue, it might not have access to write to that folder.
Did you ever run CMUD as admin?