First of all you need to know where your Linux OS is installed to. that is what drive it is currently living on. Bear in mind that Linux formats the drive as HFS rather than Fat/Fat32 or NTFS. ( These are the file systems used by various Operating Systems).
So HFS Partitions are not seen by windows, so its hidden.
To remove the partitions of Linux in WindowsXP go to your 'Control panel' > Admistrative Tools > Computer Managment
Open 'Disk Management' and you will see your Linux drives recognised as 'Unknown Partition' plus the status of the drive. Bearing in mind you know what partition and disk you installed to it will be easier to recognise as the drive/partition where you had installed it to.
Once you have identifed the drives, 'right-Click' on the drive/partiton and select 'Delete Logical Drive'
Once you have followed this through, you will now have free space.
This next part is very important. Once you have formatted the drive, re format it as your required file system type. either Fat32 or NTFS. Now the important part is coming up !
Fixing your Master Boot Record to make Windows Bootable again.
Have a Windows Boot disk with all the basic DOS Commands loaded on to the disk. A standard Windows 98/Me Boot Disk will work too.
Type in the DOS command :
e.g, from your C:\
fdisk /mbr
Or use your Windows XP run the recovery console, pick which xp install you would like to boot in to (usually you will pick #1)
then type: fixmbr. Answer Y to the dialoge.
Your master boot record will now be restored and Windows XP will be bootable once again. Your System will be restored with your original boot loader that you got with Windows XP.
Showing posts with label remove. Show all posts
Showing posts with label remove. Show all posts
Saturday, August 22, 2009
Friday, August 21, 2009
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, httpd, 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.
#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, httpd, 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.
Sunday, August 2, 2009
Remove "Uninstallable" XP Utilities
Think you can't uninstall Windows Messenger, WordPad, and similar components? Think again. This hack shows you how. Windows has always had a problem with uninstalling software, and it's particularly poor at uninstalling its own utilities, such as WordPad or Windows Messenger. Uninstalling these utilities can free up hard- disk space if your hard disk is starting to fill up. And if you never use Windows Messenger, you most likely will want to uninstall it because the program frequently launches itself automatically even after you've shut it down repeatedly, kind of like Dracula returning from the dead. It won't bother you any longer if you uninstall it. To remove XP utilities and components, you normally choose Control Panel Add or Remove Programs Add/Remove Windows Components to get to the Windows Components Wizard, shown in Figure 2-12 . To uninstall a utility or component, just follow the wizard's instructions. Figure 2-12. The Windows Components Wizard
Ah, but there's a catch. A number of Windows utilities and componentsnotably Windows Messenger and WordPaddon't show up in the Windows Components Wizard so there's no apparent way to uninstall them. But you can, in fact, remove these components. XP has a Setup Information file that controls what appears in the Windows Components Wizard. If you edit this file, you can force these components to appear in the wizard, and then you can remove them as you would any others. To start, use Notepad or another text editor to open the Setup Information file, sysoc.inf, which is generally found in the C:\WINDOWS\INF folder. For safety's sake, make a backup of the file before editing it, so you can revert to it if you need to. You should also set up a system restore point before making the changes. To set up a system restore point, choose Control Panel Performance and Maintenance System Restore and follow the instructions.
C:\WINDOWS\INF is a hidden folder, so if you want to view its contents, you will have to enable hidden folders by going into Windows Explorer and choosing Tools Folder Options View Show Hidden Files and Folders.
When you open the file, look for the line describing the program you want to uninstall. Lines in the file have the format:program=program.dll,O cEntry,program.inf,,numeral
Programs that are uninstallable have the word hide (or HIDE) embedded in the string. When this word is included in the string, the program won't show up in the Windows Components Wizard. The Pinball game entry, which doesn't show up in the wizard, looks like this:Pinball=ocgen.dll,OcEntry,p inball.inf,HIDE,7
To force it to show up in the wizard, remove the word HIDE from the entry that refers to the component you want to remove. For example, if you want to remove Pinball, edit its entry to this:Pinball=ocgen.dll,OcEntry,p inball.inf,,7
Save the sysoc.inf file, then run the Windows Components Wizard. The component will now show up in the wizard. Remove it as you would any other component. Keep in mind that not all of the entries in sysoc.inf are as easy to understand as Pinball and WordPad. For example, if you want to remove Windows Messenger, look for the entry that starts with the text msmsgs. If you want to remove the Accessibility Wizard, look for the entry for AccessOpt. Table 2-4 lists the "uninstallable" programs and their entries in the sysoc.inf file. Table 2-4. "Uninstallable" programs and their sysoc.inf entries Entry What entry refers to
AccessOpt Accessibility Wizard
MultiM Multimedia components, including Media Player, Volume Control, and Sound Recorder
CommApps Communications components, including Chat, Hyperterminal, and Phone Dialer
AutoUpdate Windows Automatic Update
TerminalServer Terminal Server
dtc Distributed Transaction Coordinator
dom COM+
WBEM Windows Management Instrumentation
Pinball Pinball game
MSWordPad WordPad
msmsgs Windows Messenger
You might run into a few gotchas when trying to remove "uninstallable" components. On some systems, you simply won't be able to remove Windows Messenger because Windows Messenger won't show up on the Windows Components Wizard even after you edit the sysoc.inf file. And some components, such as Terminal Server, will show up in the wizard if you edit the sysoc.inf file, but the wizard still won't let you uninstall them. 2.9.1. Hide Components You Don't Want to Be Uninstalled You can use this same technique in reverse to hide components you don't want to be uninstalled accidentally. Simply put the word HIDE in the proper place in the entry that you don't want to show up in the Windows Components Wizard. For example, if you want to hide the uninstall entry for the fax utility, edit its entry by changing:Fax=fxsocm.dll,FaxOc mSetupProc,fxsocm.inf,,7
to:Fax=fxsocm.dll,FaxOcmSetup Proc,fxsocm.inf,HIDE,7
Ah, but there's a catch. A number of Windows utilities and componentsnotably Windows Messenger and WordPaddon't show up in the Windows Components Wizard so there's no apparent way to uninstall them. But you can, in fact, remove these components. XP has a Setup Information file that controls what appears in the Windows Components Wizard. If you edit this file, you can force these components to appear in the wizard, and then you can remove them as you would any others. To start, use Notepad or another text editor to open the Setup Information file, sysoc.inf, which is generally found in the C:\WINDOWS\INF folder. For safety's sake, make a backup of the file before editing it, so you can revert to it if you need to. You should also set up a system restore point before making the changes. To set up a system restore point, choose Control Panel Performance and Maintenance System Restore and follow the instructions.
C:\WINDOWS\INF is a hidden folder, so if you want to view its contents, you will have to enable hidden folders by going into Windows Explorer and choosing Tools Folder Options View Show Hidden Files and Folders.
When you open the file, look for the line describing the program you want to uninstall. Lines in the file have the format:program=program.dll,O cEntry,program.inf,,numeral
Programs that are uninstallable have the word hide (or HIDE) embedded in the string. When this word is included in the string, the program won't show up in the Windows Components Wizard. The Pinball game entry, which doesn't show up in the wizard, looks like this:Pinball=ocgen.dll,OcEntry,p inball.inf,HIDE,7
To force it to show up in the wizard, remove the word HIDE from the entry that refers to the component you want to remove. For example, if you want to remove Pinball, edit its entry to this:Pinball=ocgen.dll,OcEntry,p inball.inf,,7
Save the sysoc.inf file, then run the Windows Components Wizard. The component will now show up in the wizard. Remove it as you would any other component. Keep in mind that not all of the entries in sysoc.inf are as easy to understand as Pinball and WordPad. For example, if you want to remove Windows Messenger, look for the entry that starts with the text msmsgs. If you want to remove the Accessibility Wizard, look for the entry for AccessOpt. Table 2-4 lists the "uninstallable" programs and their entries in the sysoc.inf file. Table 2-4. "Uninstallable" programs and their sysoc.inf entries Entry What entry refers to
AccessOpt Accessibility Wizard
MultiM Multimedia components, including Media Player, Volume Control, and Sound Recorder
CommApps Communications components, including Chat, Hyperterminal, and Phone Dialer
AutoUpdate Windows Automatic Update
TerminalServer Terminal Server
dtc Distributed Transaction Coordinator
dom COM+
WBEM Windows Management Instrumentation
Pinball Pinball game
MSWordPad WordPad
msmsgs Windows Messenger
You might run into a few gotchas when trying to remove "uninstallable" components. On some systems, you simply won't be able to remove Windows Messenger because Windows Messenger won't show up on the Windows Components Wizard even after you edit the sysoc.inf file. And some components, such as Terminal Server, will show up in the wizard if you edit the sysoc.inf file, but the wizard still won't let you uninstall them. 2.9.1. Hide Components You Don't Want to Be Uninstalled You can use this same technique in reverse to hide components you don't want to be uninstalled accidentally. Simply put the word HIDE in the proper place in the entry that you don't want to show up in the Windows Components Wizard. For example, if you want to hide the uninstall entry for the fax utility, edit its entry by changing:Fax=fxsocm.dll,FaxOc mSetupProc,fxsocm.inf,,7
to:Fax=fxsocm.dll,FaxOcmSetup Proc,fxsocm.inf,HIDE,7
Subscribe to:
Posts (Atom)
Follow Me... Stay Connected
MY STATS