WorkDir and Vista

Alessandro,

If I remember well, all important dir (OS managed) have an "ACCESS"
So I think for Programmi, and P.Piko published some of them when I was
searching for the "Burning Area" (temporay folder used by Windows CD burn
wizard...)
Have you looked at the API help?

ciao

Massimo




"Alessandro Antonangeli" <alcati@alcati.RemoveThis.com> ha scritto nel
messaggio news:g9lg61$ep4$1@aioe.org...
>> The problem is in not creating the file.
> Yes (even if i do not understand what is the advantage of calling the same
> directory in 2 different way)
>> What kind of user runs the app ? Admin of regular ?
> I didn't check (and I cannot do for the moment), but I thing it was Admin,
> because he is the only one user.
> --
> Ciao
> Alessandro
>

Massimo,

Do you think this is the funtion you mentioned ?

John

FUNC GetShellFolder(nFolder AS INT, fCreate AS LOGIC) AS STRING PASCAL
* GetShellFolder(CSIDL_PERSONAL, FALSE) persoonlijke documenten
* GetShellFolder(CSIDL_PROGRAM_FILES, FALSE) program files
LOCAL DIM sz[MAX_PATH+4] AS BYTE
LOCAL c AS STRING
IF SHGetSpecialFolderPath(HWND_DESKTOP, @sz, nFolder, fCreate)
c := Psz2String(@sz)
ENDIF
RETURN c


Massimo Bighelli schreef:
>
> Alessandro,
>
> If I remember well, all important dir (OS managed) have an "ACCESS"
> So I think for Programmi, and P.Piko published some of them when I was
> searching for the "Burning Area" (temporay folder used by Windows CD
> burn wizard...)
> Have you looked at the API help?
>
> ciao
>
> Massimo
>
>
>
>
> "Alessandro Antonangeli" <alcati@alcati.RemoveThis.com> ha scritto nel
> messaggio news:g9lg61$ep4$1@aioe.org...
>>> The problem is in not creating the file.
>> Yes (even if i do not understand what is the advantage of calling the
>> same directory in 2 different way)
>>> What kind of user runs the app ? Admin of regular ?
>> I didn't check (and I cannot do for the moment), but I thing it was
>> Admin, because he is the only one user.
>> --
>> Ciao
>> Alessandro
>>
>

Yes, John

something similar... and the CSIDL list was long, almost all the relevant
system dir

Massimo



"John Martens" <adsl672100@tiscali.nl> ha scritto nel messaggio
news:48bed842$0$24409$5fc3050@news.tiscali.nl...
> Massimo,
>
> Do you think this is the funtion you mentioned ?
>
> John
>
> FUNC GetShellFolder(nFolder AS INT, fCreate AS LOGIC) AS STRING PASCAL
> * GetShellFolder(CSIDL_PERSONAL, FALSE) persoonlijke documenten
> * GetShellFolder(CSIDL_PROGRAM_FILES, FALSE) program files
> LOCAL DIM sz[MAX_PATH+4] AS BYTE
> LOCAL c AS STRING
> IF SHGetSpecialFolderPath(HWND_DESKTOP, @sz, nFolder, fCreate)
> c := Psz2String(@sz)
> ENDIF
> RETURN c
>
>
> Massimo Bighelli schreef:
>>
>> Alessandro,
>>
>> If I remember well, all important dir (OS managed) have an "ACCESS"
>> So I think for Programmi, and P.Piko published some of them when I was
>> searching for the "Burning Area" (temporay folder used by Windows CD burn
>> wizard...)
>> Have you looked at the API help?
>>
>> ciao
>>
>> Massimo
>>
>>
>>
>>
>> "Alessandro Antonangeli" <alcati@alcati.RemoveThis.com> ha scritto nel
>> messaggio news:g9lg61$ep4$1@aioe.org...
>>>> The problem is in not creating the file.
>>> Yes (even if i do not understand what is the advantage of calling the
>>> same directory in 2 different way)
>>>> What kind of user runs the app ? Admin of regular ?
>>> I didn't check (and I cannot do for the moment), but I thing it was
>>> Admin, because he is the only one user.
>>> --
>>> Ciao
>>> Alessandro
>>>
>>

