Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!
Showing posts with label Windows. Show all posts
Showing posts with label Windows. Show all posts

Thursday, June 27, 2013

ntldr is missing error

http://pcsupport.about.com/od/findbyerrormessage/a/ntldrmissingxp.htm
  1. Restart the PC. The NTLDR error could be a fluke.
  2. Check your floppy and optical (CD/DVD/BD) drives for media and disconnect any external drives. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk, CD/DVD/BD, or external hard drive or flash drive.
    Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive with Windows installed is listed first.
  3. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors.

    Note: There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.
  4. Restore the NTLDR and ntdetect.com files from the Windows XP CD. Restoring these two important system files from the original Windows XP CD may do the trick:
    Enter Windows XP Recovery Console
    .
    When you reach the command prompt (detailed in Step 6 in the link above), type the following two commands, pressing Enter after each one:
    copy d:\i386\ntldr c:\
    copy d:\i386\ntdetect.com c:\
    
    In the command listed above, d represents the drive letter assigned to the optical drive that your Windows XP CD is currently in. While this is most often d, your system could assign a different letter. Also, c:\ represents the root folder of the partition that Windows XP is currently installed on. Again, this is most often the case but your system could be different.
    If you're prompted to overwrite either of the two files, press Y.
    Take out the Windows XP CD, type exit and then press Enter to restart your PC.
    Assuming that missing or corrupt versions of the NTLDR and/or Ntdetect.com files were your only issues, Windows XP should now start normally.
  5. Repair or replace the boot.ini file. This will prevent the NTLDR error if the cause of the problem is a boot.ini file that is not configured properly for your Windows XP installation:
    Enter Windows XP Recovery Console. The Recovery Console is an advanced diagnostic mode of Windows XP with special tools that will allow you to restore the boot.ini file.
    When you reach the command line (detailed in Step 6 in the link above), type the following command and then press Enter.
    bootcfg /rebuild

    The bootcfg utility will scan your hard drives for any Windows XP installations and then display the results. Follow the remaining steps to add your Windows XP installation to the boot.ini file.
    The first prompt asks Add installation to boot list? (Yes/No/All).
    Type Y in response to this question and press Enter.
    The next prompt asks you to Enter Load Identifier:.
    This is the name of the operating system. For example, type Windows XP Professional or Windows XP Home Edition and press Enter.
    The final prompt asks you to Enter OS Load options:.
    Type /Fastdetect here and press Enter.
    Take out the Windows XP CD, type exit and then press Enter to restart your PC.
    Assuming that a missing or corrupt boot.ini file was your only issue, Windows XP should now start normally.
    http://www.wikihow.com/Fix-Boot.Ini

    http://www.fermu.com/es/252
  6. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the "NTLDR is Missing" error.
  7. Repair the Windows XP master boot record. NTLDR error messages may also appear if the master boot record is corrupt.
  8. Reseat all internal data and power cables. NTLDR error messages could be caused by loose or malfunctioning IDE cables.

    Try replacing the IDE cable cable if you suspect it might be faulty.
  9. Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.
  10. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
  11. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch. While this will almost certainly resolve any NTLDR errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.

    If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.
  12. Replace the hard drive and then perform a new installation of Windows XP. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.

NTLDR Errors Apply To

This issue applies to the Windows XP operating system, including Windows XP Professional and Windows XP Home Edition.
Windows 8, Windows 7, and Windows Vista utilize BOOTMGR, not NTLDR.

Still Having NTLDR Issues?

See Get More Help for information about contacting me on social networks or via email, posting on tech support forums, and more. Be sure to let me know what steps, if any, you've already taken to fix the "NTLDR is missing" issue.
Other Errors That Appear During the Boot Process

Monday, June 3, 2013

PortableUpdate

http://www.portableupdate.com/default.aspx
PortableUpdate is a tool for updating a Microsoft Windows® computer without the necessity to be connected to any network. This is useful in many circumstances:
  • When the computer reside on a secure Lan isolated from internet;
  • When the computer to update doesn’t have access or can't use a proxy server;
  • When is necessary to completely update a fresh-formatted computer with the last update before connect it to the network;
  • When the computer doesn’t have an hardware network connection at all;
  • When the network connection speed is too low or it is necessary to update the computer very speedily;
  • In all the other cases when is mandatory to have the complete control on the whole updating process without connecting the computer to the network.
  • ...but of course it works very well also if connected!
How it works?
To update a computer disconnected from internet, PortableUpdate use an external cache to store the updates.
  • The cache can reside on any Usb external drive or, via Lan network, on a shared path. Once an update is copied to the cache (the only time that an internet connection is required!), the same update will be used for all computer that need that particular update.
  • You'll never download twice the same update for update different computers or for updating many times the same computer. For example, consider that the dimension of one single update can reach 442 MB in size!
  • When the update is stored into the PortableUpdate cache, the program will use the standard Windows® Update API services to update your computer.
  • As result, you can see the log update in the standard Update History Log as it was done from the normal Windows® Update site!
  • For any other technical information, please read the documentation page.

Saturday, March 16, 2013

clearing out the Printer spooler folder


http://www.sevenforums.com/general-discussion/274322-services-error-1503-cannot-start-print-spooler-others.html
Sometimes a corrupt print job can crash the print spooler services indefinitely, until it is manually cleared. Even though your printer may show 0 Print Jobs in queueHers how to:
Make sure the print spooler servies is stopped.
Click the start button, (bottom Left) Copy and paste the path below into the search programs and files bar,

C:\Windows\System32\spool\PRINTERS

This should open your spooler print jobs, If any files are showing in there, please delete them,
Then you will need to re-start the print spooler service:
Click on the Circle start button, This time, in the "search programs and files box"

Type: services.msc
Locate the printer spooler services - Right click it, and select Start.

Friday, September 28, 2012

VPN on Windows

Source
Vista VPN Server ---------------
Windows 7 VPN client. 
Virtual Private Network (VPN) - Enable Incoming VPN Connections
Virtual Private Network (VPN) – Enable Outgoing VPN Connections


Windows Built-In VPN (Windows, Free)
Five Best VPN Tools
Windows has a built-in VPN client. Surprised? Many people are. It's not a heavily advertised feature, but it covers many people's needs. Before exploring other client solutions, it's worth pulling up the quick launch box in the Windows start menu and typing "VPN" to start the configuration process. In Windows versions prior to Windows Vista, the built-in VPN client received a fair amount of criticism for lacking features and supported protocols. Since Vista and especially in the Windows 7 implementation, it's grown significantly and unless you need a feature or standard that isn't implemented you may not need to install anything at all.

===========
VPN Server software...Please recommend-vpn.jpg  
Fix for the loss of internet connection while using VPN.

For the issue of losing your internet connection while using the VPN, here's how to fix:
  1. On the client computer:
  2. Go to the Network & Sharing Center
  3. Left hand side, click Change Adapter Settings
  4. Right click your VPN client connection, and choose Properties
  5. Go the the network tab, then highlight "Internet Protocol Version 4 (TCP/IPv4)" and click the 'Properties" button.
  6. Click on the 'Advanced' button.
  7. Disable the 'Use default gateway on remote network' check box.
===========
www.tuvpn.com/es/tutoriales/pptp-en-windows7

Configurar nueva Conexión de Red

Click sobre Configurar nueva Conexión de Red.
7_pptp_paso3.jpg379

Configurar-VPN-PPTP-en-windows-7 (para ver las imágenes ir a la página original) 

En otros tutoriales se explica cómo configurar la red en GNU/Linux (Ubuntu 11.10) y Mac OSX... Y con este  para windows 7 ya tendríamos una red VPN PPTP en los principales sistemas.
Procedimiento Pulsar sobre el icono de nuestra red, en este caso de cable, y a continuación sobreAbrir centro de redes y recursos compartidos.
En la ventana que se ha abierto, presionamos sobre “Configurar una nueva conexión o red“.
VPN: Asistente
Una vez iniciado el asistente de configuración nos dará la opción de elegir entre diversos tipos de conexión, en nuestro caso tendremos que seleccionar “Conectarse a un área de trabajo“.
A continuación tendremos que elegir el modo de conexión, es decir, si queremos que establezca una conexión directamente con el servidor de la VPN o si por el contrario queremos que use la conexión activa, de modo que seleccionamos “Usar mi conexión a Internet (VPN)“.
En este punto tenemos que establecer los parámetros de la red, empezando por la dirección del servidor y un nombre que nos permita diferenciar la conexión VPN que estamos configurando del resto de conexiones existentes. El resto de opciones las dejamos sin marcar.
Por último nos pide que insertemos nuestro nombre de usuario y contraseña de la VPN, en caso de conectarnos a una red con dominio, normalmente en entornos empresariales, tendrías que escribirlo también, no es nuestro caso así que lo dejamos en blanco.
A continuación el asistente conectará con la VPN para verificar que todo está correctamenteconfigurado.
VPN: Conectar y Desconectar
Por último, para saber que estamos conectados a la VPN o bien para desconectarnos de la misma, tan sólo tendremos que pulsar de nuevo sobre el icono de la red para que aparezca la conexión. Para desconectarnos sólo tendremos que pulsar sobre la misma y a continuación sobre el botón “Desconectar“.
How to set up a VPN Server on Windows 2003
Virtual Private Networks (VPN) are an important tool in remote connectivity, especially in corporations and professional organizations, but their usage may vary from instance to instance. In any case, VPNs allow a user to access a remote network’s resources with ease, and has the potential to make life a lot easier for the end user should it be used properly.
With Windows 7, setting up a VPN server on your PC that can be accessed from anywhere on the internet is pretty simple, yet most people are neither aware of the benefits nor know the process. In this article, I’ll guide you throughhow to set up a VPN server on Windows 7 without using any extra software or applications.
Assumptions
Before I go into detail on how to set up a VPN server, here are a few assumptions that this guide makes:
  • Your internet connection utilizes a router, on which you have port forwarding permissions
  • You know your way around your router’s user interface setup, because they vary with make and model
  • You understand and acknowledge any potential security risks involved with using VPNs
  • Administrator access on the machine where you’re trying to setup the VPN server
