Fax Software

Community Forums

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 60 total)
  • Author
    Posts
  • in reply to: Symantec Message Manager Line Status #8982
    kaboondy
    Participant

    Amazingly the COM is COM3 and the IRQ remains at 21. However, it has been 3 weeks (or so) and there has not been a single crash of WinFax so far. This is a major change from 2 – 3 times per day.

    I want to thank you for all the support with this challenging issue.

    in reply to: Symantec Message Manager Line Status #8980
    kaboondy
    Participant

    It has taken quite some time to review and redo all the suggestions again for WinFax. I did finally accomplish my objective and for the past 10 days the program has not become “frozen”.

    Ultimately what ended up working was removing the Fax Modem from the computer, uninstalling the hardware from the control panel (as well as using the Add/Remove Hardware to remove the residual signature of the modem). I then installed the Fax Modem into a different physical slot in the computer and left all default settings intact. In other words, I did not change the COM setting or the IRQ. Nor did I change anything in WinFax Modem and communications settings.

    So far this has worked and I hope this long winded route might help the next person as well.

    Thank you for all your support and advice during this challenging issue. 😀 😀

    in reply to: Symantec Message Manager Line Status #8978
    kaboondy
    Participant

    Thank you.

    I did go into BIOS and disable both the ports and then in Device Manager I reassigned the port numbers to each of the COMs to a higher port number. And it did free up the lower COM ports 1, 2, and 3 as well as the IRQ but I was not able to manually force the computer to select the lower IRQ’s for the Fax Modem.

    It is curious that despite being disabled in the BIOS the “communication Ports” still show in Device Manager implying that they are still “active”. I had assumed the COM1 and COM2 must be referring to some other devices rather than the physical, external harware Serial Ports on the computer which I had disabled.

    I will reverse the changes and report back. Thanks again.

    in reply to: Symantec Message Manager Line Status #8976
    kaboondy
    Participant

    Again, thank you.

    If I understand correctly, you suggest that I revert the COM1 and COM2 in the device manager to use Com1 and Com2 respectively in the advanced button under Port Settings Tab. I will go ahead and try this.

    I am not really sure what the COM1 and COM2 in the Device Manager refer to. Then when I open the properties and look into the advanced tab under Port settings – what are the numerous (more than 20 COM settings) that I can scroll and select from refer to? Depending on the computer, some Com ports indicate that it is “used” or allocated. It would be nice to know as I really don’t understand the use of these terms “com ports” in the Properties and COM1 and COM2 headings in Device Manager. Apparently COM1 and COM2 in Device Manager are devices while the ones seen in the Port Tab are “ports“. Can you please explain as I was not able to understand from my search on the internet.

    Thank you

    in reply to: Symantec Message Manager Line Status #8974
    kaboondy
    Participant

    Thank you for your response.

    Regrettably the Fax modem is a USR plug and play type. I was in error when I stated in an earlier post that there were pins on the modem card that could be changed. At one time, I did have such a fax modem – I can look for it to see if I still have it. If I recall correctly, the modem with the “pin setting option” was an older modem (?? ISA) while the currently installed plug and play was purchased many years later (PCI). To be clear the pins on the (ISA type) modem had two sets of pin options – one to set the COM (1,2 or 3) and IRQ (1 – 7) – if I recall correctly.

    Are you suggesting that I should revert the COM1 and COM2 in the Device manager BACK to COM1 and COM2 (instead of COM5 and COM6)? Please note that the external Serial Port A and B are not used on this computer – If I understand correctly, the COM1 and COM2 are normally reserved for the external Serial A and B ports. Correct?

    No matter what I have tried, I can not seem to be able to see the COM setting in the modem properties in WinFax. Hence, I have had to use the TAPI setting. In other words the modem is installed on COM2 – confirmed by Modem and Communication Devices Properties – Test Com Ports. When I open the properties – COM2 is not an option. In my mind this seems strange because WinFax does see the modem on COM2 but will not communicate with it directly but only through TAPI.

    I am not even sure if all the effort to directly link WinFax to the modem will be helpful in solving this problem even if we are able to somehow get this to happen.

    Any other suggestions would be very much appreciated. I will continue to try on my end and report to the forum (if I am successful) in case someone else has this problem in the future (or currently).

    in reply to: Symantec Message Manager Line Status #8972
    kaboondy
    Participant

    It has been some time and I have tried a number of variables on both computers.

    1. In the BIOS – I disabled Serial Port A and Serial Port B. Both are not used and hence by disabling them it would free up COM1 and COM2 which are usually assigned to the External Serial Ports A and B.

    2. In Device Manager, under communications, there are listed LPT1 and COM1 and COM2. The COM1 and COM2 (under properties – Advanced Tab), can have their assigned COM ports changed. I changed these to a higher COM – 5 and 6.

    3. In Device Manager, I then changed the COM Port assigned to the Fax Modem from COM3 to COM2 (as this became available when COM1 and COM2 were freed). The IRQ for the Modem is set at 21 and I am unable to change it – there is a Change settings dialogue under Resources Tab but this has only “Settings based on” which appear to have a specifc protocol like 0000, 0001, 0002, 0003 etc which I did not understand and is greayed out. In other words, I can not choose to use a free IRQ (I know that IRQ 4 and 5 are free when I select the View menu in Device Manager to show by Connection.

    4. Once the COM (only) was changed for the Modem – I opened the settings for the Modem in WinFax – There was no option to Select COM2 (which the modem is now installed on). Only TAPI and COM6 show as options in the WinFax modem properties. Hence, despite having the Modem on COM2 – I still have to select TAPI to allow the Modem to work with WinFax since COM2 does not show as an option.

    If there are any futher suggestions, I would be deeply appreciative. I think I have exhausted every option or idea that has been sggested. Perhaps the only thing to do is to reboot the computer at regular intervals to avoid the WinFax from hanging after a few hours. It should be noted that once WinFax hangs, the only way to get it to work again seems to be to reboot the computer. I realize the other way is to close the program(s) in Task Manager. It is interesting that the program does not respond (the Exit option when one right clicks the Message Manager in the Task bar is greyed out so you can not exit the program gracefully. Also, once WinFax has hung, I can not open up the Modem properties in Device Manager at all. In other words the Modem also does not respond either once WinFax has hung.

    Thank you for your help and support on this very perplexing topic.

    in reply to: Symantec Message Manager Line Status #8971
    kaboondy
    Participant

    Thank you. This is very educational. I will try all the of the above suggestions and report back in a couple of days. 😀

    in reply to: Symantec Message Manager Line Status #8969
    kaboondy
    Participant

    I am reporting after several days of trials. WinFax continues to “hang” requiring a reboot after about one day of operating correctly. While this is definitely an improvement over crashing after a few hours, we would really hope to solve this problem for good (if possible).

    I have tried to reset the modem properties in WinFax – I was able to reset by pressing SHIFT and then Properties. The modem did reset and the screen shot for this is shown in the previous post – this is a class 1 and Class 2.0 modem. The program automatically selects Class 1 as the option.

    However, after resetting the modem – the modem properties only show COM 1, COM2 and TAPI as the options for the Port. There is no Option for Com3 on the drop down menu. So I took the next step (below):

    In Device Manager i uninstalled the modem and then rebooted the computer – the modem was autoomatically re-installed on COM3 (was on COM3 originally as well). When I go back to the WinFax Modem properties – I had to reset the modem as WinFax showed an error on startup – “you have not selected a modem device…” However, even after resetting the modem in WinFax – there was still no COM3 option available. Hence it remains on TAPI as selecting COM1 or COM2 will likely result in an error.

    If you have any other suggestions, I would be most appreciative of your help. Thank you. 🙂

    in reply to: WinFax Share not working #9563
    kaboondy
    Participant

    Thank you. I have learned a great deal from your forum. I will report any useful findings to the forum. Thank you.

    in reply to: WinFax Share not working #9561
    kaboondy
    Participant

    Thank you very much – I will try the suggestions tomorrow. Can you please let me know how to change the parameters of the modems that are located on the two computers that do not have the ability to keep the computer from turning them off to save power.

    in reply to: WinFax Share not working #9559
    kaboondy
    Participant

    I would appreciate knowing if anyone might have any suggestions to the above issues. Thank you very much. 🙂 😕

    in reply to: Symantec Message Manager Line Status #8968
    kaboondy
    Participant

    I will try this tomorrow and report to the forum. Thank you. 😀

    WinFax reconfigured the modem and it reports it as a Class 1 and Class 2 modem. Here is the screen shot of the report from WinFax

    [attachment=2:3k4spfur]Modem Configuration Wizard WinFax.JPG[/attachment:3k4spfur]

    [attachment=1:3k4spfur]Fax Properties for Modem in WinFax after Config.JPG[/attachment:3k4spfur]

    [attachment=0:3k4spfur]General Properties for Modem in WinFax after Config.JPG[/attachment:3k4spfur]

    I checked the Modem speed and it seemed to have changed from what it was prior to the Wizard reconfiguring the modem (was about 19000). I changed S7=55 to S7=120 for a prior issue. I left the rest of the variables as set by the Wizard (COM port vs TAPI, Class 1 vs Class2, Initialization speed). Given that this might have also contributed to the problem, I will try this for the next few days to see if this is any better. Subsequently, I can try changing the other variables listed above one at a time if instability remains for receiving calls.

    If you have any other thoughts, I would be very appreciative of any directions. Thank you.

    in reply to: WinFax Share not working #9558
    kaboondy
    Participant

    This is very helpful. I will definitely implement tomorrow and report back to you. Thank you. I did not even know this existed. 😀 😀

    I can report the following surprising information.

    All of the computers did not have the same available settings for power management. The WinFax server that receives all the faxes has a NIC card that has the Power Management tab which allows the user to unselect the box that allows the computer to shut down the device (NIC card) in order to save energy. Four other computers also had the same Modem configuration properties. Two other computer did NOT have the Power Management Tab but had the following. The Intel NIC card had drop down menu that did not show on one screen shot and hence I have copied both section of the options.

    [attachment=2:1h4ahjjf]NIC Card Properties without Power Management I.JPG[/attachment:1h4ahjjf]

    [attachment=1:1h4ahjjf]NIC Card Properties without Power Management II.JPG[/attachment:1h4ahjjf]

    Finally the server that has the Shared Fax Folder which we keep losing the connection to – DOES NOT have the power management option so that we can uncheck the box (it was set to on on all the computers where it existed). I should point out that quite frequently I will look at the Win Explorer screen only to find that all the networked drive letters have a Red X in Win Explorer (all the computers have a drive letter in each others WIN explorer to make easier access to transfer files etc). Once I see the red “X” I can double click the drive letter and it will STILL show its contents after a very brief delay but this will not hapenn automatically (without my pressing the networked drive letter).

    [attachment=0:1h4ahjjf]NIC Card Properties no Power Management Shared Fax Server.JPG[/attachment:1h4ahjjf]

    On one computer terminal that does have the power management, I tried at least a dozen times to activate the network drive letter to the Shared Fax folder and then open WinFax Message Manager to look at the Shared Fax message store but each time I got the same error as originally posted. I think this implies that each computer has to have its Power Management turned off in order to make the connection. In other words, if one computer has the NIC card turned off, the connection wont work??? Can you suggest an alternative for a solution.

    I also noticed under the properties of the Shared Fax message store, WinFax uses drive letters. Hence, I deleted the Shared Fax store from each computer and then reconnected using the \ComputerNameDShared Fax folder pointer – rather than using the Drive letter pointer. Regrettably this also did not work for the computer that would not connect (noted above)

    Again, if you have any suggestions, they would be most welcome.

    Thank you.

    in reply to: Symantec Message Manager Line Status #8966
    kaboondy
    Participant

    I can provide an update and clarify as well.

    S7 – relates to the outgoing faxes – WinFax has NEVER hung on an outgoing fax and after I changed the setting to S7=100 – the single receipient who never got my faxes (in the past) – now always gets the faxes with no issues. Hence, I don’t think there would be any benefit to changing the outgoing command string to 120 second (unless I am missing something). WinFax has ONLY ever hung on an incoming fax.

    S19 – you don’t this would help if we make a change here.

    Because WinFax hangs at the begining of the call – no caller information is shown on the Display Status window – screenshot posted on a previous post. Hence there is no way to confirm if this happens with a specific caller. I suspect this happens randomly (unassociated with the identity of a caller) and is an internal problem within our system.

    Update from the past 5 days. Two changes were made to the WinFax server based on advice from the Moderator. A. Turn off the screen saver and B. Set the modem to COM3 and Set the WinFax modem settings to COM3 (instead of TAPI).

    A. The first step was to turn off the screen saver – WinFax hung at the end of the day. This was an inprovement over WinFax hanging after a few hours.
    B. We found the computer was already on COM3 – no change was needed.
    We changed the WinFax Modem properties from TAPI to COM3 – the computer received faxes for 4 days when it hung (on the weekend) while receiving a call.

    Interstingly, when we looked at the Modem properties in WinFax today (after rebooting the computer) – the communication port had CHANGED to TAPI !! Not sure why the change happened spontaneously. In addition the choice of COM3 was not available in the WinFax Modem properties menu !! When I opened the modem in Device Manager – the modem was stil on COM3.

    Another question – does the “initialize at xxxxx bps matter here? Is there an ideal number for this. Also the Modem type – I believe I have a choice of Class 1 vs Class 2. Which one should I select? I could querry the modem and then decide which class based on the report from the modem.

    Thank you for all your asssistance. 🙂

    For now, I have left the setting on TAPI and will see how long it takes for WInFax to hang and will report to you.

    Given the information above, if you have any other suggestions on modifications to try, I would be most grateful. Thank you.

    in reply to: Symantec Message Manager Line Status #8964
    kaboondy
    Participant

    @Moderator wrote:

    @kaboondy wrote:

    …….. but I don’t think this will solve any problem because if WinFax is in a hung state (for some unknown problem), it will not answer calls regardless if your modem had disconnected or not.

    Here is an example if you wanted to change S7=120 and add S19=1 to your current WinFax modem initialization string:
    Line 1: AT&F&D2&C1&H1&R2&I0S7=120
    Line 2: ATS36=0S19=1
    Flow Control: AT&H1&R2&I0

    Thank you for the detailed answer.

    1. Can you please clarify if there is any benefit to making the changes suggested by the string above? If there is no predictable benefit – then I probably won’t make any changes to the string – who knows if the change might create another issue.

    2. The main question in my mind is which is the problem –
    A. “… because if WinFax is in a hung state (for some unknown problem),..” – ie WinFax, the program is in a hung state – OR
    B. The modem is in a hung state and then causing the WinFax program to hang – the reason I ask this is because when WinFax is in a hung state – I can not access the modem properties in either WniFax Pro Setup OR the Control Panel – Modem Properties (which I think would have nothing to do with the WinFax program itself). In other words, if the modem is working properly then should I not be able to access the modem properties in Control Panel despite WinFax being crashed?
    C. Is A. and B. really the same thing. I don’t know enough to realise if I am asking a silly question.

    This has been highly educational and I am deeply appreciative of your help and guidance. Thank you. 😀

Viewing 15 posts - 1 through 15 (of 60 total)