It asks you to enable automatic patching on first boot, has a firewall that is on by default and blocks nearly everything. It checks if you are running a virus scanner and suggest where to get one if you arn't. It warns you before opening or downloading any kind of file that is potentially dangerous. It pops up firewall dialogs when a program tries to open a connection with a warning and where you can choose to block it or "I agree to allow this despite the risk". It allows you to block the installation of activex extensions and has a popup blocker built into IE. Outlook express does not download images or content in html email.
The whole point of the story is that what makes this special is that it doesn't use irc, it uses peer-to-peer based on nullsofts WASTE. The trojans register their location on various gnutella cacheing servers. There is a master password used to contol the trojan bots that is compared to one contained md5'ed in the trojan code. To take control of the network of trojans you need to use a WASTE client to find the nearest infected machine and enter the password to issue commands.
Why are you driving on the pavement anyway? Are you trying to run people over? You should drive on the road like everyone else and leave the pavement clear for pedestrians.
Yes a funky software layer, it emulates x86 instructions on its native VLIW processor. Efficeon has this layer as well, an newer version of the Code Morphing Software.
No, it doesn't run differnt OS's than are supported by i386. The only software layer that was ever written was for x86. The idea was to reduce the power consumption of the chip by reducing its complexity/transistor count by ofloading the x86 decode stages into software. It was never their intention to make an architecture independant processor.
Not broken promises. Just over the top/. hype when it was announced at what the potential possibilities were.
Crusoe performance was never stellar, good for signal processing work but less good for interactive desktop apps with very branching code as all the instructions have to be decoded first and there is limited cache for instructions.
WinFS will provide a relational transacted system for storing files or data objects (contacts, places, calender events, + developer defined schema) (Ok the files are still files stored in a hierachical file system, but you access them group and search through a relational or object oriented inteface and API).Net Code Access Security allows specific privelege levels to be attached to specific capabilities on an individual program level rather than user level. Eg, "this program can draw a gui, and write to a specific area of the file system but cannot read or write from the rest of the file system or open network connection" The system will have a default set of permissions that should surfice for trivial apps plus a system of trust for elevating priveleges based on digital signitures, code origin and user interaction.
I believe NT already has ACLs for each kernel level object. These provide thread level security restrictions on devices, ports, processes etc.
It amazes me when people seem to think that Unix is the pinnacle of OS Design. NT may have its issues but the idea that Linux is perfection seems a bit short sighted.
A corrupt partition tables does not equal a larger hard disc. No amount of "They DID it" will make it so. If they havn't run into problems yet its only because they haven't written data to both partitions that ended up in the same place on the disc. To the OS it might appear that there are two logical drives of a large size, but there is only the same amount of physical space. Attempting to use this technique is a recipe for data corruption.
The underlying structure of the NT microkernel and hardware abstraction layer was not changed. They just moved parts of User and GDI into kernel space. NT remains largely architecture independant.
Not a Microsoftie, buy seen enough of them mention it happening to think that at least some of it must go on. Microsoftie Blogs seem to talk about their development process quite often.
Still they may only have adopted them in the last few years.
You can develop for Symbian without paying for any tools. Its more than just the nGage. The Nokia 7650, 3650, 6600 and Siemans SX1 have all sold fairly well. Also the SonyEricsson P800 and P900 if you are prepared to work with both the Series60 and UIQ interfaces. There are many phone manufacturers supporting Symbian and I'm sure they must have already shipped loads more Symbian devices than Microsoft have shipped Smartphones.
They don't have a linker because.Net is a virtual machine Jit compiler as well as massive class library. It will just become part of the Windows platform, its already included with Tablet PC, Media Center, Server 2003, Windows Mobile 2003 and it will be a major part of Longhorn. No one asks for a linker to statically link to user32 or GDI.
By the end of the year you will be able to run.Net applications natively on IA64 and AMD64 systems. By the time Longhorn comes out most new applications will be written for.Net to take advantage of the new OS features. NT itself was originally designed to be highly portable, though that may have been corrupted somewhat in subsequent generations. The transition to a different architecture will be slow but I think it will happen over the next decade or so.
A tax rebate is when an individual decides they want to bribe the populace into voting them into office so they can redirect funds into their buddies businesses in the name of national security and leave the country facing a massive budget deficit.
Well we only keep them around for the over 60s Conservatives and the tourists. They now have to pay taxes and the civil list is being reduced.
I doubt the'll still be around by the end of the Centuary.
The "all men are created equal under god" thing doesn't seem to be working that well in the US either. Would Bush have made it to the white house if it weren't for his family connections? Would Bill Gates have been able to drop out of college to found a software company and buy up QDos if it weren't for his $1 million trust fund?
To use a bluetooth mouse you must have a bluetooth stack that supports the HID profile. Microsofts bluetooth stack was completed after Windows XP shipped, It was supposed to have been included in XP SP1 but was delayed due to a lack of hardware support. It will probably be included in XP SP2.
The only way to get hold of the stack at the moment is with a MS Bluetooth keyboard/mouse or direct from MS if you are a Bluetooth hardware device manufacturer.
Mac OSX 10.2 includes support for HID devices but it was shipped after Windows XP so they had time to let the standards finalise.
I don't think you can complain about needing a driver disc for a major new Wireless subsystem.
XP has protected memory and kernel space. You don't HAVE to run as admin, teach her to use a limited user for log on and use RunAs for any troublesome apps.
Its more like the other way around. They took the multiuser kernel NT and bolted on the single user designed API Win32. The security model is built in from the ground up, not a bolted on addition. The problem is that much of the higher level and legacy stuff was designed to run on a system without such a security model in place.
People would rather have all their old applications work right out of the box than have to rework them to fit around the new system. So they put a priority on backwards compatibility, and set things up so that Home users did not need a password to get onto their own computers or change any settings.
Recently they seem to have learned the error of their ways. Shipping systems in a locked down and more secure state. So far it's only covered Server2003 and possible Office2003 but as each new generation of product arrives its going to be tougher to criticise based on security issues alone. They are already introducing their next generation API and the.Net security model will allow for even finer grained security permissions on a per-app rather than per-user basis.
If Linux hasn't already gained a significant share before Longhorn arrives, its going to find it has a much stronger competitor.
Mariah Carey - Always Be My Baby Played with YAMP on a P200 MMX Win95 in December 1998. Up till then I only had Midis and Mods and a few Wavs recorded off the radio at 8bit 22khz.
The SFU subsystem isn't any more ofan emulation layer than Win32. They both talk directly to the NT kernel native API wheras Cygwin works via Win32. It will be interesting to see if any programs run faster under SFU than they would if compiled for Win32.
Wow, great ideas. I've often thought that you should be able to make a robot with sensors, actuators and simple logic built into the eactual bricks themselves, rather than just one massive central computer. Imagine if the bricks themselves contained NAND gates and so forth, you could learn about logic circuits at the same time as building a robot, but without all the messy soldering.
You do know that isn't try don't you? NT boots into protected mode from NTLDR. Dos apps run in NTVDM a virtual machine that simulates the dos environment. NT is a pure 32bit protected memory multi tasking OS. It was written from scratch from 1988 onwards. They made it compatible with the existing APIs for the DOS based systems but it is fundamentally different underneath. They are so different that it took another decade till Windows XP to unite the two product lines and provide enough compatibility options for everything from dos, win16, win32 and directx games to get everyone to migrate with minimal difficulty. At the same time they had to compromise on some of the benifits of the new kernal, such as securiy, in order to ensure compatibility. Sure theres still a recovery console option you can boot into, but it isn't based on dos, the command syntax just looks the same.
Longhorn is where the migration away from the decade old Win32 programming model begins, but backwards compatibility has always been one of Microsofts selling points, so support for it is likely to remain for at least another decade.
You might want to think how the humidity of the dryer will effect the printer. It may not be too bad, but I wouldn't like to think of all the paper getting stuck together because it got damp.
Slashdot Mirror
Most of this stuff is coming in xp sp2.
It asks you to enable automatic patching on first boot, has a firewall that is on by default and blocks nearly everything.
It checks if you are running a virus scanner and suggest where to get one if you arn't.
It warns you before opening or downloading any kind of file that is potentially dangerous.
It pops up firewall dialogs when a program tries to open a connection with a warning and where you can choose to block it or "I agree to allow this despite the risk".
It allows you to block the installation of activex extensions and has a popup blocker built into IE.
Outlook express does not download images or content in html email.
Shame so many people are still using Windows 98.
The whole point of the story is that what makes this special is that it doesn't use irc, it uses peer-to-peer based on nullsofts WASTE. The trojans register their location on various gnutella cacheing servers. There is a master password used to contol the trojan bots that is compared to one contained md5'ed in the trojan code. To take control of the network of trojans you need to use a WASTE client to find the nearest infected machine and enter the password to issue commands.
Why are you driving on the pavement anyway? Are you trying to run people over? You should drive on the road like everyone else and leave the pavement clear for pedestrians.
Yes a funky software layer, it emulates x86 instructions on its native VLIW processor.
/. hype when it was announced at what the potential possibilities were.
Efficeon has this layer as well, an newer version of the Code Morphing Software.
No, it doesn't run differnt OS's than are supported by i386. The only software layer that was ever written was for x86. The idea was to reduce the power consumption of the chip by reducing its complexity/transistor count by ofloading the x86 decode stages into software. It was never their intention to make an architecture independant processor.
Not broken promises. Just over the top
Crusoe performance was never stellar, good for signal processing work but less good for interactive desktop apps with very branching code as all the instructions have to be decoded first and there is limited cache for instructions.
What are you talking about?
Windows has used protected mode for a decade.
Sounds like you're waiting for Longhorn.
.Net Code Access Security allows specific privelege levels to be attached to specific capabilities on an individual program level rather than user level. Eg, "this program can draw a gui, and write to a specific area of the file system but cannot read or write from the rest of the file system or open network connection"
WinFS will provide a relational transacted system for storing files or data objects (contacts, places, calender events, + developer defined schema)
(Ok the files are still files stored in a hierachical file system, but you access them group and search through a relational or object oriented inteface and API)
The system will have a default set of permissions that should surfice for trivial apps plus a system of trust for elevating priveleges based on digital signitures, code origin and user interaction.
I believe NT already has ACLs for each kernel level object. These provide thread level security restrictions on devices, ports, processes etc.
It amazes me when people seem to think that Unix is the pinnacle of OS Design. NT may have its issues but the idea that Linux is perfection seems a bit short sighted.
So download SFUand SFU.
A corrupt partition tables does not equal a larger hard disc. No amount of "They DID it" will make it so.
If they havn't run into problems yet its only because they haven't written data to both partitions that ended up in the same place on the disc.
To the OS it might appear that there are two logical drives of a large size, but there is only the same amount of physical space.
Attempting to use this technique is a recipe for data corruption.
The underlying structure of the NT microkernel and hardware abstraction layer was not changed. They just moved parts of User and GDI into kernel space.
NT remains largely architecture independant.
Not a Microsoftie, buy seen enough of them mention it happening to think that at least some of it must go on. Microsoftie Blogs seem to talk about their development process quite often. Still they may only have adopted them in the last few years.
Thats why you should never respond to spammers. It only encourages them to send out more mails.
You can develop for Symbian without paying for any tools. Its more than just the nGage. The Nokia 7650, 3650, 6600 and Siemans SX1 have all sold fairly well. Also the SonyEricsson P800 and P900 if you are prepared to work with both the Series60 and UIQ interfaces. There are many phone manufacturers supporting Symbian and I'm sure they must have already shipped loads more Symbian devices than Microsoft have shipped Smartphones.
They don't have a linker because .Net is a virtual machine Jit compiler as well as massive class library.
It will just become part of the Windows platform, its already included with Tablet PC, Media Center, Server 2003, Windows Mobile 2003 and it will be a major part of Longhorn.
No one asks for a linker to statically link to user32 or GDI.
By the end of the year you will be able to run .Net applications natively on IA64 and AMD64 systems. .Net to take advantage of the new OS features.
By the time Longhorn comes out most new applications will be written for
NT itself was originally designed to be highly portable, though that may have been corrupted somewhat in subsequent generations.
The transition to a different architecture will be slow but I think it will happen over the next decade or so.
A tax rebate is when an individual decides they want to bribe the populace into voting them into office so they can redirect funds into their buddies businesses in the name of national security and leave the country facing a massive budget deficit.
Well we only keep them around for the over 60s Conservatives and the tourists. They now have to pay taxes and the civil list is being reduced.
I doubt the'll still be around by the end of the Centuary.
The "all men are created equal under god" thing doesn't seem to be working that well in the US either. Would Bush have made it to the white house if it weren't for his family connections? Would Bill Gates have been able to drop out of college to found a software company and buy up QDos if it weren't for his $1 million trust fund?
http://philip.greenspun.com/bg/
To use a bluetooth mouse you must have a bluetooth stack that supports the HID profile.
Microsofts bluetooth stack was completed after Windows XP shipped, It was supposed to have been included in XP SP1 but was delayed due to a lack of hardware support. It will probably be included in XP SP2.
The only way to get hold of the stack at the moment is with a MS Bluetooth keyboard/mouse or direct from MS if you are a Bluetooth hardware device manufacturer.
Mac OSX 10.2 includes support for HID devices but it was shipped after Windows XP so they had time to let the standards finalise.
I don't think you can complain about needing a driver disc for a major new Wireless subsystem.
XP has protected memory and kernel space.
You don't HAVE to run as admin, teach her to use a limited user for log on and use RunAs for any troublesome apps.
Its more like the other way around. They took the multiuser kernel NT and bolted on the single user designed API Win32.
.Net security model will allow for even finer grained security permissions on a per-app rather than per-user basis.
The security model is built in from the ground up, not a bolted on addition. The problem is that much of the higher level and legacy stuff was designed to run on a system without such a security model in place.
People would rather have all their old applications work right out of the box than have to rework them to fit around the new system. So they put a priority on backwards compatibility, and set things up so that Home users did not need a password to get onto their own computers or change any settings.
Recently they seem to have learned the error of their ways. Shipping systems in a locked down and more secure state. So far it's only covered Server2003 and possible Office2003 but as each new generation of product arrives its going to be tougher to criticise based on security issues alone.
They are already introducing their next generation API and the
If Linux hasn't already gained a significant share before Longhorn arrives, its going to find it has a much stronger competitor.
Mariah Carey - Always Be My Baby
Played with YAMP on a P200 MMX Win95 in December 1998.
Up till then I only had Midis and Mods and a few Wavs recorded off the radio at 8bit 22khz.
The SFU subsystem isn't any more ofan emulation layer than Win32. They both talk directly to the NT kernel native API wheras Cygwin works via Win32. It will be interesting to see if any programs run faster under SFU than they would if compiled for Win32.
Wow, great ideas.
I've often thought that you should be able to make a robot with sensors, actuators and simple logic built into the eactual bricks themselves, rather than just one massive central computer. Imagine if the bricks themselves contained NAND gates and so forth, you could learn about logic circuits at the same time as building a robot, but without all the messy soldering.
You do know that isn't try don't you?
8 /w inntfs.asp
NT boots into protected mode from NTLDR.
Dos apps run in NTVDM a virtual machine that simulates the dos environment.
NT is a pure 32bit protected memory multi tasking OS. It was written from scratch from 1988 onwards.
They made it compatible with the existing APIs for the DOS based systems but it is fundamentally different underneath.
They are so different that it took another decade till Windows XP to unite the two product lines and provide enough compatibility options for everything from dos, win16, win32 and directx games to get everyone to migrate with minimal difficulty. At the same time they had to compromise on some of the benifits of the new kernal, such as securiy, in order to ensure compatibility.
Sure theres still a recovery console option you can boot into, but it isn't based on dos, the command syntax just looks the same.
Longhorn is where the migration away from the decade old Win32 programming model begins, but backwards compatibility has always been one of Microsofts selling points, so support for it is likely to remain for at least another decade.
http://www.microsoft.com/presspass/features/199
Windows XP has an "Advanced Networking Pack" update that enables IPv6 and Toredo Tunneling. It'll probably be rolled into SP2 as well.
The application "3degrees" makes use of the peer to peer componant for people to create groups to share music, chat and animations.
MS is pushing IPv6 heavily in Longhorn both for peer to peer collaberation applications and external devices such as bluetooth headsets.
You might want to think how the humidity of the dryer will effect the printer.
It may not be too bad, but I wouldn't like to think of all the paper getting stuck together because it got damp.