the remote desktop stuff tht comes with 2k/messenger is NOT the same as that built into xp. the xp stuff uses domain authentication and doesn't require someone sitting at the server to allow you to connect - you can use a regular terminal services client to connect.
some more key features (for me):
TAPI 3.1
wireless networking support
as for cleartype, for me the difference between it and regular antialiasing is night and day, and since my C drive is 210Gb, I'm not concerned with the space...
i think what he's saying is that if I buy your book then I should have the right to rip a page out. And I believe that under current copyright law I am alowed to do that. Further, I should be able to pay someone to do that for me: perhaps I'm disabled, or as is the case here, I'm not an expert in ripping pages out of books.
If the director's case is uphelpd, then wouldn't it also be a breach of copyright to sell any book that didn't contain each and every letter it originally contained?
I'm not surprised that the/. crowd likes it. More significantly is the fact that the mainstream press are all over it:
Rotten Tomatoes shows not a single bad review, that's pretty impressive.
Most programs that use the Win32, Win-16 or DOS APIs will run fine on XP/2K. The apps that have problems are those that step outside the bounds of those APIs: writing directly to hardware on DOS/Win16, using undocumented/kernel APIs, drivers, VxDs, etc...
He makes some valid points, but I find it rather funny that in the same breath he berates Microsoft for poor standards support and then bitches about how pooly the 'standard' software packages run on Linux.
Maybe Microsoft doesn't support all the open standards (w3c, rfc, et al) 100%, but one thing it does do well is support its developers (developers, developers...) Most windows applications I have (including some 16-bit and DOS apps) still run on XP. Obvisouly there are exceptions: apps that make use of OS-specific features (either by necessity, or accident). But on the whole they just work. I remember one of the win95 developers telling me that in one particular win3.1 app that was using a very unorthodox method for finding the address of some system data-structure (instead of just calling the approved API), they had to add code to the kernel to patch the app to 'do the right thing' when it loaded.
On the other hand, binary compatiblity on Linux just sucks ass. Library interfaces are constantly changing without recourse to backwards compatibility (libc is a prime example, as is the gcc3 debacle). This doesn't matter if all you have to do is './configure && make install', but for software vendors shipping binary-only installs it's a nightmare, and you end up having to support different versions for all the different, incompatible configurations that people have on their machines. It doesn't help that many distros have different ideas about where things should go and how to put them there.
(not trying to be palm advocte here, but...) that's technically true. most displays today (including regular CRTs) can only display 768 colors (256 red, 256 green and 256 blue), it's the 'merging' of those colors that gives the 2^24 combinations. it all comes down to what constitues 'pixel'.
I guess the real problem is that it can't display 50K+ colors at the advertised resolution, since it needs to use several real pixels to make a high-color pixel.
A pathalogical example: a 1024x768x24-bit display can display 1024x768x24 or 1x1x(the total number of different permutations of 24-bit pixels on a 1024x768 display). of course, you'd have to look at the 1x1 display from a long way off for the dithering take effect.
thanks, that's a much better article;-) so i guessed right, the 'common' pin is connected to the ground. so that begs the question: why the need for the 'ground' pin on a 3-pin plug at all? why not just attach the common pin to the case inside the device?
so, apart from the bullshit about "electricity comes into the appliance, goes through all the appliance, comes up to the switch and can't get out" what's he saying, that the 'common' pin is connected to ground? As far as I can tell, that's the only way current wouldn't flow through you if there was a short.
yeah, no fucking shit. why is it that developers always release RPMs for fuck-knows whatever RPM-based distros out there but never bother to include us debian-types? Debian my not be the #1 linux desktop, but it is definitely the #1 linux developer OS. if you want devs to support your shit, get it in debain, quick!
some more key features (for me):
TAPI 3.1
wireless networking support
as for cleartype, for me the difference between it and regular antialiasing is night and day, and since my C drive is 210Gb, I'm not concerned with the space...
Remote Desktop.
use the keypad enter key - you should be able to hit it with your right thumb without taking your hand off the mouse...
since the end result is the same, does the process actually matter?
If the director's case is uphelpd, then wouldn't it also be a breach of copyright to sell any book that didn't contain each and every letter it originally contained?
I'm not surprised that the /. crowd likes it. More significantly is the fact that the mainstream press are all over it:
Rotten Tomatoes shows not a single bad review, that's pretty impressive.
c ~ 1802617528320.3 furlongs/fortnight
what is the world coming to?
that my not be such good advice. usually when apple release a new range of machines they drop the MSRP on the older machines at the same time.
Most programs that use the Win32, Win-16 or DOS APIs will run fine on XP/2K. The apps that have problems are those that step outside the bounds of those APIs: writing directly to hardware on DOS/Win16, using undocumented/kernel APIs, drivers, VxDs, etc...
Maybe Microsoft doesn't support all the open standards (w3c, rfc, et al) 100%, but one thing it does do well is support its developers (developers, developers...) Most windows applications I have (including some 16-bit and DOS apps) still run on XP. Obvisouly there are exceptions: apps that make use of OS-specific features (either by necessity, or accident). But on the whole they just work. I remember one of the win95 developers telling me that in one particular win3.1 app that was using a very unorthodox method for finding the address of some system data-structure (instead of just calling the approved API), they had to add code to the kernel to patch the app to 'do the right thing' when it loaded.
On the other hand, binary compatiblity on Linux just sucks ass. Library interfaces are constantly changing without recourse to backwards compatibility (libc is a prime example, as is the gcc3 debacle). This doesn't matter if all you have to do is './configure && make install', but for software vendors shipping binary-only installs it's a nightmare, and you end up having to support different versions for all the different, incompatible configurations that people have on their machines. It doesn't help that many distros have different ideas about where things should go and how to put them there.
EETimes has a much better article with actual measurements and more technical info.
They should have used the new system they're testing for the 2004 presidential elections in Florida.
I guess the real problem is that it can't display 50K+ colors at the advertised resolution, since it needs to use several real pixels to make a high-color pixel.
A pathalogical example: a 1024x768x24-bit display can display 1024x768x24 or 1x1x(the total number of different permutations of 24-bit pixels on a 1024x768 display). of course, you'd have to look at the 1x1 display from a long way off for the dithering take effect.
thanks, that's a much better article ;-) so i guessed right, the 'common' pin is connected to the ground. so that begs the question: why the need for the 'ground' pin on a 3-pin plug at all? why not just attach the common pin to the case inside the device?
yup, and pretty much anything by J.Richter.
so, apart from the bullshit about "electricity comes into the appliance, goes through all the appliance, comes up to the switch and can't get out" what's he saying, that the 'common' pin is connected to ground? As far as I can tell, that's the only way current wouldn't flow through you if there was a short.
i gotta ask: what good is a polarized plug?
dude, not all linux distros are the same, get a clue. loctions of config files/libraries are different, all sorts of shit.
yeah, no fucking shit. why is it that developers always release RPMs for fuck-knows whatever RPM-based distros out there but never bother to include us debian-types? Debian my not be the #1 linux desktop, but it is definitely the #1 linux developer OS. if you want devs to support your shit, get it in debain, quick!
the problem is that if you're intelligent enough to set up such a tunnel, are you willing to rish being shot in the back of the head for doing so?
I would have thought that a country that has a 1-child-per-family law would want to encourage the male population to jack off as often as possible.