How To Make A Bootable Usb For Windows 8

Hope My All Fans Are Fine.Many Person Want To How To Make A Bootable Usb Or Flash Drive,How to Create Bootable Windows 8 USB,How To Create Bootable Windows 7 UsbDrive From Iso Image.This Topic Uploaded Byfullypcgames.blogpsot.com Now I Am Share This Topic WithEasy Method.

Just You Have Need 3 Items.

1)   1st 4gb Flash Drive.... 
2)   Software For Make Bootable Usb... DownloadPassword=fullypcgames.blogspot.com
3)   Download Window 8 Or Window 7 Its Your Choice....Window 7,Window 8

Follow Steps 

1) plug 4gb usb, 4gb minimum Size 

2)Run Software You have already downloaded This 

3)Step 2 click browse and select Iso file and click next.

4)Choose Usb to make bootable usb .

5)Now select usb drive and click begin copying.

6)wait a moment for complete progress.

7)After That Your bootable usb Done !

Enjoy.Post comments Below post And  Share With YourFriends Thanks.

Process Screen Shot!

How can I break the memory card password on my Mobiles

The use of memory cards is increasing day-by-day, flash memory being one of the most crucial. Micro SD Cards</gras> are compact space saving memory devices which can create a headache if their password is lost. This article will discuss the way to find out the memory card's passwordquickly. When the password to a Micro SD Card</gras> gets lost, the card is blocked and none of the information inside it can be accessed. Interfacing your computer and the mobile via Bluetooth can restore and reset the password. Infrared can also be used to regain access to the files. 

This article tells you how to recover a a micro SD card password and micro SD card password reset. 
This document deals with the issue of losing a password for a MICRO SD card. If the password for the card is lost then it will be blocked for further use.www.fullypcgames.blogspot.com In such a situation, the user can interface their mobile with the PC using Bluetooth or Infrared, make the changes then find the password in the file created thereafter. 

Issue

I have lost the password for my 1GB micro SD card and now it is blocked. 

Solutions

Solution one:

• Go to file manager on your mobile
• In Settings choose system folders,
• In the System folder, find a file called mmcstore
• Send the file to your PC using IR/Bluetooth
• Open the file in Notepad
• The password you need for your memory card is located within that file

Solution two:

1. Insert your card into your phone, without accessing it through the phone 

2. Run FExplorer and Open the path C:\system 

3. Find the file called mmcstore, and rename it mmcstore.txt 

4. Copy that file (mmcstore.txt) to your PC and open it in Notepad 

5. Your password will be located within that file. 
6. Download FExplorer
For Micro SD : - 

Put the card in any E series mobile or N95 etc and format it. It will not ask for a password. 

Cisco Discovery Protocol For Windows

UPDATE: Checkout and download my CDP client for Windows over on github

 Lets face it.  We have all been there; "where does this network cable / uplink / port go?"

Until now, it has been a matter of looking up cable numbers in databases, fiddling about in the back of server and network racks or worst case - sending the smallest guy down to play hunchback in the windy air conditioned gloom under the floor.

There must be a better way to tell where a network cable goes to without having to go to all that trouble every time...

Well there is.  It's called Cisco Discovery Protocol (CDP).  From Wikipedia:

The Cisco Discovery Protocol (CDP) is a proprietary Data Link Layer network protocol developed by Cisco Systems that is implemented in most Cisco networking equipment and is used to share information about other directly connected Cisco equipment, such as the operating system version and IP address.

In other words, CDP packets will give you a lot of valuable information if you can capture them. They will give you all the details of the Cisco switch your on and the port on that switch you're connected to.  Of course as CDP is proprietary, you typically won't find it anywhere else other than on Cisco networking kit.

However, VMware knew all about this "trace the cable game" when they where putting together ESX and ESXi v3.5.  VMware's solution was to build in support for CDP on all physical network interfaces of the ESX Hypervisor:

VMware CDP in action

