FastRawViewer crashed when starting in Windows 7 virtual machine

Forums: 

FastRawViewer 64bit and 32bit crash when starting in Windows 7 virtual machine.
No error message. Is .NET runtime required? Which version?
Or any other component?

What virtual machine do you use?

You need to use virtual machine with working 3D-acceleration (software OpenGL based on Mesa is OK, but very slow; VMWare DirectX works fine)

FastRawViewer is heavily tested under VMWare Workstation on Windows host. It works with any Windows version starting from WinXP (to Windows 10) and with OS X 10.6-10.10 in virtual machines.  For windows virtual machine, DirectX version is recommended (it is faster, because DirectX is forwarded to host hardware).

FRV does not work under VirtualBox (on windows host) because of very poor quality of 3D acceleration.

Have not tested under other VMs and other host software, but should work under VMware Fusion on OS X.

 

Thank you for the fast reply.
I use VMWare player on Linux Mint 17.
3D support is checked in machines properties but at startup there is a message like this
"3D Graphics acceleration will be disabled
this computer does not have a 3D graphics system supported by vmware workstation."
I will check how to enable 3D support on my system.

Try to use OpenGL version of FRV. It works on VMWare OpenGL emulator (tested under windows host only). Some features will work very slow (e.g. bicubic resampling and focus/details zones display), but basic features are OK on fast computer (pass all CPU cores to Vmware for faster processing)

I fixed the problem. After installing other video drivers (not open-source)
everything worked fine. Thanks
 

Could you please specify more details (we'll direct Linux users to your answer):

 - What videocard

 - and what drivers works fine

Thanks in advance.

Here are some more informations:
Video card is GT218 [GeForce 210]
Linux mint came with driver nvidia-304 (version 304.125-0ubntu0.0.1)
I switched to nvidia-331 (version 331.1130ubntu0.0.4). This driver was recommendet in the driver dialog.
After installation and restart everything worked fine.

Add new comment