Executable file icon

Hello.
I have a question about the creation of executable file by LabWindows/CVI 2009. After creating and running the file, in the Windows Property Bar two icons are present instead of one (one of the two disappears when program window is minimized). Is there such a way to have only 1 icon in the property bar?
Thanks
B.M.
Solved!
Go to Solution.

Hi,
assuming that you are referring to the debug executable and task bar buttons you can change the behavior by setting the panel attribute ATTR_HAS_TASKBAR_BUTTON (0, the default, means no separate taskbar button).

Similar Messages

  • Error while running executable file through java in WinNT

    I would like to run an executable file with Java.
    - If I try with notepad or paint, i.e. Windows Applications,
      I have no problem.
    - I also can run Non-Windows-Own Applications, except one.
      I get an error message, if I want to run this program through Java.
    I have tried following commands to run an executable file.
    Runtime.getRuntime().exec("cmd.exe /c "+command);
    Runtime.getRuntime().exec("cmd.exe /c start "+command);
    Runtime.getRuntime().exec("cmd.exe /c start /wait "+command);
    Runtime.getRuntime().exec("cmd.exe /k start "+command);
    command : the path to the executable file
    I can run the application directly, if I click the icon on desktop,
    but not through Java.
    here is the error message I get
    screenshot : http://www.aykut.de/error_message.jpg
    Text : "Security Check failure"
            The Logon System has been tampered with.
            The Administrator will need to re-install.
    my Idea :
    The application is "old".
    I think it was written for Win 3.1.
    Therefore I don't know if there is any other
    possibilty to run a "DOS Exe File" through Java.

    I have just figured out how it works,
    if somebody else here in forum have this problem,
    here is the solution :
    String path = "F:\...\...\Application.exe";
    String envDir = path.substring(0, path.lastIndexOf("\\"));
    String[] command = {"cmd.exe", "/c", "start", "/wait", "/D"+envDir, path};
    Process process = Runtime.getRuntime().exec(command);
    "start /Dpath" => path: environment directory F:\...\...\
    "start /wait" => wait until Application.exe terminates
    if you use Win95 or Win98 use command.com instead of cmd.exe
    Aykut

  • Word Docs have become Unix Executable Files!

    The subject says it. This has happened on both my wife's iMac G5, and my MacBook Pro. Some, not all, of our Word docs, (both using 2004, running OS X.4.7) have had their icons turned into a gray console, and in "Get Info" identify themselves as "Unix Executable File." When opened in Word, I get the option to open as if it were a foreign file, and typically, it opens with all formatting gone, and all kinds of bizarre characters at the beginning (and sometimes end) of the doc.
    Now, I can salvage the data, it seems, but is there some way to simply undo this damage without manually going through every file?
    I must say, this is exactly the kind of junk that I would expect to find on a PC. This is a stunningly bad problem, by far the worst I've experienced in almost 15 years of using Macs. I would assume that Apple is aware of this, and that they can:
    1) Explain what happened.
    2) Explain a quick and easy fix.
    Thanks to anyone (from Apple or otherwise) who can do 1 and 2 above.

    Jeffois,
    The first command I gave to you will render the directory in question, and all nested directories, inaccessible. The second command will make the diretories accessible again.
    There is a possibility that there are files in this directory structure which are not owned by you. Not likely, but I must make the assumption that these could be encountered when I give such commands "in the dark" as it were. In such a case, you would see an error regarding these files, thus the warning.
    You can return your directories to accessibility using the second command, regardless of errors you might encounter. If you do encounter errors, I will post a different form of the same commands that will work.
    Be prepared to deal with this problem any time you transfer files from a Windows-formatted volume. This is not a Windows problem, but rather one of differences between the two file systems. If you see a file show up with the executable icon, you might want to remove the execute bit right away. Unfortunately, there is no way to do this in the GUI, so you must resort to using Terminal.
    This shouldn't be too much of a problem. Just open Terminal, type this text with a traling space:
    <pre style="overflow:auto; font-family: 'Monaco'; font-size: 10px">chmod a-x</pre>
    then select all of the new files and drag them all into the Terminal window. This will create a rather long command line that includes the full path to every file you dragged in. Just press <RETURN>, and "POOF," no more execute bit!
    Scott

  • Photoshop .psd files converted to Unix Executable files

    I'm an illustrator and I store my art on CDs and DVDs. After a period of time my files are converted from Photoshop .psd files to Unix Executable files and I can't open them. What can I do to get my work back??? -and keep this from happening in the future. Why does it do this????
    Thanks for any help.

    The file sizes range from 22.2 MB to 67.9 MB.
    Size isn't the issue then. Linc was asking that question because we see that with other file types. Older fonts in particular, which have all of their data in the resource fork. If that gets stripped, you end up with a zero byte file.
    Does that mean I'll have to go through the Adobe authorization process for Photoshop again?
    If the version of Photoshop you're currently using is already activated, then no. Either way, it has nothing to do with .psd files showing as UNIX executables.
    In Windows, any file that doesn't have an association to a program is displayed as a white, dog-eared piece of paper with the Windows logo in the middle. That's Windows' way of saying, "I have no idea what this is." In OS X, (except for those files which actually are UNIX executables), displaying them as such is OS X's way of saying the same thing.
    I thought I was home free when the icon changed to a thumbnail picture of the illustration, but PS refuses to open it saying it is not a Photoshop file. ???
    Now that is weird. As of Snow Leopard, Apple put the old Type and Creator codes to rest. It will read them as a last resort to try and identify an older file, but none of Apple's applications add them to any file they save. For better compatibility with Windows, and OS X's own underlying UNIX core, file extensions have taken their place. So adding a .psd extension should have worked. Without playing with one of your files, I couldn't tell you why Photoshop declared it wasn't a valid .psd image.
    On a side note, Apple added Uniform Type Identifiers to OS X to keep things separate. A big problem in Windows is that multiple apps may use the same file extension. EPS is a big one in printing. So you have Photoshop, Illustrator, Freehand, Quark and others all using .eps for Encapsulated PostScript files. However, Windows can only associate one application to any given extension. So if Illustrator happens to be the one tagged to .eps files, it will try to open any file ending in .eps, no matter what program actually created it. OS X keeps them separate with Uniform Type Identifiers. So even though multiple files may have .eps file extensions, the extra metadata keeps track of what program it actually belongs to.
    This is what is part of the LaunchServices database, and was why it was my first suggestion. If that database is wonky, you'll see weird things like this. Have you tried clearing it yet?
    The files are fine when newly burned to CD. It is only months, or years, later that they become Unix Executable Files.  This has happened to just about all of my CD backups and it's frustrating to think that CD backup doesn't work across newer OSs and Photoshop upgrades. I suspect that may be the problem, but it just shouldn't happen.
    That shouldn't make a difference. I've got a bunch of very old files created in Photoshop back from OS 8 on CD. No file extensions, as nothing did at the time. Just Type and Creator codes. They all open fine in PS CS5.5 in Snow Leopard, though the native Photoshop files do need to have a .psd extension added.

  • Why did all my files suddenly become UNIX Executable Files?

    After reformatting my hard drive and installing Panther server, I restored the Retrospect back up of files to my home directory. Unfortunately, all the files that didn't have suffixes (eg: .doc, .xls, .pdf, etc.) suddenly had their icons replaced with an icon of a black console with the word "exec" typed in. And their kind was lost and all became: UNIX Executable File.
    Ever since this Panther server has been acting eratically.
    I have been able to resurrect the affected files by opening them in their native application and resaving them with the proper suffix. But there are thousands of files and dozens of applications that could have made each file.
    Is there a way to resurrect these files without having to open and resave every single file in its native application one at a time? Could these thousands of UNIX Executable Files be causing problems for Panther server?
    Thanks for your input.
    Gregg

    Hi TropicalReef,
    At some point during your backup/restore process the executable bit was set on your files. This should not cause a problem with the overall performance of the operating system. But to some extent this is a security risk. There are a number of GUI applications that can change file permission. I recommend you download one and remove the executable bit from your files. Read the developers documentation carefully. Changing file permission especially in batch mode can be very dangerous.
    The easiest way to make you files double clickable is to add the appropriate suffix to the file name. Again there a number of shareware and freeware apps that will do this. Check MacUpdate and VersionTracker.

  • Where are these unix executable files coming from and how do I recover the original text file?

    where are these unix executable files coming from and how do I recover the original text file?

    When you upgraded to Lion did you have AppleWorks installed on your mac?
    Most of the AW documents can be opened by Pages 09 or Numbers 09 with most of the orginal format in tact. (I do not know if previouse verision will work) just open the AW file with both and see which one works best.
    Text Edit will also open most of the AW files as well but will require a lot of work to restore them to their orginal format.
    If you have AW Database documents then they are not supported. 
    These document show up as "exec icons", Kind: Unix Executagle File.
    They also will show up as .cwk file if they are small files. I have a couple that were under 1mb that are shown as " Kind: AppleWorks Document" but will not open.
    The only option to open AW database is to have AW installed on a mac with a pre-Lion OS to recover the file.

  • Unix executable file- in backup email files

    Hello,
    I've searched the discussions and found a few posts that resemble my question but nothing exactly/ nothing suggested has worked so far.
    I have entire email files backed up to a LaCie drive- 2 actually. All of the email backup icons have been changed to "Unix executable file"- the icon is a grey box with "exec" on it.
    The promising side is that the files are still large- 301 mgs, etc- so I would think there is still information in the file.
    I've tried going into "Info" and changing "open with" to entourage or thunderbird. Or even Excel to see if I could get a tab delimited file and convert. Nothing has worked so far.
    I've seen this before with other types of backup files as well. I haven't changed operating systems, have only been working on Macs, this has happened both on a wireless ethernet disk and a firewire drive.
    Any suggestions? Thanks!
    jz

    Hi,
    Never fear! Your original MacOS disks should include the developer tools. They call it xcode these days. By default it should install extra command line utilities in /Developer/Tools. So really the command should look like:
    /Developer/Tools/SetFile -t 'TEXT' -c 'CSOm' your_mbox
    You can add /Developer/Tools to your $PATH variable to avoid the extra typing. But you can do that later. Just replace your_mbox with the path to one of your Eudora mail boxes that you've copied back to your harddrive.
    Cole

  • Unix Executable Files...why won't they open?

    I now have a new iMac and using Mavericks 10.9.3. I used TimeMachine to transfer my files (that contained these strange "Exec" files after I had updated to Mavericks on my previous iMac) a number of these files turned into something called "Exec" files (Black rectangular icon with green "exec" in the upper left corner). and randomly appeariing in diff software.  Have these files become corrupted? Should I trash them?
    Thanks for any help
    Julie

    In the Finder, click on these Exec files and press command+I. If the file is an AppleWorks document (even with no extension) it will tell you that. If it is a UNIX shell script with owner+group+world execute permissions, or a compiled executable from source code, it will state that it is a UNIX Executable File.
    In the Terminal application, you can use the file command to discern (usually) more accurately what these black Exec documents comprise. The filenames that I use below at random, were created on my machine.
    file -b dictx2
    Mach-O 64-bit executable x86_64
    file -b mvim
    POSIX shell script text executable
    file -b fubar.cwk            # Finder Get Info says it is an AppleWorks document, and opens nicely in LibreOffice
    data
    The decision to delete these depends on what they are, the purpose they may continue to serve, and in the case of word processing documents, content for retention consideration.

  • Unix Executable files within apple programs, problem???????????

    Sometime ago i was using logic pro 7,and saving my project folders on an external drive,,,all of my folders turned into EXE files and couldnt be read,,
    Now ive wiped my internal drive,,reloaded the install disks,,used disk warrior,
    If i highlight any icon such as logic,iDVD,garage band,,or any other,,"show package contents" ???? click contents then open the "MacOS" folder,, A black Unix Executable file is here,,,,in all programs,!!!!!!!!!!
    I have tried to find out if this is normal as i lost a huge amount of project folders,,,,but there is nothing or no one i can find to resolve this issue,
    i would just like to feel safe as im not much of a computer wizard,,
    anyone got an idea? yours confused,, steve

    I have tried to find out if this is normal
    Yes, it is.
    (48530)

  • Unix executable files - is it a virus

    I'm not sure if I'm in the right space but...
    Our backup hard disc which is connected to a small network (five machines) has suddenly had all the Quark files converted to "Unix Executable File" with a scarey looking devil icon on it.
    Is this a virus. How do we get rid of it. Are the files gone for ever? The hard disc is not connected directly to the internet but is a storage place for files downloaded from it. However none of the machines connected to the web have had the same thing happen, as yet.
    Desperately looking for an answer.
    Thanks for your help
    Bruce

    Bruce,
    If your network is connected to the internet, so is your network storage device, er, backup hard disk. Make sure that your network is properly configured and protected.
    Scary devil icon? Would it resemble one of these beasties or is it more like this one?
    Now for the good news: This is common for Quark files.
    I googled the problem and here are some links that tell you how to fix the problem: Quark 3, Quark 6, a macfixit tip, and a macosx.com post.
    Camelot's advice may not work, or may only work once. See the links for details.
    Hope this helps.
    -Wayne

  • Opening a Archival UNIX Executable file

    I am currently using Maverick 10.9.2 . I am trying to open an archive file amd folder.  The problem is that when I download the file, it appears as unix executable file and it cannot be opened. I have read in past posts that if the file does not have extension, it may become a unix executable file. I have changed them to .DOC, but no luck. Also when I tried to download the file later, the format changed to documents, but still could not be opened. Is there a problem because it was archived? If you have insight this problem as well, I would appreciate if you could let me know. Thanks in advance.

    I'm assumimg that the file is either a zip, tar, gnuzip, or bzip2 archive. Remove the file extention from the file and move it to your desktop. From the Finder.app > Go menu > select "Go to Folder...", in the text box type- /System/Library/CoreServices . Drag the Archive Utility.app on to the dock. The Archive Utility.app icon will now appear in the dock. Drag the archive file onto the Archive Utility.app icon and the archive should be uncompressed and appear on your desktop.

  • CDF type to Unix Executable File

    When downloading a Comma Delimited File Database, Safari saves the download as a "Unix Executable File" and my database (Filemaker) will not recognize the file type. What is the problem (or solution)? Thanks in advance

    There is no extension. What appears is the file name with an unusual (for Mac) icon. This was not the solution, but thank you. I have subsequently tried the download on two other machines with the same result. The question remains why does Safari (or Mac OSX) change a comma delimited file to an Unix executable file. I did discover that by opening the file in textedit and saving it, Filemaker will then work the file. That is only a workaround, not a solution.

  • Tugsten E2 /unix executable file

    My laptop is a MAC power book G/O.S.10.4.11.
    My external hard drive crashed. I recovered the info.The back up i had from last version of my desktop palm shows only the file mame i gave it -NON RECOGNIZABLE ICON. I'm not able to open it, when i drag the file into the palmdesktop icon it doesnt read it. On the File info says:
    KIND:unix executable file
    I opened the file on microsoft word-officce 2004 and just appear like programming caracters.
    I think I just need to add the file extesion in order the palmdesktop software read the file.
    Do you know what the extension is?, or How to make readable opening it with the palm desktop sofware?
    Post relates to: Tungsten E2

    Hey!, I've re-installed palm desktop program and it didn't read the file.
    In Mac, when a file is not readable, show's you a blank icon or in this case is showing a grey icon with green letters saying EXEC. That's why I think what I need is to add the correct extension to the file in order to be recognized by palm desktop folder.
    I'll  appreciate your help.
    Thank you.

  • "Unix Executable File" how to read?

    In clean up my older folders I've found several files that don't have any of the usual icons, but rather a Terminal file icon and the Get Info shows that they are "Unix Executable Files."
    I opened them using Text Edit and found that some have the type/creator code of WDBN MSWD and others are PICT SPNT, or DRWG MD

    Tod Wicks wrote:
    In clean up my older folders I've found several files that don't have any of the usual icons, but rather a Terminal file icon and the Get Info shows that they are "Unix Executable Files."
    I opened them using Text Edit and found that some have the type/creator code of WDBN MSWD and others are PICT SPNT, or DRWG MD
    According to this Web page
    http://support.grouplogic.com/?p=1563
    the first one is a Microsoft Word file. According to a Web search the second one is from SuperPaint and the third is from MacDraw.

  • What is an unix executable file that appeared in my folder?

    HI,
    In my folders structure I have a folder named "jobs: where I put my working files etc.
    Yesterday inside the "jobs" folder I found a file with the same name "jobs" , its icon is dark gray and it is a "unix executable file" with zero bytes...
    How was it created there?
    I think I did a permission repair this week, but this is the first time I see a Unix exec file ...

    ** folder named "jobs:" **
    When I tried to create a folder with that name, the Finder told me that the name was not valid. A colon in a Mac file or folder name used to be a bad idea. I guess it still is. I'd rename that folder to exclude the colon.

Maybe you are looking for