All, If any of you are running Win7 guest in virtualbox, I'm trying to nail down an issue and need some help. I basically keep a win7 guest on the server to access over the LAN with the --headless option to use to answer coding questions involving MinGW or VS. I have used this setup since Virtualbox 4. With the update to Virtualbox 6.0.0, the Command Prompt in the Win7 guest is rendered all but unusable. Something has changed that effects the ability to 'redraw' the terminal as lines are output (slowing output to that of a Dot-Matrix printer) Attempting to move the command prompt window (or PowerShell window) similarly results in artifacts left of the desktop which are slowly repainted to complete the move. I'm working the issue on the vbox-users-community list and I could use some additional input. With my setup I launch the Win7 guest while ssh'ed into the host server with: VBoxManage startvm Win7Pro_32bit --type headless (if needed I set the resolution for the guest with) VBoxManage controlvm "Win7Pro_32bit" setvideomodehint 1440 864 32 (I have done it this same way for years) With the install I have with vbox 5.2.22, there is no problem with the Command Prompt 'dir' listing in the Win7 guest. With 6.0.0 it takes 20.5 seconds to list 176 files (do you know how long 20.5 seconds is just waiting for a short directory list to complete is? -- it's really long) So does anyone else use Virtualbox to access headless windows 7 guest via their LAN? If so, open a Command Prompt and change to a directory with a 100 files or so and type 'dir' and let me know if it takes a painfully long time to complete while spiking the CPU usage by 40-50%. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org