Hmm. Well, everything in Windows is controlled by ACLs. Erm, well apparently in the distant past that was not true... But we can forget about that! Now this is something that is anticipated for inclusion into the Linux kernel, for example. 2.5? Who knows? Anyway. The interesting thing is that the whole problem in the this OpenBSD case was to do with this "mitigation" feature. That is to say, that to mitigate the problems associated with a hack against the OpenSSH system, not all r00t facilities should have been available. Unfortunately, erm, well the exploit would get around that. So, you get this situation in which a single r00t hole (and here you see the difference between 0 and 1 [dontcha love binary?]) gives you carte blanche to do whatever the fuck your black evil heart desires. Now, you might say to me, well, no fucker actually uses ACLs properly in Windows. And you would probably be right. Sigh.
You are assuming that anyone with an exploit would be jumping up and down, waving their dick in the air, shouting, "Me! Me! I have an exploit". Well, maybe they do, and meybe they don't. And maybe their dick is too small to see from where you are sitting...
??? I would say, rather, that it is good practice to use explicit casts (casts are not statements), if, and only if, implicit casts are not erm... explicit enough! Of course, as much as I like C++ (for example) implicit casts can get you into a lot of trouble if you don't have the entire ISO standard committed to memory. Fucked if I have...
I have to say, I have read this thread slowly tonight, over many beers, and have posted many replies, and I have this warm fuzzy feeling, which may be due to the beers, but I rather feel that it is because the chaps at Microsoft were completely right in this instance. Furthermore, there has been a remarkable breakout of geekness, the kind of geek brotherhood (and sisterhood of course) that we truly share with our counterparts, who currently reside in the dungeons deep inside the Microsoft campus. I speak not of the fabled pointy headed creatures, but of the grunts, who art not so different from ourselves, if everything be considered.
The packed decimal (80 bit extended) format used by the x87 (and others, I am sure) is just BCD, i.e. 4 bits per digit with 6 wasted values. There is no other reasonable way to store decimal in binary form (log2(10)~=3.322 bits) apart from... in binary! Well, I suppose, 1024~=1000, so you could get 3 decimal digits per 10 bits. Or 6 in 20 bits. A quick play with my calculator shows 59 digits in 196 bits to be quite acceptable!
0.5 can of course be stored exactly in IEEE format, it is 1.0*2^-1... Note also that IEEE doubles give you 52/log2(10) ~= 15 full digits of mantissa. However, the exponent is 10 bits plus a sign bit so you get 10/log2(10) ~= (very almost =) 3 digits of exponent. (The exponent also has a sign bit but you didn't include it in the 52 figure... 52+1+10+1=64) I don't know why you said that about packed decimal, that takes 4 bits per digit... Is there any other way?
Re:beat a-round the bush
on
Pet Bugs?
·
· Score: 2
Actually they appear to have flipped the sign bit. What a difference a bit can make!
It was suitably humble of them to admit it and update their homepage. Unfortunately, one remote hole is all you need. Such is the Unix nature.
Re:it looks like it's just a really good DOT3 bump
on
E3 Doom III Preview
·
· Score: 2
The bump map generation to which you refer can no longer be called "innovative", since people have been doing it for years. I first saw it in Krishnamurthy and Levoy 96 (underlying low resolution geometry is b-spline patches, but the principle is the same). The interesting bit is generating a good common parameterization of your low and high resolution meshes. Also see Cohen's Appearance-Preserving Simplification of Polygonal Models.
Yeah, that kind of marriage is every woman's dream... Seriously, I'm getting married in Transilvania, not the most expensive place on the planet, and I've already spent more than a thousand of your US "bucks". And it's not even in a church.
There were no decent games on the PS2 for ages after it came out. I finally bought my PS2 with Gran Turismo 3. It's OK, and Grand Theft Auto 3 is fun for a bit, but I'm still fairly unimpressed by the PS2 range. If I had any money right now I would buy a GameCube just for Super Monkey Ball. But I don't (getting married 1st June) and the rest of the GC launch titles are pretty average IMHO. Pikmin looks interesting. Anyway... E3 is upon us and there are plenty of nice games for all platforms showing up. All this fanboy squabbling is missing the point. Games games games!!! Woohoo!
It's not hard at all, you just need to do the math(s). If you're not stretching the texture, you just need to offset the quad by minus half a pixel in x and y. If you're stretching, well, it won't be 1-to-1, but it'll be a lot quicker than you can do in software...
The VIC chip always reads from RAM, that is the only way to read the contents of bytes $0000 and $0001. You stick a sprite in collision detection mode and read it one pixel/bit at a time.
I think it most likely won't. The main problem is the first two bytes in zero page, which are connected up to those IO lines. On the C64 they are connected to memory mapping and various hardware. On the 1541 they are used by the ROM.
Excuse me, but being a Christian does automatically make you stupid. For fuck's sake, give us some evidence that what you believe is true? Cite??? Idiot. I fucking despair for people like you.
Slashdot Mirror
Hmm. Well, everything in Windows is controlled by ACLs. Erm, well apparently in the distant past that was not true... But we can forget about that! Now this is something that is anticipated for inclusion into the Linux kernel, for example. 2.5? Who knows?
Anyway. The interesting thing is that the whole problem in the this OpenBSD case was to do with this "mitigation" feature. That is to say, that to mitigate the problems associated with a hack against the OpenSSH system, not all r00t facilities should have been available. Unfortunately, erm, well the exploit would get around that. So, you get this situation in which a single r00t hole (and here you see the difference between 0 and 1 [dontcha love binary?]) gives you carte blanche to do whatever the fuck your black evil heart desires.
Now, you might say to me, well, no fucker actually uses ACLs properly in Windows.
And you would probably be right.
Sigh.
You are assuming that anyone with an exploit would be jumping up and down, waving their dick in the air, shouting, "Me! Me! I have an exploit". Well, maybe they do, and meybe they don't. And maybe their dick is too small to see from where you are sitting...
??? I would say, rather, that it is good practice to use explicit casts (casts are not statements), if, and only if, implicit casts are not erm... explicit enough! Of course, as much as I like C++ (for example) implicit casts can get you into a lot of trouble if you don't have the entire ISO standard committed to memory. Fucked if I have...
Yeah, about 10.000000000001% of them!
That's not a bug! It's a feature! If you rely on it behaving like an integer loop, then it is a bug, but it is your bug, not Applesoft's!
I believe you meant $cfff and $cf00...
I have to say, I have read this thread slowly tonight, over many beers, and have posted many replies, and I have this warm fuzzy feeling, which may be due to the beers, but I rather feel that it is because the chaps at Microsoft were completely right in this instance. Furthermore, there has been a remarkable breakout of geekness, the kind of geek brotherhood (and sisterhood of course) that we truly share with our counterparts, who currently reside in the dungeons deep inside the Microsoft campus. I speak not of the fabled pointy headed creatures, but of the grunts, who art not so different from ourselves, if everything be considered.
Oh the times you wish people forgot to check "Post Anonymously"!
Solution: leave the debug code in?
Only joking!
The packed decimal (80 bit extended) format used by the x87 (and others, I am sure) is just BCD, i.e. 4 bits per digit with 6 wasted values. There is no other reasonable way to store decimal in binary form (log2(10)~=3.322 bits) apart from... in binary!
Well, I suppose, 1024~=1000, so you could get 3 decimal digits per 10 bits. Or 6 in 20 bits. A quick play with my calculator shows 59 digits in 196 bits to be quite acceptable!
0.5 can of course be stored exactly in IEEE format, it is 1.0*2^-1 ...
Note also that IEEE doubles give you 52/log2(10) ~= 15 full digits of mantissa. However, the exponent is 10 bits plus a sign bit so you get 10/log2(10) ~= (very almost =) 3 digits of exponent. (The exponent also has a sign bit but you didn't include it in the 52 figure... 52+1+10+1=64)
I don't know why you said that about packed decimal, that takes 4 bits per digit... Is there any other way?
Actually they appear to have flipped the sign bit. What a difference a bit can make!
That would be pure speculation on your part.
It was suitably humble of them to admit it and update their homepage.
Unfortunately, one remote hole is all you need. Such is the Unix nature.
The bump map generation to which you refer can no longer be called "innovative", since people have been doing it for years. I first saw it in Krishnamurthy and Levoy 96 (underlying low resolution geometry is b-spline patches, but the principle is the same).
The interesting bit is generating a good common parameterization of your low and high resolution meshes.
Also see Cohen's Appearance-Preserving Simplification of Polygonal Models.
Yeah, that kind of marriage is every woman's dream...
Seriously, I'm getting married in Transilvania, not the most expensive place on the planet, and I've already spent more than a thousand of your US "bucks". And it's not even in a church.
There were no decent games on the PS2 for ages after it came out. I finally bought my PS2 with Gran Turismo 3. It's OK, and Grand Theft Auto 3 is fun for a bit, but I'm still fairly unimpressed by the PS2 range.
If I had any money right now I would buy a GameCube just for Super Monkey Ball. But I don't (getting married 1st June) and the rest of the GC launch titles are pretty average IMHO. Pikmin looks interesting.
Anyway... E3 is upon us and there are plenty of nice games for all platforms showing up. All this fanboy squabbling is missing the point. Games games games!!! Woohoo!
They were assimilated by nVidia ages ago... Wakey wakey!
... or just stick with the less decent monitor and keep the higher frame rate... LOL
"Like any other technology, it is not good or evil in and of itself. It just is. What people do with it is either good or evil."
That's right, and when I finish building my "Death Ray", I will only use it for good.
Honest.
It's not hard at all, you just need to do the math(s). If you're not stretching the texture, you just need to offset the quad by minus half a pixel in x and y. If you're stretching, well, it won't be 1-to-1, but it'll be a lot quicker than you can do in software...
The VIC chip always reads from RAM, that is the only way to read the contents of bytes $0000 and $0001. You stick a sprite in collision detection mode and read it one pixel/bit at a time.
I think it most likely won't. The main problem is the first two bytes in zero page, which are connected up to those IO lines. On the C64 they are connected to memory mapping and various hardware. On the 1541 they are used by the ROM.
Excuse me, but being a Christian does automatically make you stupid. For fuck's sake, give us some evidence that what you believe is true? Cite??? Idiot. I fucking despair for people like you.
Only in a use16 code segment ;-)