Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Secwin and SB Manifest

  1. #1

    Default Secwin and SB Manifest

    Hello Friedrich,

    when using #embed UAC manifest

    secwin will not find the secwin security file dssw2.tps anymore.

    Any idea how to fix this?

    If i add the manifest from within clarion the are no problems.

    Thanks much

    Kai

  2. #2

    Default Re: Secwin and SB Manifest

    Have to place the dssw2.tps in data directory not in program dir.

    Thanks much

    Kai

  3. #3

    Default Re: Secwin and SB Manifest

    > Have to place the dssw2.tps in data directory not in program dir.

    (cross posted from the other newsgroup since this group is published to the
    SetupBuilder Forums)


    Kai,

    Since your using ProPath, here is the answer (that works here with the
    SecWin demo app at least).


    All you need to do is check the box to tell SecWin to use the Data
    Directory for it's "Position", then enter the variable name that ProPath
    generates for it in the field provided.

    SecWin is looking for a location here, not an INI file.

    So if you have your dssw4.tps file in the MAINData location, you just enter
    the variable name FOLDER:MAINData (see attached screen shot).

    If your putting the file in your SYSTEMData location, you just enter the
    name FOLDER:SYSTEMData

    Note: both of these examples assume you have not changed the default
    variable name.


    In our tests here this works perfectly and it is a one minute fix<g>.

    Does that help?

    Charles



    --
    -------------------------------------------------------------------------------------------------------
    Charles Edmonds
    www.clarionproseries.com - "Get ProPath, make your Clarion programs ready
    for Windows 7 and Vista!"
    www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
    www.setupcast.com - "A revolutionary new publishing system for software
    developers - enhanced for SetupBuilder users!"
    www.pagesnip.com - "Print and Save the Web, just the way you want it!"
    www.clarionproseries.com - "Serious tools for Clarion Developers"
    www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
    and Forms!"
    www.lansrad.com - "Intelligent Solutions for Universal Problems"
    www.fotokiss.com - "World's Best Auction Photo Editor"
    -------------------------------------------------------------------------------------------------------

  4. #4

    Default Re: Secwin and SB Manifest

    Sorry - forgot the screen shot, attached.

    Charles


    --
    -------------------------------------------------------------------------------------------------------
    Charles Edmonds
    www.clarionproseries.com - "Get ProPath, make your Clarion programs ready
    for Windows 7 and Vista!"
    www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
    www.setupcast.com - "A revolutionary new publishing system for software
    developers - enhanced for SetupBuilder users!"
    www.pagesnip.com - "Print and Save the Web, just the way you want it!"
    www.clarionproseries.com - "Serious tools for Clarion Developers"
    www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
    and Forms!"
    www.lansrad.com - "Intelligent Solutions for Universal Problems"
    www.fotokiss.com - "World's Best Auction Photo Editor"
    -------------------------------------------------------------------------------------------------------
    Attached Images Attached Images  

  5. #5

    Default Re: Secwin and SB Manifest

    Hi Kai,

    > when using #embed UAC manifest
    >
    > secwin will not find the secwin security file dssw2.tps anymore.
    >
    > Any idea how to fix this?
    >
    > If i add the manifest from within clarion the are no problems.

    I don't think the manifest has any effect on this - at least I don't recall
    any issues with it. If you are testing this under Vista then most likely
    the file was being virtualized so the program didn't find it.

    I believe there is a setting in SecWin where you specify where the file is

    Best regards,

    --
    Arnór Baldvinsson - Icetips Alta LLC
    Port Angeles, Washington
    www.icetips.com - www.buildautomator.com

    Icetips product subscriptions at http://www.icetips.com/subscribe.php

  6. #6

    Default Re: Secwin and SB Manifest

    > Hi Kai,
    >
    >> when using #embed UAC manifest
    >>
    >> secwin will not find the secwin security file dssw2.tps anymore.
    >>
    >> Any idea how to fix this?
    >>
    >> If i add the manifest from within clarion the are no problems.
    >
    > I don't think the manifest has any effect on this - at least I don't recall
    > any issues with it. If you are testing this under Vista then most likely
    > the file was being virtualized so the program didn't find it.
    >
    > I believe there is a setting in SecWin where you specify where the file is

    Sounds like this might be CapeSoft solution. IS dssw4 file - just an
    updated version of dssw2.tps?

    http://www.capesoft.com/docs/secwin/secwin.htm#FAQ6.2

    6.2. Question: My app was running fine in Windows XP - but in Vista, it
    does not find the security file?

    Answer: It's almost certainly got to do with the location of your dssw4
    file. See the Secwin Global Extension, Files tab.

    Under XP it's ok to place the dssw4 file in the windows directory. In Vista
    this isn't going to work. Recommended practice is setting the dssw4 file to
    be the same location as the rest of the data.

    David

    --
    From David Troxell - Product Scope 7.8 - Encourager Software
    Product Scope 7 Viewer - NO Registration Fee! Free to Use!
    http://www.encouragersoftware.com/
    Clarion Third Party Profile Exchange Online
    http://encouragersoftware.com/profile/clarlinks.html
    http://www.profileexchanges.com/blog/

  7. #7

    Default Re: Secwin and SB Manifest

    Hello,

    thanks much for help!

    I put the dssw2.tps in the data dir. If i compile my app with XP Manifest the
    app will find the dssw2.tps if i compile with vista manifest it will not. I
    tried the manifest from within clarion and with setup builder.

    Best regards

    Kai

  8. #8

    Default Re: Secwin and SB Manifest

    > Hello,
    >
    > thanks much for help!
    >
    > I put the dssw2.tps in the data dir. If i compile my app with XP Manifest the
    > app will find the dssw2.tps if i compile with vista manifest it will not. I
    > tried the manifest from within clarion and with setup builder.

    Kai,

    There are others that are much more expert in this area that could give you
    greatly expanded explanations - but basically, WHAT kind of manifest you
    use makes a huge difference in the Vista - Windows 7 world.

    An XP manifest in a Vista - Windows 7 OS is interpreted as a "legacy" app -
    it actually stores information in an alternative location - virtualstore
    folder - SO it allows your XP manifested "legacy" to write to a folder -
    just not the one that the same app in XP would write to:

    NOW, if the program is Vista manifested - as Bruce explained to you, the
    program MUST conform to Vista - Windows 7 rules and a folder you could
    write to in XP is now READ-ONLY.

    THAT is why it's so important to examine your program's operation overall,
    and make sure it conforms to UAC Safe locations.

    For those using C6/C7 ABC - ProPath is a life saver to help you make your
    Clarion program write to UAC safe locations.

    Product Description - ProPath, MFG - LANSRAD
    Internet Link - http://www.clarionproseries.com/html/propath.html

    HOWEVER, keep this in mind - every Clarion Third Party product you include
    that has read-write operations must be reexamined to make it conform to UAC
    rules.

    ProPath can help in that area, but NOT every Third Party tool has been
    updated to include good UAC safe locations - you'll need to check with each
    vendor for solutions.

    David

    --
    From David Troxell - Product Scope 7.8 - Encourager Software
    Product Scope 7 Viewer - NO Registration Fee! Free to Use!
    http://www.encouragersoftware.com/
    Clarion Third Party Profile Exchange Online
    http://encouragersoftware.com/profile/clarlinks.html
    http://www.profileexchanges.com/blog/

  9. #9

    Default Re: Secwin and SB Manifest

    Hello,

    thanks all for you nice help here :-)

    I think i found that problem: if the data path is to long, secwin canīt open
    the file. This i very
    confusing because secwin will find the dssw2.tps file.

    My path was:

    C:\Users\Public\Documents\XRG Software\XRG Employee Performance Manager

    and i get all that problems, that Secwin canīt open the dssw2.tps file.

    If i use

    C:\Users\Public\Documents\XRG Software\XRG Software

    the dssw2.tps file will found and opened by secwin.

    Now i have to look if some variable is defined to short or what else is happen.

    I let you know.

    Thanks much Kai

  10. #10

    Default Re: Secwin and SB Manifest

    > Hello,
    >
    > thanks all for you nice help here :-)
    >
    > I think i found that problem: if the data path is to long, secwin canīt open
    > the file. This i very
    > confusing because secwin will find the dssw2.tps file.
    >
    > My path was:
    >
    > C:\Users\Public\Documents\XRG Software\XRG Employee Performance Manager
    >
    > and i get all that problems, that Secwin canīt open the dssw2.tps file.
    >
    > If i use
    >
    > C:\Users\Public\Documents\XRG Software\XRG Software
    >
    > the dssw2.tps file will found and opened by secwin.

    Kai,

    It isn't always obvious where the Clarion Third Party company is defining
    their path lengths - I know you asked Charles about ProPath -

    ProPath is defaulted to 512 (defined in the Global extension) and would
    have covered either of your two examples.

    So, ask CapeSoft to help in this important area.

    Historically and generally speaking - Clarion Third Party product paths
    were defined back in the XP days (BUT not according to UAC type paths), and
    usually not changed from one upgrade to the next.

    and also when developers had more of the mind set - VERY short paths such
    as C:\Apps\Data and I have seen defaults in some of the older products set
    to s80.

    David

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •