Marc Palaus

icon indicating a website link https://www.linkedin.com/in/marcpalaus/

icon location NYC icon location Data Scientist, Cognitive Neuroscientist.

Results 74 comments of Marc Palaus

Cannot launch non-steam games if filename has spaces in it

I use this command to start moonlight on the raspberry: `moonlight stream -720 -fps 30 192.168.1.121` This is the command used in Steam to launch the game: `"C:\Program Files\Dolphin\Dolphin.exe" /e...

Cannot launch non-steam games if filename has spaces in it

The same happens with any other path that includes spaces, not only Dolphin. For instance, if you try to launch a PS2 game using PCSX2. The thing is that the...

Stuck on "Waiting for upload to finish" if remote SSH storage is full

Hi, The upload speed is 600mbps and the download speed on the remote host is 300mbps, so I don't think it's a speed issue (testing another folder outside the almost-full...

Stuck on "Waiting for upload to finish" if remote SSH storage is full

Thanks. I tried that, but apparently my drive now is so full that I can't even create a folder (it has a few tens of free GB left, but it's...

[Bug]: Cannot Free up local space from small files (~1kB or less) in Windows

Still an issue in client 3.5.1 for Windows.

Massive slow down when NC tray icon is open

I can also confirm this behavior with the placeholders (virtual files) in my computer with Windows 10.

"File contains trailing spaces and could not be renamed, because a file with the same name already exists locally." on next sync after renaming folders on server.

bump

"File contains trailing spaces and could not be renamed, because a file with the same name already exists locally." on next sync after renaming folders on server.

bump

"File contains trailing spaces and could not be renamed, because a file with the same name already exists locally." on next sync after renaming folders on server.

This problem is still present in client 3.5.2

"File contains trailing spaces and could not be renamed, because a file with the same name already exists locally." on next sync after renaming folders on server.

The problem is still present in client 3.5.4