Do you still have the code with the longer list ?


Massimo Bighelli schreef:
> Yes, John
>
> something similar... and the CSIDL list was long, almost all the
> relevant system dir
>
> Massimo
>
>
>
> "John Martens" <adsl672100@tiscali.nl> ha scritto nel messaggio
> news:48bed842$0$24409$5fc3050@news.tiscali.nl...
>> Massimo,
>>
>> Do you think this is the funtion you mentioned ?
>>
>> John
>>
>> FUNC GetShellFolder(nFolder AS INT, fCreate AS LOGIC) AS STRING PASCAL
>> * GetShellFolder(CSIDL_PERSONAL, FALSE) persoonlijke documenten
>> * GetShellFolder(CSIDL_PROGRAM_FILES, FALSE) program files
>> LOCAL DIM sz[MAX_PATH+4] AS BYTE
>> LOCAL c AS STRING
>> IF SHGetSpecialFolderPath(HWND_DESKTOP, @sz, nFolder, fCreate)
>> c := Psz2String(@sz)
>> ENDIF
>> RETURN c
>>
>>
>> Massimo Bighelli schreef:
>>>
>>> Alessandro,
>>>
>>> If I remember well, all important dir (OS managed) have an "ACCESS"
>>> So I think for Programmi, and P.Piko published some of them when I
>>> was searching for the "Burning Area" (temporay folder used by Windows
>>> CD burn wizard...)
>>> Have you looked at the API help?
>>>
>>> ciao
>>>
>>> Massimo
>>>
>>>
>>>
>>>
>>> "Alessandro Antonangeli" <alcati@alcati.RemoveThis.com> ha scritto
>>> nel messaggio news:g9lg61$ep4$1@aioe.org...
>>>>> The problem is in not creating the file.
>>>> Yes (even if i do not understand what is the advantage of calling
>>>> the same directory in 2 different way)
>>>>> What kind of user runs the app ? Admin of regular ?
>>>> I didn't check (and I cannot do for the moment), but I thing it was
>>>> Admin, because he is the only one user.
>>>> --
>>>> Ciao
>>>> Alessandro
>>>>
>>>
>

John,

"John Martens" <adsl672100@tiscali.nl> ha scritto nel messaggio
news:48bedbc7$0$24397$5fc3050@news.tiscali.nl...
> Do you still have the code with the longer list ?


found the original message (THX Paul)

-----------------

Da:Paul Piko
Oggetto:Re: CD burning with XP
View: Complete Thread (21 articoli)
Original Format
Newsgroups:comp.lang.clipper.visual-objects
Data:2004-10-24 22:23:04 PST


Sigfried,

> thanks, I tried it with the hex value, that works very well, is there a
> library or include file with this definitions (CSIDL_CDBURN_AREA)? Would
> be nicer as to code this values in the app.

Most of the CSIDL values are already defined in the Win API library. The few
missing ones I have found are:

DEFINE CSIDL_CDBURN_AREA := 0x003b
DEFINE CSIDL_COMMON_MUSIC := 0x0035
DEFINE CSIDL_COMMON_PICTURES := 0x0036
DEFINE CSIDL_COMMON_TEMPLATES := 0x002d
DEFINE CSIDL_COMMON_VIDEO := 0x0037
DEFINE CSIDL_MYDOCUMENTS := 0x000c // virtual, not physical
DEFINE CSIDL_MYVIDEO := 0x000e
DEFINE CSIDL_PROFILE := 0x0028
DEFINE CSIDL_PROFILES := 0x003e

The MS descriptions of the CSIDL values are included below.

--
Paul
----
Paul Piko
Piko Computing Consultants


Explanation of CSIDL values from MS:

--------------------------------------------------------------------------------

