I am distributing my software by wrapping the application exe in NSIS installation wizard. I use HM NIS edit software for editing the NSIS scripts. I recently got my editor frozen when I hovered on the default functions of NSIS like 'SetCompressor', 'BrandingText' etc. This is happening only in one system regardless of user. I tried to recreate the error but failed to do so.
The error occurred on the system with windows 7 professional OS, NSIS version 2.45, HM NIS edit version 2.0.3.
I re-installed the NSIS and HM NIS edit software but still the editor gets frozen when hovered. I searched on the internet about it but found no such error. I also compared the installed files against the installed files without error but found no difference. I used beyond compare tool to compare the file. So by this I concluded that there is no file corruption.
Please help me to solve this error.
This sounds like a bug and should be reported on their bug tracker. HM NIS Edit has not been updated in over 10 years so I'm not sure if I would hold my breath waiting for a fix.
You are also using a old NSIS version! At least update to the latest v2.x. This is probably not going to fix your issue though.
The two most likely reasons for freezing are:
Bug while parsing the syntax file. Rather unlikely since it works on other systems but you could try to update the files.
Bug while displaying the tooltip. Maybe the problematic system is using a special Visual Style/Theme? Non-standard visual settings relating to shadow or animation?
Related
During installation I get "The feature you are trying to use is on a network resource that is unavailable" and prompt to specify some path to vc_runtimeMinimum_x64.msi. After providing some path to required file I get error states that this file doesn't match required version Minimum Runtime 14.14.26405.
I finally found the solution reading this question: Install vcredist_x64 with VS2017 installer project
I realized that specific VC_Redist.x64.exe files could be downloaded by links like https://aka.ms/vs/15/release/26405.00/VC_Redist.x64.exe, where 26405.00 is exactly the version I was required to fix. Note, that you need version from error text after clicking OK, not from window title.
And the last point is that this exe must be executed from cmd with argument /repair to help me with this issue. Regular execution by double click made no effect.
I found the solution elsewhere. It said to
Fix problems that block programs from being installed or removed
https://support.microsoft.com/en-us/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed
download troubleshooter button on the link.
Run it - choose option - have problem with installing - it lists programs - choose the missing / problematic visual c++ runtimes in the list
it will run and get fixed.
Repeat for each visual c++ you having problems with. I ran the program multiple times.
I have to thank this comment section for helping me with this problem, since I have not been able to work more efficently with my school, since I din't know what and if a single file somewhere deep down in the computer had to be deleted for this program to work.
I have tried install llvm 7.0.1 on Windows 10.
But the installer has text corruption like below.
It make so harder to install.
How do I fix it?
I using Windows 10 1809, chcp is 65001.
I using Japanese.
I have enabled "Use Unicode UTF-8 for worldwide language support" in Region settings".
Is this change cause of the error?
But A installer of other application does not be text curruption.
Update:
The Picture of installer with compatibility mode (Windows XP SP3)
That LLVM installer is not a Unicode NSIS installer. The LLVM team can fix it by adding Unicode True to their NSIS script.
That LLVM installer looks like it supports multiple languages (I could not find it's source, it might be using CMake/Ninja) and NSIS does try to guess the correct language but this is based on the return value of GetUserDefaultUILanguage() and not the active codepage.
I could not replicate your issue on build 18290 (after changing to UTF-8 and rebooting I verified that GetACP() returns 65001) but this is probably because my system is detected as English by NSIS.
Based on the (N) in your Next button in your screenshot I'm going to guess that your UI language is detected as Chinese or Japanese?
Without more information about your system it is hard to guess if this is a bug in NSIS or Windows. NSIS is a relatively normal application and does not call MultiByteToWideChar on its interface strings (IIRC).
Edit:
By forcing a installer to pick Japanese I can replicate your issue. The solution for this issue is to switch your "language for non-Unicode programs" back to Japanese if you wish to install this application using Japanese as the display language. Another solution you can try is to set the locale for a single application. AppLocale was Microsoft's solution to this but it is not supported on Windows 10 but there are other alternatives out there.
When building a NSIS installer without Unicode support the program stores the text internally as raw bytes encoded with the codepage of the specific language. At run time it uses functions like SetWindowTextA to set the text of UI elements. This is how non-Unicode applications have worked since the dawn of time on Windows. All non-Unicode programs that display text outside the ASCII range will have the same issue unless they have been specifically written to support UTF-8 as the active codepage (which is unlikely since it is a new feature). This feature is only useful for console applications and ported POSIX applications that assume that the narrow string is UTF-8 encoded.
Too long for a comment.
UPDATE: Looking at this a little, I am wondering if the problem is a font corruption issue. There is a description of rebuilding the font cache here: http://www.trishtech.com/2013/11/rebuild-fonts-cache-windows-8/. I think you must install a good copy of the font file first though? You do that by copying the font files into the Fonts folders I believe. I will check with Anders what font NSIS uses.
Similar issue with an MSI file: Windows Installer ugly font rendering.
Compatibility Mode: Pretty sure that UTF8-setting would cause it. I don't think it would work, but the first thing I would try would be to run the executable in compatibility mode.
Locate the setup.exe in question.
Right click the EXE, hold right mouse button down, now drag to empty desktop area and release mouse button. Click "Create Shortcut Here".
Right click Shortcut => Properties => Compatibilty tab.
Try various combinations of "Run program in compatibility mode for..."
I would try "Windows XP" highest service pack first. Click OK when done.
Now double click the shortcut to launch the executable and see what happens.
After an install in VS2015 (intel mkl library with vs integration) the c/c++ editor fails to show anything except the tab on top. No window, no text, nothing.
I dug a bit deeper: a .txt file displays fine, .cs as well. When I set in options that filetype .txt needs editing in C/C++ editor, .txt stopped displaying too.
I have compared every option in tools->options, including the environment options, to a normal working rig, found nothing.
Resetting to default options did not help, nor did changing the color scheme.
Removed the Intel directory from common7/IDE/extensions, no improvement.
I do not know where more secrets are kept, tried a registry search, but found no clues. Everything appears to match, up to the dll for language specialization in vxpackages.
Anyone, before I try to repair the installation?
Thanks in advance,
Jan
Edit: I got the editor back on track by disabling Productivity Power Tools 2015. This took me half a day. Any connection to the Intel install is doubtful!
I have a system,written on PyQt4. It is mostly developed and debug under linux (ubuntu) systems, in Eric IDE, and everything works fine. Last task was to create a nested editor for a table cell. So, i did it and it also looks nice in ubuntu. I also ran it under Windows 7 x64, and the behavior was the same.
However, after making executable file with cx_Freeze in Windows 2000 (it's weird, but this environment was configured before me), the editors behavior became unexpected. After opening Editor it's first cell have 'role == Qt.EditRole', and it's almost impossible to commit any changes there without closing the whole Editor. Another issue is about "OK" button - it closes the Editor window, but doesn't commit any changes in it also, and you cannot call it again without changing the active cell (but maybe i just forgot to emit some signals here, so it's not the main bug here).
So my question - where should i look to find the reason for these problems. I'm new to qt, and maybe it is normal behavior and just my fault in code? Or the reason is in different environments (python 2.7, latest pyqt vs python 2.6 and some older pyqt). Or it is the influence of cx_Freeze... Maybe some other directions?
Sorry for long post and my English :)
Hope to get any answers soon.
I think there's a chance that Qt or PyQt on windows 2000 server is outdated or broken.
So If possible, bring cx_freeze related code to your local computer and test it out.
If it fixes the problem, you can upgrade or reinstall Qt on windows 2000 server.
Environment: xcode 3.2.1, document-based core-data application.
I have a document-based cocoa app which uses core data. I have made multiple versions of the data model Xcode shows a xcdatamodeld directory with multiple xcdatamodels (versions) that I made over time. (I also have the appropriate mapping models). All works fine, but now when I want to create a new version, xcode refuses to show the new xcdatamodel. The file is actually created; I can see it in the finder if I go into the xcdatamodeld package.
Has anyone run into this behaviour? Is there a fix? Perhaps my xcodeproj file is corrupted somehow?
Thanks,
Martin
I'll answer my own question. Believe it or not, this anomalous behaviour was caused by a bug in a Logitech scripting addition which was tickled by the fact that I am using Default Folder X!
Weird, but true.
All better now.