Re: terminal services compatibility
- From: "swansnow" <schultz@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: 30 Aug 2005 05:56:55 -0700
> What about just specifing no path for the ini-filename.
> This should create the ini file in the current working
> directory.
> Ehm, more precisely .\
> myIniFile:=TIniFile.Create('.\my.ini');
That's what I thought, but then someone I work with suggested that
terminal services didn't quite work like that. He seemd to think that
there was something else going on than simply a logical mapping, but he
was unsure. So I'm here looking for more information (couldn't really
find much using Google). I've asked the powers-that-be if we could get
such a system for testing on, so if I'm lucky, I will be able to do
some experimentation soon.
Do you *know* that I can simply use .\ and it will work on a terminal
services system?
I seem to recall that the user's working space is a separate folder
than any exe they might be running. i.e. the exe is located on
J:\programs, and the user's folder is mapped locally to W:\john (but is
really c:\users\home\john on the server).
-Corinna
.
- Follow-Ups:
- Re: terminal services compatibility
- From: Andreas Koch
- Re: terminal services compatibility
- References:
- terminal services compatibility
- From: swansnow
- Re: terminal services compatibility
- From: pr
- Re: terminal services compatibility
- From: swansnow
- Re: terminal services compatibility
- From: pr
- Re: terminal services compatibility
- From: swansnow
- Re: terminal services compatibility
- From: Andreas Koch
- Re: terminal services compatibility
- From: Andreas Koch
- terminal services compatibility
- Prev by Date: Re: OOP style
- Next by Date: Re: HTTPS using Indy
- Previous by thread: Re: terminal services compatibility
- Next by thread: Re: terminal services compatibility
- Index(es):
Relevant Pages
|