CSIDL values provide a unique system-independent way to identify special
folders used frequently by applications, but which may not have the same
name or location on any given system. For example, the system folder may be
"C:\Windows" on one system and "C:\Winnt" on another.

Constants

CSIDL_FLAG_CREATE (0x8000)
Version 5.0. Combine this CSIDL with any of the following CSIDLs to force
the creation of the associated folder.

CSIDL_ADMINTOOLS (0x0030)
Version 5.0. The file system directory that is used to store administrative
tools for an individual user. The Microsoft Management Console (MMC) will
save customized consoles to this directory, and it will roam with the user.

CSIDL_ALTSTARTUP (0x001d)
The file system directory that corresponds to the user's nonlocalized
Startup program group.

CSIDL_APPDATA (0x001a)
Version 4.71. The file system directory that serves as a common repository
for application-specific data. A typical path is C:\Documents and
Settings\username\Application Data. This CSIDL is supported by the
redistributable Shfolder.dll for systems that do not have the Microsoft®
Internet Explorer 4.0 integrated Shell installed.

CSIDL_BITBUCKET (0x000a)
The virtual folder containing the objects in the user's Recycle Bin.

CSIDL_CDBURN_AREA (0x003b)
Version 6.0. The file system directory acting as a staging area for files
waiting to be written to CD. A typical path is C:\Documents and
Settings\username\Local Settings\Application Data\Microsoft\CD Burning.

CSIDL_COMMON_ADMINTOOLS (0x002f)
Version 5.0. The file system directory containing administrative tools for
all users of the computer.

CSIDL_COMMON_ALTSTARTUP (0x001e)
The file system directory that corresponds to the nonlocalized Startup
program group for all users. Valid only for Microsoft Windows NT® systems.

CSIDL_COMMON_APPDATA (0x0023)
Version 5.0. The file system directory containing application data for all
users. A typical path is C:\Documents and Settings\All Users\Application
Data.

CSIDL_COMMON_DESKTOPDIRECTORY (0x0019)
The file system directory that contains files and folders that appear on the
desktop for all users. A typical path is C:\Documents and Settings\All
Users\Desktop. Valid only for Windows NT systems.

CSIDL_COMMON_DOCUMENTS (0x002e)
The file system directory that contains documents that are common to all
users. A typical paths is C:\Documents and Settings\All Users\Documents.
Valid for Windows NT systems and Microsoft Windows® 95 and Windows 98
systems with Shfolder.dll installed.

CSIDL_COMMON_FAVORITES (0x001f)
The file system directory that serves as a common repository for favorite
items common to all users. Valid only for Windows NT systems.

CSIDL_COMMON_MUSIC (0x0035)
Version 6.0. The file system directory that serves as a repository for music
files common to all users. A typical path is C:\Documents and Settings\All
Users\Documents\My Music.

CSIDL_COMMON_PICTURES (0x0036)
Version 6.0. The file system directory that serves as a repository for image
files common to all users. A typical path is C:\Documents and Settings\All
Users\Documents\My Pictures.

CSIDL_COMMON_PROGRAMS (0x0017)
The file system directory that contains the directories for the common
program groups that appear on the Start menu for all users. A typical path
is C:\Documents and Settings\All Users\Start Menu\Programs. Valid only for
Windows NT systems.

CSIDL_COMMON_STARTMENU (0x0016)
The file system directory that contains the programs and folders that appear
on the Start menu for all users. A typical path is C:\Documents and
Settings\All Users\Start Menu. Valid only for Windows NT systems.

CSIDL_COMMON_STARTUP (0x0018)
The file system directory that contains the programs that appear in the
Startup folder for all users. A typical path is C:\Documents and
Settings\All Users\Start Menu\Programs\Startup. Valid only for Windows NT
systems.

CSIDL_COMMON_TEMPLATES (0x002d)
The file system directory that contains the templates that are available to
all users. A typical path is C:\Documents and Settings\All Users\Templates.
Valid only for Windows NT systems.

