[ddiokno]

Hi,
I came home and woke my screen up (seti was set to blank screen and energy saver turns it off). When I woke it up, briefly saw seti graph in the background disappear and then a dialog box came up which said "Warning, platform Macintosh can't be found. Continuing in test mode.". I'm not sure if this has anything to do with seti, or what? Has anyone else ever seen this message before? The only other things running in the background were Outlook Express 5.02 and Internet Explorer (which is a normal thing). Anyone now if this is related to SETI? Or was this just some sort of weird amalgamation? I haven't installed any programs other than software update which installed the sprockets... but the reason I posted it here was because it came up during Seti....
just thought I's see if anyone else has seen this
dave
go Team Macnn!

[ddiokno]

I forgot... i'm runnningFirewire PB 500 320MB 18GBHD OS 9.04 w/all system updates...
dave

[wlonh]

ok, i am thinking this weird error message was due to some fluke in the NewWorldROM of all new Macs since the iMac... at some critical point (gawd knows exactly what point or why that point was arrived at by SETI client software) SETI may have detected Open Firmware and not recognized it, therefore the SETI software did not 'see' MacOS in the incarnation it was used to 'seeing' it...

i know that to some people i must be sounding like a broken record because i blame NewWorldROM as being at the root of many issues with Macs these days... see, the older Macs before the iMac had ONE ROM file and now we have TWO, BootROM (hardware) and MacOS ROM (software, written into RAM) and my contention is that NewWorldROM is still a sort of beta thing... sure seems to be, because new Macs exhibit issues that my trusty beige G3 rev2 minitower would never dream of pulling on me... (damn, i love that beige minitower) and what is the ONE big FUNDAMENTAL difference (sure there are other differences but none as fundamental as the ROM thing) between my beige and newer Macs?

BINGO: NewWorldROM...

[brock76]

ddiokno,

this will explain your problem......it is a multi-platform wide problem. The final touches to version 3 is due out VERY soon and the berkeley boys are trying to set up their so when 3 comes out, no earilier version will be able to send back W/Us. So this will force everyone to upgrade to v 3.0

VIZ:

Warning!
There are reports coming in all around that there may be a problem with uploding results to the Berkeley servers.  These problems are manifesting themselves in the form of "WARNING: Platform XXXXXXX not found; continuing in test mode".  Where XXXXXXX is the client being used.  There are *alot* of people who are experiencing this problem right now, and there is no word from the Berkeley guys what is up.  When this error message is shown the work units do not appear to be credited to that person's account...and it is happening across different platforms and clients.  I can't say what the best thing to do is....I am not sure if those work units results are actually being kept track of over there, or if they eventually will be credited to accounts.  I just turned off the auto connect for my SETI Queue and will hold out until it looks like things are straightened out.
This is just an idea....but I think they are working on getting things prepared for the version 3.0 client release and are getting things checked out to prevent older clients from sending in results.  The problem is...the version 3.0 client isn't released yet and this shouldn't be happening....but that is only my "theory".   Will keep you informed on what is going on over there.   -zAmboni

AND:

Fixed.
Welp i guess the problem that they were having is fixed now.  Granted I have no idea what was wrong and how they fixed it, but it appears that the work unit credit for those who had the error message is gone forever.  The servers were down for maybe 15-30 min this afternoon, and when they were back up the problem experienced earlier was fixed.  Several team members who posted some results at this time, had the error, and as of this time the credit for the work units were not posted.  The only thing I have seen about this was posted on sci.astro.seti earlier this afternoon:

For a few hours this morning our server stopped accepting results since it didn't recognize legitimate SETI@home clients as, well, legitimate clients. This has been fixed. Sorry about all the confusion and credits M.I.A..
- Matt - SETI@home

brock

[This message has been edited by wlonh (edited 08-29-2000).]

[ddiokno]

Thanks Brock and Lon... it really freaked me out... well, not really, but was very perplexing... good to see "we are not alone:-)"

I got the same error message today in the middle of a work unit. Dunno whats going on.

Moof

[wlonh]

so brock, is that where you jumped ship?

with nary a 'fare thee well'...

i edited your message due to the subversive nature of the URL, you could have been nice and just posted the info, but NO... you had to post that damned URL to that damned other team.

NOT nice at all...

[This message has been edited by wlonh (edited 08-29-2000).]

[brock76]

Ya it's good to hear from you too Lon.

and......

no, I did not jump ship to THAT team.


brock

[this message will probably get edited by Lon as well]

[wlonh]

Ray Charles said it best... hit the road, Jack...

one good turn deserves another