Showing posts with label cmd. Show all posts
Showing posts with label cmd. Show all posts

Tuesday 26 July 2016

How to Create You Lab on Kali Linux - Using VMware or VBox

Before you start - Here are something that you need to consider..

  • Install VirtualBox or Vmware
  • Install LiveCD in VirtualBox or Vmware
  • Boot and try out your LiveCD

Introduction.


There are lots of tutorials available on the internet related to hacking but the big problem lies in testing your theoretical skills. Unless you don't have practical exposure to hacking, you cannot really understand the strength of it. The technique I will discuss here will be advantageous for those who have only single system and want to set up a testing network using it. In case you have multiple systems then you can easily test for your skills by making one system as target and other as attacker.
VMware Workstation 12 Pro - Leading Edge PC Virtualization VMware Workstation 12 Pro


Download VMware Workstation or Player

The best way to practice hacking is within a virtual environment. Essentially, you set up a hacking system, such as Kali Linux, and some victims to exploit. Ideally, you would want multiple operating systems (Windows XP, Vista, 7, and 8, as well as a Linux flavor) and applications so that you can try out a variety of hacks.

Virtual machines and a virtual network are the best and safest way to set up a hacking lab. There are several virtualization systems out there, including Citrix, Oracle's VirtualBox, KVM, Microsoft's Virtual PC and Hyper-V, and VMware'sWorkstation, VMware Player and ESXi. For a laboratory environment, I strongly recommend VMware's Workstation or Player. Workstation is commercial product that costs under $200, while Player is free. You can also get a free 30-day trial of Workstation.

Player is limited to just playing VMs , while Workstation can both create and play VMs. Let's download VMware's Workstation or Player here.


Then - For you Images you can download a pre-built image. As it will allow you to save some time, you don't need to build the image from scratch. Here is a link for you to download several Linux pre-built Linux Images on SourceForge.

I don't encourage you to download pre-built Windows VM from anywhere, for the single fact that Microsoft itself provides you with pre-built Windows VM for you to use on your VM Lab. Again I did the research for you and here it the link for you to download the Windows of your choice,  Obs: Remember Windows only allow you to use those VM images for 30 days. Please, READ Microsoft TERMS AND CONDITIONS before you use their software here is the url for you.



Keep posted - This tutorial continues on Part 2

Also check this Handful tutorials I have found online:

Checkout our tutorial videos below. Learn more about.
  1. OWASP AppSec Basics: http://www.youtube.com/watch?v=CDbWvEwBBxo
  2. OWASP SQL Injection: http://www.youtube.com/watch?v=pypTYPaU7mM
  3. OWASP Cross Site Scripting: http://www.youtube.com/watch?v=_Z9RQSnf8-g
  4. OWASP Strict Transport Security: http://www.youtube.com/watch?v=zEV3HOuM_Vw

Tuesday 23 December 2014

Some Things I've learnt about GNS3

I am in no way an expert on GNS3, just a trainee   below are a few things i have learnt lately. I thought it might be a good idea to produce something like this. If everyone replied to it and added a few tips of their own it could be turned into a CLN GNS3 tips and tricks document.


GNS3 Web Sites
http://www.gns3.net GNS3’s primary Web site
http://wiki.gns3.net GNS3’s Wiki site
http://www.ipflow.utc.fr/index.php/Cisco_7200_Simulator Dynamips – the actual emulator

http://www.ipflow.utc.fr/blog/ Dynamips blog
http://dyna-gen.sourceforge.net/ Dynagen
http://www.ipflow.utc.fr/bts/ Dynamips/Dynagen bug tracking
http://7200emu.hacki.at Hacki’s forum
===

1. GNS3 has less chance of crashing if the bin files are unzipped.

2. Currently images for 2600 routers must be uncompressed to work with Dynamips.

3. To dramatically reduce the load on your processor, right click on the router and choose idle, after a few moments it will give you a list to choose from.
Choose the one with a * against it, if you don't see a * in the choice run it again.

4. If you don't need any special routers then use the same type on the whole lab, this will use far less processing power and memory.

5. To print out the diagram of your network click file then export, you can export all or just what is visible.

6. To move your router/routers/links etc click the left mouse button and draw around what you want to move, you can then move everything that is inside that shape.