How to set up a VPN server
The process is not that complicated. Let’s begin.
Navigate to Windows Control Panel, and select Network and Internet. You then need to access the Network and Sharing Center, bringing you to a screen showing all your network information and configured connections. On this window, select ‘Change adapter settings’ from the left sidebar.
how to set up a vpn
Clicking this will bring you to a new window listing all your network connections, however many you may have. In this window, the top menu bar is usually hidden (as with all of Windows 7), so press Alt to bring it forth, and navigate toFile > New Incoming Connection.
how to set up a vpn
A wizard shall now start which will help you set up a VPN server on your PC. In the first screen, you define who shall be able to access your network – it can be anyone from you to your spouse or children – but it’s generally a good idea to give your administrator account access to connect via VPN as well.
how to set up a vpn
Hit Next and you will be telling your computer how people will connect to the VPN. Usually there is only one option available, “Through the internet” but in my case you can see an additional one which is a virtual modem.
how to set up a vpn
The final page will determine what kinds of machines can access the VPN – including Macs and Unix servers – so it’s best to leave the default setting as it is here.
how to set up a vpn
Complete the wizard, let it populate the VPN settings and wait till you’ve given with a final name for this incoming connection. This name would usually resemble your PC’s network name, but make a note of it as this information will be required to establish connectivity with the VPN.
Connecting to your VPN
Next, you need your PC’s IP address and the default gateway. If that information is not already available, the easiest way to obtain it is using “ipconfig” command in Windows’ command prompt interface. See the screenshot below.
how to set up a vpn
Finally, you need to add VPN’s communication port to your router’s settings. To do that, log in to your router and navigate to port forwarding settings (there are no standard instructions because every router’s interface varies from others). You need to create a new forwarding to port 1723 which is by default the port that VPNs use to connect. Also, this port needs to be pointed to your PC’s IP address that was obtained through ipconfig command. Save your settings and reboot the router once.
That completes the entire tutorial on how to set up a VPN server on your Windows 7 computer. Depending on your machine and hardware, you may require a couple of reboots more both on your PC and router, but that’s about it. Your VPN server is up and ready for any client computer to communicate with.
Configuring-a-split-tunnel-pptp-vpn-in-windows-7/
Howto-windows-7-pptp-vpn-setup-tutorial

Wednesday, September 26, 2012

BCD 0xc000000f Error

How To Fix Boot/BCD 0xc000000f Error This article is specific to Windows 7 but similar errors occur on Vista and Windows 2008/R2.
After rebooting your computer you receive the following error:
Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1.insert windos cd and run a repair your computer option.
File: /boot/bcd
Status: 0xc000000f
Info: an error occurred while attempting to read the boot configuration data.
You may receive a similar error which lists the error code as 0xc0000034 or missing file: \windows\system32\winload.exe instead.
You may also receive further errors after trying to repair the bcd store using bootrec and bcdedit as follows.
The requested system device cannot be found.
The “Windows Boot Configuration Data File is Missing Required Information
The “Windows Boot Configuration Data File is Missing
An error occurred while attempting to read the boot configuration data
Cause and Fix
The most likely cause of this error is that you tried to dual boot two operating systems and then later decided to remove one. This inadvertently may have deleted the bcd boot store. The trick here is to run the above commands in the right order and set your boot partition to active. Let’s get started.
Make sure your boot partition is set to Active
Boot from your DVD and choose the repair option. From the recovery console type “diskpart” and press enter and then type “list disk” to get a list of physical disks installed.
Running diskpart to fix bcd bood errorIn the example here I only have one disk in my machine, if you have more than one identify the disk which has the Windows boot partition on it and then select it. Select it by typing “select disk 0″ (in my case). Now type “list partition”. The Windows 7 boot partition is a 200 MB primary partition. As you can see here it was on disk 0. Select it by typing “select partition 2″ or whichever number matches your 200MB partition.
Set the partition to ActiveNow type “detail partition” and look where it says “Active”. If it says yes then move onto the next section otherwise type “Active” and press enter, Windows should report the partition is now marked as active. Now reboot and boot into the recovery console again.
Repair the MBR and boot sectors
From the recovery console run these commands in this order:
  • bootrec /fixmbr
  • bootrec /fixboot
Now reboot the machine again into the recovery console and type “bcdboot path to your windows folder“.  Your windows folder will normally be c:\windwows but in the recovery console it may show up as D:\windows so make sure you get the path right. In my case it was “bcdboot d:\windows”. This will will build a new bcd boot store and copy over all boot files needed to boot. Now reboot your machine one last time and it should work. If it doesn’t run the two bootrec commands again.
If you have any additional operating systems you want to add use the bootrec /scanos command.
If you still have issues you may have a system with a GPT disk. In this case you will have an EFI sytem partition that must always be active. See the following if you get Failure when attempting to copy boot files or suspect you have an EFI system.

Tuesday, January 17, 2012

runas command

You’ll need admin privileges to stop and start a service. 
On XP, you can use a command like this:
runas /noprofile /env /user:Administrator cmd
You will be prompted for the Administrator password, and a new command window will open.

Saturday, December 10, 2011

Windows: MoBo upgrade, same hard drive

Source
It is possible i think to take a disk image of your old drive using Aconis True Image home, then clone to another drive without the drivers, this would solve your problem i think, as win7 will install its own so it will work, then install the proper drivers for your  motherboard. Not as complex as it sounds, but would save you buying any other software again. 
--------------------------------------
(* First warning, be sure the HD settings are the same, if you used AHCI, use the same or default settings. If you did not use AHCI on the first mobo then DO NOT USE AHCI on the new one *)
Upon first try the system appeared to load but then locked on the Windows splash screen. Tried to boot into safe mode, but the same outcome. Booted safemode/command prompt and saw that the ATI PCIE video driver was trying to load. Since the new mobo was Nvidia based, this was problematic.

