After installing P3 (an old 16-bit version) on my Win2K3 terminal server, I noticed that performance was pathetic - intolerable, actually. There is a permissions problem as well but I don't have a solution to that one yet. Maybe I'll work on that as time permits - but not a big deal as I'm the only one to use it.
Anyway, after trying a few other things I found a posting somewhere that suggested I run the program once immediately after I had installed it but before I returned to execute mode (clicked on "finish" in the add/remove programs dialog). I did this and noticed that the program ran quickly! However, after I left install mode and returned to execute mode performance was back to pathetic. Something in execute mode was causing the problem.
I found an enlightning Microsoft article at: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ts_cmd_changeuser.mspx that describes the operation of the Change User comand.
While poking around on google groups with my friend Tony I found this seemingly unrelated article:
Google Groups : corel.wpoffice.office2002-installs
The secret is in program compatibility flags!
Reference: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/31655e26-f0f2-44e3-af91-f0b7d406f531.mspx.
So, to solve, I created the following key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\TerminalServer\Compatibility\Applications\P3]
And I then created a new DWORD entry: Flags = 0x00000404
And that's it.
Monday, May 30, 2005
Thursday, May 26, 2005
Removing Norton programs using SymNRT
Removing your Norton program using SymNRT
A Symantec tool for purging Norton products from your system.
A Symantec tool for purging Norton products from your system.
Thursday, May 19, 2005
Thursday, May 05, 2005
PingPlotter
PingPlotter: "PingPlotter is a network troubleshooting and diagnostic tool. It uses a combination of traceroute, ping, and whois to collect data quickly, and then allows you to continue to collect data over time to give you the information you really need to identify problems (both short-term and long-term trends).
PingPlotter is unique in its ability to collect data, over a period of hours, days or weeks, allowing you to then focus on particular aspects of that data to determine where the problems are happening. Of course once you've found the problem, you need to communicate that problem to someone that can help, and Ping Plotter graphically shows problems in a way that is compelling and intuitive. This can greatly shorten the time, for instance, it takes to convince your network service provider or ISP that a problem really exists. PingPlotter isn't just a tool to help you troubleshoot Internet connections, however, and has a place in any administrator's arsenal of tools.
Not only does Ping Plotter help you locate existing problems, but it can also be setup to watch for new problems as they happen and then notify you via the powerful built-in alerts capability."
PingPlotter is unique in its ability to collect data, over a period of hours, days or weeks, allowing you to then focus on particular aspects of that data to determine where the problems are happening. Of course once you've found the problem, you need to communicate that problem to someone that can help, and Ping Plotter graphically shows problems in a way that is compelling and intuitive. This can greatly shorten the time, for instance, it takes to convince your network service provider or ISP that a problem really exists. PingPlotter isn't just a tool to help you troubleshoot Internet connections, however, and has a place in any administrator's arsenal of tools.
Not only does Ping Plotter help you locate existing problems, but it can also be setup to watch for new problems as they happen and then notify you via the powerful built-in alerts capability."
Wednesday, May 04, 2005
Monday, May 02, 2005
Did Installing An Anti-Spyware Program Kill Your IP Networking?
Newsletter #47 Late April 2005
From Mark Minasi's newsletter:
Did Installing An Anti-Spyware Program Kill Your IP Networking?
Sometimes the cure is worse than the disease.
A good friend installed Microsoft's Anti-Spyware beta at my recommendation. (I can't stress how much you need this or some other anti-spyware tool. I've liked ADAware as well.) Anyway, he had a terrible reaction to the anti-spyware tool -- his IP stack no longer worked. I was puzzled until I ran across this feature of XP's SP2 and 2003's SP1. Just type this command:
netsh winsock reset catalog
As it turns out, many things insert themselves between your IP stack and the rest of your system. Most are benign or outright helpful. But because something that sits between the rest of the OS and the IP stack may not be the ONLY thing between the OS and the IP stack, these in-between programs must play well with one another -- these in-between programs all sit in a line and must be aware of who's ahead of them and who's behind them in line. that way, if one in-between program exits, it knows to link the program behind it in line to the one in front of it in line. (This "line" is the "catalog" in the above command.) But some poorly written browser helper objects (one type of these in-between programs often used in spyware) aren't good at cleaning up after themselves and, when those kinds of browser helper objects are removed by anti-spyware tools, then the line of "in-between programs" may get messed up, with the result that you can't do anything on IP.
In any case, the bottom line is that if installing some kind of anti-spyware tool has made it impossible for you to network, open up a command line and try typing "netsh winsock reset catalog."
From Mark Minasi's newsletter:
Did Installing An Anti-Spyware Program Kill Your IP Networking?
Sometimes the cure is worse than the disease.
A good friend installed Microsoft's Anti-Spyware beta at my recommendation. (I can't stress how much you need this or some other anti-spyware tool. I've liked ADAware as well.) Anyway, he had a terrible reaction to the anti-spyware tool -- his IP stack no longer worked. I was puzzled until I ran across this feature of XP's SP2 and 2003's SP1. Just type this command:
netsh winsock reset catalog
As it turns out, many things insert themselves between your IP stack and the rest of your system. Most are benign or outright helpful. But because something that sits between the rest of the OS and the IP stack may not be the ONLY thing between the OS and the IP stack, these in-between programs must play well with one another -- these in-between programs all sit in a line and must be aware of who's ahead of them and who's behind them in line. that way, if one in-between program exits, it knows to link the program behind it in line to the one in front of it in line. (This "line" is the "catalog" in the above command.) But some poorly written browser helper objects (one type of these in-between programs often used in spyware) aren't good at cleaning up after themselves and, when those kinds of browser helper objects are removed by anti-spyware tools, then the line of "in-between programs" may get messed up, with the result that you can't do anything on IP.
In any case, the bottom line is that if installing some kind of anti-spyware tool has made it impossible for you to network, open up a command line and try typing "netsh winsock reset catalog."
Subscribe to:
Posts (Atom)
