Win32 API 1.1.1 compilation problems

We don't (alas) use Sun's compilers here, so I've
tried to compile the Win32 emulation library, version
1.1.1, using gcc 3.3.2. It yields the warnings and
outright errors listed below. I think it's a little
appalling that Sun didn't at least try this
themselves; it would give them some clues as to what
kinds of problems their own compilers aren't catching,
beyond the effect of getting them to notice and fix
these particular problems.
Glenn
gcc -I../include -D__EXTENSIONS__ -c Files.c -o release/Files.o
Files.c: In function `GetFileAttributesEx':
Files.c:745: warning: right shift count >= width of type
gcc -I../include -D__EXTENSIONS__ -c NamedPipe.c -o release/NamedPipe.o
NamedPipe.c: In function `NamedPipeBroadcast':
NamedPipe.c:185: warning: passing arg 3 of `pthread_create' from incompatible pointer type
gcc -I../include -D__EXTENSIONS__ -c ThreadFuncs.c -o release/ThreadFuncs.o
ThreadFuncs.c: In function `GetCurrentThread':
ThreadFuncs.c:134: error: incompatible type for argument 1 of `memset'
ThreadFuncs.c:135: error: incompatible type for argument 1 of `memset'
*** Error code 1 (ignored)
gcc -I../include -D__EXTENSIONS__ -c WSASockets.c -o release/WSASockets.o
WSASockets.c: In function `WSASendTo':
WSASockets.c:158: warning: passing arg 3 of `pthread_create' from incompatible pointer type
WSASockets.c: In function `WSARecvFrom':
WSASockets.c:216: warning: passing arg 3 of `pthread_create' from incompatible pointer type
WSASockets.c: In function `WSAEventSelect':
WSASockets.c:247: warning: passing arg 3 of `pthread_create' from incompatible pointer type
gcc -I../include -D__EXTENSIONS__ -c mutex.c -o release/mutex.o
mutex.c: In function `CreateMutex':
mutex.c:47: error: incompatible types in assignment
*** Error code 1 (ignored)
gcc -I../include -D__EXTENSIONS__ -c time.c -o release/time.o
time.c: In function `LocalFileTimeToFileTime':
time.c:369: warning: integer constant is too large for "long" type
time.c:375: warning: integer constant is too large for "long" type
time.c:376: warning: integer constant is too large for "long" type
time.c: In function `SetTimeZoneInformation':
time.c:752: warning: comparison between pointer and integer
time.c:780: warning: comparison between pointer and integer
time.c: In function `UnixTimeToFileTime':
time.c:993: warning: integer constant is too large for "long" type
time.c: In function `FileTimeToUnixTime':
time.c:1019: warning: integer constant is too large for "long" type
time.c:1023: warning: integer constant is too large for "long" type
time.c: In function `bValidateFileTimeRange':
time.c:1051: warning: integer constant is too large for "long" type
time.c:1054: warning: integer constant is too large for "long" type
time.c:1055: warning: integer constant is too large for "long" type
gcc -I../include -D__EXTENSIONS__ -c virtual.c -o release/virtual.o
virtual.c: In function `VirtualFree':
virtual.c:511: warning: comparison between pointer and integer
virtual.c: In function `VirtualAlloc':
virtual.c:746: warning: comparison between pointer and integer
virtual.c:746: warning: comparison between pointer and integer
virtual.c: In function `VirtualProtect':
virtual.c:873: warning: comparison between pointer and integer
virtual.c:873: warning: comparison between pointer and integer
gcc -I../include -D__EXTENSIONS__ -c sysinfo.c -o release/sysinfo.o
sysinfo.c:548:28: warning: unknown escape sequence '\-'

The Solaris(TM) OE Implementation for Win32 API Version 1.0 has been compiled by the WorkShop Compilers 5.0 98/12/15 C 5.0 at SUN.
All the source files have ".c" extension which mean you can not use the "CC"/C++ compiler to compile it. You must use the C compiler "Sun WorkShop 6 update 1 C 5.2" instead of C++ compiler "Sun WorkShop 6 update 1 C++ 5.2" to compile this package.
Hope this will help.
Thanks!
Amjad

Similar Messages

  • Win32 API Version 1.0

    Hi,
    I have just downloaded the "Win32 API Version 1.0 " and I am trying to compile it under the
    Solaris 2.6 and Forte 6.1/C++5.2/. I am facing some strange problems like
    socklen_t in Files.h not defined and so on. I don't know which version of Solaris
    and C++ compiler is supported.
    Thanks you for your help
    Dimitar

    The Solaris(TM) OE Implementation for Win32 API Version 1.0 has been compiled by the WorkShop Compilers 5.0 98/12/15 C 5.0 at SUN.
    All the source files have ".c" extension which mean you can not use the "CC"/C++ compiler to compile it. You must use the C compiler "Sun WorkShop 6 update 1 C 5.2" instead of C++ compiler "Sun WorkShop 6 update 1 C++ 5.2" to compile this package.
    Hope this will help.
    Thanks!
    Amjad

  • Kill RT task frontpanel RED-X versus WIN32-API

    I have a LabVIEW task compiled to EXE which is downloaded to a remote processor; the front panel remains open locally.
    I want to kill that task and re-download it. This works the way I want if I use the local mouse to click the RED-X kill box on the upper right corner of the local front panel for the remote task... The panel disappears AND the remote task stops executing.
    The problem is that when I use the WIN32-API to try and kill the local front panel for the remote task I never get the remote task killed. Some  WIN32-API calls such as sending EndTask via USER32.DLL to the local panel's window ID cause the local panel to close but the remote task keeps running and is not aborted. Sending a WM_Close to the local panel's window ID involves the operator because it produces a LabVIEW dialog asking me whether I "want to close all RT tasks or not"
    What message do I send to the window, or what system call do I envoke to get the same result as that simple local mouse click on the RED-X kill box on the upper right corner of the local front panel for the remote task?
    Thanks, Jerry

    Hello.
    Normally a Real-Time task does not require a front panel so closing the Front Panel that you have opened remotely does not necessarily cause the VI to stop running, it merely disconnects the front panel connection to the VI.
    In order to achieve the same resul, you can use an Invoke Node to close another VI.
    To do this you will need to
    follow the steps outlined below.
    Open a blank VI and place an Open VI Reference on the block diagram.
    Create
    a control to the "VI Path" input of the Open VI Reference. On the front
    panel you will need to browse to the VI you want stopped.
    Wire an Invoke Node to the Open VI Reference and set the Invoke Node to "Abort VI."
    Wire a Close Reference to the Invoke Node.
    Wire a General Error Handler to the Close Reference.
    Open the VI that you want to stop. Make sure it is running and then run the vi you just created. This will stop the first VI.
    Hope this helps! 
    Kameralina
    Ask NI (ni.com/ask)
    Search The KnowledgeBase
    NI Developer Zone
    Measure It. Fix It. ni.com/greenengineering/
    NI Vision ni.com/vision/

  • LabVIEW call Win32 API DLL function from third party

    Hi everyone,
    I'm trying to build a LabVIEW 2010 interface on 32-bit Window XP system to configurate and communicate to an Anglient laser head through its USB expansion box. I contacted the vendor and they shared a win32 API with some dll files. I started with a function called "A55292Find", but the CLF node always pop up error 1097.I checked the MSDN to get the corresponding LabVIEW data type for CLF.
    My question is: Do I need to initialize those arguments? (How can I know the values of them if initialization is needed?)
    Could anyone help me figure out what's the problem?
    Here is what I have from API documents about this function:
    The A55292Find function returns lists of handles and board types for all the 55292 USB
    Expansion Modules connected to the system.
    A55292RC __cdecl A55292Find(
    HANDLE hBoxes[], // List of handles for the boxes found. (as Unsigned 32-bit integer numeric)
    BOARDTYPE PortABrdType[], // List of board types for slot A boards (as Unsigned 16-bit integer numeric)
    BOARDTYPE PortBBrdType[], // List of board types for slot B boards (as Unsigned 16-bit integer numeric)
    WORD *spMaxBoxes); // dimension for all of the passed arrays. (as Unsigned 16-bit integer array data pointer)
    // (function return type as Unsigned 32-bit integer numeric)
    Parameters
    HBoxes[] Array that will receive the list of HANDLES for all the 55292 boxes connected.
    PortABrdType[] An array that will receive Slot ‘A’ board type information for each 55292 box.
    PortBBrdType[] An array that will receive Slot ‘B’ board type information for each 55292 box.
    spMxBoxes Passes the maximum number of values that can be held in hBoxes, PortABrdType, and PortBBoardType arrays to the A55292Find routine and returns the actual number of boxes found
    The return value will be one of the following A55292RC return codes:
    Value Meaning
    A55292_NO_ERROR No error
    A55292_TIMEOUT Timeout accessing a shared memory
    Remarks
    This routine must be called to obtain handles and board type information used in calling all the other routines. If there are significantly more array elements than boxes, the routine will take longer to complete.
    These are the definitions: 
    typedef DWORD A55292RC; enum{A55292_NO_ERROR, A55292_HANDLE_ERROR,...}
    typeder WORD BOARDTYPE; enum{A55292_PCAL_BOARD, A55292_NO_BOARD, ...}
    Thanks a lot,
    Kang
    Solved!
    Go to Solution.
    Attachments:
    call A55292Find.vi ‏10 KB

    nkang11 wrote:
    Hi Mr. Kalbermatter,
    As you told me, I should try to use the defined enumeration words as control and indicator.
    For the previous CLF node, it successfully returned the hardware configuration (I have only connected a board at slot A):
    But I really want to see a string return as "A55292_PCAL_BOARD" which is defined by "typedef WORD BOARDTYPE; enumeration {...}; Does that mean I need to change the data type or do something like "converter"? Or initialize the array first, then convert it to string type?
    Right now, I'm trying to open the laser card by using "A55292PcalOpen(HANDLE hDev, SLOTSELECT SlotSelector);" function which requires to use the enumeration constants from " typedef WORD SLOTSELECT; enum {A55292_PORT_A, A55292_PORT_B};" but I'm confused to shot an constant control to a new CLF node.
    Since almost all of the arguments in dll function are typedefined as WORD, short and struct et al, I hope you could give me some hints on it.
    Thank you very much sincerely!
    Kang
    Depending on the actual C implementation you can simply create a LabVIEW enum with the according item names or use a ring control instead. Teh enum requires the numeric values of the items to be in consecutive order without any gaps in between. This is a given if the C definition never assigns a specific number to the item. If the C enum is not consecutive you need to go with a ring control instead.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Error compling Solaris(TM) OE Implementation Win32 API

    Hi,
    I have downloaded above API from sun web site. I am not able to compile it. Do I have to use forte to complie it ? I am using gnu gcc /g++ 2.95.3 on sparc solaris 8.
    I am able to compile without any flags. Means no CFLAGS, no OPTIONS and no LIB64_FLAGS. with this flags it is giving me error for each .c file :
    gcc : language CC not recognised.
    gcc : xxxxx.c linker input file unused since linking is no done.
    And if I use 'release/libwin32.so' that is supplied with download and includes that into my program, it gives me error :
    /Win32_Library/include/wintypes.h:134 declaration does not declare anyhing
    /Win32_Library/include/wintypes.h:169 parse error before 'char'
    /Win32_Library/include/wintypes.h:240 declaration does not declare anyhing
    /Win32_Library/include/wintypes.h:241 declaration does not declare anyhing
    And wintypes.h :
    134: typedef unsigned long DWORD;
    135: typedef unsigned long long DWORD64;
    168: typedef unsigned int SID;
    169: typedef SID *PSID;
    239:typedef BOOL *LPBOOL;
    240: typedef CHAR TCHAR;
    240: typedef CHAR _TCHAR;
    And it is also giving me too many warnings for widec.h, wchar_iso.h and getwc.
    thaks in advanced.

    Hi,
    Yes, you need to use the Forte C/C++ compiler (Formerly known as Sun's Workshop compiler) to compile the library. The Solaris(TM) OE Implementation of Win32 API library has never been tested with gcc compiler.
    It is also mentioned in the README file under the root level folder for this library that this version of library has been compiled by the Sun WorkShop 5.0 98/12/15 C on SunOS Solaris 8. One should use the cc compiler "Sun WorkShop 5.0 98/12/15 C 5.0" or higher version to compile this library.
    Thanks!

  • 3.3 Bug: Win32 API Error 2 - Please help

    Wondering if anyone may be able to help with the following error message:
    "An internal error has occured: Win32 API error 2 ("The system cannot find the file specified") When calling ShellExecuteExW from AgWorkspace.shellExecute".
    The wonderfully unhelpful persons at the helpline said they could not help me but indicated If I reload the version 3.3 in a different location the problem would go away since some plug-in from v1.4 had infected the new install.
    I have no custom add-ins/plug-ins, everything is default.
    I followed these instructions, however still have the same error. I removed then re-installed 3.3 on another drive away from C:\Progfiles......
    Any suggestions?

    Sorry F. McLion, I could have provided the following additional information:
    v1.4 lightroom owned, operating without issue, installed in default location
    C:\... drive
    v3.3 trial downloaded, installed default location, export operating without
    issue
    v1.4 launched to compare, export working fine
    v3.3 launched, export results in error message; determined that export actually
    worked, just resulted in the error message
    un-installed v3.3 per phone support (manager)
    re-installed v3.3 on F:\ drive from copy downloaded on F:\... drive. No change.
    Odly after I removed then re-installed v3.3, the pictures I was working
    on appeared in the re-installed instance with the most current changes - I would
    suspect a clean un-install would have removed any semblence of work done prior
    to removing (at least pointers to modified files). Since not, this means the
    un-install did not truely un-install, it simply removed some files but also left
    some remnents.
    Microsoft XP Home edition V 2002 Service Pack 3
    Dell Dimension 8400 P4 3.00 Ghz 3.00GB ram
    Hope this helps.
    John

  • Re: [iPlanet-JATO] sp3 jsp compiler problem

    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text
    substitution situations, and as a completely independent tool its use is not
    restricted to migration situations (or file types for that matter).
    Second, I sympathize with the unfortunate trouble you are experiencing due to
    Jasper's (perhaps more strict) compilation, but in what way did the iMT
    automated translation contribute to these inconsistencies that you cited?
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a
    translation situation, the only way "OnClick" would have been introduced was if
    it had been part of the pre-existing project's "extraHTML" (which was written
    by the original customer and just passed through unchanged by the iMT) or if it
    was added manually by the post-migration developer.
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
    similar to the OnClick situation described above?
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no
    equivalent in the NetDynamics world, so any content tags in your code must have
    been introduced by your developers manually. Its a shame that jasper is so
    particular, but the iMT could not help you out here even if we wanted to. The
    constants that are used by the iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
    only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    [Non-text portions of this message have been removed]

    Thanks a lot Matt and Mike for your prompt replies.
    I agree completely that iMT doesn't introduce the inconsistencies.
    About the three cases I mentioned, the third one happens only in
    manually created JSPs. So it has nothing to do with iMT. The first
    two are mainly due to the existing HTML code, as you rightly pointed
    out.
    The reason I made the suggestion is since we know that case 1 and 2
    won't pass the japser compiler in sp3, we have to do something about
    it. The best place to do this, in my mind, is iMT. Of course, there
    might be some twists that make it impossible or difficult to do this
    kind of case manipulation or attribute discard.
    Weiguo
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    Weiguo,
    First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
    tool its use is not restricted to migration situations (or file types
    for that matter).
    >
    Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
    in what way did the iMT automated translation contribute to these
    inconsistencies that you cited?
    >
    1. Changed the case of the tag attribute to be the same as what's
    defined in tld.
    example: changed OnClick to onClick
    The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
    introduced was if it had been part of the pre-existing
    project's "extraHTML" (which was written by the original customer and
    just passed through unchanged by the iMT) or if it was added manually
    by the post-migration developer.
    >
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
    >
    >
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
    in your code must have been introduced by your developers manually.
    Its a shame that jasper is so particular, but the iMT could not help
    you out here even if we wanted to. The constants that are used by the
    iMT are defined in
    com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
    see, the only situation of a closing tag with any space in it is
    public static final String CLOSE_EMPTY_ELEMENT = " />";
    But that should not cause the type of problem you are referring to.
    Mike
    ----- Original Message -----
    From: Matthew Stevens
    Sent: Thursday, September 06, 2001 10:16 AM
    Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
    Weiguo,
    Others will chime in for sure...I would highly recommend the Regex Tool from
    the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
    posted to the group (even recently) on directions and advantages of creating
    your own RULES (rules file) in XML for arbitary batch processing of source.
    >
    matt
    -----Original Message-----
    From: weiguo.wang@b...
    [mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
    Sent: Thursday, September 06, 2001 12:25 PM
    Subject: [iPlanet-JATO] sp3 jsp compiler problem
    Matt/Mike/Todd,
    We are trying to migrate to sp3 right now, but have had a lot of
    issues with the new jasper compiler.
    The following workaround has been employed to solve the issues:
    1. Changed the case of the tag attribute to be the same as
    what's
    defined in tld.
    example: changed OnClick to onClick
    2. Removed attributes which are not defined in tld.
    example: escape attribute only defined in three tags
    but in some pages, it's used although it's not defined as an
    attribute
    of certain tags. The jasper compiler doesn't like it.
    3. In an end tag, there can't be any space.
    example: </content > doesn't work. </content> works.
    As I see it, we have two options to go about solving this problem:
    >>
    1. Write a script which will iterate through all the jsp files and
    call jspc on them. Fix the errors manually when jspc fails. Jspc will
    flag the line number where an error occurs.
    2. Write a utility which scans the jsp files and fix the errors when
    they are encountered. We should define what's an error and how to
    correct it. It's best if we combine this with solution 1 since we
    might miss an error condition.
    Actually, there might be another option, which is seeking help from
    you guys since you have better understanding of JATO and iAS. Can you
    do anything to help us?
    We would be happy to hear your thoughts.
    At last, I would like to suggest modifying the moko tool so that
    these rules are enforced and the generated JSPs work with the new
    compiler. This is for the benefit of any new migration projects.
    Thanks a lot.
    Weiguo
    [email protected]
    Choose from 1000s of job listings!
    [email protected]
    Service.
    >
    >
    >
    [Non-text portions of this message have been removed]

  • Servlet Compilation Problem !

    Hi,
    I am just starting to learn servlets and I got problem in compiling them. I got compilation error in
    import javax.servlet.*;statement. Seems that the compiler cannot find the servlet package. I got J2EE 1.4 beta installed on my machine but there is no servlet.jar package. I am using J2SDK 1.4.1_02, J2EE 1.4 beta and Tomcat 4.1.24.
    Can anyone help me with my servlet compilation problem?
    Thanks in advance!
    Josh

    servlet.jar is here :
    <tomcatdir>\common\lib
    add it to your compiler classpath

  • Compilation problem in a JSP page

    Hi all,
    I'm trying to write a jsp page and some java stuff in it.
    It goes something like this -
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
    <%@ page contentType="text/html;charset=windows-1255"%>
    <html>
      <head>
        <meta http-equiv="Content-Type" content="text/html; charset=windows-1255"/>
        <title>Michael</title>
      </head>
      <body>
    <%
              String strError="";
    %>
    </body>Now the problem is that I get compilation problem about the use in java -
    "String cannot be resolved to a type"
    I know for sure that in other computers it's work, the question is what I'm missing?
    I have Java VM installed and I've downloaded and installed the latest JDK, what else?
    thanks,
    Michael.

    Michael4488 wrote:
    BalusC wrote:
    Then you should be using JSTL/EL.I don't familiar with this technology, any way - Its work on one computer so in my understanding it should work on the other as well.It is not related to the actual problem. It was just a comment on your code. Using scriptlets is considered as bad practice.
    I understand that of course, but I don't use any configuration file or set any special parameters in my computer.
    What exactly does the compiler need in order to recognize the Java code in the JSP page? If i manually add the JAVA_HOME environment variable it will work?
    where should I refer it to? "..\Java\jre1.6.0_07\lib" will do?It must point to the root installation directory of the JDK (thus not the JRE!).

  • I am receiving this error message when trying to export pictures: 'Unable to Export": An internal error has occured: Win32 API error 2 ( "The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute.// I have a H

    I am receiving this error message when trying to export pictures: 'Unable to Export": An internal error has occured: Win32 API error 2 ( "The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute.// I have a HP ENVY Phoenix, fully loaded, 1 1/2 years old.

    Nevermind I fixed it. Thank you.

  • Win32 API to get cluster List from domain

    Hi ,
      we are using NetServerEnum API to retrive the list of cluster from domain. But it failed with error 2127 on windows 2008 server and the cluster /list command also failed with same error.
    But if we pass domain name to cluster .exe then it works.
    So is there any win32 API other than NetserverEnum which will give the list of clusters in a domain.

    Hi,
    can you also use powershell here?
    Get-Cluster -domain yourdomainFQDN.com
    This will give you all failover cluster in the specified DNS domain.
    Hope that helps.
    Regards
    Ramazan
    Ramazan Can [MVP Cluster] http://ramazancan.wordpress.com/

  • Win32 API & DLL calls

    Is possible to call in java directly the Win32 API or using a DLL?

    I dont believe you can do it directly but I think you can call a VBSCRIPT that can call WIN32 API directly

  • Win32 API calling by Code Interface Node

    Hi all,
    I wish to call a Win32 API function by using the code interface node.
    However, I don't know the data types in LabVIEW corresponding to the "HANDLE
    *" in Visual C++.
    Here's the function I wish to call:
    BOOL bOpenDriver (HANDLE * phDeviceHandle, PCHAR devname) {
    *phDeviceHandle = CreateFile(devname,
    GENERIC_WRITE,
    FILE_SHARE_WRITE,
    NULL,
    OPEN_EXISTING,
    0,
    NULL);
    if (*phDeviceHandle == INVALID_HANDLE_VALUE) {
    return (FALSE);
    } else {
    return (TRUE);
    Thank you in advance.
    JJ

    If this is really a Windows API function, then the handle can most likely be treated as an I32.
    Note that you can't actually do anything with the handle other than passing it to other functions.
    If you search this site for "LabVIEW" and "DLL" you should find some resources about working with DLLs and Win32 API DLLs.
    Try to take over the world!

  • Win32 api interface

    Does anyone have any information on the win32 api i would like to write a java application that woudl allow me to list all of the task names in the taskmanger
    Something like Win32::Setupsup for perl

    Hello,
    Please,
    is there any body who knows how I can search for the availability of Windows resources through Java. I am trying to write an application that can simulate a situation like this:
    "Imagine that I am using Skype with a video on my webcam. On the other hand I am writing to another friend using MSN. Then my friend wants to add video. My application should notify that the video resource is already in use. Actually this is already done on windows. "
    But I would like to move on the software layer in Java. Any suggestion would be highly appreciated.
    MoiseMbaya

  • Win32 API

    is there ne way i can use win32 API in JAVA, is there ne compatibility possible ?

    http://java.sun.com/docs/books/tutorial/native1.1/
    Read this link.
    ***Annie***

Maybe you are looking for