How to Hide files inside a picture using Command Prompt - video

How to Hide files inside a picture using Command Prompt in windows easy way to hide files inside an image file (without any software)

First create a new folder in C:\ drive and name it anything i'm gonna name it "Hide"

Now move the files you want to hide and the picture in which you want to hide to the folder.

Select the files you want to hide and right click select "Add to archive..." and give the compressed file a name for example: Compressed.rar

Now open command prompt.
type cd\ to go to your root directory


Then type
copy /b yourimage.jpg+Compressed Files.rar xyz.jpg

your files will be hidden inside the image. To get your files back right click
on the image(xyz.jpg) and open it with Winrar you will see your files
you can extract the files anywhere you want on your computer.

Linux vs Windows - Fundamental Differences

Users who decided to switch from Windows to Linux have encountered major differences between the two operating systems and often gave up a free solution in favor of commercial solutions that did not know the fundamental differences between the two operating systems . The process of migrating from +Windows to +Linux would be achieved more easily if users would know exactly the difference. To help with this process will highlight the major fundamental differences between these two operating systems.


+Linux vs +Windows fundamental differences

1. Price

Given the current state of the economy, price plays a major role in the choice of operating system. Increasingly more people pay attention well deserved Linux operating system. In this area Linux supremacy can not be challenged because most distributions are free. Maybe you can think to ask "what is free?", The answer is simple: Linux is designed and developed by a community of programmers who are working for the same company, Linux has been free since the beginning sale. Most programs were developed for Linux are free. There are alternatives to all commercial software that runs only on Windows and that are free does not make them less qualitative. In some cases these free and open source programs are better than commercial alternatives.

2. Freedom

With Linux you have the freedom to choose, we can not say the same about Windows that will block the way Microsoft believes should be working operating system. +Microsoft believes that if offers users a taskbar, Start button, system tray icons and one is enough. For some maybe it is, but most users will have something different or more custom features. Using the +Linux operating system can make it look exactly as you want, the only limits are time and imagination.

3. The hierarchy file system

In Linux uses a secure hierarchical system, it all starts in the root directory "/". Drives are labeled / dev / sda, / dev / sdb, etc.. In Windows system is hierarchical and depends on the number of multiple storage units, use a root for each storage unit. Under Linux just a drive root directory contains the other drives present are mounted in / media /.

4. Hardware Support

Here things are a bit complicated because Windows has a much larger market segment (even huge) and most hardware manufacturers want their product to be 100% compatible with +Windows. Under Linux hardware support depends on how the manufacturer is convinced by the developers to deliver specifications. May encounter cases where specifications are not issued by the manufacturer and such hardware will not work properly under +Linux. However, in recent years attention has been paid increasingly higher hardware manufacturers +Linux operating system and the cases in which the hardware does not work on +Linux are pretty isolated.

5. Security

This topic is highly debated by both parties. Perhaps because of the huge market share, and the attention given to vulnerability of +Windows you are much weaker than +Linux. The main vulnerability of Windows is the access to the root. To do damage on a +Linux system you really need to know the root password. That does not mean that +Linux is 100% sure, there are many security holes in +Linux. When it is discovered a vulnerability in the Linux community it is solved by very quickly when
+Microsoft demonstrated many times that they need too much time to solve a problem.

These are important fundamental differences between +Windows and Linux. What major differences did you notice between these operating systems? Over the fundamental difference do you think the hardest pass a new user of Linux?
+Tech-place

Decrease The Shutdown Time In Windows

Whenever you give the shutdown command in your Windows PC, it forwards the request to all the running services. It waits before it tells you if any of the service did not respond to the shutdown request (waits for 12 seconds in Windows 7 and 6 seconds in Windows 8). You can then force stop them or wait for them to respond. But if you have many services running, then 12 seconds for each service is much time to wait for.




So to decrease that time we have a simple trick that can decrease this time and hence decrease the shutdown time. The trick is simple, you just need to edit a registry entry that is responsible for the waiting time.
CAUTION You need to edit the registry, do this only if you have the knowledge of editing the Windows Registry.

How To Decrease the Shutdown Time in Windows :
1. Open the “Run” dialog box either from the “Start” menu, or by pressing the “Windows Key + R”, and then type “regedit” in the window that pops-up.

2. Now you need to navigate to “HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control”. Now when you click on “Control”, look in the right pane and find the key named “WaitToKillServiceTimeout“. Double click on it and change its value to 2000.

Repairing Windows XP in Eight Commands

Windows could not start because the following file is missing or corrupt:

\\WINDOWS\\SYSTEM32\\CONFIG\\SYSTEM

