🚀 go-pugleaf

"bar" <shaikakbar250281@yahoo.co.in> wrote in message 
news:480642de@newsgroups.borland.com...

> DeleteFile("C:\\Program Files\\MyProgram\\a.jpg");
>
> The above works in XP. In Vista it doesn't work, the
> user is administrator. How to resolve the issue.

Did you verify that the file actually exists?  What does DeleteFile() 
actually return?  If FALSE, what does GetLastError() return?


Gambit 

bar wrote:

>DeleteFile("C:\\Program Files\\MyProgram\\a.jpg");
>
>The above works in XP. In Vista it doesn't work, the user is administrator.
>How to resolve the issue.

Fairly simple, really...
Don't place any files in the Program Files that you want to delete.

Only viruses and malware try to delete files in there.

Bob Gonder <notbg@notmindspring.invalid> wrote:

>bar wrote:
>
>>DeleteFile("C:\\Program Files\\MyProgram\\a.jpg");
>>
>>The above works in XP. In Vista it doesn't work, the user is administrator.
>>How to resolve the issue.
>
>Fairly simple, really...
>Don't place any files in the Program Files that you want to delete.
>
>Only viruses and malware try to delete files in there.

... and any program using the old, old paradigm of keeping everything in
one place.

Alan Bellingham
-- 
Team Browns
<url:http://www.borland.com/newsgroups/> Borland newsgroup descriptions
<url:http://www.borland.com/newsgroups/netiquette.html>      netiquette

Alan Bellingham wrote:
>Bob Gonder wrote:
>
>>Only viruses and malware try to delete files in there.
>
>... and any program using the old, old paradigm of keeping everything in
>one place.

By the great and glorious wisdom of Microsoft, they are the same thing.

Bob Gonder wrote:
 > bar wrote:
 > >
 > > DeleteFile("C:\\Program Files\\MyProgram\\a.jpg");
 > >
 > > The above works in XP. In Vista it doesn't work
 >
 > Fairly simple, really...
 > Don't place any files in the Program Files that you want to delete.
 >
 > Only viruses and malware try to delete files in there.

Yikes... One of my apps (totally free, but not viral or malicious in any 
way) uses the installation directory (C:\Program...) and its contents as 
a point of reference. The individual users gets their default files from 
there. On occasion, the default files names changes and some files are 
removed and some are added and some files even gets their contents 
changed... If *any* user of the app decides to click the "update" button 
(when presented to them), everything in the reference directory 
(C:\Program...) will get updated.

Updating has exactly the same effect as installing the app. clean, 
except it wont be noticed by old users of the app.

"First time user? Fine, you get the latest default settings! Old user? 
Ok, just enjoy the new features of the application. Your old settings 
are unchanged! Really!"

How should I split my application up to pass the viral test?

Is there some sort of posix placement for apps./files in Windows 
nowadays? That'd be great!

Cheers,
Ted

"Ted Lyngmo" <tedREMOVETHIS@lyncon.se> wrote in message 
news:4807af87$1@newsgroups.borland.com...

> One of my apps (totally free, but not viral or malicious in any way)
> uses the installation directory (C:\Program...) and its contents as a
> point of reference. The individual users gets their default files from 
> there.

That portion is fine.

> On occasion, the default files names changes and some files are
> removed and some are added and some files even gets their
> contents changed... If *any* user of the app decides to click the
> "update" button (when presented to them), everything in the
> reference directory (C:\Program...) will get updated.

Your updater needs to run under an admin account in order to changed files 
in the "C:\Program Files" hierarchy.


Gambit 

Remy Lebeau (TeamB) wrote:
 > Ted Lyngmo wrote:
 > >
 > > On occasion, the default files names changes and some files are
 > > removed and some are added and some files even gets their
 > > contents changed... If *any* user of the app decides to click the
 > > "update" button (when presented to them), everything in the
 > > reference directory (C:\Program...) will get updated.
 >
 > Your updater needs to run under an admin account in order to changed
 > files in the "C:\Program Files" hierarchy.

Howdy Remy!

Got that, but if we (the users and I) needs the program to update the 
way it did pre Vista? It's been working since W95...

Cheers,
Ted

"Ted Lyngmo" <tedREMOVETHIS@lyncon.se> wrote in message 
news:4807c404$1@newsgroups.borland.com...

> Got that, but if we (the users and I) needs the program to
> update the way it did pre Vista? It's been working since W95...

These restrictions are not new in Vista.  They have been around for a long 
time.  It is just that each new OS version enforces them more then the 
previous OS version did.


Gambit 

Ted Lyngmo wrote:

>Is there some sort of posix placement for apps./files in Windows 
>nowadays? That'd be great!

Currently (Vista), C:Users/[UserName]/AppData/[Local or Roaming]/YourApp

If you use old code, Vista places your data in c:ProgramData/,
same folder structure as Program Files.
I have no idea how many version of Windows that will last.

You should be (for several releases of Windows now) using
the shell functions to get the data paths.
Such as SHGetFolderLocation and a few more SHGet....

You should be able to Google this group for code.

Bob & Remy,

I'm sure you are right... Most of the code used when installing and 
updating my app is derived from what I've seen in the registry ... in 
W95 & W98 :-)

Time to read up a bit...

Thanks,
Ted

Bob Gonder wrote:

