![]() ![]() Since you are comfortable with running from python source, did you happen to already have python or C++ Qt already on your system? I have had a couple reports before about system-wide Qt environment variables sometimes upsetting hydrus's private Qt. If this works for you, that narrows down the problem. HYDRUS program files can be located on a local drive of the computer). HYDRUS should be installed on each computer, connected to the network, in the same way as on any other stand-alone computer (i.e. The installation package has about 50 MB. The network authorization of HYDRUS is controlled by NetHASP Hardware Key. Does it boot? Does it give you a different error? Different versions of pyinstaller work better or worse for certain unusual situations, such as running the program with a symlink. Downloading the Installation Program We recommend that you download and install the latest version of HYDRUS 1.xx. However, here is a different build, using an older version of Please try extracting and running that on your desktop or similar. There is supposed to now be a 'windowed' dialog hook to display the debug traceback, but I am only getting problems through it. Otherwise, go straight to 'server' or 'server.exe' or 'server.pyw' in your installation directory. ![]() If you installed in Windows, you can hit the shortcut in your start menu. If you have the client, you have the server. I believe this is ultimately because of Qt wanting to be a non-console (windowed) program, and the debug normally working with console output. start the server Since the server and client have so much common code, I package them together. Two debug modes fail to build, and another appeared to go ok, but then does not boot the exe correctly. Hmm, yeah, I did not have luck building different kinds of debug build for the client. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |