In the age of the internet dividing rights up based on geographical regions makes little sense (if any).
In the age of the great Brusselian monolith devouring [formerly] free and independent states, I know it ain't exactly the fashionable point to make, but that BBC thang is [at least ostensibly] owned by [and operated for the pleasure of] the tax-paying British citizenry.
If they don't want us to see it, well, they're the ones paying fer it.
Remember, "Capitalism" is marxist - or at least Sombartic - rhetoric.
To the extent that we "believe" in anything, we don't believe in "Capitalism" - rather, we believe in freedom, which necessarily presupposes the existence of private property rights.
However, to equate freedom with something so vulgar as the ownership of a spinning machine, a steam engine, or a plow, is to lose the battle over language [ipso facto the underlying ideological war itself].
Hell, I'll go you one step further: To the extent that we "believe" in anything, it's not that we believe in "freedom," but that we believe in opposition to tyranny [which is precisely what the marxists would impose upon us].
And their tyranny begins with the corruption and nullification of language [as a vehicle for describing the truth].
What's the state of the art of Microsoft connectivity from behind a NAT router?
Time was, NT domain controllers couldn't talk to each other if at least one of them was behind a NAT, and I think that was true for at least the early versions of Active Directory.
Nowadays, can you get remote domain controllers [respectively - Active Directory controllers] to talk to each under something like the following?
BDC -> NAT -> OpenSSL -> NAT -> PDC
If not OpenSSL, then insert your favorite encryption protocol.
Oh, and the same question for Microsoft clients: What can you do for e.g.
client -> NAT -> THE CLOUD -> NAT -> PDC
so that the entire sequence is encrypted, and the client can, e.g. download and upload files?
FYI: For some reason, the new Slashdot code is inserting blank spaces in all these URLs, typically after "qc=" [making it "qc= "]. Anyway, bottom line is that none of these URLs work as is.
1) Copy the address
2) Start | Run | WMPLAYER.EXE
3) Ctrl-U to open a URL
4) Ctrl-V to paste the address
5) Remove the empty space that/. added after the word "windows" [so that the incorrect "/windows/" becomes the correct "/windows/"]
6) Hit OK
IMHO Don't EVER purchase hardware based on the assumption that it will be compatable with some future software. You really need to decide if you would be happy with this hardware running currently available software and purchase or wait based on that. FWIW I've got a few light servers based on this series of motherboard and running 32bit Linux (Debian) and I'm perfectly happy with the performance and reliability.
Yeah, I think we're in agreement there: I'll assume that there will be problems in upgrading to Win64, and, when they day comes, if there aren't any problems, so much the better.
But AMD seems to have utterly abandoned the 32-bit Athlon MP line, so those platforms are pretty much a dead end, in that they offer no hope whatsoever in terms of future upgradeability. Plus, they're stuck at a 266 MHz FSB.
I suppose there's Intel, but, quite frankly, I'm not in much of a mood to give them any of our money.
I write for the Inq, and I talk to people, this is more than idle speculation
Here's our big dilemma: We're looking at making a big investment in new AMD x86-64 hardware, especially the new line of 940-socket motherboards from Tyan.
So here's my question: If we invest in this hardware, what do you think the chances will be that, when Win64 finally starts to appear next year, it will be able to run on this platform?
I've got this foreboding sense of dread that we'll spend thousands upon thousands of dollars on hardware, and thousands of man hours getting everything up and running, only to discover, a year from now, that Win64 won't be stable on that platform.
Any thoughts on this, or any gossip? At this point, I'd take any information I can get my hands on.
Thanks!
PS: This WOW [Windows on Windows] software emulation crap may be the kiss of death for Win64. The whole purpose of x86-64 is to be able to run 32-bit programs at hardware speed.
Software emulation could very well be the straw that breaks the camel's back - it certainly sank the Itanic.
I know outsourcing is supossed to bring everyone up to the same level, but what happens if a cycle emerges, whereby companies just pick a region on a decade by decade basis, keeping wages down permenatntly! They'd like too you know. But that's worst case senario.
Or - the people could start their own companies, and stick it to the man.
What is it with this defeatist attitude around here? If you hate your job, then quit, and start your own company! BE YOUR OWN BOSS!!! Reap your own dividends!
Liberty. What an antiquated, 18th century absurdity...
Seriously, though: The only reason any job exists is to maximize shareholder value.
If the business structure is other than "C-Corporation" or "S-Corporation," then you can make a suitable substitution for the word "shareholder," but it's the same idea.
PS [for the grandparent] - You said: [I]t's YOUR job to do what they say.
I say: What are you, somebody's slave? If Massuh says "Jump," do you say "How high?"
Do you REALLY think that the point of 64 bit machines is having bigger integers?
The point is not that the "integers" are a different size on a 64-bit machine.
The point is that the counters that you use to index Java arrays are limited to 32-bits worth of [albeit relative] addresses, rather than the full 64-bit addresses of the underlying hardware and its operating system.
And yes, there are plenty of things that need to cross the 2 ^ 32 = 4 "Giga" barrier. Such as, for instance, high quality MPEGs of Gone With the Wind or Titanic.
do you really have 32GB of RAM in your machine for this task or are you just complaining for the fun of it??
I mean, really - 640K should be all that anyone could ever want, right?
Back to my original question, though: What is the point of a 64-BIT OPERATING SYSTEM if its FLAGSHIP INTERFACE is only 32-BITS? And will remain 32-bits into the foreseeable future?
How can a salesman in the Solaris division try to sell his clients a 64-bit operating system on exhorbitantly expensive 64-bit hardware, when, just last week, a salesman from the Java division dropped by and told the very same client that 32-bits was all they'd ever need?
Seems like the client might as well stick with a 32-bit Win32 platform running on 32-bit hardware.
Or, better yet, upgrade to a 64-bit platform [Win64] running on 64-bit hardware [AMD x86-64] with a true 64-bit interface [C# & the CLI].
Many characters had huge breasts that must have contained helium bladders to keep them upright, plus a titanium support structure built into their costume. They reminded me of Frank Frazetta's cover illustrations for Conan the Barbarian.
Uhh, remind me again why this is supposed to be A Bad Thing(TM)?
This is far, far and away the most important reply on this entire thread.
Of course, I'm not exactly sure what it means, and I'm still sitting here contemplating what it might have to say about salesmen and the pointy-headed bosses who purchase from them, but it's a must read for anyone who's curious about why things are the way that they are, and not the way that we think they should be.
PS: You can never overestimate the business in end of things, even in the tech world. For instance, I once read an interview with Thomas Watson Jr, in the WSJ, in the late eighties-early nineties timeframe, when it looked like IBM was about to go bankrupt, and he made the point that he thought it was a huge mistake when IBM moved away from leasing mainframes [which had been his great insight] and into selling mainframes. Oddly enough, with their massive push into "services" and "service contracts" over the last ten years, they've come almost full circle, back to the leasing model.
In the age of the internet dividing rights up based on geographical regions makes little sense (if any).
In the age of the great Brusselian monolith devouring [formerly] free and independent states, I know it ain't exactly the fashionable point to make, but that BBC thang is [at least ostensibly] owned by [and operated for the pleasure of] the tax-paying British citizenry.
If they don't want us to see it, well, they're the ones paying fer it.
My, that sounds like Capitalism.
Remember, "Capitalism" is marxist - or at least Sombartic - rhetoric.
To the extent that we "believe" in anything, we don't believe in "Capitalism" - rather, we believe in freedom, which necessarily presupposes the existence of private property rights.
However, to equate freedom with something so vulgar as the ownership of a spinning machine, a steam engine, or a plow, is to lose the battle over language [ipso facto the underlying ideological war itself].
Hell, I'll go you one step further: To the extent that we "believe" in anything, it's not that we believe in "freedom," but that we believe in opposition to tyranny [which is precisely what the marxists would impose upon us].
And their tyranny begins with the corruption and nullification of language [as a vehicle for describing the truth].
I think Miguel may have underestimated Microsoft.
That would be MIS-underestimated.
What's the state of the art of Microsoft connectivity from behind a NAT router?
Time was, NT domain controllers couldn't talk to each other if at least one of them was behind a NAT, and I think that was true for at least the early versions of Active Directory.
Nowadays, can you get remote domain controllers [respectively - Active Directory controllers] to talk to each under something like the following?
If not OpenSSL, then insert your favorite encryption protocol.Oh, and the same question for Microsoft clients: What can you do for e.g.
so that the entire sequence is encrypted, and the client can, e.g. download and upload files?Thanks!
Do you remember what you used as a power supply?
Thanks!
If you want to go with Enermax you'd probably want something like EG651AX-VH(W)FM
Good grief, those are some expensive parts:
I guess the Antec is not quite as bad: FYI: For some reason, the new Slashdot code is inserting blank spaces in all these URLs, typically after "qc=" [making it "qc= "]. Anyway, bottom line is that none of these URLs work as is.Unfortunately, in their infinite wisdom, the powers that be at
mms://demand.stream.aol.com/wb/gl/wbonline/windows /wbmovies/batmanbegins/teaser/teaser_500.wmv
Now all you have to do is
See, easy as pie. Any monkey could do it.They do require EPS12V PSUs and are physically fairly large but nothing unusual for a dual board.
We were hoping to standardize on the Enermax 600W "Noisetaker":
It's supposed to be "Intel ATX12V Ver. 1.3", but I'll have to make sure that that's the same thing as "EPS12V".You know, in the good old days, it seemed like matching a power supply to a motherboard wasn't such a royal pain in the ass.
Sorry, forgot to ask the questions:
1) Any problems [or "issues" or "gotchas"] that you could warn me about with the Tyan dual Opteron boards?
2) If you have experience with them, same as 1), but for the dual Athlon MP/760MPX boards.
Thanks!
IMHO Don't EVER purchase hardware based on the assumption that it will be compatable with some future software. You really need to decide if you would be happy with this hardware running currently available software and purchase or wait based on that. FWIW I've got a few light servers based on this series of motherboard and running 32bit Linux (Debian) and I'm perfectly happy with the performance and reliability.
Yeah, I think we're in agreement there: I'll assume that there will be problems in upgrading to Win64, and, when they day comes, if there aren't any problems, so much the better.
The other option is to go with something older, like the Athlon MP/760MPX series of boards (such as the Tiger MPX S2466N-4M, http://www.tyan.com/products/html/tigermpx.html).
But AMD seems to have utterly abandoned the 32-bit Athlon MP line, so those platforms are pretty much a dead end, in that they offer no hope whatsoever in terms of future upgradeability. Plus, they're stuck at a 266 MHz FSB.
I suppose there's Intel, but, quite frankly, I'm not in much of a mood to give them any of our money.
Thanks. The grandparent had me scared there for a second.
I write for the Inq, and I talk to people, this is more than idle speculation
Here's our big dilemma: We're looking at making a big investment in new AMD x86-64 hardware, especially the new line of 940-socket motherboards from Tyan.
Compare e.g. the S2880-S2885 line (http://www.tyan.com/products/html/matrix.html) - I don't think we'll be able to afford the S4880 range.
So here's my question: If we invest in this hardware, what do you think the chances will be that, when Win64 finally starts to appear next year, it will be able to run on this platform?
I've got this foreboding sense of dread that we'll spend thousands upon thousands of dollars on hardware, and thousands of man hours getting everything up and running, only to discover, a year from now, that Win64 won't be stable on that platform.
Any thoughts on this, or any gossip? At this point, I'd take any information I can get my hands on.
Thanks!
PS: This WOW [Windows on Windows] software emulation crap may be the kiss of death for Win64. The whole purpose of x86-64 is to be able to run 32-bit programs at hardware speed.
Software emulation could very well be the straw that breaks the camel's back - it certainly sank the Itanic.
I know outsourcing is supossed to bring everyone up to the same level, but what happens if a cycle emerges, whereby companies just pick a region on a decade by decade basis, keeping wages down permenatntly! They'd like too you know. But that's worst case senario.
Or - the people could start their own companies, and stick it to the man.
What is it with this defeatist attitude around here? If you hate your job, then quit, and start your own company! BE YOUR OWN BOSS!!! Reap your own dividends!
Liberty. What an antiquated, 18th century absurdity...
I actually design printer firmware for a living... internal memory has limited write cycles.
Care to expound?
It shaved an hour of time right out of my day, but that hour would have been spent explaining why I didn't do things that I wasn't asked to do.
Let me guess: You worked for the goverment?
MOD THIS UP INSIGHTFUL!!!!
Seriously, though: The only reason any job exists is to maximize shareholder value.
If the business structure is other than "C-Corporation" or "S-Corporation," then you can make a suitable substitution for the word "shareholder," but it's the same idea.
PS [for the grandparent] - You said: [I]t's YOUR job to do what they say.
I say: What are you, somebody's slave? If Massuh says "Jump," do you say "How high?"
So was IBM at fault?
Or were you wrong to blame them in the first place?
The point is not that the "integers" are a different size on a 64-bit machine.
The point is that the counters that you use to index Java arrays are limited to 32-bits worth of [albeit relative] addresses, rather than the full 64-bit addresses of the underlying hardware and its operating system.
And yes, there are plenty of things that need to cross the 2 ^ 32 = 4 "Giga" barrier. Such as, for instance, high quality MPEGs of Gone With the Wind or Titanic.
do you really have 32GB of RAM in your machine for this task or are you just complaining for the fun of it??
I mean, really - 640K should be all that anyone could ever want, right?
Back to my original question, though: What is the point of a 64-BIT OPERATING SYSTEM if its FLAGSHIP INTERFACE is only 32-BITS? And will remain 32-bits into the foreseeable future?
How can a salesman in the Solaris division try to sell his clients a 64-bit operating system on exhorbitantly expensive 64-bit hardware, when, just last week, a salesman from the Java division dropped by and told the very same client that 32-bits was all they'd ever need?
Seems like the client might as well stick with a 32-bit Win32 platform running on 32-bit hardware.
Or, better yet, upgrade to a 64-bit platform [Win64] running on 64-bit hardware [AMD x86-64] with a true 64-bit interface [C# & the CLI].
All at a tiny fraction of the cost...
Or maybe I should say: What's the purpose of purchasing a 64-bit operating system like Solaris if its flagship interface is 32-bits?
Don't believe me? Try javac-ing the following under Java 1.5.x:
Lotsa luck.Many characters had huge breasts that must have contained helium bladders to keep them upright, plus a titanium support structure built into their costume. They reminded me of Frank Frazetta's cover illustrations for Conan the Barbarian.
Uhh, remind me again why this is supposed to be A Bad Thing(TM)?
I ain't seen a mod point in a good couple of weeks, but if I had any...
Anyone with mod points: Please mod this guy up.
This is far, far and away the most important reply on this entire thread.
Of course, I'm not exactly sure what it means, and I'm still sitting here contemplating what it might have to say about salesmen and the pointy-headed bosses who purchase from them, but it's a must read for anyone who's curious about why things are the way that they are, and not the way that we think they should be.
PS: You can never overestimate the business in end of things, even in the tech world. For instance, I once read an interview with Thomas Watson Jr, in the WSJ, in the late eighties-early nineties timeframe, when it looked like IBM was about to go bankrupt, and he made the point that he thought it was a huge mistake when IBM moved away from leasing mainframes [which had been his great insight] and into selling mainframes. Oddly enough, with their massive push into "services" and "service contracts" over the last ten years, they've come almost full circle, back to the leasing model.
I patently reject your characterization of me as an "ambulance chaser."
Then vote for Senator Edwards - He's your guy!!!
As for your bit of code, I'm pretty certain that would seg fault on any operating system, regardless of bitness.
Seg fault?
I was hoping for something more like a BSOD.
Darn.