in

Data Techniques Forums

FaxMan 4.6 SDK on Windows 7

Last post 09-24-2009 12:36 PM by Admin. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 09-16-2009 2:44 AM

    FaxMan 4.6 SDK on Windows 7

    Calling the FaxSchedule() function on Windows 7 (x86) always returns 0xfffffff8 (FAX_ERR_BADFILE) and the fax doesn't get scheduled.   The same call works correctly on Windows 2000, XP, Server 2003 and Server 2008.  The fmf created appears to be fine (verified by renaming to .TIF and opening in a graphics viewer). 

    I also notice that the "sentinel" member of the APPINFO structure obtained from the call to FaxRegisterApp is set to an invalid value (0xbcbcbcdd) when called on Windows 7 - which may or may not be related to the FaxSchedule() issue.

    Any advice would be appreciated.

     

  • 09-16-2009 8:18 AM In reply to

    Re: FaxMan 4.6 SDK on Windows 7

    Hi Stuart,

    We havent seen any issues in running FaxMan on Windows 7. Can you run the MFC Sample app on that system and send a fax ?

    I just ran that app and  was able to schedule and send some faxes.

     

  • 09-24-2009 6:54 AM In reply to

    Re: FaxMan 4.6 SDK on Windows 7

    Hi,

    I have run the FaxMan Demo App (the MFC sample) and after I enter some sample details (To, Company, Fax Number, Subject and Comment) and then click "Send Now", a small dialog box pops up with "Schedule Error Occurred" in the title bar and nothing in the main body.

    I can send a screeshot if that would be of use.

    Thanks.

     

  • 09-24-2009 9:55 AM In reply to

    Re: FaxMan 4.6 SDK on Windows 7

    I have performed further investigation and notice that the sample programs all exhibit the same behaviour when they are launched unless Fax Man Server is first launched using "Run As Administrator" which causes it to run with UAC Virtualisation disabled.  

  • 09-24-2009 12:36 PM In reply to

    Re: FaxMan 4.6 SDK on Windows 7

    Hi,

    FaxMan does need to run as admin when run under Vista or Windows 7. It has a manifest so you should get prompted to allow it to run as admin when you start it up. If you run it as a service then it will automatically run as admin and you wont get this issue.

     

Page 1 of 1 (5 items)
Copyright 2009 Data Techniques, Inc. All Rights Reserved.