May 3rd, 2009

You are currently browsing the articles from MS Windows Vista Compatible Software written on May 3rd, 2009.

Manual Removal of W32/AutoIt.OJ Worm

Manual Removal of W32/AutoIt.OJ Worm

W32/AutoIt.OJ is a worm. The worm will infect Windows systems.
This Worm Copies its files to Windows\System Folder as hidden files.
This worm information updated on April 29, 2009.
Other names of W32/AutoIt.OJ Worm:
This worm is also known as Worm.Win32.AutoIt.oj, Win32/Autoit.FO, W32.Harakit.

Damage Level : Medium/High
Distribution Level: Medium
W32/AutoIt.OJ 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/AutoIt.OJ Worm Known File Removal Tool

[In Windows Vista Run As Administrator, After Execution System Will Restart]

%Windows\System\csrcs.exe
%Windows\System\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/AutoIt.OJ 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 ]
and then continue with the removal. 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.]

The W32/AutoIt.OJ Worm modifies registry at the following locations to ensure its automatic execution at every system startup:
Delete The Entries
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Delete file entries from right side

Search Registry For W32/AutoIt.OJ 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)

Ultimate Links PC Tips™

Written by FireFly on May 3rd, 2009 with no comments.
Read more articles on W32/AutoIt.AA Trojan and W32/Autoit.GC and csrcs.exe and W32/AutoIt.HI and worm removal and otherSoftware and manual removal and Windows.

System Services and Runlevels

The init command boots Ubuntu to a specific system state, commonly referred to as its runlevel. Runlevels determine which of the many available system services are started, as well as in which order they start. A special runlevel is used to stop the system, and a special runlevel is used for system maintenance. As you will see, there are other runlevels for special purposes.

You will use runlevels to manage the system services running on your computer. All these special files and scripts are set up during your installation of Ubuntu Linux, and they receive their initial values based on your choices during the installation.

Runlevel Definitions
The Ubuntu runlevels are defined for the Ubuntu system in /etc/init.d. Each runlevel tells the init command what services to start or stop. Although runlevels might all have custom definitions, Ubuntu has adopted some standards for runlevels:

• Runlevel 0—Known as “halt,” this runlevel is used to shut down the system.

• Runlevel 1—This is a special runlevel, defined as “single,” which boots Ubuntu to a root access shell prompt where only the root user may log in. It has networking, X, and multi-user access turned off. This is the maintenance or rescue mode. It allows the system administrator to perform work on the system, make backups, or repair configuration or other files.

• Runlevel 2—This is the default runlevel for Ubuntu.

• Runlevels 3–5—These runlevels aren’t used in Ubuntu but are often used in other Linux distributions.

• Runlevel 6—This runlevel is used to reboot the system.

Runlevel 1 (also known as single-user mode or maintenance mode) is most commonly used to repair file systems and change the root password on a system when the password has been forgotten. Trespassers with physical access to the machine can also use runlevel 1 to access your system.

Never forget that uncontrolled physical access is virtually a guarantee of access to your data by an intruder.

Booting into the Default Runlevel
Ubuntu boots into runlevel 2 by default, which means it starts the system as normal and leaves you inside the X Window System looking at the Gnome login prompt. It knows what runlevel 2 needs to load by looking in the rc*.d directories in /etc. Ubuntu contains directories for rc0.d through to rc5.d and rcS.d.

Assuming that the value is 1, the rc script then executes all the scripts under the /etc/rc.1 directory and then launches the graphical login.

If Ubuntu is booted to runlevel 1, for example, scripts beginning with the letter K followed by scripts beginning with the letter S under the /etc/rc1.d directory are then executed:

# ls /etc/rc1.d/
K01gdm K19hplip K20laptop-mode K20vsftpd K80slapd
K01usplash K20acpi-support K20makedev k21acpid K86ppp
...etc...
K19cupsys K20inetutils-inetd K20ssh K74-bluez-utils S20single

These scripts, as with all scripts in the rc*.d directories, are actually symbolic links to system service scripts under the /etc/init.d directory.

The rc1.d links are prefaced with a letter and number, such as K15 or S10. The (K) or (S) in these prefixes indicate whether or not a particular service should be killed (K) or started (S) and pass a value of stop or start to the appropriate /etc/init.d script. The number in the prefix executes the specific /etc/init.d script in a particular order. The symlinks have numbers to delineate the order in which they are started. Nothing is sacred about a specific number, but some services need to be running before others are started. You would not want your Ubuntu system to attempt, for example, to mount a remote Network File System (NFS) volume without first starting networking and NFS services.

Booting to a Non-Default Runlevel with GRUB
There might come a time when you do not want to boot into the default runlevel, such as when you want to repair the X server or install a new graphics driver. You’ll need to follow several specific steps to boot to a non-default runlevel if you use the default boot loader for Ubuntu, GRUB.

The GRUB boot loader passes arguments, or commands, to the kernel at boot time. These arguments are used, among other things, to tell GRUB where the kernel is located and also to pass specific parameters to the kernel, such as how much memory is available or how special hardware should be configured. To override the default runlevel, you can add an additional kernel argument to GRUB as follows:

1. At the graphical boot screen, press e (for edit), scroll down to select the kernel, and press e again.
2. Press the spacebar, type single or 1 (Ubuntu allows S and s as well), and press Enter.

