Secwin and SB Manifest

[NewsArchive]

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

[NewsArchive]

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

Thanks much

Kai

[NewsArchive]

> 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"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

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"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

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

[NewsArchive]

> 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/

[NewsArchive]

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

[NewsArchive]

> 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/

[NewsArchive]

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

[NewsArchive]

> 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

[NewsArchive]

> 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.

Kai,

As mentioned before, you can quickly adjust the variable size of ProPath on
the MISC tab of the global extension. It defaults to 512.

However here in all our tests for SecWin4, it works fine with that size.

You could set it to 256 and recompile in a minute or so (ProPath uses the
number you specify to set the variable length).

But I do doubt that is your problem.

If it fixes it, be sure to let us know as it would appear to be a SecWin3
issue then.


BTW - what version of SecWin and Clarion are you using?

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"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

Hi Charles,

i´m using Secwin 3.x latest release.

I think also there is no issue with propath.

It must be an problem with Secwin / Pathlenght / Vistamanifest

I hope i can find the reason next days.

If not i could use short directory names but i try to find the problem to give
the info to the community.

Best regards

Kai

[NewsArchive]

> i´m using Secwin 3.x latest release.

Ok, if I get some time over the next few days I may see about downloading
that version and testing it here (I've been up to my ears in getting
ProImage and ProScan ready to release).


> I think also there is no issue with propath.

I don't think so either.


> It must be an problem with Secwin / Pathlenght / Vistamanifest
>
> I hope i can find the reason next days.
>
> If not i could use short directory names but i try to find the problem to give
> the info to the community.

I really don't think it is the length of the path perhaps as much as a
manifest or permission thing.

Instead of this:

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

Try this:

C:\Users\Public\Documents\XRG\XRGEPM

That will be a short enough path and I am almost willing to bet that it
will not work for you.

Either way it is an easy test that will put the path length question to
rest once and for all for you.

:-)

Good luck on your projects!

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"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

Actually, the manifest didn't cause the problem but did reveal it.
I'm guessing he was using an XP manifest when he had Clarion add it, so his
app was virtualized and appeared to work (as long as only the one user
account with the virtualized files logged on).
With the SB manifest, his non-compliant app was revealed as such.

Jane