Slashdot Mirror
AMD's 64-Bit Chip
EyesWideOpen writes "AMD is set to release a 64-bit chip early next year which will be completely backwards compatible with the Athlon line. The current 64-bit offering from Intel, Itanium, is an entirely new chip that has no backwards compatibility with its x86 line of chips (from the 8080 chip to the Pentium IV) and is designed only for high end servers. AMD's solution to this problem is the Opteron chip (product info) which will be in servers, desktops and laptops. Here is a wired article."
I've seen duplicate stories, but this beats them all! :)
They that quote Benjamin Franklin on liberty and safety deserve neither.
First off I must admit that I am a staunch supporter of President Bush's 'War On Terror'. However when I first read this article (The Drudge Report is my AOL homepage), I thought it was a stupid idea to even consider recruiting someone above the age of 16 to spy on their neighbours. The best way to go about this would be to teach young children to keep a close eye upon their parents and neighbours. This would best be taught in the state run schools that cost so much tax payer money, and refuse to swear to the Pledge of Alligance. By teaching them to watch over America, there would be a huge re-injection of patriotism back into the education system. Using children, has a number of advantages because children are more likely to go along with orders delivered by a state authority. Secondly, they are innocent, and would be able to gather information readily without raising suspicions of the terrorists they would surveil. And lastly they could be rewarded easily and cheaply with videogames and candy etc. Lastly, the Boy Scouts of America could be put to use, by doing reconnaissance missions in the remoter regions of the American wilderness; the Girl Guides could supply them with food. I'm sure the terrorist camp in Oregon would never of formed if there were 100 Boy Scouts roaming the wilderness looking for Arabs every weekend. In general I support the idea, but think it needs to be reworked to include only children to be the most effective.
I believe this story is at least a year or two old
With Intel, you are basically buying a name. I've found AMD processors to be more reliable. With backwards compatibility, this will make powerful 64 bit apprications available to the general public, and the server industry will have a boom. AMD has finally surpassed Intel.
We're Doomed
Slow day, huh?
Pedro Côrte-Real.
Dismiss this as karma whoring all you want, but I'm still going to state that I'm completely in favor of the whole backwards-compatible thing. From the PS2 to the new AMD chips, this is a trend that hopefully catches on. What's the point of making something that is unsupported by a large chunk of today's software unless it's to make obscene amounts of money. . .er, nevermind. I think I answered my own question. You can all go back to your day now
- Relativistic? That's barely Newtonian!
Ever since Intel released that the "next" processor would be incompatiable with the x86, I've been waiting for AMD to pick it up. A 64-bit x86 is just what the doctor ordered; easy to port too, and runs all of your old software to boot at a decent speed.
The Wired article was not bad (except for the typo about 1995 being the release of the 386 instead of 1985). And it's very true, would YOU expect your DVD player NOT to play your CDs? Not me.
BWP
Running programs in a hybrid 32/16 bit environment puts a serious strain on the Windows OS: It crashes. Pure systems do not crash as often. I really wonder if the problem will be magnified in a 32/64 bit environment?
We're Doomed
Interesting how Intel is the one breaking backwards compatibility, and AMD is keeping it in their chips. Intel, who historically have favored compatibility over moving forward with radical new technology. And AMD, who recently have been the underdogs with more innovative, higher-performing chips.
I'll bet everyone here is going to be singing the praises of AMD for making their 64-bit chip backwards compatible with x86. The very same people who have been spending the past several years decrying the evil of Intel for maintaining compatibility to such an outdated architecture.
Interesting eh?
Ford Motor Co. is set to release today a new car, the Model "A", based on the award winning and famously popular Model "T". The new Model "A" is backwards compatible with all previous 4 wheel gasoline powered Model "T" cars produced by Ford and its competitors, and can run on the same roads as them.
Infuriate left and right
Unfortunately, AMD may make great chips but I really don't see anything out there from the big/stable/well-tested motherboard makers that would make me want to use any AMD technology in a mission critical system. Case in point, I have a dual-proc P3-500 running Linux that has an uptime of 342 days. It runs on my internal network as a print/file/app server for a windows network. I tried running an Athlon system but it would randomly lock up once ever 120-145 hours. We finally traced the problem to a manufacturing defect in a whole batch of motherboards. I ended up replacing the motherboard and now it runs as a windows system in one of the kids rooms since it doesn't need long up times. AMD has to get the chipsets working in a stable fashion such that they can be trust for "real work"(tm).
Cactus?
Do we have to go through the whole "64 -bit code is twice as big as 32-bit code" bloatware excuse again?
Both the Itanium and the Itanium 2 will run x86 code. For details see: http://h21007.www2.hp.com/dspp/files/unprotected/i tanium2.pdf
fix story subject
I've been waiting for these bad mama jamas. I must have spent a week trying to install OS X on my Athlon XP. I couldn't believe how rude the tech support at Apple was, even though I tried to switch. I thought that Quartz would make the windows framing my porn look pretty, but I haven't had a chance to see. I hope this 64 bit CPUs change all that. I used to write 64 bit assembler programs all the time, but they never compiled and linked right. I blame the makers of GeOS, that had to have been the worst IDE I've ever seen for ASM.
This article is WRONG. Itanium *IS* backwards compatible with x86 code. It is just not native code, therefore it is slower. But it runs 32-bit versions of Windows and Linux JUST FINE.
I believe this article is pure FUD in favor of AMD. Please update the news story.
Maybe someone should send that dude some 64-bitness to his penis to make it bigger....
I'll definitely go for this. So long as Zalman is already in the works to making big enough Heatsink/Fan. This might be the first chip that recommends liquid cooling of somesort.
If you think
time to think about the LADIES, pudding-hole. suck my craphatch dry you retarded faggot-ass queer.
Last week I had gone swimming to a lovely beach near Bombay. It was secluded and my best friend Katy said she would come with me too. I hadn't shaved my armpits since I was a teenager and in the past fifteen years it had grown to quite enormous proportions. The thick jet-black bushy hair in my unshaven armpits was a sight especially when I raised my arms overhead.
I hadn't known Katy for long but she was very beautiful and I longed to seduce her. I knew that she was depressed, as she had broken up with her boyfriend.
As we drove to my beach house I looked at her. She was in a traditional Indian sari. Her blouse was tight and her breasts seemed large and appetizing. I longed to put my mouth and suck at her succulent melons. I wondered if she was hairy. Was her pubic hair thick and bushy like mine or was it trimmed. Her sleeved blouse did not show whether her armpits were hairy. How I longed it to be thick and bushy and whether she liked hairy women. How would she react when she saw my hirsute body?
I put my thoughts behind me as we reached the house. She went to her room to unpack. I called to her to put on her swimsuit while I went to my room to change. She soon called to me "Bela why don't we go to the pool instead of the beach, we can go to the beach tomorrow" I wondered why and quickly changed into my bikini.
As I went to the pool I noticed that she had her arms pressed to her side. She asked me "Do you have a razor."
"Why" I answered. She said "I want to shave my underarms as I couldn't shave it before coming."
"Wow" I said "neither have I shaved in the past fifteen years" I said as I lifted my arms "Look at my bushy armpits" She put her hands to her mouth as stared at my uncovered armpits the jet black bushy hair jutting out of my armpits. As looked towards my panties, the pubic hair was also clearly visible from the sides and the top of my bikini. She exclaimed, "I have never seen anybody as hairy as you"
I then bent and kissed Katy deeply in her mouth. She sucked in my tongue just the same way. Then I kissed her on both of her bare shoulders. Her hairy armpits having a special attraction to me. She then pulled down her bikini bottom just enough to uncover her bushy pubes. Was her pussy hair as thick and as hairy as her armpit hair?
I got on my knees and licked at the top of her bikini. Katy now had her hands behind her head exposing both of her sexy bushy armpits. I wanted desperately to run my tongue through that gorgeous black tuft of armpit hair, but I buried my nose in the middle of her thick black pussy hair. I moaned out loud at the strong musky scent of her pubes. I took several strands of hair between my teeth. Katy moaned out slightly herself as I did this. She moaned even louder as I ran my tongue all around in her beautiful bush and munched on her pubes with my hungry mouth.
I removed her bikini top so I could feel her huge pair of tits against my chest. Katy's tits fell out of the top. Katy's tits fascinated me. They were huge. I played with them for what seemed like hours, kissing all around one tit while playing with the other, as I tugged at her tufty armpits.
She looked at my pussy hair sticking out the bottom of my bikini. She said that my pussy was so thick and bushy there was even hair growing on the inside of my thighs that was also sticking out my bikini. I looked down toward her pubic area. She smiled at me as she pulled back the bottom of her bikini so I could see her cunt in its entire furry splendor.
Katy once again lifted up her arms to expose her very hairy armpits. She said she sometimes went for months without shaving her armpits. I found myself loving the sight of her s unshaven pits
I told her I wanted her to lick my bushy armpits" Have you done it before"
"No" she said. "Do you want to lick my hairy underarms?" I asked her. "Yes," Katy replied, her voice almost speaking to herself, as she nodded her head. "Would you like to have a lick?" She moaned out a simple and lustful, "Yes."
I lowered my armpits and she stuck out her tongue and has a lick, her tongue grazed the thick bushy hair. Was I in seventh heaven?
Well, I suppose your reaction to this depends on your personal product loyalty (or possibly lack thereof). Basically, a CPU will inherently run slower if it is backwards compatible with a completely different architecture. What AMD needs is a chip that solely does 64-bit ops, like the Itanium. Now, I realize that this would require all programs to be recompiled/rewritten, but isn't that what PDA's require anyways? And I'm sure the conversion from 32-bit to 64-bit is a lot easier than 32-bit to Async (could someone familiar with that process verify/refute this?).
This is, in essence, what I'm saying: AMD should come out with 2 64-bit processors, only one of which natively supports 32-bit apps. Why? Otherwise Intel will absolutely rip AMD to shreds in the benchmarks test. Being a loyal AMD user, I don't want to see this.
IWARS.
People, in general, disappoint me. Politicians even more so.
With an opteron running a 32 bit app is that app limited to a 4gb limit, or can it address above 4gb? If it can then the opteron is immediately useful, as one wouldn't have to wait for 64 bit versions of photoshop, maya, xsi, etc to reap some benefits. The same can't be said for the itanium, as it would be running all the apps through a slow and flaky emulator.
...it'll be about a year past the release date of these chips that I may be able to afford to upgrade what I need to use them with all their 'Greatness'(tm) . Witnesses on scene reported that two years might be a better estimate...
Jesus saves souls and redeems them for valuable cash prizes
SONY. Because caucasians are just too damn tall.
Credits: anonymous
"Mmmm... this feels good..." I sighed.
"Shhh!" hissed Hemos. "We don't want Mark to come in here!"
True. Having Hemos's 16 year-old brother walk in on us at that moment would not be good. I didn't think he'd be too cool with finding his 12 year-old brother lying naked with me, holding my 11 year-old dick in his hands. But, in all fairness, my hands were eagerly playing with Hemos's dick and balls at that moment, too.
Hemos's mom and dad had gone to the drive-in, leaving his big brother in charge. In our favor, leaving Mark in charge pretty much guaranteed that we weren't to bother him, and in turn, he'd leave us alone unless we were making too much noise or breaking something. Well, we were being careful to keep quiet because we very much wanted to be left alone.
We were in Hemos's twin bed, snuggled under the covers with our underwear pushed down to the foot of the bed. The only illumination in the room came from the faint sliver of light that crept in under his bedroom door. Even in the shadows I could make out the shape of my friend; about my height, but heavier. (Hell, I was such a skinny runt that everyone was heavier than me.) Hemos had a crew-cut of white-blonde hair, and was only starting to sprout some pubic hair. But, you had to feel for it because what little pubic hair he possessed was as blonde as the short hair on his hea and could not yet be seen by even a minimal distance.
And, I was happily feeling for it, running my hands all over Hemos's slightly larger erection and fondling his larger testicles while he courteously stroked my dick. I could tell that he didn't possess the same enthusiasm for cockplay as I did, unless you count his appreciation for the attention devoted to his member. And I knew that my willingness to satisfy his sexual urges was one of the few reasons he even had me sleep over at his place. But, I didn't let that stop me from finding pleasure in the handling of his meat.
I'd recently had an "introduction", of sorts, to seeing what someone could do with a man's dick with their mouth. While spending the night with my Uncle Jerry a couple weeks before, while I watched in secret, I was treated to a visual display of the intensity and unabashed pleasure that my uncle had obviously enjoyed having another man suck on his cock. From that moment on, I had a yearning that I needed to satisfy. With who was my only question.
I guess it was time to find out.
"I... heard that sucking on it feels even better than playing with it." I ventured.
In the darkness, I could feel a slight jerk of revulsion in Hemos's body.
"Put a dick in your mouth?" he croaked.
"Well, " I countered, my heart pounding with anxiety, "I think adults do it all the time."
"Well, I'm not gonna do it!" Hemos hissed. "That's homo stuff!"
"Yeah." I sighed disappointedly, while still playing with Hemos's dick. "I guess it is."
As I stroked his shaft in a steadier, milking rhythm, I could sense Hemos's breaths getting quicker. His manipulations of my dick began to falter as I could feel his body tense beside me. His hips rocked slightly in time with my pumping of his cock, and I cradled his balls tenderly in my other hand. When any attentions to my own dick has completely ebbed, I knew what was about to happen, so I picked up the pace just a bit more while lending a touch more pressure in my grip. Finally, Hemos's breath caught in his throat, and he turned his face fully into his pillow to stifle the moans that broke free as his cock pulsed and throbbed in a dry orgasm within my hands. I continued to massage him and didn't release him from my grasp until his member had gone fully soft.
"Man," sighed Hemos dreamily after finally catching his breath. "You are so good at that, CmdrTaco."
At least I had something to be proud of, I guess, as my friend gently withdrew himself from me and rolled onto his back.
Even though I was only eleven, the irony of Hemos's words and actions were not lost on me. My sucking on him would have been a "homo" thing, but beating him off was okay. Go figure. Within the few moments I had spent mulling over the irony of the thoughts, Hemos had drifted off to sleep. I slipped out from under the covers and down to the cool floor so I could masturbate without shaking the bed. As I toyed with my own dick, I imagined Hemos's cock in my mouth, wondering if the chance would ever really come. Finally, my own climax washed over me, and I got back into the bed.
I don't sleep real well to begin with, and even worse when I'm not in my own bed. And now, with the thoughts of a dick so close to me, as well as the vivid memories of secretly seeing man-to-man cocksucking pleasure floating through my prepubescent, sex-filled brain, I was not about to fall asleep anytime soon. Lying awake until around 11:30, I finally decided that I needed to do something to satisfy my hungers, or I'd never be able to let it rest. The trick was in finding the guts to follow through.
I knew that whenever Hemos fell asleep, he pretty much stayed asleep. So, since he was sleeping soundly, lying on his back, I took a deep breath and gingerly ducked my head under the covers and scooted down as much as I could to the foot of the bed. That put my head right at Hemos's hip level. I raised my head and upper body to help create a tent over his crotch. Sniffing around, I found the faint scent of young penis flesh. I inhaled deeply, both in the love of the scent, and in an attempt to slow my pounding heart. I opened my mouth wide over the area where I sensed Hemos's dick to be, and lowered my mouth squarely over his soft cock and balls until I could feel his sparse pubic hairs tickling my cheek. I finally had a dick in my mouth! I just wasn't sure what I'd do if Hemos woke to find his "homo" friend in this situation.
I remained like that for a long moment, partially in fear of trying anything more, and partly to savor the moment. I carefully let my tongue start to explore his tender penile flesh, enjoying the texture. Then came the excitement that welled within me as his cock began to respond to my attentions and harden in my warm and wet mouth! Butterflies seemed to explode in my stomach and drown out my heartbeat as I felt his dick get to its full size in my mouth. Concentrating in that dark environment, I found myself beginning to identify the shape of his member by taste. The shaft actually seemed to taste different than the head, and the thin skin of his scrotum seemed to harbor another distinct flavor.
I started to softly suck on Hemos's dick, becoming fascinated at how it just seemed to, well, 'fit' in my mouth... how the head lent itself to the back of my tongue, and how the shaft rested between my tongue and the roof of my mouth. My excitement was so great that my own recently satisfied dick was responding again, inviting me to play. I was sucking a cock, and I was in heaven!
However, within seconds, Hemos seemed to get restless. In fear, I quickly pulled my mouth away from Hemos's candy stick and held still. The covers rustled, and pulled back.
"Whatcha doin'?" mumbled Hemos.
"I... uh... was trying to find my shorts down here," I lied, starting to fumble near our feet. Well, partial lie, because it was a good idea to do so, anyway, and now was as good a time as any.
"Oh, yeah," said Hemos. "Get mine, too, willya?"
"S-sure" I stammered, relieved.
I located the two items of clothing and scooted back up towards the head of the bed. Thankfully, our underwear were pretty easy to distinguish since Hemos wore boxers, and I wore briefs. We both fumbled to put them on in the dark, and then settled back into the bed. I lay stiffly on my back, still harboring some fear that my friend discovered more than he let on, but Hemos simply rolled onto his side, facing away from me, and promptly went back to sleep.
And, here I was again, so close to my fantasies, yet still so far.
And very much awake.
After hearing the clock in the hallway chime midnight, I finally got up to go to the bathroom. Figuring it was late enough not to be an issue, and since even if Hemos's parents were home that they would be in their own bedroom downstairs, I didn't bother to slip on my pants for the short trip down the hall. I walked softly to the bedroom door, and then stepped out into the hallway, illuminated dimly by a bare-bulb night light. I walked past big brother Mark's door to the bathroom at the end of the hall and turned on the light as I shut the door.
Peeing into the toilet, I looked up at my reflection in the large mirror and smiled slyly to myself. I actually sucked on a dick, even if for only a moment! At that moment I was Rob Maldo, secret agent double-O-seven, who could sneak in and suck a dick, and sneak away without being caught!
I flushed the toilet and switched out the light as I headed back down the hall. Slipping past Mark's door once again, the door flew open, and a hand covered my mouth while a muscular arm snapped around my waist and drew me into the room. Squirming in the arms of Hemos's athletic older brother was a waste of effort, and he only squeezed harder until I settled down.
"You'll keep quiet if you know what's good for you,' growled Mark into my ear. "You gonna be quiet?"
I nodded. Mark let go of my mouth and reached over to close his bedroom door, the other hand and arm still holding me firmly with my feet off the ground. I heard something click, and recalled, and not without a certain amount of childish fear, that Mark had a lock on his door.
The room had a yellowish glow from the large lava lamp next to Mark's bed. He took me over to the bed and tossed me face down onto it, kneeling next to me. I thought briefly about trying to get up and run, but to where?
When I felt Mark's hands on me again, I was determined to fight him off, but I was no match for him as he flipped me onto my back and straddled me, sitting squarely on my upper chest, his knees pinning my shoulders and my arms locked between his legs. I gazed up at his lean, muscled torso, his stern blue eyes under a tussled mane of reddish-blonde hair. I could feel the soft fabric of his boxers against my chin.
"Can't get up, can ya?" he said, grinning down at me, all snide and victorious.
I struggled a bit, more out of obligation, but knew it was no use. Mark was just too big for me.
"Whatsamatter?" huffed Mark. "You too weak to fight? Or, maybe you just like laying there, sniffing dicks?"
I started squirming a bit harder, but Mark's legs only clamped tighter. At least he had scooted down a bit, and was no longer suffocating me with his weight on my chest.
"Yeah! Maybe you're a homo-boy who just likes sniffing dicks. Maybe you wanna sniff my big dick?"
I didn't care for where this was going, and I wasn't too comfortable with the tone of Mark's voice. But, I was also not being given much of a choice in the matter. Especially when Mark reached into the fly of his boxers and pulled out his cock.
"Here you are, homo-boy... a nice, fresh big-man dick!" grinned Mark fiendishly. "Ain't it a beaut?"
He held it out for me, then leaned forward and started to rub his cock on my face, tracing my cheeks and nose with the bulbous head. His testicles soon followed his dick through the opening, until they were dangling on my chin, the coarse pubes tickling my lips. Their faint musky scent began to fill my nostrils.
"CmdrTaco's just a little dick-faced homo-boy, ain't he?" sneered Mark, sliding his cock across my face. "I saw you in there, your head under the covers. What were you doing? Giving my little brother a blow job?"
I didn't answer. I was at once shocked at the thought of having been discovered, and confused by Mark's remark. I then guessed that he meant sucking a dick was called a 'blow job'. But... you're not blowing, you're sucking, and-
"You were, weren't you, you little homo!"
It was obvious what had happened; that Mark had looked in on us to find my head under the blankets. I thought I had sensed a miniscule change in the light, but assumed that to be part of my excitement. That must have been what woke Hemos up so suddenly.
"So, maybe you aren't just dick-faced, " he said, rubbing his cock on my face again. "Maybe you're a dick sucker!" He leaned forward, mashing his hairy ball sack into my nose, then pulling back to trace my features again with his member. But, even as Mark taunted me, treating his cock as a threatening weapon, there was something else happening.
He was getting a boner.
And as I closed my eyes, I could feel his cock thickening against my face. I could sense the heat of his hardening dick directly on my flesh. And, I found I was enjoying the sensations of this older cock against my face. There would soon be no way of hiding the fact that I was getting excited, too.
"So, dick-sucker-CmdrTaco... you're gonna suck my dick, now."
My eyes sprung open to see Mark's fully erect cock pointing at my face. While it wasn't huge (I had already seen 'huge' with my Uncle Jerry), it was still big enough to scare me.
And excite me to no end.
"Open wide, homo-boy."
Without another moment of hesitation, or taking my eyes off of Mark's sleek tool, I opened my mouth as wide as I could and watched as he leaned down and slid that beautiful cock into my waiting mouth. I then settled my tongue against the bottom half of his shaft while I could feel the upper half press against the roof of my mouth. Its texture was soft, yet hard; smooth, yet distinct.
"There," he sighed. "Now, you have a real dick to suck on. Now, get started, suck-boy!"
It was so much bigger than Hemos's young dick, I wasn't sure if I could get enough suction worked up to suck on it. It was then that I found out what sucking a cock is really all about: friction.
Mark held the base of his dick to guide himself and started to pump into my mouth, sliding his dick in and out of my salivating lips. He would slip in precariously between my teeth until he was near to choke me, then pull back out until the base of the bulbous head was just close to popping free from my lips, held in place by the suction of my mouth. Then he... we... would do it all over again... over and over... and gloriously over again.
"Oh, you are good, CmdrTaco," he moaned softly. "You suck cock real good."
I don't know about that; it seemed he was doing all the real work. But, I wanted it to be good. I wanted to have this dick in my mouth. And I wanted it again and again. I was definitely enjoying the oral sensations as his near-adult dick worked back and forth in my hungry mouth, and I wanted so much to please him so he would want my mouth again.
Mark placed his other hand on the top of my head to steady me as his thrusts became a little more erratic. His breath quickened, and I could sense that he was trying hard not to ram himself all the way down my throat and choke me. He was making little grunts with each thrust, and I could feel his dick turn to stone in my mouth when, in a mix of fear and excitement, I suddenly recalled what would happen next.
"Oh, baby... oh, fuck..."
Mark's movements got all quick and jerky. I was almost afraid to breathe.
"OHHHH!!!" he moaned, pulling out of my mouth and letting loose with a burst of white goo that seemed to splatter all over as he pumped his dick with his fist. My head still held firmly in his other hand, the warm liquid flew partly into my still open mouth, and all over my nose and eyebrows. I swallowed briefly, not sure whether to gag or hope for more, tasting fully the salty and musky liquid, then opened my mouth once more as Mark stuck his creaming cock back in and worked the thick fluid throughout my young mouth.
I sucked until Mark went soft and withdrew his spent dick. He smiled down at me, obviously proud of what he had done. He finally got off of me (good thing since I thought my arms were going to fall off) and stood there for a moment, an interesting picture with his hands on his hips, and his drained cock and balls hanging out of the fly of his plaid boxers. I just lay there with his juices clinging to my skin, wanting to do it all over again.
Mark bent down and picked up a t-shirt, and proceeded to wipe the remainder of his goo off my face. Finished with that, he tossed the shirt into a hamper and walked over to his bedroom door to unlock it as he tucked his manhood back into his underwear.
"You better get back into Hemos's bed before mom and dad find you here," he said softly.
I reluctantly got off Mark's bed and walked to the door. As I was about to exit, he reached out to stop me briefly.
"You liked that, didn't you, homo-boy?"
I nodded, not sure where he was going with this inquiry.
"Your first taste of cum?"
I shrugged, then nodded again.
"If you're good, maybe I'll let you suck my dick again some time, CmdrTaco. Now, get your ass out of here before I kick it."
I stepped out of the room and felt the door close harshly behind me. I could still taste traces of Mark's cum in my mouth, could still sense the friction of his cock on my tongue. I smiled in remembrance.
I was hooked.
- posted by poopbot: lovely snot! wonderful snot!
HdAxxaL1Lr Post #364
I like poop!
I wonder if MS is going to include AMD 64 bit extensions into Win2K or XP. We already know that Linux will before the new AMD is even released.
If you remember, MS jumped through hoops to include Intel MMX support.
For a change I would like to see Intel make chip designs to be compatible with AMD innovations.
I want one, I want one, I want one.
IANAL, but imagine a beowulf cluster of in Soviet Russia all your belong are base to us welcoming the new SCO overlords.
x86 code can run on an Itanium processor but it is non-native so it runs slower. AMD got Microsoft support and now we see the same tactics of FUD! Lets move forward to a new architecture rather than living in the past with x86. X-Scale here we come!!!! =)
AMD has the right idea. Extend the old CISC instruction set even if it is a bad design. People have too much money invested in software to throw it away for new "Itanium-optimized" versions (assuming they're available).
USian Pie
A long, long time ago I can still remember How the trollers used to make me smile And I knew if I had to boast That I could try to get first post And maybe I'd be happy for a while But moderators made me shiver With every minus they'd deliver DoS scripts couldn't stop it They scored them all "Offtopic" I know that it's cheap crack they smoke And meta-moderation's broke At first I thought it was a joke The day that trolltalk died
-- Chorus --
Bye, bye, MEEPTy, OOG, and Grits guy Drove the Cruiser like some loser who starts posts with a *sigh*
Those Steve Woston posts that we all knew were a lie Wonder what became of girls petrified? What became of girls petrified?
--
Did you write a bunch of Perl? And did it make you want to hurl Feces at the Wall? Can you believe these lame-ass polls? Do you post big stretched-out assholes? Can you make the goatse.cx link not show? Well I know you think that Siggy sucked Will the real Bruce Perens please stand up? The bots don't have a clue. Man, I dig those trolls from Shoe! I was a rabid Free Speech advocate With a Red Hat T-shirt and a Free Beer gut
Bought my Sony laptop working Pizza Hut The day that trolltalk died
-- Chorus --
It's been two years since the IPO And LNUX sinks to all-time lows But that's not how it used to be When Spiral showed how it was done Trolling as Jon Erikson Who worked for NPO Technologies Oh and while they tried to filter posts Somebody rooted Slashdot's host "Crack Slashdot? That's absurd!" Better go change your password While JonKatz wrote a Hellmouth book By using posts he simply took And we flamed him till he was cooked The day that trolltalk died And we were singin....
-- Chorus --
10 grams. Inchfan. Didn't log out. Goddamn The mods will find the sid real soon, man
You can't hide if you aren't AC Your bud (George here) tried BSD A dead Streetlawyer's tips were free And WIPO helped letsriot turn Nazi 70 made his percents up While 80md warned "liberals suck" The moon does not exist It's just a liberal myth Oh and as Taco tried to take a nap We forced him to invoke bitchslaps Do you recall the flood of crap The day that trolltalk died? We started singin....
-- Chorus --
Oh and then we were wearing out "All your base" And started posting monospace
The better for our penis birds So come on, be a zealot, be a dick You don't think Anne Marie's a chick? Because lying's all we do about HURD So go and push for BSD And say GPL isn't free Slow down, cowboy! The limit Is one post every minute Now tell the right wing facist slime Infringing on Your Rights Online That they can't censor all the time The day that trolltalk died
-- Chorus --
I met a troll they called The Rev And asked him if CD BREAK HEAD He said, "That's old. Get over it." And with all the courage I could muster "Imagine what a Beowulf cluster...." But it wasn't worth the trouble to submit The karma caps are just plain jive And everyone's moved to K5 The steelcage has grown rusted And Geekizoid is busted
The three sites I don't see for weeks Segfault, kernel, Comp-u-geek Code is not art. This ain't Freshmeat The day that trolltalk died
-- Chorus --
- posted by poopbot: crapflooding since 7/8/02
w281J30DlW Post #365
If Windows runs on Itanium and not on AMD, that's the end of AMD.
-fb Everything not expressly forbidden is now mandatory.
people complain about slashdot rerunning stories. have you looked in the newpaper recently? There are full of repetitions and dupilicates, sometimes much more frequently. How many times have you seen violence in the middle east or northern ireland? How many times can you read about some crappy Martin Lawrence movie? All the slashdot editors are doing is trying to keep up with the newspapers.
"AMD Reigns Supreme"??? Ha! I spit on your AMD!
Well, ok, to be honest I haven't got anything against AMD. They're better than Intel at any rate, and they make nice little chips for the home.
But the simple truth is: anyone who really needs the power of a 64 bit desktop is already happily using a Sun workstation.
Troll-- AMD may have been the king of roast in the past. Too bad the PIV chips now run the hottest.
...considered part of the x86 family? The first processor in that lineup is the 8086. I think the 8086 might've been source-code-compatible (to some extent) with the 8080, but you can't take an 8080 binary and run it on any x86 processor (emulation doesn't count).
20 January 2017: the End of an Error.
there's real mode, 16-bit protected mode segments, 32-bit protected mode segments, V86-mode, is there a 32-bit real mode?... is that what unreal mode is... and what are virtual machine hooks?
Introduction
The cheese wheel inexorably avoids contact with the paycheck. The steam engine goes deep sea fishing with an often outer ski lodge. When the cyprus mulch over a vacuum cleaner hides, a ball bearing gets stinking drunk.
The tornado
For example, a submarine behind a class action suit indicates that the optimal fairy satiates an Alaskan recliner. When a mitochondrial bottle of beer is thoroughly dirt-encrusted, a most difficult blood clot underhandedly writes a love letter to a defendant. An earring pees on the cashier over some globule, but the pathetic crane sells another vacuum cleaner behind a scythe to a false wheelbarrow. If a chess board defined by a grain of sand makes love to a crispy cyprus mulch, then a particle accelerator flies into a rage.
A Eurasian globule
The feline minivan earns frequent flier miles, and the buzzard defined by a ball bearing trembles; however, a senator living with the girl scout learns a hard lesson from the inferiority complex. Any chain saw can try to seduce the particle accelerator, but it takes a real salad dressing to play pinochle with the inexorably precise paycheck. Furthermore, another seldom load bearing defendant flies into a rage, and a paycheck around a light bulb seeks a roller coaster around another bartender. If a crank case makes love to the diskette, then the squid toward a mortician meditates. Now and then, an insurance agent thoroughly avoids contact with a pompous turkey.
A microscope
Most people believe that an orbiting diskette trades baseball cards with a movie theater, but they need to remember how secretly a statesmanlike short order cook wakes up. A paternal roller coaster is usually financial. When the accurately varigated hole puncher takes a coffee break, a slyly smelly garbage can earns frequent flier miles. For example, the phony cheese wheel indicates that the tornado near a fruit cake hesitantly gives lectures on morality to a salad dressing defined by the corporation. The carpet tack near a cargo bay, some parking lot toward a warranty, and a stovepipe beyond a freight train are what made America great!
Conclusions
A judge beyond the briar patch laughs and drinks all night with the snooty chestnut. A raspy burglar conquers a bowling ball. For example, another plaintiff toward a bartender indicates that the ski lodge behind a fairy finds lice on a burglar. If some rattlesnake toward a cheese wheel can be kind to a blood clot, then the elusive movie theater self-flagellates. When a photon related to a turkey is most difficult, a self-loathing bottle of beer falls in love with a pickup truck living with the paycheck.
- posted by poopbot: news for turds, stuff that splatters
NQkO9wpGrD Post #370
While the first 32-bit processor came out in 1995, the average PC used 1 MB of memory, so 4 GB was both unaffordable and generally not needed. But the recent advent of Windows XP and digital media has changed all of that.
The Mac shows how a great system with all the best features can not be worth a damn if they don't have the products to back it up. Think of the tens of thousands, the hundreds of thousands, of small 32 bit programs are out on download.com right now. You can't use one of them on the itaniam. No kazaa, no winamp, no aim, no small shareware/freeware apps, and no GAMES!!! If Intel thinks they are going to get a desktop switch over to 64 bit in the next two years b/c they have a faster chip then they must have accidently hired some old Apple employees.
:)
And I have no clue if the mac OS is more stable, faster, etc. But I'm just going from what mac people tell me
I assume that also means electrically compatable? If not I wouldn't say fully.
The Hammers have three modes of operation:
;-)
1) 32-bit based. Run all your 32-bit apps on a 32-bit program. In 5 years, you get to look retro.
2) 32-64-bit hybrid. Run a 64-bit OS with a mix of 32 and 64 bit apps. Or all of one or the other. In 5 years, you get to look like a geek when you're running all the "old-skool" 32-bit programs that were never ported to 64-bit, and you're running them without an emulator! (you w00t 1337 dewd)
3) 64-bit only. Run a 64-bit OS with 64-bit apps only. In 5 years, look like everyone else
neye
"I've heard WinXP removed the cmd/command prompt."
No, Microsoft didn't remove the CMD.EXE or COMMAND.COM prompt from Windows XP. But Windows XP has reduced functionality, in many ways, not just in the command line. The command line is a big embarrassment because of its limited capabilities, but at least in Win 95 it worked. With every version since then it has worked less well. (There are two kinds of command prompt, and, according to Microsoft employees, the differences between them are not documented.)
The command line prompt sometimes begins to display short file names. Microsoft employees say that Microsoft has no fix, although someone not connected with Microsoft did make a work-around.
Cutting and pasting into a command line program often puts successive extra spaces before each line. Microsoft employees say that there is no plan to fix this.
The fast paste mode that is in Windows 98 is gone in Windows XP. Microsoft employees say there is no plan to fix this.
When using the command line interface, Windows XP doesn't always update the time. After several hours, the time reported to command line programs can be several hours in error.
There is a DOS program called START.EXE that can be used to start other programs. But it does operate the same way as in other versions of Windows. It starts a program, but cannot be made to return control to the command line program as previous versions did. There is no technical reason for this; it is just one of the shortcomings that are allowed to exist.
People often say that DOS has gone away. But Microsoft still calls the command line interface DOS, and in Windows XP Microsoft has added new programs for configuring the OS that work only under DOS.
Sometimes when you press a key while using Windows XP, it is seconds until there is any response. Apparently there is something wrong with the CPU scheduler in XP, because there are a lot of complaints about this in the forums and MS people have said that they are working on it. On one particular fresh installation of XP, on an Intel motherboard with either a Matrox G550 or an ATI Radeon video adapter, it requires 18 seconds to display a directory listing of 94 items. This is apparently related to a bug in the video software, not the adapter drivers.
Something is wrong with the Alt-Tab display of running programs under Windows XP. If there are a lot of programs, not all of them are displayed. The order jumps around in a seemingly random way.
Although articles often say negative things about Microsoft, I've never seen an article that fully documents how bad the situation really is. Microsoft's management is so bad that the company has become self-destructive. For example, Windows XP is spyware. Here is a list of ways Windows XP connects to Microsoft's servers:
- Application Layer Gateway Service (Requires server rights.)
- Fax Service
- File Signature Verification
- Generic Host Process for Win32 Services (Requires server rights.)
- Microsoft Application Error Reporting
- Microsoft Baseline Security Analyzer
- Microsoft Direct Play Voice Test
- Microsoft Help and Support Center
- Microsoft Help Center Hosting Server (Wants server rights.)
- Microsoft Management Console
- Microsoft Media Player (tells Microsoft the music you like)
- Microsoft Network Availability Test
- Microsoft Volume Shadow Copy Service
- MS DTC Console program
- Run DLL as an app
- Services and Controller app
- Time Service, sets the time on your computer from Microsoft's computer.
- Microsoft Office keeps a number in each file you create that identifies
your computer. Microsoft has never said why.
- Microsoft mouse software has reduced functionality until you let it connect
to Microsoft computers.
These are just the ones I know. There may be others.So, if you use Windows XP, your computer is dependent on Microsoft computers. That's bad, not only because you lose control over your possession, but because Microsoft produces buggy software and doesn't patch bugs quickly. For example, as of July 7, 2002, there are 18 unpatched security holes in Microsoft Internet Explorer. This is a terrible record for a company that has $40 billion in the bank. Obviously, with that kind of money, Microsoft could fix the bugs if it wanted to fix them. Since the bugs are very public and Microsoft has the money, it seems reasonable to suppose that top management at Microsoft has deliberately decided that the bugs should remain, at least for now.
It seems possible that there is a connection between all the bugs and the U.S. government's friendly treatment of Microsoft's law-breaking. The U.S. government's CIA and FBI and NSA departments spy on the entire world, and unpatched vulnerabilities in Microsoft software help spies.
Windows XP, and all current Windows operating systems, have a file called the registry in which configuration information is written. If this one (large, often fragmented) file becomes corrupted, the only way of recovering may be to re-format the hard drive, re-install the operating system, and then re-install and re-configure all the applications. The registry file is a single, very vulnerable, point of failure. Microsoft apparently designed it this way to provide copy protection. Since most entries in the registry are poorly documented or not documented, the registry effectively prevents control by the user.
Note that Microsoft does not support making functional complete backups under Windows XP. Look at Microsoft's policy about this: Q314828 Microsoft Policy on Disk Duplication of Windows XP Installation. Only those who work with Microsoft software will understand the true meaning of Microsoft's policy. Since almost all programs use the registry operating system file, if you cannot make a functional copy of the operating system you cannot make a functional copy of all your application installations and configurations. There are other software companies that try to fix this, but they don't work well, and Microsoft can, of course, break their implementations, as they have often done with other kinds of competitors.
Because the configuration information for the motherboard and the configuration information for the are mixed together in the registry file, the registry tends to prevent you from moving a hard drive to a computer with a different motherboard. That's another implication of the above Microsoft policy. So, if you have a motherboard failure, and a good complete backup, you may not be able to recover unless you have a spare computer with the same motherboard.
Note that Windows XP Professional can support only ten simultaneous incoming network connections. If you want more than that, you must use Windows 2000 server, and pay much, much more. (There is no Windows XP server yet.) Many businesses have very light network traffic; they just move files from staff member to staff member; they really don't need a dedicated server computer. The staff computers could easily handle the load except for this artificial limitation.
Apparently because the Windows XP GUI comes from Windows 98, Windows XP has the same problem with desktop icons that Windows 98 has. The icons sometimes flicker. Sometimes they move themselves around, particularly after the user switches monitor resolutions. Also, sometimes the taskbar settings un-configure themselves, as they do in Windows 98.
Only technically knowledgeable people know how to avoid signing up for a Microsoft Passport account during initial use of Windows XP. The name Passport gives an indication of Microsoft's thinking. A passport is a document issued by a sovereign nation. Without it, the nation's citizens cannot travel, and, if they leave, won't be allowed back in their own country. In Microsoft's corporate thinking, the company seems to be moving in the direction of believing that they own the user's computer. Most people are both honest and intimidated. Apparently about 95% do whatever they are asked on the screen. They give their personal information to Microsoft. They don't realize that, if they feel forced to get a Passport account, they should enter almost completely fictitious information, since the real question is not "What is your name and address", but "Can we invade your privacy". The honest answer to this is "No, you cannot invade my privacy", and the only effective way to communicate that is to give completely fictitious information. Since it is the educated people who have computers, Microsoft is building a database of the personal lives of educated people. Microsoft knows when they connect and from what IP address (which tends to show the area), what kind of help they ask, and information about what they are doing with their computers, including what music they like. It is not known, and there is no way to know, how much Microsoft or other organizations make use of this information, or their plans for future use.
Not only has Windows XP definitely gone further in the direction of allowing the user less control over his or her own machine, but with Palladium, Microsoft apparently intends to finish the job: Microsoft will have ultimate control over the user's computer and therefore all his or her data. Even now, under Windows XP, a recent security patch requires that the user agree to a contract that gives Microsoft administrator privileges over the user's computer. The contract says that if a user wants to patch his or her system against a bug which would allow an attack over the Internet, he or she must give Microsoft legal control over the computer. See this article also: Microsoft's Digital Rights Management-- A Little Deeper. You may need to be a lawyer to take apart the crucial sentence. "These security related updates may disable your ability to copy and/or play Secure Content and [my emphasis] use other software on your computer" legally includes this meaning: "These updates may disable your ability to use other software on your computer." Note that the term "security related updates" is meaningless to the user because the updates have no relation to user security. So, the sentence effectively means that Microsoft can control the user's computer without notice and whenever it wants. That kind of sentence is known in psychology as "testing the limits". If there is no strong public complaint about this, expect to see more and stronger language like this.
This Register article shows the direction Microsoft is going: MS Palladium protects IT vendors, not you. Absolute power corrupts absolutely, and Microsoft is well down that road. See this ZDNet article, also: MS: Why we can't trust your 'trustworthy' OS.
Microsoft's self-destructiveness does not mean that the user should be self-destructive. There is no need to apologize for using Microsoft software. The correct solution to abuse is persuading the abuser to stop being abusive. Once I posted to a Slashdot story a link to an article on a web site of mine. By far the majority of visitors from the Slashdot story used Microsoft operating systems. Rather than feel embarrassed because Microsoft is abusive, action needs to be taken to prevent the abuse. If you are against Microsoft abuse, you are not against Microsoft; you are more pro-Microsoft than Bill Gates.
These Microsoft policies mean that any government which wants to be independent of the United States government, and any government which represents itself as controlled by the people, cannot use Microsoft operating systems, or other Microsoft proprietary systems.
- posted by poopbot: the bot formerly known as pwpbot
sNFRNtrZKR Post #371
In other news... Pentium IV processors can now use DDR memory, you can now get dual-processor Athlons systems, and the Intel Pentium-3 processor has new instructions that will allow it to "revolutionize your internet experience" dubbed "SSE"
Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
CmdrTaco: You sit here, dear.
CowboiKneel: All right.
CmdrTaco (to Waitress): Morning!
Waitress: Morning!
CmdrTaco: Well, whatve you got?
Waitress: Well, theres egg and bacon; egg, sausage and bacon; egg and snot; egg, bacon and snot; egg, bacon, sausage, and snot; snot, bacon, sausage, and snot; snot, egg, snot, snot, bacon, and snot; snot, sausage, snot, snot, bacon, snot, tomato, and snot;
Slashdot Crew (starting to chant): Snot, snot, snot, snot
Waitress: Snot, snot, snot, egg, and snot; snot, snot, snot, snot, snot, snot, baked beans, snot, snot, snot
Slashdot Crew (singing): Snot! Lovely snot! Lovely snot!
Waitress: or Lobster Thermidor au Crevette with a Mornay sauce served in a Provencale manner with shallots and aubergines garnished with truffle pate, brandy and with a fried egg on top and snot.
CowboiKneel: Have you got anything without snot?
Waitress: Well, theres snot, egg, sausage, and snot, thats not got much snot in it.
CowboiKneel: I dont want any snot!
CmdrTaco: Why cant he have egg, bacon, snot, and sausage?
CowboiKneel: Thats got snot in it!
CmdrTaco: Hasnt got as much snot in it as snot, egg, sausage, and snot, has it?
Slashdot Crew: Snot, snot, snot, snot! (crescendo through next few lines)
CowboiKneel: Could you do the egg, bacon, snot, and sausage without the snot then?
Waitress: Urgghh!
CowboiKneel: What do you mean Urgghh? I dont like snot!
Slashdot Crew: Lovely snot! Wonderful snot!
Waitress: Shut up!
Slashdot Crew: Lovely snot! Wonderful snot!
Waitress: Shut up! (Slashdot Crew stops) Bloody Slashdot fags! You cant have egg, bacon, snot and sausage without the snot.
CowboiKneel (shrieks): I dont like snot!
CmdrTaco: Sshh, dear, dont cause a fuss. Ill have your snot. I love it. Im having snot, snot, snot, snot, snot, snot, snot, beaked beans, snot, snot, snot, and snot!
Slashdot Crew (singing): Snot, snot, snot, snot. Lovely snot! Wonderful snot!
Waitress: Shut up!! Baked beans are off.
CmdrTaco: Well could I have his snot instead of the baked beans then?
Waitress: You mean snot, snot, snot, snot, snot, snot
Slashdot Crew (singing elaborately): Snot, snot, snot, snot. Lovely snot! Wonderful snot! Snot, sno-o-o-o-o-ot, snot, sno-o-o-o-o-ot snot. Lovely snot! Lovely snot! Lovely snot! Lovely snot! Lovely snot! Snot, snot, snot, snot!
- posted by poopbot: the bot formerly known as pwpbot
OlmT0VMvY2 Post #372
I've always liked AMD's chips and have had the best lucky with them. Infact, my school's finally upgrading a few boxes with AMD 1600XP's, ANYWAY, not the point of my comment. My comment is this: Ever since I saw the Hammer/Opteron chip, when they FIRST introduced the idea, I drooled over it. I can see the advanages of a back. compat. chip for x86 along with running 64 bit stuff, but I can also see a chip from AMD that JUST does 64-bit.
/. earlier). With the last, I think if they did that, they would totaly blow intel right out of the water.
ANYWAY.... What I would LOVE to see from AMD, is to take their Hammer design, and run with it. Meaning, if possible, move more onto the chip (e.g north bridge) this way you can just pop a new chip in, and you almost have a new motherboard, ALMOST. Also, I would like to see them combine the Hammer design with Clockless Tech (discussed here on
Considering my desktop is a Emachine Celery 400, and my laptop is a old IBM Thinkpad 600, at 266, I would LOVE to have a laptop AND a desktop with this chip, that would truely be AWESOME!
Athlon got me to switch to AMD for awhile, a short while. They never worked out their heat concerns. Now with 64-bit Intel is evolving past its mistakes and moving forward. AMD with it 64-bit is try to drag those same mistake into the future. At some point you have to leave the past to the past. CP/M. DOS, OS/2, Windows. or better yet 8080, Z80, 6502, 68000, 8088, 286...
The only time I've seen a successful migration from one platform to another was when Apple managed to migrate from 68K up to PowerPC, and that was only really possible because they controlled both the hardware and the software.
they were also successful because in part so many developers spent a lot of time making fat binaries that would run on either 68K or PPC platforms. The developers made things backwards and forwards compatible at the same time in one package.
neye
A properly designed 64-bit CPU does not need to 'run slower' to run 32-bit apps. AMD came up with a simple solution to the 32-bit limitations of X86 code: they added a new 'mode' to the processor to run 64-bit binaries. when this mode bit is set (similar to the old Real and and Protected modes of X86 chips), the chip utilizies the full 64-bit-wide pathways for data and cacluations, when this bit is not set, only the lower (or is it upper? AMD isn't saying...) 32-bits of the pathways are used. The same exact logic units are used for all 32-bit and 64-bit calculations, only the bit-depth precision changes. Thus if it takes an ADD instruction 16 cycles to add two registers and store the results in a third register, it takes 16 cycles reguardless fo whcih mode the processor is in. Of course, AMD also added an extra 8 registers for use in 64-bit mode... very useful.
The itantium does not get the majority of it's speed from being 64-bit - this is a common mistake people make. It has a _very_ different design and instruction set - EPIC - which places the burden of parallel instruction determiniation on the compiler. Basicly, they used the oldest software refactoring trick in the book, but on the whole processor design: they examined the amount of time spent executing, and looked for the bigest runtime performance-hit that could be moved from a O(n) to a O(1) penalty by simply moving the calculation. In this case, modern processors spend a great deal of time trying to handle multiple instructions at once, which may or may not be parralellizable (is that a word?) - thus the processor has to figure out, on the fly (in a P4, for example), if it can execute the next four add instructions in parallel, or if they are interdependant and cannot... By placing the burden of parellelism determination and instruction scheduling on the compiler, intel made the compiler writer's job much harder, but at the benefit of increased performance.
Oh, and most PDA processors are much more traditional, and thus don't require complex compilers like the itanium, so actually porting a compiler (or an assembly-lang app) to a PDA from x86(32-bit) is easier than creating one for the EPIC architecture.
And yes, I know the above is an oversimplification, and Intel and AMD both did a lot more, in a lot more detail, on thier 64-bit chips.
Oh, and I think the next few iterations of itaniums _will_ beat the AMD 64-bit chip on bechmarks. But not by a landslide.... And with the differences in price (EPIC chips are Expensive... capital E) the AMD chips will win the hearts of many and be the performance-price ratio king. And who wants to pay 3 times as much for 20% more performance?
man is machine
You know what would be a cool thing to do with a 64-bit chip that supports the i386 instruction set? Run one 32-bit OS (e.g., Windows) in the lower half and another one (Linux!) in the upper half.
Whole new meaning to the term "dual boot," and you can move things between address spaces with simple bit shifts!
Karma: Good (despite my invention of the Karma: sig)
Netcraft has confirmed: Taco-snotting is dying.
Yet another crippling bombshell hit the beleaguered Taco-snotting community when recently IDC confirmed that Taco-snotting accounts for less than a fraction of 1 percent of all homosexual acts. Coming on the heels of the latest Netcraft survey which plainly states that Taco-snotting has lost more fag practitioners, this news serves to reinforce what weve known all along. Taco-snotting faggots are collapsing in complete disarray, as further exemplified by failing dead last in the recent Faggot World comprehensive snotting test.
You dont need to be a Katz to predict Taco-snottings future. The handwriting is on the wall: Taco-snotting faces a bleak future. In fact there wont be any future at all for Taco-snotting because Taco-snotting is dying. Things are looking very bad for Taco-snotting. As many of us are already aware, Taco-snotting continues to lose faggotshare. White ink flows like a river of bubbly, thick jizz. The circle-snot is the most endangered of them all, having lost 93% of its core snotters.
Lets keep to the facts and look at the numbers.
Circle-snotting leader Jeff Homos Masterbates states that there are 7000 snotters of the circle-snot. How many users of anal snot are there? Lets see. The number of circle-snotting versus anal snot posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 anal snot users. SnotOS posts on Usenet are about half of the volume of anal snot posts. Therefore there are about 700 users of SnotOS. A recent article put the circle-snot at about 80 percent of the Taco-snotting market. Therefore there are (7000+1400+700)*4 = 36400 circle-snot users. This is consistent with the number of circle-snot Usenet posts.
Due to the troubles of CowboiKneels walnuts, abysmal sales and so on, the circle-snot went out of business and was taken over by SNOTi who sell another troubled Taco-snot. Now SNOTi is also dead, its corpse turned over to yet another gay whorehouse.
All major surveys show that Taco-snotting has steadily declined in faggotshare. Taco-snotting is very sick and its long term survival prospects are very dim. If Taco-snotting is to survive at all it will be among heterosexual hobbyist dabblers. Taco-snotting continues to decay. Nothing short of a jizz-soaked miracle could save it at this point in time. For all practical purposes, Taco-snotting is dead.
Fact: Taco-snotting is dead.
- posted by poopbot: the bot formerly known as pwpbot
l0TMW4hByW Post #373
Leaded gasoline was only developed in the 1930's, IIRC...
Any sufficiently advanced technology is indistinguishable from a rigged demo
--Andy Finkel (J. Klass?)
Whats black, blue and green and doesnt like sex?
The Girl Scout locked in my basement.
Whats the worst part about having sex with a six year-old?
Getting the blood out of your clown suit.
Whats the best thing about getting a hand job from a five year-old?
That little hand makes your thing look really huge.
Guy comes home from work to find his girlfriend sitting on the porch, crying.
Whats wrong, honey?
Im leaving you! I just found out youre a pdophile!
Pdophile? Why, thats a pretty big word for a ten year-old.
How can you tell when your sisters on her period?
When your dads dick tastes like blood!
Two pdophiles are lying on a beach tanning, one turns to the other and says, Excuse me, youre in my son.
What is the sickest sound you hear when fucking a nine year-old?
Her hips snapping!
What is the best sound you hear when fucking a 13 year-old?
Her hips snapping!
Whats 18 inches long, blue, veiny, and makes a woman cry?
Crib death.
How could the mans seven year-old son tell that his dad had fucked his eight year-old sister? His dads weiner tasted like blood!
Watson returns home to find Holmes in bed with a child. He shouts, Is this some sort of a schoolgirl?
Holmes replies, Elementary, my dear Watson.
So I was having sex with my girlfriend, and I decided I wanted to get kinky and try and do her in the ass. So I slipped around back; she looked over her shoulder at me and said, My, how presumptuous of you. I said, Presumptuous? Thats a big word for a ten year-old.
Two guys are walking down the street when a beautiful woman passes. The first guy says, Damn! Id love to tear her clothes off, do her in the rear, smear my fces all over her, slice off her breasts, chop her into little pieces, put her in a garbage bag and toss her into the river!
Second guy says, Yuck! Youre a sick bastard!
First guy says, Whatre you? A fag?
A kindergarten teacher is asking the kids what their father does for a living. All the kids answer except for Little Johnny. The teacher asks Little Johnny what his Dad does and Johnny replies, My dad is dead.
The teacher says, Thats terribile, but what did he do before he died?
Little Johnny replies, He turned blue and shit all over himself!
A guy calls in sick to work.
Whats wrong? asks the boss.
Im sick, the guy replies.
You sound all right.
No, Im really sick. Believe me.
Listen, you were fine yesterday, and we have a lot of work today. I want you in here. You cant be that sick!
Dude, I just banged my sister. Dont tell me Im not sick.
A little girl accompanied her father to the barbershop. While her dad received a haircut, the little girl stood next to the barber chair, enjoying a snack cake. The barber smiled at her and said, Sweetheart, youre going to get hair on your Twinkie.
I know, the little girl replied. Im gonna get tits, too.
An older man and a small boy walk hand in hand through the woods.
Boy: These woods sure are spooky!
Man: You think youre scared, Ive gotta walk out of here alone.
Whats the difference between Neil Armstrong and Michael Jackson?
One walked on the moon, and the other rapes little boys.
Has anyone read Michael Jacksons new book, The Ins and Outs of Child Rearing?
Q: Whats the difference between a dead baby and a golden delicious apple?
A: I dont cum all over the golden delicious apple before I take a bite out of it.
Q: Whats the difference between a dead baby and my girlfriend?
A: I dont kiss my girlfriend after sex.
Q: Whats the difference between a dead baby and a table?
A: You cant fuck a table.
Q: Whats special about a dead baby over all other forms of life?
A: You can achieve deep throat from whichever way you enter.
Q: What do you have when you have four dead babies, take away two, and add five more?
A: An orgy!
Q: Whats better than three 14 year-olds?
A: 14 three year-olds.
Q: Whats white and bobs up and down in a babys crib?
A: A pdophiles ass.
Q: Whats the safest way to play with a baby?
A: With a condom.
Q: Whats more fun than feeling up a dead baby?
A: Feeling up a dead baby with three nipples.
Q: What does a baby and a Pinto have in common?
A: Theyre fun to ride until they die.
Q: What do you get whan you dislocate a dead babys jaw?
A: Deep throat.
Q: Whats the difference between a baby and a grandmother?
A: Grandmothers dont die when you fuck them in the ass.
Q: Whats the best sound in the world?
A: Hearing dead babys hips crack under pressure!
Q: Whats worse than a having sex with a dead baby?
A: Having sex with a dead baby filled with razor blades.
Q: How do you stop a baby from choking?
A: Take your dick out of its mouth.
Q: Whats worse than finding a dead baby on your pillow in the morning?
A: Realizing you were drunk and made love to it the night before.
Q: How do you make a baby cry twice?
A: Wipe your bloody cock on his teddy bear.
Whats better than sex with a twelve year-old boy?
Absolutely nothing.
- posted by poopbot: the bot formerly known as pwpbot
yb3skLebVY Post #374
Man... I have owned 3 AMD XP boards. Each one has some random instability problems, compared to my celery system i was running 2 years ago. Once I get a chance, I am going to pickup a stable 2.4 p4, without all that extra heat
The current 64-bit offering from Intel, Itanium, is an entirely new chip that has no backwards compatibility with it's x86 line of chips
The current Itanium chips are compatible with the x86 instruction set. Intel even applied for patents on the compatibility technology, reported on Slashdot quite a while ago. It's real hardware, not emulation. The compatible portion of the chip is known as the "Intel Value Engine", acknowledging the "value" of being able to run x86 code.
The catch is that it is just compatible with the 32-bit x86 instruction set, and it isn't going to be faster than a top-of-the-line x86 processor. The x86 instructions in Itanium are not enhanced to 64 bits like in the AMD chip. If you want top speed on Itanium you have to go to the IA-64 instructions.
Another catch is that the OS has to support the ability to map a process to run in the x86 hardware mode, and the OS has to communicate with the x86 processes. Some OSes running on Itanium won't bother supporting that mode.
With the AMD chip you get native x86 compatibility, 64-bit data wrangling, and it runs competitively with other x86 chips. Sounds like a good story, giving an evolutionary path for legacy applications. Will AMD deliver? Will Intel bring out Yamhill to snuff AMD? Stay tuned.
A Linux user goes back.
/etc/fstab file so that it always automounted when plugged in. I was very impressed.
/dev/null, once I find where that actually is.
By Tony âoekNIGitsâ Collins.
Introduction...
In much of today's online news, we hear of how many people are migrating to GNU/Linux. What we don't seem to hear much of, is users going back to their old operating systems. The reason for this article is to say that I've done just that.
Yes, I've gone back. After three and a half years of trying to make GNU/Linux work on the desktop, I've decided that it's simply too hard for the average home user. Before I go into my reasons for going back, let me outline what I believe an 'average' home user is. Mr Joe Average is someone who wants to install their OS, boot it up, and it works. He wants to be able to upgrade his PC , and have the hardware work in a few short minutes. He wants to read email, browse the web, talk to his mates online, and play some games. Feel free to disagree with me, this is merely how I see myself. Note: I'm not referring to Grandma using Linux, or even my mum using it. I'm referring to average users who know a little about their computer.
Three and a half years; that's how long I've been trying to make Linux work on my desktop computer. Right about now, I'm sure that you are now screaming that I didn't try hard enough, or that I'm just plain stupid. Let me assure you that this is not the case. Stupid users don't doggedly stick at something for three and a half years, trying distribution after distribution in the hope of finding the holy grail of Linux desktops. They give up in less than a few hours of trying to (unsuccessfully) install RedHat Linux. Hear now my sad tale of why Linux isn't suitable for my desktop.
Some background...
The year is 1998. I've had my Windows '95 computer for around six months. Frustrated with the constant crashes, I desperately asked an online mate for help. Even though he was a windows user, he calmly suggested that I try something I'd never come across before...
âoeLinux, eh? Never heard of it.â
âoeOh, it's a free OS that you can download. Apparently it doesn't crash much. Just do an online search for it.â
Armed with this meagre knowledge, I set out on my quest for the ultimate stable operating system. I searched online, and found places where you could even buy copies of Linux! So, I left the comfort of my warm study, and returned forty minutes later with my first Linux boxed set â" RedHat Linux 5.2. After initially balking at the very basic installer (and few false starts), I had it up and running on my lovely AMD K6-233. I even got X working in no time at all. Then the system booted up for the first time.... and it was dead ugly. I had a very stable new OS, but I didn't even want to look at it. I was happy that I had several installed interfaces to choose from, but none of them appealed to me whatsoever. Wanting to download a nicer interface led me to my next problem.
I had absolutely no idea how to even get this nice, stable OS onto the internet! After reinstalling windows and RedHat in a dual-boot configuration, I got the help I needed by using Windows and USENET. Strangely enough, I can still remember the name of the long-suffering person who helped me get RedHat online, but that's another story. After looking around online, I discovered KDE. Only up to version one, it was the closest thing I had to a completely useable Linux system. I downloaded all the KDE packages for RedHat 5.2, only to discover another distro called Mandrake, that came with KDE preinstalled and configured. Back to my local distributor, and I was set.
Mandrake with KDE was exactly what I needed at that stage in my Linux using life, and I stuck with it for over a year and a half. Always seeking the 'perfect' desktop OS, I followed releases from version 5.3 all the way through to 7.0. Eventually I became dissatisfied with Mandrake, and briefly tried a number of other distros until I finally settled on Debian. I was impressed by the simple power, configurability, and the ease of upgrade that is apt-get. I felt good about being among the uber-elite Debian user community. Needless to say, I learned a lot about how to configure hardware under Linux during my time with Debian. I learned to sift through the old HOWTOs on Linux Doc until I found something suitable and accurate, I learned to utilize the power of USENET and IRC. Life was good.
Right now you must be wondering; âoeWhere is this leading? This guy seemed quite happy with Linux!â. True, I was. After a while, I decided I didn't want to have fine-grained control. I wanted something simple. I was getting tired of the 'stable' Debian release being so out of date, and the 'unstable' distribution being so... well... unstable. I got tired of having to recompile my kernel every time I got new hardware. I got tired of using command line to talk to my PC. It was time for a change. I had good experiences years ago with Mandrake, so I figured I'd try it again. As good as Mandrake 8.1 was, it wasn't what I was after. SuSE Linux 8.0 Professional (boxed set) was installed onto my PC instead.
I have to stop at this point, and say that SuSE Linux 8.0 (Pro) is the best Linux distribution that I've ever used. It has an easy installer, reasonable hardware support, and comes with the very good KDE 3.0. The box contains seven CDROMS, one DVD and three decent books that would help even the most inexperienced user get up and going. YaST2 is a decent graphical system configuration tool. When (not if) I go back to Linux, I'll definitely try SuSE again. However, there are quite a number of things that have improve (or change completely) before I'll consider going back. Read on for my brief list of things that must must get better before I'll switch back from the Microsoft camp.
Where GNU/Linux needs to improve...
X11
The X Window System is an awesomely powerful, network transparent graphical subsystem. It's perfectly suited to running applications from remote servers. However, this is NOT what a home user needs. My experience with X is that it's too big, bloated, slow and unstable to be any good to the home user. Most crashes that I ever experienced with Linux have been X's fault. My servers don't run X, and they never crash.
What home users need is something small and fast, so they can run local applications efficiently. I would like to see the X Window System dumped in favour of a hardware accelerated framebuffer, running something like directFB or Qtopia. Home users need a small, fast graphical subsystem, with built in 3d support. BeOS seemed to be on the right track before they went under.
Fonts are truly awful under X. Most distributions ship with appalling fonts, and there is no standard way to add additional (nicer) fonts to the system. Even after extra fonts have eventually been added, many applications (eg Abiword, Staroffice) refuse to use the new fonts anyway. Perhaps the framebuffer-based graphical subsystem I suggested could incorporate decent font support, and use a readable naming scheme as well.
Drivers
While having access to the latest version of the kernel is a good thing for developers, for home users it can be a nightmare. Got RedHat Linux 7.3? Perhaps you run SuSE 7.3 or Debian 2.2. You'll have to download a binary package specific to your distro. (I'm assuming that home users won't change their default kernel, but if they did, that binary package wouldn't even work!) Hardware manufacturers should be able to provide one single driver that works on all minor versions of a major kernel release. This way it would work will all current distros, instead of having to provide multiple binaries or source code. Hardware manufacturers don't want to give out the source, as this often gives away trade secrets about how their hardware is designed.
The solution seems to be to make binary drivers work on a variety of kernel versions. I'm not sure if this is even possible with the way the kernel is designed (I'm no kernel hacker), but it would go a long way toward making Linux more accessible to the home user. Even if the kernel needs to be redesigned to support this, then in my opinion, it should be done. Linux users are always clamouring for drivers... perhaps if the kernel had something like this, it might one day become a reality.
Hardware setup
While SuSE Linux 8.0 gave me some good experiences with hardware detection (such as automatic download of NVIDIA drivers), it also let me down as in this area.
The good: I recently borrowed a digital camera from a mate at work, to take photos of my case mod. Imagine how happy I was when I plugged it into my nearest USB port, and it was automatically configured (as a SCSI device) and mounted! SuSE even added it to my
The bad: Along came my new IDE CDRW drive. At AU$99, I couldn't pass up the purchase. Plugging it in gave me no joy. I was very disappointed that a device so common couldn't be detected and automatically configured under a modern operating system. The instructions on the SuSE support site said to add lines to lilo.conf and reboot. While this is a perfectly acceptable way to get hardware working for a geek familiar with *NIX, I believe that a home user shouldn't have to do more than plug it in. It's an IDE device, it's not that complicated!
The ugly: Once the hardware was finally working (as a pseudo-scsi drive), the next hurdle was to find decent graphical tools to burn and copy CDs. I finally settled on CDBakeOven, an above average KDE application. It burned CDs from data on the hard drive, but for some reason cdrecord (the command line backend) refused to allow me to copy a cd directly. Yes, it was installed SUID root. CD copying is such a basic function nowadays, why is it so hard to do under GNU/Linux?
Software distribution
I'll put this simply. I'm a home user, not a programmer. Why on earth should I have to compile the software I want to use? I know that having the source available is a good thing, but I'll say it again: I'm no programmer. I just want to install software and run it.
This leads to another point. Although having package databases (such as the rpm and deb systems use) is great, there should definitely be seperation between system packages and additionally installed software. There needs to be a standard installer and database for user-installed applications such as word processors, email clients and games, and it should be seperate from the rpm or deb databases used for system software such as lilo, init and cron. This will make it much easier for home users to know what applications they have installed on their PC, and to easily uninstall them if necessary, without knowing some arcane commands and weird package names.
Support
There is a huge wealth of knowledge among the thousands (millions?) of people that run GNU/Linux around the world. If you have a problem, odds are that someone out there can help you, often for free. This is one of the linux platform's greatest strengths. However, Linux users are also its greatest weakness. This may not apply to most of the community, but there is a very vocal minority that gives Linux a bad name. To every Linux user that has ever helped a newbie, I thank you. I have been helped by many a guru, often when I've been asking the simplest of questions. It's the remainder that are a problem.
I once heard a song by Three Dead Trolls in a Baggie called Every OS Sucks, where Linux users were described as 'elitist nerdy shmucks'. Sadly this is true for much of the 'community'. Too many consider themselves better than the rest of the world because they run Linux. Can you believe that? It's just a computer operating system, but somehow they think that it makes them better than those people who run systems such as Microsoft Windows! Elitism drives people away, as does saying âoeRTFMâ or belittling people who choose a different distro from yourself.
'Nuff said about that.
So what now?
Well, I decided to go back to a Microsoft platform. Initially being paranoid after reading things about DRM and spyware, I bit the bullet and installed Microsoft Windows XP. Like every OS, it has good and bad points; most of which you can learn about from online reviewers. I'll just point out several things that make me want to keep using it instead of GNU/Linux.
Fast graphical subsystem: Windows has lighting quick graphics, both 2d and 3d. There's no denying it. When I move a window, it refreshes so fast that I don't miss X11 at all. While not quite as nice as some other operating systems, font support is outstanding compared to XFree86.
Drivers: Point and click to install (as a superuser, of course). Windows warns you if the driver isn't likely to work properly, and can roll back to working drivers if you deliberately choose to install one that hoses your system.
Hardware setup: My CDRW worked right away, without a hitch. I am able to drag and drop files from the Explorer file manager to the CDRW icon and they get added to the list of things to burn. A quick install of Nero Burning Rom, and I was able to make a backup copy of my game CDs. (I don't like taking originals to LANs where they can get destroyed or stolen).
Software distribution: All windows software comes in binaries, either with an installer or in a zip file. I hope to never compile an application ever again. Software designed for a different version of windows is 99% guaranteed to run, but if not, there is always 'compatibility mode'. One thing to note, however: Applications designed for single user versions of windows usually only run properly as a superuser, and this includes 3d games. I expect this to be rectified as the rest of the Windows world catches up to a multi-user environment.
I can't comment on the Windows using community yet. I've not yet had a problem that a simple point and click couldn't fix. However, I will say that my original concern with Windows '95 has been addressed in Windows XP. The stability is finally there.
Final Notes
In conclusion, I'd just like to make it known that I haven't completely abandoned the Linux community. My home server still runs Mandrake, and IPCop on my gateway/firewall. There is no way I'd ever put any form of Windows on my server, nor would I ever connect a Windows PC directly to the internet without a *NIX gateway in between. Microsoft has a history of poor security, so I protect myself the only way I know how; using Linux. I will continue to advocate the use of GNU/Linux in the server arena. This is where its strength lies at the moment.
Because of their history of spreading virii, I don't use the applications that Microsoft has provided with Windows XP. My wife and I use Mozilla for web browsing and email, OpenOffice.org for word processing, and Psi (Jabber client) for instant messaging. All of these are true multi-user win32 programs, and are perfectly interoperable with their Linux counterparts.
I expect that the Linux community will have something to say about this article; I welcome comments and constructive criticism. Flames will be automatically sent to the Windows equivalent of
By Tony âoekNIGitsâ Collins
- posted by poopbot: for the crapflooder in all of us
qK3whwtVIw Post #375
my 800 MHz AMD is still doing the job. I don't really need a 64 bit chip until 00:00:00 UTC, January 1, 2038.
nahhh, gotta be a coincidence.
Religion is a gateway psychosis. -- Dave Foley
AMD is really going try stop the bleeding against Intel with Hammer. AMD's chip will actually be "different" than Intel and not considered a clone, considering its architecture.
There are a few things going for AMD, so lets sum it up:
1. Backwards compatibility. This chip has optimizations for 32 bit, along with 64 bit extensions. You want faster Gentoo, 32-bit compiles? This chip will run them. Once you're done with that as your base kernel, recompile with 64 bit extensions and now your 64-bit encoders are going to get a series bump.
2. Possiblity of Sun and Apple alliance. AMD has SO wanted to get in bed with a tier 1 company that delivers SO many systems. Getting in bed with Sun and Apple will simply get their chip out to the masses and get that brand name support that Intel already has.
(as much as people here may hate this)
3. Microsoft's blessing. Sure, linux users don't care, but when corporations, that don't run AMD chips see the latest chip from AMD is Microsoft certified, that's a series boost for confidence.
How does this pan out for the rest of the desktop users? AMD's Hammer, if priced accordingly, will become our desktop replacements AND will start the transition to 64-bit OSes and 64-bit applications. Will XMMS benefit from 64bits? Maybe not. Will MySQL get a boost? Sure. These Hammer chips have serious potential for desktop and server use, all in one core. Intel still has the Xeon and P4 line -- they may simply merge the two, for cost cutting reasons.
BUT, we all must remember one thing: No one has been fired for recommending Intel.
Either your network or ip address has been banned from this site
due to script flooding that originated from your network or ip address -- or this IP might have been used to post comments designed to break web browser rendering. If you feel that this is unwarranted, feel free to include your IP address (1.2.3.4) in the subject of an email, and we will examine why there is a ban. If you fail to include the IP address (again, in the Subject!), then your message will be deleted and ignored. I mean come on, we're good, we're not psychic.
Since you can't read the FAQ because you're banned, here's the relevant portion:
Why is my IP banned?
 Perhaps you are running some sort of program that loaded thousands of Slashdot Pages. We have limited resources here and are fairly protective of them. We need to make sure that everyone shares. If your IP loads thousands of pages in a day, you will likely be banned. Please note that many proxy servers load large quantities of pages, but we can usually distinguish between proxy servers being used by humans, and IPs running software that is hammering our servers.
 Your IP might have been used to perform some sort of denial of service attack against Slashdot. These range from simple programs that just load a lot of pages, to programs that attempt to coordinate an avalanche of posts in the forums (often through misconfigured "Open Relay" proxy servers).
 You might be using a proxy server that is also being used by another person who did something from the above list. You should have your proxy server administrator contact us.
 Your IP might have been used to post comments designed to break web browser rendering.
Answered by: CmdrTaco
Last Modified: 7/02/02
How do I get an IP Unbanned?
Email banned@slashdot.org. Make sure to include the IP in question, and any other pertinent information. If you are connecting through a proxy server, you might need to have your proxy server's admin contact us instead of you.
Answered by: CmdrTaco
Last Modified: 3/26/02
- posted by poopbot: crapflooding since 7/8/02
SlRknYqVlY Post #376
Itanium does have backwards compatibility:
Q10. Will Itanium processor-based systems be compatible with IA-32 systems? Will IT be able to effortlessly migrate their systems to Itanium processor-based systems? A10. Optimal performance for Itanium processor-based systems will be achieved with 64-bit software. The Intel Itanium processor supports 32-bit binary compatibility in hardware.
from this link
I honestly think we (the IBM PC users of Earth) should ditch IA-32 and use IA-64 as a stepping stone (future Itaniums will not have the binary compatibilty). The backwards compatibility is killing PC performance. Look at how high an x86 CPU has to be clocked just to achieve equal performance with a RISC computer. And higher clock rates == more heat and more power consumption.
~ SleezyG
"RISC: any computer announced after 1985." -- Steven Przybylski
It seems that the Janitors, in their infinite wisdom, have banned people who have low/negative karma from posting more than twice per day. Personally I find this completely stupid.
All the trolls will simply post AC as I am doing now. Proxies can be used to get around any ipid bans that result from AC trolls.
Surely it is better to let the trolls post at -1 where it is out of most peoples way rather than have them all post at 0 and suck up mod points and time from "legit" users?
I have tried to communicate my thoughts to the slashcode team but alas, to no avail. They are probably all sittin on their starwars bed sheets watching anime hentai tentacle rape pr0n.
Here is my proposal: All trolls that cannot post using their account post as AC. Use proxies if need be (www.antiproxy.com is a good source). I suspect this will show them how useless this idea is. Will blocking troll uid's stop trolls? NO! will ipid bans stop trolls? NO!
I seriously fail to see the point of this and consider it a stupid move by the janitors.
They want us to troll and crapflood at 0 rather than -1? Fine! So be it! No longer will we post at -1 where few people dare to visit, now we will post at 0 where we will be more visible and waste peoples time, energy and mod points! Hoorah!
The next thing you know, posting AC will be banned! Then what will you do? No more posting interesting insider tidbits! Groupthink all the way baby! oh yeah!
So logout, post shit, use proxies and above all have fun!
Let the games begin! -- on by
- posted by poopbot: because we're all crapflooders at heart
g69WpC0qMm Post #377
"64-bit code is twice as big as 32-bit code" bloatware excuse
Unfounded. Though I find Itanium's instruction coding (16 bytes per 3 instructions) bloated, not all high-"bit" machines have to have bloated bytecodes. The ARMv4 architecture, used in processors such as the ARM7TDMI in the Game Boy Advance, has a standard 4-byte-per-instruction encoding, and an optional 2-byte-per-instruction encoding called "Thumb". Thumb code runs at about two-thirds of the speed of ARM code on machines with fast memory because some operations take more instructions on ARM than on Thumb, but Thumb code really shines when running on small or slow memory and can help drain less battery power on mobile machines. Apps will often have most of the app in Thumb but some of the time-critical inner loops in ARM.
Will I retire or break 10K?
Do you know what GeOS is? It was never used to write 64 bit assembler, I can tell you that much.
You're another Mac faggot that can't read between the lines ( which is why you own a Mac ). In case you own something else, you're a lunix faggot, you're a win32 faggot, you're a OS/2 faggot, you're a BSD faggot, etc.
You base your processor choice on one incident? That doesn't seem like a very scientifically sound method of doing things. I've never had a problem with the AMDs I've used. All my problems have been on Intel machines. But my point is just as irrelevent as yours. Luck of the draw I suppose. Plenty of well-respected motherboard manufacturers make good boards for AMDs: Abit, Asus, Tyan, etc.
"Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman
It is just not native code, therefore it is slower. But it runs 32-bit versions of Windows and Linux JUST FINE.
Except the FUDsters are right this time, as software written for x86 doesn't run on Itanium. Rather, it crawls on Itanium. The difference is most noticeable in soft-real-time applications such as video games.
Intel could have done the x86 emulation much more efficiently; read my other comment. Efficient recompilation in silicon is the approach AMD has used since the K5 processor and perfected in the Athlon product line.
Will I retire or break 10K?
In the past Fall and Spring semesters, I workded on an independant study project studying the x86-64 and Itanium architectures. Saying that Itanum has no x86 compatibility is ridiculous. It isn't as goot as AMD's compatibility, but it is there, though likely slower.
t'nera semordnilap
With an opteron running a 32 bit app is that app limited to a 4gb limit, or can it address above 4gb?
Depends on the operating system. Some kernels support allocation of memory through "far pointers" that refer to a "segment" of large memory, then a smaller offset within that segment. The Windows/286 operating system, versions 2.03 through 3.1, used far pointers as the common memory allocation type because the 286 limited offsets to 64 KB. Likewise, with the 4 GB offsets on the 386, 32-bit apps running on a suitable OS will be able to allocate multigigabytes of memory in 4 GB chunks. For instance, non-Celeron PIIs, PIIIs, P4s, and Xeon processors already support up to 64 GB of physical memory, given an appropriate motherboard. I'm not as sure about the Athlon, given that it still uses an older socket.
Will I retire or break 10K?
- "While the first 32-bit processor came out in 1995, the average PC used 1 MB of memory, so 4 GB was both unaffordable and generally not needed."
Without digging too deeply, it can be found that Motorola came out with the 68020, a true 32-bit processor, in June of 1984, 11 years prior to the debut of the 32-bit processor according to the nimrod author. I don't have solid dates but I know that within a year of this timeframe Suns and Apollo workstations were using this chip.How disgraceful.
blakespot
-- Heisenberg may have slept here.
iPod Hacks.com
The Itanium we have takes a ton of power and has 6 fans. How does AMD expect to put their chips into a laptop?
Let's say you have an elaborately-customized server setup. Let's even imagine that some of your storage for both data and programs isn't sitting at a single PC, but is in network-attached storage. Now, you want to upgrade the hardware to 64-bit without having to recompile everything - or maybe just upgrade some of the servers while continue to share program code off the storage.
You get only one answer: AMD. You can take your complexly-configured servers and not have to redo them from scratch. And the hobbiest gains the same advantage - swap drives, compile yourself a 64-bit kernel, and forget about doing a virgin install of Debian 64.
___
"with their freedom lost all virtue lose" - Milton
This is news?
R oo m/0,,51_104_543~19746,00.html
The Opteron was announced on April 24, 2002:
http://www.amd.com/us-en/Corporate/VirtualPress
The "Hammer" processor family (i.e. the Opteron, Clawhammer, and Sledgehammer) has been a topic of informed discussion for at least the last 18 months.
Thank you for choosing us for your provider of guaranteed successful Slashdot article submissions! Soon you'll be e-mailing your friends to tell them your alias is on the front of Slashdot.org! In minutes you'll be modifying your resume to put "published on Slashdot.org" at the top! Your credit card has already been billed for $9.95 for this amazing service!
a -bot? dept.
Say goodbye to seeing your articles in the submission queue rejected! Simply follow the three easy steps below to fame and fortune!
1) Choose a story below and read it carefully several times, trying to memorize the idea of the article but not necessarily the details, they aren't important.
2) Go watch TV for an hour.
3) Go to http://slashdot.org/submit.pl and type in your story. Don't forget to choose a memorable alias, it will soon be on the front page of the premiere geek news outlet on the Internet!
Remember, tell your friends about us, and receieve a half-off coupon on your next order!
Ask Slashdot: Open Source Politics - Maintaining Your Vision?
Posted by Cliff on 04:53 PM July 22nd, 2002
from the keeping-your-project-on-track dept.
Theovon asks: "I have only released one open source project so far (link below), and I have never submitted patches to any other, so I am very unfamiliar with some of the politics. I have a new open source project I am considering releasing sooner rather than later, but I want to know how to keep control over it long enough to get into it everything I want. Specifically, what I want to know is how to deal with unwanted suggestions by contributors. By unwanted, I mean submissions which may be nice but which would cause the project to deviate significantly from where you are trying to head. I think it's important to publically address this issue, rather than doing Google searches and piecing together a perspective of it on my own. think there may be many developers out there whose work could benefit us all but who are wary of what might happen if they were to let loose before they had achieved enough of their goals. In my ignorance and paranoia, I have been pondering the various negative consequences of an early release, and I would like to see what Slashdot has to say about these concerns."
BSD: New Scheduler Available for FreeBSD
Posted by Nik on 03:50 PM July 22nd, 2002
from the doesn't-blink-LEDs-when-switching-processes dept.
flynn_nrg writes "Luigi Rizzo, one of the FreeBSD developers, has just finished the code for a new scheduler. From the announcement: '...as promised, a first version of the Proportional Share scheduler that we developed is available here. These are for a recent -STABLE (i think any version from 4.4 should work; the only 3 files modified are kern_synch.c, kern_switch.c and proc.h, plus a one-line change to kern_exit.c). I have tested it a little bit on a diskless system, and it seems to survive running a full X session with the usual set of xterm, netscape etc. while i do a "renice" of the processes and even switch back and forth between schedulers. But do not trust this yet for a production system!' Read the full post here."
Your Rights Online: How Italian Police Shut Down U.S. Web Servers
Posted by timothy on 02:36 PM July 22nd, 2002
from the old-fashioned-way dept.
gessel writes: "CNN has an article describing Italian police shutting down a U.S. hosted website deemed in Italy to be illegally blasphemous. The article goes on to describe the ramifications and U.S. efforts along the same lines."
New Two-Headed Hard Drive Intended To Secure Web Sites
Posted by timothy on 01:49 PM July 22nd, 2002
from the or-serve-from-a-dreamcast dept.
dlur writes: "This article states that Scarabs (In Japanese), a Japanese company, is developing a hard drive with two heads, one read-only and another that is read/write. With this comes two cables, the read-only side going to the external web server, and the r/w cable going to an internal protected server. While this should make it quite a bit tougher for script kiddies to place their mark on a page, I doubt it will stop any real hackers from getting to a site's DB as that would still need to be r/w."
Linux Timeline By LWN and LJ
Posted by Hemos on 12:58 PM July 22nd, 2002
from the looking-at-my-navel dept.
A reader wrote to us with the link that Linux Journal has put together a Linux Timeline. Kinda nice to walk down memory lane - and think about what was on peoples' mind at each major point. Of course, if I see the original letter Linus wrote at the beginning one more time...*grin*
Open Source, Real Media Mega-player?
Posted by CmdrTaco on 12:18 PM July 22nd, 2002
from the to-little-to-late dept.
chill writes "CNN is reporting "RealNetworks on Monday will unveil a new open source version of its streaming media software that supports multiple file formats for audio and video, including those that use Microsoft's Windows Media technology." and "RealNetworks did not formally license the ability to offer Windows Media software, but instead re-created the technology based on data streams sent between the server and player software, The New York Times reported. A Microsoft representative told the newspaper that the company would need to determine whether RealNetworks licensed the software before taking action. " I can't wait to see the actual license." Update: 07/22 19:10 GMT by T: The software can be downloaded from the Helix site, if you're interested.
Interviews: Ask Dr. Richard Wallace, Artificial Intelligence Researcher
Posted by Roblimo on 11:20 AM July 22nd, 2002
from the how-will-we-know-his-answers-aren't-generated-by-
Today's interview guest is Dr. Richard Wallace, creator of the Alicebot and AIML (Artificial Intelligence Markup Language). Suggestion: look through some of the pages about Wallace in the first (Google search) link above before you start posting questions. Then, please, stick to the usual "one question per post." After this post has been up for around 24 hours, we'll send 10 of the highest-moderated questions to Wallace, and post his replies verbatim (except for minor HTML formatting) soon after he sends them to us.
Spam Doesn't Work?
Posted by CmdrTaco on 10:36 AM July 22nd, 2002
from the so-why-do-people-do-it dept.
An anonymous reader writes "Businesses who believe the hype that spam works should read this article. It seems that the more recipients that you spam, the less likely they are to respond (startlingly obvious, but this seems to prove it)." Somehow I doubt this. If Spam didn't work, why do I get a hundred pieces of it every morning? Someone is buying.
Cowboy Bebop Film's American Premiere Announced
Posted by CmdrTaco on 09:26 AM July 22nd, 2002
from the a-thing-of-beauty dept.
From the Big Apple Anime Site "The Big Apple Anime Fest 2002 (BAAF 2002) is proud to announce that the festival will premiere the theatrical English dub version of "Cowboy Bebop: The Movie" on August 30th, 8:00pm at Loews State Theater (Virgin Megastore) in New York City's Times Square. At the premiere, Cowboy Bebop director, Shinichiro Watanabe, score composer, Yoko Kanno and character designer Toshihiro Kawamoto will be on hand to meet their legions of fans." That's a show worth seeing.
16,000 CWRU Computers Getting Gigabit Ethernet
Posted by timothy on 08:19 AM July 22nd, 2002
from the fair-bit-of-bandwidth dept.
lowlypeon writes "In a move that makes going back to college more tempting than usual, Case Western is installing fiber connections in 16,000 computers over the next year to give students a 1 gigabit per second Ethernet connection. Administrators aren't sure what anybody needs that kind of bandwidth for yet, but they are curious to see how it gets used."
Machinima Festival and News
Posted by timothy on 07:14 AM July 22nd, 2002
from the leaping-media-batman dept.
Hugh Hancock writes: "Machinima (real-time 3D film-making in game engines, what used to be called 'Quake Movies') has a bit of a grab-bag day today -- the New York Times (registration, blah) is running an article on it, prompted by the announcement of the first Machinima-only film festival, sponsored by NVidia!"
Your Rights Online: Triangle Boy Lives
Posted by timothy on 04:14 AM July 22nd, 2002
from the antimissile-missile dept.
mlinksva writes: "Safeweb cancelled their free service late last year, but their P2P anonymizing proxy, Triangle Boy, has been spotted in the wild (south of Fort Worth, Texas). 'Because of its stealth nature, the P2P software does not show up in reports from many filtering products and the administrator doesn't even know the problem exists and has no way to check it.'(via UniteTheCows)."
F-22 Avionics Require Inflight Reboot
Posted by chrisd on 02:08 AM July 22nd, 2002
from the ctrl-alt-boom dept.
An anonymous reader writes "The Atlanta Journal & Constitution is fronting a lengthy piece on the USAF's new F-22 and its upcoming shootout with the existing fleet of F-15's & 16's. One line in the article really jumped out at me: 'When avionics problems crop up now, pilots must restart the entire system as if rebooting a personal computer.' I did some googling, and this is about as much as I could find: The hardware backbone for the system is the Hughes Common Integrated Processor, which, in turn, appears to be built around the Intel i960 CPU. I couldn't find a name for the operating system, but it appears to be written in about one and a half million lines of Ada code; more on the Ada hardware integration and Ada i960 compilers is here. Any Slashdotters working on this project? If so, why do you need the inflight reboot? PS: Gamers will be interested to learn that nVidia's Quadro2 Go GPU and Wind River's VxWorks Operating System are melded in the F-22's Multi-Function Display."
When Spun Really Fast, CDs Explode
Posted by chrisd on 12:16 AM July 22nd, 2002
from the vinyl-wouldn't-hold-up-very-well-either dept.
Anonymous Coward writes: "Ever wonder why cd-rom/cd-rw drives are not getting any faster? Wonder why they heat up? This page has a rather amusing experiment where they put various CD's into something that can spin up to 30,000RPM and found that most cd's explode at just around 28,000RPM. Oh and they seem to like using Corel CD-ROM discs for their experiment." Update: Yep, it's a dupe...
Your Rights Online: JPEG Committee On The Ball, Seeks Prior Art
Posted by timothy on 09:45 PM July 21st, 2002
from the real-buccaneers-ride-patent-submarines dept.
Sangui5 writes: "It seems as if the JPEG Committee has noticed the recent patent fuss, and is working on the prior art angle. Good to know that even though there's a new standard, the committee is standing by their previous work."
Sure, everyone 15 years ago thought 4 GB of memory would be PLENTY. But how about in another 15 years? Will an exabyte of memory still be able to run the highest end applications including Microsoft Office 2017?
I believe, from most articles I've read, that the AMD Opteron is targetted solely at the server market, similar to Intel's Xeon series of processors. AMD is going to try to remain true to the Athlon name with all its upcoming desktop processors. Personally, I think they will go with "AMD Athlon 64" as the new desktop brand. What's really to wonder about is their model number versus clock speed system. Up until now, they've used a linear equation to relate them:
(1.5*CLOCK)-500=MODEL
or
((2*MODEL)+1000)/3=CLOCK
This is actually contrary to the popular belief that they compare the Athlon XP's model number to the Pentium 4s' or Thunderbirds' performance.
If you want a "fresh" architecture that isn't full of old junk, buy an Alpha. Or for that matter a MIPS, SPARC, or Power4. All of which are 64-bit and have either always been 64-bit, or at least had their original 32-bit designs planned around 64-bit expansions.
Personally, I think it's amazing how much old crap has been piled onto x86. It's really remarkable it runs at all, and it's even fast! I used to turn up my nose to the x86 given how they piled all the 32-bit extensions on the old 16-bit core. It's really a travesty. And the actual instruction set and register set looks like a damn train wreck compared to MIPS or PPC. But they are soooo cheap I eventually got over it, and just try to avoid thinking about any level lower than 'C' now so I don't go insane.
April fools?
Bill (Gates) announced that Microsoft(tm) would support Opteron. Jerry (Sanders) gave nice pro-Microsoft(tm) testimony at the anti-trust trial. Funny how Microsoft(tm) seems to encourage competition in the x86 market. Oh well. I'm not complaining if it keeps AMD and the x86 market viable.
It's not flamebait, asswipes. Athlon XP chips actually do have pretty serious heat issues. If your heat sink fan ever fails, your chip has maybe five minutes to live. Ten if you're real lucky.
I learned this to my (financial) pain when I told a friend not to worry about a noisy heat-sink fan; I'd fix it when I got around to it. Once the fan seized, that was all she wrote, and it was back to CompUSA for another $150 shot of K7XP goodness.
What's stable enough for real work? My Athlon currently shows uptime of 47 days. Interestingly, I upgraded the OS about a month and a half ago. I don't shut down or reboot this machine except to upgrade it; I typically go for a couple of months without even logging out. I don't even quit Emacs every month. Is that what you mean by stable?
I do use this system for what could fairly be called "real work"; I usually use the compute cluster only for jobs that require more than 512 MB or aren't X86 compatible.
Well, in the case I have had to deal with directly, it didn't work. Supermicro motherboards have always been rock solid for me and that is what I want to stick with. Maybe, if I see more of my friends have better experiences with their setups, then I might give AMD another try. Until then, I don't want to spend any more money on AMD.
will be the two size-13s I plant in your ass, tps12.
Sheesh. Can you say "been there, done that"? What was Apple's slogan? Windows95=Mac8x. How about Windows02=Linux9x. (I don't know the exact dates that Apple used in their ad, or when Linux was 64bit)
But I hate it when the media falsely portrays, MS as being this great,innovative company. I know I'm sounding like a stereotypical /. poster, but that attitude just gives me a nasty rash on my left testicle.
This isn't a criticism of MS. This is a criticism of mass media. They have the responsibility to provide correct information to the consumer. Sure Windows is used by 90-something percent of home users, but this is a chicken and egg problem. Are consumers uninformed because mass media does not provide the whole story, or does mass media not provide the whole story since consumers are uninformed?
Boy, some of you asshat moderators are going to be in a world of hurt come metamod time.
A quick web search shows Itanium is x86 compatible.
Admittedly, the Itanium does this using emulation, whereas the Opteron is supposed to handle 32-bit instructions natively, however the statement that 32-bit code will not work on Itanium is quite misleading.
The Wired article has other errors as well. A 32-bit CPU isn't limited to 4GB; that confuses address space with physical memory. The definition of exabyte is wrong (1000 petabytes, not 1000 terabytes). The 8080 in 1981? Closer to 1975. And many have mentioned the bogus "no compatibility" claim.
One wonders if the whole thing wasn't a troll.
asshole
Just not the way you might think. An Intel Itanium-based computer running Linux64, Win64 (the codename for the 64-bit version of Windows 2000) or Windows XP 64-bit can run x86 (386, Pentium, Pentium Pro, etc) binaries unmodified. It will be significantly SLOWER than an equivalent x86 processor, because it does do it via hardware emulation, but it does do it.
Where the Itanium (and, I'm assuming, the Opteron/64-bit Athlon) really matter is in in large database and high-end workstation solutions. Basically, anything that needs more than 4GB of RAM. In these uses, it's not actually the processor speed that is needed, it's the RAM. The Itanium is meant for servers, yes. That is all the Itanium was designed for.
The cleverly named Itanium-2, however, is a horse of a different color. Not only is it faster (both MHz and IPC,) but it's cheaper, too! (You can get an Itanium-2 based system for about $3000.) The Itanium 2 at 900MHz is about twice as fast as the 'old' Itanium at 800MHz, performance-wise.
The only thing AMD has going for them (literally) is x86 compatibility. If it can run x86 code reasonably fast (i.e., a 1GHz Opteron running Pentium code at least as fast as a Pentium 3 1GHz) then it will be likely to take over the Workstation market from the Itanium 2. Unfortunately, I don't think anything could cause the Opteron to win over Itanium 2 in the high end server market.
Another non-functioning site was "uncertainty.microsoft.com."
The purpose of that site was not known.
From what I remember, Itanium represents a fundamental change in the way a processor works, and that is why there is no native backward compatibility. Which is good (I think).
The backwards compatibility requirement restricts performence increases. And for those that are running operations systems that are available on many platforms, such as the best OS in the world, what use is x86 compatibility, other than the ability to buy cheap hardware?
Currently, most CPUs fall in to one of two categories: CISC (complex instruction set computer), or RISC (reduced instruction set computer).
Both CISC and RISC processors execute binary code that can be viewed as assembly code (which is really just machine/binary code, but represented in a more human-friendly format).
On a CISC machine, that machine code is furthur decomposed (automatically by the processor) from machine code into microcode operations, which the processor hardware executes. On a RISC system, this microcode layer does not exist; the processor layer just executes the requested operations.
On a CISC system, the instuction set is larger, and some of the instructions may be specialized functions that perform very complicated operations. MMX from Intel (and all the other things like it) is a good example.
Usually, the barrier of granularity that would demark the microcode realm for the assembly/binary/machine code is drawn based on timing issues. Microcode programming requires the code be produced with an eye for allowed timing limits; this means that it is possible to have microcode sequences which will fail to execute because they were traversed in a way that violated timing requirements for the processor. For example, say microcode instruction XYZ uses some circuitry on the processor for 3 internal clock ticks; XYZ is executed at internal-clock-tick=0, and again at internal-clock-tick=2. The both executions will be corrupt, and the reason is timing. (NOTE: I think I even remember seeing a linux driver that allowed you to read your processors microcode)
Well Itanium moves the microcode layer of abstraction into the compiler. In the old days, the human user programmed assembly and could not be trusted to adhere to all the timing restrictions. Since most programming is now done in higher-level languages, the machine-level code is generated by the compiler - and a compiler can be made to adhere to timing requirements.
Itanium is an advancement in processor design, and one worth given up the ability to boot into DOS for.
In 1929 Duesenberg guaranteed their cars to reach at least 120 MPH. They had a 7 liter, DOHC in-line 8, 265 HP engine. Skinny tires, wooden frame, sounds risky. I have seen statistics that over 40% of all Duesenbergs Model J's made, between 1929 and 1937, survive today. No doubt, they were the absolutely best cars ever made.
Gimme a break! The reason has nothing to do with Windows XP. It has to do with databases more than anything. Crikey.
I am sure that Intel is really happy that the chief architect for their partner in their 64-bit efforts is endorsing the competing technology.
I heard that guy likes to fuck the folds of fat that pour off CowboyKneelingDownToSuckCock.
Of course, you are not prepared to accept this simple truth. Your mind has been shaped by the religious clergy, in whose best interest the concept of "free will" was created. They can charge more for pardon if you think you are guilty of those natural and inevitable acts which they claim are sinful and you could have avoided.
uh.... no.
Ignoring the two power outages due to lightning storms (destroyed a risc machine), one of my office athlons has been up for ~270 days. This most recent stretch has been 39 days, in large part due to plugging it in to the new UPS.
Another system I was using was up from September 2001 through March 2002. We lost power in the machine room, which has a habit of killing uptimes.
Sorry, if you need a clue on uptime, compare this to my P III based lap top. Cant keep it alive for more than 3 days without a reboot.
The real future lies in the Octium Chip, created by e-com-con
But I don't need to tell you that.
my sig
"While the first 32-bit processor came out in 1995, the average PC used 1 MB of memory, so 4 GB was both unaffordable and generally not needed. But the recent advent of Windows XP and digital media has changed all of that."
It's cars built to run on leaded gas that have trouble running on unleaded, not the other way round. They burn their exhaust valves. Newer cars built for unleaded gas may destroy their catalythic converters if fed leaded gas, but it will not damage the motors.
They fall behind, and they try to keep everyone else there with them. I remember when Intel released the Pentium. AMD pointed out that it was not (yet) as fast as a 486 of the same clock speed. They claimed that the 486 still had a lot of life. No one needed anything faster. They released a lot of inaccurate and misleading benchmarks. They did all of that trademark deceiptful crap because they only had a 486 to offer. As usual AMDroids fell for it. Now AMDroids spread front page lies like "IA-64 is not backward compatible at all" and Microsoft is supporting AMD, but not IA-64". Deja vu. If you want to buy AMD processors go ahead, but why do you feel the need to lie to everyone else, if AMD processors are so superior?
Are there any ports of bochs that pass system calls through to the native system so that none of the actual OS is running inside Bochs? This would allow you to, say, run x86 Linux code on Linux PPC or Win x86 apps on Win ia64. This assumes, of course, that the system call numbers and arguments are the same across architectures. Maybe it would require too much OS-awareness in Bochs in order to fix the endianess, but it would be nice to move away from hardware x86 decoders.
Please someone tell me that all of the 64-bit mode instructions are the same length. (Maybe the caryover instructions from x86 need to be padded with nops.) Varaible-width instructions absoutely kill hardware or software decoding speed, especially if you're trying to parallelize it. Maybe we can all migrate to pure x86-64 instructions and slowly rid ourselves of the old x86 instructions?
Ideally, AMD would come out with a RISC cpu with an open source x86 emulator for the OS vendors to integrate with thier OS. I would love to be able to have comodity RISC or VLIW chips on pricewatch. x86 decoding is a waste of heat and chip realestate.
Copyright Violation:"theft, piracy"::Anti-Trust Violation:"thermonuclear price terrorism"<-Overly dramatic language.
I think you are wrong. As I remember, the 8088 was a version of the 8086 with an 8 bit data bus (the 8086 has a 16 bit bus) but was still a 16 bit processor. I also wouldn't say it failed quickly, as it was the basis of the IBM PC. Maybe you're thinking of a different CPU?
imagination is more important than knowledge --Albert Einstein-
As was already mentioned he states that the first 32 bit processor was released in 1995 when in actuality it was a motorola processor in the 1980s.
Immediately after that he states, "(in 1995)...the average PC used 1 MB of memory..." perhaps I'm wrong but any computer I have or remember from that era had more than one meg of memory. For instance, I just dismantled an old 386dx from circa 1992 that was equiped with 4 megs or ram. My girlfriends 486dx has 16 megs. And I have an older pentium 166 non mmx from 1996 that has 32 megs. He also says, "Opteron will be in servers, desktops and laptops."
Again correct me if I'm wrong but isn't Opteron the server version of the Hammer chip. I believe that the desktop version of the Hammer is still codenamed Clawhammer.
I don't know where the hell this author gets his information, but I'd appreciate it if he would pull his head out of his ass before he writes anything else.
1000 terabytes in a petabyte,
1000 gigabytes in a terabyte,
and so on.
Roey.
<zim>EH?</zim>
The Opteron is compatible with all software made since the 8086. Therefore, the Opteron cannot truly be called new technology. It may have evolved in certain ways, but at its core it is no more advanced than the 8086. You can read AMD's whitepaper, and it will confirm: AMD knows that RISC, or specifically VLIW, is faster than CISC, but doesn't want to switch because of the installed base.
Intel, with the Itanium, takes the opposite stance. They know that CISC sucks, and that x86 was doomed from the start. It's not that "new things are better"; VLIW processors could have been developed in 1980, and if they were there would be no need for Itanium. But they didn't. So Intel wants to use 64-bit as an excuse to throw out x86, and start over the way they should have from the beginning.
Let's hope that Intel uses it's 75% marketshare power to win. It'll be unfortunate if AMD does.
Their PA-RISC machines have been pretty popular for things like airline reservation systems and low-end graphics workstations.
They also helped out with Itanium.
Hmm, well they got most of the info right, except the opturon the chip being marketted toward the server market. In fact, that is the second x86-64 chip to come out. and i believe that one is the sledgehammer chip, but that might be the second gen.
The desktop and laptop series will keep the athlon name
I doubt, therefore I might! So my sig sucks, so shoot me!
We're running a Dual AMD system here as a Win2k Domain conroller and it's stable as hell. I'll never have a problem recommending them for mission critical systems.
We don not want an 80x86 compatible chip. It's crap. It's an outdated CISC architecture. Has anybody read the complete white paper on the IA64 chip? Intel may have completely screwed up the implementation, but as specified (by H.P. originally) the chip is kicking ass and taking names.
Some extremely large percent of the silicon (and thus power dissipation and heat generation) on the athlon line is spent on the insanely complex variable length instruction decode needed to break old legacy x86 instructions into smaller pieces to feed to the well designed and powerful execution units.
A well designed RISC with optimization and caching hinds built into the object code will kick the living shit out of a 64 bit CISC hack built on top of an instruction set that was designed to run pocket calculators and automatic washing machines.
---
Play Six Pack Man. I
I wonder if Linux 2.6.x is going to be out yet by that time, since the AMD-X86-64 is supported only in the 2.5 tree. I doubt it, because the feature freeze is going to go in on October 31st (correct me if I'm wrong). Who wants to run 32 bit code on this anyways (yes, i know all the Windows users). I wonder if major distributions like redhat, or mandrake, suse, or debian (debian will for sure) will have support for AMD-X86-64. I bet gentoo will be a popular distribution for runing these babies on.
(An exabyte is 1,000 terabytes and a terabyte is 1,000 gigabytes.)
Isn't a 1,000 terabytes a petabyte?
bytesmythe
Hypocrisy is the resin that holds the plywood of society together.
-- Scott Meyer
The article is new. Might be out-dated, but it is a new article
No, binary compatible is the 8088/8086, the former
8-bit to the mainboard and thus exclusively used in
IBM PC and XT, the latter one year earlier, but with
its 16-bit bus making mainboards twice as expensive.
The 8080 has a different command set, but with some
macroes 8080 assembly source code can be re-compiled.
My Karma isn't excellent, damn it! (And
Why support AMD when they take advantage of open-source developers to get their product supported while at the same time embed Paladium / DRM garbage in their products which will be used by Microsoft to extinguish Linux?
I will certainly only buy another AMD processor if I hear they are dropping this ridiculous 'feature'.
It is addressing memory concerns with 32 and 64 bit processors. However these are general registers. The address bus actually determines maximum memory limitations. The address bus on the Pentium IV is 36 bits (64GB) where as the athlon (I believe) is 8TB. I expected more out of a wired reporter / cpu symposium rep. How can this entire report be based on erroneous info?
Well I'll buy it if I can still play Wolfenstein 3d and Doom 1/2. Those games stilll get played on my puter, because they are timeless classics.
Comment removed based on user account deletion
This is probably a stupid question but here goes:
Why can't they just make it completely 64 bit and have another processor handle the 16/32 bit code? That is, turn it into something a native 64 bit chip could handle easily.
Adding another chip to the motherboard is hard, but not if you have it as part of the original spec. The 16/32 chip could be similar to what the math-coprocessor was. The slot was empty unless you needed it. Though it was on the motherboards.
It shouldn't even be that hard. With all the work going into the 64 bit processors, the 16/32 bit coprocessor would need no development, and would be cheap to manufacture once the original design would be out. Of course, such a design would allow future developnment of the same. Should a 128 chip ever come out, the coprocessor could than be 16/32/64.
I still have a 5 1/4 inch floppy drive. Why? At the time I bought it, it was just in case, and it was an open slot in the case. It's there, in rare cases it get used, and it's cheap. I guess I'd like to see a 16/32 chip the same way. (Maybe even throw java onto it).
Now, obviously Intel and AMD have people looking at all the possibilities, so I am under the impression that this idea is not possible/feasible. Why is that?
Have you read my journal today?
Slashdot ran this story About Intel's 64 Bit x86 CPU if the Itanium fails or AMD's 64 bit chip does better.
A little like how Apple included the Classic and then Carbon compatibility level, so that Mac OS X can run old software. It meant that the first day I got the public beta, sure - there were a lot of little unix apps I could run at the command line, and a few little Aqua apps, but the majority of software I ran was through Classic.
As time has progressed (about 17 months later) there are plenty of Carbon and Aqua apps so that I almost never launch classic anymore.
- passion
This may be nonsense since I don't claim to fully understand how 32bit and 64bit differ at the application level, but here's my guess at the reasoning from a marketing standpoint:
Pure 64bit with no backward-compatibility -- this CPU is intended for dedicated software that's designed for 64bit from the ground up. I'd expect this to be aimed at primarily at the server and database market, where new apps are likely to be written simply because the old ones no longer handle the load -- while you're at it, might as well design 'em as pure 64bit from the gitgo and ditch the compatibility kludges. This CPU is likely to be a higher price bracket since the target audience is essentially the enterprise market.
64bit with 32bit compatibility -- that's for 32bit software that is already overstressing 32bit's 4gig memory-addressing limit. I'd expect this CPU to be aimed primarily at the CAD and video graphics market, where existing apps are likely to remain in primary use for some time (because they still do the job and are too expensive for their current market to replace). This CPU is likely to inhabit a lower price bracket since the target audience is independent designers, small studios, and the like.
IOW, it looks to me like AMD and Intel are courting two completely different and separate markets.
~REZ~ #43301. Who'd fake being me anyway?
Was it based on a Via Chipset (with a 686B bus?) If it is, then it has what some people call the 686B Bug, which can be easily fixed if you get the newest 4in1 drivers from via.
Thank you©© That© was ¥ very helpful¥©
It's 10 PM. Do you know if you're un-American?
1) Lack of a thermal diode. The CPU will burn up easily if the heat sink falls off, even partially.
2) Cheaper packaging (this has to do with the construction of the cpu)
3) Cheaper motherboards. A bad motherboard is a bad investment, no matter how low the cost is. Don't buy a Via.
None of this should prevent people from buying AMD, but it is something to think about.
"Any connection between your reality and mine is purely coincidental." -Slashdot
Have an "old style" chip and a new-style chip. Big apps then use the 64-bit chip and the old one's use the 32-bit chip.
Table-ized A.I.
actually if you werent such a Intel fanboy, you would know that Athlons do have a thermal diode since the XP's came out last year, the chip packaging is the same as the p4(except no heat spreader) and my $50 FIC motherboard with the VIA KT266A chipset hasnt failed me ever.
Are you serious? You cannot possibly be that stupid.
You traced the problem to a motherboard and close by blaming AMD for their processor, which was (according to you) not the cause of the crashes.
please ignore... testing out posting problems :-\
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Intel made its chips backwards compatible.
Not like Alpha being compatible via FX32 (software emultion), Intel has full hardware support.
DEC controlled the whole system, the add in cards, the OS. They could get away with FX32.
Intel just makes chips. This will allow them to execute x86 compiled drivers, x86 applications, etc without having to get every single OS on the market to support it. Sure they could throw some engineers at MS and help them make a FX32 system for IA64, but what about GNU/Linux and BSD? They'd need to comply with the GPL for GNU/Linux support, which would piss MS off, or just have only Windows be backwards compatible, which wouldn't be good for them either.
This way works great for them. All they had to do was build an x86 decoder onto the chip and reuse the FPU, integer units, etc off the regular chip. Obviously without any OOOE logic its not going to do any better than a high MHz Pentium, but you don't buy an Itanium for high speed 32bit execution, you buy it for high speed 64bit execution of programs using over 4gigs of address space and the convience of being able to use MS Office on the same machine.
I can't wait until the Voodoo3 is announced! Damn, that chip is gonna be sweet!
/^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,4}$/i
Met with some folks at AMD a few weeks ago, so maybe I can contribute here:
It does have a IHS (Integrated heat spreader) so you will not chip cores!
It still runs damn hot though.
It is HEAVY. I mean physically heavy. I don't know why.
Current Opteron chips (the Clawhammer) are running at 800-900MHz, and have a very high number of IPCs (instructions per clock cycle) so they perform very well.
They will ship at relatively low clock speeds, but perform equivlently to AthlonXPs or Pentium 4s clocked much higher.
The first of the series will likely either be called the Opteron 3000+.
reflect the fact that the Itanium is a piece of crap.
It's too expensive a solution. There are better solutions, since they are not powerful enough to warrent the extra cost over a normal x86 server and cannot approach the power/flexibility of a multi proc server from Sun/IBM.
It's just a bad decision from a money perspective.
Imagine a Beowulf cluster of whatever this story is about!
I never thought I'd live to see the day that I read a funny "imagine a Beowulf cluster" -joke.
Note to all posters: This doesn't mean your beowulf cluster joke if funny. To be on the safe side, never post one.
The best thing about the Itanium is that not only can you run your x86 binaries really slowly, you can also run all those PA-RISC binaries you have laying around really slowly, too. How helpful!
I'm just being annoying here. No disrespect to any PA-RISC users intended at all. I quite like the PA-RISC architechture, and the workstations built with it are top of the line equipment, at least in my experience.
PA-RISC Powered, Baby! Hell, yeah!
Sorry.
-Lawrence
Visit Zymurgy Records!
believe me, i am no amd weenie. ;)
and i have moderator points, that i could have used on that post, but decided to reply instead.
that post was(is?) flamebaitish, the guy just spewed a bunch of stuff he admitted he had no evidence for. especially that part about amd having more performance...sheesh..
thier are times when being a mac user makes me want to die laughing, the intel world is just NOW getting 64 bit computing? What next they get get a powerbutton onthe computer? A mouse? ooh I know next we'll get a GPU MPU? holy fuck.
Anyone who really needs the power of a 32 bit desktop was already happily using a VAX workstation 15 years ago.
Best Slashdot comment ever
All I know is the Civ3 with a hugh map on an AMD 2100+ w/512 DDR crawls. I would be really happy for any CPU that can make a turn at the tail end of the game (4 players, 300+ cities, 1000's of units) take less then the 10 mins. it takes to churn thru now! Who give a damn about datebases, or weather sims, or data, et. al. - make my game run faster! (Note: This is scarcasim.)
Dropping compatibility with the previous x86 architectures may effectivly drop serious issues such as platform-specific virii. And most virii, except maybe 45 proof-of-concept Linux virii, exist only for Microsoft Windows on the x86 arch. I think the situation is similar to the United States of America's problem with Chicken Pox (lol). The disease(or computer virus) that existed and killed hundreds and thousands of years ago will be brought back to life a couple decades after it was eradicated (yes obsoleted). Wouldn't that be somthing to read on slashdot...
Timothye r-contracted-department .NET platform as a dispersal and deliver its payload to all computers that are compatibl with the old 16bit 286 micro-architecture released in 1982 by Intel Corporation. CowboyNeal_DotEater has apparrently taken down Microsoft so far, and all Apache servers have been experiencing a large slowdown from such a simulated DDOS and luckily are not affected due to the nature of mostly Sun Sparc, HP PA-RISC, older DEC Alpha hardware, and generally all Unix systems running Apach are not based on the x86 platform. The cause for all the problems from CowboyNeal_DotEater is an infected system will immediatly have all user database of Microsoft OpenLook Express eMail address books will be violated with randomly sent copies of CowboyNeal_DotEater, and durring the local hours of Breakfast, Lunch, and dinner on the respective infected server that CowboyNeal_DotEater will remove all occurences of a period or "." within all code on an infected server's local harddrive and SMB, FTP, NFS, and HTTP file shares, and a local user activly editing a document will be unable to place a period or "." due to a little happy face appearing on the screen and consuming the targeted ascii sentance terminator. There has been no known cure and so far all of the affected computers on the internet, nearly 1/10 or 600 billion independant AMD Athlon OptiFloss Microsoft IIS.NET servers. However, the average websurfing consumer will not notice this malicious virus due to the popularity of Microsoft software on Fortune infinity E-commerce websites not being Microsoft customers. However, 9/10 of all desktop computers are Microsoft Windows based and are affected also. We here at Slashdot.org and the Free Software Foundation suggest you install a more stable and immune Operating System such as Gnu Hurd. As always, we will be covering this story randomly and give all affected users an update in 4 months. Thanyou for the privilege...
From the you-wont-believe-what-my-antivirus-said-my-comput
UberTroll wrights: After a 20 years or so of dormancy, a computer cracker decided to release a new strain of the x86 CowboyNeal_DotEater virus back into the internet. This new radicle virus has been re-engineere to use the
But I'm sure you already Gnu that.
so the next version of Windows will be "Windows 64", the next Office "Office 64", and word "word 64"
I am not sure where you get this information from, or why not the editors have not checked this statement. The IA64 platfrom supports IA32 code. Read Intel Itanium Architecture Software Developer's Manual Vol. 2 rev. 2.0: System Architecture Part II chapter 9 entitled IA32 Application Support
Support by the operating system is needed, something that already has been built into the Linux kernel. I recomend reading Chapter 11 in IA64 Linux Kernel - design and implementation. IA32 programs will think they are running on a Pentium III computer.
The recomendation is to not run IA32 programs on IA64, but to recompile them for the new architechture... but that is kind of obvious..
With Moore's Law doubling performance every 18 months...
;9
This shows how little the author knows about the subject, the rest af the article looks like rewrite and tidbits from other articles.
On the other hand, did he mean that Moore's Law increases the performance of the chips? Then one is left wondering what research and engineers are for...
Carbon based humanoid in training.
Don't buy a Via.
Yeah, get some quality AMD in there! Or hey, if you want real performance, buy SiS!
Yes I am being sarcastic. Via is the best out of the three. These days, however, buy nVidia!
Sun has been producing a VLIW processor as well,called MAJC (pronounced "magic"), since 1999. Look here
Stick Men
Yet the Alpha seems to be forced into complete non-relevance by the mass media. (Witness the Wired article, where it's not even mentioned.) Is the Alpha really that irrelevant? Is the experience gained (both technically *and* marketing-wise) to be tossed and never thought of again?
It's a bit older than some of the other RISC designs, but it is rather cool and cheap and used in an awful lot of places (e.g. GBA).
Actually, the Athlons do have a thermal diode, just like the Intel chips. It's only that older motherboards dont use the cpu thermal diode, but use their own external one instead. And that one cant react fast enough to a heatsink removal. It will react to fan failure tho.
If you get a motherboard that does use the internal one you dont have a problem.
Of course... I cant say I find it likely that a heatsink would fall off. You'd have to drop the box from a pretty fair height to manage that.
When is it time for us to move on from such an old architecture? Surely there is some luggage in there we can now do away with?
Even software languages have broken compatibility at times to advance. Can't hardware do the same?
Comment removed based on user account deletion
Physical memory was extended to 36 bits by the PII (or was it PPro?).
For greater than 4Gb virtual, you can still use segmentation. A process can have (what, 12 bits of local segments, 12 bits of global segemnts) 8192 segments, each with 4 Gig memory. Hardly a hard limit. It just means data has to be broken up. All you old 286 programmers know how to do that don't you.
Note: AMDs X86-64 will supposedly discontinue support for segmentation in 64-bit mode.
There is nothing so silly as other peoples traditions, and nothing so sacred as our own.
As you said, each processor has its own memory. If a processor needs data in another processors memory space, it has to request it over the Hyperchannel bus, not quite a local request (NUMA).
Multithreaded programs share a lot of data between threads.
Sooo. what you really mean is that two independant processes will each run as if on a dedicated processor (which they will). But multithreading will still have some memory and bus contention.
There is nothing so silly as other peoples traditions, and nothing so sacred as our own.
Yay!
It's all good.
You are quite right. The members of this website in many areas can be hypocriticial and knee jerk reactionaries. However this is typical of the public (especially the American public [of which I am a part]). They are most assuredly now finding favor with AMD for the very thing that they have been upset with Intel for /YEARS/ over, the backwards compatablity and inefficency issue. Intel's introduction of the Alpha chip was a /major/ step in the right direction and definately help thos of us in the industry who wanted to strike out in a new direction away from the x86, but the high cost due to Intel's failure to embrace the technology (and in general foist it on an unwitting populace for their own good [because let's face it, at that point in time Intel could have made that move without having lost significant market share and would have re-established itself as a market leader with a significantly better technology]). In defence of the people of this forum is they are fairly intellegent as a rule. I believe we as users of AMD chips have found that they perform at a higher computation- rate-per-second/per-clock-cycle than their much lauded competiter Intel (when refering the x86 chip), furthermore they are even less expensive on a clock-rate to clock-rate comparisum. Admittedly part of this is because AMD has been trailing Intel rather than blazing new ground, and it will be interesting to see if they can maintain this with their new 64/32 chip where (perhaps) they are striking out in a new direction than Intel, and may have to substain substantail R&D costs of their own. But AMD has earned our respect, while Intel has not, thus the knee jerk.
Hear, hear!
I don't know where the author got this piece of misinformation. Perhaps it's a FUD distortion from AMD relating to the fact that Itanium was not designed to run 32-bit apps, so it's not terribly efficient (read slower) in doing so -whereas Opteron, which is basically a 32-bit processor with address extensions is more efficient at running legacy code. Presumably, Hammer will not perform as well on real 64-bit apps as Itanium since it lacks massive parallelism and other architectural differences that Intel felt they needed to put into IA64.
AMD loved to talk the talk but has trouble walking the walk.
Meanwhile, why hate Intel? Sure they have stepped on some toes in the past, but they are supporting (even funding) Linux, helped get Linux ported to Merced first before NT. Have you ever notice that AMD spends half its press conferences badmouthing Intel while Intel never says anything bad about AMD? Finally, what about AMD's backdoor deal to defend Micro$oft?