It's been confirmed that the difficulty settings only get applied on the initial start of the mission. The moment you transition to another zone in a multi-zoned mission or load a saved game, you get set back to normal.
It's pretty easy to test, too- On normal difficulty, you can run up behind a patrolling guard across a wood or stone floor and blackjack him before he can turn around. If the game's actually operating at expert difficulty, you won't reach him in time.
That wouldn't fix the problem. The game ignores the.ini setting as well. It always resets the difficulty to normal on any zone transition or savegame load.
It's probably a hard-coded default on load, and they simply neglected to apply the user-selected (or even.ini-specified) difficulty setting.
There's no Miranda warning or 5th amendment in Germany. Besides, he confessed and the evidence found would have brought a conviction even had he plead not guilty.
The P4 may be rated as higher wattage but it certainly doesn't run "hotter".
Higher operational wattage will equate to more heat. It's an inevitable application of thermodynamics. If your P4 is cooler than a lower-rated Athlon, then it would have to be because it wasn't operating at its rated power for some time before you took the temperature.
I'd expect this, though, because of the P4's proper power management when idle. It'll only ever be operating at peak wattage if it's actually being pegged at 100%, and even compiles and games don't really peg the CPU at 100% every microsecond.
You see similar thermal performance on the Athlon when running "cooling" software to disconnect the CPU bus when idle. It's mindbogglingly stupid that the design requires using ACPI (if you want STPGNT issued automatically), and going out of your way to flip a bit in the northbridge... but if you're actually using that facility, then AMD's chips don't run very hot either. The machine I'm typing this on right now has a Barton 3000+, and is idling at 32C with the AMD stock heat sink. I'm using VCool. It can also throttle down the CPU rather than just shut it down as heat mounts, which is another hardware feature present in the Athlon that AMD sadly doesn't just have the processor handle on its own.
My Athlon 3000+ with an 80$ radiator Zen cooler idled at 23C over ambient. Certainly I was cooling it correctly, heck I had the sides off my case and a 12" desk fan blowing on the thing...
The Zen is horribly overrated. It does piss-poor job at cooling, but it certainly is well-hyped. The turbine cooling design is only effective at very high airflow; something which a pair of 60mm fans will not supply (in fact, having a second fan makes things worse because of turbulence between the two fans). Instead, the air spends too much time trapped in the radiator and is actually less efficient than an open heat sink. It's far beyond a safe weight, sounds like the jet engine it's modeled after, and is a terrible waste of resources using pulsating heatpipe construction without the airflow neccessary to make it worthwhile. Not to sound insulting, but it's typical of aftermarket component manufacturers whenever they try something new. It's a design that sounds great on its face, but practical physics dictate otherwise. They either don't do the math, or they do and decide that it's "good enough" to sell and recoup the research costs.
It should also be noted that the Zen is now sold caveat emptor, and for good reason. Here's a review/product warning concerning the Zen; one of many.
Okay, having the sides off the case and a desk fan blowing in it is NOT proper cooling. You will trap a lot of dust in and on all cooling components, which will reduce their effectiveness. This stuff will clog the fan and really cake on to everything, requiring scraping/solvent to remove if you let it build up long enough.
You're also creating an area of warm air over the motherboard as the incoming air from the fan mixes with the hot air and pushes against the board itself to escape sideways. The resulting billowing effect means that the hot air lingers around the processor long enough to ensure it's always shrouded in air that's a bit above ambient. This is in addition to hampering cooling fans by creating turbulence.
Proper cooling of your system involves straight paths through for the air. Ideally you should have air intakes on the bottom front or sides of your case, and exhaust out the power supply (proper power supplies are designed for this, so there's no need to be shy about passing the CPU's waste heat through it) or optionally a "blowhole" at the top. This ensures a constant supply of cool (and calm) air for all components.
The P4 is definitely the better choice for you heat-wise and it's great that you're happy with it, because quite frankly, you seem to be an idiot when it comes to thermal management. You'd probably damn well kill your processor if it didn't have management built-in.
The civvies were still around during the invasion, and so were the random muggers and car-jackers, for that matter.
It was actually funny to witness them milling about normally amidst a raging battle between aliens and superheroes. So long as they didn't actually come within about three feet of an alien, they completely did not notice them, and thus didn't flee in panic.
There were more than enough aliens at a few points, though, to ensure that the "run like a little girl" zone around the NPCs usually got breached.
What would've been really cool is if all the heroes somehow beat all the aliens
On some servers and areas, we did just that. Others were neglected by the heroes and fell, while a few more were neglected by the developers and didn't get invaded at all. The alien ships eventually just vanished. No special effects, just deleted. It was a little anti-climactic.
Even when getting some severe 2-second latency, I was seeing them make with their full run and shoot animations uninterrupted. The exception being when I was very far away- In which case, they did seem to hop from place to place but while still performing their animations.
I was playing a Tanker in GC1 on Pinnacle. There were about a hundred heroes swarming over the plaza and hospital as hundreds of Ritki poured out of 8 portals in the pools down the steps. Things occasionally got a little choppy (eg: area heal on 50+ people who are simultaneously under various effects and flinging powers every which way), but never so bad that I couldn't run up and mash mentalists or provoke commanders off lower level players.
This is with 768MB ram, Radeon 9800 Pro and Barton 2600.
The only lag issue I experienced was some kind of disconnect from the map server (or so said the error message displayed in my client), and for a while afterward everything from command execution to damage display was delayed a couple seconds.
This is a relatively closed system monitored by an administrator and most likely governed by a usage policy. Perform the same study on machines found in copy shops or in homes and I'm sure the results would be quite different. (http://slashdot.org/comments.pl?sid=99442&cid=8 48 0053)
Most browsers that ship with various Linux distros are more careful about cookies by default, which is a plus.
Nothing would prevent alteration of login scripts, but it's also much harder to hide spyware in a Linux box if the user knows where their login scripts are.
If we're talking about Joe Average, however, you can't expect Joe to know anything about login scripts.
The general design of startup and login scripts under most unices does make anti-spyware less of a losing battle, though. For instance, since conf files are separate from login scripts, you could provide blanket protection for your scripts with a very simple service hooked into a file monitoring daemon. Alert the user to a potentially hazardous change and allow a rollback. If the service is run by root, then malware run as a user can't circumvent the protection.
There are a lot of options, and I'm sure we'll see them soon enough if Linux's user base continues to grow as it has.
Back in the day you talk about (386/486) you could put CPUs in *WRONG* without much trouble.
Even better, plug the AT power connectors in the wrong way.
You had to manage IRQs/Memory addresses yourself, by jumper.
I actually much preferred this to wrestling with PnP cards that don't play nice with each other and boards that set the IRQ soley by slot number.
Now, this is probably the fault of the card manufacturers for failing in building their hardware to share IRQs properly, but it's irritating to deal with nonetheless.
You get what you pay for.
This is only true to a point. Taken to an extreme (and people often do), it's called a rip-off.
I've seen the format. I've seen worse, and bmp is hardly bad enough to mess up an implimentation for.
I don't feel it's harsh at all to criticise over this. The Apache Group should also be embarassed for the same. (what, you assumed I'm yet another anti-MS/pro-OSS zealot?)
Integer overflows are easily avoided, and the very fact that they crop up so often is the reason programmers keep such a sharp eye out for them (at least where I work, anyway).
You don't realize how true this is after the W2K source leak. Microsoft has to take drastic measures if they are to stem the flood of exploits.
Making sure nothing can buffer overrun to execute with even user privileges is a neccessity now that countless local holes are known (Overflow on loading a bitmap? How in the hell did they manage to screw that up?).
"Train on every track" is less complex. The moment you add more complexity, you invite disaster.
How many bits are you going to add for every conceivable problem? Losing comms is only one possibility. Stale data, corrupted data, or malignant data are all dangerous conditions that can be detected by sanity checks, but are not "comms down" conditions. What happens when something unforseen happens and your "train on track" bits stay as they are, indicating nothing wrong?
Data in a ridiculous (yet safe) state is a clear indication that a failsafe situation has occured. The actual problem can and should be determined out-of-band.
In that case, yes, they won't like you much if you have newsbin going 24/7. Anything high-volume going over their upstream providers' links is what they take issue with.
I haven't received a letter yet but I have friends who did... people might want to start thinking about limiting their download, especially with the very popular dvdr newsgroups. It does take 5 GIGs of download per movie. You can easily let newsbin download at 300k/s 24/7.
Most providers are ecstatic to have you downloading from their local servers (news, proxy), as it costs them next to nothing. The traffic doesn't cross their expensive uplinks.
Provided they aren't doing something silly like hosting their newsgroups outside their local network, they're a lot less likely to come down on you for newsbin than they are for, say, BitTorrent.
I'm also Canadian and have never had to wait exorbitant lengths of time in the health care system, and neither has anyone I know. You are wrong.
You're either bullshitting, or this woman took too many detrimental actions (ie: not show up for appointments, refuse to stay in hospital under care when told to, etc).
Slashdot Mirror
It's been confirmed that the difficulty settings only get applied on the initial start of the mission. The moment you transition to another zone in a multi-zoned mission or load a saved game, you get set back to normal.
It's pretty easy to test, too- On normal difficulty, you can run up behind a patrolling guard across a wood or stone floor and blackjack him before he can turn around. If the game's actually operating at expert difficulty, you won't reach him in time.
That wouldn't fix the problem. The game ignores the .ini setting as well. It always resets the difficulty to normal on any zone transition or savegame load.
.ini-specified) difficulty setting.
It's probably a hard-coded default on load, and they simply neglected to apply the user-selected (or even
Tables are of course a big requirement for representing tabular data, even though a whole bunch of idiots use them for page layout.
You mean like slashcode?
There's no Miranda warning or 5th amendment in Germany. Besides, he confessed and the evidence found would have brought a conviction even had he plead not guilty.
The P4 may be rated as higher wattage but it certainly doesn't run "hotter".
Higher operational wattage will equate to more heat. It's an inevitable application of thermodynamics. If your P4 is cooler than a lower-rated Athlon, then it would have to be because it wasn't operating at its rated power for some time before you took the temperature.
I'd expect this, though, because of the P4's proper power management when idle. It'll only ever be operating at peak wattage if it's actually being pegged at 100%, and even compiles and games don't really peg the CPU at 100% every microsecond.
You see similar thermal performance on the Athlon when running "cooling" software to disconnect the CPU bus when idle. It's mindbogglingly stupid that the design requires using ACPI (if you want STPGNT issued automatically), and going out of your way to flip a bit in the northbridge... but if you're actually using that facility, then AMD's chips don't run very hot either. The machine I'm typing this on right now has a Barton 3000+, and is idling at 32C with the AMD stock heat sink. I'm using VCool. It can also throttle down the CPU rather than just shut it down as heat mounts, which is another hardware feature present in the Athlon that AMD sadly doesn't just have the processor handle on its own.
My Athlon 3000+ with an 80$ radiator Zen cooler idled at 23C over ambient. Certainly I was cooling it correctly, heck I had the sides off my case and a 12" desk fan blowing on the thing...
The Zen is horribly overrated. It does piss-poor job at cooling, but it certainly is well-hyped. The turbine cooling design is only effective at very high airflow; something which a pair of 60mm fans will not supply (in fact, having a second fan makes things worse because of turbulence between the two fans). Instead, the air spends too much time trapped in the radiator and is actually less efficient than an open heat sink. It's far beyond a safe weight, sounds like the jet engine it's modeled after, and is a terrible waste of resources using pulsating heatpipe construction without the airflow neccessary to make it worthwhile. Not to sound insulting, but it's typical of aftermarket component manufacturers whenever they try something new. It's a design that sounds great on its face, but practical physics dictate otherwise. They either don't do the math, or they do and decide that it's "good enough" to sell and recoup the research costs.
It should also be noted that the Zen is now sold caveat emptor, and for good reason. Here's a review/product warning concerning the Zen; one of many.
Okay, having the sides off the case and a desk fan blowing in it is NOT proper cooling. You will trap a lot of dust in and on all cooling components, which will reduce their effectiveness. This stuff will clog the fan and really cake on to everything, requiring scraping/solvent to remove if you let it build up long enough.
You're also creating an area of warm air over the motherboard as the incoming air from the fan mixes with the hot air and pushes against the board itself to escape sideways. The resulting billowing effect means that the hot air lingers around the processor long enough to ensure it's always shrouded in air that's a bit above ambient. This is in addition to hampering cooling fans by creating turbulence.
Proper cooling of your system involves straight paths through for the air. Ideally you should have air intakes on the bottom front or sides of your case, and exhaust out the power supply (proper power supplies are designed for this, so there's no need to be shy about passing the CPU's waste heat through it) or optionally a "blowhole" at the top. This ensures a constant supply of cool (and calm) air for all components.
The P4 is definitely the better choice for you heat-wise and it's great that you're happy with it, because quite frankly, you seem to be an idiot when it comes to thermal management. You'd probably damn well kill your processor if it didn't have management built-in.
Though once you've learned LaTeX, well, you've learned LaTeX.
Next time you've got to use it, you'll get things done correctly and quickly.
The trick is volountarily learning useful things before applying them under the clock.
The civvies were still around during the invasion, and so were the random muggers and car-jackers, for that matter.
It was actually funny to witness them milling about normally amidst a raging battle between aliens and superheroes. So long as they didn't actually come within about three feet of an alien, they completely did not notice them, and thus didn't flee in panic.
There were more than enough aliens at a few points, though, to ensure that the "run like a little girl" zone around the NPCs usually got breached.
What would've been really cool is if all the heroes somehow beat all the aliens
On some servers and areas, we did just that. Others were neglected by the heroes and fell, while a few more were neglected by the developers and didn't get invaded at all. The alien ships eventually just vanished. No special effects, just deleted. It was a little anti-climactic.
Pinnacle, GC1 here.
Even when getting some severe 2-second latency, I was seeing them make with their full run and shoot animations uninterrupted. The exception being when I was very far away- In which case, they did seem to hop from place to place but while still performing their animations.
I was playing a Tanker in GC1 on Pinnacle. There were about a hundred heroes swarming over the plaza and hospital as hundreds of Ritki poured out of 8 portals in the pools down the steps. Things occasionally got a little choppy (eg: area heal on 50+ people who are simultaneously under various effects and flinging powers every which way), but never so bad that I couldn't run up and mash mentalists or provoke commanders off lower level players.
This is with 768MB ram, Radeon 9800 Pro and Barton 2600.
The only lag issue I experienced was some kind of disconnect from the map server (or so said the error message displayed in my client), and for a while afterward everything from command execution to damage display was delayed a couple seconds.
NDIS Wrapper, though it only applies to network drivers.
This is a relatively closed system monitored by an administrator and most likely governed by a usage policy. Perform the same study on machines found in copy shops or in homes and I'm sure the results would be quite different.8 48 0053)
(http://slashdot.org/comments.pl?sid=99442&cid=
And indeed they were quite different.
Most browsers that ship with various Linux distros are more careful about cookies by default, which is a plus.
Nothing would prevent alteration of login scripts, but it's also much harder to hide spyware in a Linux box if the user knows where their login scripts are.
If we're talking about Joe Average, however, you can't expect Joe to know anything about login scripts.
The general design of startup and login scripts under most unices does make anti-spyware less of a losing battle, though. For instance, since conf files are separate from login scripts, you could provide blanket protection for your scripts with a very simple service hooked into a file monitoring daemon. Alert the user to a potentially hazardous change and allow a rollback. If the service is run by root, then malware run as a user can't circumvent the protection.
There are a lot of options, and I'm sure we'll see them soon enough if Linux's user base continues to grow as it has.
Back in the day you talk about (386/486) you could put CPUs in *WRONG* without much trouble.
Even better, plug the AT power connectors in the wrong way.
You had to manage IRQs/Memory addresses yourself, by jumper.
I actually much preferred this to wrestling with PnP cards that don't play nice with each other and boards that set the IRQ soley by slot number.
Now, this is probably the fault of the card manufacturers for failing in building their hardware to share IRQs properly, but it's irritating to deal with nonetheless.
You get what you pay for.
This is only true to a point. Taken to an extreme (and people often do), it's called a rip-off.
I've seen the format. I've seen worse, and bmp is hardly bad enough to mess up an implimentation for.
I don't feel it's harsh at all to criticise over this. The Apache Group should also be embarassed for the same.
(what, you assumed I'm yet another anti-MS/pro-OSS zealot?)
Integer overflows are easily avoided, and the very fact that they crop up so often is the reason programmers keep such a sharp eye out for them (at least where I work, anyway).
You don't realize how true this is after the W2K source leak. Microsoft has to take drastic measures if they are to stem the flood of exploits.
Making sure nothing can buffer overrun to execute with even user privileges is a neccessity now that countless local holes are known (Overflow on loading a bitmap? How in the hell did they manage to screw that up?).
"Train on every track" is less complex. The moment you add more complexity, you invite disaster.
How many bits are you going to add for every conceivable problem? Losing comms is only one possibility. Stale data, corrupted data, or malignant data are all dangerous conditions that can be detected by sanity checks, but are not "comms down" conditions. What happens when something unforseen happens and your "train on track" bits stay as they are, indicating nothing wrong?
Data in a ridiculous (yet safe) state is a clear indication that a failsafe situation has occured. The actual problem can and should be determined out-of-band.
That's your DNS server, not SCO's webserver.
You've just queried sco.com with nslookup, which returns a blank entry. The address you need to query is: www.sco.com
nslookup will return the proper entry in the lines following your server info.
Well, looks like my ISP honors the TTLs. www.sco.com now points to 127.0.0.1
You'll just be pinging localhost.
:)
Looks like they opted for solution #5 from the netcraft article the other day: redirect www.sco.com to 127.0.0.1.
Real sporting of netcraft to provide SCO with free consulting.
Indeed.
In that case, yes, they won't like you much if you have newsbin going 24/7. Anything high-volume going over their upstream providers' links is what they take issue with.
I haven't received a letter yet but I have friends who did... people might want to start thinking about limiting their download, especially with the very popular dvdr newsgroups. It does take 5 GIGs of download per movie. You can easily let newsbin download at 300k/s 24/7.
Most providers are ecstatic to have you downloading from their local servers (news, proxy), as it costs them next to nothing. The traffic doesn't cross their expensive uplinks.
Provided they aren't doing something silly like hosting their newsgroups outside their local network, they're a lot less likely to come down on you for newsbin than they are for, say, BitTorrent.
I'm also Canadian and have never had to wait exorbitant lengths of time in the health care system, and neither has anyone I know. You are wrong.
You're either bullshitting, or this woman took too many detrimental actions (ie: not show up for appointments, refuse to stay in hospital under care when told to, etc).