Forum Replies Created
-
Posts
-
I have not tried that combination before, does it work if you don’t destroy the send object after creating the attachments?
Quote: from kshivan on 6:15 am on Dec. 1, 2001
We have Win Fax 9.03 installed and running in a seperate server and printing doucments to that as of now. I would like to initiate this process through the coldfusion application. Whether this is possible with 9.03 version or should I upgrade to 10.0 and above. How do I develop this interface with Coldfusion – Any ideas..Cold fusion application runs in a different server.The application needs to be on the same machine as WinFax, you can do this with 9.0 or 10.0 (both include SDK functionality)
The SDK uses Microsoft COM, if you can use COM with Coldfusion it should work.Quote: from vdeepakkumar on 5:38 am on Dec. 1, 2001
Hi,I am in an urgent need of online documentation for WinFax (preferably ver 9.03+ or 10 or Pro) and some helpful code snippets geared towards automating the FAX software via my ASP application.
Any assistance would be greatly appreciated.
deepak
Hi Deepak, there are some samples available via this link
http://www.getfaxing.com/download.htm
there are links here to download the symantec pdf files for all versions of the SDKI don’t think you can run the Controller (wfxctl32.exe) as a service, but you can try.. Are services programmed differently than a regular app? I would assume so, I am not too familiar with the development of services. I would assume this wouldn’t work, because if it did, Symantec would have probably used the Controller instead of developing another “service” to be used!
Quote: from Jos on 9:08 am on Nov. 29, 2001
I have the same problem in Win 98 working with Visual Basic 5.0.
It might not be a Win xp problem.
Using the sdkSend app. from the cd does not work here also.Joe , does Help, About in WinFax display 10.02?
Quote: from NDS on 10:30 am on Nov. 29, 2001
I have installed 10.02 on two machines, one with Windows XP and the other with Windows 2000. SDK works with Windows 2000 but not with Windows XP, the send screen always comes up. Interesting side problem, I have also installed the macros for Word and Excell on both systems. The macro in Word causes the progrom to crash and you cannot open word without unstalling Winfax Pro. This happens on both operating systems. Any comments?Steve
Looks to be a XP + 10.02 problem. I’ve checked the Symantec SDK area and there have been no responses from Symantec on this issue.
To fix the macro problem, delete the WFWORD2K.DOT file found in the STARTUP directory of Word. (Do a search)
or start Word without any templates using WORD /A switch. Symantec’s solution is to download an older macro and install it (from their site), but the digital certificate included with this macro is expired. You will get prompted each time you start Word about the macro not being safe (unless you leave your security level set to Low, which IS NOT recommended)You can also fix the problem by downloading tje shareware macro :
http://www.getfaxing.com/downloads/wfxmacro.exe
It will install overtop your existing macro, and should work. If you can live with nag screens, it will do you fine for simple print to winfax operation. If you register, well, you get support and we like you here.I have installed 10.02 on two machines, one with Windows XP and the other with Windows 2000. SDK works with Windows 2000 but not with Windows XP, the send screen always comes up. Interesting side problem, I have also installed the macros for Word and Excell on both systems. The macro in Word causes the progrom to crash and you cannot open word without unstalling Winfax Pro. This happens on both operating systems. Any comments?
Steve
I have the same problem in Win 98 working with Visual Basic 5.0.
It might not be a Win xp problem.
Using the sdkSend app. from the cd does not work here also.And if I run the “winfax controller program” as a NT service (i think there is an utility in the NT Resource Kit that can do that), do you think it’ll work properly?
Hi Alessio,
Unfortunately, you need to be logged in to be able to send faxes. The SDK works only when the Controller is activated on the PC. There is something called the WinFax Service that will load on NT/2000/XP machines, but it does not contain any SDK code so you can’t run any of your automated applications with this. Therefore, a user must be logged on to the PC and the Controller active before you can use any SDK function.As for using Win NT 4.0 Server, you should be OK.
For attachments, the attachment type must be “known” or “associated” in Windows for that operation to work. Not all attachments will convert properly, you can test it out by setting the Printer to WinFax and then right-clicking a file in Explorer and selecting “Print”. If it prints properly, then it should function with WinFax.
Sorry, I don’t know, the only machine with installed 10.02 has XP. If it’s really important, I can install 10.02 on my WinMe machine and try there… let me know.
Another question:
Is it a 10.02 problem, or a XP + 10.02 problem?
does Win 2000 or Win98 + 10.02 work?> Let me know if you hear anything back from Symantec > on this issue.
OK.
> I understand that the 10.02 upgrade simply fixes
> compatibility with Outlook XP integration,
> support for multiple users in XP? (not sure about that)as for multiple users, to a degree winfax always supported it, as the info it keeps in the Registry always had a part in HKCU – user name, toolbars, fonts, columns, etc. Probably now they added some security-related features – I have an impression that the whole software industry has almost lost the interest in anything but security.
I didn’t hear about Outlook XP problems, not using it really.
(Edited by vrapp at 11:14 am on Nov. 24, 2001)
