Sunday, April 4, 2010

Nod32 - Free username and password




NOD32 IDs Update Time April 05,2010 18:12:26 ThreatSense Update:v.4995 (20100402)

Username: EAV-29249310
Password: xefc8jcn6k

Username: EAV-29249311
Password: sv844kn7f2

Username: EAV-29259923
Password: puk3mhuamm

Username: EAV-29249307
Password: dj8aev4seb

Username: EAV-29261030
Password: 2jvcs83bp2

Username: EAV-29249309
Password: k8878rdfe6




Read more...

Monday, March 29, 2010

Nod32 Free Username and password




NOD32 IDs Update Time March 29,2010 15:12:26 ThreatSense Update:v.4982 (20100329)

Username: EAV-28733936
Password: 4mv3mxdev5

Username: EAV-28733944
Password: 7f5rx4merv

Username: EAV-28733949
Password: b7jujc88af

Username: EAV-28732549
Password: hscsdp3e7s

Username: EAV-28732552
Password: 4mku8bbbx4

Username: EAV-28732553
Password: v5ck4dmtaf




Read more...

10 ways to tweak your Linux Boot Process




Linux rarely needs to be rebooted. But when it does, it’s often slow to boot. Fortunately, there are ways to speed things up. Some of these methods are not terribly difficult. (although some, unfortunately, are). Let’s take a look.

#1: Disable unnecessary services


Depending upon the use of the machine, plenty of services won’t be needed. Using Linux just for a desktop? Then you won’t need sendmail, http, and many other services. If your server is only a web server, you can shut off many services as well. To do this, you can go to the Administration menu and take a look at the Services entry. Just deselect all of the services you don’t want to start.

#2: Disable unnecessary kernel modules

If your desktop is wired to the Ethernet, you don’t need to have a wireless kernel module loaded. This task is a bit more difficult and will require a kernel recompilation, which is not the easiest task to undertake. To do this, you will need the kernel sources. Then, follow the standard steps for compiling a kernel. The difference is that you’re going to go through your system and disable all of the modules you don’t need.

The best way to find out what kernel modules currently install and run on your system is to install Bootchart. Not only will this give you a good list of modules, it will illustrate for you what is happening during your system boot. You can also issue the command chkconfig –list | grep 3:on to find out what services are running. Once you know what loading modules you don’t need, you can remove them during a kernel recompilation. While you’re at it, compile the kernel to exactly match your architecture.

#3: Use a lightweight window manager instead of GNOME or KDE

I plug smaller footprint window managers for a reason — they drastically reduce graphical boot time. Instead of having to wait that extra 30 to 60 seconds for GNOME or KDE to boot up, why not wait two to 10 seconds for Enlightenment or XFCE to boot up? Not only will they save you boot time, they will save your memory and the headache of dealing with bloatware.

#4: Use a text-based login instead of a graphical login

Most of my Linux machines boot to run level 3 instead of run level 5. This will halt at the text-based login, where I only have to log in and issue startx to start my desktop of choice. The graphical logins do two things: increase load times and create headaches trying to recover from an X windows fubar.

#5: Use a lighter-weight distribution

Instead of loading the heavyweight Fedora, why not try a Gentoo, Arch, or Puppy Linux? The boot times for these smaller distributions are far faster than the more bloated Fedora (and even Ubuntu). Of the larger distributions, OpenSuSE claims to boot the fastest, but I have not personally tested this. Between the latest Fedora and Ubuntu, Ubuntu blows Fedora’s boot times away (and that is out of the box).

#6: Use an OpenBIOS

If you’re savvy enough to upgrade your PC’s firmware, you might consider migrating to an open source BIOS. One caveat to using open firmware is that it allows Linux to actually initialize the hardware as it boots (instead of relying on the BIOS). On top of that, many open BIOSes can be configured to meet your machine’s specific needs. If you don’t go the open BIOS route, you can at least configure your BIOS to not search for a floppy drive that’s not there or to boot directly to the first hard drive (instead of the CD drive first).

#7: Avoid DHCP

If you are working on a home network (or a small business network) where address lease isn’t a problem, go with static IP addresses. This will keep your machine from having to call out to a dhcp server to get an IP address. If you take this approach, make sure you configure your /etc/resolve.conf to reflect your DNS server addresses as well.