Well, this was a revelation!  For the first time us server techies can check up on the networks techies.  Not only could we tell instantly where a network cable was plugged in, we could tell them if it was in the wrong place too! [bwah ha haaa - rubs hands in a maniacal way!]

Of course this is OK for VMware Hypervisors and Linux based servers / desktops but what about Windows servers / desktops?

Capturing CDP is tough in Windows: CDPR will do it, as will Wireshark, but both require WinPcapto be installed.  This isn't really practical as potentially I want to find CDP data without installing any additional software or rebooting the host (WinPcap requires a reboot).

The Solution - TCPDump
I've found a version of TCPDump for Windows that was built on the WinPCap SDK; this means this little 500k utility can capture CDP packets on a machine without any additional tools.  What's more, as it's shipped as single command line .exe file, it's portable meaning it can be run from a USB stick, a batchfile, etc.  

You can get this updated version of TCPDump from micoOLAP

Using TCPDump
Quite simple, but don't be put off by the plethora of switches.

Firstly you need to find the interface number of the network adaptor you are trying to find CDP data for.  Use this command:

tcpdump -D

This will provide you information similar to this:

TCPDump Listing Interfaces

I'm interested in capturing data from my HP NC7782 Gigabit Adaptor; interface 2.

So lets run the command and capture some CDP data!  Here is the command:

tcpdump -i 2 -nn -v -s 1500 -c 1 ether[20:2] == 0x2000

Breaking this down:

• -i 2 = interface 2
• -nn = not resolving dns or port numbers
• -v = verbose mode
• -s 1500 = snagging up to 1500 bytes of the CDP packet
• -c 1 = capture one packet before exiting 
• ether[20:2] == 0x2000 = checking bytes 20 and 21 from the start of the ethernet header for a value of 2000 (hex)

Phew! I feel a batch file coming on, because I'm never going to remember all of that!

Here is what output looks like:

CDP Data in Windows!

Excellent.

Oh and by the way, tell the apprentice he can come out from under the computer room floor now, we know where these cables go.

*** UPDATE: 4 May 2010 ***
Here is the batch file I use to list adaptors, prompt for adaptor number and then run tcpdump on that adaptor:

@echo off
tcpdump -D
echo.
echo.
echo.
Set /P adaptor=Please Enter Adaptor Number to Listen on: 
tcpdump -i %adaptor% -nn -v -s 1500 -c 1 ether[20:2] == 0x2000
pause

Windows 7: Fix Wireless Trouble

With the proliferation of wireless networks, it is becoming more and more likely that if you live in upwards of a fairly well a populated area, you are going to have problems with your wireless LAN.

Problems that are likely to include random wireless drops, undetectable or uncontactable wireless networks, data throughput problems, etc etc.

The question is - what can be done to try and get to the bottom of these problems?

Perhaps the best place to start is to run a single command line tool to find out as much information as we can about:

• Wireless adapter model
• Adapter card driver details
• Configured wireless LAN profile(s)
• Full details of wireless networks currently visible

As you can see, quite a lot of information from a single command!

Historically to get this level of information, you would need to look in several places (device manager, wireless networking info) and install 3rd party applications such as NetStumbler etc.

OK, so how do you get all this info from the single command?  Easy peasy.

1. Click Start (aka Windows Orb) and enter cmd into the text box and hit enter to open a command prompt
2. Into the command prompt window, enter the command:

netsh wlan show all >wireless.txt

3. This will run the command and pipe the output of the command into the file wireless.txt for easy reading
4. Still in the command prompt window, run

notepad wireless.txt

5. This will open the output from the "netsh wlan show all" command in notepad

With a bit of luck, you should now be looking at something that looks a bit like this: 

=======================================================================
============================== SHOW DRIVERS ===========================
=======================================================================
Interface name: Wireless Network Connection

    Driver                    : Intel(R) PRO/Wireless 2200BG Network Connection
    Vendor                    : Intel Corporation
    Provider                  : Intel
    Date                      : Wed 19/12/2007
    Version                   : 9.0.4.39
    INF file                  : C:\Windows\INF\oem1.inf
    Files                     : 3 total
                                C:\Windows\system32\DRIVERS\w29n51.sys
                                C:\Windows\system32\Netw2c32.dll
                                C:\Windows\system32\Netw2r32.dll
    Type                      : Legacy Wi-Fi Driver
    Radio types supported     : 802.11g 802.11b
    FIPS 140-2 mode supported : No
    Hosted network supported  : No
    Authentication and cipher supported in infrastructure mode:
                                Open            None
                                Open            WEP
                                Shared          None
                                Shared          WEP
                                WPA-Enterprise  TKIP
                                WPA-Enterprise  CCMP
                                WPA-Personal    TKIP
                                WPA-Personal    CCMP
                                WPA2-Enterprise TKIP
                                WPA2-Enterprise CCMP
                                WPA2-Personal   TKIP
                                WPA2-Personal   CCMP
    Authentication and cipher supported in ad-hoc mode:
                                Open            WEP
                                Shared          WEP
                                Open            None
                                Shared          None
======================================================================= 
============================= SHOW INTERFACES ========================= 
=======================================================================

etc etc etc!

Troubleshooting:

Channels in "SHOW NETWORKS MODE=BSSID" section 
Find your wireless LAN and compare this to the channel details of the other wireless networks detailed in the results file.  If your wireless network is using the same channel as someone else's then change your wireless access point or router to use a different wireless channel.   

