Vista complications

[Frank M. Cook]

We're upgrading from CBuilder3 to CB2007. We're running into some trouble
and we think we may have screwed up when we allowed the program to install
to Program Files on a Vista Business computer. We'd like to start over
again.

Can we just cut and paste the directory to a new location?

If we uninstall, delete files, and reinstall, will we run into license
issues?

Can we install on a second XP computer just to eliminate the possibility it
is Vista messing things up for us or would that be a license issue? We only
have one programmer but in the transition period it would be useful to let
him try both Vista and XP to better understand problems.

[Remy Lebeau (TeamB)]

We're running into some trouble and we think we may have screwed up
when we allowed the program to install to Program Files on a Vista
Business computer.

Why do you think that? That is where applications are supposed to be
installed.

Can we just cut and paste the directory to a new location?

No. There are many Registry entries that reference the folders the IDE
uses.


Gambit

[Frank M. Cook]

Post by Remy Lebeau (TeamB)

We're running into some trouble and we think we may have screwed up
when we allowed the program to install to Program Files on a Vista
Business computer.

Why do you think that? That is where applications are supposed to be
installed.

That's what I used to think too before Vista but with our own application
we've had to start having Vista users install elsewhere because Vista is
really serious about treating everything in Program Files as Read Only and
virtualizing the files there. However, if you say that CBuilder and Delphi
will work fine installed in Program Files on Vista because everything that
needs to be written to is created under My Documents, then I'll believe you
and look elsewhere for the solution to our problems.

We're trying to get the old Orpheus components to compile and it's
frustrating us. Being in Program Files felt like part of the problem, but
maybe it's just a matter of editing the Orpheus stuff to get correct all the
references to reflect Vista appropriate locations.

[Edwin Lau]

Post by Frank M. Cook
We're upgrading from CBuilder3 to CB2007. We're running into some trouble
and we think we may have screwed up when we allowed the program to install
to Program Files on a Vista Business computer. We'd like to start over
again.
Can we just cut and paste the directory to a new location?
If we uninstall, delete files, and reinstall, will we run into license
issues?
Can we install on a second XP computer just to eliminate the possibility it
is Vista messing things up for us or would that be a license issue? We only
have one programmer but in the transition period it would be useful to let
him try both Vista and XP to better understand problems.

I do not have a Vista Business computer but from what I understand, the
issue that you might be facing could be due to the fact that in Vista
Business, Data Execution Prevention (DEP) is turned on for all
application. That does seems to give some problem for some application.
I am however not sure if it is the same issue for CB2007. Perhaps you
can turn that off and restart your computer and see if that resolve your
problem.

Incidentally, what problem are you actually facing ?

[Frank M. Cook]

<Incidentally, what problem are you actually facing ?>

we were struggling to get the Orpheus components to work and needed to be
sure it wasn't Vista. it wasn't. we started over rewriting the source to
correct all references to CBuilder projects to the latest names and equally
importantly getting everything located in and referenced to the proper
directories.

[Lance Rasmussen]

Orpheus works fine on Vista (using D2006 and D2007 at least), at least as
far as the tables go. Our apps use it and while we've made some minor
modifications, their not in relation to pathing / OS issues.

Do note that Vista IS really serious about Program Files being read only.
The best approach, which while a pain, can help out with other compatibility
and future compatibility issues, is to use the given pathing contants for
where the application and where data goes and to only write data / INI's,
etc into a Read/Write directory. If you're doing this on a user by user
basis, its a little easier. If you're doing this as machine specific, then
you have to use some different pathings.

As much grief as its caused us to deal with Vista, it has cleaned up a few
things with working with the server products and our programs had no issues
with Server 2008 because of it too.

Lance

Post by Frank M. Cook
<Incidentally, what problem are you actually facing ?>
we were struggling to get the Orpheus components to work and needed to be
sure it wasn't Vista. it wasn't. we started over rewriting the source to
correct all references to CBuilder projects to the latest names and
equally importantly getting everything located in and referenced to the
proper directories.
--
Frank M. Cook
www.acsplus.com

[Frank M. Cook]

Post by Lance Rasmussen
Do note that Vista IS really serious about Program Files being read only.
The best approach, which while a pain, can help out with other
compatibility and future compatibility issues, is to use the given pathing
contants

understood. we've opted so far not to use Microsoft's plan though. we've
changed our default data location to be a data directory under an our
company directory created under the root rather than under program files
(our old location). we haven't gone with the hidden application data
location because it's very hard for us to do telephone support that way and
it is also hard for the user to backup.

we moved most of our ini files to a subdirectory under our data. we have a
lot of ini files that store customer specific settings that wouldn't change
from user to user within the company. we do have a few that are truly user
sensitive and once we get ported to 2007 we may move them to reflect the
pathing constants. this all ties in with Orpheus as we use the Orpheus
State Controls to create and retrieve the information from the ini files.