7. I find that if you move around the interface identities they eventually go back to their original position. I don't move them anymore as it looks a bit
messy when that happens.

8. You can't use GNS3 for the SWITCH studies, GNS3 only has basic switch capabilities.

9. You can create computers and run ping's/telnet with VPC, the document attached shows you how, its very simple to follow. I did find that it takes a few times for it to accept being a cloud, once you click ok just open it back up and check it.

10. I personally find that it is best to connect your links between routers when they are switched off, sometimes i find it fails otherwise.

11. You can create a router to act like a pc, this is shown below but it is also in the document.


Router(config)# no ip routing         Turns off IP routing function
Router(config)# interface fa0/0      Switches to FastEthernet interface
Router(config-if)# ip address address subnet_mask Assigns IP address and subnet mask to interface
Router(config-if)# no shutdown      Turns interface on
Router(config-if)# exit                     Returns to global configuration mode
Router(config)# ip default-gateway gateway_address Configures the default gateway
Router(config)# ip http server         Optional – starts http server process
===

12. You can connect GNS3 to real equipment, i have not done this yet myself, it is in the document attached how to do this.

13. When using windows 64 bit GNS3 will default to program files (x86). GNS3 is a 32 bit program for windows so point it to program files not the (x86).

14. I have a Lenovo Thinkpad with a i7 processor and 4GB of RAM. With 7 routers of the same type my processor is running between 8 and 15 %, my RAM consumption is around 2.3 to 2.8 GB. That is also using a few other programs on my laptop at the sometimes.

Tuesday 10 September 2013

Linux Containers on Virtualbox - Disposal Boxes by Michal Migurski's

Hey look, a month went by and I stopped blogging because I have a new job. Great.
One of my responsibilities is keeping an eye on our sprawling Github account, currently at 326 repositories and 151 members. The current fellows are working on a huge number of projects and I frequently need to be able to quickly install, test and run projects with a weirdly-large variety of backend and server technologies. So, it’s become incredibly important to me to be able to rapidly spin up disposable Linux web servers to test with. Seth clued me in to Linux Containers (LXC) for this:
LXC provides operating system-level virtualization not via a full blown virtual machine, but rather provides a virtual environment that has its own process and network space. LXC relies on the Linux kernel cgroups functionality that became available in version 2.6.24, developed as part of LXC. … It is used by Heroku to provide separation between their “dynos.”
I use a Mac, so I’m running these under Virtualbox. I move around between a number of different networks, so each server container had to have a no-hassle network connection. I’m also impatient, so I really needed to be able to clone these in seconds and have them ready to use.
This is a guide for creating an Ubuntu Linux virtual machine under Virtualbox to host individual containers with simple two-way network connectivity. You’ll be able to clone a container with a single command, and connect to it using a simple <container>.local host name.

The Linux Host

First, download an Ubuntu ISO. I try to stick to the long-term support releases, so I’m using Ubuntu 12.04 here. Get a copy of Virtualbox, also free.
Create a new Virtualbox virtual machine to boot from the Ubuntu installation ISO. For a root volume, I selected the VDI format with a size of 32GB. The disk image will expand as it’s allocated, so it won’t take up all that space right away. I manually created three partitions on the volume:
  1. 4.0 GB ext4 primary.
  2. 512 MB swap, matching RAM size. Could use more.
  3. All remaining space btrfs, mounted at /var/lib/lxc.
