AW: AW: still problems with Vista virtualizing my db

[Tiemo Hollmann TB]

Hi Thorsten,
btw. I'm a man, so TiemO :)

uff, you are right - I don't liked to hear your ideas :(

My setup is made with innosetup - which works fine with Vista. But my
updates are online updates of single files by my own app. So this is
obviously where I am passing the wants and needs of Vista, and I am really
not that system technician to dig into all these Vista needs to create a
Vista compatible updater. Grrr.

But what Doug posted with CACLS, sounds very interesting, perhaps I should
give it a try...

Thanks for showing me a hint
Tiemo


> -----Ursprüngliche Nachricht-----
> Von: valentina-bounces at lists.macserve.net [mailto:valentina-
> bounces at lists.macserve.net] Im Auftrag von Thorsten Hohage
> Gesendet: Montag, 2. März 2009 08:35
> An: Valentina Developers
> Betreff: Re: AW: still problems with Vista virtualizing my db
> 
> Hi Tiema,
> 
> On 2009-03-02, at 07:43, Tiemo Hollmann TB wrote:
> 
> > any idea yet?
> Yes - several ideas but perhaps you don't like to hear them to much ...
> 
> So first of all here is a link to a tech note from Omnis (NO it is not
> related wether with Valentina, nor with Rev - but good explanation and
> a start point).
> 
> 	<http://www.omnis.net/technotes/index.html?detail=tnwi0001>
> 
> 
> > Obviously either the rev engine or the valentina engine makes
> > something, what provokes Vista to virtualize the db. But only after
> > an update???
> Changes in program files needed to be reflected in all this registry /
> rights staff - so after every update you need to set everything again
> for the "new" version.
> 
> So as far as I get M$ docs and more, at least you must have a real
> (Vista) installer for your specific app for every little byte you want
> to change. Do you use something like VISE right now or do you simple
> copy the files over?
> 
> 
> 
> Here is another quote (thanks to Doug :-) - again from Omnis List (due
> to several reasons Omnis Studio was an IDE needed to battle with all
> the Vista hassle really early - because it was able to run on Vista at
> all w/o any changes, e.g. in contrast to REALbasic - don't know about
> Rev ...)
> 
> > I guess we are different - we install to the program files folder in
> > Vista.
> >
> > I use installer vise and just put things where they are supposed to
> > go, regardless of the UAC.   Studio 4.3.1 handles the after install
> > stuff with the UAC properly because of one of the files that runs
> > called 'studiorg'.   as far as I know it is the thing that handles the
> > finicky stuff with Vista when you start up your application.
> >
> > the other thing I do it to make sure that we have full read/write
> > access to our application directory after the install.   So we have a
> > little bat file we include in the application directory that we then
> > run.
> >
> > all it effectively has in it is the following DOS command which gives
> > full access by studio to any file in the studio directory.   Since it
> > is run by installer vise as part of the install, it runs just fine and
> > the user sees none of the dos stuff.
> >
> > the command is.
> >
> > CACLS "C:\Program Files\Theatre Manager" /T /C /e /g EVERYONE:f
> >
> >
> > replace 'Theatre Manager' with the name of your directory/application.
> 
> 
> So for me the most important part, except PROPER installation is the
> usage of this nice statement.
> 
> 
> regards,
> 
> Thorsten Hohage
> --
> 
> Valentina Technology Evangelist
> generic objects  GmbH - Leiter Solution Center Nord
> 
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina