Page 1 of 1
Windows2000 Screen artifacts
Posted: 25. May 2009, 02:55
by kihjin
Hi,
Using virtualbox 2.1.4 here. Host is ubuntu x64 8.10
I've installed both Windows 2000 and Windows 2000 server. In both installations, during the install (and after) the screen has artifacts.
when connecting over RDP the mouse tracking isn't quite correct. Actually, mouse tracking is absolutely not correct. The RDP shows two mouse cursors with the actual and simulated mouse obviously not matching up.
I've tried this on two machines with the same result. Anyone else experience this or know what I can do to fix it?
Thanks.
Re: Windows2000 Screen artifacts
Posted: 25. May 2009, 03:17
by Perryg
There were problems discussed with earlier versions of VBox and different screen problems. Repairs were made but I do not remember which version. I am fairly sure that by version 2.0.0 it was but that version had problems of a different kind. The newest version 2.2.2 should fix this for you though. Also if you have not you should install the guest additions. This could help as well.
Also if you could give more information when you create posts it would really help to figure out the problem. As a rule all of the guest settings, host memory, and versions are a must.
Re: Windows2000 Screen artifacts
Posted: 25. May 2009, 03:49
by kihjin
Hi Perry, thanks for the reply.
Host Machine 1: Ubuntu 8.10 x64, 6GB RAM, AMD Phenom(tm) 9850 Quad-Core Processor
Host Machine 2: Ubuntu Server 8.04.1 x64, 4GB RAM AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
As noted in my original post, the behavior was experienced on both systems with VirtualBox 2.1.4 PUEL
Guest settings:
Host 1
Code: Select all
$ VBoxManage showvminfo windows2000
VirtualBox Command Line Management Interface Version 2.1.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
Name: windows2000
Guest OS: Windows 2000
UUID: a30d9763-ac1b-4158-91dc-259dc3ec7fbf
Config file: /home/------/.VirtualBox/Machines/windows2000/windows2000.xml
Memory size: 500MB
VRAM size: 28MB
Boot menu mode: message and menu
ACPI: on
IOAPIC: off
PAE: off
Time offset: 0 ms
Hardw. virt.ext: on
Nested Paging: on
VT-x VPID: off
State: powered off (since 2009-05-25T00:57:55.529000000)
Monitor count: 1
3D Acceleration: off
Floppy: empty
SATA: disabled
IDE Controller: PIIX4
Primary master: /home/----/.VirtualBox/HardDisks/windows2000.vdi (UUID: 24b812af-d02e-41e4-910a-4a331aa8ab1a)
DVD: none
NIC 1: MAC: -------, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
UART 1: disabled
UART 2: disabled
Audio: disabled (Driver: Unknown, Controller: Unknown)
Clipboard Mode: Bidirectional
VRDP: enabled (Address 0.0.0.0, Port 3389, MultiConn: off, ReuseSingleConn: off, Authentication type: null)
USB: disabled
$ VBoxManage showvminfo windows2000server
VirtualBox Command Line Management Interface Version 2.1.4
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.
Name: windows2000server
Guest OS: Windows 2000
UUID: f6a8c3fd-0943-4b63-81c3-66030afe1861
Config file: /home/-----/.VirtualBox/Machines/windows2000server/windows2000server.xml
Memory size: 500MB
VRAM size: 21MB
Boot menu mode: message and menu
ACPI: on
IOAPIC: off
PAE: off
Time offset: 0 ms
Hardw. virt.ext: on
Nested Paging: on
VT-x VPID: off
State: powered off (since 2009-05-25T00:57:06.583000000)
Monitor count: 1
3D Acceleration: off
Floppy: empty
SATA: disabled
IDE Controller: PIIX4
Primary master: /home/-----/.VirtualBox/HardDisks/windows2000server.vdi (UUID: 89131631-ec37-414a-933c-62ffcd601dad)
DVD: None
NIC 1: MAC: ------, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
UART 1: disabled
UART 2: disabled
Audio: disabled (Driver: Unknown, Controller: Unknown)
Clipboard Mode: Bidirectional
VRDP: disabled
USB: disabled
Host 2
Code: Select all
Name: ----
Guest OS: Windows 2000
UUID: 4ba8019a-4369-4de8-9132-c8851d9229be
Config file: /home/----/.VirtualBox/Machines/----/----.xml
Memory size: 512MB
VRAM size: 32MB
Boot menu mode: message and menu
ACPI: on
IOAPIC: off
PAE: off
Time offset: 0 ms
Hardw. virt.ext: on
Nested Paging: on
VT-x VPID: off
State: aborted (since 2009-05-25T00:09:10.021000000)
Monitor count: 1
3D Acceleration: off
Floppy: disabled
SATA: disabled
IDE Controller: PIIX4
Primary master: /home/----/disks/-----/disk.vdi (UUID: bbb7b61c-e919-4991-843a-58dc7e326609)
DVD: empty
NIC 1: MAC: -----, Attachment: Host Interface 'eth0', Cable connected: on, Trace: off (file: none), Type:
Am79C973, Reported speed: 10 Mbps
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
UART 1: disabled
UART 2: disabled
Audio: disabled (Driver: Unknown, Controller: Unknown)
All this aside, as far as you know, VirtualBox should support windows 2000 pro and server out of the box with no additions?
I'll have to get around to upgrading to 2.2.2. I wasn't looking to do that just yet, I'd really like to upgrade in a sandbox environment and test it out first. How well does running a vm in a vm work?
Re: Windows2000 Screen artifacts
Posted: 25. May 2009, 04:17
by Perryg
I installed it and it worked fine for me. I did see some tearing before I installed the Guest Additions but nothing like what you are showing. I think it was on 2.14 or earlier as well, not sure about that though because it has been a while. I can say without a doubt that mine is clean and doing fine with Ver. 2.2.2.
I also have 2000 Adv Serv. with no problems.
Unfortunately a vm in a vm will not work.
Re: Windows2000 Screen artifacts
Posted: 25. May 2009, 05:45
by kihjin
I can confirm that 2.2.2 does fix the screen tearing issue with Windows 2000 server. Additionally, this fix doesn't require guest additions.
However there mains a problem which was present in 2.1.4.
Over RDP, there are serious mouse problems. For one, two cursors appear on the screen; one for the host and one for the guest. These cursors don't line up properly.
What makes this situation stranger is that in the Qt GUI, there are no cursor problems.
I installed guest additions to see what would happen. The cursor issues over RDP went away.
Does this inconsistency between non-GA RDP and non-GA Qt GUI with regards to the mouse cursor make sense? I suppose since GA fixes this, it might be a moot point.