alucryd / oxyromon

Rusty ROM OrgaNizer
Other
111 stars 13 forks source link

Set ROM_DIRECTORY on Windows error #92

Closed Zombanana closed 3 months ago

Zombanana commented 11 months ago

Hi,

I don't know if I am just to stupid to set the ROM_DIRECTORY or if it's a bug. I am on Windows 11.

Setting the "ROM_DIRECTORY" with following command: oxyromon config -s ROM_DIRECTORY D:\Redump

results in

Creating "\\?\D:\Redump"

1 2

Is this a bug or I am to stupid? Sorry if this is my stupidness :/

Zombanana commented 11 months ago

The ROM_DIRECTORY Path works as expected, it seems to be just a display error. If you start the webserver and edit the path inside this, it shows the ROM_DIRECTORY Path also correctly. The Display Error is just listed from cmd.

My fault was that I thought oxyromon, would find my Roms immediatly, after I set the Rom Directory Path. But you still have to use the "import-roms" command.

After that everything went fine.

alucryd commented 11 months ago

Thanks for bringing this to my attention, will need to find why it displays wrong on Windows, shouldn't be too hard to fix.

alucryd commented 10 months ago

Hopefully this fixes the paths on Windows: https://github.com/alucryd/oxyromon/commit/ca24983a9afe4d84d9b44bab710244863ea300b1

Don't have a Windows install to test right now, will probably create a VM.

Zombanana commented 10 months ago

Hi,

after 0.17.0 is released, I can test it. I have Windows installed on my machine and report it back to you. By the way, the issue is just visual.

alucryd commented 6 months ago

@Zombanana Released 0.17.0 in november, did you have time to test it?

Zombanana commented 6 months ago

Hi alucryd,

Unfortunately I am right now in the process of building a new Unraid Server and to move all my drives / data from Windows to an Unraid array. At the moment I have no access to my data until it's moved to the Unraid server.

So that can take a while until I am ready :/

alucryd commented 6 months ago

No worries, please take your time.

alucryd commented 3 months ago

Going to close as I'm fairly sure the commit I linked above did fix the issue. Please reopen if that's not the case.