CSIDL_COMMON_VIDEO (0x0037)
Version 6.0. The file system directory that serves as a repository for video
files common to all users. A typical path is C:\Documents and Settings\All
Users\Documents\My Videos.

CSIDL_CONTROLS (0x0003)
The virtual folder containing icons for the Control Panel applications.

CSIDL_COOKIES (0x0021)
The file system directory that serves as a common repository for Internet
cookies. A typical path is C:\Documents and Settings\username\Cookies.

CSIDL_DESKTOP (0x0000)
The virtual folder representing the Windows desktop, the root of the
namespace.

CSIDL_DESKTOPDIRECTORY (0x0010)
The file system directory used to physically store file objects on the
desktop (not to be confused with the desktop folder itself). A typical path
is C:\Documents and Settings\username\Desktop.

CSIDL_DRIVES (0x0011)
The virtual folder representing My Computer, containing everything on the
local computer: storage devices, printers, and Control Panel. The folder may
also contain mapped network drives.

CSIDL_FAVORITES (0x0006)
The file system directory that serves as a common repository for the user's
favorite items. A typical path is C:\Documents and
Settings\username\Favorites.

CSIDL_FONTS (0x0014)
A virtual folder containing fonts. A typical path is C:\Windows\Fonts.

CSIDL_HISTORY (0x0022)
The file system directory that serves as a common repository for Internet
history items.

CSIDL_INTERNET (0x0001)
A virtual folder representing the Internet.

CSIDL_INTERNET_CACHE (0x0020)
Version 4.72. The file system directory that serves as a common repository
for temporary Internet files. A typical path is C:\Documents and
Settings\username\Local Settings\Temporary Internet Files.

CSIDL_LOCAL_APPDATA (0x001c)
Version 5.0. The file system directory that serves as a data repository for
local (nonroaming) applications. A typical path is C:\Documents and
Settings\username\Local Settings\Application Data.

CSIDL_MYDOCUMENTS (0x000c)
Version 6.0. The virtual folder representing the My Documents desktop item.
This should not be confused with CSIDL_PERSONAL, which represents the file
system folder that physically stores the documents.

CSIDL_MYMUSIC (0x000d)
The file system directory that serves as a common repository for music
files. A typical path is C:\Documents and Settings\User\My Documents\My
Music.

CSIDL_MYPICTURES (0x0027)
Version 5.0. The file system directory that serves as a common repository
for image files. A typical path is C:\Documents and Settings\username\My
Documents\My Pictures.

CSIDL_MYVIDEO (0x000e)
Version 6.0. The file system directory that serves as a common repository
for video files. A typical path is C:\Documents and Settings\username\My
Documents\My Videos.

CSIDL_NETHOOD (0x0013)
A file system directory containing the link objects that may exist in the My
Network Places virtual folder. It is not the same as CSIDL_NETWORK, which
represents the network namespace root. A typical path is C:\Documents and
Settings\username\NetHood.

CSIDL_NETWORK (0x0012)
A virtual folder representing Network Neighborhood, the root of the network
namespace hierarchy.

CSIDL_PERSONAL (0x0005)
The file system directory used to physically store a user's common
repository of documents. A typical path is C:\Documents and
Settings\username\My Documents. This should be distinguished from the
virtual My Documents folder in the namespace, identified by
CSIDL_MYDOCUMENTS. To access that virtual folder, use SHGetFolderLocation,
which returns the ITEMIDLIST for the virtual location, or refer to the
technique described in Managing the File System.

CSIDL_PRINTERS (0x0004)
The virtual folder containing installed printers.

CSIDL_PRINTHOOD (0x001b)
The file system directory that contains the link objects that can exist in
the Printers virtual folder. A typical path is C:\Documents and
Settings\username\PrintHood.

CSIDL_PROFILE (0x0028)
Version 5.0. The user's profile folder. A typical path is C:\Documents and
Settings\username. Applications should not create files or folders at this
level; they should put their data under the locations referred to by
CSIDL_APPDATA or CSIDL_LOCAL_APPDATA.

