Clarion 6 Vista Installation Fix Version 1.10

[NewsArchive]

All,

I have uploaded a new version 1.10 of the "Clarion 6 Vista Installation Fix"
application.

As you probably know, the Windows Vista operating system provides a new
security feature named User Account Control (UAC). A Vista-aware installer
is required in order to correctly install your applications on Vista. The
same is true for Windows Server 2008 ("Longhorn").

Even if your Clarion 3rd party vendor provides a Vista-aware installer, it's
not possible to correctly auto-detect the installed Clarion version. The
original Clarion 6 installer is unable to write to the WIN.INI file and to
update the system path environment variable on Windows Vista and Windows
"Longhorn". These actions require a Vista-aware installer with
administrator execution level privileges.

We have developed a tiny "Clarion 6 Vista Installation Fix" installer
application compiled with SetupBuilder 6.5. This freeware application makes
the appropriate WIN.INI modifications so 3rd party installations can detect
Clarion 6 on Vista and Windows Server 2008 machines. It also adds the
Clarion \Bin path to the system path environment variable.

You can download the code-signed installer application from this URL:
http://lindersoft.com/c6_vista_fix.exe

This is a freeware application and you can redistribute it to your
customers.

You can use the fix on Windows Vista and Windows Server 2008 ("Longhorn").
Because Clarion 6 cannot be run on 64-bit versions of Windows, the
application detects x64 now and displays a warning.

Just follow the wizard to apply the fix and all 3rd party installers should
be able to auto-detect your Clarion 6 environment on Vista and Windows
Server 2008.

To uninstall the "Clarion 6 Vista Installation Fix", just start
"c6_vista_fix.exe" again or use the "Uninst_Clarion 6 Installation Fix for
Vista.exe" uninstaller application located in your Clarion 6 folder.

Hope this helps.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.5
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Thanks!

Edvard Korsbæk
BB-Soft A/S

[NewsArchive]

> We have developed a tiny "Clarion 6 Vista Installation Fix" installer
> application compiled with SetupBuilder 6.5.

Thanks for the reminder and the utility! I finally began the upgrade to
Vista yesterday (I expect it'll take weeks to get everything sorted out
and installed as I like) so your timing is perfect.

--

Dave

Clarion Magazine: http://www.clarionmag.com
In-depth Clarion articles, news, tips & tricks, printed books and e-books

Source Code Library: http://www.clarionmag.com/cmag/sourcelib.html

Clarion blog: http://www.clarionmag.com/blog/
Personal blog: http://www.knobblegrud.com/

[NewsArchive]

> Thanks for the reminder and the utility! I finally began the upgrade to
> Vista yesterday (I expect it'll take weeks to get everything sorted out
> and installed as I like) so your timing is perfect.

Cool :)

Friedrich

[NewsArchive]

Hi Friedrich,

>You can download the code-signed installer application from this URL:
>http://lindersoft.com/c6_vista_fix.exe
>
>This is a freeware application and you can redistribute it to your
>customers.

I've done some more experimentation on Vista with older versions of
Clarion. It appears that none of the installers update the Path
properly, so I will do that in my installs automatically. OTOH, it
appears that the older installs update the win.ini correctly if you
are logged in as administrator. I think I'll leave the win.ini alone
since it appears that the older installers update it properly. I
tested this with the original Clarion 5.5 installer, which was made
with Wise. I _think_ later 5.5 were built with SB 4, so I'm presuming
that they also update the win.ini correctly?

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

Are you sure it updated the real WIN.INI or do you see the "correct" values
in a virtualized WIN.INI?

I don't think any Vista-unaware installer (SB4, SB5, all Wise Std/Pro
versions, etc.) can correctly write to the WIN.INI (or update the PATH
environment variable). Otherwise, the new Vista security feature would be
absolutely worthless <g>.

Friedrich

[NewsArchive]

Hi Friedrich,

>Are you sure it updated the real WIN.INI or do you see the "correct" values
>in a virtualized WIN.INI?

Well, I'm logged in as admin. I run Total Commander and go to the
Windows folder and view Win.Ini:

