Parallels mounter is unable to open the virtual hard disk - parallels

I installed parallel 9 with Windows 10 images installed on mac.
When I try to share mac folders to windows 10 manually I encounter following error
"Parallels mounter is unable to open the virtual hard disk".
Following document : http://kb.parallels.com/en/112609 to do mannually installation.

It fails because Parallel 9 does not support Windows 10. After upgrade to Parallel 12 and re-install Win 10. Everything goes fine.

Related

VS Code not running windows 7 64bit

I have only one Windows 7 64 bit old PC. And I learning web development and I want to run VS Code code editor but when I install VS Code and double click launching icon then VSCode does not launching.
Confirmation my PC:
RAM : 4GB (DDR4)
HDD : 500 GB
CPU : Dual Core Processors
GPU:
OS : Windows 7 64bit
I am the first on this platform so please forgive me if I have made any mistakes.
Thank you.
Currently, you can install Visual Studio Code v1.70.3.
P.s. It works well in my computer.
https://code.visualstudio.com/updates/v1_70
this is last supported version for Windows7
I also still use Windows 7 Pro 64-bit. I discovered that the latest version of Code downloaded directly from Microsoft - 1.74.3 at the time I'm writing this - runs fine and all features (like debugging) appear to work IF you use the ZIP download. Every time I start it, it pops up the message "Visual Studio Code on Windows 7 will no longer receive any further updates." But when the next update comes along, I plan to just download the newest zip.
Note that all the projects I had opened in the installed version are still available in the zipped version. So, I won't be upgrading this system to Windows 10.
Hardware# Visual Studio Code is a small download (< 200 MB) and has a
disk footprint of < 500 MB. VS Code is lightweight and should easily
run on today's hardware.
We recommend:
1.6 GHz or faster processor 1 GB of RAM Platforms# VS Code is supported on the following platforms:
OS X El Capitan (10.11+) Windows 8.0, 8.1 and 10, 11 (32-bit and
64-bit) Linux (Debian): Ubuntu Desktop 16.04, Debian 9 Linux (Red
Hat): Red Hat Enterprise Linux 7, CentOS 7, Fedora 34

CentOS 8 Pane is dead VMware Workstation 15.5

I am using VMware Workstation 15.5 and trying to install CentOS 8. When I boot and it starts the installer it gives me a message on the
bottom "Pane is dead". I tried to set "install operating system later", picked CentOS 7, selected ISO as the CD ROM device and attempted the install.
Unfortunately VMware does not pick up the boot device as ISO and goes right to DHCP boot. So I tried a CentOS 7 ISO, same thing. I just upgraded VMware Workstation from 15.0 to 15.5.
I finally find a solution to this problem.
You need to download your CentOS 8 iso.
Open VMware and create a virtual machine like normal, editing as you want, and don't worry if VMware detects it as CentOS 5 or
earlier, just keep ongoing.
Launch your VM and wait, if it shows you the "Pane is dead" just turn off the virtual machine.
Open de settings of your VM and just remove the disk "Using the autoinst.iso"
Open again your virtual machine and the problem probably will be fixed.

Database connection issue in installing Powerbuilder 8 application to Windows 10

I'm trying to get a legacy Powerbuilder 8 application to work in a Windows 10 environment. The application has not been installed from any installation package, I simply open it from a network share containing all the necessary files. It works this way in Windows 7 systems. In Windows 10 the app opens fine, but connecting to database fails with error message:
999: DBMS MSS is not supported in your current installation.
Neither Windows 7 nor Windows 10 workstations have any specific database access drivers installed.
My development environment has Windows 10 and there connection to the database works ok. The database server is installed locally in the dev environment, though.
We had a problem with Powerbuilder 8.4 and 0racle 10 and 11. With Windows 10 patch 1803. When we copied files to local drive it worked. We were getting strange data base error. It had to do with smb version 1. June 30 2018 Windows 10 solved the problems. If your still having problem this may be worth a shot.

Bluestacks installation does not start after extracting

My Bluestacsk2 installation does not pop-up after extracting. Just nothing happens after that window. I tried disabling antivirus programs and running it as administrator. My system fulfils the system requirements:
Windows 10 Pro, 4 GB Ram.
Version: BlueStacks2_native_8e68b6e001e5a05ff01c3f89c5790f9d
I also have the latest version of Directx and .NET framework. My graphic card is up to date and works very well.
This problem occurs only for the Bluestacks 2. I can setup the previous beta version. I tried both win7 and win10 versions for Bluestacks2 but they are not starting to install.
I figured out that I don't have enough space in C drive. But it was really annoying that Bluestacks does not warn me about this. I had several gigabytes in C, but I have been able to install it properly after I removed 10 gb of data from there. (I don't think you need to remove such big data)

My app created on XP does not run on Windows 7

I am trying to run an app I created at work (I sent myself the .exe file) so that I could see how it looks on Windows 7.
My laptop (running 64-bit Windows 7) won't even open it, though. It opens some compatibility wizard to try to rectify whatever the problem is, but that doesn't work either.
Is there anything I need besides the .exe itself, that I should have copied over?
A team member using Windows 7 can run it (by checking it out of Subversion and running it in the VS IDE, anyway), but the display if "off" (The FlowLayoutPanel's controls are experiencing a kind of "wardrobe malfunction"). But I, as mentioned, can't even run it.
What might be the problem/solution?
If you are running the Professional edition of Windows 7 or higher then it will include the option to install the "Windows XP Virtual Machine". You can then run your app as normal under the virtual machine, quckest and easiest way to resolve these sort of issues in Windows 7.