optimized sources

Seti@Home optimized science apps and information

Welcome, Guest. Please login or register.
24 May 2013, 11:45:53 pm

Quote from: seti_britta on 17 Apr 2007, 12:34:59 pm

Heut gabs auch so eine: Service Pack1 für C++2005 (KB926748)
habs installiert und hinterher kann man nix mehr compilieren, überall C4003, eine Katastrophe, hab schon rumgesucht in diversen Foren, aber denke ich werd mal den Stand von vor dem update einspielen müssen, damit es wieder klappt, oder hat schon jemand diese Probleme mit den veränderten Headerdateien gelöst Huh

...
--------------------------------------------------------
Und so sieht´s jetzt aus
Microsoft Visual Studio 2005
Version 8.0.50727.762(SP.050727-7600)
Microsoft .NET Framework
Version 2.0.50727
--------------------------------------
hat jemand noch Vorschläge zu dem Problem Servicepack ??

Hi,
ich hab' das SP1 zu VS2005E ebenfalls installiert (Anfang Januar), konnte jedoch keine Probleme oder Veränderungen feststellen. Vielleicht musst Du es einfach nochmal probieren (Deinstallieren, Reboot, Installieren, Reboot). Viel Erfolg.

Hi all,
have decide to uninstall SQL and Visual Studio 8 including C++20005 complete and start with a new install of all at the beginning. Takes a little time.
Why I do so ?
Most problems are long path names including spaces.
for instance:
C:\Programme\Microsoft SQL Server\90\SDK\Lib\x86
C:\Programme\Microsoft Visual Studio 8\VC\lib
LIB and linker don´t like that.
Short names without spaces are demanded.
like:
C:\I\SQL\90\SDK\Lib\
C:\I\VS8\VC\lib
C:\I\SDK
-------------------------------------------
@urs --> have deinstalled service pack 1, my lib does not work correct when I use the präprocessor
best of all ---> new install

Britta,

you can circumvent the long file name problem. "Programme" becomes "PROGRA~1", for example.

Basically, it works like:

Chars 1-6 are used as they are, in caps. Then, a tilde and a number is appended. So, "Program Files" on the same computer would be "PROGRA~2" with the short file name.

Using this scheme, you can convert any old file or path name. You could also just use a 16-bit app (one that comes with a vcrt30.dll or vbrun300/400.dll, for example) that opens a file. It will show you the path in the above syntax.

HTH,
Simon.

@Simon
thanks for the hints....
- have problems to uninstall SQL Server 2005, looks like a difficult action
found this: http://support.microsoft.com/kb/909967/en-us?spid=2855&sid=699
Is there an easy way to do the deinstallation, have you a hint?
If I try to uninstall about Systemsteuerung --> Software I get Error 2147944122 problem with WMI configuration
Cry

did now go backwards , take last thursday in systemreconfiguration, did uninstall all Visual applications and the IDE, made some updates from Microsoft to be at the actual update level. SQL Server is now running again and .NET Framework 2.0 with latest updates.
Let run boinc. It crashes after some time. look at "error message in Boinc" Cry

setti_britta :

maybe is better to reinstall whole OS .... Wink

hi all,
after great difficulties, have now deinstalled the damaged .NET Framework. Used a tool named dotnetfx_cleanup_tool. Was not easy to find that. After new start of the PC, I was able to install the .NET Framework 2.0 sucessful. Seti boinc works now without any problems.
After that I deinstalled the SQL Server sucessful. Now I can start setup Visual Studio and the IDE with short path names.
------------------

Today I made some deinstallations from different user programs, cleaned the registry, defrag all disks, and made a full backup, in preparation of the new install of SQL and Visual Studio.
Work is going on.
Grin

Hi all,
my new installed development system is running. Short paths are activ now

