TOPIC:

Hello,

I am using CodeTyphon 2.40 on a Windows 7 Ultimate x64 machine.

After building the toolkit (CodeTyphon > Remove and Build All) without errors, only the 32-bit version of Lazarus works.
The 64-bit version does show it's splash screen but nothing else appears.

Is it possible to debug Lazarus64 initialization somehow, in order to discover why it cannot load?

Many thanks in advance.

Edit: Launching Lazarus64.exe directly from lazarus\bin64, displays the following error requester (the 32-bit version launches fine with the same method).

Please Sir
Try to rebuild Lazarus

Do you have administrator privileges ?
Please check your antivirus app

look and this thread

Thank you for your prompt reply.

sternas wrote: Please Sir
Try to rebuild Lazarus

I did several times.
On another Windows 7 x64 Ultimate PC the same Lazarus64 executable runs fine.

Do you have administrator privileges ?
Please check your antivirus app

Yes, UAC is turned off.

Probably it's something wrong with this Windows installation.

If this PC has previews Lazarus or FreePascal installation
try to remove them

Γειά σου Μάνο,

Frontier314 wrote: I am using CodeTyphon 2.40 on a Windows 7 Ultimate x64 machine.

Me too and it is working like a charm...

Frontier314 wrote: After building the toolkit (CodeTyphon > Remove and Build All) without errors, only the 32-bit version of Lazarus works.
The 64-bit version does show it's splash screen but nothing else appears.

Ok. First of all make sure you have UNINSTALLED any previous FreePascal or Lazarus installations. By that i mean possible installations of Lazarus and FreePascal using installers from the respective sites.

Try to build your environment step by step. What i usually do is:

1. Unzip CodeTyphonIns.zip in a folder. That folder will be the installation
source folder and NOT the final working folder.

2. Enter the previous folder and execute install.bat. Press "0" and hit "Enter"
to install the CodeTyphon Center.

3. After the installation of CT Center finishes the prompt will show 9 choices.
Press "1" and hit "Enter". Hopefully the CT Center will start.

4. From CT Center go to menu "FreePascal" to build the FreePascal compiler. If
one needs both x86 AND x64 (like me) then better start with the smallest option
first. In our case that would be the x86 option with the crosselement for arm-wince.

5. Select "FreePascal" menu and click on "FPC 32bit Build Compiler".

6. After FPC 32bit and GDB 32bit are ok, select "Cross-Build/FreePascal 32bits"
menu and from the list of CrossBuild elements, select the one suitable. In
our example we will select "FPC32 build cross element arm-wince"

7. After arm-wince Cross Element and GDB are ok, select "Lazarus/Lazarus 32bit
Build BigIDE"

For the x64 edition of FPC and Lazarus perform again the steps "5" through "7" but selecting the "x64" verions
this time (and also bypass the arm-wince part).

Hope it helps...

Kostas

Γεια σου Κώστα, τελικά οι Έλληνες είμαστε παντού

The funny thing is that on this "faulty" desktop installation, Lazarus (apart from the previous version of CodeTyphon) has never installed (i.e the official versions that come with their installer). On another machine (a notebook) with Win7 x64, Lazarus64 builds fine, so this makes me believe that the desktop Windows installation is at fault.

I'll try what you suggested Kostas and will report back here. Thanks.

After some testing it seems that everything builds and runs fine except Lazarus64 BigIDE (Lazarus64 SmallIDE works fine).
I've redirected the build output of ScriptsWin\x_Lazarus_Win64_Build.bat to a text file, but I do not see any compilation issues.

Frontier314 wrote: Γεια σου Κώστα, τελικά οι Έλληνες είμαστε παντού

Frontier314 wrote: After some testing it seems that everything builds and run fine except Lazarus64 BigIDE (Lazarus64 SmallIDE works fine).
I've redirected the build output of ScriptsWin\x_Lazarus_Win64_Build.bat to a text file, but I do not see any compilation issues.

This is REALLY strange. The installation scripts always build first the SmallIDE. In the case of BigIDE, the Small gets build first and then the Big follows...
But with no errors? And after a successful installation procedure? ...the first thing that crosses my mind right now is the suggestion of sir Sternas: Antivirus.
That might be a problem. And also, if windows were faulty then shouldn't there be problems in the x86 version also?

Kostas

With no more info
I can't think anything else
Μάνο
please more info for your pc box

papadouk wrote: This is REALLY strange. The installation scripts always build first the SmallIDE. In the case of BigIDE, the Small gets build first and then the Big follows...