[Clarion 6.0 Enterprise Edition]
bin=BIN\
root=C:\Clarion\Clarion6\
exename=C60EE
workdir=C:\Clarion\Clarion6\BIN\
[Clarion 5.5 Enterprise Edition]
bin=BIN\
root=C:\Clarion\C55\
exename=C55EE
workdir=C:\Clarion\C55\BIN\

The first section comes from your C6Fix and the C55 comes from the 5.5
install. The C6 section was NOT there after I ran the C6 install, it
did not come in until after I ran your C6 fix. So I _presume_ that
this is the correct win.ini - i.e. it is the one that was updated with
your C6 fix.

The win.ini in the virtualstore only contains the C6 section from the
original C6 install. It does NOT contain the C5.5 section.

So based on that I'm pretty certain that this is the actual win.ini
file and the installer absolutely did update it;)

The C5.5 install did NOT update the path.

>I don't think any Vista-unaware installer (SB4, SB5, all Wise Std/Pro
>versions, etc.) can correctly write to the WIN.INI (or update the PATH
>environment variable). Otherwise, the new Vista security feature would be
>absolutely worthless <g>.

Well...<bg>

Note that I am logged in as admin and I have not tried this with my
"regular user" account to see what happens there.

Best regards,

Arn&#243;r Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Friedrich,

BTW: This is Windows Vista Home Premium, set up to use UAC etc. I'm
logged in as admin but haven't set up any special anything on this
machine. I.e. it is pretty much strigh out of the store, I haven't
even changed the wallpaper;)

Best regards,

Arn&#243;r Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Friedrich,

If Vista requested elevation when the installer was run, it would be able to
write (non-virtualized) within Program Files.

Why would Vista request elevation without an appropriate manifest?

As I demonstrated in one of my Clarionmag articles, there's a
not-very-bright algorithm that looks as the file name.

For example, make a folder on an Vista machine. Copy Notepad.exe from an XP
machine into that folder. (Use notepad from XP, so it won't have a
Vista-aware manifest.)
Run notepad. It's notepad. Duh.
Now rename the copied notepad to InstallMyProg.exe or MySetup.exe
Run it again.
Whoopeee... elevation... based on having "install" or "setup" in the .exe
file name.

And you thought Microsoft was just another pretty face....

Jane

[NewsArchive]

Hi Arnór,

Aha, I see. I have Vista Ultimate and "Detect application installations and
prompt for elevation" is disabled. So the Vista-unaware installers never
run elevated here. So the Vista edition makes a difference ;-)

Friedrich

[NewsArchive]

> So the Vista edition makes a difference ;-)

What a surprise.

Ram&#243;n Reed

[NewsArchive]

>
> What a surprise.
>

<G>

Friedrich

[NewsArchive]

Hi Friedrich,

>Aha, I see. I have Vista Ultimate and "Detect application installations and
>prompt for elevation" is disabled. So the Vista-unaware installers never
>run elevated here. So the Vista edition makes a difference ;-)

Where is that set? I've made almost no changes to the setup from the
initial install so I would presume this is basically what users would
get. Are you saying that higher level Vista gives you less access
level?

All the installers I've run on this machine, vista aware or not,
require admin and prompt me for admin login even if I'm logged in a
Regular User with no admin rights.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>Aha, I see. I have Vista Ultimate and "Detect application installations
>>and prompt for elevation" is disabled. So the Vista-unaware installers
>>never run elevated here. So the Vista edition makes a difference ;-)
>
> Where is that set? I've made almost no changes to the setup from the
> initial install so I would presume this is basically what users would
> get. Are you saying that higher level Vista gives you less access
> level?
>
> All the installers I've run on this machine, vista aware or not,
> require admin and prompt me for admin login even if I'm logged in a
> Regular User with no admin rights.

It's a new group policy (see Group Policy Object Editor). If you enable
this policy, application installation packages that require elevation of
privileges will be detected through a heuristic algorithm, and the
configured elevation prompt will be triggered.

Friedrich

[NewsArchive]