3. Finally, press b to boot, and you’ll boot into runlevel 1 instead of the default runlevel
listed in /etc/inittab.

Source of Information : Sams Ubuntu Unleashed 2008 Edition

Written by magakos on May 3rd, 2009 with no comments.
Read more articles on Ubuntu Linux and otherSoftware.

The Milton Keynes Project – 23 years in the making

As some may be aware, I’m finally hunkering down on a project that most people I’ve told about it are scratching their heads about in equal measures of bemusement and amusement. A photo study of Milton Keynes. Unusual for someone who generally really likes landscape photography but not that unusual if you know me. I’ve got quirky interests and I’m happy for it to stay that way.

New 3/5/09 : Milton Keynes: The Future

Why am I doing this?

I’ve always had an equal appreciation for the built environment as I have the rural landscape. I know what I like and I don’t. I hate the Twyford Down cutting, but I love the spot near Greatham Bridge. I feel somewhat repelled by Leicester but thoroughly enthralled (obsessed perhaps is closer to the truth) by Milton Keynes. It is bizarre but there you go. I can only explain it’s because the many times I went there when I was little and the massive impression it made on me when I was little. I’m trying to explore that wonder in this current work.

What is it? Aims and Goals?

It’s a mixture of landscape photography and street photography. I’m seeking out what I find pleasing and even beautiful about the place, and also the people that truly make the place. I’ve gone in with a fairly open mind and acknowledge (and you will see it in the final book) that not everything is perfect and that some of the commonly cited ‘issues’ with MK on a couple of counts have some decent grounding behind them. My aim is a personal one, to capture why I like the place so much and why I feel it is important to Britain as a whole. Goals are for ambitious people and I am not doing this for world peace or something profoundly impossible. My goal might be for a few people to pick it up and have their perceptions changed or at least a seed of intrigue to be sowed.

I’m very cautious of ending up with a Pittsburgh Project and if I am utterly honest: I think this is my Pittsburgh Project, but I’m putting a start and end on it for impression:mk – for my own sanity and the project’s success. I’m not suggestion I have even 1% the brilliance of W Eugene Smith, but I can see a thread of similarity. After all, arguably this is a project I started when I first visited the city in the 80s, thought about photographing at school and then began slowly in 2004 before taking a 5 year hiatus on the project. I was meant to start again late 2006 but other issues tainted progress.

Where can I read more about this project and inter-related issues?

What does the project name mean?

Milton Keynes is abbreviated MK all over the place, and I can’t think of anyone who lives in MK that wouldn’t know what you meant if you said MK to them. The impression part is in the literally sense an impression, a subjective view of a topic/subject. It’s also a direct nod to impressionism and one of my all time favourite paintings: Impression, Sunrise. Finally, as with many current developments, the names of them seem to follow a pattern e.g. Stadium:MK, the hub:mk and the centre:mk

How am I doing it?

Largely I am using my Leica M2 and I’m visiting often, all seasons and spending weekends and sometimes longer (depending on if I can get time off work and annual leave allowance permitting!) staying in the city and walking and driving around. I’m a very keen walker so some visits I have walked upwards of 30 miles in one weekend but its one of the few ways to really get to grips with the place. Intentionally you can’t see much from the car from the grid roads.

I’m also using a Canon EOS 3 for the night exposures and any telephoto based shots (which are minimal.)

Unusually for me, the project is largely in colour although I do have some very nice black and white shots but I’m inclined to keep them back as I’m concerned that consistency will not be achieved by mixing between colour, duotone, black and white etc.

So far I have used colour wise: Kodachrome 64 (bulk of daytime work), Fuji Provia 100F (remainder of daytime work and pretty much all night time long exposure work) and for black and white Kodak Tri X at box speed and pushed to 1600, and Fuji Neopan Acros for the finer daytime work. Black and white development has been by myself (originally using ID11, now using Xtol) and processing for Kodachrome has been done by Dwayne’s in Kansas, USA. E6 processing by Peak Imaging.

Written by lilserenity on May 3rd, 2009 with no comments.
Read more articles on otherSoftware and Uncategorized.

Just because I can…

I really have no practical use for this, but it sure was fun to set up and get to work

Written by jaysonrowe on May 3rd, 2009 with no comments.
Read more articles on hackintosh and osx86 and KVM and otherSoftware and Computing and Leopard and Virtualization.

Configuring Libraries and your Devices

Richard H. recently did an excellent review about adding content to your Libraries in Windows 7. I just want to add some additional information I discovered when adding folders to my personal Libraries. Folders that are on a Network need to be indexed before you can start utilizing them through Libraries for functions such as Instant Search and Organization, this also applies to devices such as external hard disk. Note that, if the content is on a removable hard disk or network device, the content of the folder will only be available when the device are connected to your computer.

To make a folder available offline

In this scenario, I am indexing a folder from a computer networked with my Windows 7 PC.

When you make a network folder available offline, copies of all the files in that folder will be stored on your computer's hard disk. Take this into consideration if the network folder contains a large number of files.

1. While connected to the network, locate the network folder that you want to make available offline.

2. Right-click the folder, and then click Always available offline.

Preparing a folder to be added to your Library

Note
If you don't see the Always available offline command, you might be using an edition of Windows 7 that doesn't support offline files.
If the location contains a lot of files, it might take some time for the Library to add those files to the index.