Archiving and releasing CVI projects

Hi
At my company, we have to release the software code into a version control system.
This is so anybody else can retrieve, modify and rebuild the project, especially when or if I, the creator, is gone.
My question is about NI software versions, both the CVI version and all of the required NI driver versions used to create the project.
The project references many include *.h files in their installed location, usually ..\Program Files\National Instruments\.. etc.
Updating a project relies on the fact that the computer which initially released the build stays in-place, or no NI driver updates occurred.
Building the retrieved project on another computer, therefore, does not work.
So, should my archived/released project copy all driver files [like Nidaqex.h, etc] into a "local" \Include folder, which locks-in that drive version,
or continue to rely on the NI installed folder location?
Accompanying my software release is a companion document called a VD [version document] which fully describes the created environment
required for the initial release. This greatly helps anyone in the future to re-build the project with step-by-step instructions.
If there is any other "white papers" within the NI web-site that would enhance this subject, I would be appreciated to be directed to it.
Scott Youngren

>> "Building the retrieved project on another
computer, therefore, does not work."
Are you sure of your assertion? I continuously switch projects from one computer to another without compiling problems; I also switched during time between PCs with different localization (english vs. italian OS release: it impacts among other things on "program files" directory name) and different OS versions (win2k vs. WinXP) without facing any problem.
IMHO the main hint is to maintain standard SW places when installing NI software on different machines, a fact that permits to switch between them without problems.
A different matter can be the use of non-NI software, for which you will need to investigate on file location for DLLs, include and so on on different machines.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Similar Messages

  • RE: List Archive and Release Management

    Hi back.
    >> what procedures do people use to manage the development, testing
    and release of software?
    It's useful to have a separate repository for Development, QA, Production,
    etc. It's true that you have to 'import' between them, each time you
    propagate changes. It might seem like a pain to constantly export/import,
    but actually it's better that way.
    Firstly, you should only export to QA when you're absolutely sure it's ready
    for quality assurance, and this doesn't happen every day (or shouldn't)
    Second, the advantage of this is that you get a 'clean' import and compile
    each time, with no other baggage. This is especially critical when you
    migrate from QA to a production environment.
    There's no need to have a testing_verXX repository, just make a different
    workspace for each version of test.
    Just check out all the components, import, and integrate. The 'old'
    workspace will have a snapshot of the old release.
    * Don't Update that old workspace or you'll lose it!
    * Put an administrator password on the repos, to protect against
    inadvertent usage.
    * It's expensive to have many repositories running on your environment
    manager, so I recommend only one repos for each of development, QA and
    Deployment.
    * You might want to consider only bringing up the production repos as
    required, they hog RAM like crazy.
    It's critical to have a complete image of each version of every application
    you have in production. That way, you can recreate any problem.
    It's even useful to migrate your development repos every now and then. As
    you know, these repos beasties can grow quite large, and it's god to start
    from scratch on a regular basis.
    For example, every month or so, our core architecure team releases a new
    version of the core components. We all integrate, and we create a new repos
    from the core architecture stuff, and import all our stuff over the top of
    it. That way, we keep a loose coupling between sub-systems, and their stuff
    never depends on ours. Also, with a split developmen repos, you can locate
    the different teams on different intranets, or even on different sides of
    the world, all with relatively little fuss.
    Forté SCM hooks and SCCSWe use a unix version control called CMVC.
    Whenever we integrate, it checks out the pex files, exports them, and checks
    them back in.
    John Pianezze
    S1 Technologies (Asia Pacific)
    Melbourne, Australia
    -----Original Message-----
    From: Duncan Kinnear [SMTP:[email protected]]
    Sent: Wednesday, July 21, 1999 1:05 PM
    To: [email protected]
    Subject: List Archive and Release Management
    Hi folks!
    First of all, does anyone know what's going on with the list archive
    on
    SageIT? There doesn't seem to be a search facility anymore. Seems
    a
    bit weird when each message is appended with a little signature
    'advertising' a searchable archive.
    Second (and this is the biggy!), what procedures do people use to
    manage the development, testing and release of software? I'm
    talking
    about how you keep them separate, how you do hot-fixes, how you
    identify installed versions at customer sites, etc.
    I've thought that we could do it with separate repositories for
    "current
    development", "testing_verXX", "release_verXY", etc., where we
    export
    from "development" and then import into "testing", and similarily
    for
    "release".
    Also, we are looking at using the Forté SCM hooks and SCCS on our
    Unix host to store historical versions of the projects/classes. But
    we
    somehow need to identify which version of a particular component is
    installed at the customer site. I had thought of defining a
    constant in
    each project/class called "SCCS_VER" which contains the SCCS
    keywords that get mapped to SCCS ID and date when put into SCCS.
    Then the constant could be used to display these values in a
    Window's
    "About" window.
    Any thoughts/opinions welcome.
    Cheers,
    Duncan Kinnear,
    McCarthy and Associates, Email:
    [email protected]
    PO Box 764, McLean Towers, Phone: +64 6 834
    3360
    Shakespeare Road, Napier, New Zealand. Fax: +64 6 834
    3369
    Providing Integrated Software to the Meat Processing Industry for
    over 10 years
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive
    <URL:http://pinehurst.sageit.com/listarchive/forte>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

    Under Forte 2 we used to export all projects, then import them into a make
    repository, then produce an app. Due to the time involved importing &
    exporting, and errors resulting from importing projects out of order, we
    switched to making copies of the dev repository and producing apps from
    that. For us, it used to take 2+ hours to export/import, as opposed to 5
    minutes for copying repository files. Unfortunately, we have found that
    unless we force-compile prior to deploying, we will get errors when
    attempting to compile partitions.
    Our current procedure:
    Shut down dev repos
    Copy to make env
    make a workspace that includes all projects
    force-compile
    update
    integrate
    make a new workspace for each app to make
    make each app
    export code
    remove unused workspaces
    clean repos
    -----Original Message-----
    From: Peter Sham (HTHK - Assistant Manager - Software Development, IITB)
    [mailto:[email protected]]
    Sent: Wednesday, July 21, 1999 3:31 AM
    To: John Pianezze; Duncan Kinnear
    Cc: [email protected]
    Subject: RE: List Archive and Release Management
    Hi,
    We, like what you've explained, keep different releases of our application
    in different workspaces. However, when the release is getting larger, this
    "check-out-every-components-then-overwrite-by-import" procedure get tougher.
    Sometimes, it even creates garbage in the repository which corrupts my
    workspace.
    So, I have an alternative proposal on this procedure ( though I haven't
    really test on this idea ) which is to create a new repository for each new
    release.
    What do you think?
    Regards,
    Peter Sham.
    -----Original Message-----
    From: John Pianezze [SMTP:[email protected]]
    Sent: Wednesday, July 21, 1999 3:44 PM
    To: Duncan Kinnear
    Cc: [email protected]
    Subject: RE: List Archive and Release Management
    Hi back.
    what procedures do people use to manage the development, testingand release of software?
    It's useful to have a separate repository for Development, QA, Production,
    etc. It's true that you have to 'import' between them, each time you
    propagate changes. It might seem like a pain to constantly export/import,
    but actually it's better that way.
    Firstly, you should only export to QA when you're absolutely sure it's
    ready
    for quality assurance, and this doesn't happen every day (or shouldn't)
    Second, the advantage of this is that you get a 'clean' import and compile
    each time, with no other baggage. This is especially critical when you
    migrate from QA to a production environment.
    There's no need to have a testing_verXX repository, just make a different
    workspace for each version of test.
    Just check out all the components, import, and integrate. The 'old'
    workspace will have a snapshot of the old release.
    * Don't Update that old workspace or you'll lose it!
    * Put an administrator password on the repos, to protect against
    inadvertent usage.
    * It's expensive to have many repositories running on your environment
    manager, so I recommend only one repos for each of development, QA and
    Deployment.
    * You might want to consider only bringing up the production repos as
    required, they hog RAM like crazy.
    It's critical to have a complete image of each version of every
    application
    you have in production. That way, you can recreate any problem.
    It's even useful to migrate your development repos every now and then. As
    you know, these repos beasties can grow quite large, and it's god to start
    from scratch on a regular basis.
    For example, every month or so, our core architecure team releases a new
    version of the core components. We all integrate, and we create a new
    repos
    from the core architecture stuff, and import all our stuff over the top of
    it. That way, we keep a loose coupling between sub-systems, and their
    stuff
    never depends on ours. Also, with a split developmen repos, you can locate
    the different teams on different intranets, or even on different sides of
    the world, all with relatively little fuss.
    Forti SCM hooks and SCCSWe use a unix version control called CMVC.
    Whenever we integrate, it checks out the pex files, exports them, and
    checks
    them back in.
    John Pianezze
    S1 Technologies (Asia Pacific)
    Melbourne, Australia
    -----Original Message-----
    From: Duncan Kinnear [SMTP:[email protected]]
    Sent: Wednesday, July 21, 1999 1:05 PM
    To: [email protected]
    Subject: List Archive and Release Management
    Hi folks!
    First of all, does anyone know what's going on with the list archive
    on
    SageIT? There doesn't seem to be a search facility anymore. Seems
    a
    bit weird when each message is appended with a little signature
    'advertising' a searchable archive.
    Second (and this is the biggy!), what procedures do people use to
    manage the development, testing and release of software? I'm
    talking
    about how you keep them separate, how you do hot-fixes, how you
    identify installed versions at customer sites, etc.
    I've thought that we could do it with separate repositories for
    "current
    development", "testing_verXX", "release_verXY", etc., where we
    export
    from "development" and then import into "testing", and similarily
    for
    "release".
    Also, we are looking at using the Forti SCM hooks and SCCS on our
    Unix host to store historical versions of the projects/classes. But
    we
    somehow need to identify which version of a particular component is
    installed at the customer site. I had thought of defining a
    constant in
    each project/class called "SCCS_VER" which contains the SCCS
    keywords that get mapped to SCCS ID and date when put into SCCS.
    Then the constant could be used to display these values in a
    Window's
    "About" window.
    Any thoughts/opinions welcome.
    Cheers,
    Duncan Kinnear,
    McCarthy and Associates, Email:
    [email protected]
    PO Box 764, McLean Towers, Phone: +64 6 834
    3360
    Shakespeare Road, Napier, New Zealand. Fax: +64 6 834
    3369
    Providing Integrated Software to the Meat Processing Industry for
    over 10 years
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive
    <URL:http://pinehurst.sageit.com/listarchive/forte>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive
    <URL:http://pinehurst.sageit.com/listarchive/forte>-
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive
    <URL:http://pinehurst.sageit.com/listarchive/forte>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

  • List Archive and Release Management

    Hi folks!
    First of all, does anyone know what's going on with the list archive on
    SageIT? There doesn't seem to be a search facility anymore. Seems a
    bit weird when each message is appended with a little signature
    'advertising' a searchable archive.
    Second (and this is the biggy!), what procedures do people use to
    manage the development, testing and release of software? I'm talking
    about how you keep them separate, how you do hot-fixes, how you
    identify installed versions at customer sites, etc.
    I've thought that we could do it with separate repositories for "current
    development", "testing_verXX", "release_verXY", etc., where we export
    from "development" and then import into "testing", and similarily for
    "release".
    Also, we are looking at using the Fort&eacute; SCM hooks and SCCS on our
    Unix host to store historical versions of the projects/classes. But we
    somehow need to identify which version of a particular component is
    installed at the customer site. I had thought of defining a constant in
    each project/class called "SCCS_VER" which contains the SCCS
    keywords that get mapped to SCCS ID and date when put into SCCS.
    Then the constant could be used to display these values in a Window's
    "About" window.
    Any thoughts/opinions welcome.
    Cheers,
    Duncan Kinnear,
    McCarthy and Associates, Email: [email protected]
    PO Box 764, McLean Towers, Phone: +64 6 834 3360
    Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369
    Providing Integrated Software to the Meat Processing Industry for over 10 years
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

    Hi folks!
    First of all, does anyone know what's going on with the list archive on
    SageIT? There doesn't seem to be a search facility anymore. Seems a
    bit weird when each message is appended with a little signature
    'advertising' a searchable archive.
    Second (and this is the biggy!), what procedures do people use to
    manage the development, testing and release of software? I'm talking
    about how you keep them separate, how you do hot-fixes, how you
    identify installed versions at customer sites, etc.
    I've thought that we could do it with separate repositories for "current
    development", "testing_verXX", "release_verXY", etc., where we export
    from "development" and then import into "testing", and similarily for
    "release".
    Also, we are looking at using the Fort&eacute; SCM hooks and SCCS on our
    Unix host to store historical versions of the projects/classes. But we
    somehow need to identify which version of a particular component is
    installed at the customer site. I had thought of defining a constant in
    each project/class called "SCCS_VER" which contains the SCCS
    keywords that get mapped to SCCS ID and date when put into SCCS.
    Then the constant could be used to display these values in a Window's
    "About" window.
    Any thoughts/opinions welcome.
    Cheers,
    Duncan Kinnear,
    McCarthy and Associates, Email: [email protected]
    PO Box 764, McLean Towers, Phone: +64 6 834 3360
    Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369
    Providing Integrated Software to the Meat Processing Industry for over 10 years
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

  • *** Can I archive and export a self-contained DVDSP project?

    I think I'm having trouble with the burner on my tower so I would like to try my current project on my other tower. I would rather not rebuild the project, so is there a way to archive and export the project as a self-contained file so it will open up on another machine and I won't have to re-link everything?
    Thanks in advance.

    Nope, no way to back up project like that. If you make folders though and then with the Project right beneath the root folder and other folders beneath it, then copy the entire folder over, it will relink. Take a look here
    http://discussions.apple.com/thread.jspa?messageID=2061440&#2061440

  • Release all phases and tasks if project definition is released

    Hello,
    I have several phases and tasks in a project and when I release the project only the first phase is also released. I am not working with approvals.
    Is the a possible to release all phases when the project is released?
    Thank you and have a nice weekend,
      Vanessa

    Hi Vanessa,
    You can create an implementation of BADI dpr_events, with filter dpr_tv_badi_method = ON_DPO_RELEASED.
    ir_sender instance will be the project in that case, so you can easily retrieve the phases object and release them at this moment.
    Matthias

  • Is it possible to make .dll file of .vi project then load it to CVI and use the APIs in the dll to CVI project

    Is it possible to make .dll file of .vi project then load it to CVI and use the APIs in the dll to CVI project?

    Hi Kumar,
    It is possible to make .dll from Labview and i think we can call the same from other programming application also.
    Pls refer the
    below link
    http://zone.ni.com/devzone/cda/tut/p/id/4038
    GAnesan KAni

  • Difference between debug and release

    Hallo,
    I'm in trouble with sending CAN-Message to servo-controllers (Lust).  In debug -mode all works fine, but in release it seem's that there some leaks in the message.
    I've already added some delays between send-orders, but it doesn't help.
    the CAN is a USB-adapter from PEAK.
    1. Does CVI make some changes as I include the peak.dll (included in my project) from debug to release?
    2. Is there some alternative of using the Delay-Command in windows?.
    greetings
    F.A.

    Debug mode and Release mode are different configurations for building your .Net
    project. Programmers generally use the Debug mode for debugging step by step
    their .Net project and select the Release mode for the final build of Assembly
    file (.dll or .exe). follow link for more information
    http://net-informations.com/faq/net/debug-release.​htm
    cros.
    http://net-informations.com

  • Finder crashes, won't let me archive and install

    I'm at a complete loss. After installing the latest update to MacOS X, everything is messed up. And it seems unfixable. The finder won't stay open, no matter what user your under, though I can still open everything from the dock. I've tried:
    1. Creating a new user.
    2. Running disk utility, doesn't work.
    3. Repairing permissions, works, but doesn't fix problem.
    4. Running Norton Utilities, doesn't work.
    5. Archiving and Installing, which brings up an error that tells you to try again.
    6. Archiving and installing, without keeping the user file and network settings in tact.
    7. Random other stuff I can't recall (such as some terminal stuff), but didn't work.
    Is my only option to try to back this stuff up and reinstall? Do you think that will even work? My mother has a copy of disk warrior that she would have to send me. That's something else I could try, but I'm not sure if it would be worth it. Also, I can still boot up in OS 9.
    Crash report:
    Host Name: john-breslins-powerbook-g4-15
    Date/Time: 2006-04-07 18:38:47.168 -0600
    OS Version: 10.4.6 (Build 8I127)
    Report Version: 4
    Command: Finder
    Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
    Parent: WindowServer [56]
    Version: 10.4.4 (10.4.4)
    Build Version: 1
    Project Name: Finder_FE
    Source Version: 5292100
    PID: 1226
    Thread: 2
    Exception: EXCBADACCESS (0x0001)
    Codes: KERNINVALIDADDRESS (0x0001) at 0xa286a90c
    Thread 0:
    0 libSystem.B.dylib 0x9002c128 semaphorewait_signaltrap + 8
    1 libSystem.B.dylib 0x90001990 pthreadmutexlock + 472
    2 com.apple.DesktopServices 0x9289723c GetRootNode + 44
    3 com.apple.finder 0x0001a1ac 0x1000 + 102828
    4 com.apple.finder 0x00015c28 0x1000 + 85032
    5 com.apple.finder 0x00019d2c 0x1000 + 101676
    6 com.apple.finder 0x00013d84 0x1000 + 77188
    7 com.apple.finder 0x0001afa8 0x1000 + 106408
    8 com.apple.finder 0x0001aeb0 0x1000 + 106160
    9 com.apple.finder 0x0001ad44 0x1000 + 105796
    10 com.apple.finder 0x000168ac 0x1000 + 88236
    11 com.apple.finder 0x00016514 0x1000 + 87316
    12 com.apple.finder 0x00014980 0x1000 + 80256
    13 com.apple.finder 0x0000a8f8 0x1000 + 39160
    14 com.apple.finder 0x0000a67c 0x1000 + 38524
    15 com.apple.finder 0x0000a460 0x1000 + 37984
    16 com.apple.finder 0x000069c0 0x1000 + 22976
    17 com.apple.finder 0x0000313c 0x1000 + 8508
    18 com.apple.finder 0x00002d54 0x1000 + 7508
    19 com.apple.finder 0x000a97d0 0x1000 + 690128
    Thread 1:
    0 libSystem.B.dylib 0x9002edcc kevent + 12
    1 com.apple.DesktopServices 0x9288a2b0 TFSNotificationTask::FSNotificationTaskProc(void*) + 56
    2 ...ple.CoreServices.CarbonCore 0x90bc9260 PrivateMPEntryPoint + 76
    3 libSystem.B.dylib 0x9002ba68 pthreadbody + 96
    Thread 2 Crashed:
    0 com.apple.DesktopServices 0x928a70bc TNode::SetTimerToHandleSyncRequest(TNode*, double) + 52
    1 com.apple.DesktopServices 0x928a706c TNode::SyncRequestedTestAndSet(double) + 92
    2 com.apple.DesktopServices 0x9288aa48 TNodeSyncTask::SyncTaskProc(void*) + 400
    3 ...ple.CoreServices.CarbonCore 0x90bc9260 PrivateMPEntryPoint + 76
    4 libSystem.B.dylib 0x9002ba68 pthreadbody + 96
    Thread 3:
    0 libSystem.B.dylib 0x9002c128 semaphorewait_signaltrap + 8
    1 libSystem.B.dylib 0x90001990 pthreadmutexlock + 472
    2 com.apple.DesktopServices 0x92895c3c THFSPlusPropertyStore::Open(bool) const + 440
    3 com.apple.DesktopServices 0x928959a4 THFSPlusPropertyStore::CreateUniqueNameList() + 72
    4 com.apple.DesktopServices 0x92894b24 TNode::ScavengeProperties() + 76
    5 com.apple.DesktopServices 0x92893cb0 TNodeOpenSyncTask::OpenSyncTaskProc(void*) + 228
    6 ...ple.CoreServices.CarbonCore 0x90bc9260 PrivateMPEntryPoint + 76
    7 libSystem.B.dylib 0x9002ba68 pthreadbody + 96
    Thread 2 crashed with PPC Thread State 64:
    srr0: 0x00000000928a70bc srr1: 0x000000000000f030 vrsave: 0x0000000000000000
    cr: 0x42000222 xer: 0x0000000020000007 lr: 0x00000000928a7094 ctr: 0x0000000090001348
    r0: 0x0000000000000000 r1: 0x00000000f0101980 r2: 0x00000000a286a8c0 r3: 0x0000000000653490
    r4: 0x0000000000000000 r5: 0x0000000000000000 r6: 0x00000000ffffffff r7: 0x0000000044370617
    r8: 0x000000000001952e r9: 0x0000000000000000 r10: 0x0000000043300000 r11: 0x00000000a2887648
    r12: 0x0000000090001348 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x00000000928a7094
    r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000000
    r20: 0x0000000000000000 r21: 0x00000000f0101ad0 r22: 0x0000000000100003 r23: 0x000000000061ea20
    r24: 0x00000000a288a8c0 r25: 0x0000000000000000 r26: 0x0000000000000000 r27: 0x000000000181b800
    r28: 0x0000000000000000 r29: 0x0000000000653490 r30: 0x0000000000000000 r31: 0x000000009288a8c0
    Binary Images Description:
    0x1000 - 0x322fff com.apple.finder 10.4.4 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
    0x718000 - 0x71afff com.apple.textencoding.unicode 2.0 /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
    0x8fa79000 - 0x8fd27fff com.apple.QuickTime 7.0.4 /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
    0x8fe00000 - 0x8fe51fff dyld 44.4 /usr/lib/dyld
    0x90000000 - 0x901bbfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
    0x90213000 - 0x90218fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
    0x9021a000 - 0x9026dfff com.apple.CoreText 1.0.1 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
    0x9029a000 - 0x9034bfff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
    0x9037a000 - 0x90734fff com.apple.CoreGraphics 1.258.27 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
    0x907c1000 - 0x9089afff com.apple.CoreFoundation 6.4.4 (368.25) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x908e3000 - 0x908e3fff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x908e5000 - 0x909e7fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
    0x90a41000 - 0x90ac5fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
    0x90aef000 - 0x90b5dfff com.apple.framework.IOKit 1.4 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x90b74000 - 0x90b86fff libauto.dylib /usr/lib/libauto.dylib
    0x90b8d000 - 0x90e65fff com.apple.CoreServices.CarbonCore 681.3 (671.2) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x90ecb000 - 0x90f4bfff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x90f95000 - 0x90fd6fff com.apple.CFNetwork 129.13 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x90feb000 - 0x91003fff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
    0x91013000 - 0x91094fff com.apple.SearchKit 1.0.5 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x910da000 - 0x91104fff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x91115000 - 0x91123fff libz.1.dylib /usr/lib/libz.1.dylib
    0x91126000 - 0x912e9fff com.apple.security 4.3 (25966) /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x913ec000 - 0x913f5fff com.apple.DiskArbitration 2.1 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x913fc000 - 0x91423fff com.apple.SystemConfiguration 1.8.2 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x91436000 - 0x91441fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
    0x91446000 - 0x91466fff libmx.A.dylib /usr/lib/libmx.A.dylib
    0x9146c000 - 0x91474fff libbsm.dylib /usr/lib/libbsm.dylib
    0x91478000 - 0x914f3fff com.apple.audio.CoreAudio 3.0.3 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x91530000 - 0x91530fff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
    0x91532000 - 0x9156afff com.apple.AE 1.5 (297) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
    0x91585000 - 0x91652fff com.apple.ColorSync 4.4.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
    0x916a7000 - 0x91738fff com.apple.print.framework.PrintCore 4.5 (177.10) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
    0x9177f000 - 0x91836fff com.apple.QD 3.8.19 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
    0x91873000 - 0x918d1fff com.apple.HIServices 1.5.1 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
    0x918ff000 - 0x91923fff com.apple.LangAnalysis 1.6.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
    0x91937000 - 0x9195cfff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
    0x9196f000 - 0x919b1fff com.apple.LaunchServices 168.10 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
    0x919cd000 - 0x919e1fff com.apple.speech.synthesis.framework 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x919ef000 - 0x91a2efff com.apple.ImageIO.framework 1.4.6 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
    0x91a44000 - 0x91b0cfff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
    0x91b5a000 - 0x91b6ffff libcups.2.dylib /usr/lib/libcups.2.dylib
    0x91b74000 - 0x91b91fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x91b96000 - 0x91c05fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x91c1c000 - 0x91c20fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x91c22000 - 0x91c69fff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
    0x91c6e000 - 0x91cabfff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x91cb2000 - 0x91ccbfff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x91cd0000 - 0x91cd3fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x91cd5000 - 0x91cd5fff com.apple.Accelerate 1.2.1 (Accelerate 1.2.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x91cd7000 - 0x91db7fff com.apple.vImage 2.3 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
    0x91dbf000 - 0x91ddefff com.apple.Accelerate.vecLib 3.2.1 (vecLib 3.2.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
    0x91e4a000 - 0x91eb8fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
    0x91ec3000 - 0x91f57fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
    0x91f71000 - 0x924f9fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
    0x9252c000 - 0x92857fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
    0x92887000 - 0x9290ffff com.apple.DesktopServices 1.3.3 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
    0x92950000 - 0x92b7bfff com.apple.Foundation 6.4.5 (567.26) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x92c99000 - 0x92d77fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
    0x92d97000 - 0x92e85fff libiconv.2.dylib /usr/lib/libiconv.2.dylib
    0x92f38000 - 0x92f38fff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x92f3a000 - 0x92f4efff com.apple.ImageCapture 3.0 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
    0x92f66000 - 0x92f76fff com.apple.speech.recognition.framework 3.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
    0x92f82000 - 0x92f97fff com.apple.securityhi 2.0 (203) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
    0x92fa9000 - 0x93030fff com.apple.ink.framework 101.2 (69) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
    0x93044000 - 0x9304ffff com.apple.help 1.0.3 (32) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
    0x93059000 - 0x93086fff com.apple.openscripting 1.2.5 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
    0x930a0000 - 0x930b0fff com.apple.print.framework.Print 5.0 (190.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
    0x930bc000 - 0x93122fff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
    0x93153000 - 0x931a2fff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
    0x931d0000 - 0x931edfff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
    0x931ff000 - 0x9320cfff com.apple.CommonPanels 1.2.2 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
    0x93215000 - 0x93522fff com.apple.HIToolbox 1.4.6 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
    0x94160000 - 0x9422afff com.apple.audio.toolbox.AudioToolbox 1.4.1 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x9427e000 - 0x9427efff com.apple.audio.units.AudioUnit 1.4 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x9455c000 - 0x945a0fff com.apple.bom 8.3 (86.1) /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x946bf000 - 0x946cefff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
    0x946d6000 - 0x946e2fff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
    0x94728000 - 0x94740fff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
    0x94747000 - 0x947b8fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
    0x94ae3000 - 0x94ae9fff com.apple.filesync 3.0.4 (99.8) /System/Library/PrivateFrameworks/FileSync.framework/Versions/A/FileSync

    Hi johnink, Welcome to Apple Discussions.
    4. Running Norton Utilities, doesn't work.
    This is probably the source of your problem. First of all get rid of Norton, use it for a coaster or a frisbee but not on your Mac! Do not let Norton near your X system, it will hose it!
    Norton Disk Doctor is not compatible with OS X 10.4 Tiger. Symantec ceased development of Norton Utilities for Macintosh and Norton SystemWorks for Macintosh 2 years ago. But it has been ruining systems since the intro of X.
    You should create a complete backup of your files and erase & re-install the OS.
    -mj
    [email protected]
    iMac G4 17 FP 800 MHz 768MB   Mac OS X (10.4.6)   2 X LaCie d2's APC-UPS / iMac 333MHz 256MB 10.3.9

  • Error while releasing the project

    Hi Friends,
    While releasing the project I am getting the error :-
    JV Object Type Is Required by JV Parameters for company code 1000.
    What does it mean and how can I overcome this.?
    Help will be rewarded and appreciated.
    Regards

    Hi Amit,
    go to CJ02 and open the project click on settlement rule tab(or press F7).
    then u will go on one new screen. in that screen follow the following path
    goto------->settlement parameter (or press F8)
    then u will reach another screen there will be settlement profile
    field . u select it as  not for settlement.
    then back on main project change sreen and save it
    now u go in cj02 and release.
    Regards,
    Vivek Tripathi
    Edited by: vivek tripathi on Sep 24, 2008 6:37 AM

  • File paths and archiving (and referenced files).

    I've come to the stage where I need to start using referenced files (out of disk space on my laptop) and also start archiving projects. One of my plans was to start keeping an off-site backup of all the originals in case something really bad happened. I'm also going to have on-site backup of projects. But for the off-site originals I would like to have some simple way of finding the photos in case something bad happens, my idea was to simply create a PDF from the list view where I could see the photo and the file path to where it's stored (I plan to store them in simple year-month-day hierarchy).
    The reason why I'm not going to archive the projects off-site is simply the cost, I did a test yesterday and it looks like just storing the originals would be approx 1/3 in size of the projects.
    If someone has a better idea of how to handle this please let me knoe

    I'll try to explain.
    About the cost: Hard disk space is really cheap and I can not see how the cost should be that expensive. This is based on your statement that you still have your images on your laptop and that itself limits the amount of space hence a rather small library.
    When it comes to backing up your projects you have several options. First, if you really want to be cheap about hard disk space (I think you should not since your images really are priceless) you can export projects of your referenced images and not consolidate the images into the exported project. Not to consolidate vs. consolidate images on export really makes a difference in the exported project size. On the other hand, not consolidate images on export of a project makes you back up your images separately, which leads to more work.
    My advice is then; buy two disks (preferable three disks), and export your projects with the images consolidated into one of them and start using the other one with your referenced images.
    I always advice users to have their images in at least three different locations and IMHO the ideal solution for you would be to have your images referenced on one disk and mirrored backups on the other two disks, either one stored in two different locations in case of burglary, fire etc.
    Regards
    Paul K

  • File naming, archiving and time management

    I've posted on this subject before, but I have a new twist that I'd like to get some feedback on.
    I usually import my photos, keeping the master (now called original) file name until the end of the calendar year.  At the end of the year, I like to change the original name for classification and archiving purposes.  By then, I've usually made all of the deletions for the year, so I feel comfortable renaming the photos with some sort of counter or index.  My preferred classification system is: "Custom Name"/"Image Date_"/"Counter" (0000).
    The problem that I'm experiencing is that it is impossible to rename my originals using this format without some inaccuracies if I try to name them all at once without readjusting the computer's internal time zone settings.  I live on the east coast, so if I have a photo shot at 10:30 pm PDT on 2011-03-14, it gets named with a date of 2011-03-15, which obviously isn't accurate for when that photo was shot.  Well, it is accurate based on East Coast Time, but I want the file to be renamed with the date that it was shot, where it was shot, not where my computer currently resides.  Of course, I could rename the batch of 2011 photos in segments, but that would mean multiple quits/reopens from Aperture in order to change the time zone appropriately.
    It seems that my only choices are to either rename my photos at the time of import using the correct time zone settings on my computer, or to not use this renaming format.  Neither of these options are very appealing, since this renaming format is my preferred method.
    I guess my question is: does anyone have any insights or advice on either how to better work around this problem, or if not, other renaming methods that they like to use for archival and organizational purposes?  I know there are many to choose from, but I'm looking for something simple, which also provides direct information about the image, should I want to reference my Originals (which I do outside of Aperture from time to time).
    Thanks for adding to this discussion...
    mac

    Allen,
    SierraDragon wrote:
    mac-
    Personally I create a folder for each Project and copy pix from CF card into those folders. Then I import from the backup hard drive into Aperture using the folder name as the Project name.
    Usually each Project includes only one day or less, and I may have YYMMDD_JonesWed_A, YYMMDD_JonesWed_B, etc. for a large or multiday shoot. I do not let any Project contain more than ~400 Nikon D2x RAW+JPEG files.
    Projects are just that and never put into folders other than by month and/or year, just a forever chronological list. All organizing is done via Albums and Keywords. JonesWed_2011 is a keyword that can be an Album instantly when needed; bride is a keyword; wed is a keyword; flower is a keyword; etc.
    I use wedding just as an example. The process applies to all kinds of shoots.
    I use the 1-9999 Nikon auto-numbering of image files, and never rename image files except  sometimes during export. That way original image names can always be found across mass storage devices in the future independent of any application.
    -Allen
    SierraDragon wrote:
    Usually each Project includes only one day or less, and I may have YYMMDD_JonesWed_A, YYMMDD_JonesWed_B, etc. for a large or multiday shoot. I do not let any Project contain more than ~400 Nikon D2x RAW+JPEG files.
    Why do you keep the photo count in a project to around 400 files or so?  Is it detrimental to speed, or are there other considerations that have led you to work this way?
    SierraDragon wrote:
    Projects are just that and never put into folders other than by month and/or year, just a forever chronological list. All organizing is done via Albums and Keywords. JonesWed_2011 is a keyword that can be an Album instantly when needed; bride is a keyword; wed is a keyword; flower is a keyword; etc.
    So, you are saying that you sometimes put projects into folders by month and/or year?  Or, do you just keep all projects at the top level of the hierarchy?  The only folders I use are at the top of my hierarchy, and they are by year, 2002, 2003, 2004...2012.  I then keep all of my projects in the appropriate year.  I used to keep folders that were named things like, "Travel", "Occasions"..., but this became problematic when I had overlap, and images could fit in more than one designated folder.
    SierraDragon wrote:
    I use the 1-9999 Nikon auto-numbering of image files, and never rename image files except  sometimes during export. That way original image names can always be found across mass storage devices in the future independent of any application.
    It sounds as though you don't actually rename your images at all, but rather just keep the original names.  I don't like to do this because after deletions, it creates gaps in my sequence, and I also end up with multiple images with the same name.  I like for each image to have its own unique identifier by name.
    I'm considering importing the images using a version name, where the version is named by the image date.  I'll keep the original file name intact until the end of the year, and then, should I decide to rename my files, I could base my renaming system off of the version name.  This will automatically capture the date of the image without being reliant on my computer's time zone settings.

  • How to display html content with image in Adobe Flash and Flex mobile project?

    Hi,
      I have a html content with image in it. How to display it in Adobe Flash Builder and Flex mobile project? Which control needs to be used for this?

    Hello,
    The only current way is to use an iFrame, or if you only need some html tags you could use the Text Layout Framework.
    Here this is the iFrame approach:
    http://code.google.com/p/flex-iframe/
    If the swc do not work in Flex4 just use its ource code which works...
    ...it is basically based on this:
    http://www.deitte.com/archives/2008/07/dont_use_iframe.htm
    see also and vote, please:
    http://bugs.adobe.com/jira/browse/SDK-12291
    http://bugs.adobe.com/jira/browse/SDK-13740
    Regards
    Marc

  • My iMac has a1T hard drive,and it is full!. So i look for archives and there are 6000 mailrecoveredfrom gmail, and i can not erase them. Is it a virus? What can i do?

    My iMac has a 1T hard drive and it is full ! So i look for the archives and there are6000 mails recovered from gmail and i can not erase them. Is it a virus?
    What can i do ?

    It sounds like a runaway process is filling up your volume.
    Boot in safe mode. First, disconnect all wired peripherals except keyboard, mouse, and monitor, if applicable, and remove all aftermarket expansion cards. The instructions provided by Apple are as follows:
    Be sure your Mac is shut down.
    Press the power button.
    Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including your login items.
    Use a tool such as the one linked below to explore your volume and find out what's taking up the space:
    OmniDiskSweeper - Products - The Omni Group

  • Failed 'Archive and Install' - will CLI ditto or rsync save me?

    I've done an 'Archive and Install' that ran properly, executed the restart, and then presented a message saying the installation can not be completed because of insufficient space on the target volume. To be clear, the computer restarts in the 'Installer' and displays the error message. I click 'OK' and it does a little loop and reappears. I can't properly quit the installer, force-quit, restart, anything. So I eventually power down.
    More info :
    I can boot from the install disk and in the system profiler I see 9.5 gigs free on the HD. The SMART status is verified. In fact the 'Hardware' section and 'Network' section seems okay, the 'Software' sections reveal the faults. Here I see no mounted applications, no extensions, no frameworks, etc. It's as if I can see where the install gave up. I have run disk utility and repaired the disk, the permissions, and it returns no errors and a nice green message. I ran DiskWarrior and it found nothing to repair. I was able to see my files in the preview, including my sparse image, but decided not to go ahead with a re-build, because I don't think that's going to save my system folder that's split in two. (From the failed A&I)
    I am using FileVault and I am aware that these forums advise that I should have disabled it before trying the installation. Alas, the drive-space overhead was not to be found. I did, however, have room enough for the install, I thought. (And I do have my most critical data backed up, but not the whole system.) When I ran the install from the OS X DVD it indicated 15.6 gigs necessary for installation. I had in excess of 18. I know, I know, too close for comfort, and the FileVault image probably needed more overhead, and...
    Chalk it up to knowledge and change.
    So now I've got that external FW drive I should have had in the first place and I want to clone my whole HD over so I can start anew with an 'Erase and Install'. (Unless somebody thinks of something better. Bless the previous system?)
    I'm not an idiot, but new to the command line (at least since the GUI has existed). I'm wanting to try this :
    ditto source target
    or
    rsync -xrlptgoEv --progress --delete / /Volumes/target
    Do I need to be in 'single user mode' (root - which I can access), or should I execute from the terminal via the install disk?
    I just want to be sure I get this right, I'm confident that my data is there I just need to finesse it out.
    Advance thanks to Kappy, your posts have saved me before...

    Doesn't really sound like archive and install would be of much benefit to you, with as fubarred as everything sounds. However, you would at least have what you had before, just in case there's some unixy or other obscure thing that you did in the past that you need to reinstall because of the reversion to an OEM state. After 10.4.0 is reinstalled from DVD, then apply the OS 10.4.11 combo ppc update to get you up to the latest and greatest in one fell swoop. I believe that QT7.4 came out later than 10.4.11 release so that should be okay. Don't know about QT7.3, though.

  • Recursive scanning of .tar.bz2 archives / Older release notes

    This is actually a two part question, but the two parts are somewhat related.  1) Recursive scanning of .tar.bz2 archives  If I create a new content filter to match on executables (attachment-filetype == "Executable") this detects directly attached exe files. It also detects exe files in .zip-archives, and it detects renamed exe files in .zip archives. All is well.  What it does not detect are exe files in .tar.bz2 archives. This surprised me as this is not an especially obscure format, and the Ironport lists tar and bz (along with zip) in the Compressed mime category.  Maybe this is a bug, and it's fixed in a newer release (this is on 6.5.2-101). Which brings me to the next question  2) Older release notes  Where can I find release notes for the releases between 6.5.2-101 and the current release (7.0.1), in order to find if this was fixed along the way?

    Not sure about the tar.bz2 archives, but the older release notes can be found on the support portal under Appliance Documentation > Email. There is a small link at the top right corner of the page "earlier releases". Yes, its very well hidden

Maybe you are looking for