PowerBasic in Vista

[Jim Seekamp]

I was forced to start using a Vista machine for development, and every time I compile in Windows Vista, it brings up an annoying security warning window that asks if I'm sure I want to run this software!!
I turned off user account security in Vista, but it STILL COMES UP EVERY TIME!!

Anyone know a workaround for this??

[Scott Slater]

Is the compiler installed on that machine's hard drive or on a remote? I have it installed under Vista 64-bit here on the local hard disk and have never had any such warnings. My UAC is enabled.

[Jim Seekamp]

It's installed on the same hard drive, but when I moved to this computer, it only had a C: drive, and my old one had a C and a D -- I had all my PB pathing to the D drive, so I created a "network" D: drive, pointing to a folder on the C: drive where I put all my old D: drive stuff. Do you think that's the problem??

[Cliff Nichols]

My answer would be yes.
I see the problem all the time (XP and Vista) that it asks about running this software because it was downloaded (even files from my network)

I have not found how to turn it off (did not research much), but since I am admin and the only user, then it should not affect me, but it does.

I suspect M$ counts anything not internal to the computer to be "The INTERNET" whether it is contained inside a firewall or not????

[Dale Yarker]

What folder/directory do you keep you .bas files and folder you compile to?

Vista is protective of C:\Program Files and C:\ProgramData

Cheers,

[Michael Mattias]

Using File Exporer, check the files' "Properties"

If an "unblock" button appears, do that and 'Apply'

I think this only happens if you use IE/OE, but other browsers and mail clients may do the same thing.

If using IE/OE, if you download or save a ZIP file attachment, do this to the ZIP file BEFORE you extract files, or you may have to do this 'properties/unblock' thing for each file extracted from the archive.

[Scott Slater]

Use the following steps:

1. Open Internet Options Dialog Box from IE7 (YES that's correct, IE7 )

2. Select the Security Tab

3. Select 'Local Intranet' icon from the zones shown

4. Click on 'Sites' command button, which opens a 'Local Intranet' Dialog Box

5. Click on the 'Advanced' command button, which opens a dialog box where you are able to;

add and remove websites from your intranet.

6. Add "\\servername\" to list of websites. Click 'Close, then 'OK' to return to main Internet Options Dialog Box.

The default security level should now allow you to run your EXEs from the network drive without getting these warnings.

[Cliff Nichols]

Internet Options Dialog Box from IE7 (YES that's correct, IE7 )

Ahhh yessssss....the almighty IE that thinks it is your security center. (GRRRRRRrrrrr.....will they NEVER learn that a browser is a browser, and not a security program???)

I will NEVER figure out why so called "Programmers" will jump through hoops to force you to use an M$ product. (Except they were mis-lead, and don't know any better????) instead of a simple 1 line of code allowing you to open YOUR default email, browser, other application.....rather than forcing you to use theirs????

1 line of code....is that soooooo hard to keep track of???? just 1 line????

I will digress, but still annoys me that to fix a security setting, I have to know to look at IE to fix it, and not in "Security Settings" where it belongs.

[Kev Peel]

"Internet Options" (Inetcpl.cpl) is a control panel applet, it does not require IE to be launched. There is a link to it from IE (as you would expect)

[Cliff Nichols]

"Internet Options" (Inetcpl.cpl) is a control panel applet, it does not require IE to be launched. There is a link to it from IE (as you would expect)

Thanx for the pointer Kev :wavey:

(Still annoys me that when trying to debug a security setting M$ hid it in IE or Internet options.....but I digress)

But to me it REALLLLLY is counter-intuitive

Yeah its one of "Them Bones" that this ole' dog can NOT let go of

[Patrice Terrier]

Use a manifest to change the application's privilege

Example:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
    <assemblyIdentity 
        version="1.0.0.0" 
        processorArchitecture="X86" 
        name="www.zapsolution.com" 
        type="win32" />
    <description>WinXP Manifest For ZAP</description>
    <dependency>
        <dependentAssembly>
            <assemblyIdentity 
                type="win32" 
                name="Microsoft.Windows.Common-Controls" 
                version="6.0.0.0" 
                processorArchitecture="X86" 
                publicKeyToken="6595b64144ccf1df" 
                language="*" />
        </dependentAssembly>
    </dependency>

    <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
      <security>
        <requestedPrivileges>
          <requestedExecutionLevel level="asInvoker" />
        </requestedPrivileges>
      </security>
    </trustInfo>

</assembly>

The important section is shown in red below:

<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" />
</requestedPrivileges>
</security>
</trustInfo>


and add this line to your resource file:
CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST "control.man"
where "control.man" is the name of the manifest file to be used.

[Mike Doty]

http://www.powerbasic.com/support/pb...ad.php?t=38151

[Scott Slater]

It's a really good idea to use a manifest regardless of whether or not your ap needs additional privileges if you intend to deploy on vista. If an ap has no manifest vista will try to determine needed privileges based on the name of the exe file which can sometimes cause headaches.

You can also embed the manifest directly into the RC file as shown in this example.

#include "resource.h"
#define IDR_MANIFEST 1 // 2 for a DLL
#define RT_MANIFEST 24
 
AAA ICON DISCARDABLE MYICON.ICO
 
// This can be used to imbed the manifest directly into the RC file instead of using
// an external XML file...
 
IDR_MANIFEST RT_MANIFEST MOVEABLE PURE
{
    "<assembly xmlns=""urn:schemas-microsoft-com:asm.v1"" manifestVersion=""1.0"">
       <assemblyIdentity
         name=""Microsoft.Windows.Shell.shell32""
         processorArchitecture=""x86""
         version=""2.20.0.01""
         type=""win32""/>
       <description>Windows Shell</description>
       <dependency>
         <dependentAssembly>
           <assemblyIdentity
             type=""win32""
             name=""Microsoft.Windows.Common-Controls""
             version=""6.0.0.0""
             processorArchitecture=""x86""
             publicKeyToken=""6595b64144ccf1df""
             language=""*""
           />
         </dependentAssembly>
       </dependency>
       <asmv3:trustInfo xmlns:asmv3=""urn:schemas-microsoft-com:asm.v3"">
         <asmv3:security>
           <asmv3:requestedPrivileges>
             <asmv3:requestedExecutionLevel
               level=""asInvoker""
               uiAccess=""false"" />
           </asmv3:requestedPrivileges>
         </asmv3:security>
       </asmv3:trustInfo>
     </assembly>"
}