Fix was quick for me.
1. Wrote down the video driver name - (something like atipcie.sys)
2, Booted with Bartpc (or anyother utility that will let you boot and edit the NTFS partition)
3. Deleted the ati driver
4. Booted the drives on the new mobo.
5. installed new chipset drivers for the Asus.
This worked for me. I also had an MSI mobo but I had to copy vga.sys to the ATIpcie.sys to get this to work. Either way, Windows 7 was flexible enough to allow the new drivers to be loaded for the new mobo.
-------------------------------------
If anyone else is looking for a solution to this issue,
1. get a Hirens boot cd
2. boot into the mini xp Provided on Hirens
3. In the hirens utilities, Find registry tools, and click on FIX hdd controller
It launches a dos window, where you select your target root, and choose repair.
It seems to delete the old driver out of current control set 00 from your registry, and replace it with generic version.
=======================
You will have to do what's known as a "repair installation". All your files & programs *should* remain intact, but you will have to reinstall all the Windows Updates plus the drivers for your new board.
Be sure to back up any important files, documents, pics, etc before swapping boards, just in case something goes wrong. And depending on what you're upgrading from & to, you *may* have to replace more than just the board/CPU/RAM.
=======================
Two possibilities you can hear:
  1. “I just always reinstall the OS.”
  2. “I upgraded once and I didn’t have to do anything to the OS, so that’s what I’m going to try this time.”
Well, Option #1 will certainly work all the time, no matter what. As for Option #2, whether or not the OS will boot depends on the hard disk controller driver. So, just because #2 worked for one upgrade doesn’t mean it will work for another.
Fortunately, whether you use Windows or Linux, there is a very easy way to prepare for a motherboard upgrade.
Now, I’m going to assume that if you think you can upgrade a motherboard, that means you kind of know what you are doing and you can find your away around Windows. If you don’t know how to get to Device Manager in Windows, well, stop right there and either get somebody to help you, or edumacate yourself right quick!
So, to start with, I will assume you are using Windows. For Linux users, see below.
Whether you have Windows XP, Vista, or Windows 7, the process for prepping your puter for a motherboard upgrade is exactly the same. What you need to do is to set the hard disk controller driver in Windows to the standard, plain vanilla Windows version. The reason for this is quite simple, and is illustrated in the following example:
  • You have an AMD processor and VIA chipset in your current machine
  • You want to upgrade to an Intel-based system
  • When you swap out the hardware and try to boot, Windows will use the hard disk controller driver for your old chipset, and thus you will get a blue screen because it can’t load the OS. Oops.
The same can be true if you are moving from Intel to AMD, or even from AMD to AMD or Intel to Intel. It’s also possible that you are already using the default Windows hard disk controller, which means you don’t have to change anything. But just in case, do the following:
  1. Go to Device Manager
  2. Expand the “IDE ATA/ATAPI controllers
  3. If you have an entry like “Standard AHCI 1.0 Serial ATA Controller” or “Standard Dual Channel PCI IDE Controller“, you’re all set. Just stop and upgrade your hardware, and you should be fine 99% of the time. If not, carry on to #4.
  4. Right-click the non-standard disk controller entry and choose Properties -> Driver tab -> Update Driver. I’m talking controller entry here, notATA Channel o“, “Primary IDE Channel“, etc.
  5. Choose the “Browse your computer/Let me pick” options until you get a list of compatible drivers. Select the default “Standard” driver:
    - For a SATA drive: Standard AHCI 1.0 Serial ATA Controller
    - For an IDE drive: Standard Dual Channel PCI IDE Controller
  6. Click OK, and don’t reboot – shut down your computer and perform your hardware upgrade. If you reboot before your upgrade, Windows may automatically replace the standard driver with the custom one that you just tried to replace!