Signal strength in "SHOW NETWORKS MODE=BSSID" section 
Yes I know the Windows 7 GUI gives you signal strength (and that's about all), but this method is more accurate.  Is the strength any good?  With a higher signal strength, is the wireless connection more stable? 

These two are the most likely culprits when it comes to unstable wireless connections.

Some more advance troubleshooting includes: 

Driver in "SHOW DRIVERS" section
In my case:

    Driver                    : Intel(R) PRO/Wireless 2200BG Network Connection
    Vendor                    : Intel Corporation
    Provider                  : Intel
    Date                      : Wed 19/12/2007
    Version                   : 9.0.4.39

Armed with this info, I can hit Intel's website and see if there is a newer version driver available and update.

Alternatively, I could go to the Windows Update Catalogue and search for MS approved driver updates or hotfixes.  See here for how to use the catalogue.

Basic Rate and Other Rate in "SHOW NETWORKS MODE=BSSID" section
Try configuring your wireless card via device manager to run at one of the basic rates listed.  Does this make any difference?  Trial and error to see how fast you can go whilst remaining stable.

Conclusion
As we have seen, by running one simple command you can grab all sorts of valuable wireless information and  have a real good stab at fixing wireless networking woes.

If all else fails, then there is always Ethernet over power!

Location via Wi-Fi MAC Address

With all the iPhone tracking claims and counter claims, (seehere for details) it appears that Google have been silently collecting and building a publicly accessible Wireless router location database via their Streetview camera cars and virtually all Android devices.

And now you too can interrogate that database to find any wireless router in the world!  All you need is the MAC address of the wireless router in question.

Have a look at http://samy.pl/androidmap/

When the phone detects any wireless network, encrypted or otherwise, it sends the BSSID (MAC address) of the router along with signal strength, and most importantly, GPS coordinates up to the mothership. This page allows you to ping that database and find exactly where any wi-fi router in the world is located.

For furter reading on what a MAC address is have a look here


Finding your Wireless Router's MAC Address
Following assumes that you are wirelessly connected to the router you wish to find the MAC address of.

Windows (any current version)
Open a command prompt and enter the following command:

ipconfig

The return should look something like this:

IP Address. . . . . . . . . . . . : xxx.xxx.xxx.xxx
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : yyy.yyy.yyy.yyy

Taking the default gateway IP address, plumb it into the following command (obviously you will have numbers rather than y's):

 arp -g yyy.yyy.yyy.yyy

The return should look something like this:

  Internet Address      Physical Address
  yyy.yyy.yyy.yyy       zz-zz-zz-zz-zz-zz

Copy and paste the physical address (again you should have alphanumerics rather than just z's) into http://samy.pl/androidmap/ and hit probe.

Linux 
Open a terminal session and enter the following command:

route -n

The return should look something like this: 

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         yyy.yyy.yyy.yyy    0.0.0.0         UG    0      0        0 wlan0

Taking the default gateway IP address, plumb it into the following command (again, you will have numbers rather than y's):

 arp -vn yyy.yyy.yyy.yyy

The return should look something like this:

Address              HWtype  HWaddress
yyy.yyy.yyy.yyy      ether   zz:zz:zz:zz:zz:zz

Copy and paste the HWaddress (again you should have alphanumerics rather than just z's) intohttp://samy.pl/androidmap/ and hit probe.

====

Oh look Google know where you are... again.

Thanks goto @samykamkar for making android map available.

Adding VLANs to Cisco Nexus 1000v

Having scoured the internet and drawing a blank when looking  for a simple process to follow when adding a VLAN and subsequent VMware VM access port group and to a Cisco Nexus 1000v switch, I ended up stitching together the Cisco commands after reading lots and lots of Cisco Nexus configuration guides.

The annoyance is that whilst you can monitor the configuration of your Nexus 1000v through VMware Virtual Center, you cannot configure it.  All Nexus 1000v configuration must be done at the command line. 

In this post I present to you the configuration commands I use when adding an additional VLAN to a Nexus 1000v switch.

First off - What is a Cisco Nexus 1000v?

Well if you have a spare 5 minutes and 17 seconds, have a watch of the following:

If not, put simply a Nexus 1000v replaces / augments a standard VMware distributed switch as shown below:

A single Nexus 1000v consists of a minimum of 2 modules:

VEM = Virtual Ethernet Module - Installed on the ESXi host itself
VSM = Virtual Supervisor Module - The 1000v management VM

Setting up a Nexus 1000v

Have a read of Kendrick Coleman's excellent guide here: Standing Up The Cisco Nexus 1000v In Less Than 10 Minutes

Of course, if you were setting your Nexus 1000v from scratch, you would know which VLANs to add 'right off the bat', so would have no need to add additional VLANs.

However as we all know change happens.

Adding VLANs to Cisco Nexus 1000v

Yes, I'm not a network administrator, however these commands work for me.  They should work for you too.

Create a VLAN and name it correctly:

First step is to create a VLAN and give it a name.  I like to name my VLANs in line with their VMware port group name.  Here I'm creating VLAN 456 and calling it "VM_Prod_VL456":

     conf t
     vlan 456
     name VM_Prod_VL456
     end

Create a VMware Access Port Group and give it a friendly name

Next step is to create the VMware port group as it would appear in Virtual Center Networking.  Here I'm calling my VMware port group "VM_Prod_VL456" and hooking it to my VLAN 456.  I'm also going to give my "VM_Prod_VL456" port group 512 access ports to plug my VMs into:

     conf t
     port-profile type vethernet VM_Prod_VL456
     vmware port-group
     switchport mode access
     switchport access vlan 456
     vmware max-ports 512
     no shutdown
     state enabled
     end

Add VLAN to the trunk port group

Final step is to allow the newly crated VLAN 456 access to the rest of the network via the ESXi physical network cards.  Sometimes referred to as the Nexus 1000v trunk ports.  In my example, these ports are called  "SYSTEM-UPLINK".  I'm also going to save my configuration via "copy run start":

     conf t
     port-profile SYSTEM-UPLINK
     switchport trunk allowed vlan add 456
     end
     copy run start

Job done.  Time to start creating some VM's and hooking them into my newly created "VM_Prod_VL456" port group.