You can attempt to repair this file by starting Windows Setup
using the original Setup CD-ROM.

Select ‘R’ at the first screen to start repair.

Which renders your PC inaccessible from the standard boot procedures of Windows XP. You try safe mode, to no avail. You’re particularly savvy and try issuing the FIXBOOT and FIXMBR commands in the Windows recovery console, but after each reboot, you’re merely greeted with the same obnoxious and terrifying blue screen of death that’s preventing you from accessing your precious data.

Perhaps you’ve also seen these error screens:

Windows NT could not start because the below file is missing or corrupt:

X:\\WINNT\\System32\\Ntoskrnl.exe
_________________

Windows NT could not start because the below file is missing or corrupt:

X:\\WINNT\\System32\\HAL.dll
_________________

NTLDR is Missing
Press any key to restart
_________________

Invalid boot.ini
Press any key to restart


Allow me to build tension by prefacing the end-all/be-all solution with my background: Having worked for the now-incorporated Geek Squad branch of Best Buy Corporation for the better part of eight months, I have seen dozens upon dozens of systems come through our department with any one of these errors, brought in by customers who are afraid they did something, have a virus, or are in jeopardy of losing their data. Prior to my discovery of an invaluable sequence of commands, our standard procedure was to hook the afflicted drive to an external enclosure, back up a customer’s data and then restore the PC with the customer’s restore discs or an identical copy of Windows with the customer’s OEM license key. If the customer wasn’t keen on the applicable charges for the data backup, we informed them of the potential risks for a Windows repair installation (Let’s face it, they don’t always work right), had them sign a waiver, and we did our best.

Neither of these procedures are cheap in the realm of commercial PC repair, nor do they inspire a tremendous level of confidence in the technician or the hopeful client.

In an effort to expedite our repair time and retain the sanity of myself and other technicians, I received permission to undertake a case study on a variety of PCs currently in service that exhibited any of the aforementioned symptoms, and I took it upon myself to find a better solution. After crawling through the MSKB, Experts Exchange, MSDN and sundry websites all extolling the virtues of a solution to these problems, I only found one that worked, and it has been reliably serving me for the better part of two weeks on seventeen PCs to date. The process is simple: Get to the Windows Recovery Console for your particular Windows installation, navigate to the root letter of your installation (C: in most cases), issue eight commands, and reboot. The cornerstone of this process is a command called “BOOTCFG /Rebuild” which is a complete diagnostic of the operating system loaded into the recovery console; the purpose of the command is to remove/replace/repair any system files that were preventing the operating system from loading correctly. Amongst the files it fixes are:

Windows Hardware Abstraction Layer (HAL)
Corrupt registry hives (\\WINDOWS\\SYSTEM32\\CONFIG\\xxxxxx)
Invalid BOOT.INI files
A corrupt NTOSKRNL.EXE
A missing NT Loader (NTLDR)
The command process may apply to other types of blue screens or Hive/HAL/INI/EXE/DLL-related stop errors, but I have not had the luxury of computers in this type of disrepair. The process I am about to outline is virtually harmless, and if you feel you may be able to correct your PC’s boot-time blue screens and stop errors with the sequence, feel free to try. Let us now begin with a step-by-step instruction for correcting these issues.

GETTING TO THE WINDOWS RECOVERY CONSOLE
Insert your Windows XP CD into your CD and assure that your CD-ROM drive is capable of booting the CD. Configuring your computer to boot from CD is outside of the scope of this document, but if you are having trouble, consult Google for assistance.
Once you have booted from CD, do not select the option that states: “Press F2 to initiate the Automated System Recovery (ASR) tool.” You’re going to proceed until you see the following screen, at which point you will press the “R” key to enter the recovery console:

After you have selected the appropriate option from step two, you will be prompted to select a valid Windows installation (Typically number “1″). Select the installation number, (As mentioned, “1″ in most cases), and hit enter. If there is an administrator password for the administrator account, enter it and hit enter. You will be greeted with this screen, which indicates a recovery console at the ready:

PROCEEDING WITH THE REPAIR FUNCTIONS
There are eight commands you must enter in sequence to repair any of the issues I noted in the opening of this guide. I will introduce them here, and then show the results graphically in the next six steps. These commands are as follows:
C: CD ..
C: ATTRIB -H C:\\boot.ini
C:ATTRIB -S C:\\boot.ini
C:ATRIB -R C:\\boot.ini
C: del boot.ini
C: BOOTCFG /Rebuild
C: CHKDSK /R /F
C: FIXBOOT
To “Go up a directory” in computing is to revert back to the directory above the current folder you’re operating in. If, for example, I’m in the C:WINDOWSSYSTEM32 directory, and I want to get at a file in the WINDOWS directory, I would merely type CD .. and I would be taken out of the SYSTEM32 folder and up one level to WINDOWS. We’re going to do the same thing here from the WINDOWS folder to get to the basic root of C:

Now that we are at C: we can begin the process of repairing the operating system
and that begins with modifying the attributes of the BOOT.INI file. Briefly, BOOT.INI controls what operating systems the Windows boot process can see, how to load them, and where they’re located on your disk. We’re going to make sure the file is no longer hidden from our prying eyes, remove the flag that sets it as an undeletable system file, and remove the flag that sets it as a file we can only read, but not write to. To do this, we will issue three commands in this step:

C:ATTRIB -H C:\\BOOT.INI
C:ATTRIB -R C:\\BOOT.INI
C:ATTRIB -S C:\\BOOT.INI
to remove the Hidden, System and Read Only flags.

Now that we’ve modified the attributes for the BOOT.INI file, it’s up for deletion. The syntax for it is simple: { DEL | FILE NAME }, e.g., C:DEL BOOT.INI deletes the BOOT.INI file.

Now for the most important step of our process, the BOOTCFG /REBUILD command which searches for pre-existing installations of Windows XP and rebuilds sundry essential components of the Windows operating system, recompiles the BOOT.INI file and corrects a litany of common Windows errors. It is very important that you do one or both of the following two things: First, every Windows XP owner must use /FASTDETECT as an OS Load Option when the rebuild process is finalizing. Secondly, if you are the owner of a CPU featuring Intel’s XD or AMD’s NX buffer overflow protection, you must also use /NOEXECUTE=OPTIN as an OS Load Option. I will demonstrate both commands for the purpose of this guide, but do not set NOEXECUTE as a load option if you do not own one of these CPUs. For the “Enter Load Identifier” portion of this command, you should enter the name of the operating system you have installed. If, for example, you are using Windows XP Home, you could type “Microsoft Windows XP Home Edition” for the identifier. This gives the process some authenticity, if you’re keen on being a perfectionist.

This step verifies the integrity of the hard drive containing the Windows XP installation. While this step is not an essential function in our process, it’s still good to be sure that the drive is physically capable of running windows, in that it contains no bad sectors or other corruptions that might be the culprit. No screenshot necessary here! Just type CHKDSK /R /F at the C:> prompt. Let it proceed; it could take in excess of 30 minutes on slower computers, when this is finished move on to the seventh and final step.

This last step also requires no screenshot. When you are at the C:> prompt,
simply type FIXBOOT. This writes a new boot sector to the hard drive and cleans up all the loose ends we created by rebuilding the BOOT.INI file and the system files. When the Windows Recovery Console asks you if you are “Sure you want to write a new bootsector to the partition C: ?” just hit “Y,” then enter to confirm your decision.

RESULTS AND WRAP-UP
It’s time to reboot your PC by typing EXIT in the Windows Recovery Console and confirming the command with a stroke of the enter key. With any luck, your PC will boot successfully into Windows XP as if your various DLL, Hive, EXE and NTLDR errors never existed. You’ve just saved yourself from many hours of work, frustration, potential data loss and shelling out your hard-earned greenbacks at a brick’n'mortar operation.

How to Compress your videos 50% without losing quality

many people ask me to compress their  video  so here is what you need

Most of the time when we compress any video file we loos the quality of video.

Today i am going to show how easily you can compress videos 50% without losing quality.

Download and Install Handbrake software.

Select your Source videos and choose the output destination folder. and click on the start

How to See if Your Hard Drive is Dying

Hard drives use S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) to gauge their own reliability and determine if they’re failing.  You can view your hard drive’s S.M.A.R.T. data and see if it has started to develop problems.

Unfortunately, Windows doesn’t have an easy-to-use built-in tool that shows your hard disk’s S.M.A.R.T. data.  We will need a third-party tool to view this information, though there is a way to check your S.M.A.R.T. status from the command prompt.

Mehtod 1 :- use HDDScan freeware utility, it will give you full report of your hard-disk status.

 Download 

Method 2 :- In the Command prompt (Run > cmd) type the following command

Wmic

"Diskdrive get status"

Get the complete Domain Report of any Website

If you want to Find out the information of Registered domain information of any site, Registered Owner name , Hosting company name , Domain creation date , Domain Expiration date, IP-address information & Raw domain information.


You will easily get all the information with DomainHostingView Tool

Suppose you want to get the full information of facebook.com, just enter the website name.

 

 DOWNLOAD