Before firing up your upgraded puter, be sure to connect your primary boot drive up properly and configure the BIOS with that drive as the first boot hard disk. Normally, I try to connect all the drives in the computer and configure the BIOS boot order and such exactly as it all was in the old computer.
When you turn on your new monster, Windows should load and be able to access the boot hard drive just fine. It may take a bit longer than usual since Windows will be detecting your new hardware and trying to install drivers. Don’t freak out if everything doesn’t work at first – the important thing is to get the OS booted so you can install drivers and get the rest of your hardware configured and functioning properly.
That’s pretty much it. I have found this works 99% of the time. For the 1% of the time that it does NOT work for whatever reason, you can always throw the Windows disc into the optical drive, boot from it, and select a “Repair Install”. This will probably overwrite all your Windows files, and you’ll have to reapply all your Windows updates and such, but at least your data will remain intact. Just be sure not to accidentally wipe the drive. That would be bad, especially if you don’t have a backup. But, you DID make a backup first, right??
=======================
My old motherboard died without my having the ability to delete the old drivers off of the hard drive. I have installed a new motherboard and am attempting to boot into the old hard drive, however, Windows 7 will simply start up, try to load the files, and then enter a restart loop.
I know why this is happening. It cannot find the appropiate files to boot off the hard drive because the new motherboard is conflicting with the old drivers on the old hard drive.
I have attempted to boot off the Windows 7 disc and do a repair, however, it does not work. Right now I am dual-booting from a secondary hard drive, and I have full access to the old hard drive.
Basically, I need to manually delete the old drivers from the old hard drive, or find some way to install the new drivers on it whilst booting from the secondary drive. (In other words, I'm booting off D:\ and I'd like to install drivers whilst on D:\ to C:\)
How can I do this?
Things I will NOT do, and will not even consider, so please don't tell me to:
I will not wipe my old hard drive. The programs and data on it are too valuable. And while the data is easily saved, the programs are not and I'd have to reinstall. Some of the programs were obtained when I was in college and my college distributed free programs by download. Now that I am no longer in college, I'd have to pay hundreds of dollars for replacements (for example, Adobe Photoshop CS4 and Symantec Antivirus).
So to repeat, I will NOT consider a hard drive format and fresh install.
I am, however, willing to do any steps to manually delete or install new drivers, no matter how complex or time consuming the steps are. It is worth it to me. All I need to do is get rid of those old drivers. If someone could tell me how, I'd be greatful.
==========================
Source
you should be able to connect them and use their data. Some items to watch for:
1. If these are IDE units, review how to set their jumpers for Master and Slave roles and how to connect. If they are SATA, do NOT change any jumpers - there is NO Master or Slave in SATA units.
2. When they are installed, check in your BIOS Setup screens where you set Boot Priority Sequence. Make sure neither of these units is part of your boot possibilities.
3. I am not sure how a Windows OS will read or deal with a HDD that contains LINUX OS and data, presumably in a File System that is not what Windows is used to handling. I'm kind of assuming you've already familiar with this issue.
4. Although some people have set up systems that can boot either from one HDD containing Linux or from another containing Windows, I doubt you could simply tell your new machine to boot from that old Linux HDD. I would expect you'd have the same problem as trying to use a Windows OS from another machine - the OS installed on the HDD contains just the right drivers for the devices in the OLD machine, and not the ones for the new machine. In the Windows world there is a procedure called a Repair Install you can do from a Windows Install CD to fix this (sometimes). I don't know how it is handled in Linux.
==========================
www.daniweb.com/forums/thread142082.html
most if not all info in that link is about winxp and not win7 ,and most of the help in the thread or links in the thread are not info releated to when your orignal board is a dead board ,like in the situation !
having said that i don't recall ever getting it to work for me with a broken MB,maybe once when the new boards chipset was the same as broken one .
i would think it may be possible with the lates UBCD/or hirens bootcd .i have one here somewhere that has winxp lite on it that may get you in to where you could uninstall chipset drivers and stuff .but only used it once and not sure even what one it is that can boot to live winxp lite ,
hirens= http://www.hiren.info/pages/bootcd
ubcd= http://www.ultimatebootcd.com/
or live linux cd .= http://www.knopper.net/knoppix/index-en.html
==========================

Source
The only problem with buying a new PC ““ one that has existed for years and that hardware technology can’t solve ““ is when you want to move the operating system to your new hard drive. Simply copying your operating system from one hard drive to another doesn’t work, and trying to install your old hard disk into your new PC may result in issues as well. There is a solution to this issue, however.
Making Your Clone
move operating system to new hard drive
Operating systems are finicky beasts. They don’t like to be copied directly over to a new hard drive, and the operating system on your new PC will most certainly won’t let you copy over it (at least as long as it’s running). There’s good reason for this, in terms of curtailing security threats and preventing accidental operating system damage, but it certainly makes moving a full operating system more difficult.
Since copying operating system files the old-fashioned way doesn’t result in a bootable operating system being transferred over, you’ll need to rely on a process called cloning. Cloning a hard drive replicates all or some of the files on it and also replicates the file structure of the hard drive. This creates a perfect bootable copy. Other MakeUseOf authors have discussed this topic already, so check out Tina’s post about popular freeware cloning software and Benjamin’s post about how to clone a hard drive with Clonezilla.

Cloning Problems
how to move operating system to another drive
Unfortunately, while cloning does create a perfect copy of your hard drive and the operating system on it, it isn’t always the best solution. The process of cloning is itself a bit complex, and it will presumably require that you at some point have an extra hard drive, since directly cloning your existing drive to the drive on your new PC would wipe out the new PC’s drive entirely.
The other issue with cloning is that creating a perfect copy does not guarantee that your old operating system will work with your new PC. When an operating system installs itself on a PC, it also installs a plethora of drivers relating to your PC’s hardware. If you transfer your existing OS to a new PC, much of that hardware is going to be different ““ and that can be a shock to your OS. It will have drivers for certain hardware, but that hardware is gone. It will try to compensate by installing new drivers automatically, but if it can’t find the right drivers it will likely crash.
You may be able to repair the operating system if you still have the install disc around, or can load the installer onto another bootable device, but this can be a frustrating process.
Transferring Files
how to move operating system to another drive
If cloning sounds like too much work, or you’ve tried it and found that it failed, you can forgo trying to transfer the entire operating system and instead transfer only your files and system settings.
Windows has a utility for this called Windows Easy Transfer. As the name implies, the goal of the software is to transfer everything from your old PC to your new PC that could easily be lost. It doesn’t transfer software, but it does transfer documents, photos, music, program settings, etc. Once the process is complete, your new PC should behave much as the old one did, and should have all of your personal files as well.
move operating system to new hard drive
The Windows Easy Transfer software is free, but a direct USB connection between computers requires that you buy a Windows Easy Transfer Cable. You can skip this, however, by connecting two computers via a network and transferring files that way. A direct Ethernet connection is usually quickest.
Linux users can accomplish this same task by using a utility called Rsync
Apple users aren’t left out in the cold, either ““ OS X comes with a utility called Migration Assistant that will help you transfer files to your new Mac from an old one.
Conclusion
Personally, I don’t recommend that most users go with cloning, although it is the only option that results in a true full operating system transfer. Utilities that transfer all critical system information and your personal files usually give you a better result ““ they transfer important data, but don’t leave room for driver compatibility issues that could cause crashes.
Let us know if you have done this, and if so, what method you chose to go with.