CSIDL_PROFILES (0x003e)
Version 6.0. The file system directory containing user profile folders. A
typical path is C:\Documents and Settings.

CSIDL_PROGRAM_FILES (0x0026)
Version 5.0. The Program Files folder. A typical path is C:\Program Files.

CSIDL_PROGRAM_FILES_COMMON (0x002b)
Version 5.0. A folder for components that are shared across applications. A
typical path is C:\Program Files\Common. Valid only for Windows NT, Windows
2000, and Windows XP systems. Not valid for Windows Millennium Edition
(Windows Me).

CSIDL_PROGRAMS (0x0002)
The file system directory that contains the user's program groups (which are
themselves file system directories). A typical path is C:\Documents and
Settings\username\Start Menu\Programs.

CSIDL_RECENT (0x0008)
The file system directory that contains shortcuts to the user's most
recently used documents. A typical path is C:\Documents and
Settings\username\My Recent Documents. To create a shortcut in this folder,
use SHAddToRecentDocs. In addition to creating the shortcut, this function
updates the Shell's list of recent documents and adds the shortcut to the My
Recent Documents submenu of the Start menu.

CSIDL_SENDTO (0x0009)
The file system directory that contains Send To menu items. A typical path
is C:\Documents and Settings\username\SendTo.

CSIDL_STARTMENU (0x000b)
The file system directory containing Start menu items. A typical path is
C:\Documents and Settings\username\Start Menu.

CSIDL_STARTUP (0x0007)
The file system directory that corresponds to the user's Startup program
group. The system starts these programs whenever any user logs onto Windows
NT or starts Windows 95. A typical path is C:\Documents and
Settings\username\Start Menu\Programs\Startup.

CSIDL_SYSTEM (0x0025)
Version 5.0. The Windows System folder. A typical path is
C:\Windows\System32.

CSIDL_TEMPLATES (0x0015)
The file system directory that serves as a common repository for document
templates. A typical path is C:\Documents and Settings\username\Templates.

CSIDL_WINDOWS (0x0024)
Version 5.0. The Windows directory or SYSROOT. This corresponds to the
%windir% or %SYSTEMROOT% environment variables. A typical path is
C:\Windows.

The problem is that I do not know where the program has been installed (Inno
setup)
So if it is installed in "Program files" i get the mess, becuase i do not
know where it really is
If it is installed (as, at the end, i did) in C:\MyFirmName\MyProgramDir all
works fine and i get the true path
--
Ciao
Alessandro

"Massimo Bighelli" <info@arcasistemi.it> ha scritto nel messaggio
news:48bed4bb$0$1081$4fafbaef@reader1.news.tin.it. ..
>
> Alessandro,
>
> If I remember well, all important dir (OS managed) have an "ACCESS"
> So I think for Programmi, and P.Piko published some of them when I was
> searching for the "Burning Area" (temporay folder used by Windows CD burn
> wizard...)
> Have you looked at the API help?
>
> ciao
>
> Massimo
>
>
>
>
> "Alessandro Antonangeli" <alcati@alcati.RemoveThis.com> ha scritto nel
> messaggio news:g9lg61$ep4$1@aioe.org...
>>> The problem is in not creating the file.
>> Yes (even if i do not understand what is the advantage of calling the
>> same directory in 2 different way)
>>> What kind of user runs the app ? Admin of regular ?
>> I didn't check (and I cannot do for the moment), but I thing it was
>> Admin, because he is the only one user.
>> --
>> Ciao
>> Alessandro
>>
>

In my pc running XP all programs are normally in C:\Programmi which is the
italian dir of "C:\Program files"
And they really are there. When I setup a program, it recognise the Italian
name of the folder.

It would have been nice if on all the PC, without regarding of the language,
all the program were in "C:\Program files".
So every one know where to find installed programs.
Then the alias could be usefull for other languages: so if i do
cd Programmi
I am in C:\Programmi, but i see in reality the content of "C:\Program
files"
And if I do
cd "C:\Program files"
I am in "C:\Program files" and see the same content
And if I create a file in C:\Programmi is the same as if I create on
"C:\Program files"

