![]() ![]() Version 5.20 (18 September 2017): Tabbed software selection and settings improved error handling fixed errors in Spanish and Italian localization added button to hash archive fixed broken UI at 125% system font size added Windows 10 builds 16267, 16278, 1628 (including developer tools) added Office 2016 for Mac builds 15.36.1, 15.37 and 15.38. Version 5.21 (20 September 2017): Improved error handling removed Windows 10 OEM/COEM. NET Framework 4.6.2 or newer, Internet Explorer 8 or newer ![]() Our new tool will make your life easier, and provides and interface to Microsoft TechBench to download original Windows images directly from Microsoft's server. This new tool allows an easy and comfortable way to download genuine Windows 7, 8.1 and 10, as well as Office 2007, 2010, 20 disk images (ISO) directly from Microsoft's servers.Įver since Microsoft pulled the Windows disk images from Digital River, hunting for untouched ISO files has been a pain. ![]()
0 Comments
![]() ![]() 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. ![]() |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |