Your best source of information and news about software, xp and software on the internet

October 27th, 2009

You are currently browsing the articles from MS Windows Vista Compatible Software written on October 27th, 2009.

Manual Removal of W32/AutoRun.FOC Worm » olhrwef.exe

W32/AutoRun.FOC Worm Known Files » olhrwef.exe, nmdfgds0.dll, nmdfgds1.dll, 0xuc.com, yudald.bat, autorun.inf
W32/AutoRun.FOC is a worm. The worm will infect Windows systems.
This Worm Copies its file(s) to Windows\System32, root of Windows installed drive folder as hidden files or active non-hidden files.
This worm information updated on September 26, 2009.
Other names of W32/AutoRun.FOC Worm:
This worm is also known as Worm.Win32.AutoRun.foc, Worm:Win32/Taterf.B, Worm.AutoRun.NNX.
Download Registry, Taskmanager and Folder Options Repair Tool

W32/AutoRun.FOC Worm Manual Removal Instructions
Recommend Removal from Safe Mode:
How to Start in Safe mode:
Restart your Computer, Press F8 Repeatedly, when your Screen turns on, Select Safe mode, press enter.

The Infected Files Can be Seen in these folders and names also Running in Tasks
End the Following Active Process Before Removal
  • [ Kill the Process, Use Killbox if your Access Denied ]
Download W32/AutoRun.FOC Worm Known File Removal Tool
[In Windows Vista Run As Administrator, After Execution System Will Restart]
  • %Windows\system32\olhrwef.exe
  • %Windows\system32\nmdfgds0.dll
  • %Windows\system32\nmdfgds1.dll
  • %Root of Windows\yudald.bat
  • %Root of Windows\0xuc.com
  • %Root of Windows\autorun.inf
    [ No Exact Information about Files, search above related files in Program files Folder ]
    If you have any of these files in running process from task manger, end the process before removal.
    Note: if task manager is disabled, Download the following file, Click to Download - Enable Registry.reg[ Right Click - Save Target As/Linked Content As ]
    Open it with Regedit.exe [%system32\regedit.exe], then it Confirms Add to registry Yes or No, Confirm Yes, then click Ok.
W32/AutoRun.FOC Worm Entries Manual Removal From Registry
Click Start, Run,Type regedit,Click OK.
Note: If the registry editor fails to open the threat may have modified the registry to prevent access to the registry editor.
  • Download this UnHookExec.inf, [ Right Click - Save Target As/Linked Content As ]
  • Save it to your Windows desktop.
  • Do not run it at this time, download it only.
  • After booting into the Safe Mode or VGA Mode
  • Right-click the UnHookExec.inf file and click Install. [This is a small file. It does not display any notice or boxes when you run it.]
  • Or Download Regfile to enable Registry editor 
  • Download Registry Enabler [ Right click - Save Target As ] 
  • Open it with Registry editor
W32/AutoRun.FOC Worm modifies registry at the following locations to ensure its automatic execution at every system Startup:
Delete The Entries

HKEY_USERS\S-1-5-21-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXX-XXXX\Software\Microsoft\Windows\CurrentVersion\Run
Delete file entries from right side
Search Registry For W32/AutoRun.FOC Worm File Names listed above to remove completely,
Edit Menu - Find, enter Keyword and remove all value that find in search.

Exit the Registry Editor,
Restart your Computer.
Recommended Removal Tools:
Kaspersky Antivirus or Internet Security [Shareware]
Spyware Doctor [Shareware]
AVG Antivirus [Freeware]
Killbox [Freeware]

Written by magakos on October 27th, 2009 with no comments.
Read more articles on Autorun.inf and olhrwef.exe and worm removal and manual removal and otherSoftware.

Widget Anatomy – Touch and D-Pad inputs, oh joy!

This is fifth and final part of my Widget Anatomy series that described the ins and outs of the Widget Framework that shipped with windows mobile 6.5.  In this installment we will discuss the different ways a Widget can receive inputs from the user and how best respond to them.

First the easy one: Touch

Touch is the primary input for all our professional devices and it looks like they will be a significant percentage of our device offering.  Handling this is fairly easy since the browser engine translate the touch event into a mouse click which can be handled by using the onclick event handler as shown in the following example:

   1: <html>
   2: <head>
   3:     <script type="text/javascript" src="js/ImageSearch.js"></script>
   4: </head>
   5: <body>
   6:     <div id="SearchBox">
   7:         <input id="SearchQuery"/>
   8:         <img src="images/search.png" class="searchIcon" 
               onclick="doSearch();" />
   9:     </div>
  10: </body>
  11: </html>

It is important to note that, since there is no “mouse” for widgets most of the other mouse related events like onmouseover, onmousemove, etc will not be triggered in a reliable enough way to use them.

Now the hard one: The Directional-Pad

I been making special emphasis to the fact that Widgets work seamless across all Windows Phones so, we need to ensure that the can be used correctly when the user interacts with it using the directional path.

It is important to note that, unlike IE6, a The widget framework will respond to a D-Pad input event by moving the focus to the closed actionable element in the direction of the user click.  This behavior is similar to the old pocketIE and among friends we call it “Link to Link navigation”.

An actionable element is defined as any DOM element that can receive focus (Like a form field) or an element that implements its onclick event handler.  When an actionable element gain focus the onfocus even is triggered, the same way, the focus is moved away from the element the onblur event is triggered.  Now we can easily use those events to show the user where the focus is since the Widget Framework does not automatically highlights the focused element.  We do this because we don’t want to inhibit the creativity of the widget creator to design his/her own focused highlight strategy.

The only “little” extra detail is that all elements that can gain focus need to have the tabindex property defined (the value is not important).  This is easily forgotten but if not set, the focus and blur events will not trigger, 

<html>
<head>
<script type="text/javascript">
   1:  
   2:     function OnFocus(element) {
   3:         element.style.backgroundColor = "red";
   4:     }
   5:     
   6:     function OnBlur(element) {
   7:         element.style.backgroundColor = "white";
   8:     }
</script> 
</head>
<body>
<div onfocus="OnFocus(document.getElementById('one'))"
     onblur="OnBlur(document.getElementById('one'))"
     onclick="alert(1)"
     tabindex=1>
        <p id="one" style="font-size:medium:">1</p>
</div>
<div onfocus="OnFocus(document.getElementById('two'))"
     onblur="OnBlur(document.getElementById('two'))"
     onclick="alert(2)"
     tabindex=2>
        <p id="two" style="font-size:medium;">2</p>
</div>
</body>
</html>

In this example, we created two divs that can receive the input focus, you can move from one to the other using the D-Pad, the element that receives focus changes the color of its background to red.

Screen05  Screen06

Conclusion

Writing Windows Mobile applications is now as easy as writing a web page, and, by following some best practices your widget can be as functional and attractive as any other native application on the platform.

This is the end of this blog series and since Windows Phones are now available on many countries, you should go get one and write many cool widgets for it.  Don’t forget to share the results with the world by uploading them to the marketplace!

Until next time

Jorge Peraza

Widget anatomy series at glance

#1 The manifest

#2 The keys for a great user experience

#3 Performance and battery life

#4 Security insights

#5 Touch and D-Pad inputs, oh joy!

Written by Jorge Peraza on October 27th, 2009 with no comments.
Read more articles on 6.5 and widgets and otherSoftware.

Windows7 Trigger Start Services – Part 2: Building a Trigger Start Optimized Service

In the last post Windows 7 Trigger Start Services – Part 1: Introduction, we introduced Windows7 Trigger Services as a great way to optimize your services to have better performance and improved security. In this post you will learn how to convert a standard automatic-start service to a trigger-start service that starts up only when a certain event occurs in the system. We’ll use a WPF application (obviously managed code) that registers and monitors a service (also implemented using .NET). To bridge between the .NET world and the native Win32 APIs that we saw in the previous post, we use a C++/CLI interoperability layer.

This sample application has 3 parts:

  • A C++/CLI interoperability layer that provides a regular and easy .NET API to the controller application
  • A WPF controller application that lets you register and run the service
  • A simple .NET service that looks for a USB storage device (disk on key) and on it, a specific folder named “ToCopy” from which to copy files to your local “C:\FromUSB” folder

The following image illustrates the solution structure.

image

Let’s start by reviewing the .NET Service code implementation. This is a simple Windows service written in C#. The purpose of this service is to copy pictures automatically to your local hard-drive- “c:\FromUSB” from the USB storage device that is plugged into your computer.

The service implementation can be found at USBService.cs. This class inherits the ServiceBase base class and overrides the OnStart and OnStop methods. This class has a DoWork method that actually does all the copying of images from the USB disk to your local drive. The DoWork method writes to a log file that we will be monitoring.

The real interesting part of the service implementation is the OnStart method. This method is called once the service is started. Notice that the first line of code checks whether the service is configured as a trigger start service. If the “if” statement returns false, we create a new instance of a timer and have it poll every 5 seconds. Before Windows7, this was the only way to implement such a service, that is, by regularly polling the system to check for a USB device. Therefore, the service needs to run 24x7 to poll the system. This is highly wasteful of resources and keeps the system from transitioning to a low-power state, increases the application attack surface, among other negative things.

