More

Starting QGIS after install on windows XP home?

Starting QGIS after install on windows XP home?


New to QGIS and installed 2.6.1 on Windows XP desktop home edition. No errors received during install. When I launch QGIS Brighton from Start - Programs the qgis-bin.exe - Entry Point Not Found pops up.

The procedure entry point xmlSchemaNewDocParserCtxt could not be located in the dynamic link library libxml2.dll.

The same error shows when launching QGIS Browser 2.6.1 as QGIS Desktop 2.6.1.


Look out for all appearances oflibxml2.dllon your system. It seems that QGIS expects another version than the one that is addressed first by your PATH varaible.

The one in the QGIS Brighton/bin path should be the right one.

On my XP computer, I have versions between 493kB and 1016kB, and QGIS needs the largest one, from 23.07.2013.


GRUB menu doesn't appear after Ubuntu install alongside with Windows 10

I shrunk Windows partition, freed 100 Gb, installed Ubuntu into it, installed GRUB into into MBS of the first drive and after reboot I got Windows and with no any option to select. Even in BIOS in boot priority config I see that the main drive entitled as Windows.

My question is not what to do. I don't want to see these long canvases of text and pictures you can find bu searching on this topic, saying only what authors do not understand what are they doing.

My question is what is happening?

How BIOS can know operating system? What is boot sequnce in my case and why does MBR code is ignored?

Some authors recommend to run this command under Windows:

What does it do and how can it help?

I was able to boot my linux partition win Grub for Windows, and currently

(I was entering some bad words during experiments)

Looks like it just prints some info from EFI partition.


How to Properly Reinstall a Program in Windows

A quick way to open Control Panel in Windows 10 or Windows 8 is with Power User Menu, but only if you're using a keyboard or mouse. Choose Control Panel from the menu that appears after pressing WIN+X or right-clicking on the Start button.

Click on the Uninstall a program link located under the Programs heading, or Add or Remove Programs if you're using Windows XP.

If you're not seeing several categories with links below them, but instead just see several icons, pick the one that says Programs and Features.

If the program you're planning on reinstalling requires a serial number, you'll need to locate that serial number now.

Locate and click on the program you want to uninstall by scrolling through the list of currently installed programs you see on screen.

If you need to reinstall a Windows Update or an installed update to another program, click on the View installed updates link on the left-hand side of the Programs and Features window, or toggle the Show updates box if you're using Windows XP. Not all programs will show their installed updates here but some will.

Click the Uninstall, Uninstall/Change, or Remove button to uninstall the program.

This button appears either on the toolbar above the program list when a program is selected or off to the side depending on the version of Windows you're using.

The specifics of what happens now depends on the program you happen to be uninstalling. Some uninstallation processes require a series of confirmations (similar to what you may have seen when you first installed the program) while others may uninstall without requiring your input at all.

Answer any prompts as best you can - just remember that you are wanting to completely remove the program from your computer.

If uninstalling doesn't work for some reason, try a dedicated software uninstaller to remove the program. In fact, if you already have one of these installed, you may have even seen a dedicated uninstall button in Control Panel that uses that third-party program, such as the "Powerful Uninstall" button when IObit Uninstaller is installed — feel free to use that button if you see it.

Restart your computer, even if you're not required to.

In my opinion, this is not an optional step. As annoying as it might sometimes be, taking the time to reboot your computer will help ensure that the program is completely uninstalled.

Verify that the program you uninstalled has been fully uninstalled. Check that the program is no longer listed in your Start menu and also check to make sure that the program's entry in Programs and Features or Add or Remove Programs has been removed.

If you created your own shortcuts to this program, those shortcuts will likely still exist but of course, will not work. Feel free to delete them yourself.

Install the most updated version of the software available. It's best to download the latest version of the program from the software developer's website, but another option is to just get the file from the original installation disc or a past download.

Unless instructed otherwise by the software documentation, any patches and service packs that might be available should be installed to the program after the reboot following the installation (Step 8).


2 Answers 2

Here is the solution I found. This probably isn't the only possible solution, but the only one that worked so far. Feel free to contribute, as it's likely imperfect

The guide generally assumes the computer can boot off your device. The workaround to boot off USB will be posted, but it might be easier to just stop at this point if the computer cannot.

