Hi All,

I'm working on my InnoSetup script to make sure it is Vista-friendly.
I use DBISAM 4.x C/S, server is run as a service
From what I understand, I can put the server files in Program Files,
but can't write to any of these files after initial installation. I'm
assuming the server service can't write to these files either?

So, I should put the server config, lock, database, & temp files in the
CommonAppData folder? Any thoughts? Anybody working with Vista
installations yet?

Maybe we can use this thread to discuss our Vista installation
experiences/questions/woes.

Regards,

Jason Lee

Hi

I too have updated my app(let)s for Vista and also use Inno.
It now seems to work just fine.  The only thing that may still be an
issue for me is creating a share at install time.  Vista *seems* to
have a timeout which turns off network discovery if it is not used for
a while, and that *seems* to block 'net share..'

As you would expect I install all the read-only files to the Program
Files tree and the database and other user writable files to the
commonappdata tree.

I do not use CS so I will only say that I would have expected the
server process to be configurable to write to the {pf} tree but I
suspect the data would be better in the commonappdata tree with
appropriate permissions to stop ordinary users from having direct
access.  But maybe I am way out of line on this?

My tip is:
   'Steer well clear of Virtualization!'.


Malcolm

Jason,

<< So, I should put the server config, lock, database, & temp files in the
CommonAppData folder? Any thoughts? Anybody working with Vista installations
yet? >>

I would point, at the very least, the server config file to the common app
data folder.   That's what we do with the .ini for the ElevateDB Server, and
it works fine.   The rest of the lock files will locate themselves in the
database directories, so as long as you keep the databases out of the
Program Files area, you'll be fine.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:557B204C-8EA8-4A14-B1FA-2310109CDF4D@news.elevatesoft.com...
> The rest of the lock files will locate themselves in the database
> directories, so as long as you keep the databases out of the Program Files
> area, you'll be fine.
>

Ah! my dear Holmes very interesting please elaborate your deduction.
I'am just thinking about avoiding that very place myself in WinXPx64.
My reason for that decision are the 2 Program Files folders. I figured
the "Program Files (x86)" folder may be a no go area for future Delphi
tools. 64 bit is nothing like the 16 bit to 32 bit goldrush and as Vista is
struggling to pull itself together I'am looking outside the box. MS gave
XP a longer cut off date to PC builders over here at least but they all
ship Vista unless you ask. I hear the SP1 for Vista is out but as yet I
havent grabbed it I will wait. Now for the killer question has anyone
got a DBisam server running on Linux 64 yet ?
I ask because my nice new dual booting 64 bit box bought for 5 quid
in a car boot sale is up and running. Loading Windows on a Sata drive
is a pain if you have never done it. I normaly buy my hardware ready built,
or just put a lan card in or more ram or something or even an IDE drive,
but SATA needs drivers during the windows install hit f6 in setup then load
the drivers file via a floppy and a floppy only. So why no EDB files in the
Program Files in Vista Tim ?

Rita

More dribble from Rita on the subject of XP
http://news.yahoo.com:80/s/infoworld/20080115/tc_infoworld/94616_1

Rita,

<< So why no EDB files in the Program Files in Vista Tim ? >>

Due to the "virtualization" in Vista, it won't work properly:

http://support.microsoft.com/kb/927387

--
Tim Young
Elevate Software
www.elevatesoft.com