XP Virtual errors: Could not enable integration features

Topic

New Reply

XP Virtual errors:

Recd error #1, then re-booted recd error #2

1) Could not enable integration features. (What “tools menu” & where is it located, path?)
2) The virtual machine could not be started, access denied. (was access denied because of #1 or something else?)

XP virtual worked fine earlier this week and has been working fine for months..

Thanks,

klxdrt

Reply | Quote

Replies

Have you tried re-booting?

Joe

--Joe

Reply | Quote

See if there is a .vsv file in the same directory where your .vmc is. If so, rename the file to .vsv.bak or something like that and see if XP mode will start. If so, delete that file and research how to set the VM so it shuts down all the time instead of trying to resume from hibernation.

Reply | Quote

Thanks for the timely response & tips. I really appreciate it as I am not a tech, but a very experienced business user of all versions of W since 3.0.

In addition to my orig posting,

1) I rebooted several times to no avail.
2) Renamed the .vsv as suggested to no avail.
3) researched & found at http://dailytips.net76.net/?p=617
“Shut Down – This option behaves just like when you shut down Windows 7. XP Mode shuts down the virtual machine just as if the operating system were running on a physical computer. No volatile memory information is saved and the operating system warns you if you have applications still running when you try to close XP Mode.

This is the safest close option; it ensures that the XP Mode Virtual Machine will not hang on the next start-up. However, start-up and shutdown times are definitely longer than when using a Hibernation close.”

4) Set close option to “shut down” to no avail.

Below are screen shots of what I did. I sorry that the form’s software did not allow to properly visually merchandise the proper sequence of my screen shots.

cheers,

klxdrt

Reply | Quote

I think you found the right action to apply to possibly prevent this in the future if and when you can restore the current VM to operation. I just had a thought that it might be reading only the first three characters after the period and still assuming it is a working .vsv file. I don’t know enough about Virtual PC ( I use VMWare Player ) to tell you to just delete it but try replacing the .vsv with .bak so no remnant of .vsv is there at all or move the file to another folder so Virtual PC cannot find that file at all and try booting again. If that doesn’t work, try moving the vpcbackup file temporarily as well. If that doesn’t work then there must be something corrupt in the actual XP mode VM. Is there anything you need to get out of the VM?

One further possibility is to download VMWare Player version 3.0.# , and use that to import the XP Mode installation into a working VMWare Player VM. This might work because VMWare has its own integration features and won’t use Virtual PC integration features. You start with the older version (upgrade later to version 5.#) first because it has a menu item specifically for importing XP mode. If that works its very easy to copy the VM installation folder and keep that as a backup copy in case anything further happened to the VM. I’ve occasionally had a VM there that won’t start because it didn’t shut down properly but deleting any .lck files in the VM folder fixed that issue.

Finally if none of that works, as far as I know you have to dump that install and start over with a fresh copy of XP Mode.

Reply | Quote

FUN downtown,

Thanks for the quick reply. I’ll probable have to remove & re-install as I did once before. I have one older program has capabilities not found in newer sw. I use it for special communication situations and other “off the reservation” situations. NO critical data etc.

I’ll continue to trouble shoot and get back with any solution I come up with. For 73 yr old guy, I have learned a lot about XP virtual. Is VMWARE free?

cheers,

klxdrt

Reply | Quote

The .vsv file can be deleted. I doubt that it would be read with a different extension, though.

Reply | Quote

No, not with a different extension, just giving a different option by mentioning moving. I did have a program that read a file renamed .ext.bak as a working .ext file so had the thought that that might be the case here as well and that I should have recommended complete extension replacement.

Reply | Quote

VMWare Player is free for personal use. I think VMWare the company specializes in virtual products only as far as I know and I think they are very good. VMWare Player is more versatile and robust compared to VirtualPC (though you probably don’t have a need for those in the use you describe) and of course is still being updated and improved. Microsoft ended support for VirtualPC in Windows8.

In version 4 and 5 the import XP mode menu item is gone, but if one downloads and installs version 3.0., which VMWare so craftily still keeps available in a tuck of the Internet for those who have the “where there’s a will, there’s a way” attitude, there it is.

Reply | Quote

Re-installed XP virtual working now, Thanks.

I removed XP Virtual & the Virtual Machine, then reinstalled. Then I changed CLOSED: Shut Down from Hibernate. I’m told this would be a better choice for stability.

Thanks for all this forum’s help.

klxdrt

Reply | Quote