C:\I\INTEL\IPP
C:\I\INTEL\MKL
C:\I\SC\seti -->for the seti sources
C:\I\SC\seti\boinc
C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe
C:\I\SDK --> Software Development Kit
C:\I\VS8 --> Visual Studio
------------------------------------------------------
If I don´t use the präprozessor, system works fine.
The use of the Präprozessor is still a Problem, linker did not find the objektmodul.
Can anybody of you have a look at this Crunch3r, Simon ?
----------------------------------------------------------------------------------
Buildprotokoll Erstellen wurde gestartet: Projekt: "setiboincdb", Konfiguration: "Release32-NOGFX|Win32"
Befehlszeilen Die temporäre Datei "c:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\RSP0000225483688.rsp" wird erstellt. Inhalt:
[
/O2 /Ob2 /Oi /Ot /Oy /GT /I "C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\db" /I "C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX" /I ".." /I "..\.." /I "..\..\..\boinc\lib" /I "..\..\..\boinc\win_build" /D "Release32-NOGFX" /D "WIN32" /D "NDEBUG" /D "_LIB" /D "_MT" /D "_WINDOWS" /D "_CONSOLE" /D "HAVE_STD_MAX" /D "HAVE_STD_MIN" /D "HAVE_STD_TRANSFORM" /D "CLIENT" /D "NBOINC_APP_GRAPHICS" /D "_VC80_UPGRADE=0x0710" /D "_MBCS" /P /GF /FD /EHsc /MT /Zp16 /GS- /Gy /Fo"Release32-NOGFX\\" /Fd"Release32-NOGFX\vc80.pdb" /W3 /c /Wp64 /TP "..\..\db\xml_util.cpp"

"..\..\db\sqlrow.cpp"

"..\..\db\sqlint8.cpp"

"..\..\db\sqlblob.cpp"
]Erstellen der Befehlszeile "cl.exe @"c:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\RSP0000225483688.rsp" /errorReport:prompt"Die temporäre Datei "c:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\RSP0000235483688.rsp" wird erstellt. Inhalt:
[
/OUT:"C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\setiboincdb.lib" /LIBPATH:"C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX" /LIBPATH:"C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build"

".\Release32-NOGFX\sqlblob.obj"

".\Release32-NOGFX\sqlint8.obj"

".\Release32-NOGFX\sqlrow.obj"

".\Release32-NOGFX\xml_util.obj"
]Erstellen der Befehlszeile "lib.exe @"c:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\RSP0000235483688.rsp"" Ausgabefenster Kompilieren...
Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version 14.00.50727.42 für 80x86
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
cl /O2 /Ob2 /Oi /Ot /Oy /GT /I "C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\db" /I "C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX" /I ".." /I "..\.." /I "..\..\..\boinc\lib" /I "..\..\..\boinc\win_build" /D "Release32-NOGFX" /D "WIN32" /D "NDEBUG" /D "_LIB" /D "_MT" /D "_WINDOWS" /D "_CONSOLE" /D "HAVE_STD_MAX" /D "HAVE_STD_MIN" /D "HAVE_STD_TRANSFORM" /D "CLIENT" /D "NBOINC_APP_GRAPHICS" /D "_VC80_UPGRADE=0x0710" /D "_MBCS" /P /GF /FD /EHsc /MT /Zp16 /GS- /Gy /Fo"Release32-NOGFX\\" /Fd"Release32-NOGFX\vc80.pdb" /W3 /c /Wp64 /TP "..\..\db\xml_util.cpp"
"..\..\db\sqlrow.cpp"
"..\..\db\sqlint8.cpp"
"..\..\db\sqlblob.cpp"
xml_util.cpp
sqlrow.cpp
sqlint8.cpp
sqlblob.cpp
Bibliothek wird erstellt...
Microsoft (R) Library Manager Version 8.00.50727.42
Copyright (C) Microsoft Corporation. All rights reserved.
"/OUT:C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\setiboincdb.lib" "/LIBPATH:C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX" "/LIBPATH:C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build"
".\Release32-NOGFX\sqlblob.obj"
".\Release32-NOGFX\sqlint8.obj"
".\Release32-NOGFX\sqlrow.obj"
".\Release32-NOGFX\xml_util.obj"
LIB : fatal error LNK1181: Eingabedatei ".\Release32-NOGFX\sqlblob.obj" kann nicht geöffnet werden.
Ergebnisse Das Buildprotokoll wurde unter "file://c:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\BuildLog.htm" gespeichert.
setiboincdb - 1 Fehler, 0 Warnung(en)
------------------------------------------------------
greetings seti_britta