Exactly!
The SmallIDE script builds the x64 SmallIDE version fine (it runs), but the BigIDE script creates an executable that produces an exception and fails.

But with no errors? And after a successful installation procedure? ...the first thing that crosses my mind right now is the suggestion of sir Sternas: Antivirus.
That might be a problem. And also, if windows were faulty then shouldn't there be problems in the x86 version also?

I did not spot something wrong in the build output, but I might be wrong since it's quite big (over 1.5MB of text).
I do suspect something - regarding the fact that the x86 version works but the x64 BigIDE doesn't - regarding SysWOW64 (the environment that BigIDE x86 executes) and the native system (where BigIDE x64 fails). Maybe there is some corruption.

I will follow Sir Sternas and your suggestion and will re-build BigIDE x64 after uninstalling my antivirus (Avast).
Will post results.

sternas wrote: With no more info
I can't think anything else
Μάνο
please more info for your pc box

Thank you Sir Sternas for your help.

I have two Windows 7 PCs (a desktop and a notebook) with the following specifications:

Notebook (on this one CodeTyphon works absolutely fine and BigIDE x64 works like a charm):
Intel Core i7 @ 2.80GHz
Windows 7 x64 Ultimate
8GB RAM

Desktop (on this one BigIDE x86 works fine but BigIDE x64 aborts with an exception while SmallIDE x64 works):
Intel Core2Duo Q6600 @ 3.02GHz
Windows 7 x64 Ultimate
4GB RAM

Let me know if there's anything else that you need.

It's very strange ...

Here's what I did on my desktop PC:

- Uninstalled AVAST!.
- Run - from an elevated command prompt - the command "SFC /SCANNOW". The tool found some violated system files and repaired them. Rebooted, run the command again and everything is OK.
- Turned UAC off (reboot). The system works without an antivirus program and with UAC turned off.
- On an elevated command prompt, I've executed the ScriptsWin\x_Lazarus_Win64_Build_Small.bat to create the SmallIDE Win64. The process was successful and the executable for Lazarus runs fine.
- On the same elevated command prompt the script x_Lazarus_Win64_Build.bat is executed. The output of this process is attached, no build errors. The resulting Lazarus BigIDE Win64 executable produces an exception that triggers Microsoft DrWatson and reports it to them (still does not load).
- Copied the Lazarus BigIDE x64 executable compiled on the notebook (which runs fine) to the desktop and it does not run. Performed the opposite - i.e copying the desktop compiled Lazarus64 BigIDE to the notebook - and it works.

Uninstalled CodeTyphon completely and install the latest Lazarus64 version from sourceforge (v0.93.30.2) which runs fine.

I do not want to bother you more with this, the problem is purely related to my desktop system which produces this erratic behaviour.

So this makes clear that the problem comes from a component that gets compiled only in the big IDE. Somehow this component does not react good with your system, Manos.
You windows are in Greek language? If yes have you tried to switch them to English and retry? I know what i am saying now is one in a million BUT from my small experience with windows, the Greek versions had different libraries than the original versions.

Just thoughts...

Kostas

papadouk wrote: So this makes clear that the problem comes from a component that gets compiled only in the big IDE. Somehow this component does not react good with your system, Manos.

Exactly.

You windows are in Greek language? If yes have you tried to switch them to English and retry? I know what i am saying now is one in a million BUT from my small experience with windows, the Greek versions had different libraries than the original versions.

No, it's the US version with Greek NLS.

My friend
it's obvious that your PC have problem
My suggestion is to reinstall MSWindows

I plan to reinstall the OS on that machine as soon as my replacement hard disk arrives.
Again, thank you very much for your support.

A long time has passed since I've reported this problem. I couldn't find some time to re-install the OS, but yesterday I tried to debug Lazarus BigIDE x64 in order to find out what might cause this behaviour.

It turned out that my Windows installation was fine and indeed there are problems with some printer components in Lazarus BigIDE that are causing the program to fail.

For more info, see this thread:
www.pilotlogic.com/sitejoom/index.php/fo...offline-printer#1960

Is it possible to discretely identify the component(s) that cause the error to your installation?

The only way to do this is to Build BigIDE, starting with SmallIDE and recompiling Lazarus including certain components at a time.
Unfortunately neither Application Verifier or Dependency Walker can identify the Lazarus component at fault, because everything is compiled inside the big fat IDE executable. If Lazarus would be somehow "segmented" (i.e the components would be shared libraries loaded when needed) then it would be possible to trace each of them.