Hi Friedrich,

>It's a new group policy (see Group Policy Object Editor). If you enable
>this policy, application installation packages that require elevation of
>privileges will be detected through a heuristic algorithm, and the
>configured elevation prompt will be triggered.

Where is this accessed?

Best regards,

Arn&#243;r Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

As mentioned in my other reply to Friedrich, that is ENabled on both my
32-bit Vista Ultimate and Home Premium machines... and I'm pretty sure I
left them at their default settings.

In Vista Ultimate (and probably Business, but I don't have that running at
the moment), you'll find it by running GPEDIT.MSC.
Then go to
Computer Configuration
Windows Settings
Security Settings
Local Policies
Security Options
User Account Control: Detect application blah blah.....

Home Premium refuses to run GPEDIT.MSC, so I find the setting directly in
the registry:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Pol icies\System\EnableInstallerDetection

Jane

[NewsArchive]

Hi Jane,

>Home Premium refuses to run GPEDIT.MSC, so I find the setting directly in
>the registry:
>HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Pol icies\System\EnableInstallerDetection

It is set to 1 on my machine.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

On mine also after a complete reinstall of Home Premium and of Ultimate.

Jane

[NewsArchive]

Hi Jane,

>On mine also after a complete reinstall of Home Premium and of Ultimate.

So this IS turned ON by default by a standard installation of Vista?

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór and Jane,

I can confirm that it is DISABLED on 1 x Vista Ultimate 64-bit and 3 x Vista
Ultimate 32-bit here in our office. All machines have a very similar
configuration and the installed protection software is identical. I did not
change any policy setting.

So perhaps one of the protection software products changed the state of the
"Detect application installations and prompt for elevation" option ?! This
could be an explanation.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.5
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

> Hi Arn&#243;r and Jane,
>
> I can confirm that it is DISABLED on 1 x Vista Ultimate 64-bit and 3 x Vista
> Ultimate 32-bit here in our office. All machines have a very similar
> configuration and the installed protection software is identical. I did not
> change any policy setting.
>
> So perhaps one of the protection software products changed the state of the
> "Detect application installations and prompt for elevation" option ?! This
> could be an explanation.

Or could it be that the version(s) sold in the US are different than
those sold overseas? Nah, MS would never do that. <g>

Ram&#243;n

[NewsArchive]

Ramón,

>> So perhaps one of the protection software products changed the state of
>> the "Detect application installations and prompt for elevation" option ?!
>> This could be an explanation.
>
> Or could it be that the version(s) sold in the US are different than those
> sold overseas? Nah, MS would never do that. <g>

<G> We have original U.S. versions.

Friedrich

[NewsArchive]

Hi Friedrich,

>So perhaps one of the protection software products changed the state of the
>"Detect application installations and prompt for elevation" option ?! This
>could be an explanation.

What software would that be?

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>So perhaps one of the protection software products changed the state of
>>the "Detect application installations and prompt for elevation" option ?!
>>This could be an explanation.
>
> What software would that be?

I have avast! Professional on both Vista32 and Vista64 machines. Perhaps
the installer (or an avast! application option) changed the installation
detection option.

Friedrich

[NewsArchive]

Hi Arnór,

Confirmed. I have formatted the hard drive, installed Vista Ultimate
32-bit. Did not apply any Vista patch. "Detect application installations
and prompt for elevation" is ENabled. Installed avast! Pro and it updated
itself to the latest version. Installer detection is DISabled! No idea if
this happened during the installation or application initialization process.
I did not check any option that would allow the modification of a group
policy.

I don't know if other "protection" products do similar things.

Friedrich

[NewsArchive]

Jane,