Note: You'd want to use a 2-4 GB USB stick. The newer 32+ GB sticks aren't always recognised by older BIOS

Download FreeDOS legacy, Windows 9x image, UltraISO. Install UltraISO (trial version will do).

  • UltraISO will be used as it doesn't hide the USB contents (as rufus does. If a solution with rufus found, feel free to switch the guide over to rufus)
  • FreeDOS is chosen over MS-DOS because of pragmatic reasons, such as,
    • FreeDOS supports large capacity FAT32 out of the box, MS-DOS will struggle with large-capacity volumes
    • FreeDOS appears to natively prefer the modern filename conventions, compared to 8:3 filenames. Something that could become a problem later on in the guide if MS-DOS was used
    • MS-DOS was distributed initially on floppies, which makes it quite difficult to burn onto USB. Especially for it's to be used with legacy hardware
    • FreeDOS supports USB r/w, something that might come in handy if you get in trouble

    Start UltraISO, open Freedos legacy ISO. Go to Bootable -> Write disk image. Select,

    Then press "Write", "Yes". The image burning should take

    Close UltraISO, open it back again. Open your Windows 9x image and extract the image contents to some folder ISO (you could use your archiving app for this matter, too, not just UltraISO). Then copy the folder onto your flash device.

    Also copy the drivers and software you need to the folder SW on your USB flash drive

    Unplug the device and plug it to your to-be Windows 9x machine. Go to BIOS and see if you can boot off your USB stick

    If you cannot, you are probably into the world of pain. At one time what worked for me if getting a second small USB stick that it could somehow see, writing an Easybcd BIOS extender onto it

    After having booted up, do install FreeDOS onto the to-be Windows 9x machine. Install the base (minimalistic) package without sources

    While still USB plugged in, copy over the ISO and SW folders onto the hard drive,

    • /s - to tell xcopy to copy all of its subfolders, source
    • C: - your USB (!) drive letter, always
    • D: - your HDD drive letter, seemingly always

    Unplug the USB drive, and now boot from the internal storage. Notice that this time, C: will be assigned to the internal storage (which eliminates bugs)

    When prompted with the DOS configurations, select "no drivers (emergency)" configuration. This will prevent any bugs

    CD to ISO folder ( cd ISO ), run setup.exe with the switches you want. For example,

    The /NM (No Machine checking, allows installation from FreeDOS) and /IS (Ignore Scandisk) are prescribed by FreeDOS.

    Conventionally burn an image onto USB with UltraISO / Rufus -> boots ok, BSODs when installing drivers with `Fail to read from C:/" (the USB)

    Conventionally burn an image onto USB with UltraISO / Rufus, begin the installation of Win9x from another media, unplug USB when beginning the installation -> Hangs before getting to GUI. If unplugged later, the GUI setup alleges it'd need to write 5.1 MB onto drive C:/ (the drive-letter assigned to the USB, possibly the installer app bug)

    Conventionally burn an image onto USB with UltraISO / Rufus, change autoexec.bat to use other drive-letter - no luck

    You have to get the system booted up under DOS to start with. That's the hard part. If you have a working Windows 9x/ME system you can just format the flash drive as FAT16/32 and select to make the drive bootable. Copy the win98 folder from the Windows 98 setup CD on to the flash drive. Finding the DOS fdisk and format programs from a working Windows 9x install or Windows 98 boot floppy may be needed as the target drive will need to be partitioned and formatted prior to installing Windows. The flash drive should boot up like any other hard drive. Make sure the computer has 1GB of RAM or less else unpatched Windows may hang. Windows 97 (95 OSR2) and later versions support FAT32.

    You can use an emulator like QEMU to boot from a floppy image of a Windows 9x boot disk and set the flash drive device to the 1st hard drive. Then just run sys a: c: in DOS after partitioning and formatting the flash drive to make it bootable. Copy utilities like fdisk and format from the boot disk to the flash drive so you can format the target hard drive.


    Dual-boot boot menu does not show up after installing Ubuntu 15.10 alongside Windows 10

    I have installed Ubuntu 15.10 alongside Windows 10 with UEFI. To install Ubuntu, I chose the option install alongside Windows 10 or something similar to this. Then I created a new partition for Ubuntu and installed it. After installation, the boot menu did not show up. Initially I thought Ubuntu has not been installed, but when I plugged in the USB drive and wanted to install Ubuntu I saw an option of reinstalling Ubuntu on my machine. So, I found out that Ubuntu is installed. Pressing F8 and F12 also does not help.

    Can anyone help me bring up the GRUB boot menu?

    In Windows, I also entered the command bcdedit /set path EFIubuntugrubx64.efi in cmd, but still the boot menu does not show up.


    Reply (Himanshu) :
    Just boot in bios and, if you can, add boot option with name say ubuntu and path EFI/ubuntu/shimx64.efi . No need for live PCB or anything. Move the boot option to top. This is for dell GUI bios but I assume it works for all. Or you may want to see this or this, where you can enable Windows Boot Loader for one boot or forever as you wish, and boot Ubuntu from it. If you want now, you can use the installed Ubuntu terminal to use the commands update-grub to use GRUB instead. (Not enough reputation to answer properly btw.)


    5 Answers 5

    WPKG makes for an excellent way of installing software. You can't just auto-click next, but its flexible enough to allow you to run msiexec for your silent install msi files as well as custom commands for whatever else you run.

    has information about application deploy, not all the software are in the list, but it's better than nothing.

    AutoIT is fantastic, there are others but i've set up many auto-installs with this.

    You would be better off setting up one machine, taking an image of it and deploying that image. There are numerous ways to do this. It's not practical to write a tutorial here but fortunately a lot of other people have already written them. A bit of Googling should turn up plenty of articles on the various deployment methods.


    3 Answers 3

    I'd go with the idea of creating an nLite'd XP disc. This gives you the most control over what is installed on the laptops on the first hit, and will minimize the number of visits to Windows Update, reboots and prompts along the way. It will also let you trim down the install footprint, and allow you to specify the common settings.

    First, determine the flavour(s) of Windows XP that you want to install on these 9 laptops. If you're considering making them all Pro or Home, then it's even less work for you. Each flavour would obviously need its own nLite'd disc.

    If I were doing this job, I'd do this:

    • inventory all the laptops with their model numbers
    • for each older model, download the drivers (Audio, (W)LAN, Video, Bluetooth, trackpad, webcam, etc, etc.) from their respective manufacturer web sites. If none are available, hope that XP has them built in.
    • consider downloading the power management tools as well
    • rip the Win XP install CD to a directory
    • nLite it along with XP Service Pack 3 - Lifehacker has details!
    • include the drivers from point 2 in the nLite image. Sure, all laptops will have them installed, but no biggie.
    • consider the option of writing your newly created ISO to a bootable USB thumb-drive. This will cut down the installation time vs. optical media. Of course you'd be dependent on the ability for those Win98 vintage machines supporting this. Even still, the time saved on those others would still make it worthwhile.

    There are a couple of methods you can use and for your situation I'd suggest either sysprep, of which I'm no fan, or an unattended install using an answer file. There's some very good documentation around for both. However, you may wish to reconsider, at least for those machines for which you have a recovery dics or partition.

    In addition to the install of Windows itself you have two issues to resolve. One is the Windows licensing, which is messy to say the least, and I'm going to leave that entirely up to you.

    The second is the hardware differences. You may run into some trouble here because Windows hardware support for laptops is downright pathetic. You might be lucky, but don't lay any bets on it. In many cases the only real hope you have is the laptop manufacturer's web site because too often generic drivers don't work very well, if at all, with laptops.

    If you thought a manual install of Windows on a few laptops was going to be slow, boring and time consuming, you're in for a real sad experience with some of those drivers. Install one and reboot. Install another and reboot. etc., etc., and that's after you are able to locate them at all. This is why recovery discs/partitions are so highly recommended.


    2 Answers 2

    A 64-bit operating system won't be able to run a 16-bit program unless you run the program through an emulator or a virtual machine. For more info, see these Super User posts:

    This question on Arqade: How to get old 16-bit Windows games to work on 64-bit Windows?, is similar to yours, but the solutions in the answers won't help since you can't run Windows XP mode in Windows 7 Home Basic / Premium.

    Use an emulator like DOSBox for 16-bit DOS games.

    Since NBA Live 98 doesn't seem to be a DOS game, you might want to try the emulator, Win3mu.

    Win3mu is a Windows 3.0 emulator. It includes an 8086 CPU emulation that loads 16-bit Windows executables and maps API calls onto the modern 32 or 64-bit Windows API.

    The website for Win3mu only offers a source code download. An installable build for Win3mu can be downloaded from https://github.com/Mwyann/win3mu/releases.

    Another alternative is to use a Virtual Machine (VM). A VM will allow you to run a 32-bit OS within 64-bit Windows 7. A VM software you might want to try is VirtualBox, which you can use to run Windows 7 32-bit, Windows XP 32-bit, or an even older Windows OS within Windows 7 Home Basic / Premium.

    The best thing to do is to get a 32-bit Operating System. This would most likely make the game compatible. I have tested this by running Zork on my 32-bit and 64-bit partitions. You can make two separate partitions.

    However, if you are not in a position to do this, you can make a Virtual Machine (VM) and put in a 32-bit operating system (does not matter which, does not matter what OS). However, if you are not the 'nerdy' type of person that's willing to be frustrated, this is probably not the option for you.

    Your third and final option is to use a DOS emulator, such as DOSBox, or one in a virtual machine (pure DOS). This is the best option since your game since to be for 16-bit operating systems, and pure DOS is 16-bit.

    Edit: If you have a copy of Windows 95, 98, or ME, this will be fine as well since these versions only have a 32-bit version.


    3 Answers 3

    I will try to answer your question as best that I can. It is a question of timing. By 2009, Apple was shipping Macs with firmware or offered firmware upgrades that allowed Windows to be installed in BIOS/MBR mode. This firmware is stored in your Mac. The firmware does not change when you upgrade to a new version of OS X. Therefore, the version of OS X currently installed has nothing to do with whether you can run Windows on your Mac. In fact, it is possible to run Windows on your Mac without any version of OS X installed.

    To install a particular version of Windows on a Mac, a few timing aspects need to be considered. The Windows installation DVD needs recognize your Macs hardware in order to install the drivers needed to install and boot to Windows. Since Windows XP was released in 2001, one should not expect the DVD (or maybe CD) to contain the drivers for the 2009 Mac models. Granted, to a certain extent, hardware can be designed to operate in a legacy mode in order to install an older operating system. When the difference is 8 years, this is difficult to do. Also, Microsoft installations allow for newer drivers to be introduced during the installation process, but this was never employed for Windows installations on Macs in 2009. Instead, Microsoft released Windows XP DVDs with Service Packs already installed. These newer DVDs contained the drivers need to allow Windows to install and boot on Macs. Once, Windows was up and running, better drivers could be installed to upgrade existing drivers and support other hardware such as the camera and sound. These drivers were part of a package referred to as "The Boot Camp Support Software". This software also provided a way to boot back to OSX and a utility to update Apple software such as iTunes. When "The Boot Camp Support Software" installs, the Windows partition is renamed BOOTCAMP. For this reason, it has become customary to refer to the Windows installation on a Mac as Boot Camp. In fact, you can rename the partition to anything after installing "The Boot Camp Support Software".

    Apple's web site says you can install Windows XP on your Mac. Whether you need SP2 or SP3 included on the DVD is just a matter of timing. I do not have an answer. SP2 was released in 2004 and SP3 can out in 2008. Since SP3 was the last offered for XP, such a DVD should work for you.

    Although your question did not ask about installing a newer version of Windows, I will include my thoughts anyway. Generally, Microsoft does not require new drivers for each release of Windows. For example, when upgrading Windows, the newer version just adopts the drivers from the previous version. Also, Microsoft may offer new drivers though Windows Update. Windows 10 appears to have he ability to connect to the internet and download drivers during the installation process.

    Apple's web site reports your Mac can only run 32 bit XP, Vista and Windows 7. This probably is not true. You have a 2.0 GHZ Core 2 Duo 2.0 processor. I am writing this answer on a 2007 iMac with a 2.4 GHz Core 2 Duo processor. The operating systems is Windows 10 Pro 64 bit. Apple is not entirely wrong. The Boot Camp Assistant will not let you install the newer Windows operating systems, but you don't have to use the Boot Camp Assistant. I guess your complaint is the Boot Camp Assistant version that comes with El Captain OS X 10.11 will not let you install the older XP operating system. Again, the Boot Camp Assistant is just an assistant used to make windows easier to install. It does not have to be used.