The problem is that WorkDir() give a path and I cannot use it for creating a
file because is not valid/recognized by the system.

In Unix (Linux) this aliases exist from 20 years: may be MS will be able to
make something similar (and working) in the next SO version ...
--
Ciao
Alessandro

"John Martens" <adsl672100@tiscali.nl> ha scritto nel messaggio
news:48beb6e1$0$24402$5fc3050@news.tiscali.nl...
> Alessandro,
>
> The advantage is that in dutch a folder name Afbeeldingen is better
> understood by the majority of Windows users than a foldername Picture.
>
> In order to have windows and it's apps working in the same way MS cannot
> vary the 'real' names of folders but they can alias the folders in own MS
> apps.
>
> John
>

Hi Alessandro,
On Thu, 4 Sep 2008, at 00:44:10 [GMT +0200] (which was 0:44 where I live)
you wrote about: 'WorkDir and Vista'

> The problem is that I do not know where the program has been installed (Inno
> setup)
> So if it is installed in "Program files" i get the mess, becuase i do not
> know where it really is
> If it is installed (as, at the end, i did) in C:\MyFirmName\MyProgramDir all
> works fine and i get the true path

Inno setup records the installation directory in the registry.
Look for

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall\<yourproduct>_Is1

Entry "Inno Setup: App Path"



--
Robert van der Hulst
AKA Mr. Data
Vo2Jet & Vo2Ado Support
VO & Vulcan.NET Development Team
www.heliks.nl

Hi Robert
Thanks for the information
But I do not have a Vista machine, so I cannot test if the registry key
contain the right path or the wrong.
I think the "wrong", because during the installation i noticed the English
path and if i use the English path i cannot create the file
--
Ciao
Alessandro

"Robert van der Hulst" <E-55525A53-3176-E@heliks.nl> ha scritto nel
messaggio news:548109347.20080904090537@heliks.nl...
> Hi Alessandro,
> On Thu, 4 Sep 2008, at 00:44:10 [GMT +0200] (which was 0:44 where I live)
> you wrote about: 'WorkDir and Vista'
>
>> The problem is that I do not know where the program has been installed
>> (Inno
>> setup)
>> So if it is installed in "Program files" i get the mess, becuase i do not
>> know where it really is
>> If it is installed (as, at the end, i did) in C:\MyFirmName\MyProgramDir
>> all
>> works fine and i get the true path
>
> Inno setup records the installation directory in the registry.
> Look for
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall\<yourproduct>_Is1
>
> Entry "Inno Setup: App Path"
>
>
>
> --
> Robert van der Hulst
> AKA Mr. Data
> Vo2Jet & Vo2Ado Support
> VO & Vulcan.NET Development Team
> www.heliks.nl
>

Alessandro,

Mostly you should avoid language specific variants to things like the
working folder and go back to using CSIDL defines with the API calls. We
have Vista and XP clients and things like the All Users data are is
definitely different. Even the default install location is different.
However by using the APIs we get a consistent and installation specific
outcome the application can rely on.

Erik Visser put together a nice little function list using the API to
gather this information and I think it would be more appropriate than
relying on things like WorkDir(). You can't guarantee what VO does under
the covers.

Geoff



"Alessandro m. Antonangeli" <alcati@alcati.RemoveThis.com> wrote in
message news:g9hdeo$2nh$1@aioe.org:

> Hi all
> Just to know
> Installing a program with a localized version of Vista (Italian here), Vista
> say that the destination directory is "Program files" instead of the
> localized name ("Programmi" in Italian).
> Also WorkDir() give the English name.
> So the installed software will be:
>
> "C:\Programmi\YourSoftwareName"
>
> but WorkDir() will report
>
> "C:\Program files\YourSoftwareName"
>
>
> --
> Ciao
> Alessandro