#8: If you can spare it, get rid of hotplug

Hotplug is the system that allows you to plug in new devices and use them immediately. If you know your server won’t need this system, delete it. This will cut down on boot time. On many systems, hotplugging consumes much of the boot time. Removing hotplug will vary depending upon the distribution you use. NOTE: udev has, for the most part, replaced hotplug. But if you’re running an older distribution, this does apply.

#9: If you are REALLY daring, you could give initng a try

The initng system serves as a replacement for the sysvinit system and promises to drastically decrease boot times in UNIX-like operating systems. If you would like to see the initng system in action, you can give the Pingwinek livecd a try.

#10: Use a hack with Debian

If you’re using Debian, there is a simple hack you can use to switch your startup scripts to run in parallel. If you look at the /etc/init.d/rc script, you will see: CONCURRENCY=none around line 24. Change this line to CONCURRENCY=shell and you should see a reduction in boot times.

That’s about it. Of course there are always more and better hacks out there. But the above should mostly cover everything. The good news is that you’re most likely already running Linux, so the burden of boot times is generally eased by the infrequency of reboots.




Read more...

How To Speed up Firefox




Okay so everybody saw lately Google Chrome which is preety damn fast internet browser. Interesting why did they manage to make their own browser while they pay 70% of Firefox revenue to be on their bar right? Of coursde they just want to gather more info about you ;) Thats the theory of google working with FBI. Either way, lets speed up mozilla firefox a bit!

Stuff shown here is simple to be made and will really make the browser work better and faster .
For starters lets stop Firefox from eating so much RAM! This may preven loose of your data so you wont need files recovery. Increase Computer Speed And Stability By Removing Corrupted Registry Files With Registry Toolkit.

Anyways lets get back to business.
Tak off the amount of RAM Firefox uses for its cache:
1. Type in browser window about:config
2. Find – browser.sessionhistory.max_total_viewer
3. Set the value to 0

Reduce RAM usage to around 10MB when Firefox is minimized [i bet this kills your memory sometimes with many tabs open!]:

1. Open Firefox and go to the Address Bar. Type about:config and then press Enter.
2. Right Click in the page and select New -> Boolean.
3. In the box that pops up enter config.trim_on_minimize. Enter.
4. Select True
5. Restart Mozilla Firefox.

Increase the Speed at Which Firefox loads pages

1. Type about:config into the address bar and hit Enter.
(Normally the browser will make 1 request to a web page at a time which is wack. When you enable pipelining it will make several at once, which really speeds up page loading.)

2. Alter the entries as follows:
Set network.http.pipelining to true
Set network.http.proxy.pipelining to true
Set network.http.pipelining.maxrequests to some number like 12.

This means it will make 12 requests at once.

3. Lastly, right-click anywhere and select New-> Integer. Name it nglayout.initialpaint.delay and set its value to 0

And that is how we speed up newest version of Mozilla Firefox 3.0.8 and all other versions.




Read more...

Fix Windows Explorer Error When Browsing Folder




Have you been experiencing that Windows Explorer problem?


This problem occurs when you try to browse folders when suddenly your Explorer.exe is not responding and you need to restart Explorer.exe. Hence, your whole system hangs for a few seconds and you basically can do nothing with your taskbar has also gone.

Then after the finger-crossing moment is over, your icons in the system tray have also been resetted. In my case, some of the icons have also disappeared and I need to end the process and restart it so that I can use or monitor the application again.

It indeed occurred to me so often that I thought it was my folder being corrupted and deleted the whole folder in the end. Apparently, it was not.

This error is caused by the automatic image preview built-in in Windows. This image preview feature is loaded inside the system files and always loaded whenever your system boots by default. To be more exact, it is registered as the shmedia.dll. It is better known as the Media File Property Extractor Shell Extension. Therefore, once we unload this dll file, you will not experience this Windows Explorer error again.

To unload or un-register the shmedia.dll, simply from Start Menu > Run, type:

regsvr32 /u shmedia.dll

This command will let you un-register the shmedia.dll and hopefully, there will be no Windows Explorer error again.




Read more...
 

Facebook Fan Page

Gift Box


Gift box

Page Viewed
blogspot statistics

Twitter box

Cheatingz - Pc tips tricks tweaks and hacks Copyright © 2010 Website powered by Blogger Designed by Puzzifier