Hi,
today I compiled seti_boinc. All sourcefiles are free of any error now. At the end I have a small problem with the linker, did not found objektfile.
------------------------------------------------------
Buildprotokoll Erstellen wurde gestartet: Projekt: "seti_boinc", Konfiguration: "Release32-NOGFX|Win32"
Befehlszeilen Die temporäre Datei "c:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\RSP00001F12082484.rsp" wird erstellt. Inhalt:
[
/OUT:".\Release/seti_boinc.exe" /INCREMENTAL:NO /LIBPATH:"C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\glut" /LIBPATH:"C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\image_libs" /LIBPATH:"C:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\jpeglib" /LIBPATH:"glut" /LIBPATH:"image_libs" /LIBPATH:"jpeglib" /MANIFEST /MANIFESTFILE:".\Release32-NOGFX\seti_boinc.exe.intermediate.manifest" /PDB:".\Release/seti_boinc.pdb" /SUBSYSTEM:WINDOWS /MACHINE:X86 glut32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib

".\Release32-NOGFX\amd64fft8g.obj"

".\Release32-NOGFX\analyzeFuncs.obj"

".\Release32-NOGFX\analyzePoT.obj"

".\Release32-NOGFX\analyzeReport.obj"

".\Release32-NOGFX\app_ipc.obj"

".\Release32-NOGFX\boinc_api.obj"

".\Release32-NOGFX\chirpfft.obj"

".\Release32-NOGFX\fft8g.obj"

".\Release32-NOGFX\filesys.obj"

".\Release32-NOGFX\gaussfit.obj"

".\Release32-NOGFX\gdata.obj"

".\Release32-NOGFX\graphics_api.obj"

".\Release32-NOGFX\graphics_data.obj"

".\Release32-NOGFX\gutil.obj"

".\Release32-NOGFX\lcgamm.obj"

".\Release32-NOGFX\main.obj"

".\Release32-NOGFX\malloc_a.obj"

".\Release32-NOGFX\parse.obj"

".\Release32-NOGFX\pulsefind.obj"

".\Release32-NOGFX\s_util.obj"

".\Release32-NOGFX\sah_gfx.obj"

".\Release32-NOGFX\sah_gfx_base.obj"

".\Release32-NOGFX\schema_master.obj"

".\Release32-NOGFX\seti.obj"

".\Release32-NOGFX\seti_header.obj"

".\Release32-NOGFX\shmem.obj"

".\Release32-NOGFX\spike.obj"

".\Release32-NOGFX\sqlblob.obj"

".\Release32-NOGFX\sqlrow.obj"

".\Release32-NOGFX\timecvt.obj"

".\Release32-NOGFX\util.obj"

".\Release32-NOGFX\version.obj"

".\Release32-NOGFX\windows_opengl.obj"

".\Release32-NOGFX\worker.obj"

".\Release32-NOGFX\tgalib.obj"

".\Release32-NOGFX\xml_util.obj"

".\Release32-NOGFX\rdtarga.obj"

".\Release32-NOGFX\jcapimin.obj"

".\Release32-NOGFX\jcapistd.obj"

".\Release32-NOGFX\jccoefct.obj"

".\Release32-NOGFX\jccolor.obj"

".\Release32-NOGFX\jcdctmgr.obj"

".\Release32-NOGFX\jchuff.obj"

".\Release32-NOGFX\jcinit.obj"

".\Release32-NOGFX\jcmainct.obj"

".\Release32-NOGFX\jcmarker.obj"

".\Release32-NOGFX\jcmaster.obj"

".\Release32-NOGFX\jcomapi.obj"

".\Release32-NOGFX\jcparam.obj"

".\Release32-NOGFX\jcphuff.obj"

".\Release32-NOGFX\jcprepct.obj"

".\Release32-NOGFX\jcsample.obj"

".\Release32-NOGFX\jctrans.obj"

".\Release32-NOGFX\jdapimin.obj"

".\Release32-NOGFX\jdapistd.obj"

".\Release32-NOGFX\jdatadst.obj"

".\Release32-NOGFX\jdatasrc.obj"

".\Release32-NOGFX\jdcoefct.obj"

".\Release32-NOGFX\jdcolor.obj"

".\Release32-NOGFX\jddctmgr.obj"

".\Release32-NOGFX\jdhuff.obj"

".\Release32-NOGFX\jdinput.obj"

".\Release32-NOGFX\jdmainct.obj"

".\Release32-NOGFX\jdmarker.obj"

".\Release32-NOGFX\jdmaster.obj"

".\Release32-NOGFX\jdmerge.obj"

".\Release32-NOGFX\jdphuff.obj"

".\Release32-NOGFX\jdpostct.obj"

".\Release32-NOGFX\jdsample.obj"

".\Release32-NOGFX\jdtrans.obj"

".\Release32-NOGFX\jerror.obj"

".\Release32-NOGFX\jfdctflt.obj"

".\Release32-NOGFX\jfdctfst.obj"

".\Release32-NOGFX\jfdctint.obj"

".\Release32-NOGFX\jidctflt.obj"

".\Release32-NOGFX\jidctfst.obj"

".\Release32-NOGFX\jidctint.obj"

".\Release32-NOGFX\jidctred.obj"

".\Release32-NOGFX\jmemmgr.obj"

".\Release32-NOGFX\jmemnobs.obj"

".\Release32-NOGFX\jquant1.obj"

".\Release32-NOGFX\jquant2.obj"

".\Release32-NOGFX\jutils.obj"

".\Release32-NOGFX\rdbmp.obj"

".\Release32-NOGFX\rdcolmap.obj"

".\Release32-NOGFX\rdgif.obj"

".\Release32-NOGFX\rdppm.obj"

".\Release32-NOGFX\rdrle.obj"

".\Release32-NOGFX\rdswitch.obj"
]Erstellen der Befehlszeile "link.exe @"c:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\RSP00001F12082484.rsp" /NOLOGO /ERRORREPORT:PROMPT" Ausgabefenster Verknüpfen...
LINK : fatal error LNK1181: Eingabedatei ".\Release32-NOGFX\amd64fft8g.obj" kann nicht geöffnet werden.
Ergebnisse Das Buildprotokoll wurde unter "file://c:\I\SC\seti\seti_boinc_2k3_2.2B-Ben-Joe\client\win_build\Release32-NOGFX\BuildLog.htm" gespeichert.
seti_boinc - 1 Fehler, 0 Warnung(en)
--------------------------------------------------------
Wink

