Forum > Windows (32/64)
Lazarus IDE won't start on Windows 7 64bit
jstraarup:
Hello,
I have a couple of computers that cannot run the Lazarus IDE, or any executables build by Lazarus.
By cannot run, I mean: Nothing appears to be happening, when I run the program.
If I try to start the IDE, it just exits immediately, without anything happening on the screen. No errors, no nothing.
I have tried building an executable with Lazarus, and running it on 6 computers where it works perfectly - and on two machines, where nothing happens at all. All these computers have similar configurations, which confuses the matters even more.
I cannot see anything in "Event viewer", and it does not seem to be blocked by McAfee.
I guess these computers miss some dependencies, or the app is shut down by a security mechanism in my company.
Does anybody have a suggestion on how to proceed?
Are there any relevant log files, or switches I can turn on, to see what is happening?
All the machines run Windows 7 Enterprise 64 bit.
Thank you in advance.
Handoko:
Hello jstraarup,
Welcome to the forum.
Try:
- (Temporary) disable any antivirus and run Lazarus, can it start?
- Restart your computer to safe mode and run Lazarus, can it start?
- Make sure you computer is virus-free.
- What Lazarus version did you use? Try other versions, maybe 32-bit.
- Make sure the checksum of your Lazarus installer never changed. If it changed, your computer may already infected by virus.
Read more:
http://forum.lazarus.freepascal.org/index.php/topic,37244.msg249767.html#msg249767
wp:
* Did you install additional components on these failing PCs? Possible candidates could be the packages sqlitelaz and/or sqlite3laz if the sqlite(3) dlls are not found (or not 64bit in your case) - IIRC, I've seen a similar crash in this case. Also look for other packages requiring external dlls. Find the installed packages in "packagefiles.xml" in the Lazarus profile folder (normally c:\users\<your name>\appdata\lazarus), or the folder specified as --pcp or --primary-config-file in the commandline parameters or in the file lazarus.cfg.
* Create a Lazarus log file, i.e. run Lazarus with the parameter "--debug-log=name_of_log_file.txt", and post the log file created.
* Copy the Lazarus.exe from a non-failing machine to a failing machine (of course, only after making a backup copy first). Does it crash now as well?
jstraarup:
Hi Handoko,
Thank you for the welcome, and thank very much for your quick reply :-)
Unfortunately, I cannot (even temporarily) disable antivirus. This part is outsourced, and out of my management.
Safe mode, might be possible to enter (it varies) - this is a good suggestion. I will try this, when one of the machines are available.
It is unlikely - but of cause not impossible - that the machines are infected with virus, as they have up-to-date antivirus.
And one of the machines where it didn't work, has been locked down since being imaged, without any admin privileges until recently where I removed it, in attempt to debug the problem.
I have also tried with fresh profiles.
I have tried both 32-bit and 64-bit, of the home build executables - but only the mixed package of the IDE.
I will try both individually, but I suspect that I will see the same result.
Regarding the checksum of the installer. I will check it out, but I'm 99.9% sure that it has not been modified.
Thanks again for your suggestions.
jstraarup:
Hi wp,
I have not installed any additional components on the failing PC's. I have just installed the Lazarus IDE (mixed 32/64bit), and no special configuration of any kind. There are installed other scientific applications, that might ship with different versions of sqlite for instance.
I will take look for packages requiring external DLLs. I think it is very likely that it tries to load wrong DLL, but I did not know about the packagefiles.xml file.
When I have access to a machine, I will also try to run it with the debug switch, and copy the exe from a good machine - to a bad machine.
Excellent suggestions. Thank you very much.
Navigation
[0] Message Index
[#] Next page