Yes, I know. I fear that I missed the posting where Arnór said his
installer requested elevation :-(

I have the Vista Ultimate 32-bit and 64-bit flagship editions on five
different machines. By default, the "Detect application installations and
prompt for elevation" option is disabled. So it never runs elevated here
and for all C5, C55, C6 installations, virtualization kicks in on my Vista
machines.

So we have different results on different Vista editions. Cool <g>

Friedrich

[NewsArchive]

Strange, Friedrich.
On my Vista Ultimate 32-bit machine that setting is ENabled... and I'm
pretty sure I left it at its default. It's also set on my Home Premium
machine.
I think I'll reformat the disk and reinstall just to make sure.... Or maybe
both of them.....

Jane

[NewsArchive]

Hi Friedrich,

>Yes, I know. I fear that I missed the posting where Arn&#243;r said his
>installer requested elevation :-(

_My_ installer requires admin, i.e. the "Execution Level" on the
"Generator" tab is set to requireAdministrator. Also note that these
installs are for Clarion developers, i.e. third party tools that are
for the most part put into the Clarion\whatever folders.

>I have the Vista Ultimate 32-bit and 64-bit flagship editions on five
>different machines. By default, the "Detect application installations and
>prompt for elevation" option is disabled. So it never runs elevated here
>and for all C5, C55, C6 installations, virtualization kicks in on my Vista
>machines.

If that is the same as the
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Pol icies\System\EnableInstallerDetection
settting then it is set to 1 on my machine and that's how it came
configured.

Best regards,

Arn&#243;r Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Friedrich,
I reinstalled two machines.
One has Win2kPro and Win2KServer, so I just wiped one partition and
installed Home Premium. Installer Detection is enabled (pic).
The second machine... I reinitialized the MBR and installed Ultimate
(32-bit) cold from the media. Also enabled. (pic)
I have NOT applied any MS patches (maybe they change something?)
So I, at least, get the same results on these two editions.

Jane

[NewsArchive]

Hi Jane,

>I have NOT applied any MS patches (maybe they change something?)
>So I, at least, get the same results on these two editions.

I have all MS updates applied to my laptop as of tonight. This key
values is 1 on my machine.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Friedrich,

>I don't know if other "protection" products do similar things.

So you are saying that some installers may change the value of that
registry key from the Vista default 1 to 0?

So you really need to test things with this key both set to 1 and set
to 0. Do you know if you need to reboot in between to make it kick
in?

Best regards,

Arn&#243;r Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>I don't know if other "protection" products do similar things.
>
> So you are saying that some installers may change the value of that
> registry key from the Vista default 1 to 0?

Yes, this seems to be the case.

> So you really need to test things with this key both set to 1 and set
> to 0. Do you know if you need to reboot in between to make it kick
> in?

Yes, a reboot is required to make the configuration change effective (and
disable the installer detection feature).

BTW, do you still have SB4 installations in development or why do you have
to check this in your (new) insallations?

Friedrich

[NewsArchive]

Arnór,

>>Yes, I know. I fear that I missed the posting where Arnór said his
>>installer requested elevation :-(
>
> _My_ installer requires admin, i.e. the "Execution Level" on the
> "Generator" tab is set to requireAdministrator. Also note that these
> installs are for Clarion developers, i.e. third party tools that are
> for the most part put into the Clarion\whatever folders.

If you have a Vista-aware installer (e.g. SetupBuilder 6.5) then you don't
have *any* problem. The installer will only execute with administrator
execution level privileges or it will not start at all ;-) See below.

>>I have the Vista Ultimate 32-bit and 64-bit flagship editions on five
>>different machines. By default, the "Detect application installations and
>>prompt for elevation" option is disabled. So it never runs elevated here
>>and for all C5, C55, C6 installations, virtualization kicks in on my Vista
>>machines.
>
> If that is the same as the
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Pol icies\System\EnableInstallerDetection
> settting then it is set to 1 on my machine and that's how it came
> configured.

This is only of interest if you have *legacy* installations (not
Vista-aware). For example, the old (and original) Clarion 6.0 install
image.

It doesn't matters what the value of "EnableInstallerDetection" is if you
are using SetupBuilder 6.5 ;-)

Does this help?

Friedrich

[NewsArchive]

Hi Friedrich,

>BTW, do you still have SB4 installations in development or why do you have
>to check this in your (new) insallations?

I don't. I'm using SB6.5 latest. But when I installed older versions
of Clarion, they updated the Win.INI correctly and you asked if I was
sure if it was writing to the actual win.ini or the virtualized one.

I'm developing third party installs and for this to work under vista,
the win.ini and path MUST be updated. Either manually or with an
install. It appears that if this registry setting is 1 (as it seems
to be by default) the installers update the win.ini correctly, but not
the path. My script updates the path correctly for all versions that
I have so I'm not worried about that. I was concerned about the
win.ini but I'm not messing with that<g> Either the Clarion
installers update it correctly or not and if not, I'm pretty sure my
installs will not cause any more problem than anyone elses<bg>

Best regards,



Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>BTW, do you still have SB4 installations in development or why do you have
>>to check this in your (new) insallations?
>
> I don't. I'm using SB6.5 latest. But when I installed older versions
> of Clarion, they updated the Win.INI correctly and you asked if I was
> sure if it was writing to the actual win.ini or the virtualized one.
>
> I'm developing third party installs and for this to work under vista,
> the win.ini and path MUST be updated. Either manually or with an
> install. It appears that if this registry setting is 1 (as it seems
> to be by default) the installers update the win.ini correctly, but not
> the path. My script updates the path correctly for all versions that
> I have so I'm not worried about that. I was concerned about the
> win.ini but I'm not messing with that<g> Either the Clarion
> installers update it correctly or not and if not, I'm pretty sure my
> installs will not cause any more problem than anyone elses<bg>

IMO, you should not rely on the "actual" group policy setting. If the user
was smart enough to run the Clarion 5.x installer with "Run as
administrator", then it updated the WIN.INI even if the "Detect application
installations and prompt for elevation" group policy was DISabled.

The Clarion 6 installer *never* updates the WIN.INI.

BTW, Jane is completely right. The default setting for the "Detect
application installations and prompt for elevation" group policy in a
non-enterprise environment is ENabled!

--
User Account Control: Detect application installations and prompt for
elevation
Default: Enabled (home) / Disabled (enterprise)
--

Friedrich

[NewsArchive]

Hi Friedrich,

>This is only of interest if you have *legacy* installations (not
>Vista-aware). For example, the old (and original) Clarion 6.0 install
>image.
>
>It doesn't matters what the value of "EnableInstallerDetection" is if you
>are using SetupBuilder 6.5 ;-)

Exactly. My concern is with developers who install my third party
products under Vista and are installing them for C4, C5, C5.5 or C6.0,
none of which are vista aware. My testing shows that under vista, out
of the box, they all seem to update the correct win.ini file (not the
virtual one) but fail to update the path. My script updates the path
correctly for all versions so I think I'm safe - for now;)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>This is only of interest if you have *legacy* installations (not
>>Vista-aware). For example, the old (and original) Clarion 6.0 install
>>image.
>>
>>It doesn't matters what the value of "EnableInstallerDetection" is if you
>>are using SetupBuilder 6.5 ;-)
>
> Exactly. My concern is with developers who install my third party
> products under Vista and are installing them for C4, C5, C5.5 or C6.0,
> none of which are vista aware. My testing shows that under vista, out
> of the box, they all seem to update the correct win.ini file (not the
> virtual one) but fail to update the path. My script updates the path
> correctly for all versions so I think I'm safe - for now;)

IMO, the C6 installer never updates the correct WIN.INI file under Vista or
Windows Server 2008. That's why I have released the c6_vista_fix.exe
Clarion 6 Vista Installation Fix.

Friedrich

[NewsArchive]

Hi Friedrich,

>IMO, you should not rely on the "actual" group policy setting. If the user
>was smart enough to run the Clarion 5.x installer with "Run as
>administrator", then it updated the WIN.INI even if the "Detect application
>installations and prompt for elevation" group policy was DISabled.

I'm not relying on it, just curious about it. I'm NOT updating the
WIN.INI.

>The Clarion 6 installer *never* updates the WIN.INI.

