svn path=/trunk/boinc/; revision=20200

    in boinc_parse_init_data_file()
- client sim: make it work again

svn path=/trunk/boinc/; revision=20199

        the remaining thread the process will deadlock.

    lib/
        diagnostics.h
        diagnostics_win.cpp
        win_util.cpp

svn path=/trunk/boinc/; revision=20198

svn path=/trunk/boinc/; revision=20197

svn path=/trunk/boinc/; revision=20196

svn path=/trunk/boinc/; revision=20195

svn path=/trunk/boinc/; revision=20194

    Should add the Adv Prefs dialog as well.

svn path=/trunk/boinc/; revision=20193

svn path=/trunk/boinc/; revision=20192

    it contains HOST_INFO, which now contains COPROCS,
    which has a vector.
    Define a clear() for APP_INIT_DATA.

svn path=/trunk/boinc/; revision=20191

    anonymous-platform app versions.
    Otherwise fractional GPU requirements get truncated to zero.
    Thanks to Crunch3r for identifying the problem.
    

svn path=/trunk/boinc/; revision=20189

user web: do SQL escaping before storing prefs in the database as some projects store user-editable strings in the preferences.

svn path=/trunk/boinc/; revision=20188

    (min_core_version etc.) is < 10000,
    multiply it by 100 and print a warning.

svn path=/trunk/boinc/; revision=20187

svn path=/trunk/boinc/; revision=20185

svn path=/trunk/boinc/; revision=20184

svn path=/trunk/boinc/; revision=20183

svn path=/trunk/boinc/; revision=20181

svn path=/trunk/boinc/; revision=20180

svn path=/trunk/boinc/; revision=20179

    From Nicolas. fixes #974
- client: tiny code shuffle

svn path=/trunk/boinc/; revision=20178

svn path=/trunk/boinc/; revision=20176

    
    clientgui/
        ViewNotices.cpp,h

svn path=/trunk/boinc/; revision=20152

svn path=/trunk/boinc/; revision=20151

svn path=/trunk/boinc/; revision=20150

    10000*major + 100*minor + release,
    rather than 100*major + minor.
    Sometimes you need release-level resolution.
    This affects:
    - app_version.min_core_version
    - config: min_core_client_version_announced
    - config: min_core_client_version
    Projects using these must multiply them by 100.

svn path=/trunk/boinc/; revision=20149

MGR: Fix tools menu when using account manager and switching Simple to Advanced View; update XCode project for ViewNotifications* -> ViewNotices*

svn path=/trunk/boinc/; revision=20147

	- XML_PARSER: handle CDATA

svn path=/trunk/boinc/; revision=20146

    if project has crazy DCF, don't automatically request 1 sec;
    only request work if there's a shortfall.
- intermediate checkin for notices stuff

svn path=/trunk/boinc/; revision=20145

Commit from BOINC Translation Services by user ChristianB. 370 of 389 messages translated (18 fuzzy).

svn path=/trunk/boinc/; revision=20144

svn path=/trunk/boinc/; revision=20143

svn path=/trunk/boinc/; revision=20142

    sends the first rather than last 64KB of stderr to server.
    This doesn't belong here; this choice should come from the server.
    I may take this out later.
- user web: when add a private message, always add a notification

svn path=/trunk/boinc/; revision=20141

deletion' pass to 50000 (can be changed with -delete_antiques_limit).
  Previously large number of antiques led to not deleting any at all.
- Allow to change the interval between passes with -delete_antiques_interval.

svn path=/trunk/boinc/; revision=20138

svn path=/trunk/boinc/; revision=20137

svn path=/trunk/boinc/; revision=20133

svn path=/trunk/boinc/; revision=20132

svn path=/trunk/boinc/; revision=20131

svn path=/trunk/boinc/; revision=20130

svn path=/trunk/boinc/; revision=20129

    to restart app for 10 minutes.
    Hopefully what will happen is:
    - another instance of app is running in slot dir
        (shouldn't happen, but sometimes does)
    - that app will eventually finish, and will write
        a checkpoint file saying so.
        It will call boinc_finish(0), but the client won't notice
        that it has exited.
    - the next time the client starts the app,
        it will acquire lock, see that it's done,
        and call boinc_finish(0).
        This time the client will notice,
        and the job will be reported as correct.
    The downside to all this is that the client won't know
    that the CPU is in use, and will schedule NCPUS jobs.

svn path=/trunk/boinc/; revision=20128