Tuesday, November 8, 2011

Repair windows XP

http://www.geekstogo.com/forum/topic/138-how-to-repair-windows-xp/

Monday, November 7, 2011

Slipstreaming of RAID drivers in WinXP CD

Extracted from  
Thanks for the tutorial!!
Table of Contents
  1. Introduction
  2. First Steps
  3. Extract the boot image from a Windows XP CD
  4. How to slipstream Windows Service Pack 3
  5. How To slipstream SATA Drivers Using nLite
  6. Burn a bootable CD or DVD Using Nero V 7.8
  7. Burn a bootable CD or DVD using nLite
  8. Conclusion
First Steps
Before we can start the process of creating Windows install disc, we first need to gather some software. Below is a list of software that you will need to download and install, as well as CDs that you should have on hand in order to continue.
  1. An existing copy of Windows XP home, Professional, or Media Center. Unfortunately, for this step you can not use an OEM CD provided by your computer manufacturer (Dell, HP, etc).
  2. Nero Burning Rom or nLite if you do not have NERO
  3. ISOBUSTER
  4. Network installation copy of Windows XP Service pack 3
  5. A copy of your SATA drivers from your motherboard Web site if you have a SATA HDD that requires special drivers.
  6. A blank writable CD or DVD and a CD/DVD burner.
Once you have made sure you have all the software or media listed above, you should create a folder that will be used to store the files that will be written to the installation disc. For this tutorial, we suggest you create a folder on your C: drive labeled XPCD. Once the folder is created, please copy the entire contents of your XP CD to this folder.

Extracting the boot image
[...]
Using the Command Line to slipstream the service pack:
Click on the Start Menu and then select Run. Then type command into the Open: field. Finally, click on the OK button. You will now be at a command prompt where you should type the following bolded lines. After each line, press enter on your keyboard as shown in the figure below.
CD\
C:WindowsXP-KB936929-SP3-x86-ENU.exe /integrate:C:\XPCD

Slipstream Service Pack 2 command prompt

If you are using an OEM Windows XP CD you will receive the following error. This error means that you cannot use this type of CD to create a slipstreamed installation and will not be able to continue with this tutorial.

This Service Pack cannot be integrated into a destination that also has integrated Software Updates.

Now that you are done slipstreaming the service pack using the command line. You should now skip to the section detailing how to slipstream your SATA hard drive drivers. If you are not using a SATA drive you can skip ahead to learn how to burn the DVD.
[...]
How To slipstream SATA Drivers Using nLite
If you have not already installed nLite, you will need to download and install the program first. Next, you will need to download your SATA drivers from your motherboard or computer manufacture's web site. In our example, I will be using VIA raid drivers from Biostar. Once the SATA drivers have been downloaded, you should extract them to a folder on your hard drive. In our example, we have extracted the drivers into the C:\SATA Driver folder.
Now that everything is prepared you should start the nLite program. When the program starts, click on the Next button, and then at the next screen, select the Browse button to see a screen similar to the one below.

nLite locate windows install
Now select your Windows installation folder that we created at C:\XPCD and then click on the OK button. nLite will scan the directory and identify any previously installed service packs. When it has finished, click on the Next button. You will now be on a screen asking if there are any presets that you would like to use. Just click on the Next button again to continue.
You will now be on the Task Selection screen. Simply click once on the Drivers button so that the circle becomes green as shown in the image below.

Select Drivers in the Task Selection screen
After selecting Drivers, you should click on the Next button. You will now be at the Drivers screen. You should now click on the Insert button and then select the Multiple driver folder option so you can include all of the drivers for your specific operating system.

Select multiple driver folder
You will now be prompted for the folder where your extracted drivers are. You now want to browse to this folder, and when there, locate the correct folder for your Operating system. In our case it is the x86 directory since I am using 32bit Windows XP Pro.

You should now select the folder, and then press the OK button. nLite will now automatically install the drivers contained in both subdirectories. You will now see a screen showing the available drivers found in these folders. You should click the All button to select all drivers for your system and then press the OK button.
NOTE: If there are drivers for other versions of windows, for example Vista or 64 bit drivers, do not install them as it will cause file load errors. If you do select them, nLite will notify you of the problem.
When done selecting the correct drivers, click on the OK button.
A new screen will appear asking what driver mode you would like to select. At this screen, you should select the Textmode Driver as shown in the image below.

Textmode driver
If multiple are listed in the Textmode integration options box, select the appropriate driver for your operating system. The OK button will now become available and you should click on it. Do this same routine for for each and every driver that you are installing.
After selecting Textmode Driver you will be at a page listing all the drivers that will be installed. You should click on the Next button and then click on the OK button when it asks if you want to start the process. Your SATA drivers will now be integrated into your Windows files folder. When the process has finished, click on the Next button and then the Finish button.
You are now ready to burn the Windows files to your a bootable DVD. If you will be using Nero to create this DVD, then you can continue to the next section. Otherwise, you can skip ahead to instructions on how to use the free nLite utility to create your DVD.

