"Show me another process that can give the same kind of energy gain - 8 to 10 : 1, in the same volume, easily transported and stored. To the best of my knowledge, there isn't one."
Uranium. Beats the shit out of it.
And you're neglecting the power draw from cracking plants, the energy used during the transportation of the oil, and the fact that internal combustion engines are around 25% efficient. All incur losses to your quoted 10/8:1 ratio.
Also, as far as waste is concerned: while uranium is radioactive, it's not like it wasn't when it was in the ground. The only pollution is heated water (which is a problem, but not like incompletely-combusted hydrocarbon reactions) and the spent pellets. Oh well, the total background radiation on Earth will not change.
I believe all this crap has been merged into the North Bridge, but back in the pre-pentium days, you had an Intel 8259 PIC or equivalent that generated an interrupt on IRQ 8 (I have since forgotten what vector that relates to). As a default, that chip generated a pulse 18.2 times a second.
If you were so inclined, you could hijack this timer. Divide 0x1234DD by the frequency you want to pulse at, write the byte value 0x34 to port 0x43, to tell the PIC you want to write, then send (result % 0x100) to 0x40, then (result / 0x100) 0x40. If you wanted to go back, you write zeros.
You had to monkey around with the BIOS clock handler too. Save the vector, call it when necessary based on your frequency or else you'd do what MS Flight Sim 4 did and throw off the system clock until next reboot.
I agree. You can watch all you like, but when some guy manages to sneak in a carbon fiber knife and slaughters 20 people before the guards get there, all these multimillion dollar cameras really did was provide the guys in the viewing room a spectacular shot of it.
See, I look at it this way: they pretend this "surveillance" is an ACTIVE defense. That's silly. Prominent and well-trained security are the best. Besides, nothing is ever going to stop a guy hellbent on causing damage. You will never stop a guy with a row of pipebombs under his coat who is willing to die.
Cameras are only good for proving an incident happened, IMO. And they aren't even that good without a proper chain of evidence to back them up.
It's unfortuneate you can't just put that in an interest bearing account. That sort of puts the screws to the public because, as you state, you tie that money up, it can't be used.
Heh, your last line (despite its intent;) ) reminds me of when I was in highschool. As budding programmer, I was pretty damn quick on the keyboard, even one-handed (due to some combination of laziness and possibly *that*). In English class, we all were in the lab typing our papers. I think I was fooling around with Word Macros or some bolonga because I hated English class, so I was just screwing around with one hand on the keyboard and one hand holding my head at a slant. My teacher must not have noticed I was just zombied out, because on my report card, along with the D I so proudly earned, my teacher wrote that I needed to learn touch typing. Pfft. $100 says I could out-type her one-handed.
Jiffylube does the same shit, believe it or not. If you invent a faster way of changing oil and you are an employee of Jiffylube at the time, they will claim ownership of it. Jiffylube, for those of you who don't know, is one of those 15 minute oil-change garages that hires mostly highschool-level wanna-be mechanics. Seems kind of on the border of "we own you 24/7 while under the employ of JiffyLube". Seriously, if a company tried to claim ownership of anything I invented on my own watch, they'd be at the bottom of a lake by the morning.
What kind of programmer? If you're a systems programmer, I'm gonna cry. Not to be mean, but the whole x86-64 architecture is incredible compared to the old IA-32. EIGHT more (visible) GP registers! EIGHT! Wider MM registers. More FP registers, IIRC.
Not only can you utilize more physical memory, but you can map a larger amount of virtual memory, which is particularly going to be useful once people have 2-3GB of RAM and video cards have aperture sizes into the 512-768MB range, you start running out of 32-bit addressable space.
Then don't forget the arithmetic aspect of it either. If you've never overflowed a 32-bit register, then you haven't lived, man!!!:p
I agree. I think that the single player campaign was a sort of "proof of concept" and that Bioware was testing the waters to see how far the Mod community would take the game.
Ever since I saw that promo with the little Sony robots that did the fan dancing to the music, I imagined hundreds of little bipedal robots just running through a city, minigun in hand, shooting everything in its path, powered by swarm AI. Scary future we have set ourselves up for. I hope that as a species, we are smart enough to not let it go too far.
Go look it up if you do not trust me. There was certainly a virus that attempted to break your monitor. I have a VGA/EGA programming manual, the contents of which TELL YOU how to do precisely that. There is no way since at least the EGA and probably the CGA to 'mismatch' a video adapter, because they are programmable.
You know what, here, enjoy:
Misc Output Register
Port 0x3C2, index 0x00 -> This register controls the polarity of sync outputs to the display as well as video clock rate. Display damage will result from OOB values.
Reset Register
Port 0x3C5, index 0x00 -> Write 0x00 to this port, if left for an extended period of time, display damage will result.
Clock Mode Register
Ports 0x3C4 and 0x3C5, index 0x01 -> Configures timing circuits of the sequencer. You get the idea.
AND THE BIG ONE
CRT CONTROLLER RESGISTERS
Ports 0x3B4/0x3D4 and 0x3B5/0x3D5, indices 0x00-0x07 0x10-0x12 0x15-0x17 -> Controls CRT timing, Horizontal and Vertical Retrace, Blanking, Start and End. Monitor damage can result from improper values.
Wow, who would have thunk it?
I'll admit that I can't find a lick of information about any hard disk failure virus. I'm still sure there was one, but I can't support it. Let's pretend there was, you simply write a virus that overtakes the BIOS timer and disk interrupt handlers so the normal operation of the PC would be unaffected.
Also, I quote, 'Note that I refrain from calling you "retarded..."' Then do it, motherfucker! You've gone so far as to write the actual words, you may as well go all out. Is that some sort of disclaimer?
Continuing, you obviously can READ, I was calling to attention your COMPREHENSION skills, because they are obviously lacking. You said I was wrong (which I'm obviously not, as proven above) then you said the exact same goddamn thing I did. So are we done here?
I don't belive any native 32-bit Protected Mode 80386 and above operating environment can run without an MMU. If you could get Windows to run in real mode, I think you could do it.
The one nitpick I have with your statement is about security. MS has gotten their act together with reliability and somewhat with 'playing nice', although it pisses me off how they fuck with standards like XML, but they aren't secure at all. Nothing to do with closed source vs open source, but their development model was not designed securely from the start, and now it's biting them in the proverbial ass.
Hopefully with the inclusion of the NX flag-aware code, most buffer overflow attacks will just throw an exception and DOS the service instead of allowing an attacker to root it, but the fact remains that the service is still down.
Yeah... Shit like that gets real old, real fast. Like the 'real' DB guy is doing something hard. Please. I think people like that need to step back and see that there are a lot harder things involving computers than doing 'real' DB dev. Then maybe they'll get off their high horse and shut the fuck up for once.
Mafia put Uranium pellets in some guy's desk and
he died 6 months or so later. Sometimes people just want your ass to suffer with no real trace back to them. No need for off-the-wall, knee-jerk posts like that.
I think that spin-up amperage might be a bit higher (like a fan, where the initial current draw is very high but the mean draw is lower). But then again, I could be wrong.
This site harbors some real gems, *sigh*...
First, you *just* said monitors COULD be over driven. Just like I did, I even disclaimed it in a similar manner. Yet you chose to write stupid shit. So, what the fuck? Why? Why be retarded and piss me off? Can't you read? FYI, there was at least one virus that exploited the VGA 0x3C0 write port.
Second, from what I remember, the disk failure virus simply ran the drive until it failed. It didn't overspin it, it just wrote and wrote and wrote until the drive gave up.
No, you can cause physical damage with a virus. Monitors were especially susceptible to that before they had built-in frequency limiting, you could overdrive them and that was the end of that. Hard disks could be spun to the point of failure, etc.
Slashdot Mirror
And you're neglecting the power draw from cracking plants, the energy used during the transportation of the oil, and the fact that internal combustion engines are around 25% efficient. All incur losses to your quoted 10/8:1 ratio.
Also, as far as waste is concerned: while uranium is radioactive, it's not like it wasn't when it was in the ground. The only pollution is heated water (which is a problem, but not like incompletely-combusted hydrocarbon reactions) and the spent pellets. Oh well, the total background radiation on Earth will not change.
Extreme examples prove nothing. This kid's future is fucked, maybe he can be rehibilitated so he isn't a drain on society when he gets out.
Now I obviously don't believe child molesters should be given second chances, but this is a far less severe circumstance.
I believe all this crap has been merged into the North Bridge, but back in the pre-pentium days, you had an Intel 8259 PIC or equivalent that generated an interrupt on IRQ 8 (I have since forgotten what vector that relates to). As a default, that chip generated a pulse 18.2 times a second.
If you were so inclined, you could hijack this timer. Divide 0x1234DD by the frequency you want to pulse at, write the byte value 0x34 to port 0x43, to tell the PIC you want to write, then send (result % 0x100) to 0x40, then (result / 0x100) 0x40. If you wanted to go back, you write zeros.
You had to monkey around with the BIOS clock handler too. Save the vector, call it when necessary based on your frequency or else you'd do what MS Flight Sim 4 did and throw off the system clock until next reboot.
I agree. You can watch all you like, but when some guy manages to sneak in a carbon fiber knife and slaughters 20 people before the guards get there, all these multimillion dollar cameras really did was provide the guys in the viewing room a spectacular shot of it.
See, I look at it this way: they pretend this "surveillance" is an ACTIVE defense. That's silly. Prominent and well-trained security are the best. Besides, nothing is ever going to stop a guy hellbent on causing damage. You will never stop a guy with a row of pipebombs under his coat who is willing to die.
Cameras are only good for proving an incident happened, IMO. And they aren't even that good without a proper chain of evidence to back them up.
It's unfortuneate you can't just put that in an interest bearing account. That sort of puts the screws to the public because, as you state, you tie that money up, it can't be used.
Oil changes are retardedly simple. So yes, I "really think" it's possible.
Heh, your last line (despite its intent ;) ) reminds me of when I was in highschool. As budding programmer, I was pretty damn quick on the keyboard, even one-handed (due to some combination of laziness and possibly *that*). In English class, we all were in the lab typing our papers. I think I was fooling around with Word Macros or some bolonga because I hated English class, so I was just screwing around with one hand on the keyboard and one hand holding my head at a slant. My teacher must not have noticed I was just zombied out, because on my report card, along with the D I so proudly earned, my teacher wrote that I needed to learn touch typing. Pfft. $100 says I could out-type her one-handed.
Jiffylube does the same shit, believe it or not. If you invent a faster way of changing oil and you are an employee of Jiffylube at the time, they will claim ownership of it. Jiffylube, for those of you who don't know, is one of those 15 minute oil-change garages that hires mostly highschool-level wanna-be mechanics. Seems kind of on the border of "we own you 24/7 while under the employ of JiffyLube". Seriously, if a company tried to claim ownership of anything I invented on my own watch, they'd be at the bottom of a lake by the morning.
Medco all the way.
What? You have to be kidding... You're talking out of your ass, buddy. Smells like astroturfing to me.
What kind of programmer? If you're a systems programmer, I'm gonna cry. Not to be mean, but the whole x86-64 architecture is incredible compared to the old IA-32. EIGHT more (visible) GP registers! EIGHT! Wider MM registers. More FP registers, IIRC.
:p
Not only can you utilize more physical memory, but you can map a larger amount of virtual memory, which is particularly going to be useful once people have 2-3GB of RAM and video cards have aperture sizes into the 512-768MB range, you start running out of 32-bit addressable space.
Then don't forget the arithmetic aspect of it either. If you've never overflowed a 32-bit register, then you haven't lived, man!!!
Don't AMD and Intel have a massive cross-licensing agreement? And aside from that, IBM is giving AMD a pretty big hand on their proc technology.
I agree. I think that the single player campaign was a sort of "proof of concept" and that Bioware was testing the waters to see how far the Mod community would take the game.
Ever since I saw that promo with the little Sony robots that did the fan dancing to the music, I imagined hundreds of little bipedal robots just running through a city, minigun in hand, shooting everything in its path, powered by swarm AI. Scary future we have set ourselves up for. I hope that as a species, we are smart enough to not let it go too far.
Did anyone else read that as "NIST Studies Virus, DDoS Effect on Girls?"
I suppose DDoS'ing a girl is a pretty good way to give her a virus.
I got up to finger and BASH freaked. ^C took care of that, then fsck started warning me that I was about to rape my drives. The rest didn't do much.
Go look it up if you do not trust me. There was certainly a virus that attempted to break your monitor. I have a VGA/EGA programming manual, the contents of which TELL YOU how to do precisely that. There is no way since at least the EGA and probably the CGA to 'mismatch' a video adapter, because they are programmable.
You know what, here, enjoy:
Misc Output Register
Port 0x3C2, index 0x00 -> This register controls the polarity of sync outputs to the display as well as video clock rate. Display damage will result from OOB values.
Reset Register
Port 0x3C5, index 0x00 -> Write 0x00 to this port, if left for an extended period of time, display damage will result.
Clock Mode Register
Ports 0x3C4 and 0x3C5, index 0x01 -> Configures timing circuits of the sequencer. You get the idea.
AND THE BIG ONE
CRT CONTROLLER RESGISTERS
Ports 0x3B4/0x3D4 and 0x3B5/0x3D5, indices 0x00-0x07 0x10-0x12 0x15-0x17 -> Controls CRT timing, Horizontal and Vertical Retrace, Blanking, Start and End. Monitor damage can result from improper values.
Wow, who would have thunk it?
I'll admit that I can't find a lick of information about any hard disk failure virus. I'm still sure there was one, but I can't support it. Let's pretend there was, you simply write a virus that overtakes the BIOS timer and disk interrupt handlers so the normal operation of the PC would be unaffected.
Also, I quote, 'Note that I refrain from calling you "retarded..."' Then do it, motherfucker! You've gone so far as to write the actual words, you may as well go all out. Is that some sort of disclaimer?
Continuing, you obviously can READ, I was calling to attention your COMPREHENSION skills, because they are obviously lacking. You said I was wrong (which I'm obviously not, as proven above) then you said the exact same goddamn thing I did. So are we done here?
I don't belive any native 32-bit Protected Mode 80386 and above operating environment can run without an MMU. If you could get Windows to run in real mode, I think you could do it.
The one nitpick I have with your statement is about security. MS has gotten their act together with reliability and somewhat with 'playing nice', although it pisses me off how they fuck with standards like XML, but they aren't secure at all. Nothing to do with closed source vs open source, but their development model was not designed securely from the start, and now it's biting them in the proverbial ass.
Hopefully with the inclusion of the NX flag-aware code, most buffer overflow attacks will just throw an exception and DOS the service instead of allowing an attacker to root it, but the fact remains that the service is still down.
Yeah... Shit like that gets real old, real fast. Like the 'real' DB guy is doing something hard. Please. I think people like that need to step back and see that there are a lot harder things involving computers than doing 'real' DB dev. Then maybe they'll get off their high horse and shut the fuck up for once.
Mafia put Uranium pellets in some guy's desk and he died 6 months or so later. Sometimes people just want your ass to suffer with no real trace back to them. No need for off-the-wall, knee-jerk posts like that.
Because, hopefully, in the long run, humans will finally realize that being a greedy shit won't help anyone?
I think that spin-up amperage might be a bit higher (like a fan, where the initial current draw is very high but the mean draw is lower). But then again, I could be wrong.
This site harbors some real gems, *sigh*...
First, you *just* said monitors COULD be over driven. Just like I did, I even disclaimed it in a similar manner. Yet you chose to write stupid shit. So, what the fuck? Why? Why be retarded and piss me off? Can't you read? FYI, there was at least one virus that exploited the VGA 0x3C0 write port.
Second, from what I remember, the disk failure virus simply ran the drive until it failed. It didn't overspin it, it just wrote and wrote and wrote until the drive gave up.
No, you can cause physical damage with a virus. Monitors were especially susceptible to that before they had built-in frequency limiting, you could overdrive them and that was the end of that. Hard disks could be spun to the point of failure, etc.