Closed yhz114514 closed 1 day ago
I'm sorry, I don't have a Windows device to test. All four of my computers are Macs.
I've encountered this problem a few times.
This problem is likely due to the port required by DeepLX is somehow not released properly.
For windows, simply use powershell/cmd
to run netstat -ano | findstr :1188
(default port) to see any process taking that port, and try to terminate it.
If this problem persists, simply log out and back in or restart the computer.
In addition, sometimes some error will be shown in the command line window. You can use powershell command ./deeplx_windows_amd64.exe; Read-Host
in the program directory to prevent window from automatically closing to inspect it.
For most cases: then
done.
好的,感谢指导
Sometimes it cannot be started correctly under the Windows operating system. The command line window of the program will close itself at the moment of startup. This problem is unstable and sometimes does not trigger, but it causes a lot of inconvenience.