Burn a bootable CD or DVD Using Nero
Please note that older versions of NERO may not use the same steps as what are outlined in this guide. These steps were created for use with Nero 7 and above.
If you own Nero, then start the Nero Burning ROM program. Once started, if you do not see an option labeled Make Bootable DVD, as shown in the image below, you will need to enable the advanced user settings.

Nero Burning ROM
To start, select the Make Bootable DVD option. On the next screen you will be asked to select a Boot image. You should browse to the folder where you saved the Microsoft Boot image that you extracted using Isobuster in previous steps and select it. Please note, that by default Nero will be looking for a file with a .IMA extension, so you will need to change the file type to All Files (*.*) in order to select the MICROSOFT CORPORATION.img boot image. This is shown in the figure below.

Select Boot image in Nero
You should now click on the Boot tab and put a checkmark in Enable expert settings. Then change Kind of Emulation to No Emulation. Then change the Number of loaded sectors to 4. When done your screen should look similar to the image below.

Change Boot options in Nero
Under the ISO tab, you should not have to change any settings. Just click on the tab to make sure it is configured as shown in the image above. If you have an older version of Nero you will not have the option Do not add the ';1' ISO file version extension under the Relax restrictions category.

ISO Option tab in Nero
Now click on the Label tab. We recommend changing the labels on your completed CD or DVD so that they match your Windows CD. To do that Select Manual and then enter the labels into the ISO 9660 and Joilet fields. For Windows XP Pro you should enter WXPCCP_EN. For Windows XP Home you should enter WXHCCP_EN. An example of this is shown in the image below.

Label options in Nero
Now click on the New button to open the file browser as shown in the image below.

File browser window in Nero
In the right hand pane you will navigate to your slipstreamed location, C:\XPCD, and left-click once on it to select it. Then select all of the files in the right-hand pane and drag them into the left-hand pane. When this is completed, click on the Burn button in the top menu bar. Nero will create the bootable CD for you and you will now have a Slipstreamed Windows XP SP3 CD or DVD!

Burn a bootable CD or DVD using nLite
If you have not already installed nLite, you will need to download and install the program first and then start it.When the program starts, click on the Next button, and then at the next screen, select the Browse button to see a screen similar to the one below.

nLite locate windows install
Now select your Windows installation folder that we created at C:\XPCD and then click on the OK button. nLite will scan the directory and identify any previously installed Service Packs. When it has finished, click on the Next button. You will now be on a screen asking if there are any presets that you would like to use. Just click on the Next button again to continue.
You will now be on the Task Selection screen.

Select Bootable ISO
On this screen select the Bootable ISO option as shown in the image above and then click on the Next button.You will now be at the Bootable ISO screen that will look similar to the image below.

nLite Bootable ISO screen
If the screen above does not look exactly like what you see on your computer, do not be concerned as we need to make some changes first. First change the Mode option to Direct Burn. Then, for the Label field we recommend using the same label that was on your original Windows CD. For Windows XP Pro you should enter WXPCCP_EN into the Label field. For Windows XP Home you should enter WXHCCP_EN into the label field. Next, make sure your CD/DVD burner is selected in the Device menu. Last, but not least, change the Burn Speed to 8X in order to get a reliable burn.
When you have finished configuring these settings, we need to specify our boot image. To do that, change Boot Sector to custom and a window will open asking you to locate your boot sector. You should browse to the folder where you saved the Microsoft Boot image that you extracted using Isobuster in previous steps and select it. Please note, that by default nLite will be looking for .bin or .dat files, so you will need to change Files of type to All Files. Once you do that you will be able to select the MICROSOFT CORPORATION.img boot image as shown in the image below.

Select boot image in nLite

Once you have changed all of your settings and selected your boot image, we are ready to create the Windows installation media. To start this process, click on the Burn button. A confirmation prompt will appear asking if you are sure you want to burn the content to the media. You should click on the Yes button to start the process. nLite will now start preparing the content that will be copied to your media. This may take some time, so please be patient. When it has finished preparing the files, nLite will start writing them to your media as shown in the image below.

Burning your Windows CD with nLite

Please be patient while the files are written to your media. When it has finished, you will see a message stating the written files were verified successfully. You can then click on the Next button and then click on the Finish button to close nLite.
You now have a Slipstreamed SP3 CD or DVD!
============= ==============

How to slipstream SATA drivers into Windows XP setup CD, on your dual boot PC with Windows 7 or Vista
When you install Win XP, setup can not find your Hard Drive or your softwareRAID  is not recogniyed
 
 
 
 

Sunday, November 6, 2011

Bootloaders in multiboot OS

