How To Install Windows 2000 On Virtualbox Vs Vmware
Starting position: there is an old computer with Win2K on board. Some ancient and hard-to-get programs are installed on it. Their installation disks had been lost long ago, so they cannot be reinstalled on a new operating system, and their compatibility with even WinXP is in doubt. In addition there is the newly obtained machine with cool i7 processor and pre-installed Windows 7. Objective: to get rid of that old computer, retaining the old programs with all their settings.Solutions:1. Migrating Win2K as a second system to the new computer with multiboot.
Create a new logical drive, clone Win2K on it, install a boot manager on Win7 (eg, free EasyBCD), solve the problem of compatibility with the SATA AHCI and other drivers. Undoubted disadvantage of this option is the need to unload each OS to run another one, and it's provided that drivers for a very old system on modern hardware are found. And also the installation of a SATA controller drivers using Intel Matrix Storage is still dancing with a tambourine, and not the fact that it will go through.2. Porting to a virtual machine. In my opinion - the best option. But it may encounter pitfalls, and this article is devoted to the matter how to overcome all of them.I've been using VMWare Workstation and consider it very good tool. The benefits of virtual machines are well known - the presence of multiple operating systems (clients) on a single physical computer (host) with simultaneous use of them and the host, network connection between themselves and the physical machines and sharing host's resources, devices and ports.
Step 2: Install VirtualBox in Ubuntu and Linux Mint. It is very easy to install VirtualBox in Ubuntu. All you need to do is to use the command below: sudo apt install virtualbox Step 3: Install Windows 10 in VirtualBox. Start VirtualBox. You should see a screen like the one below. Even though VirtualBox now supports VmWare's open vmdk disk format, this creates a couple of complications: Windows 2000. Your original Windows 2000 boot CD or ISO image; A Windows 2000 CD Key; The administrator password for your Windows 2000 install (This may not be required, see below).
I've also tried Virtual PC and VirtualBox, but stopped at VMWare - it seemed most convenient. In addition, there is VMWare Player - a free version of VMWare Workstation with slightly truncated functionality. Therefore, I will describe the process of migration to VMWare.At the time, I have successfully transferred the Windows XP on VMWare machine using VMWare Converter. However, in this case, several different versions of the converter failed with conversion error. So, I had to find some unconventional solution.The process described below is suitable for migration Win2K as well as WinXP.Disclaimer: all done by you at your own risk. In the event of a material or moral damage the author puts his hands in his pocket;))So: the host - a new PC running Windows 7 64 bit, straight from the tin (at the time of writing) VMWare Workstation 8.0.2 it installed.
What else to have before the process:1. Utility to create and restore the image and clone partitions and disks (Acronis True Image, Symantec Norton Ghost (both are commercial), Clonezilla (free), etc.). I've used the first one, and for brevity I will call it just 'Acronis'.2. Windows 2000 or XP installation (CD or ISO-image) - to work with Recovery Console.3. Floppy image with the SCSI driver for VMWare (available for downloading or ).4. Update KB835732 (Microsoft online: Win2K -,; WinXP -, ).5.
External USB HDD (if while transferring system (step 3) you are using method 1) or IDE to USB adapter or enclosure (method 2).Step by step:1. Preparing Win2K to transfer.a. Make sure SP4 is installed. Does not hurt to install all other updates.b. Download KB835732 proper for your OS and copy it to the root (or other easily accessible folder) of the system disk.2. Creating a new virtual machine. Choose Windows 2000 Professional on a suggestion to select the operating system for the VM ( Select a Guest Operating System). When asked about the maximum amount of disk I set 40 GB as such was the size of the physical disk with Win2K, and it was filled with more than two-thirds.
Windows Virtualbox Images
The rest of the settings may stay default. After reaching the screen Ready to Create Virtual Machine, click the button Customize Hardware. And change the type of New CD/DVD from the default IDE to SCSI. If you leave IDE, the system won't mount the virtual CD/DVD needed to install VMWare Tools after the first successful run. Later after installing the VMWare Tools, and, accordingly, all virtual drivers, you can change the type back to IDE.3. Transfer content of the physical disk to the VM virtual disk. There are several ways:Method 1:a. Use Acronis to create image of the physical disk with Win2K and copy the image to an external USB drive.
Program facut stampile rotunde. Plug this drive to the host.b. Start the virtual machine from a CD or Acronis image, and in the menu VM Removable Devices find our external drive and click the submenu Connect (Disconnect from Host).
The disk will now be recognized by Akronis.If Acronis is booted from ISO-image, this image must be on a disk other than that connected external drive, because we are disconnecting it from the host.c. Restore the image to a virtual disk.Method 2:a. Remove the original hard drive from the old computer, connect it as an external (via adapter or enclosure) to the host.b. The same steps as in part b of Method 1.c. Clone the content of the physical disk (or move only necessary partitions) to the virtual disk.The first method only requires an external drive (or even a big and quick stick, that is not unusual in our time). If you don't have an IDE to USB adapter or lazy to dismount the original drive, it's preferred. And additional system backup can not hurt.
Disadvantage: if the old computer only has USB1.1, the process of image creating might be long. Well, run it on the night!Chance is a third way - to work directly with a physical disk from the VM. Dismount the disc from the old machine, connect it to the host as either internal or external, and mount as virtual in the VM. This method is more tedious, since the letters of all partitions should be removed before mounting to prevent concurrent access to the disk of the host and VM, and at the very mounting - identify disk in the list of species like PhysicalDrive0, PhysicalDrive1 etc. If it came to remove the drive, the second method of transfer would have been better.
This third way - only for those who have no place on the new computer (the host), and who is going to run a VM with a physical disk constantly.4. Running a virtual machine - the system goes into BSoD with the message:Inaccessible boot device.This happens due to the fact that the disk in VM is connected to a virtual SCSI controller, and the system has no appropriate driver. You can solve this problem by replacing the IDE atapi.sys driver file with a file having the same name, but containing a virtual SCSI controller driver for VMWare. This trick will cheat the system at boot time by putting the right driver with a name corresponding to the settings in the registry.a.
Insert Win2K/WinXP installation disk in the CD/DVD-ROM and specify CD/DVD setting to use physical drive, or mount the ISO image of this disk to the virtual machine's drive. Mount floppy image of SCSI driver for VMWare into the virtual floppy drive.
Windows 8.1 Iso For Virtualbox
Check the checkboxes Connect at power on in the Device status section for both of the above virtual devices.b. Start VM from CD/DVD (assign boot sequence in BIOS of virtual machine once and for all, or else press Esc after powering on the VM and select CD-ROM drive). The process of Windows installation will start.
Open Recovery Console, choose our system, and the system folder C:WINDOWS or C:WINNT will appear in the command prompt. Type the following code. Cd SYSTEM32DRIVERSdel atapi.syscopy a:vmscsi.sys atapi.sysYou can skip the second line, then agree to overwrite the existing atapi.sys.All of the above applies to the case when the old drive is of IDE type. If it is connected to the SCSI or SATA controller, atapi.sys could not be used. Need to determine, which file contains driver of the controller of your disk type and replace it with vmscsi.sys. Recovery Console command LISTSVC that produces a list of system services can help to identify the driver file.
It must be treated in the category Boot (2nd column).c. Restart the VM by typing exit at the command line. This time the system is booting successfully.It is worth noting that the system after its startup replaces the fake IDE driver back with the original one, so in case of rebooting without installing the driver VM SCSI controller, the blue screen comes back. That's why I rejected all offers of the system to manually install drivers and to reboot and in the first place installed the driver of SCSI Controller in Device Manager from the same floppy. Now reboot is not fraught with the blue screen, and the system starts up successfully (but still had to reboot once, as below). If you accidentally restarted VM and got BSoD again - repeat Step 4.5.
Installing VMware Tools. Run - and get this message:Microsoft Runtime DLLs cannot be installed on this operating system. Please see Microsoft KB835732 for details.Install update KB835732, reboot (now you can), and VMware Tools are being installed without problems. Hooray, we have successfully moved into a virtual machine!By the way, not the fact that a similar problem with the installation of VMware Tools will pop up in your case. Especially if, as I mentioned at the beginning, all the updates were installed in the original system before the transfer. Nevertheless, have KB835732 at hand, and it is desirable - right on the drive for easy access.
I don't know what I am doing wrong, but I just can't install Windows 98 SE or 2000 in Virtualbox.My OS is Vista Home Premium.I've spent hour and hours trying to install Windows 98, but keep getting the same error. Tried 3 different Win98 images, an endless amount of settings, guides, but nothing helped. See this topic:Then I stopped trying and instead tried to install Windows 2000. This won't work either. It looked as if it worked fine when installing, but right when I have chosen time/date format, etc. As it is doing the final installation it restarts and I have to choose the time/date settings, etc.
Again, and it restarts at the same point again, and so it cycles if I keep trying.Also, while trying to install Windows 2000 I have tried many settings and followed guides - but I just can't get it to work no matter what I try!What am I doing wrong?!I am new to this forum, so if you need any information that I haven't written please let me know. Posts: 8 Joined: 5. Jul 2009, 01:56 Primary OS: MS Windows Vista VBox Version: OSE other Guest OSses: Windows 98. Well the Win98 is a different thing. You should just forget it because even if you are able to get it installed you have to hack it to make it work on the newer machines that we have today.As for the Win 2000, pro, and Advanced that is a different story. I installed it by using the dynamic disk and setting the max to 16 GB then I set the RAM to 128Meg and Video to 10 Meg. My install was from a real Windows install CD and not an image though and it is possible that the image you have is corrupt or for an OEM install which means it could be looking for something that it was supposed to see.
Out of curiosity where did the image come from? Site Moderator Posts: 34373 Joined: 6.
Sep 2008, 22:55 Primary OS: Linux other VBox Version: OSE self-compiled Guest OSses:.NIX. Ok, I have tried many settings, so it can be that the image is currupted. But this also sounds wierd to me, since I created the image myself from an old windows cd (i am not using any dvd/cd drive on my computer, so I always create images of the things I need on another machine to use on my own).But I have only tried one win2000 though, I will see if I can get another and try, but I would be surprised if it works. Posts: 8 Joined: 5. Jul 2009, 01:56 Primary OS: MS Windows Vista VBox Version: OSE other Guest OSses: Windows 98. Perryg wrote:Well the Win98 is a different thing.
Install Windows 2000 Free
You should just forget it because even if you are able to get it installed you have to hack it to make it work on the newer machines that we have today.Sorry to interrupt, but:Why do you believe it is necessary to have to 'hack' Windows 98 in order to get it to run in a virtual machine? Isn't one of the functions of a virtual machine software like VMware Workstation or Virtualbox to enable us to run other, including older OSs, even on the new computers today?Windows 98 is old, no doubt about it. But it is not 'that' old. VMware Workstation (4, 4.5, 5, 5.5, 6 and now 6.5) has always been able to install Windows 98 without any problems, as long as you keep in mind the limitations, such as the fact that you cannot install Windows 98 on a virtual machine with more than 512MB RAM. I have 2 Windows 98 virtual machines on my computer with Windows XP x64 as host and running VMware Workstation 6.5, and they work fine. I can run some old games in them such as Legend of Galactic Heroes IV (Chinese) which runs properly only under Windows 95 or 98.If Virtualbox cannot run Windows 98 properly inside a virtual machine, then I would say this is a problem with Virtualbox itself, not with the computer, as VMware Workstation has been able to do this all the time.
VMware Workstation also has VMware Tools support for Windows 98 as well.To run a Windows 98 virtual machine I would suggest a maximum of 512MB RAM, a 2GB hard disk image, and disabling USB support in the virtual machine, for a start.