Shell out $800 + $12.95 a month for a dual tuner HD TiVO with Cable Card. The Tivo HD box released this summer costs $300, not $800. The Tivo service fee gets as low as $8.33 a month if you prepay 3 years in advance. Here in Phoenix (Cox cable) the cable card rental is $2 (you only need one if it is a multistream card). So your monthly cost is $10.33. Cox's HD DVR costs $18.00 a month plus a $5.00 "service" fee.
So if you amortize it over three years, the Tivo DVR and service costs less than the Cox DVR. And it works very well indeed.
1) If you go into the Visual Basic editor and print the "Value" property of the cell containing the formula =850*771 you get 65535, as you should. The "Text" property however is "100000". So it seems the problem is not in the internal computation, but in the conversion to the displayed value.
2) That said, I am not sure why, if you then enter =A1+1 into another cell you get 100001 instead of 65536. It seems the formula is picking up the displayed value, not the internal value when you perform addition, but not when you do multiplication.
3) There is something special about the value 77.1. Other variations on the calculation produce the correct result. 85 * 771 = 65535 850 * 77.1 = 100000 8500 * 7.71 = 65535
I wrote a short C program so I could see what the actual floating point representations of these numbers were:
#include #include
int main (int argc, const char *argv[]) {
if (argc != 3)
{
puts("You must enter two numbers");
}
else
{
double v1 = atof(argv[1]);
double v2 = atof(argv[2]);
double result = v1 * v2;
printf("%f * %f = %f\n", v1, v2, result);
printf("%#016I64x * %#016I64x = %#016I64x\n", *(long long *)&v1, *(long long *)&v2, *(long long *)&result);
}
return 0; }
Notice that the value 77.1 has a repeating fraction when represented in floating point. So does the result. In fact if you dig out your Intel manuals and decipher the hex representation of the result you find that it is the binary equivalent of 65534.99999999999999...
It seems that the problem occurs in the conversion of that value to displayable text.
What's worse is that there is no way to distinguish between authentic "User Account Control" dialog and a fake one that is poped up by a malicious application trying to collect admin credentials.
Here's the link.
A subsequent poster indicated he was able to locate another log file which pointed to the section of the registry whose permissions needed to be fixed.
Jeff
Me too. I got the same error message. I checked the svcpack.log file that it leaves behind in the \windows directory and it indicated that the problem occurred while doing something to the registry, but it provided no clue as what section.
I posted a query on a MS newsgroup and got a response from an MVP that indicated that it was a rights issue, that I didn't have rights to modify some section of my registry.
My suspicion is that this problem resulted from my machine having being a member of two different active directory domains during its life.
Anyhow, I threw in the towel and reformatted the disk and did a clean install of the original XP release followed by SP2. That worked just fine, but it was quite a chore to reinstall all the software I had accumulated in the two years since I last did a clean install.
Slashdot Mirror
A few observations:
1) If you go into the Visual Basic editor and print the "Value" property of the cell containing the formula =850*771 you get 65535, as you should. The "Text" property however is "100000". So it seems the problem is not in the internal computation, but in the conversion to the displayed value.
2) That said, I am not sure why, if you then enter =A1+1 into another cell you get 100001 instead of 65536. It seems the formula is picking up the displayed value, not the internal value when you perform addition, but not when you do multiplication.
3) There is something special about the value 77.1. Other variations on the calculation produce the correct result.
85 * 771 = 65535
850 * 77.1 = 100000
8500 * 7.71 = 65535
I wrote a short C program so I could see what the actual floating point representations of these numbers were:
#include
#include
int main (int argc, const char *argv[])
{
if (argc != 3)
{
puts("You must enter two numbers");
}
else
{
double v1 = atof(argv[1]);
double v2 = atof(argv[2]);
double result = v1 * v2;
printf("%f * %f = %f\n", v1, v2, result);
printf("%#016I64x * %#016I64x = %#016I64x\n", *(long long *)&v1, *(long long *)&v2, *(long long *)&result);
}
return 0;
}
This produced:
850.000000 * 77.100000 = 65535.000000
0x408a900000000000 * 0x4053466666666666 = 0x40efffdfffffffff
Notice that the value 77.1 has a repeating fraction when represented in floating point. So does the result. In fact if you dig out your Intel manuals and decipher the hex representation of the result you find that it is the binary equivalent of 65534.99999999999999...
It seems that the problem occurs in the conversion of that value to displayable text.
Actually there is a way to distinguish the UAC prompts from ones generated by a malicious application. This question is addressed in a post on the UAC blog:6 1.aspx
http://blogs.msdn.com/uac/archive/2006/05/03/5895
Here's the link. A subsequent poster indicated he was able to locate another log file which pointed to the section of the registry whose permissions needed to be fixed. Jeff
Me too. I got the same error message. I checked the svcpack.log file that it leaves behind in the \windows directory and it indicated that the problem occurred while doing something to the registry, but it provided no clue as what section.
I posted a query on a MS newsgroup and got a response from an MVP that indicated that it was a rights issue, that I didn't have rights to modify some section of my registry.
My suspicion is that this problem resulted from my machine having being a member of two different active directory domains during its life.
Anyhow, I threw in the towel and reformatted the disk and did a clean install of the original XP release followed by SP2. That worked just fine, but it was quite a chore to reinstall all the software I had accumulated in the two years since I last did a clean install.