Does Getting Polyps Removal Hurt

Virtual Box - XP with Ubuntu as host

I would like to summarize some issues and tips, which at the operation of Windows XP in a VirtualBox unbuntu occurred.

• "shared folder" to make a few issues that would be:
  
  • USB stick is not fully accessible
  • with some CAD programs can not access files in shared folders
• to access directories on the host system to be able to recommend the following procedure which can be completely dispensed with the shared folders.
  
  • network login on the Ubuntu host system
  • USB flash drive in the host system combine happens (
    automatically in the directory / media / NamedesUSBSticks
  • second network card for VirtuelleBox as the only host adapter (eg vboxnet0)
  • Samba share on the root directory for the interface vboxnet0 like. in this file / etc / samba / smb.conf:

       #======================= Global Settings ========= 
     ============== [global] workgroup = WORKGROUP 
     
     server string = host 
     wins support = yes dns proxy = no 
     
     
     interfaces = 127.0.0.0 / 8 bind interfaces vboxnet0 
     only = yes 
     
     log file = / var / log / samba / log. 
    % m max log size = 1000 syslog = 0 
     
     panic action = / usr / share / samba / panic-action% d 
       
     unix extensions = no 
      
     ####### Authentication ####### 
     security = user 
     encrypt passwords = true 
     passdb backend = tdbsam 
     obey pam restrictions = yes 
     unix password sync = yes 
     passwd program = /usr/bin/passwd %u 
     passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . 
     pam password change = yes 
     map to guest = bad user 
      
     ########################## SHARES ###################### 
     # share für virtualbox 
     [datenaustausch] 
     comment = data exchange 
     path = / 
     browseable = yes 
     read only = no 
     # User for Samba login 
     valid users = vbox 
     write list = vbox 
     # Local users for the local permissions on the Linux system 
     force user = htl 
     force group = htl 
     guest ok = no 
       

    After changing your smb.conf always restart the Samba server with "/ etc / init.d / smbd restart"
    Caution! The Samba server is allowed to work only on the host-only adapter, otherwise anyone can access with the specified user on the network to all connected drives on the user!
  • create a Samba user in Linux (Here for users vbox)

       sudo useradd-m sudo passwd vbox vbox 
     
     sudo smbpasswd-a vbox 
       

  • connecting the drives required by the host in a startup script that with "gpedit.msc" at the user's Login is started. The correct IP address depends on the host-only adapter and is usually for the first adapter 192.168.56.1
    

       net use Z: \\ \\ 192.168.56.1 \\ data exchange password / USER: vbox / PERSISTENT: NO net use 
     I: \\ \\ 192.168.56.1 password \\ data exchange \\ home \\ htl / USER: vbox / PERSISTENT: NO 
       

  • At startup, the Virtualbox host-only adapter and then start the Samba server. The best in the file / etc / rc.local:
    

       VBoxManage hostonlyif vboxnet0 ipconfig - ip 192.168.56.1 
     / etc / init.d / smbd restart does not   



• at VBox USB 4.0 more: In
  / etc/udev/rules.d/10-vboxdrv.rules MODE = "0600" to MODE = "0666" Change
• Serial port COM1 for Windows XP guest system setup:
  • In the VM settings under serial interface:
    - serial interface enable
    - Port Number: COM1
    - Port Mode: Host interface
    - Port / File Path: / dev/ttyS0
    

  • In the windows box:
    - Control Panel
    - Hardware
    - Hardware is already connected
    - At the bottom of the list "Add New Hardware
    - select device manually
    - Ports COM and LPT
    - communication ports
    -> COM 3 is provided from installing, but leave still stand, then again,
    - Control Panel
    - Hardware
    - Hardware is already connected
    - At the bottom of the list in "Add New Hardware
    - Hardware automatically
    -> then should Com1 In Device Manager to be understood and also work
    

• reduce vdi -> instructions