Domain: liutilities.com
Stories and comments across the archive that link to liutilities.com.
Comments · 8
-
Re:"Microsoft regrets
Do you mean something like Winword which has been included in Windows since Windows95 or 98?
-
Re:computers: still not for lay people
I'm sure that, if Granny can figure out how to use msconfig, she'll be able to use Google (first link returned from a search of "tfswctrl.exe").
-
Windows services list
In the past, I've found this list to be very handy in figuring out which services are simply unnecessary. While I don't agree that you want to shut down *all* services (I wanted my USB key to work...stuff like that), You can shut down a LOT of unnecessary garbage to help speed up the system and boot time...not to mention make things a little more secure.
-
why not use the same software they are?most of the people out there seem to be using the same software after a quick search, NovaNet-Web from NovaStor, http://www.novastor.com/
Here are just a few I found with a quick search of '448 blowfish backup' on google
-
Re:$0 marginal cost...iPodService and iTunesHelper...
I have 1 word for you regarding these: msconfig
Just turn the iTunesHelper and iPodService off...It is not that difficult to do...
In fact if you look HERE you will see that iTunesHelper.exe is a non-essential service and therefore safe to turn off.
the iPodService is also non-essential. You can turn it off as well. Look HERE for more information.
-
Re:$0 marginal cost...iPodService and iTunesHelper...
I have 1 word for you regarding these: msconfig
Just turn the iTunesHelper and iPodService off...It is not that difficult to do...
In fact if you look HERE you will see that iTunesHelper.exe is a non-essential service and therefore safe to turn off.
the iPodService is also non-essential. You can turn it off as well. Look HERE for more information.
-
Re:Microsoft: Bloat Versus Speed
"no, it isn't" oh yes it is
-
Re:I Hate to Say ItFunny, no where in the doc for GetTickCount() does it say it is deprecated and not to use it. The only thing it does say is "If you need a higher resolution timer, use a multimedia timer or a high-resolution timer." I don't know what the program needs since I did not write it nor have I seen the code. Maybe they didn't need a high-res timer and wanted a tick count for how long the system has been up? I don't think that is too much to ask from on OS.
The GetSystemTimeAsFileTime() function retrieves the current system date and time. The information is in Coordinated Universal Time (UTC) format. It doesn't tell you how long the system has been up.
Oh, and if MS did not think this is a problem why did they fix it in a WinNT service pack? Also, right in that link MS says
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
MS also didn't seem to fix it in Win2000 Server and their own engineers got hurt by it, specifically with Rpcss.exe which according to MS
SYMPTOMS
If GetTickCount is "deprecated" as you state, why in the world is MS's own programmers using it in rpcss.exe? According to this site
The Rpcss.exe process consumes 60 percent or more of CPU time, and system performance and network performance are affected. This symptom typically occurs 49.7 days after the server is started.
CAUSE
This problem occurs because a call to the GetTickCount timer function causes the function to overflow 49.7 days after the server is started.rpcss.exe is an executable of Microsoft Windows Opearting System. It is reponsible for Remote Procedure Call services on the local machine. These are public services available to the local network. This program is important for the stable and secure running of your computer and should not be terminated.
Still not convinced and want to appologize for MS? Well here are some more of MS's software that are affected by it in Windows 2000 servers (what this FAA project is using).
Print Spooler Stops Scheduling Print JobsThe Print Spooler service may stop scheduling print jobs to specific Simple Port Monitor (SPM) ports. Although incoming jobs are queuing into the spooler, print jobs may not start. Note that this symptom occurs 49.7 days after you start the Print Spooler service.
There are a bunch of MS apps affected by this logic flaw that has been passed from version to version of MS OSes. If this flaw affected all these MS developers who have far more access to proprietary docs, I don't see how other developers would not stumble over it as well since they do not have access to the proprietary OS.