Quote from: seti_britta on 13 Apr 2007, 03:32:21 pm

@Aragon
how you know I´m working on further optimization of the seti sourcecode. Till now I have done more about two hundred changes in the sourcecode. The main problem is the migration from 2003 to Visual C++2005. Many changes are necessary to compile the sources without any error and without a lot of warnings. But that´s not an easy job and many problems are to solve on this way. That´s what I´m doing at the moment. Crunch3r helped me to set up the Visual C++2005 development system., using IPP and MKL.
-------------------------------------------
for all others: work is going on
glut
image_libs
jpeglib
libboinc
libboincapi
setiboincdb
are now compiled without any error, without any warnings /w3
--------------------------------------------
Optimizer is 90% done,
--------------------------------
happy weekend Wink

Had a problem with my PC so it's taken me a while to get back here.... Roll Eyes

Thx for the update. Wink

Hi all,
back from the weekend holiday I started my PC, but the power supply did not start. After I disconnected all disks the powersupply started and the board was running. I think the powersupply is defect. Tomorrow I will buy a more powerful 420W powersupply and repair the PC. It is a P4 2.6MHZ with 2 IDE disks and 1 CD-burmer and 1 DVD-burner. This machine was runnung 24/7 for 2years and 2 months.
Today I´m here with my old 200MMX W98, to write these messages.
Its a installation on the fly, board, PSU, disk is laying on the desk in my lab. How you see it works.....
hoping will be back soon.

Good luck Britta!

In the past week, I've replaced two faulty PSUs that just gave up and died after running for 5+ years each. I've always got some spare PSUs lying around for this very reason - if a mission-critical system goes down, it'll be back up soon enough (newer servers all get ordered with redundant PSUs for this reason - my boss doesn't like the extra cost, but he liked the cost from downtime a whole lot less...).

Regards,
Simon.

Yesterday I set the new PSU in the PC, and it starts sucessfull, but did not load XP from the disk. So I decide to restart with my last full backup from april 24 th. The restore of the system disk was sucessful and Xp starts again. Happy that no further hardware are crashed. Both disks are OK now and the computer works again normal.
Summary I lost more of a complete week of work.
Must now reinstall Visual Studio including C++, SDK, IPP and MKL to continue.
Work is going on.
-------------------------
resume: it is allways good to have a full backup of the System disk.
regards seti_britta.
Grin

The SDK is now new installed and I can compile seti sources again. Try to compile Optimizer, all sources are compiled, but at the end LIB ended with error:
LIB : fatal error LNK1181: Eingabedatei ".\Release32-NOGFX\AKfoldSSE.obj" kann nicht geöffnet werden.
Simon can you have a look at this ---> BuildLog.zip
don´t see the error today ;-(
-------------------------------------------------------------------
Today 4.Mai the Intel MKL license ended for me.
This message is to alert you that your evaluation period for the product below will expire as of May 04, 2007.
Product Name: Intel(R) Math Kernel Library for Windows*
------------------------------------------------------------------------------
After new install of Framework 2.0, Boinc installed as a service ended after a half hour of work with following massage:
BOINC client
Problemsignatur
szAppName:boinc.exe szAppVer:5.9.0.64 szModName:msvcr80.dll szModVer:8.0.50727.42 Offset:00008890
-------------------------------------
did install the new client again from Crunch3r´s Website, but no sucess, same error occured.
Any ideas Huh

Crunch3r , Simon ??

Mfg seti_britta

BuildLog.zip (2.31 KB - downloaded 41 times.)

Seti@Home optimized science apps and information \| Powered by Enigma 2.0 (RC1). © 2003-2013, LSP Dev Team. All Rights Reserved.	Seti@Home optimized science apps and information Forums \| Powered by SMF. © 2005, Simple Machines LLC. All Rights Reserved.