No, not "read", worked with. Intimately. The PPro 200 was the only chip in the (initial) family that was of any great significance. I'm not sure which Alpha was "released" at that time, I'm confused as to which preproduction model I had in hand, but the PPro could not touch the AXP 233. The AXP 150/166 was already approaching 2 years old when the PPro came out. P6-150's were marginally better than the P5-133's. 32 bit software only.
Yes, the P6 core has definitely had some pretty long legs. And it was a design I was thoroughly upset at Intel for dumping for that bastard P4 architecture. 20 stage pipelines, who'd a thunk it? Itanic on the desktop. almost 3 years, and they've gone a Ghz and a half?:-)
The original P54C took the major hit because they sold it as "workstation class" and it ended up having such a nasty floating point bug that it killed it's early adoption (nevermind that the Pentium was a DOG compared to the new AXP 150 at the time). The consumer market (in the form of AMD, I believe) started with the clock-tripling. Once this was seen as a viable option, you set the stage for the eventual Pentium Pro debacle, where it was Intel's king of the hill for about 2 months before some Pentium MMX CPU's started kicking the crap out of it.
In all respects, that's the one thing that Exchange has that I *REALLY* like. vbscript forms around your data to build more robust applications. Issues with Version Control and replication aside, it's a decent applications platform, especially if you're doing sales force automation.
You need a server CAL for EVERY desktop that connects to your server, no matter who it is. You need an Exchange CAL specifically for Exchange clients, IMAP/POP3 included, AFAIK.
You just don't have to pay the outlook tax, or the windows desktop tax.
How reasonable is it? The Pentium wasn't slower than the 486, 486 wasn't slower than the 386, and the 386 surely wasn't slower than the 286... The Pentium Pro was an anomaly. It was rushed. Intel was getting slaughtered by Alpha and others, and losing (can't say lost, they didn't really have any to speak of) quite a good bit of marketshare in the workstation market (which Intel wanted to expand into). Hence a processor that in it's slowest version, 150 mhz, was not much faster than a Pentium 133.
Well, their hope was that they could translate some of that hyperthreading into real performance advantage with those uber-deep pipelines they have (what marketdroid thought THAT was a good idea?). When that failed, back to the drawing board...
Mostly because there's little consistency in web browsers. There's nothing stopping IE from supporting 100 file+ uploads, but interfaces are sometimes more difficult to write in Javascript than to wrap an MFC widget around something. It's so hard writing a javascript interface that A) looks the same on every browser, and B) different versions of the same browser.
IT departments can't control what goes on with personal laptop computers either. Protecting the network from itself is getting to be big business these days.
You know, now that you state the blatantly obvious, it does...
Wonder if it would have made a difference (and no, I'm not willing to find out;-) ).
For whatever reason, it seems like YaST2 on particular devices doesn't like detecting them unless you've rebooted a couple times. For instance, it never loaded the i2o driver for my supertrak controller until AFTER I had the promise driver working...
I thought that was moire, and anti-aliasing was taking sharp edges (whether stair-stepped or not) and make them less sharp so as to make them pleasing to the eye?
Mostly because, in the U.S. at least, there are at least 3 distinctly different and mutually incompatible cellular networks, so you automatically lock yourself out of one of them.
You'd have thought those fuckers would have put in a link:
Get newest super-duper version of IE <a href>Here!</a>.
They can take the time to tell you that your browser sucks, and is unable to use their website, but they're clueless enough to not be able to promote their own fucking browser. Morons.
Once upon a time, most installers had the ability to interrupt the install process, and fix things from a command prompt if for some reason the installer bogeyed (like say, screwing up your LVM configuration?). SuSE 8.2 gave me NO end of troubles trying to get my Promise SuperTrak SX6000 and LVM working. I had to boot a rescue cd, munge the LVM configuration myself, reboot, get SuSE to boot off my munged boot image, copy a shitload of files locally, and then run yast2 all over again to get stuff installed. It was miserable.
Contrast with RedHat 6.2, where I could drop to a shell, do all my stuff, then fg % back, and continue on my merry way.
Installers *CAN* get too dumb. It's one thing to make sophisticated installers. It's something else completely to take away the flexibility and power of Linux just to satisfy the need for a dumb-enough-for-grandma install tool.
Why not a simple menu option, F12 for uber-super installer mode?
Slashdot Mirror
No, not "read", worked with. Intimately. The PPro 200 was the only chip in the (initial) family that was of any great significance. I'm not sure which Alpha was "released" at that time, I'm confused as to which preproduction model I had in hand, but the PPro could not touch the AXP 233. The AXP 150/166 was already approaching 2 years old when the PPro came out. P6-150's were marginally better than the P5-133's. 32 bit software only.
:-)
Yes, the P6 core has definitely had some pretty long legs. And it was a design I was thoroughly upset at Intel for dumping for that bastard P4 architecture. 20 stage pipelines, who'd a thunk it? Itanic on the desktop. almost 3 years, and they've gone a Ghz and a half?
The original P54C took the major hit because they sold it as "workstation class" and it ended up having such a nasty floating point bug that it killed it's early adoption (nevermind that the Pentium was a DOG compared to the new AXP 150 at the time). The consumer market (in the form of AMD, I believe) started with the clock-tripling. Once this was seen as a viable option, you set the stage for the eventual Pentium Pro debacle, where it was Intel's king of the hill for about 2 months before some Pentium MMX CPU's started kicking the crap out of it.
Unless that web interface can cache it's data locally, the client/server round trips are gonna kill you.
-Chris
Thank god someone else agrees with me. :-)
Right. You *WANT* to run vbForms on a Mac? ;-)
In all respects, that's the one thing that Exchange has that I *REALLY* like. vbscript forms around your data to build more robust applications. Issues with Version Control and replication aside, it's a decent applications platform, especially if you're doing sales force automation.
You need a server CAL for EVERY desktop that connects to your server, no matter who it is. You need an Exchange CAL specifically for Exchange clients, IMAP/POP3 included, AFAIK.
You just don't have to pay the outlook tax, or the windows desktop tax.
Hah! I had to find a guy two towns over. It was like crack, man...
me: w0ts up d00d
him: d00d, go g3tz th1s sw33t m0d: <serdoom>
me: dr00l
yeah, good old days of one on one rocket fests... That was what, 1993?
Then there was the time I got busted in '94 with 6 of my friends coopting the SGI's at work to play networked Doom. Now that was a blast.
Why oh WHY aren't there more cheerleader shots???!?!?!?
I mean, come on, on an HD broadcast, put a little picture-in-picture cheerleader-cam on for us...
How silly, indeed!
How reasonable is it? The Pentium wasn't slower than the 486, 486 wasn't slower than the 386, and the 386 surely wasn't slower than the 286... The Pentium Pro was an anomaly. It was rushed. Intel was getting slaughtered by Alpha and others, and losing (can't say lost, they didn't really have any to speak of) quite a good bit of marketshare in the workstation market (which Intel wanted to expand into). Hence a processor that in it's slowest version, 150 mhz, was not much faster than a Pentium 133.
Well, their hope was that they could translate some of that hyperthreading into real performance advantage with those uber-deep pipelines they have (what marketdroid thought THAT was a good idea?). When that failed, back to the drawing board...
www.objectstore.net
Amazon.com uses it.
Mostly because there's little consistency in web browsers. There's nothing stopping IE from supporting 100 file+ uploads, but interfaces are sometimes more difficult to write in Javascript than to wrap an MFC widget around something. It's so hard writing a javascript interface that A) looks the same on every browser, and B) different versions of the same browser.
4x Plextor SCSI CD drive, with a dozen caddies that I hoard like diamonds... worthless, but so pretty, and functional when you need them...
bricks/stones, glass houses.
Re: sig:
cat[e]gorizing...
IT departments can't control what goes on with personal laptop computers either. Protecting the network from itself is getting to be big business these days.
You know, now that you state the blatantly obvious, it does...
;-) ).
Wonder if it would have made a difference (and no, I'm not willing to find out
For whatever reason, it seems like YaST2 on particular devices doesn't like detecting them unless you've rebooted a couple times. For instance, it never loaded the i2o driver for my supertrak controller until AFTER I had the promise driver working...
Cheers
I thought that was moire, and anti-aliasing was taking sharp edges (whether stair-stepped or not) and make them less sharp so as to make them pleasing to the eye?
Mostly because, in the U.S. at least, there are at least 3 distinctly different and mutually incompatible cellular networks, so you automatically lock yourself out of one of them.
Yeah, and they need an AMD64 OS too. ;-)
Betas notwithstanding...
versioning, maybe.
I was particularly referring to the graphical installer, where your issue should never pop up, but you do bring up a good point. Thanks.
You'd have thought those fuckers would have put in a link:
Get newest super-duper version of IE <a href>Here!</a>.
They can take the time to tell you that your browser sucks, and is unable to use their website, but they're clueless enough to not be able to promote their own fucking browser. Morons.
And we let them drive our entire industry...
Boy, are YOU gonna love Yast2 when it gets around to your distro...
Once upon a time, most installers had the ability to interrupt the install process, and fix things from a command prompt if for some reason the installer bogeyed (like say, screwing up your LVM configuration?). SuSE 8.2 gave me NO end of troubles trying to get my Promise SuperTrak SX6000 and LVM working. I had to boot a rescue cd, munge the LVM configuration myself, reboot, get SuSE to boot off my munged boot image, copy a shitload of files locally, and then run yast2 all over again to get stuff installed. It was miserable.
Contrast with RedHat 6.2, where I could drop to a shell, do all my stuff, then fg % back, and continue on my merry way.
Installers *CAN* get too dumb. It's one thing to make sophisticated installers. It's something else completely to take away the flexibility and power of Linux just to satisfy the need for a dumb-enough-for-grandma install tool.
Why not a simple menu option, F12 for uber-super installer mode?