Jason

-1- files

somebody should correct me, but the only 2 DLL found so far, resides in the BOINC folder on the same place as the client. the dll called

dbghelp.dll
boinc.dll

when dlls resides in the same folder as the application, normaly they will be found.
Offen DLLs have to be registered (regsvr.exe xyz.dll & parameters), I did not

If there is a registery setting, it has to be copied to target system

-2- registery settings
in addition with the filesystem, NT (windows) loves to write down adidional Infos in the registery (database).
see on your working windows, open a cmd, type regedit and "enter"
when the tool is started, press f3 (find) and let search for boinc,
pressing f3 repeates the search. you will find several ENTRIES named boinc,
two of them have information about the PATH, where the client resides.

you see what I mean.
This "path settings" appears 2 times in the registery.
on the target pc they should match to your settings.

The section can be exported (gives a .reg) in automation
regedit xzy.reg puts the setting in the regtistery

There a 2 parameters for hiding the start of registery editor and suppress the need to click ok on a message box.

also you can copy paste the following 6 lines to notepad and save as yxz.reg


Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\BOINC]
"ClientPath"="c:\\boinc\\boinc_gui.exe"
"ClientDir"="c:\\boinc"
"WinDir"="C:\\WINDOWS\"



the 2nd entry

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\boinc_gui.exe]
"Path"="c:\\boinc"
@="c:\\boinc\\boinc_gui.exe"



now you have 2 xyz.reg files edit them and change the path for your setting

yes there are 2 \\.

there are 2 more registery entries, concerning the 2 dlls, so far no need to change or to add the settings.


Afther booting pe and "mapping drive", first add the 2 registery entries
and the start the client.

several way to do it,
one way: create a do_reg.cmd

type in

regedit /s/e \\serverpc\folder\regfile1.reg
regedit /s/e \\serverpc\folder\regfile2.reg

close it and put in a startup sequence or startup folder.

this mini script put the value with no user intervention into the registery

An other way is to include this reg at the pe build time.

hope to give the needed information so you can build ot with less files
sorry I don't whant to write to much but Is not easy with the registery an windows would like to share information as" clear as possible



> happens.. it ran for about 12 hours today while I was at work.
looks like a stable installation, waiting for the AMD pc should first empty there queues bevor migrating
>

>
> As for Hyper Threading, there should be support for HT in BArtPE as the kernal
> is the same.. but like the regulat instal of BOINC you have to run two CLI's
> to use the other virtual CPU..
thankyou, one problem solved, like on seti 1

goodluck

Richard

Ok, I undestand all the registry entries made by boinc..they all seem dependant on the GUI anyway but The thing I don't understand is this:

I ran the BOINC CLI from a pc that didn't have BOINC installed... so none of those reg entries would have been there and it ran fine but the PE setup dies once the WU is downloaded and it starts to crunch it.. from my testing the CLI is portable on any system as long as the dlls mentioned are in the same directory as the app... You can even rename the cli app to whatever.exe and no issues, the only issues I get are when I run it from the PE enviroment, I'm thinking it as something to do with everything residing in memory, after it downloads the WU begins the crunching process it breaks.. some where the transfer from the ramdisk to the server share its erroring... and there are no logs in PE to even look at..

Now if i let a standard PC download the WU and begin the crunching process then close that app on the standard PC and start it up on PE it runs fine till a new WU is downloaded. this is telling me its some where in the process of downloading and begining the crunching process.

Still crunching on the old app,
Jason

<a> [/url]

not sure if still alive

got same as you

with the PE got:
SETI@home - 2004-07-15 14:17:25 - Unrecoverable error for result 10ja04ab.10011.6082.198574.40_3 ( - exit code -1066598274 (0xc06d007e))

SETI@home - 2004-07-15 14:17:15 - Approximate throughput 24021.195089 bytes/sec
SETI@home - 2004-07-15 14:17:23 - Finished download of setiathome_3.08_windows_intelx86.pdb
SETI@home - 2004-07-15 14:17:23 - Approximate throughput 38361.492974 bytes/sec
SETI@home - 2004-07-15 14:17:23 - Starting computation for result 10ja04ab.10011.6082.198574.40_3 using setiathome version 3.08
SETI@home - 2004-07-15 14:17:25 - Unrecoverable error for result 10ja04ab.10011.6082.198574.40_3 ( - exit code -1066598274 (0xc06d007e))
SETI@home - 2004-07-15 14:17:25 - Deferring communication with project for 9 minutes and 22 seconds
SETI@home - 2004-07-15 14:17:25 - Computation for result 10ja04ab.10011.6082.198574.40 finished

About the same when running the CLI version

>You can even rename the cli app to whatever.exe
the most of them (exeption at m$) your right.

All the manipulation had no influence.

Mesured what's going on while the boncclient installs,
yes, at least the grafical interface will install something in the windows directory, the screensaver(!). But that seams not to be mandatory, if an NT user, runs under restricted accout settings without havingthe persission to write to a system folder it will also failes.

I'am nearly sure, the PE installations of this thread users/readers are running fine, we can download and aftherwords it plays bad.
Then something can't write, can't swap, can't do that what it can on a "non" PE.

I will stay subcribed to this, maybe other ideas, helpfull hints come in.

someone has tried to make a ghost (or an other image) from a running pe and then reloaded to a harddisk?

Richard