Btrfs (B-tree file system, pronounced “Butter F S”, “Butterfuss”, “Better F S”, or “B-tree F S") is a GPL-licensed experimental copy-on-write file system. It will allow our cloned containers to occupy only as much disk space as is changed, which will decrease the overall file size of the virtual machine.
During the OS installation process, you’ll need to select a host name. I used “ubuntu-demo” for this demonstration.

Host Linux Networking

Boot into Linux. I started by installing some basics, for me: git, vim, tcsh, screen, htop, and etckeeper.
Set up /etc/network/interfaces with two bridges for eth0 and eth1, both DHCP. Note that eth0 and eth1 must be commented-out, as in this sample part of my /etc/network/interfaces:
## The primary network interface
#auto eth0
#iface eth0 inet dhcp

auto br0
iface br0 inet dhcp
        dns-nameservers 8.8.8.8
        bridge_ports eth0
        bridge_fd 0
        bridge_maxwait 0

auto br1
iface br1 inet dhcp
        bridge_ports eth1
        bridge_fd 0
        bridge_maxwait 0
Back in Virtualbox preferencese, create a new network adapter and call it “vboxnet0”. My settings are 10.1.0.1, 255.255.255.0, with DHCP turned on.


Shut down the Linux host, and add the secondary interface in Virtual box. Choose host-only networking, the vboxnet0 adapter, and “Allow All” promiscuous mode so that the containers can see inbound network traffic.

The primary interface will be NAT by default, which will carry normal out-bound internet traffic.
  1. Adapter 1: NAT (default)
  2. Adapter 2: Host-Only vboxnet0
Start up the Linux host again, and you should now be able to ping the outside world.
% ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=63 time=340 ms
…
Use ifconfig to find your Linux IP address (mine is 10.1.0.2), and try ssh’ing to that address from your Mac command line with the username you chose during initial Ubuntu installation.
% ifconfig br1

br1       Link encap:Ethernet  HWaddr 08:00:27:94:df:ed  
          inet addr:10.1.0.2  Bcast:10.1.0.255  Mask:255.255.255.0
          inet6 addr: …
Next, we’ll set up Avahi to broadcast host names so we don’t need to remember DHCP-assigned IP addresses. On the Linux host, install avahi-daemon:
% apt-get install avahi-daemon
In the configuration file /etc/avahi/avahi-daemon.conf, change these lines to clarify that our host names need only work on the second, host-only network adapter:
allow-interfaces=br1,eth1
deny-interfaces=br0,eth0,lxcbr0
Then restart Avahi.
% sudo service avahi-daemon restart
Now, you should be able to ping and ssh to ubuntu-demo.local from within the virtual machine and your Mac command line.

No Guest Containers

So far, we have a Linux virtual machine with a reliable two-way network connection that’s resilient to external network failures, available via a meaningful host name, and with a slightly funny disk setup. You could stop here, skipping the LXC steps and use Virtualbox’s built-in cloning functionality or something like Vagrant to set up fresh development environments. I’m going to keep going and set up LXC.

Linux Guest Containers

Install LXC.
% sudo apt-get lxc
Initial LXC setup uses templates, and on Ubuntu there are several useful ones that come with the package. You can find them under /usr/lib/lxc/templates; I have templates for ubuntu, fedora, debian, opensuse, and other popular Linux distributions. To create a new container called “base” use lxc-create with a chosen template.
% sudo lxc-create -n base -t ubuntu
This takes a few minutes, because it needs retrieve a bunch of packages for a minimal Ubuntu system. You’ll see this message at some point:
##
# The default user is 'ubuntu' with password 'ubuntu'!
# Use the 'sudo' command to run tasks as root in the container.
##
Without starting the container, modify its network adapters to match the two we set up earlier. Edit the top of /var/lib/lxc/base/config to look something like this:
lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.network.hwaddr = 00:16:3e:c2:9d:71

lxc.network.type=veth
lxc.network.link=br1
lxc.network.flags=up
lxc.network.hwaddr = 00:16:3e:c2:9d:72
An initial MAC address will be randomly generated for you under lxc.network.hwaddr, just make sure that the second one is different.
Modify the container’s network interfaces by editing /var/lib/lxc/base/rootfs/etc/network/interfaces (/var/lib/lxc/base/rootfs is the root filesystem of the new container) to look like this:
auto eth0
iface eth0 inet dhcp
        dns-nameservers 8.8.8.8

auto eth1
iface eth1 inet dhcp
Now your container knows about two network adapters, and they have been bridged to the Linux host OS virtual machine NAT and host-only adapters. Start your new container:
% sudo lxc-start -n base
You’ll see a normal Linux login screen at first, use the default username and password “ubuntu” and “ubuntu” from above. The system starts out with minimal packages. Install a few so you can get around, and include language-pack-en so you don’t get a bunch of annoying character set warnings:
% sudo apt-get install language-pack-en
% sudo apt-get install git vim tcsh screen htop etckeeper
% sudo apt-get install avahi-daemon
Make a similar change to the /etc/avahi/avahi-daemon.conf as above:
allow-interfaces=eth1
deny-interfaces=eth0
Shut down to return to the Linux host OS.
% sudo shutdown -h now
Now, restart the container with all the above modifications, in daemon mode.
% sudo lxc-start -d -n base
After it’s started up, you should be able to ping and ssh to base.local from your Linux host OS and your Mac.
% ssh ubuntu@base.local

Cloning a Container

Finally, we will clone the base container. If you’re curious about the effects of Btrfs, check the overall disk usage of the /var/lib/lxc volume where the containers are stored:
% df -h /var/lib/lxc

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3        28G  572M   26G   3% /var/lib/lxc
Clone the base container to a new one, called “clone”.
% sudo lxc-clone  -o base -n clone
Look at the disk usage again, and you will see that it’s not grown by much.
% df -h /var/lib/lxc

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3        28G  573M   26G   3% /var/lib/lxc
If you actually look at the disk usage of the individual container directories, you’ll see that Btrfs is allowing 1.1GB of files to live in just 573MB of space, representing the repeating base files between the two containers.
% sudo du -sch /var/lib/lxc/*

560M /var/lib/lxc/base
560M /var/lib/lxc/clone
1.1G total
You can now start the new clone container, connect to it and begin making changes.
% sudo lxc-start -d -n clone
% ssh ubuntu@clone.local

Conclusion

I have been using this setup for the past few weeks, currently with a half-dozen containers that I use for a variety of jobs: testing TileStache, installing Rails applications with RVM, serving Postgres data, and checking out new packages. One drawback that I have encountered is that as the disk image grows, my nightly time machine backups grow considerably. The Mac host OS can only see the Linux disk image as a single file.
On the other hand, having ready access to a variety of local Linux environments has been a boon to my ability to quickly try out ideas. Special thanks again to Seth for helping me work through some of the networking ugliness.

Further Reading

Tao of Mac has an article on a similar, but slightly different Virtualbox and LXC setup. They don’t include the promiscuous mode setting for the second network adapter, which I think is why they advise using Avahi and port forwarding to connect to the machine. I believe my way here might be easier.
Shift describes a Vagrant and LXC setup that skips Avahi and uses a plain hostnames for internal connectivity.

The Owner of this post is Michal Migurski
Find is Blog here http://mike.teczno.com/notes/disposable-virtualbox-lxc-environments.html 

Thursday 11 July 2013

Solve VMWare Workstation 9 Error on Linux Kernel 3.8.0-26



I have VMware Workstations 9 installed on my uBuntu 13 machine and today without any apparent reason it stop working throwing me the following error, every time I've tried to boot up any VM machine.


To solver the problem .. here is what I have done ... created bash script to handle problems with VMware Player on 13.04 ...




  • #!/bin/bash
  • if [[ $UID != 0 ]]; then
  •     echo "Please run this script with sudo:"
  •     echo "sudo $0 $*"
  •     exit 1
  • fi
  • sudo ln -s /usr/src/linux-headers-$(uname -r)/include/generated/uapi/linux/version.h /usr/src/linux-headers-$(uname -r)/include/linux/version.h
  • cd /usr/lib/vmware/modules/source
  • sudo tar -xf vmci.tar
  • cd vmci-only
  • sudo sed '127s/.*/   .remove = vmci_remove_device,/' driver.c > driver.c.tmp
  • mv driver.c.tmp driver.c
  • sudo sed '1753s/.*/static int/' driver.c > driver.c.tmp
  • mv driver.c.tmp driver.c
  • sudo sed '1981s/.*/static void/' driver.c > driver.c.tmp
  • mv driver.c.tmp driver.c
  • cd ..
  • sudo tar -cf vmci.tar vmci-only/
  • sudo rm vmci-only/ -Rf
  • sudo vmware-modconfig --console --install-all
  • sudo rm /usr/src
  • Before write the script I've open the terminal and type " #sudo kate " then when kate opened I entered the script and saved on " /usr/src/open-vm-tools-xxxx.xx.xx" (replace the x with year month and day) and save it. Then close Kate

    The Open terminal again and do the following;


    after you should have VMware workstation running...



    This is another posting showing "how to do computing" for everyday computer usages... For a general public

    Wednesday 21 November 2012

    10 Reasons Why PCs Crash And You Must Know


    Fatal error: the system has become unstable or is busy," it says. "Enter to return to Windows or press Control-Alt-Delete to restart your computer. If you do this you will lose any unsaved information in all open applications."

    You have just been struck by the Blue Screen of Death. Anyone who uses Mcft Windows will be familiar with this. What can you do? More importantly, how can you prevent it happening?

    1 Hardware conflict

    The number one reason why Windows crashes is hardware conflict. Each hardware device communicates to other devices through an interrupt request channel (IRQ). These are supposed to be unique for each device.

    For example, a printer usually connects internally on IRQ 7. The keyboard usually uses IRQ 1 and the floppy disk drive IRQ 6. Each device will try to hog a single IRQ for itself.

    If there are a lot of devices, or if they are not installed properly, two of them may end up sharing the same IRQ number. When the user tries to use both devices at the same time, a crash can happen. The way to check if your computer has a hardware conflict is through the following route:

    * Start-Settings-Control Panel-System-Device Manager.

    Often if a device has a problem a yellow '!' appears next to its description in the Device Manager. Highlight Computer (in the Device Manager) and press Properties to see the IRQ numbers used by your computer. If the IRQ number appears twice, two devices may be using it.

    Sometimes you may have to find more recent drivers on the internet to make the device function properly. A good resource is www.driverguide.com. If the device is a soundcard, or a modem, it can often be fixed by moving it to a different slot on the motherboard (be careful about opening your computer, as you may void the warranty).

    When working inside a computer you should switch it off, unplug the mains lead and touch an unpainted metal surface to discharge any static electricity.

    To be fair to Mcft, the problem with IRQ numbers is not of its making. It is a legacy problem going back to the first PC designs using the IBM 8086 chip [this is quite hold article, I need to update some stuff here]. Initially there were only eight IRQs. Today there are 16 IRQs in a PC. It is easy to run out of them. There are plans to increase the number of IRQs in future designs.

    2 Bad Ram

    Ram (random-access memory) problems might bring on the blue screen of death with a message saying Fatal Exception Error. A fatal error indicates a serious hardware problem. Sometimes it may mean a part is damaged and will need replacing.

    But a fatal error caused by Ram might be caused by a mismatch of chips. For example, mixing 70-nanosecond (70ns) Ram with 60ns Ram will usually force the computer to run all the Ram at the slower speed. This will often crash the machine if the Ram is overworked.

    One way around this problem is to enter the BIOS settings and increase the wait state of the Ram. This can make it more stable. Another way to troubleshoot a suspected Ram problem is to rearrange the Ram chips on the motherboard, or take some of them out. Then try to repeat the circumstances that caused the crash. When handling Ram try not to touch the gold connections, as they can be easily damaged.

    Parity error messages also refer to Ram. Modern Ram chips are either parity (ECC) or non parity (non-ECC). It is best not to mix the two types, as this can be a cause of trouble.

    EMM386 error messages refer to memory problems but may not be connected to bad Ram. This may be due to free memory problems often linked to old Dos-based programmes.

    3 BIOS settings

    Every motherboard is supplied with a range of chipset settings that are decided in the factory. A common way to access these settings is to press the F2 or delete button during the first few seconds of a boot-up.

    Once inside the BIOS, great care should be taken. It is a good idea to write down on a piece of paper all the settings that appear on the screen. That way, if you change something and the computer becomes more unstable, you will know what settings to revert to.

    Mcft Windows is better at allocating IRQ numbers than any BIOS. If possible set the IRQ numbers to Auto in the BIOS. This will allow Windows to allocate the IRQ numbers (make sure the BIOS setting for Plug and Play OS is switched to 'yes' to allow Windows to do this.).

    4 Hard disk drives

    After a few weeks, the information on a hard disk drive starts to become piecemeal or fragmented. It is a good idea to defragment the hard disk every week or so, to prevent the disk from causing a screen freeze. Go to

    * Start-Programs-Accessories-System Tools-Disk Defragmenter

    This will start the procedure. You will be unable to write data to the hard drive (to save it) while the disk is defragmenting, so it is a good idea to schedule the procedure for a period of inactivity using the Task Scheduler.

    The Task Scheduler should be one of the small icons on the bottom right of the Windows opening page (the desktop).

    Some lockups and screen freezes caused by hard disk problems can be solved by reducing the read-ahead optimisation. This can be adjusted by going to

    * Start-Settings-Control Panel-System Icon-Performance-File System-Hard Disk.

    Hard disks will slow down and crash if they are too full. Do some housekeeping on your hard drive every few months and free some space on it. Open the Windows folder on the C drive and find the Temporary Internet Files folder. Deleting the contents (not the folder) can free a lot of space.

    Empty the Recycle Bin every week to free more space. Hard disk drives should be scanned every week for errors or bad sectors. Go to

    * Start-Programs-Accessories-System Tools-ScanDisk

    Otherwise assign the Task Scheduler to perform this operation at night when the computer is not in use.

    5 Fatal OE exceptions and VXD errors

    Fatal OE exception errors and VXD errors are often caused by video card problems.

    These can often be resolved easily by reducing the resolution of the video display. Go to

    * Start-Settings-Control Panel-Display-Settings

    Here you should slide the screen area bar to the left. Take a look at the colour settings on the left of that window. For most desktops, high colour 16-bit depth is adequate.

    If the screen freezes or you experience system lockups it might be due to the video card. Make sure it does not have a hardware conflict. Go to

    * Start-Settings-Control Panel-System-Device Manager

    Here, select the + beside Display Adapter. A line of text describing your video card should appear. Select it (make it blue) and press properties. Then select Resources and select each line in the window. Look for a message that says No Conflicts.

    If you have video card hardware conflict, you will see it here. Be careful at this point and make a note of everything you do in case you make things worse.

    The way to resolve a hardware conflict is to uncheck the Use Automatic Settings box and hit the Change Settings button. You are searching for a setting that will display a No Conflicts message.

    Another useful way to resolve video problems is to go to

    * Start-Settings-Control Panel-System-Performance-Graphics

    Here you should move the Hardware Acceleration slider to the left. As ever, the most common cause of problems relating to graphics cards is old or faulty drivers (a driver is a small piece of software used by a computer to communicate with a device).

    Look up your video card's manufacturer on the internet and search for the most recent drivers for it.

    6 Viruses

    Often the first sign of a virus infection is instability. Some viruses erase the boot sector of a hard drive, making it impossible to start. This is why it is a good idea to create a Windows start-up disk. Go to

    * Start-Settings-Control Panel-Add/Remove Programs

    Here, look for the Start Up Disk tab. Virus protection requires constant vigilance.

    A virus scanner requires a list of virus signatures in order to be able to identify viruses. These signatures are stored in a DAT file. DAT files should be updated weekly from the website of your antivirus software manufacturer.

    An excellent antivirus programme is McAfee VirusScan by Network Associates ( www.nai.com). Another is Norton AntiVirus 2000, made by Symantec ( www.symantec.com).

    7 Printers

    The action of sending a document to print creates a bigger file, often called a postscript file.

    Printers have only a small amount of memory, called a buffer. This can be easily overloaded. Printing a document also uses a considerable amount of CPU power. This will also slow down the computer's performance.

    If the printer is trying to print unusual characters, these might not be recognised, and can crash the computer. Sometimes printers will not recover from a crash because of confusion in the buffer. A good way to clear the buffer is to unplug the printer for ten seconds. Booting up from a powerless state, also called a cold boot, will restore the printer's default settings and you may be able to carry on.

    8 Software

    A common cause of computer crash is faulty or badly-installed software. Often the problem can be cured by uninstalling the software and then reinstalling it. Use Norton Uninstall or Uninstall Shield to remove an application from your system properly. This will also remove references to the programme in the System Registry and leaves the way clear for a completely fresh copy.

    The System Registry can be corrupted by old references to obsolete software that you thought was uninstalled. Use Reg Cleaner by Jouni Vuorio to clean up the System Registry and remove obsolete entries. It works on Windows 95, Windows 98, Windows 98 SE (Second Edition), Windows Millennium Edition (ME), NT4 and Windows 2000.

    Read the instructions and use it carefully so you don't do permanent damage to the Registry. If the Registry is damaged you will have to reinstall your operating system. Reg Cleaner can be obtained from www.jv16.org

    Often a Windows problem can be resolved by entering Safe Mode. This can be done during start-up. When you see the message "Starting Windows" press F4. This should take you into Safe Mode.

    Safe Mode loads a minimum of drivers. It allows you to find and fix problems that prevent Windows from loading properly.

    Sometimes installing Windows is difficult because of unsuitable BIOS settings. If you keep getting SUWIN error messages (Windows setup) during the Windows installation, then try entering the BIOS and disabling the CPU internal cache. Try to disable the Level 2 (L2) cache if that doesn't work.

    Remember to restore all the BIOS settings back to their former settings following installation.

    9 Overheating

    Central processing units (CPUs) are usually equipped with fans to keep them cool. If the fan fails or if the CPU gets old it may start to overheat and generate a particular kind of error called a kernel error. This is a common problem in chips that have been overclocked to operate at higher speeds than they are supposed to.

    One remedy is to get a bigger better fan and install it on top of the CPU. Specialist cooling fans/heatsinks are available from www.computernerd.com or www.coolit.com

    CPU problems can often be fixed by disabling the CPU internal cache in the BIOS. This will make the machine run more slowly, but it should also be more stable.

    10 Power supply problems

    With all the new construction going on around the country the steady supply of electricity has become disrupted. A power surge or spike can crash a computer as easily as a power cut.

    If this has become a nuisance for you then consider buying a uninterrupted power supply (UPS). This will give you a clean power supply when there is electricity, and it will give you a few minutes to perform a controlled shutdown in case of a power cut.

    It is a good investment if your data are critical, because a power cut will cause any unsaved data to be lost.

    Wednesday 14 November 2012

    How To Hide & UNHIDE Hard disk Volumes By CMD Command




    How To Hide and unhide the hard disk Volumes using CMD Commands :

        First check how many drives are there in my computer and then see which drive holds your secret files.Then make the drive to invisible by following the below steps of using cmd commands,

        start->run->cmd->DISKPART
        DISKPART>list volume (it list available partition volumes)
        select the volume by SELECT VOLUME 1or 2 ..
         Hide the selected volume by REMOVE LETTER C or D or... command.

    Note :For Unhide the hidden drive use the command ASSIGN LETTER after selecting the hidden drive.


    Now to unhide the partition:
    Go to an elevated command prompt=run cmd.exe as administrator

    Enter following commands:

    DISKPART --- run the diskpart program
    LIST DISK ---- list the disks in system
    SELECT DISK n ----n is number of disk with hidden volume
    DETAIL DISK ----- to make sure you got the right one
    LIST VOLUME ------lists the volumes in the system
    SELECT VOLUME n ----n is the number of the hidden volume
    DETAIL VOLUME ---- to make sure you got the right one
    ATTRIBUTES VOLUME CLEAR HIDDEN ---clear the hidden attribute
    EXIT --- exit from DiskPart
    EXIT --- exit from command shell

    Later if you want to hide the volume again then the command is:
    ATTRIBUTES VOLUME SET HIDDEN

    This is another posting showing "how to do computing" for everyday computer usages... For a general public



    Thursday 7 June 2012

    How to use FTP with Command Line (Command Prompt)

    How to use FTP from the command line. 


     FTP (File Transfer Protocol) allows you to transfer files between your PC and other Internet systems (hosts). You can transfer files, work with local or remote directories, rename and display files, and execute system commands.

    Before you start, you must know how to log on to the remote system and have a userid and password on that system. Note: Some systems allow anonymous ftp access. To use anonymous ftp, use anonymous as your userid and your e-mail address as the logon password. Logging Onto and Off of a Remote System To begin using Microsoft's FTP client, Open a command prompt and switch to the destination directory (where you want the download file).

    To start an FTP session, enter: ftp host_name where hostname is the name or IP address of the remote system. You will then be asked to enter your userid and password.

    Once you have successfully logged onto a remote system, you will be able to use ftp commands to view a listing of files on the remote system and transfer files between the two systems.


    Example: Download i386.exe (Windows NT 3.5 Resource Kit) from ftp://ftp.microsoft.com/bussys/winnt/winnt-public/reskit/nt35/i386 to C:\Temp\Download
    1. Open a command prompt. Enter CD C:\Temp\Download (assuming that directory exists).
      Enter: ftp ftp.microsoft.com

      You should now see a prompt similar to this:
      Connected to ftp.microsoft.com.
      220 Microsoft FTP Service
      User (ftp.microsoft.com:(none)):


    2. For the userid, Enter: anonymous

      You should see a prompt similar to this:
      331 Anonymous access allowed, send identity (e-mail name) as password.
      Password:


    3. Enter: userid@domain.com as the password at the "Password:" prompt.
      Note: Any e-mail address in a userid@domain.com format should work. You will not be able to see the password as you type it.


    4. To download i386.exe from the bussys/winnt/winnt-public/reskit/nt35/i386 directory, Enter: get bussys/winnt/winnt-public/reskit/nt35/i386/i386.exe
      Note: You could have also used ls to view the directory and file names, cd bussys/winnt/winnt-public/reskit/nt35/i386 to switch directories, and get i386.exe to download the file from within that directory.


    5. To end the FTP session, Enter: quit or bye.
    Note: Once you have extracted the resource kit, you will have to expand individual files 
    example: expand choice.ex_ choice.exe



    FTP Commands

    For a list of FTP commands, at the "ftp>" prompt, Enter: helpWhen using ftp from the command prompt, the following list of supported commands will be displayed:
    Note: Hover your mouse over a command to see what the output of "help *" is for that command.


    !   

    delete

    literal

    prompt

    send

    ?   

    debug

    ls  

    put 

    status

    append

    dir

    mdelete

    pwd 

    trace

    ascii

    disconnect

    mdir

    quit

    type

    bell

    get 

    mget

    quote

    user

    binary

    glob

    mkdir

    recv

    verbose

    bye 

    hash

    mls 

    remotehelp

    cd  

    help

    mput

    rename

    close

    lcd 

    open

    rmdir
    
    

    The question mark (?) command is equivalent to the help command. Typing help or ? followed by the name of a command will display a brief description of the command's purpose. The exclamation point (!) can be used to shell to the system (command) prompt. Type Exit to return to the FTP session.

    You can also issue a subset of system commands to perform as you shell out, e.g., ! dir %windir% | more. When the commands in the shell have completed, you will be returned to the FTP session. The pwd command will list the current directory on the remote machine.

    To change directories on the remote machine, use the cd command. To create a new directory on the remote machine, use the mkdir command followed by the name you would like to assign to the new directory. The lcd command can be used to change directories on the local (PC) machine.

    To display a listing of files on the remote system, enter: ls or dir.



    To download a file (copy a file from the remote system to your PC), you can use the command get or recv followed by the name of the file you would like to download. Optionally, you can follow the filename with a second filename which will be assigned to the file when it is downloaded to your PC.

    To download multiple files, you can use the mget command followed by a descriptor for the files you would like to download (e.g.: *.f for all files ending in ".f" or *.* for all files).

    You will be prompted to indicate whether you would like to download each file in turn. To turn off this prompting, enter the prompt command prior to entering the mget command; you will receive the message "Interactive mode OFF" indicating that prompting has been deactivated. By default, files are downloaded and uploaded in ASCII file transfer mode.

    To download or upload files using Binary format mode, enter the command Binary at the "ftp>" prompt prior to downloading or uploading the file(s). To return to ASCII file transfer mode, enter the ASCII command. To upload a file (copy a file from your PC to the remote system), you can use the command put or send followed by the name of the file you would like to upload.

    Optionally, you can follow the filename with a second filename which will be assigned to the file when it is uploaded to the remote system. The mput command can be used to upload multiple files.

    You can use the close or disconnect command to drop the current ftp connection without exiting from the command enironment and then use the open command to connect to a new host.

    How to Create a Ansible Lab on your Local Machine using Vagrant in 5 min using ChatGPT - Part 2

    Update the above Vagrantfile Centos 8 servers and add Public IP and dhcp on each server .. To update the provided Vagrantfile for the three ...