PrinterShare® - How It Works – Free Software


Client Hardware , Desktops, Notebooks , Workstations , Thin client Enterprise Products – Servers , Storage , Switches , Router , VPN , VOIP , Wireless Software – Vmware , Microsoft , Symantec , IBM , Networking Components – Data / Voice , Firewall solutions , Security products Professional Services – Data center solutions, Networking solutions , Mailserver , Groupware. Managed Services – Infrastructure Management Solutions
12:13 AM
kamlesh.sitapara
10:45 AM
9:59 PM
kamlesh.sitapara
5:45 AM
kamlesh.sitapara
Antivirus for Swine flue To improve immunity to have resistance against SWINE Flue infection following remedy is suggested.
Recipe
* One cup of drinking water
* One tea spoon of GUD ( made out of sugarcane juice )
* One tea spoon of Ambla powder
* Half tea spoon of Ginger powder
* 1/3 tea spoon of turmeric powder.
* 2 to 3 leaves of tulsi if available.
The entire mixture to be boiled it should be taken in the morning just like tea.
7:26 PM
4:19 AM
4:26 AM
kamlesh.sitapara
4:23 AM
kamlesh.sitapara
10:36 PM
12:10 AM
kamlesh.sitapara
12:39 AM
kamlesh.sitapara
12:35 AM
1:12 AM
12:10 PM
kamlesh.sitapara
2:01 AM
kamlesh.sitapara
10:35 PM
The following table summarizes the information from the previous section, but it is sorted by port number rather than service name.
Port | Protocol | Application protocol | System Service Name |
n/a | GRE | GRE (IP protocol 47) | Routing and Remote Access |
n/a | ESP | IPSec ESP (IP protocol 50) | Routing and Remote Access |
n/a | AH | IPSec AH (IP protocol 51) | Routing and Remote Access |
7 | TCP | Echo | Simple TCP/IP Services |
7 | UDP | Echo | Simple TCP/IP Services |
9 | TCP | Discard | Simple TCP/IP Services |
9 | UDP | Discard | Simple TCP/IP Services |
13 | TCP | Daytime | Simple TCP/IP Services |
13 | UDP | Daytime | Simple TCP/IP Services |
17 | TCP | Quotd | Simple TCP/IP Services |
17 | UDP | Quotd | Simple TCP/IP Services |
19 | TCP | Chargen | Simple TCP/IP Services |
19 | UDP | Chargen | Simple TCP/IP Services |
20 | TCP | FTP default data | FTP Publishing Service |
21 | TCP | FTP control | FTP Publishing Service |
21 | TCP | FTP control | Application Layer Gateway Service |
23 | TCP | Telnet | Telnet |
25 | TCP | SMTP | Simple Mail Transfer Protocol |
25 | UDP | SMTP | Simple Mail Transfer Protocol |
25 | TCP | SMTP | Exchange Server |
25 | UDP | SMTP | Exchange Server |
42 | TCP | WINS Replication | Windows Internet Name Service |
42 | UDP | WINS Replication | Windows Internet Name Service |
53 | TCP | DNS | DNS Server |
53 | UDP | DNS | DNS Server |
53 | TCP | DNS | Internet Connection Firewall/Internet Connection Sharing |
67 | UDP | DHCP Server | DHCP Server |
67 | UDP | DHCP Server | Internet Connection Firewall/Internet Connection Sharing |
69 | UDP | TFTP | Trivial FTP Daemon Service |
80 | TCP | HTTP | Windows Media Services |
80 | TCP | HTTP | World Wide Web Publishing Service |
80 | TCP | HTTP | SharePoint Portal Server |
88 | TCP | Kerberos | Kerberos Key Distribution Center |
88 | UDP | Kerberos | Kerberos Key Distribution Center |
102 | TCP | X.400 | Microsoft Exchange MTA Stacks |
110 | TCP | POP3 | Microsoft POP3 Service |
110 | TCP | POP3 | Exchange Server |
119 | TCP | NNTP | Network News Transfer Protocol |
123 | UDP | NTP | Windows Time |
123 | UDP | SNTP | Windows Time |
135 | TCP | RPC | Message Queuing |
135 | TCP | RPC | Remote Procedure Call |
135 | TCP | RPC | Exchange Server |
135 | TCP | RPC | Certificate Services |
135 | TCP | RPC | Cluster Service |
135 | TCP | RPC | Distributed File System |
135 | TCP | RPC | Distributed Link Tracking |
135 | TCP | RPC | Distributed Transaction Coordinator |
135 | TCP | RPC | Event Log |
135 | TCP | RPC | Fax Service |
135 | TCP | RPC | File Replication |
135 | TCP | RPC | Local Security Authority |
135 | TCP | RPC | Remote Storage Notification |
135 | TCP | RPC | Remote Storage Server |
135 | TCP | RPC | Systems Management Server 2.0 |
135 | TCP | RPC | Terminal Services Licensing |
135 | TCP | RPC | Terminal Services Session Directory |
137 | UDP | NetBIOS Name Resolution | Computer Browser |
137 | UDP | NetBIOS Name Resolution | Server |
137 | UDP | NetBIOS Name Resolution | Windows Internet Name Service |
137 | UDP | NetBIOS Name Resolution | Net Logon |
137 | UDP | NetBIOS Name Resolution | Systems Management Server 2.0 |
138 | UDP | NetBIOS Datagram Service | Computer Browser |
138 | UDP | NetBIOS Datagram Service | Messenger |
138 | UDP | NetBIOS Datagram Service | Server |
138 | UDP | NetBIOS Datagram Service | Net Logon |
138 | UDP | NetBIOS Datagram Service | Distributed File System |
138 | UDP | NetBIOS Datagram Service | Systems Management Server 2.0 |
138 | UDP | NetBIOS Datagram Service | License Logging Service |
139 | TCP | NetBIOS Session Service | Computer Browser |
139 | TCP | NetBIOS Session Service | Fax Service |
139 | TCP | NetBIOS Session Service | Performance Logs and Alerts |
139 | TCP | NetBIOS Session Service | Print Spooler |
139 | TCP | NetBIOS Session Service | Server |
139 | TCP | NetBIOS Session Service | Net Logon |
139 | TCP | NetBIOS Session Service | Remote Procedure Call Locator |
139 | TCP | NetBIOS Session Service | Distributed File System |
139 | TCP | NetBIOS Session Service | Systems Management Server 2.0 |
139 | TCP | NetBIOS Session Service | License Logging Service |
143 | TCP | IMAP | Exchange Server |
161 | UDP | SNMP | SNMP Service |
162 | UDP | SNMP Traps Outbound | SNMP Trap Service |
389 | TCP | LDAP Server | Local Security Authority |
389 | UDP | LDAP Server | Local Security Authority |
389 | TCP | LDAP Server | Distributed File System |
389 | UDP | LDAP Server | Distributed File System |
443 | TCP | HTTPS | HTTP SSL |
443 | TCP | HTTPS | World Wide Web Publishing Service |
443 | TCP | HTTPS | SharePoint Portal Server |
445 | TCP | SMB | Fax Service |
445 | TCP | SMB | Print Spooler |
445 | TCP | SMB | Server |
445 | TCP | SMB | Remote Procedure Call Locator |
445 | TCP | SMB | Distributed File System |
445 | TCP | SMB | License Logging Service |
445 | TCP | SMB | Net Logon |
500 | UDP | IPSec ISAKMP | Local Security Authority |
515 | TCP | LPD | TCP/IP Print Server |
548 | TCP | File Server for Macintosh | File Server for Macintosh |
554 | TCP | RTSP | Windows Media Services |
563 | TCP | NNTP over SSL | Network News Transfer Protocol |
593 | TCP | RPC over HTTP | Remote Procedure Call |
593 | TCP | RPC over HTTP | Exchange Server |
636 | TCP | LDAP SSL | Local Security Authority |
636 | UDP | LDAP SSL | Local Security Authority |
993 | TCP | IMAP over SSL | Exchange Server |
995 | TCP | POP3 over SSL | Exchange Server |
1270 | TCP | MOM-Encrypted | Microsoft Operations Manager 2000 |
1433 | TCP | SQL over TCP | Microsoft SQL Server |
1433 | TCP | SQL over TCP | MSSQL$UDDI |
1434 | UDP | SQL Probe | Microsoft SQL Server |
1434 | UDP | SQL Probe | MSSQL$UDDI |
1645 | UDP | Legacy RADIUS | Internet Authentication Service |
1646 | UDP | Legacy RADIUS | Internet Authentication Service |
1701 | UDP | L2TP | Routing and Remote Access |
1723 | TCP | PPTP | Routing and Remote Access |
1755 | TCP | MMS | Windows Media Services |
1755 | UDP | MMS | Windows Media Services |
1801 | TCP | MSMQ | Message Queuing |
1801 | UDP | MSMQ | Message Queuing |
1812 | UDP | RADIUS Authentication | Internet Authentication Service |
1813 | UDP | RADIUS Accounting | Internet Authentication Service |
1900 | UDP | SSDP | SSDP Discovery Service |
2101 | TCP | MSMQ-DCs | Message Queuing |
2103 | TCP | MSMQ-RPC | Message Queuing |
2105 | TCP | MSMQ-RPC | Message Queuing |
2107 | TCP | MSMQ-Mgmt | Message Queuing |
2393 | TCP | OLAP Services 7.0 | SQL Server: Downlevel OLAP Client Support |
2394 | TCP | OLAP Services 7.0 | SQL Server: Downlevel OLAP Client Support |
2460 | UDP | MS Theater | Windows Media Services |
2535 | UDP | MADCAP | DHCP Server |
2701 | TCP | SMS Remote Control (control) | SMS Remote Control Agent |
2701 | UDP | SMS Remote Control (control) | SMS Remote Control Agent |
2702 | TCP | SMS Remote Control (data) | SMS Remote Control Agent |
2702 | UDP | SMS Remote Control (data) | SMS Remote Control Agent |
2703 | TCP | SMS Remote Chat | SMS Remote Control Agent |
2703 | UPD | SMS Remote Chat | SMS Remote Control Agent |
2704 | TCP | SMS Remote File Transfer | SMS Remote Control Agent |
2704 | UDP | SMS Remote File Transfer | SMS Remote Control Agent |
2725 | TCP | SQL Analysis Services | SQL Analysis Server |
2869 | TCP | UPNP | UPNP Device Host |
2869 | TCP | SSDP event notification | SSDP Discovery Service |
3268 | TCP | Global Catalog Server | Local Security Authority |
3269 | TCP | Global Catalog Server | Local Security Authority |
3343 | UDP | Cluster Services | Cluster Service |
3389 | TCP | Terminal Services | NetMeeting Remote Desktop Sharing |
3389 | TCP | Terminal Services | Terminal Services |
3527 | UDP | MSMQ-Ping | Message Queuing |
4011 | UDP | BINL | Remote Installation |
4500 | UDP | NAT-T | Local Security Authority |
5000 | TCP | SSDP legacy event notification | SSDP Discovery Service |
5004 | UDP | RTP | Windows Media Services |
5005 | UDP | RTCP | Windows Media Services |
42424 | TCP | ASP.Net Session State | ASP.NET State Service |
51515 | TCP | MOM-Clear | Microsoft Operations Manager 2000 |
6:27 PM
kamlesh.sitapara
10:04 AM
9:52 AM
9:48 PM
kamlesh.sitapara
Since then, what was once one of many possible ideas has built momentum toward becoming the plan dictated by conventional wisdom.
While this bandwagon may have already gained too many passengers and too much speed to stop now, one can’t help but wonder exactly what the problem is with Vista. Ask around and you will get the same answer over and over.
"People hate Vista."
As someone who continues to analyze the question of Vista in the context of the value of doing a workstation OS migration along with a server OS migration (XP to Vista and Server 03 to 08), I know that the success of any project is often determined by the reactions of users. So, what is it exactly, that people hate about Vista. Here are the Top 10 things people hate about Microsoft’s Windows Vista.
A great deal of the griping about Vista comes from the simple fact that it is different. Users complained bitterly about “losing” files which were simply placed in a different location. Let’s face it, putting anything and everything inside My Documents was starting to wear out its welcome, and while power users may have been well aware that My Documents was under the Documents and Settings folder, not everyone really ever grasped that. The new file locations make sense once you are willing to learn something new.
The biggest single problem with the image of Vista has been the User Account Control. It may also cause the greatest leap forward in computer security and software quality since the invention of the PC. The truth is that for years now, some vendors have thrown together drivers and programs without much thought to writing good software. The theory was to just get something working and then ship it out the door.
For better or worse, Microsoft had gotten Windows XP to the point where virtually worthless code could still function without adversely affecting too many users or systems. However, there were significant security issues with this model. Virtually every program or driver required Admin privileges to be installed, and with various hooks and processes reaching deep into the core of the OS, stability and security issues were constantly arising.
Unfortunately, the UAC carried the design flaw of asking “Are You Sure,” over and over to the user who eventually gave up reading any of the boxes. Even worse, the UAC grabbed full control of the computer and forced users to interact with it. Users never like to be forced to do anything, even if it is for their own good.
Chalk this one up to a corporate blunder. Microsoft was trying to be the good guy to the vendors and companies it works with. Unfortunately, this made it the bad guy to the users of the Vista OS. Systems running anything near the minimum specifications for Vista did see a pretty big performance hit. Still users with more powerful systems complain that XP is faster. Sure it is. It does less. That isn’t rocket science.
However, I think everyone agrees that it is time for Microsoft to spend a little more time optimizing its code, and a little less time “integrating” every new technology into the OS so it can’t be required to remove it.
When Vista first came out, it was common practice among IT savvy people of all levels to monitor a system’s memory usage. If memory usage spiked up with the installation of a new program, one could assume that program was not well coded and wasted system resources.
However, Vista had a new memory management paradigm. The idea was, why not use all of the memory that is there. Free memory is wasted memory — was the mantra. In fact, this is a great idea and can substantially improve performance. The problem is that people didn’t understand that there was a new memory model in effect, so it looked like Vista was “hogging” all of that memory. This plus #4 equaled more than a few people screaming about bloat and inefficiency.
Whether it’s the constantly blinking hard drive light, or actually being able to hear a high speed drive spin up, it doesn’t take long to notice that Vista is constantly accessing your hard disk. It takes even less time to jump to the conclusion that Vista is too big and inefficient to load itself and run programs without making tremendous use of the swap file and other disk based storage.
In reality, this activity is a byproduct of the new memory model which attempts to always take advantage of all available memory. In order to do this, the OS has to load something into memory to fill the space. It also has to take something out of memory and put it back on the hard drive when a new program or process starts that needs to use some of that “full” memory. If you aren’t aware of what is going on, it does seem like the hard drive is being used too often.
If anything did more damage to Vista in user’s minds than the UAC, it was the seemingly nightmarish lack of drivers for various hardware. Microsoft took the blame for this one, when in reality the hardware vendors were to blame.
Vista was never a secret, nor was its new, improved, more stable driver model. Vendors literally had years to build drivers for Vista, but drivers don’t make money, or buzz, or press, so they were ignored until it was too late. The vendors, of course, quickly took to blaming Vista for “breaking” their drivers.
There can be debate among reasonable men, the extent to which Microsoft should be held accountable for its operating system’s ability to play video games. With a half-dozen gaming consoles, including Microsoft’s own Xbox, one might consider that it isn’t Vista’s job to play high-end games. The Gamers of the world politely (and not so politely) disagree.
Any true power gamer has long since replaced several components of any computer system from the vendor, even so-called gaming systems. Spend five minutes on any gaming forum and you’ll see posts ranging from over-clocking hardware, to upgrades that require a soldering iron. Over the years, these communities have learned to stretch their gaming power to the limits without breaking XP. That experience, of course, is missing on Vista. Tricks that once produced additional power, now produce crashes.
Many of Vista’s improvements are under the hood. Better security, improved stability, tighter driver models, better memory usage, automatic hard drive defragmenting, an I/O model that allows for lower priorities for “behind the scenes” tasks — are all leaps forward in OS architecture. But, none of them are really visible to Joe User who has to wonder what they paid extra for when their PC came loaded with Vista.
No manufacturer can be expected to sell last year’s model forever, but when Microsoft announced that it would no longer allow people to purchase Windows XP, it seemed like the company was bullying users into using a product that they didn’t want. The problem was exacerbated when Microsoft let loose Service Pack 3 which solidified the idea in many user’s head that XP was still a “current” operating system and the only reason Microsoft wouldn’t let them buy it was dollars.
What many people fail to understand is just how long after a product stops selling that Microsoft must support it. The cut-off for XP was more about starting the clock ticking down on XP support, than about forcing users to buy Vista.
Much of Vista’s criticism comes in the form of “XP is better. Whether this is true or not, it shows that users have come to both understand, and respect Windows XP. Over the years, various patches, updates and three service packs have turned it into a solid workhorse that can be counted on by home users and corporations alike who with millions of installed systems, are not surprisingly reluctant to undertake the huge task of replacing that systems.
Windows XP was not universally loved when it was first released either. As a computer consultant at the time, I can remember the multitude of complaints and criticisms then as well. The difference was that Windows XP replaced Windows 95/98 which was never a very good operating system. The migration to XP came with the idea that at least it wasn’t Windows 95. This time, it’s different. People look at Windows XP and see a perfectly good if dated operating system.
Windows 7 is apparently coming as fast as Microsoft can get it here, but as early looks have shown, Windows 7 is the next version of Vista, not the next version of XP. In the end, it seems Vista will be Microsoft’s OS of the future, it just might have a new name.
9:48 PM
kamlesh.sitapara
Since then, what was once one of many possible ideas has built momentum toward becoming the plan dictated by conventional wisdom.
While this bandwagon may have already gained too many passengers and too much speed to stop now, one can’t help but wonder exactly what the problem is with Vista. Ask around and you will get the same answer over and over.
"People hate Vista."
As someone who continues to analyze the question of Vista in the context of the value of doing a workstation OS migration along with a server OS migration (XP to Vista and Server 03 to 08), I know that the success of any project is often determined by the reactions of users. So, what is it exactly, that people hate about Vista. Here are the Top 10 things people hate about Microsoft’s Windows Vista.
A great deal of the griping about Vista comes from the simple fact that it is different. Users complained bitterly about “losing” files which were simply placed in a different location. Let’s face it, putting anything and everything inside My Documents was starting to wear out its welcome, and while power users may have been well aware that My Documents was under the Documents and Settings folder, not everyone really ever grasped that. The new file locations make sense once you are willing to learn something new.
The biggest single problem with the image of Vista has been the User Account Control. It may also cause the greatest leap forward in computer security and software quality since the invention of the PC. The truth is that for years now, some vendors have thrown together drivers and programs without much thought to writing good software. The theory was to just get something working and then ship it out the door.
For better or worse, Microsoft had gotten Windows XP to the point where virtually worthless code could still function without adversely affecting too many users or systems. However, there were significant security issues with this model. Virtually every program or driver required Admin privileges to be installed, and with various hooks and processes reaching deep into the core of the OS, stability and security issues were constantly arising.
Unfortunately, the UAC carried the design flaw of asking “Are You Sure,” over and over to the user who eventually gave up reading any of the boxes. Even worse, the UAC grabbed full control of the computer and forced users to interact with it. Users never like to be forced to do anything, even if it is for their own good.
Chalk this one up to a corporate blunder. Microsoft was trying to be the good guy to the vendors and companies it works with. Unfortunately, this made it the bad guy to the users of the Vista OS. Systems running anything near the minimum specifications for Vista did see a pretty big performance hit. Still users with more powerful systems complain that XP is faster. Sure it is. It does less. That isn’t rocket science.
However, I think everyone agrees that it is time for Microsoft to spend a little more time optimizing its code, and a little less time “integrating” every new technology into the OS so it can’t be required to remove it.
When Vista first came out, it was common practice among IT savvy people of all levels to monitor a system’s memory usage. If memory usage spiked up with the installation of a new program, one could assume that program was not well coded and wasted system resources.
However, Vista had a new memory management paradigm. The idea was, why not use all of the memory that is there. Free memory is wasted memory — was the mantra. In fact, this is a great idea and can substantially improve performance. The problem is that people didn’t understand that there was a new memory model in effect, so it looked like Vista was “hogging” all of that memory. This plus #4 equaled more than a few people screaming about bloat and inefficiency.
Whether it’s the constantly blinking hard drive light, or actually being able to hear a high speed drive spin up, it doesn’t take long to notice that Vista is constantly accessing your hard disk. It takes even less time to jump to the conclusion that Vista is too big and inefficient to load itself and run programs without making tremendous use of the swap file and other disk based storage.
In reality, this activity is a byproduct of the new memory model which attempts to always take advantage of all available memory. In order to do this, the OS has to load something into memory to fill the space. It also has to take something out of memory and put it back on the hard drive when a new program or process starts that needs to use some of that “full” memory. If you aren’t aware of what is going on, it does seem like the hard drive is being used too often.
If anything did more damage to Vista in user’s minds than the UAC, it was the seemingly nightmarish lack of drivers for various hardware. Microsoft took the blame for this one, when in reality the hardware vendors were to blame.
Vista was never a secret, nor was its new, improved, more stable driver model. Vendors literally had years to build drivers for Vista, but drivers don’t make money, or buzz, or press, so they were ignored until it was too late. The vendors, of course, quickly took to blaming Vista for “breaking” their drivers.
There can be debate among reasonable men, the extent to which Microsoft should be held accountable for its operating system’s ability to play video games. With a half-dozen gaming consoles, including Microsoft’s own Xbox, one might consider that it isn’t Vista’s job to play high-end games. The Gamers of the world politely (and not so politely) disagree.
Any true power gamer has long since replaced several components of any computer system from the vendor, even so-called gaming systems. Spend five minutes on any gaming forum and you’ll see posts ranging from over-clocking hardware, to upgrades that require a soldering iron. Over the years, these communities have learned to stretch their gaming power to the limits without breaking XP. That experience, of course, is missing on Vista. Tricks that once produced additional power, now produce crashes.
Many of Vista’s improvements are under the hood. Better security, improved stability, tighter driver models, better memory usage, automatic hard drive defragmenting, an I/O model that allows for lower priorities for “behind the scenes” tasks — are all leaps forward in OS architecture. But, none of them are really visible to Joe User who has to wonder what they paid extra for when their PC came loaded with Vista.
No manufacturer can be expected to sell last year’s model forever, but when Microsoft announced that it would no longer allow people to purchase Windows XP, it seemed like the company was bullying users into using a product that they didn’t want. The problem was exacerbated when Microsoft let loose Service Pack 3 which solidified the idea in many user’s head that XP was still a “current” operating system and the only reason Microsoft wouldn’t let them buy it was dollars.
What many people fail to understand is just how long after a product stops selling that Microsoft must support it. The cut-off for XP was more about starting the clock ticking down on XP support, than about forcing users to buy Vista.
Much of Vista’s criticism comes in the form of “XP is better. Whether this is true or not, it shows that users have come to both understand, and respect Windows XP. Over the years, various patches, updates and three service packs have turned it into a solid workhorse that can be counted on by home users and corporations alike who with millions of installed systems, are not surprisingly reluctant to undertake the huge task of replacing that systems.
Windows XP was not universally loved when it was first released either. As a computer consultant at the time, I can remember the multitude of complaints and criticisms then as well. The difference was that Windows XP replaced Windows 95/98 which was never a very good operating system. The migration to XP came with the idea that at least it wasn’t Windows 95. This time, it’s different. People look at Windows XP and see a perfectly good if dated operating system.
Windows 7 is apparently coming as fast as Microsoft can get it here, but as early looks have shown, Windows 7 is the next version of Vista, not the next version of XP. In the end, it seems Vista will be Microsoft’s OS of the future, it just might have a new name.
9:43 PM
kamlesh.sitapara
Since then, what was once one of many possible ideas has built momentum toward becoming the plan dictated by conventional wisdom.
While this bandwagon may have already gained too many passengers and too much speed to stop now, one can’t help but wonder exactly what the problem is with Vista. Ask around and you will get the same answer over and over.
"People hate Vista."
As someone who continues to analyze the question of Vista in the context of the value of doing a workstation OS migration along with a server OS migration (XP to Vista and Server 03 to 08), I know that the success of any project is often determined by the reactions of users. So, what is it exactly, that people hate about Vista. Here are the Top 10 things people hate about Microsoft’s Windows Vista.
A great deal of the griping about Vista comes from the simple fact that it is different. Users complained bitterly about “losing” files which were simply placed in a different location. Let’s face it, putting anything and everything inside My Documents was starting to wear out its welcome, and while power users may have been well aware that My Documents was under the Documents and Settings folder, not everyone really ever grasped that. The new file locations make sense once you are willing to learn something new.
The biggest single problem with the image of Vista has been the User Account Control. It may also cause the greatest leap forward in computer security and software quality since the invention of the PC. The truth is that for years now, some vendors have thrown together drivers and programs without much thought to writing good software. The theory was to just get something working and then ship it out the door.
For better or worse, Microsoft had gotten Windows XP to the point where virtually worthless code could still function without adversely affecting too many users or systems. However, there were significant security issues with this model. Virtually every program or driver required Admin privileges to be installed, and with various hooks and processes reaching deep into the core of the OS, stability and security issues were constantly arising.
Unfortunately, the UAC carried the design flaw of asking “Are You Sure,” over and over to the user who eventually gave up reading any of the boxes. Even worse, the UAC grabbed full control of the computer and forced users to interact with it. Users never like to be forced to do anything, even if it is for their own good.
Chalk this one up to a corporate blunder. Microsoft was trying to be the good guy to the vendors and companies it works with. Unfortunately, this made it the bad guy to the users of the Vista OS. Systems running anything near the minimum specifications for Vista did see a pretty big performance hit. Still users with more powerful systems complain that XP is faster. Sure it is. It does less. That isn’t rocket science.
However, I think everyone agrees that it is time for Microsoft to spend a little more time optimizing its code, and a little less time “integrating” every new technology into the OS so it can’t be required to remove it.
When Vista first came out, it was common practice among IT savvy people of all levels to monitor a system’s memory usage. If memory usage spiked up with the installation of a new program, one could assume that program was not well coded and wasted system resources.
However, Vista had a new memory management paradigm. The idea was, why not use all of the memory that is there. Free memory is wasted memory — was the mantra. In fact, this is a great idea and can substantially improve performance. The problem is that people didn’t understand that there was a new memory model in effect, so it looked like Vista was “hogging” all of that memory. This plus #4 equaled more than a few people screaming about bloat and inefficiency.
Whether it’s the constantly blinking hard drive light, or actually being able to hear a high speed drive spin up, it doesn’t take long to notice that Vista is constantly accessing your hard disk. It takes even less time to jump to the conclusion that Vista is too big and inefficient to load itself and run programs without making tremendous use of the swap file and other disk based storage.
In reality, this activity is a byproduct of the new memory model which attempts to always take advantage of all available memory. In order to do this, the OS has to load something into memory to fill the space. It also has to take something out of memory and put it back on the hard drive when a new program or process starts that needs to use some of that “full” memory. If you aren’t aware of what is going on, it does seem like the hard drive is being used too often.
If anything did more damage to Vista in user’s minds than the UAC, it was the seemingly nightmarish lack of drivers for various hardware. Microsoft took the blame for this one, when in reality the hardware vendors were to blame.
Vista was never a secret, nor was its new, improved, more stable driver model. Vendors literally had years to build drivers for Vista, but drivers don’t make money, or buzz, or press, so they were ignored until it was too late. The vendors, of course, quickly took to blaming Vista for “breaking” their drivers.
There can be debate among reasonable men, the extent to which Microsoft should be held accountable for its operating system’s ability to play video games. With a half-dozen gaming consoles, including Microsoft’s own Xbox, one might consider that it isn’t Vista’s job to play high-end games. The Gamers of the world politely (and not so politely) disagree.
Any true power gamer has long since replaced several components of any computer system from the vendor, even so-called gaming systems. Spend five minutes on any gaming forum and you’ll see posts ranging from over-clocking hardware, to upgrades that require a soldering iron. Over the years, these communities have learned to stretch their gaming power to the limits without breaking XP. That experience, of course, is missing on Vista. Tricks that once produced additional power, now produce crashes.
Many of Vista’s improvements are under the hood. Better security, improved stability, tighter driver models, better memory usage, automatic hard drive defragmenting, an I/O model that allows for lower priorities for “behind the scenes” tasks — are all leaps forward in OS architecture. But, none of them are really visible to Joe User who has to wonder what they paid extra for when their PC came loaded with Vista.
No manufacturer can be expected to sell last year’s model forever, but when Microsoft announced that it would no longer allow people to purchase Windows XP, it seemed like the company was bullying users into using a product that they didn’t want. The problem was exacerbated when Microsoft let loose Service Pack 3 which solidified the idea in many user’s head that XP was still a “current” operating system and the only reason Microsoft wouldn’t let them buy it was dollars.
What many people fail to understand is just how long after a product stops selling that Microsoft must support it. The cut-off for XP was more about starting the clock ticking down on XP support, than about forcing users to buy Vista.
Much of Vista’s criticism comes in the form of “XP is better. Whether this is true or not, it shows that users have come to both understand, and respect Windows XP. Over the years, various patches, updates and three service packs have turned it into a solid workhorse that can be counted on by home users and corporations alike who with millions of installed systems, are not surprisingly reluctant to undertake the huge task of replacing that systems.
Windows XP was not universally loved when it was first released either. As a computer consultant at the time, I can remember the multitude of complaints and criticisms then as well. The difference was that Windows XP replaced Windows 95/98 which was never a very good operating system. The migration to XP came with the idea that at least it wasn’t Windows 95. This time, it’s different. People look at Windows XP and see a perfectly good if dated operating system.
Windows 7 is apparently coming as fast as Microsoft can get it here, but as early looks have shown, Windows 7 is the next version of Vista, not the next version of XP. In the end, it seems Vista will be Microsoft’s OS of the future, it just might have a new name.
2:34 AM
5:23 AM
kamlesh.sitapara
A popular Windows blog client for your WordPress, TypePad, Blogger, Drupal, etc. blogs. Get convenience and speed of a native application, and the ability to write posts offline.
BlogJet is a desktop blogging application that greatly simplifies posting to your blog. It is user-friendly, easy to use and elegant. Emphasize Your Viewpoint
You can make text bold, italics or even change colors and fonts, create numbered and bulleted lists. BlogJet displays text in editor so it looks the same as it will appear in browser. They call it WYSIWYG (What You See Is What You Get).
Insert Pictures with Ease
Amaze the readers of your blog with funny pictures and photos of you and your friends! Just copy a picture from browser to BlogJet, or select an image from your computer, and it will be automatically uploaded to your blog when you post the entry.
Talk in Your Blog
The funniest way to express yourself and personalize your blog is to fill it with voice. When you have no words to write, take a microphone and say. Your speech will be attached to post and published with the text.
Change The History
BlogJet allows you to get the list of your previous posts with preview pane. If you want to correct mistakes or just change the text you posted, double-click a post and edit it.
Blog Everything You Find
BlogJet installs a special button on Internet Explorer's toolbar that allows you to create a blog entry about the current page.
For More Information : http://www.codingrobots.com/blogjet/
9:50 AM
kamlesh.sitapara
9:42 AM
kamlesh.sitapara
9:39 AM
kamlesh.sitapara
9:39 AM
kamlesh.sitapara
11:12 AM
Download Mix Software | |||
winrar 3.8.1 | Win Rar easy way to Zip your File... | ||
Winzip 11.2 | Zip, Unzip your File with Winzip 11.2 Version... | ||
Acrobat Reader 9.0 | Acrobat Reader 9 Latest Version... | ||
Convert Img to PDF | Convert any Image (JPG,GIF etc.,) File to PDF.... | ||
Cute PDF Convertor | Convert any Word or Excel File to PDF.... | ||
Able2Extract PDF 2 Excel Convertor | Convert PDF Sheet Two Excel.... | ||
Cute FTP | FTP Upload and Download Files.... | ||
Avast Browser | Browser for All Your Internet Need... | ||
Firefox_Setup 3.0 | Mozilla Firefox Browser Setup .... | ||
Google Chrome Browser | Google Chrome Browser Setup .... | ||
Opera Browser | Opera_9.27_International_Setup.... | ||
Internet Explorer 7 | IE7-WindowsXP without validation Tool... | ||
CC_ Cleaner_ Setup | Remove Your Unwanted Files From Computer... | ||
Download Accelerator | Increase Your Download Speed 400 Time Faster... | ||
Google_Earth_BZXE | Google_Earth_Setup.... | ||
Google Talk | Google Talk Setup.... | ||
Yahoo Messanger 9.0 | Yahoo Messanger 9 Latest Version... | ||
Rediffboll Messenger | Rediff Boll Messenger Latest Version... | ||
MSN Messanger | Install_MSN_Messenger 7.5.... | ||
Windows Live | Windows_Live_Installer.... | ||
Lock Folder | Lock Your Folder.... | ||
Nokia PC Suite | Nokia_PC_Suite_rel_6_86_9_3_eng_web.... | ||
Setup-Media Code | Windows Media Player Code.... | ||
Play Youtube Video | Play You Tube, Google, Flash Video on your PC.... | ||
Paragon partition_magic_demo | Resize, Shrink Hard Disk Partition..30 days Trial.. | ||
Windows Genuine Removal | Windows XP Genuine Advnatage Removal Patch.... | ||
Yahoo Mail to Outlook Express | Download your yahoo mail to outlook Express patch_xp.... | ||
Internet Explorer 6.0 | Microsoft I.E.6.... | ||
Baplie Viewer | Baplie Viewer... | ||
Power DVD Trial | Power DVD Trial Setup... | ||
Free Hide Folder | Hide Your Folder Setup... | ||
You Camera Software | Photo, Video to your Laptop Web Cam... |