Source by talsemgeest
How to restore the Ubuntu/XP/Vista/7 bootloader (Updated for Ubuntu 11.10)
This How-to is for windows dual booters who reinstall an operating system only to find that it has taken away access to their other operating system.
Whether you want to restore the XP, Vista, 7 or Ubuntu (Grub) bootloader, this guide will walk you through it.
All three parts of this tutorial require that you boot from a cd. If you don't know how to do this, check here.
If you have made a mistake and want to revert the changes, simply follow the instructions for reinstalling the previous bootloader. For example, if you have installed vista over ubuntu, try to get the ubuntu bootloader back, but want to get the vista bootloader back, simply follow my instructions for installing the vista bootloader.
How to restore the Ubuntu grub bootloader (9.10 and beyond)
First you need to find out what your drives are called. You can do this by going to a terminal and typing:
Code:
sudo fdisk -l
From that you need to find the device name of your Ubuntu drive, something like “/dev/sda5″.
So, still in the terminal, type:
Code:
sudo mkdir /media/sda5
sudo mount /dev/sda5 /media/sda5
And then, to reinstall the grub:
Code:
sudo grub-install --root-directory=/media/sda5 /dev/sda
Push enter and you’re done! Of course you need to replace “/dev/sda5″ and “/dev/sda” with what you found in the fdisk output.
How to restore the Ubuntu grub bootloader (9.04 and older)
First of all, all credit for this part of the tutorial goes to catlet. I am simply rewriting his tutorial to have all three bootloaders in this tutorial.
So, lets begin. To restore the grub, you must boot off the ubuntu live cd. Any ubuntu live cd will do.
Once there, open a terminal (Applications>Accessories>Terminal) and type this:
Code:
sudo grub
Next, you need to find which hard drive ubuntu and the grub is installed to. You do this by running this command:
Code:
find /boot/grub/stage1
Take note of what it returns (something like (hd0,1).)
Now you need to tell Grub where it is installed. Using the output of the last command, change this one and run it:
Code:
root (hd,)
Replacing and with what you got back before. For example, if "find /boot/grub/stage1" gave me "(hd0,1)", you would run "root (hd0,1)"
Ok, so thats the configuration over and done with. Now we just need to run one command to install the Grub to your hard drive:

Now to quit and check if it has worked:


Make sure you have taken the live cd out of your disc tray. All going well, you should start back up and see the grub once again.
How to restore the Windows XP bootloader
For this you will need your Windows XP installation CD. Boot into it now.
You will get to a part where it asks if you want to repair or recover. To do so, press "r".
If prompted, enter your Windows XP administrator password. This will leave you at at a command line, so type in the following two commands:


Then type
Code:
exit
then remove your XP cd. If everything has gone well, you should come to your XP bootloader.
How to restore the Windows Vista or 7 bootloader
To restore the Windows Vista/7 bootloader, you must first boot off your Windows Vista/7 installation DVD.
If you have one of the many OEM computers that didnt come with a Vista/7 installation disk, you can get the same effect with a Vista recovery disk, which you can download for
Vista or Win 7.
When you get to the Regional settings, select your Location/Keyboard setting then click next. On the next page you must click on "Repair your computer."
On the next page, if it finds your Windows Vista/7 installation, make sure it is UNSELECTED before clicking next.
Then click on "Command prompt". From there, type in the folowing:
Code:
bootrec.exe /fixboot
Code:
bootrec.exe /fixmbr
Now close the two windows and click "Restart."
Take out your Vista/7 DVD and hopefully, you will be left with your Windows Vista/7 Bootloader.
===========   ===========
Reinstalling GRUB 2 from LiveCD
(with my additions and corrections --cebaehren)
If you cannot boot from GRUB 2 and need to reinstall it, here is the simple method. For more details or for advanced options, refer to the Ubuntu community documentation here:
Grub2 – Reinstalling GRUB 2:
  • Boot the 9.10 Karmic LiveCD to the Desktop.
  • Open a terminal – Applications, Accessories, Terminal.
    If you have an fakeraid try first
    sudo modprobe -q dm-mod
    sudo modprobe -q dm-mirror
    sudo /sbin/dmraid -ay
    Note that in an diskmapperRAID (not multiplediskRAID!)
    the RAID device (two or more hard disks in array) is found as a nvidia device with long stupid name (nvidia_edabbdgc, with first partition as nvidia_edabbdgc1 and counting
    Use /dev/dm-0 for the array of disks and dm-1 for the first partition and so counting for the following parttitions
    that is fdisk /dev/dm-0 or /dev/dm-
  • Determine your normal system partition – `sudo fdisk -l` (That is a lowercase L)
  • If you aren’t sure, run `df -Th`. Look for the correct disk size and ext3 or ext4 format.
  • Mount your normal system partition:
    Code:
    sudo mount /dev/sdXY /mnt
    • Example: sudo mount /dev/sda1 /mnt
    • Note: The partition to mount is normally the partition on which Ubuntu was installed: sda1, sdb5, etc.
      If you have a separate /boot partition, use the device on which the /boot partition is located.
      Grub 2 works best when installed in the MBR of the drive to which BIOS boots. Also remember that you mount the partition (including the number) in this step, but you do not include the partition number when you run the “sudo grub-install” command later.
    • cebaehren note: the kernel or Linux command consider the X as a letter of alphabet for the (considered as) scsi device (sda, sdb, sdc). The partitions starting with 1 (sda1, ... sdb3, sde5, etc)
    • Note: GRUB 2 counts the first drive (not this case in X) as “0″, but the first partition (Y) as “1″
  • Only if you have a separate boot partition:
    • Code:
      sudo mount /dev/sdXY /mnt/boot
      with sdXY being your /boot partition designation.
  • Reinstall GRUB 2:
    Code:
    sudo grub-install --root-directory=/mnt /dev/sdX
    • Example: sudo grub-install –root-directory=/mnt /dev/sda
    • Note: Substitute the device on which Ubuntu was installed – sda, sdb, etc. Do not specify a partition number.
  • Unmount the partition:
    Code:
    sudo umount /mnt
  • Reboot.