But, with Windows7, you can configure such a service with a USB device arrival trigger. This means that the service will not run until a USB device arrives, specifically a USB generic disk device. We’ll get to that part of the solution in a second, but for now, if you look at the OnStart method, you will notice that we check whether the service is configured as a trigger start service; if it is, we simply call the DoWork method on another thread, as shown by the following code snippet. This should work just fine because the service is NOT running, and will start to run only when the trigger happens. And then it will not default to the timer, but rather use the thread pool to queue the work.

 protected override void OnStart(string[] args)
 {
   if (ServiceControl.IsServiceTriggerStart(ServiceName))
   {
      ThreadPool.QueueUserWorkItem(_ => DoWork());
   }
   else
   {
     _timer = new Timer(_ => DoWork());
     _timer.Change(0, 5000);
   }
 }

The ServiceControl namespace contains the C++/CLI interop layer. This layer uses C++/CLI as the binding element between the native API and the WPF application. The main ServiceControlInterop.cpp file contains all the functionality that we need and that is used by the WPF application. For example using the controller application we can use AddService(…) or RemoveService(…) to add or remove a service respectively. We can also configure the service as a trigger start service for either a USB device arrival or first available IP address by using SetServiceTriggerStartOnUSBArrival or SetServiceTriggerStartOnIPAddressArrival respectively. Reviewing both function implementations reveals that basically both are following identical paths. They:

  • First, use OpenSCManager to get a handle to the Service Control Manager (SCM)
  • Then use the SCM handle OpenService, to get an actual service handle that we wish to configure
  • Finally call ChangeServiceConfig2 to set the specific trigger

