![]() ![]() Access privileges for HYDRUS users (standard users) are discussed below. The HYDRUS installation and activation requires administrator privileges. Here we call “Server” the computer that shares the disk or directory where HYDRUS is installed. It doesn't matter which Windows operating system is on the server or on client computers, and it also does not matter if your network is "peer-to-peer" or if there is a Windows server. Let's assume you have a Windows network, as in the Figure below, and you want to install and activate HYDRUS on 20 computers (Client_01, …, Client_20). HYDRUS program files (Hydrus3D.exe and other DLLs) may not be located on a local disk. ![]() The HYDRUS network license requires that HYDRUS must be started from a network drive, i.e. 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.HYDRUS Network Installation and Activation If this works for you, that narrows down the problem. 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. 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. I believe this is ultimately because of Qt wanting to be a non-console (windowed) program, and the debug normally working with console output. 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 |