That's why I'm including and executing your C6fix as well as my path
update for older versions (which the installers do NOT update, no
matter what elevation they are at)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com



Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>>IMO, you should not rely on the "actual" group policy setting. If the
>>user was smart enough to run the Clarion 5.x installer with "Run as
>>administrator", then it updated the WIN.INI even if the "Detect
>>application installations and prompt for elevation" group policy was
>>DISabled.
>
> I'm not relying on it, just curious about it. I'm NOT updating the
> WIN.INI.
>
>>The Clarion 6 installer *never* updates the WIN.INI.
>
> That's why I'm including and executing your C6fix as well as my path
> update for older versions (which the installers do NOT update, no
> matter what elevation they are at)

Okay, perfect!

Friedrich

[NewsArchive]

Hi Friedrich,

>> That's why I'm including and executing your C6fix as well as my path
>> update for older versions (which the installers do NOT update, no
>> matter what elevation they are at)
>
>Okay, perfect!

My only concern was that silly win.ini but that seems to be updated ok
with the older installers with the right elevation and running as
admin, so I'm not going to worry about that in my installs - if it
fails, it fails for a lot of _other_ things as well<g>

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> My only concern was that silly win.ini but that seems to be updated ok
> with the older installers with the right elevation and running as
> admin, so I'm not going to worry about that in my installs - if it
> fails, it fails for a lot of _other_ things as well<g>

Yep <g>

Friedrich

[NewsArchive]

Hi Friedrich,

>IMO, the C6 installer never updates the correct WIN.INI file under Vista or
>Windows Server 2008. That's why I have released the c6_vista_fix.exe
>Clarion 6 Vista Installation Fix.

And that's why I'm running it on Vista for C6. But I had to develop
the path update for previous versions in case they are running on
vista, but I'm not attempting to update the win.ini.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

>>IMO, the C6 installer never updates the correct WIN.INI file under Vista
>>or Windows Server 2008. That's why I have released the c6_vista_fix.exe
>>Clarion 6 Vista Installation Fix.
>
> And that's why I'm running it on Vista for C6. But I had to develop
> the path update for previous versions in case they are running on
> vista, but I'm not attempting to update the win.ini.

Okay. I just wanted to be on the safe side :) because your wrote in one of
your previous messages that "...My testing shows that under vista, out of
the box, they all seem to update the correct win.ini file..."

Friedrich

[NewsArchive]

Hi Friedrich,

>Okay. I just wanted to be on the safe side :) because your wrote in one of
>your previous messages that "...My testing shows that under vista, out of
>the box, they all seem to update the correct win.ini file..."

I meant the OLD pre-C6 installers. On my machine, with no
modifications and running as an admin, the win.ini does get updated.
If it doesn't then I don't think that environment would be detected by
SB, would it? I.e. if I install 5.5 and it updated the virtualized
win.ini, would my SB6.5 install find it when using your DetectClarion
script is used? I presume that it looks in the real win.ini, not the
virtualized one?

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Arnór,

>>Okay. I just wanted to be on the safe side :) because your wrote in one
>>of your previous messages that "...My testing shows that under vista, out
>>of the box, they all seem to update the correct win.ini file..."
>
> I meant the OLD pre-C6 installers. On my machine, with no
> modifications and running as an admin, the win.ini does get updated.
> If it doesn't then I don't think that environment would be detected by
> SB, would it? I.e. if I install 5.5 and it updated the virtualized
> win.ini, would my SB6.5 install find it when using your DetectClarion
> script is used? I presume that it looks in the real win.ini, not the
> virtualized one?

Okay, I understand :)

You are right. Your SB6.5 install cannot find the Clarion information in a
"virtualized" WIN.INI. Your installer requests administrator execution
level and so all built-in Clarion detection features look in the "real"
WIN.INI.

Friedrich

[NewsArchive]

Hi Friedrich,

>You are right. Your SB6.5 install cannot find the Clarion information in a
>"virtualized" WIN.INI. Your installer requests administrator execution
>level and so all built-in Clarion detection features look in the "real"
>WIN.INI.

And IMO if it doesn't work, well then I have done just about
everything I can to resolve it (using your C6 fix and my path fix) and
I'm happy with it:)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php