Similar Questions

• How to solve the problem of VMWare Workstation 8 - unable to open/dev/vmmon

  Initially, I had this problem in March 2011 after installing VMWare Workstation 7 on a lab machine 5.7 RHEL and attempt to boot an image I know was good and should work. .  Someone else fixed the problem for me - I think they had to install a new/different libraries (vmmon.o and vmnet.o for vmware).  However, I find no information detailing what has been done to solve the problem.

  I see the same error on the same machine after upgrading to VMWare Workstation 7.0 for VMWare Workstation 8.0.

  1 here are the mistakes I see:

  a. "Could not open/dev/vmmon.

  b. "failed to initialize the surveillance apparatus.
  c. "cannot change the power state of VM: cannot find a valid peers to connect to.

  Also, when I run the stop etc/init.d/vmware, then run /etc/init.d/vmware start, I see that the State of "Virtual Machine Monitor" is DOWN.

  
  2 here is the information on VMWare Workstation:

  VMWare Workstation 8.0.1 build 528992

  3 here is the RHEL uname - information for the host:

  2.6.18 - 274.7.1.el5xen Linux #1 SMP xxx.xxx.xxx kills Oct 17 12:06:22 EDT 2011 x86_64 x86_64 GNU/Linux
  Release of RedHat Enterprise Linux Server 5.7 (Tikanga)

  The problem could be that the version of vmmon.o and vmnet.o that comes by default with vmware does not work with linux kernel version I have on my system.  I think I need to build a new vmmon.o and vmnet.o on my particular 5.7 RHEL.

  I found that to build a new version of vmmon.o you Executive vmware - config.pl.  I have not just on my machine, and I was not able to find on the internet.

  Here is the version of vmmon.o (for RHEL 5) that I have installed on my machine:
  /usr/lib/VMware/modules/binary/BLD-2.6.18-8.EL5-x86_64smp-RHEL5/objects/vmmon.o

  Here is the version of rhel5 I use:
  2.6.18 - 274.12.1.el5xen
  It is possible that the vmmon.o using bld - 2.6.18 - 8.el5 - x86_64smp-RHEL5 is not compatible with the kernel 2.6.18 - I 274.12.1.el5xen.

  Please help me find vmware - config.pl so I can build my own vmmon.o and vmnet.o

  do not use a kernel XEN enabled when you install Workstation

• I'm unable to open one of my 'recent documents' document. It is said to make sure that the network resource is available.

  Original title: "Recent Documents".

  I'm unable to open one of my 'recent documents' document.  It is said to make sure that the network resource is available.  What does that mean?  And I can't find the document in "My Documents" is.  And I tried a search.

  Hello

  The error means either that the document no longer is located in the folder it was when it was finally opened or the location that the file was initially located in is no longer in the same place.

  Example 1: I open a document in the My Documents folder, then after closing the document, I moved manually the file to the desktop.

  Example2: I open a document located on a removable hard drive. After the closure of the paper, I then disconnect the removable hard drive of the PC.

  In these two examples, Windows would be able to find the Document using the "Recent Documents" list

  Step 1: I recommend that you check the trash or see if the document is located on a removable hard drive (or USB key) that is is more attached to the computer.

  Step 2: Use recovery software of the third party to recover the document.
   
  THIRD WARNING:
  Using third-party software, including hardware drivers can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee that problems resulting from the use of third-party software can be solved. Software using third party is at your own risk.

• VMware Workstation 9: could not open/dev/vmmon: no such file or directory

  I'll have a plethora of problems installing and get VMware Workstation 9 (9.0.2 build-1031769) to work on Ubuntu 13.04 (kernel 3.8.0 - 26-generic).

  I experienced exactly the same process on my laptop and it works perfectly, while on the desktop, it seems that everything breaks. Could someone give me some kind of help / advice on how I can do to get this working. I tried full uninstall / reinstall of the software, headers of the kernel, kernel images, different kernels, patches here on fresh installs of everything I can think of. Here are the issues I encounter in the order of importance (or so I think):

  (1) whenever I try to open my new (and virtual) machine, I get the error sequence of:

  "Could not open/dev/vmmon: no such file or directory. " Please make sure that the "vmmon" kernel module is loaded. '--> 'Failed to initialize the device monitor. "->" cannot change the power state of VM: could not find a valid peer to connect to '

  
  

  (2) every time I try to run the following command to configure the modules on a completely fresh setting (reinstalled kernel, vmware) I get the following output:

  sudo modconfig vmware - console - install-all

  Stopping VMware services:

  Demon of authentication makes VMware

  VM communication interface socket family is

  Virtual machine communication interface is

  Virtual machine monitor makes

  File system is blocking

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmmon-only '.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/driverLog.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/linux/hostif.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/apic.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/comport.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/cpuid.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/hashFunc.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/memtrack.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/phystrack.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/task.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/common/vmx86.o

  CC [M] /tmp/modconfig-G9S0TM/vmmon-only/vmcore/moduleloop.o

  LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmmon-only/vmmon.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmmon-only/vmmon.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  CP f vmmon.ko. /... vmmon.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmmon-only '.

  Using 2.6.x kernel build system.

  make: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only»

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/hub.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/userif.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/netif.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/bridge.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/filter.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/procfs.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac_compat.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/smac.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetEvent.o

  CC [M] /tmp/modconfig-G9S0TM/vmnet-only/vnetUserListener.o

  LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmnet-only/vmnet.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmnet-only/vmnet.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  CP f vmnet.ko. /... vmnet.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmnet-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmblock-only.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/block.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/control.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/dentry.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/file.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/filesystem.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/inode.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/stubs.o

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/module.o

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c: in function 'ExecuteBlockOp ':

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:285: warning: assignment of incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/control.c:296: warning: passing argument 1 of the "putname" incompatible pointer type

  include/Linux/FS.h:2052: Note: expected ' struct filename *' but argument is of type ' char *'

  CC [M] /tmp/modconfig-G9S0TM/vmblock-only/linux/super.o

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/inode.c:49: warning: initialization from incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:38: warning: initialization from incompatible pointer type

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c: in function 'DentryOpRevalidate ':

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: warning: argument passing 2 of 'actualDentry-> d_op-> d_revalidate' makes whole pointer without a cast

  /tmp/modconfig-G9S0TM/vmblock-only/Linux/dentry.c:104: Note: expected 'unsigned int' but argument is of type ' struct nameidata *'

  LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!

  Warning: "putname" [/ tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmblock-only/vmblock.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmblock-only/vmblock.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  CP f vmblock.ko. /... vmblock.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmblock-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vmci-only.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/driver.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/linux/vmciKernelIf.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciContext.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDatagram.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDoorbell.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciDriver.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciHashtable.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciEvent.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQPair.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciQueuePair.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciResource.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/common/vmciRoute.o

  CC [M] /tmp/modconfig-G9S0TM/vmci-only/driverLog.o

  LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vmci-only/vmci.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vmci-only/vmci.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vmci-only/vmci.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vmci-only.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.

  CP f vmci.ko. /... VMCI.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vmci-only.

  Using 2.6.x kernel build system.

  do: enter the directory "/ tmp/modconfig-G9S0TM/vsock-only '.

  / usr/bin/make /lib/modules/3.8.0-26-generic/build/include/ - c... SUBDIRS = $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = modules

  make [1]: Entering directory ' / usr/src/linux-headers-3.8.0-26-generic'

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/af_vsock.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notify.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/notifyQState.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/stats.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/util.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/linux/vsockAddr.o

  CC [M] /tmp/modconfig-G9S0TM/vsock-only/driverLog.o

  LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.o

  Construction modules, step 2.

  MODPOST modules 1

  Warning: "mcount" [/ tmp/modconfig-G9S0TM/vsock-only/vsock.ko] undefined!

  CC /tmp/modconfig-G9S0TM/vsock-only/vsock.mod.o

  LD [M] /tmp/modconfig-G9S0TM/vsock-only/vsock.ko

  make [1]: leaving directory ' / usr/src/linux-headers-3.8.0-26-generic'

  / usr/bin/make - c $PWD SRCROOT = $PWD. \

  MODULEBUILDDIR = postgeneration

  make [1]: entering directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  make [1]: 'postgeneration' is up-to-date.

  make [1]: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  CP f vsock.ko. /... vsock.o

  make: leaving directory ' / tmp/modconfig-G9S0TM/vsock-only '.

  Starting VMware services:

  Virtual machine monitor failed

  Virtual machine communication interface failed

  Family of VM communication interface socket failed

  File system is blocking

  Virtual Ethernet failed

  Demon of authentication makes VMware

  Cannot start the services

  (3) I often get the Ubuntu "this program has planted" messages on "/ usr/lib/vmware-installer/2.1.0/vmis-launcher" "' (this message of crash always occurs when you run the"vmware-modconfig"above command on a new installation.

  (4) at different times during Assembly and have VMware workstation on my system I get Ubuntu hangs on "/ usr/lib/vmware/bin/appLoader" and even "/ bin/su" (especially when you are trying to install - su NEVER blocks anywhere else).

  Thoughts / ideas on what is happening on earth / what could have caused this all go so downhill / how to go about fixing?

  Thank you

  Solved.

  The problem is that for another program I used gcc - 4. 4 instead of later. Restore the (by update-alternatives - config ) for gcc, g ++ and CPC - bin.

  Not a very graceful exit to have a version not valid I would say, maybe some sort of basic check could be added to ensure that the correct versions are present?

• Error: "VMware Workstation has suspended this virtual machine because the disk on which the virtual machine is stored is almost full."

  I get this error message:

  VMware Workstation has suspended this virtual machine because the disk on which the virtual machine is stored is almost full. To continue, free 1.3 GB of additional disk space.

  I read up on the subject and found that I have to re size a partition. Anyone know what it could be? I can't find anything that looks like it has something to do with VMware. Does anyone know what size and what file system is it?

  My OS:
  Tumbleweed OpenSUSE x 64

  Thanks in advance

  On more creative, my home and root file systems were not extended to my full disk space :^)

• Since the last refresh of my payment for Adobe enjoy cloud data, I was not able to use the software, not Eve open one of the applications, even the payment has been made and saved to my banck account. I have been a month without service and I

  Since the last refresh of my payment for Adobe enjoy cloud data, I was not able to use the software, not Eve open one of the applications, even the payment has been made and saved to my banck account. I have been a month without service and I've not found a way to communicate directly with any responsible for Adpbe, nor received any satisfactory support of any kind. How can solve this problem? Is it possible to have a personal contact to have a personal support, instead of a jungle of pages on the web that will lead you to more of the same pages?

  The CC is waiting for bank payment, if payment is declined then CC will be suspended.

  Concerning

  Stéphane

• Urgent! How to open one of the last update of the project in an earlier version first?

  How to open one of the last update of the project in an earlier version first?

  
  

  I can't open a project that was saved in the latest version of first. My version is earlier than that of the project that have been saved

  Hello

  So far, backward compatibility is not available in Premiere Pro.

  Export your project as a FCPXML of the new version of first and try to import in the previous version.

  Kind regards

  Ilyes Singh

• Unable to manage one of the plugin

  Hello

  Unable to manage one of the plugin in my vcenter. I uninstalled the plugin, but it is not removed from Vcenter. can someone help me here

  Hello

  Find below KB 1025360 steps to solve the problems of your plugin.

  To remove the unwanted plug-ins in the list of Plug-ins available:

  1. In a web browser, go to http://vCenter_Server_name_or_IP/mob.

     VCenter_Server_name_or_IP/fmt is the name of your server vCenter or its IP address.

  2. Click on content.
  3. Click ExtensionManager.
  4. Select and copy the name of the plug-in to remove from the list of values under Properties. For a list of default plugins, see the more information section of this article.
  5. Click UnregisterExtension. A new window appears.
  6. Paste the name of the plug-in, and then click the Invoke method. This command deletes the plug-in.
  7. Close the window.
  8. Refresh the window of Managed Object Type: ManagedObjectReference:ExtensionManager to check that the plugin is deleted successfully.

  Note: If the plug-in still appears, you may have to restart the vSphere Client.

• VMware workstation - PCI switch to OS to solve the lack of host riders invited

  Hi all

  I'm quite new to VMware applications.

  To implement PCI passthrough / directly access hardware PCI by the host OS

  is it possible to just use VMware Workstation? or VMware ESXi OS is necessary?

  In this case:

  -The machine physics processor and card motherboard BIOS supports virtualization.

  -The host OS is Windows 7 64 bit.

  -A PCI card is interrupted and got only Windows XP / Vista drivers (the two 32-bit).

  -VMware Worstation 8.0 running in the host operating system.

  -VM guest OS is Windows XP (32 bit).

  Can I somehow configure direct access to the virtual machine PCI card / guest OS?

  I think that would solve a lot of pilot uncompatibility between 32/64 bit OS versions;

  It would be useful to have work directly in the VMware workstation.

  Or is it now possible only with OS ESXi and is rather simple to use here?

  Thank you very much for the support.

  LD

  VMware Workstation isn't compatible PCI Passthrough, you must run ESX or another product to make it work.

  Linjo

• BUG: Breaks VMware Fusion when there is free space on the host < 1.9 GB... result = > 1,9 GB never use for anything! (note: I do not use a virtual disk!)

  Hello

  first some info on my system:

  -

  ---

  MacBook Pro

  Processor: Core 2 Duo 2.2 GHz

  RAM: 4 GB

  HARD drive: 112 Go - 2 partitions (80 GB Mac OS x 10.5.6 32GB, Windows XP)

  ---

  VMware Fusion version: 2.0.4 (other affected versions 2.0.3/2.0.2/2.0.1/2.0)

  Allocated to the virtual machine RAM: 1.5 GB

  Under Windows XP in VMware (boot_camp) partition separated - NO VIRTUAL DRIVE! -separate the NTFS partition.

  -

  ---

  Now the bug/problem:

  Every time that free up disk space on the host partition (MacOsX) becomes less than 1.9 GB the VMware Fusion makes a break with this runtime message:

  -

  ---

  VMware Fusion has suspended this virtual machine because the disk on which the virtual machine is stored is almost full.

  To continue, free at least 1.9 GB of disk space.

  -

  ---

  Please prove me wrong, but makes no sense to me, because the result is that these 1.9 GB is never used (or VMware) :-(

  In advance, VMware Fusion allocates approximately 1.9 GB whenever the virtual machine is started then in my opinion this runtime check is redundant and the audit should run only before you start the virtual machine.

  Anyone know how to move this bug to developers or solve the problem?

  It's very annoying not being able to use almost 2 GB of disk space :-(

  Thanks for all the relevant answers :-)

  This is not a Bug! and this is the expected behavior to avoid crashing on OS X and or damage to the system as a result of unexpectedly running out of space.

  If you are currently running disks tight on space you have a bigger problem then do what it's programmed to do my protect the stability of the system, because the user is not paying attention to the State of their own Fusion system.

  Free and maintain a suitable available space as required by the programs that you use, and how they are used.

  It's a result of error of the end user, because you shouldn't be filling your drives and should always maintain a reasonable percentage of free space.

• VMWare Fusion makes a break from the virtual machine because the disk is almost full.

  Is I myself am sitting at my computer this morning, I saw a message that says the guest system Windows XP Pro on my Mac Mini has been suspended.  Here is the message:

  "VMware Fusion has suspended this virtual machine because the disk on which the virtual machine is stored is almost full."

  I can't find a way to shut down Windows to resize hard disk space allocation.  I tried the Virtual Machine menu, but all the shut down/put off the power points are grayed out.

  Any ideas out there?

  You must read the message!

  BTW if force you the VM to the bottom you may corrupt the virtual system hard disk and or the VHD file and you need to just do as the message says and free up space on the OS X hard disk even if you temporarily move a few things on an external hard drive so that you can then reactivate the Virtual Machine and continue on the it.

• Can you teach VMware WorkStation to attach NOT some devices to a virtual computer?

  What I find more tedious with VMware workstation (I use v9) is, it still attaches automatically * all * USB devices being plugged in while that VM Workstation automatically runs in a virtual computer.

  On my laptop work/computer workstation I frequently have a VM open for long periods while developing and testing programs. In the meantime, devices all USB (USB, security tokens, my cell phone keys, etc.) I plug are automatically attached to the VM without asking. However, I want to be attached to the host, which is the main system. Only when they show up there for more than half a minute or so after plugging the, I usually realize that they * new * have been connected to the virtual machine, then I neeed to detach and their connection to the host instead manually.

  I find it ANNOYING! Can't you teach WorkStation to memorize these settings and automatically connect devices, which were previously attached to some VM or at least ask me?

  M.

  This may not indicate all the scenarios, but it of a place to start, have a look on: disable the AutoConnect USB devices

• My computer is broken and I only have access to the records and am unable to open any program. Is anyway I can recover my favorites - because I'm unable to open 4 Firefix for export. Thank you

  My computer was originally with Windows Vista, however I am a linux called Ubuntu OS in order to recover my files and folders. In Ubuntu, I am unable to open the Vista of Firefox version and there for cannot export.

  http://support.Mozilla.com/en-us/KB/recovering+important+data+from+an+old+profile

  Your old profile is located here in Windows Vista and Win7:
  
  drive: \Users\Windows login user name\AppData\Roaming\Mozilla\Firefox\Profiles\profile_name

• I am unable to open and copy the file encrypted after formatting my computer

  I just format my computer before formatting, I take any backup of the drive c. but 1 file is encrypted on my backup now, I'm unable to decrypt this file and is also impossible to copy and open this folder. Please help me with this.

  I assume you have XP Pro and that you encrypted files by using the Encrypting File System (EFS).  When you use EFS, the these files decryption key is stored encrypted with your certificate store.  When you use EFS, you * MUST * back up your certificates or risk permanently losing access to your encrypted files.  Details are provided in this article which is required reading if you use EFS:

  "Best Practices for encrypting file system"
    <>http://support.Microsoft.com/kb/223316 >

  Jump down to the paragraph "why you should back up your certificates.
  Line background here, is that you have two options to recover the access to these files.  The first is to restore your certificate from the backup of the certificate that you created by the article above before you reformat your computer.  The second option is to completely restore your previous system from a backup of the image-style you did your system before reformatting and reinstalling.  Otherwise, I fear that you have permanenty lost access to these files.

  EFS is affectionately known as the 'Recycle Bin delay' in this forum.

  Sorry,
  JW

• VMware Workstation 6.5 - not enough physical memory is available to power on this virtual machine

  My host is a processor Intel Core i5 (active VT) and 8 GB of RAM Windows 7 64 bit running with hardware virtualization enabled.
  
  Apart from McAfee Antivirus and the usual Windows updates, no other software has been installed on the host machine.
  
  I am running Vmware Workstation 6.5 and I installed 3 popular VM with below guest OS, s/w and memory:
  
  VMware ESX 4-2 GB
  Server 2003 (DC and DNS) - 1 GB

  Server 2003 (vCenter Server) - 1 GB
  
  However, it is not possible for me to all 3 virtual machines run simultaneously. If I turn on Vmware ESX 4 and try to start Windows 2003 VM, it displays the following message:

  Not enough physical memory is available to power on this virtual machine with its configured settings.

  To resolve this problem, set the parameters in additional memory to allow for more virtual memory machine to swap.

  If you were able to on this Windows virtual machine on that host computer in the past, try restarting the host computer. Reboot may allow you to use a little more memory host to run virtual machines.

  Can you get it someone please let me know where are the rest of the memory is busy? Size of total memory of 3 virtual machines are only 4 GB and I have to be able to run all the VMs set 3, but in this case I can't even run two virtual machines simultaneously.

  Please help what should I do?

  With 8 GB of RAM on the host allowing why only 1 GB to be reserved for all you run virtual machines?