NetBIOS hack in windows OS

NetBIOS stands for Network Basic Input Output System. It allows your LAN or WAN to share drives, folders, files and printers. Gaining access to a computer through NetBIOS is very simple and easy. The only thing required is for the target machine to have file and printer sharing enabled and to have port 139 open. Below I will show you an example of what a hacker would do to gain access to a Windows machine through NetBIOS.


1. First the hacker would search for a target. A common tool used by hackers is Angry IP Scanner . Download and install it. (you can use any software you want to but i recommended this)
  
2. Next the hacker would insert the IP range he would like to scan. If the hacker was connected to a WLAN (Wireless Local Area Network) he would scan the local computers like I have shown below.

3. Since the hacker’s goal is to gain access to a system through NetBIOS, which runs on port 139, he will choose to scan each found host for that port. Click the downward arrow on the right and check the Scan ports box. A popup will come up asking you if you would like to select a new port. Click YES. 

4. Type in the port number 139 into the first box and click OK.

5. Click start. The program will begin scanning and when it’s complete a box with the results will come up.

6. As you can see 224 Ips were scanned. Out of those only one was alive and luckily it has port 139 open.

7. Open the Command Prompt by going to Start -> Run -> Type in cmd -> <ENTER> .

8. Now the hacker would run the “nbtstat –a TargetIPaddress” this will tell us if the target has file and printing enabled. Without it, this attack is not possible.

9. In the above image DAVIDS-MACHINE is the name of the target computer. If you look to the right of it you will see the number <20>. This means that file and printer sharing is enabled. If there was no <20> then you could not go any further and would have to find a new target.

10. Next the hacker would run the command “net view \\TargetIPaddress”. This command will display any shared drives, folders, files or printers. If nothing comes up, you won’t be able to gain access to anything since there is nothing being shared. In my case, I got the following:

11. In my example, I have two printers shared and one disk named SharedDocs. The hacker would be able to take control of my printers and view everything in my SharedDocs disk.

12. To gain access to my SharedDocs disk, the hacker would have to map out the drive onto his computer. If successful, the hacker will have all the contents of my drive on his computer.

13. To map out my drive onto his computer the hacker would use the command “net use G: \\TargetIPaddress\DriveName”. So in my case I would run the command “net use G:\\192.168.1.101\SharedDocs”. You can use any letter in place of G:\\. This just tells the computer what to name the drive on your computer.

14. What’s this? Looks like I already have a drive G. To avoid this problem, go to My Computer where it will show all of your current Drives. To fix this simply change the letter G to a nonexistent drive letter.

15. Once the command is completed successfully, go to My Computer and you should see a new drive under Network Drives. Double clicking it brings up all of the targets documents

note: if you don't want to let this happen then  protect your shared folder and dont share printer and other device

How to configure/use ProRat Trojan to hack someone's PC (Free download and instructions)

How to configure/use ProRat Trojan to hack someone's PC (Free download and instructions) 

 

• It can connect to the server more faster.
• It has more features/functions to play with your victim's PC.
• Easy to configure.

Lets start the Tutorial:

• Download ProRat and extract anywhere in your PC.
• Now run ProRat.exe and then click on Create- Create ProRat Server (342 Kbayt)

• From the Notifications tab, in the first option "Use ProConnective Notification" type your IP address. (If you don't know your IP address, simply click on the red arrow and it will automatically fill your IP address).
• Now in the second option "Use Mail Notifications" type your Email address where you want to receive notification when the server is installed on your victim's PC.

 

• In the General Settings Tab, leave as it is but don't forget to remember the password. You will be required to enter the password at the time of connection. 
• Now come to the Bind with File tab. Mark the box "Bind server with a file" and then click on Select File. Now select any file you want to bind with the server.(Binding means combining two files into one)
• You can also change the extension of the server if you want by going to the Server Extensions tab.
• Now click on Server Icon tab and select an icon for the bind files. Choose the icon wisely. If your have bind the server with some program, then select the setup icon or if your have bind the server with an image file, than select an image icon.
• Finally click on Create Server.

Now the server will be created in your current directory (the extracted folder). Send or give the server to your victim and once your victim runs the bind file in his PC, the server will be installed silently on your victim's PC. After the server is installed on your victim's PC, the server will send you an email on your given email ID to confirm you that it's been installed successfully on the victim's PC. After getting the email, run ProRat again, then click onProConnective and then click on Start to list the ProConnective connections. After then, a new window will open which will show you weather your victim is online on not.

How to create a Super Hidden folder using command prompt

How to create a Super Hidden folder using command prompt