byron, i have an hp pavillion with only recovery cd's does your system have a "recovery partition" i.e. C: = file system D:= recovery. if so then the system should be set up to look in D: as if it was the OS cd.
Yes it does, and I'm assuming it tried by the attempts to repair it though I see nothing in the log that shows that, or anything that asks to be directed to any repair options while I'm running the filesystem check. Sorry it's my first experience with Vista, only had it for a few months, though I did read that a Recovery or Restoration disc wouldn't work with filesystem check. I'd do a chkdsk /f but I don't think that will help.
Also, does anyone know if this seems like it could be the cause of the error I had with the Einstein app? Appreciate any help anyone can offer.
Never mind, found this info which appears the sidebar Settings.ini file has nothing to do with the app having an error and is well known by Microsoft so can be ignored.
If anyone has any further info about the Einstein task error I should be concerned about, I'd be interested in learing about it.
It was just brought to my attention that the latest fix to the checkpointing problem won't work on systems prior to Win 2000 (i.e. 98/ME). Actually I haven't a clue what will happen there - any volunteers for testing?
It was just brought to my attention that the latest fix to the checkpointing problem won't work on systems prior to Win 2000 (i.e. 98/ME). Actually I haven't a clue what will happen there - any volunteers for testing?
BM
just so happens I'm running my Duron with ME with the stock right now. I was trying to get a few of those done for a reference, but I can just pop the 6.07 in there now. I have a fair enough idea with what I've done. If it's not going to work I might as well find out now.
Edit: well it's in and running now. Was looking at times of 31 hours with the Duron 1800, was about 9.5% in with the stock so if it finishes I'll have a fair idea on the first one what the boost will be. I'll be watching the .cpt file to see if it updates or not.
2nd Edit 6 minutes in the .tmp file was made.
3rd Edit stderr teXt says same old [CRITICAL]: ERROR "Couldn't rename" No such file or directory as you had thought. Going to try and finish them, will just delete the .cpt file as I go.
BTW 2nd result on the Intel dual core time of 11:30:43 and validated.
XP Athlon 2200+ 2nd result also came in around 21 hours down from the norm of 26-28 stock.
Update on the pc running ME. Deleting the .cpt file doesn't work in ME, it's not recreated afterward. The .cpt.tmp file keeps updating though. Won't be anyway to update this task unless renaming the tmp file as the .cpt file will work. Or seeing if suspending it will cause the .cpt to be generated. At this point I'm more interested in seeing if it will finish and validate so unless someone comes up with a better plan, no checkpointing on this one. I have the rest of the task suspended for now.
Similar story for host 476676, the MMX Celeron 400 running Windows 98 SE.
v6.07 picked up cleanly from v6.04 at ~31%, but seems not to be able to do the checkpoint rename under any circumstances - even when I delete both the .cpt file and the .tmp file, it still creates a new .tmp and fails to rename it. I'm going to assume that manual renaming will give me a viable checkpoint just in case - this machine takes about a week CPU time, 2 weeks elapsed (50% share with SETI), so a power cut with no checkpoint will put it in serious deadline trouble!
I'm discussing this with BOINC developer Rom Walton on boinc_dev mailing list, hopefully have a fix in the BOINC API (available to all projects then) in the next few days.
I don't think you'll lose much running the stock App 6.04 on those machines until then.
6.07 sse auto detect is running good on my Athlon 2800+. Normal time was 66000 sec. for 6.04, the 6.07 app. is in the 57500 range. 15+ percent speedup. Nice speed up for this old chip. Win 2000, Athlon xp 2800+ sse only.
RE: byron, i have an hp
)
Yes it does, and I'm assuming it tried by the attempts to repair it though I see nothing in the log that shows that, or anything that asks to be directed to any repair options while I'm running the filesystem check. Sorry it's my first experience with Vista, only had it for a few months, though I did read that a Recovery or Restoration disc wouldn't work with filesystem check. I'd do a chkdsk /f but I don't think that will help.
Also, does anyone know if this seems like it could be the cause of the error I had with the Einstein app? Appreciate any help anyone can offer.
Thanks
Never mind, found this info
)
Never mind, found this info which appears the sidebar Settings.ini file has nothing to do with the app having an error and is well known by Microsoft so can be ignored.
If anyone has any further info about the Einstein task error I should be concerned about, I'd be interested in learing about it.
First result from the Intel
)
First result from the Intel 11:32:06 Similar to previous apps time as expected, no problems running and validated. Was running next to my error task.
It was just brought to my
)
It was just brought to my attention that the latest fix to the checkpointing problem won't work on systems prior to Win 2000 (i.e. 98/ME). Actually I haven't a clue what will happen there - any volunteers for testing?
BM
BM
RE: It was just brought to
)
just so happens I'm running my Duron with ME with the stock right now. I was trying to get a few of those done for a reference, but I can just pop the 6.07 in there now. I have a fair enough idea with what I've done. If it's not going to work I might as well find out now.
Edit: well it's in and running now. Was looking at times of 31 hours with the Duron 1800, was about 9.5% in with the stock so if it finishes I'll have a fair idea on the first one what the boost will be. I'll be watching the .cpt file to see if it updates or not.
2nd Edit 6 minutes in the .tmp file was made.
3rd Edit stderr teXt says same old [CRITICAL]: ERROR "Couldn't rename" No such file or directory as you had thought. Going to try and finish them, will just delete the .cpt file as I go.
BTW 2nd result on the Intel dual core time of 11:30:43 and validated.
XP Athlon 2200+ 2nd result also came in around 21 hours down from the norm of 26-28 stock.
Update on the pc running ME.
)
Update on the pc running ME. Deleting the .cpt file doesn't work in ME, it's not recreated afterward. The .cpt.tmp file keeps updating though. Won't be anyway to update this task unless renaming the tmp file as the .cpt file will work. Or seeing if suspending it will cause the .cpt to be generated. At this point I'm more interested in seeing if it will finish and validate so unless someone comes up with a better plan, no checkpointing on this one. I have the rest of the task suspended for now.
Similar story for host
)
Similar story for host 476676, the MMX Celeron 400 running Windows 98 SE.
v6.07 picked up cleanly from v6.04 at ~31%, but seems not to be able to do the checkpoint rename under any circumstances - even when I delete both the .cpt file and the .tmp file, it still creates a new .tmp and fails to rename it. I'm going to assume that manual renaming will give me a viable checkpoint just in case - this machine takes about a week CPU time, 2 weeks elapsed (50% share with SETI), so a power cut with no checkpoint will put it in serious deadline trouble!
I'm discussing this with
)
I'm discussing this with BOINC developer Rom Walton on boinc_dev mailing list, hopefully have a fix in the BOINC API (available to all projects then) in the next few days.
I don't think you'll lose much running the stock App 6.04 on those machines until then.
BM
BM
I've done the same, deleted
)
I've done the same, deleted the .cpt file and renamed the tmp. Hopefully it will do the trick if need be.
6.07 sse auto detect is
)
6.07 sse auto detect is running good on my Athlon 2800+. Normal time was 66000 sec. for 6.04, the 6.07 app. is in the 57500 range. 15+ percent speedup. Nice speed up for this old chip. Win 2000, Athlon xp 2800+ sse only.