> Ted Lyngmo wrote:
> 
> 
>>Is there some sort of posix placement for apps./files in Windows 
>>nowadays? That'd be great!
> 
> 
> Currently (Vista), C:Users/[UserName]/AppData/[Local or Roaming]/YourApp
> 
> If you use old code, Vista places your data in c:ProgramData/,
> same folder structure as Program Files.
> I have no idea how many version of Windows that will last.
> 
> You should be (for several releases of Windows now) using
> the shell functions to get the data paths.
> Such as SHGetFolderLocation and a few more SHGet....
> 
> You should be able to Google this group for code.
> 

Onething i noticed a "Virtual Store\Program Files\App\" directory storing 
exact backup of directories that have been created in the "C:\Program 
Files\App\" directory.

My app when runs checks for the directory and create some directories in the 
"C:\Program Files\App\" if not exist. XP it was working fine.

In vista if i delete the sub directories under "C:\Program Files\App\" 
manually. The program is considering the "Virtual Store\Program Files\App\" 
path as a app folder path and i don't have any control over the "C:\Program 
Files\App\" directory to create sub directories.

But anyhow i changed the app subdirectories path for the below.
XP -C:\Documents and Settings\All Users\Application Data\App\SubDirectory
Vista - C:\Program Data\App\SubDirectory.

Is this recommended. I need my app sub directories for all users, instead of 
creating for each user.

Thanks for comments
SA 

"bar" <shaikakbar250281@yahoo.co.in> wrote in message 
news:48085050@newsgroups.borland.com...

> Onething i noticed a "Virtual Store\Program Files\App\" directory
> storing exact backup of directories that have been created in the
> "C:\Program Files\App\" directory.

That is Vista's "File System Virtualization" feature at work:

    http://msdn2.microsoft.com/en-us/library/bb756960.aspx

Refer to the "Virtualization" section.

> My app when runs checks for the directory and create some directories in 
> the "C:\Program Files\App\" if not exist. XP it was working fine.

You should not be creating folders and files under "Program Files" to begin 
with.  Create them in the CSIDL_APPDATA, CSIDL_LOCAL_APPDATA, or 
CSIDL_COMMON_APPDATA folder instead, depending on your needs.  Use 
SHGetSpecialFolderLocation() or similar function to resolve those IDs to 
physical paths.

> In vista if i delete the sub directories under "C:\Program Files\App\" 
> manually. The program is considering the "Virtual Store\Program 
> Files\App\" path as a app folder path and i don't have any control over 
> the
> "C:\Program Files\App\" directory to create sub directories.

Because you are not supposed to be writing anything there to begin with, so 
Vista is making sure you don't.

> But anyhow i changed the app subdirectories path for the below.
> XP -C:\Documents and Settings\All Users\Application Data\App\SubDirectory
> Vista - C:\Program Data\App\SubDirectory.

That is the CSIDL_COMMON_APPDATA folder.

> Is this recommended. I need my app sub directories for all users,
> instead of creating for each user.

Yes, CSIDL_COMMON_APPDATA is appropriate for that purpose.


Gambit 

Thanks Remy.
I really appreciate your suggestions..

Thanks everyone for the comments.

I have to post my problem once again.

I used this code

//Unit1.cpp file

#define NO_WIN32_LEAN_AND_MEAN
#include <shlobj.h>

#include <vcl.h>
#pragma hdrstop

#include "Unit1.h"
...
...

//In a button click event i have.

void __fastcall TForm1::Button1Click(TObject *Sender)
{
    LPITEMIDLIST List = NULL;
    char Path[MAX_PATH + 1] = {0};

    if(SUCCEEDED(SHGetSpecialFolderLocation(0,CSIDL_COMMON_APPDATA, &List)))
    {
        if(SHGetPathFromIDList(List, Path))
             ShowMessage(String(Path));
    }
    else
        ShowMessage("SHGetSpecialFolderLocation failed");

     CoTaskMemFree(List);
}

1 .Compile the code i have the following error messages.
[C++ Error] winsock2.h(109): E2238 Multiple declaration for 'fd_set'
[C++ Error] winsock.h(54): E2344 Earlier declaration of 'fd_set'
[C++ Error] winsock2.h(112): E2146 Need an identifier to declare
[C++ Error] winsock2.h(153): E2238 Multiple declaration for 'timeval'
[C++ Error] winsock.h(97): E2344 Earlier declaration of 'timeval'
[C++ Error] winsock2.h(209): E2238 Multiple declaration for 'hostent'
[C++ Error] winsock.h(153): E2344 Earlier declaration of 'hostent'

bar wrote:
> Thanks everyone for the comments.
> 
> I have to post my problem once again.
> 
> I used this code
> 
> //Unit1.cpp file
> 
> #define NO_WIN32_LEAN_AND_MEAN

This needs to be in the Project Compiler conditionals.

bar wrote:

>//Unit1.cpp file
>
>#define NO_WIN32_LEAN_AND_MEAN
>#include <shlobj.h>
>
>#include <vcl.h>
>#pragma hdrstop
>
>#include "Unit1.h"
>...
>...
>
>    if(SUCCEEDED(SHGetSpecialFolderLocation(0,CSIDL_COMMON_APPDATA, &List)))

>[C++ Error] winsock2.h(109): E2238 Multiple declaration for 'fd_set'
>[C++ Error] winsock.h(54): E2344 Earlier declaration of 'fd_set'

Winsock has nothing to do with SHGet...
and is a seperate problem.

Somewhere in your deleted #includes, you have
winsock.h being included before winsock2.h

Include winsock2.h first, probably before vcl.h.
Or make sure
	_WIN32_WINNT >= 0x0400
(See in windows.h where it includes winsock2.h, and the
conditions that cause it to prefer version 2 over winsock.h)