http://setiathome.berkeley.edu/show_host_detail.php?hostid=6010844

For this laptop for various reasons I cannot run BOINC for more than a few hrs.

Anyway, I was thinking about some other things I read where people were talking about system ID's and it got me thinking. What defines these ID's, in the case of this laptop 6010844.

Every once in a while I get a BSOD due to some driver issues I'm working on. Well, for example, when I log in to say my internet banking sometimes it asks if this will be my new system or something like that when in fact nothings changed. So something about the BSODS or something being reset during a BSOD makes some things, not just my internet banking go hey, this is a new system.

I dont know if it does anything similar with BOINC (new system ID) as I haven't tried to connect in a good long while but that got me thinking as to the whole system ID thing. What about BOINC goes ok, this is this systems ID.

Sorry for the bit of rambling and the fact this this may have taken longr than it should have to ask but its late and I'm tired as F.

Ty ![url][/url]

---

Mind telling what the BSOD has to say? I ask, since Windows has a couple of thousand of them, not just one.
No matter how cryptic the message in the BSOD was, it is an indication as to what's wrong on your system. Some people can read what these messages mean. Therefore, always state what the BSOD said, not just that you had one.

---

Mind telling what the BSOD has to say? I ask, since Windows has a couple of thousand of them, not just one.
No matter how cryptic the message in the BSOD was, it is an indication as to what's wrong on your system. Some people can read what these messages mean. Therefore, always state what the BSOD said, not just that you had one.

It's a driver thing, the laptop was built around vista and I got XP. Also, there's no time to read it since it flashes and resets.

Any way, while yes I did mention a BSOD, the overall question was what defines these ID's that BOINC uses for computer identification.

---

To see and read the BSOD (or better - make photo of the BSOD screen) - uncheck Auto Restart:
(BSOD message will stay on screen until you press Reset or on/off buttons on the computer)




And the new computer ID is just the next available number.

(IDs are not reused, your laptop is #6010844 because at the time you added it to the project
all the numbers from #1 to #6010843 were taken/used by (somebody's) attached computers in the past.
So NewID(yours) = LastID(in existence) + 1
)

I don't think there is such thing "built around vista".
XP is more popular than Vista so any hardware vendor will be inclined to supply driver for XP

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Thx for the reply, I'll do that and try to catch the BSOD next time it happens if it happens. That said, so ID's are assigned by whats available at the time a system is added. So let me rephrase my original a bit.

What, if anything might assign someones computer a new ID ?

Edit: As for built around Vista, maybe a poor choice of words but I do remember having issues finding XP drivers for one or more of the laptops components. Will have to recheck everything next time I get a BSOD and post it somewhere for examination.

---

http://boinc.berkeley.edu/trac/wiki/HostId

"The computer ID and the RPC sequence number are also stored in the client's client_state.xml file. The client increments the RPC sequence number on each scheduler request.

If the scheduling server receives an RPC with a sequence number less than the expected sequence number (usually indicating that the user has copied the client_state.xml file between computers)
it creates a new database record and returns a new ID."


Maybe this means that if the computer sends scheduler request and the scheduling server receives it OK
but the computer hangs/crash (BSOD) before updating the RPC sequence number in client_state.xml file
then at next scheduler request the scheduling server "creates a new database record and returns a new ID".

<project>
    <master_url>http://setiathome.berkeley.edu/</master_url>
    <project_name>SETI@home</project_name>
    <symstore></symstore>
    <user_name>BilBg</user_name>
    <team_name>HardwareBG SETI Team</team_name>
    <host_venue>home</host_venue>
    <cpid_time>1180238970.000000</cpid_time>
    <user_total_credit>827123.292967</user_total_credit>
    <user_expavg_credit>164.719242</user_expavg_credit>
    <user_create_time>1180238970.000000</user_create_time>
    <rpc_seqno>16348</rpc_seqno>
    <hostid>4832843</hostid>

How to revert to an older HostID number?:
http://boincfaq.mundayweb.com/index.php?language=1&view=293

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

So as long the computer doesn't crash during any XML edits or any edits are interrupted then the computer should always keep the ID which for arguments sake and in the case of this laptop is the one already stated ?

---

Why "edits"? (I presume you mean manual edits)

boinc.exe (the local client) regularly changes/updates the client_state.xml file with new info
(maybe every minute if you don't change the default "Tasks checkpoint to disk at most every 60 seconds")

On the 4 computers I used for SETI in the past ~4 years it never happened (IIRC)
- they always keep the initial ID given at the time of first attach.
(and I never did reformat the disk or re-install Windows)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)