All this was explained in detail in the last post (Windows7 Trigger Start Services – Part 1: Introduction

You can download the code sample for this application. Note that you will have to run Visual Studio as administrator (see image below) because you will need to register, start, and stop services. . You will also need to Windows 7 SDK to compile the C++ part of the solution.

image

When compiling and running the default solution (the WPF application) you will see the following image.

image

This is the main WPF controller application. From here, you can create the service by clicking the Create Manual button.

Next, open the Services Window by typing “Services” in the Start Menu search box. You should see the Service window. Locate the USBCopyService; it should appear as in the following image.

image

Click the Run button and then the Refresh button in the Services window, or just press F5. You will not notice a great deal of change, but the USBCopyService changed from Manual to Started, as shown in the following image.

image

 

A second look at the actual application reveals the service activity in the log file. As you can see in the following image, the services awaken every 5 seconds and poll the system, looking for USB devices:

image

Click the Stop button to stop the service and then click the Delete Service to delete it. Now click the Trigger Start button to register and configure the service as a trigger start service that is triggered once a USB Generic disk arrives. If you check the Service window, you will see the USBCopyService listed as “manual” where in reality it is configured as triggered start service (there is just no graphical representation of that).

If you plug in a USB disk with a “ToCopy” folder the service will kick into action and copy the files to c:\FromUSB. Not the best implementation, but hey, it is only a demo. The following image shows a single line in the log file because the service actually ran only once; it executed the DoWork method and then quit. It didn’t run and poll the system every 5 seconds and didn’t waste resources or become a security liability.

image

To conclude

Developing a service with Windows 7 trigger start service in mind might be a little more difficult than a regular “auto-run” service that just runs in idle from boot to shutdown. But in practice, all it takes is only a few lines of code, no more. And these few lines of code can have a very big affect in terms of resource consumption and security. So the next time you build a new Windows Service, try to incorporate triggers.

You can learn about Windows 7 using the Windows 7 Training Kit for Developers or by viewing Windows 7 videos on Channel 9.

You can also get hands-on experience for Windows 7 Trigger Start Services using the Windows 7 Online training that is part of the Channel 9 Learning Center

Written by Yochay Kiriaty on October 27th, 2009 with no comments.
Read more articles on Windows 7 Training Kit and Trigger Start Services and Windows 7 Trigger Start Services and otherSoftware and windows 7 and .Net and Performance and Microsoft.

Netstat

The Netstat tab provides information on three sets of network data available on the workstation:

• The routing table
• The active network services
• The multicast network information

Ubuntu maintains an internal routing table to keep track of how to forward network packets to remote networks. Selecting the Routing Table radio button then clicking the Netstat button produces a list.

The routing table matches network destinations with a gateway that can send the packets to the remote network. The routing table always includes at least two entries. One entry is the default route, 0.0.0.0. This route defines the gateway to use by default for sending packets to any network on the Internet. Usually this gateway is the IP address of your broadband modem connection.

The other route defines the local network your Ubuntu workstation is connected to. In the example, the workstation is connected to the 10.0.1.0 public network address and uses the default gateway to send packets to this network.

The active network services selection displays a list of what network ports are currently in use on the workstation. Different software packages use different network ports to listen for incoming connections. Many network servers are assigned standard network ports, such as TCP port 80 for web servers and TCP port 25 for email servers.

The network port list includes the current state of the port. TCP uses 11 states to define what mode the network port is in.


TCP Network Port States
LISTEN Waiting for a connection request from a remote client

SYN-SENT Sent a connection acknowledgment and waiting for one in return

SYN-RECEIVED Received a connection acknowledgment from remote client

ESTABLISHED Port is ready to send and receive data with the remote client

FIN-WAIT-1 Sent a connection disconnect request to the remote client

FIN-WAIT-2 Received a connection disconnect from the remote client in response to a connection disconnect request sent by the port

CLOSE-WAIT Remote client initiated a connection disconnect

CLOSING Waiting for a response from a sent connection disconnect request

LAST-ACK Waiting for remote client to acknowledge a connection disconnect request

TIME-WAIT The port is on hold for a preset amount of time after the connection disconnects

CLOSED The connection is officially closed



The TCP states are invaluable for troubleshooting network programs. By checking the network port states, you often can determine whether a remote device is closing a connection early or is keeping a connection open too long.

The final feature of the Netstat tab is the multicast network information. This protocol allows devices to subscribe to special multicast IP addresses on network routers. Network routers handle multicast packets only when they have a device on the network that requests them. This list displays whether the Ubuntu workstation has registered to receive any multicast packets on the network.

Source of Information : Wiley Ubuntu Linux Secrets

Written by magakos on October 27th, 2009 with no comments.
Read more articles on Ubuntu Linux and otherSoftware.

Windows Home Server Featured on Computer Outlook Radio Show

In case you missed it, our very own Steven Leonard (Senior Product Manager) and Jonas Svensson (Community Program Manager) were featured on the “Java with John” Computer Outlook radio show on Sunday, October 25. In case you missed it, you can listen to the replay here. Enjoy!                                                                        

Steven and Jonas kicked off the show by reminding the audience of the great features in Windows Home Server and then talking about how active our Windows Home Server community has been … taking advantage of the latest tools and resources as well as sharing feedback and best practices with Microsoft and the broader community. The guys also highlighted how the Power Pack 3 beta can improve the Windows Home Server experience with Windows 7 and Windows Media Center.

Host John Iasiuolo is a long-time user of Windows Home Server and had some cool insights about how he’s using the product at home and work, calling out some of his favorite features along the way. Of course we always love to hear from happy users! We look forward to sharing more Windows Home Server tips and tricks on future shows.

- Dave Berkowitz, Senior Product Manager, Core Infrastructure Marketing, Microsoft

Written by Dave Berkowitz on October 27th, 2009 with no comments.
Read more articles on otherSoftware.

Announcing Final Releases of Platform Update for Windows Vista Technologies

Today we are announcing the final release of the Platform Update for Windows Vista. The Platform Update for Windows Vista features a set of runtime libraries which add support for new technologies making it easier for developers to develop for Windows 7 and Windows Vista without impacting their users.

The Platform Update for Windows Vista will be available for free via Windows Update, Windows Server Update Services and the Microsoft Download Center. You will need to have Windows Update “recommended settings” enabled in order to automatically receive the update without additional action.

These updates include the following:

  • Windows Ribbon and Animation Manager Library: contains the Windows Ribbon API, a command framework that enables developers to quickly and easily create rich ribbon experiences in their applications, and the Windows Animation Manager API, an animation framework for managing the scheduling and execution of user interface element animations.
  • Windows Graphics, Imaging, and XPS Library: components for developers to leverage the latest advancements in modern graphics technologies for gaming, multimedia, imaging and printing applications. It includes updates to DirectX to support hardware acceleration for 2D, 3D and text based scenarios; DirectCompute for hardware accelerated parallel computing scenarios; and XPS Library for document printing scenarios.
  • Windows Automation API: allows accessibility tools and test automations to access Windows user interface in a consistent way across operating system versions.
  • Windows Portable Devices Platform: supplies the infrastructure to standardize data transfers between an application and a portable device, such as a mobile phone, digital camera, or portable media player.

Note that the Windows Automation API will also be made available as a separate download for PCs running Windows XP.

For specific details about the Platform Update for Windows Vista as well as the Platform Update for Windows Server 2008, click here.

By making these libraries broadly available through the Platform Update for Windows Vista, we expect customers will find an increasing number of applications using new features in Windows 7.

Written by Brandon LeBlanc on October 27th, 2009 with no comments.
Read more articles on Windows Portable Devices Platform and Windows Graphics and XPS Library and Windows Ribbon and Windows Automation and Platform Update for Windows Vista and Windows Server 2008 and windows 7 and otherSoftware and Windows Server 2008 R2 and Windows Vista.

« Older articles

No newer articles