C7 installs

[NewsArchive]

Friedrich

I have noticed a problem with some clarion 3rd party installs
I don't think its a setup builder problem or something the 3rd party vendors
are missing.....

I was installing some templates for clarion 7 (C:\clarion7 is my clarion
folder)

I run the install
the install registers the template in C7
Everything works fine

BUT
in my clarion 6 libsrc folder (C:\clarion6\librsc)
my builtinsclw gets edited and all the information gets deleted except for a
few lines
Below is all that remains after the install runs

!include('builtins.fm2')
Compile('***',FM2=1)
module('')
OPEN(FILE,UNSIGNED = 022H),NAME('ds_FILEOPEN')
end
***
OMIT('***',FM2=1)
module('')
OPEN(FILE,UNSIGNED = 022H),NAME('Cla$FILE_OPEN') !
end
***

I then have to restore a backup of my builtins.clw to compile any C6 apps.
C7 works fine and all the templates are registered

Ever see this?

--
Eric Jacobowitz
www.castlecomputer.com
www.cctsoftware.com

[NewsArchive]

Eric,

If memory serves, that is generated by the FM3 post installation utility
template. I don't think its needed by C7.

--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm

[NewsArchive]

I dont think so.
I didt have the problem after running the FM3 install
but did have the problem after running an install by another 3rd party
vendor. I contacted the vendor about it, but we are looking other places as
well

--
Eric Jacobowitz
www.castlecomputer.com
www.cctsoftware.com

[NewsArchive]

Hi Eric,

> I didt have the problem after running the FM3 install
> but did have the problem after running an install by another 3rd party
> vendor. I contacted the vendor about it, but we are looking other places as
> well

Only products that replace certain functionality of the RTL need to edit the
builtins, such as FM which replaces the OPEN statement. My guess is that
the developer is not picking up the correct placement of the builtins.clw
for C7 and is editing the C6 one and something goes wrong or the C7 one is
different and he's looking for something that isn't in the C6 one.

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Eric,

You are right. It's not caused by SetupBuilder.

I assume, the 3rd-party vendor modifies (for whatever reason) your original
builtins.clw file. I would suggest to contact the 3rd-party vendor and try
to find out what he is doing with your C6 builtins.clw. Check the
builtins.clw before and after installation and you know the name of the
3rd-party product that causes it.

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner