The answer to the question is: You can re-establish your WinFiol channel files by using the WinFiol Channel File Manager tool located in the WinFiol program folder.
Since Windows Server 2012 Microsoft system does not support *.hlp files thus we are not able to use WinFIOL's help. Could you provide a solution for this?
A
Answer by
Alex Urbach
I encountered the same issue on Windows 10 X64 and the simplest way to fix it is with the help of another application called Help Explorer. I managed to open HLP and CHM files with simple clicks like File > Browser > Open.
You can download the software through the websites listed on Google Search: https://goo.gl/Xm6YoI
I am having a problem with WinFiol installation & usage in Windows 2008 R2 64-bit terminal server. WinFiol GUI does not start when we connect remotely to the server using Windows Remote Desktop. We are running WinFiol server edition and we have a license for 50 users.
Winfiol is installed to VMware server. It does work when we log in to the virtual machine "locally" using VMware admin tool, but this cannot be used as a remedy.
The problem appears when the user connects from the network with the Remote Desktop Connection tool; we can see that WinFiol process starts, but it doesn't open any GUI or gives any error message. Even when we try to use it with the same user account or with admin rights.
Just the winfiol.exe process starts running in the background and nothing else happens.
Perhaps, the problem is related to ancient Java 1.4 which is shipped together with WinFiol installation CD.
P
Answer by
Pete Clapp
The problem is not with the VMware, but with the network settings of the VMware machine that's configured. Of course, you will be able to connect locally, the problem is with the remote part. If you want to connect to VMware from another location, you will enter the IP of the VMware machine but Windows doesn't know how to forward the request to the actual machine. You need to configure port forwarding from VMware so that when the incoming requests are delivered, Windows should know where to point them.
For example:
Your Machine : 1.1.1.1 Vmware Machine: 2.2.2.2:3398 //3389 is the default RDP port.
You will need to configure the settings so that when IP 1.1.1.1 is accessed automatically it points to 2.2.2.2:3398.
Then you will be able to connect your machine. Java has nothing to do here because this is a connectivity issue.
I uninstalled WinFIOL 6.3 and installed WinFIOL 7.1, but it doesn't run. Can you help?
P
Answer by
Pete Clapp
The application doesn't run on your computer either because it is not compatible with your system or it is not correctly installed. Also, some of its files may be in conflict with the similar files from the previous version. In order to fix the issue, uninstall the software using its uninstaller or Add or Remove program feature, run a registry cleaner to make sure that there are no leftover registry keys in your system, reboot your computer and install it again. If it doesn't work, you will need to reinstall WinFIOL 6.3. If you no longer have the installation package, you need to contact the developer and ask for it.
The answer to the question is: You can re-establish your WinFiol channel files by using the WinFiol Channel File Manager tool located in the WinFiol program folder.
Since Windows Server 2012 Microsoft system does not support *.hlp files thus we are not able to use WinFIOL's help. Could you provide a solution for this?
I encountered the same issue on Windows 10 X64 and the simplest way to fix it is with the help of another application called Help Explorer. I managed to open HLP and CHM files with simple clicks like File > Browser > Open.
You can download the software through the websites listed on Google Search: https://goo.gl/Xm6YoI
Note: The first 1-3 websites should be helpful.
I am having a problem with WinFiol installation & usage in Windows 2008 R2 64-bit terminal server.
WinFiol GUI does not start when we connect remotely to the server using Windows Remote Desktop.
We are running WinFiol server edition and we have a license for 50 users.
Winfiol is installed to VMware server. It does work when we log in to the virtual machine "locally" using VMware admin tool, but this cannot be used as a remedy.
The problem appears when the user connects from the network with the Remote Desktop Connection tool; we can see that WinFiol process starts, but it doesn't open any GUI or gives any error message. Even when we try to use it with the same user account or with admin rights.
Just the winfiol.exe process starts running in the background and nothing else happens.
Perhaps, the problem is related to ancient Java 1.4 which is shipped together with WinFiol installation CD.
The problem is not with the VMware, but with the network settings of the VMware machine that's configured. Of course, you will be able to connect locally, the problem is with the remote part. If you want to connect to VMware from another location, you will enter the IP of the VMware machine but Windows doesn't know how to forward the request to the actual machine. You need to configure port forwarding from VMware so that when the incoming requests are delivered, Windows should know where to point them.
For example:
Your Machine : 1.1.1.1
Vmware Machine: 2.2.2.2:3398 //3389 is the default RDP port.
You will need to configure the settings so that when IP 1.1.1.1 is accessed automatically it points to 2.2.2.2:3398.
Then you will be able to connect your machine. Java has nothing to do here because this is a connectivity issue.
I uninstalled WinFIOL 6.3 and installed WinFIOL 7.1, but it doesn't run. Can you help?
The application doesn't run on your computer either because it is not compatible with your system or it is not correctly installed. Also, some of its files may be in conflict with the similar files from the previous version. In order to fix the issue, uninstall the software using its uninstaller or Add or Remove program feature, run a registry cleaner to make sure that there are no leftover registry keys in your system, reboot your computer and install it again. If it doesn't work, you will need to reinstall WinFIOL 6.3. If you no longer have the installation package, you need to contact the developer and ask for it.