Index
2003-04-29 09:33Malcolm Greene : EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 10:12Malcolm Greene : RE: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 10:46Ed Leafe : Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 12:26Paul McNett : Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 12:30Greg Gum : RE: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 12:49Paul McNett : Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 13:05Chet Gardiner : Re:[OT] EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 13:19Paul McNett : Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 13:39Malcolm Greene : RE: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
2003-04-29 13:50Paul McNett : Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)
Back to top
EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Malcolm Greene

Posted: 2003-04-29 09:33:00   Link

JVP, others,

I'm looking for some opinions regarding the VFP 8 EULA agreement as it =

relates to the distribution of VFP 8 runtime files to WINDOWS platforms.

1. Does the VFP 8 EULA agreement require us to distribute VFP runtime =

files solely in an MSM format thereby restricting us from using 3rd =

party Setup utilities not based on Windows Installer technology? The =

text in question comes from section 2.3 "so long as you redistribute =

such content in its entirety and do not modify such content in any way"

a) In other words, does that mean that we are also restricted from =

distributing Self-Extracting zip file collections of our VFP 8 =

application? (We have several large corporate customers who request a =

set of files vs. a formal setup. They review the individual files that =

we distribute with our application and decide which files they want to =

distribute in their environment and where these files should go)

b) Does this restriction mean that if one of our client's corrupts a VFP =

8 runtime file that we are legally required to have the user re-install =

our application from scratch vs. sending the user the corrupted or =

deleted file?

c) Do you see any reasonable interpretation of the EULA that might allow =

the distribution of VFP 8 runtime files separate from the MSM packaging, =

i.e. if we redistribute the unmodified content of the MSM files vs. the =

MSM files themselves?

2. Is there anything in the EULA agreement that restricts us from =

distributing VFP 8 applications to the Windows 95 platform?

3. Is there resource at Microsoft where we can send such questions for =

an unambiguous - yes or no answer?

Thanks!

Malcolm

-----Original Message-----

From: profox-admin@leafe.com [mailto:profox-admin@leafe.com]On Behalf Of

John V. Petersen

Sent: Tuesday, April 29, 2003 6:57 AM

To: profox@leafe.com

Subject: RE: [OT] Preview of VFP/Europa

But what about section's 2 and 3????? Yes, I can justify "that" in terms

of the EULA... <s>

2. ADDITIONAL LICENSE RIGHTS -- REDISTRIBUTABLE CODE. In addition

to the rights granted in Section 1, certain portions of the Software, as

described in this Section 2, are provided to you with additional license

rights. These additional license rights are conditioned upon your

compliance with the distribution requirements and license limitations

described in Section 3.

2.1 Sample Code. Microsoft grants you a limited,

nonexclusive, royalty-free license to: (a) use and modify the source

code version of those portions of the Software identified as "Samples"

in REDIST.TXT or elsewhere in the Software ("Sample Code") for the sole

purposes of designing, developing, and testing your software product(s),

and (b) reproduce and distribute the Sample Code, along with any

modifications thereof, in object and/or source code form. For

applicable redistribution requirements for Sample Code, see Section 3.1

below.

2.2 Redistributable Code-General. Microsoft grants you a

limited, nonexclusive, royalty-free license to reproduce and distribute

the object code form of any portion of the Software listed in REDIST.TXT

("Redistributable Code"). For general redistribution requirements for

Redistributable Code, see Section 3.1 below.=20

2.3 Redistributable Code-Microsoft Merge Modules ("MSM").

Microsoft grants you a limited, nonexclusive, royalty-free license to

reproduce and distribute the content of MSM file(s) listed in REDIST.TXT

in the manner described in the Software documentation only so long as

you redistribute such content in its entirety and do not modify such

content in any way. For all other applicable redistribution

requirements for MSM files, see Section 3.1 below.

2.4 Redistributable Code-Visual C++: Microsoft Foundation

Classes (MFC), Active Template Libraries (ATL), and C runtimes (CRTs).

If this EULA accompanies Visual C++, then in addition to the rights

granted in Section 1, Microsoft grants you a license to use and modify

the source code version of those portions of the Software that are

identified as MFC, ATL, or CRTs (collectively, the "VC

Redistributables"), for the sole purposes of designing, developing, and

testing your software product(s). Provided you comply with Section 3.1

and you rename any files created by you that are included in the

Licensee Software (defined below), Microsoft grants you a limited,

nonexclusive, royalty-free license to reproduce and distribute the

object code version of the VC Redistributables, including any

modifications you make. For purposes of this section, "modifications"

shall mean enhancements to the functionality of the VC Redistributables.

For all other applicable redistribution requirements for VC

Redistributables

3. DISTRIBUTION REQUIREMENTS AND OTHER LICENSE RIGHTS AND

LIMITATIONS. If you choose to exercise your rights under Section 2, any

redistribution by you is subject to your compliance with Section 3.1;

some of the Redistributable Code has additional limited use rights

described in Section 3.2.

3.1 General Distribution Requirements. =20

(a) If you choose to redistribute Sample Code, or

Redistributable Code (collectively, the "Redistributables") as described

in Section 2, you agree: (i) except as otherwise noted in Section 2.1

(Sample Code), to distribute the Redistributables only in object code

form and in conjunction with and as a part of a software application

product developed by you that adds significant and primary functionality

to the Redistributables ("Licensee Software"); (ii) that the

Redistributables only operate in conjunction with Microsoft Windows

platforms; (iii) that if the Licensee Software is distributed beyond

Licensee's premises or externally from Licensee's organization, to

distribute the Licensee Software containing the Redistributables

pursuant to an end user license agreement (which may be

"break-the-seal", "click-wrap" or signed), with terms no less protective

than those contained in this EULA; (iv) not to use Microsoft's name,

logo, or trademarks to market the Licensee Software; (v) to display your

own valid copyright notice which shall be sufficient to protect

Microsoft's copyright in the Software; (vi) not to remove or obscure any

copyright, trademark or patent notices that appear on the Software as

delivered to you; (vii) to indemnify, hold harmless, and defend

Microsoft from and against any claims or lawsuits, including attorney's

fees, that arise or result from the use or distribution of the Licensee

Software; (viii) to otherwise comply with the terms of this EULA; and

(ix) agree that Microsoft reserves all rights not expressly granted. =20

You also agree not to permit further distribution of the

Redistributables by your end users except you may permit further

redistribution of the Redistributables by your distributors to your

end-user customers if your distributors only distribute the

Redistributables in conjunction with, and as part of, the Licensee

Software, you comply with all other terms of this EULA, and your

distributors comply with all restrictions of this EULA that are

applicable to you.=20

(b) If you use the Redistributables, then in addition to

your compliance with the applicable distribution requirements described

for the Redistributables, the following also applies. Your license

rights to the Redistributables are conditioned upon your not (i)

creating derivative works of the Redistributables in any manner that

would cause the Redistributables in whole or in part to become subject

to any of the terms of an Excluded License; or (ii) distributing the

Redistributables (or derivative works thereof) in any manner that would

cause the Redistributables to become subject to any of the terms of an

Excluded License. An "Excluded License" is any license that requires as

a condition of use, modification and/or distribution of software subject

to the Excluded License, that such software or other software combined

and/or distributed with such software be (x) disclosed or distributed in

source code form; (y) licensed for the purpose of making derivative

works; or (z) redistributable at no charge.

3.2 Additional Distribution Requirements for Certain

Redistributable Code. If you choose to redistribute the files discussed

in this Section, then in addition to the terms of Section 3.1, you must

ALSO comply with the following.=20

(a) Microsoft SQL Server Desktop Engine ("MSDE"). If you

redistribute MSDE you agree to comply with the following additional

requirements: (a) Licensee Software shall not substantially duplicate

the capabilities of Microsoft Access or, in the reasonable opinion of

Microsoft, compete with same; and (b) unless Licensee Software requires

your customers to license Microsoft Access in order to operate, you

shall not reproduce or use MSDE for commercial distribution in

conjunction with a general purpose word processing, spreadsheet or

database management software product, or an integrated work or product

suite whose components include a general purpose word processing,

spreadsheet, or database management software product except for the

exclusive use of importing data to the various formats supported by

Microsoft Access. A product that includes limited word processing,

spreadsheet or database components along with other components which

provide significant and primary value, such as an accounting product

with limited spreadsheet capability, is not considered to be a "general

purpose" product.=20

(b) Microsoft Data Access Components. If you redistribute

the Microsoft Data Access Component file identified as MDAC_TYP.EXE, you

also agree to redistribute such file in object code only in conjunction

with and as a part of a Licensee Software developed by you with a

Microsoft development tool product that adds significant and primary

functionality to MDAC_TYP.EXE.

3.3 Separation of Components. The Software is licensed as a

single product. Its component parts may not be separated for use by

more than one user.

3.4 Benchmark Testing. The Software may contain the

Microsoft .NET Framework. You may not disclose the results of any

benchmark test of the .NET Framework component of the Software to any

third party without Microsoft's prior written approval.

©2003 Malcolm Greene
Back to top
RE: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Malcolm Greene

Posted: 2003-04-29 10:12:00   Link

Ed,

I read Ken's clarification. My feeling is that was intentionally left =

vague to provide the community with greatest flexibility. Kind of =

reminds me of a "don't ask - don't tell" policy.

Since we haven't seen any feedback from MS to the contrary, we're going =

to continue to distribute the UNMODIFIED CONTENTS of the VFP MSM files =

to WINDOWS based platforms using a setup utility of our choice. If we're =

told to cease and desist, we'll look at other alternatives.

Malcolm

-----Original Message-----

From: profox-admin@leafe.com [mailto:profox-admin@leafe.com]On Behalf Of

Ed Leafe

Sent: Tuesday, April 29, 2003 11:08 AM

To: profox@leafe.com

Subject: Re: EULA question regarding distribution of VFP runtime files

to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

On Tuesday, April 29, 2003, at 10:58 AM, Malcolm Greene wrote:

> 3. Is there resource at Microsoft where we can send such questions for =

> an unambiguous - yes or no answer?

Yes, and he's already answered. The "clarification" is available at=20

http://leafe.com/archives/showMsg/137340, and clearly refuses to answer=20

any further questions that people may have. The only option available=20

to you is to hire an attorney to interpret all the conflicting and=20

confusing language, and then take your chances that he/she has=20

interpreted it the way Microsoft will decide it means at any point in=20

the future.

___/

/

__/

/

____/

Ed Leafe

http://leafe.com/

http://opentech.leafe.com

[excessive quoting removed by server]

©2003 Malcolm Greene
Back to top
Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Ed Leafe

Posted: 2003-04-29 10:46:00   Link

On Tuesday, April 29, 2003, at 10:58 AM, Malcolm Greene wrote:

> 3. Is there resource at Microsoft where we can send such questions for

> an unambiguous - yes or no answer?

Yes, and he's already answered. The "clarification" is available at

http://leafe.com/archives/showMsg/137340, and clearly refuses to answer

any further questions that people may have. The only option available

to you is to hire an attorney to interpret all the conflicting and

confusing language, and then take your chances that he/she has

interpreted it the way Microsoft will decide it means at any point in

the future.

___/

/

__/

/

____/

Ed Leafe

http://leafe.com/

http://opentech.leafe.com

©2003 Ed Leafe
Back to top
Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Paul McNett

Posted: 2003-04-29 12:26:00   Link

Greg Gum writes:

> So are there any other (non-legal) issues for Fox on Linux?

Yes.

+ No HTML Help=20

+ No ActiveX (with various repurcussions in the IDE: class browser won't=20

load, for one)

+ Printing is difficult to set up

+ various vfp popup windows will cycle the main window to the back while=20

showing the popup. Workaround is to set the window to AlwaysOnTop

+ Windows fonts will be substituted with the available X11 fonts (not a=20

problem but it could be annoying)

+ No copy/paste of objects from within the form/class designer

+ SQLSTRINGCONNECT() will always result in a Stack Overflow (VFP error).=20

SQLCONNECT() will work. This means that you must set up and use DSN's=20

instead of passing the connect string manually.

=2E..and possibly other items that I haven't come across yet. I'm running=

my=20

personal TimeTracker application, built in VFP8, on my Linux box without=20

Windows. Except for printing, it runs as well on Linux as it does on=20

Windows. I'm also developing with VFP7 and VFP8 from the IDE on Linux.

Along with the problems I mention above, there's also issues with=20

deployment. Wine being alpha software is not easy to install. Once Wine i=

s=20

installed, however, its a simple matter to copy over your EXE along with=20

the VFP8 runtimes (vfp8r.dll, vfp8renu.dll, and msvcr70.dll).

--=20

Paul McNett

©2003 Paul McNett
Back to top
RE: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Greg Gum

Posted: 2003-04-29 12:30:00   Link

So are there any other (non-legal) issues for Fox on Linux?

Greg

-----Original Message-----

From: Paul McNett [mailto:p@ulmcnett.com]=20

Sent: Tuesday, April 29, 2003 12:15 PM

To: profox@leafe.com

Subject: Re: EULA question regarding distribution of VFP runtime files

to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Charlie Coleman writes:

> I too, as soon as I have apps ready for Linux (and they have the=20

> record-locking thing addressed in WINE), I will be advertising and=20

> deploying my software on Linux (probably not via MSMs though).

By the way, the record locking issue has been resolved for a couple

months=20

now.

--=20

Paul McNett

Liberal Earthling

[excessive quoting removed by server]

©2003 Greg Gum
Back to top
Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Paul McNett

Posted: 2003-04-29 12:49:00   Link

Charlie Coleman writes:

> I too, as soon as I have apps ready for Linux (and they have the

> record-locking thing addressed in WINE), I will be advertising and

> deploying my software on Linux (probably not via MSMs though).

By the way, the record locking issue has been resolved for a couple month=

s=20

now.

--=20

Paul McNett

Liberal Earthling

©2003 Paul McNett
Back to top
Re:[OT] EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Chet Gardiner

Posted: 2003-04-29 13:05:00   Link

Ooooooh.

The Great and Powerful JiViP has spoken to us mere mortals from his Burning

Bush! Oh, we Genuflect to you; Omniscient, Omnipotent JiViP!

So when M$ show up at your door, Malcolm, send them to our God JiViP for His

Clarification.

----- Original Message -----

From: "Malcolm Greene" <mgreene@bdurham.com>

To: <profox@leafe.com>

Sent: Tuesday, April 29, 2003 11:15 AM

Subject: RE: EULA question regarding distribution of VFP runtime files to

WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Thanks John!

Malcolm

-----Original Message-----

From: profox-admin@leafe.com [mailto:profox-admin@leafe.com]On Behalf Of

John V. Petersen

Sent: Tuesday, April 29, 2003 12:16 PM

To: profox@leafe.com

Subject: RE: EULA question regarding distribution of VFP runtime files

to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

My take is this...the MSM is a wrapper for the distributable components.

IMO, if you wanted to distribute VFP without the MSM's, so long as the

contained runtimes were distributed only on a MS-Windows platform, you

would be fine. How you manage that process is up to you...

Again, just my opinion, but I think it is a reasonable one...

< JVP >

-----Original Message-----

From: profox-admin@leafe.com [mailto:profox-admin@leafe.com] On Behalf

Of Malcolm Greene

Sent: Tuesday, April 29, 2003 10:59 AM

To: profox@leafe.com

Subject: EULA question regarding distribution of VFP runtime files to

WINDOWS platforms (was off-topic: Preview of VFP/Europa)

JVP, others,

I'm looking for some opinions regarding the VFP 8 EULA agreement as it

relates to the distribution of VFP 8 runtime files to WINDOWS platforms.

1. Does the VFP 8 EULA agreement require us to distribute VFP runtime

files solely in an MSM format thereby restricting us from using 3rd

party Setup utilities not based on Windows Installer technology? The

text in question comes from section 2.3 "so long as you redistribute

such content in its entirety and do not modify such content in any way"

a) In other words, does that mean that we are also restricted from

distributing Self-Extracting zip file collections of our VFP 8

application? (We have several large corporate customers who request a

set of files vs. a formal setup. They review the individual files that

we distribute with our application and decide which files they want to

distribute in their environment and where these files should go)

b) Does this restriction mean that if one of our client's corrupts a VFP

8 runtime file that we are legally required to have the user re-install

our application from scratch vs. sending the user the corrupted or

deleted file?

c) Do you see any reasonable interpretation of the EULA that might allow

the distribution of VFP 8 runtime files separate from the MSM packaging,

i.e. if we redistribute the unmodified content of the MSM files vs. the

MSM files themselves?

2. Is there anything in the EULA agreement that restricts us from

distributing VFP 8 applications to the Windows 95 platform?

3. Is there resource at Microsoft where we can send such questions for

an unambiguous - yes or no answer?

Thanks!

Malcolm

-----Original Message-----

From: profox-admin@leafe.com [mailto:profox-admin@leafe.com]On Behalf Of

John V. Petersen

Sent: Tuesday, April 29, 2003 6:57 AM

To: profox@leafe.com

Subject: RE: [OT] Preview of VFP/Europa

But what about section's 2 and 3????? Yes, I can justify "that" in terms

of the EULA... <s>

2. ADDITIONAL LICENSE RIGHTS -- REDISTRIBUTABLE CODE. In addition

to the rights granted in Section 1, certain portions of the Software, as

described in this Section 2, are provided to you with additional license

rights. These additional license rights are conditioned upon your

compliance with the distribution requirements and license limitations

described in Section 3.

2.1 Sample Code. Microsoft grants you a limited,

nonexclusive, royalty-free license to: (a) use and modify the source

code version of those portions of the Software identified as "Samples"

in REDIST.TXT or elsewhere in the Software ("Sample Code") for the sole

purposes of designing, developing, and testing your software product(s),

and (b) reproduce and distribute the Sample Code, along with any

modifications thereof, in object and/or source code form. For

applicable redistribution requirements for Sample Code, see Section 3.1

below.

2.2 Redistributable Code-General. Microsoft grants you a

limited, nonexclusive, royalty-free license to reproduce and distribute

the object code form of any portion of the Software listed in REDIST.TXT

("Redistributable Code"). For general redistribution requirements for

Redistributable Code, see Section 3.1 below.

2.3 Redistributable Code-Microsoft Merge Modules ("MSM").

Microsoft grants you a limited, nonexclusive, royalty-free license to

reproduce and distribute the content of MSM file(s) listed in REDIST.TXT

in the manner described in the Software documentation only so long as

you redistribute such content in its entirety and do not modify such

content in any way. For all other applicable redistribution

requirements for MSM files, see Section 3.1 below.

2.4 Redistributable Code-Visual C++: Microsoft Foundation

Classes (MFC), Active Template Libraries (ATL), and C runtimes (CRTs).

If this EULA accompanies Visual C++, then in addition to the rights

granted in Section 1, Microsoft grants you a license to use and modify

the source code version of those portions of the Software that are

identified as MFC, ATL, or CRTs (collectively, the "VC

Redistributables"), for the sole purposes of designing, developing, and

testing your software product(s). Provided you comply with Section 3.1

and you rename any files created by you that are included in the

Licensee Software (defined below), Microsoft grants you a limited,

nonexclusive, royalty-free license to reproduce and distribute the

object code version of the VC Redistributables, including any

modifications you make. For purposes of this section, "modifications"

shall mean enhancements to the functionality of the VC Redistributables.

For all other applicable redistribution requirements for VC

Redistributables

3. DISTRIBUTION REQUIREMENTS AND OTHER LICENSE RIGHTS AND

LIMITATIONS. If you choose to exercise your rights under Section 2, any

redistribution by you is subject to your compliance with Section 3.1;

some of the Redistributable Code has additional limited use rights

described in Section 3.2.

3.1 General Distribution Requirements.

(a) If you choose to redistribute Sample Code, or

Redistributable Code (collectively, the "Redistributables") as described

in Section 2, you agree: (i) except as otherwise noted in Section 2.1

(Sample Code), to distribute the Redistributables only in object code

form and in conjunction with and as a part of a software application

product developed by you that adds significant and primary functionality

to the Redistributables ("Licensee Software"); (ii) that the

Redistributables only operate in conjunction with Microsoft Windows

platforms; (iii) that if the Licensee Software is distributed beyond

Licensee's premises or externally from Licensee's organization, to

distribute the Licensee Software containing the Redistributables

pursuant to an end user license agreement (which may be

"break-the-seal", "click-wrap" or signed), with terms no less protective

than those contained in this EULA; (iv) not to use Microsoft's name,

logo, or trademarks to market the Licensee Software; (v) to display your

own valid copyright notice which shall be sufficient to protect

Microsoft's copyright in the Software; (vi) not to remove or obscure any

copyright, trademark or patent notices that appear on the Software as

delivered to you; (vii) to indemnify, hold harmless, and defend

Microsoft from and against any claims or lawsuits, including attorney's

fees, that arise or result from the use or distribution of the Licensee

Software; (viii) to otherwise comply with the terms of this EULA; and

(ix) agree that Microsoft reserves all rights not expressly granted.

You also agree not to permit further distribution of the

Redistributables by your end users except you may permit further

redistribution of the Redistributables by your distributors to your

end-user customers if your distributors only distribute the

Redistributables in conjunction with, and as part of, the Licensee

Software, you comply with all other terms of this EULA, and your

distributors comply with all restrictions of this EULA that are

applicable to you.

(b) If you use the Redistributables, then in addition to

your compliance with the applicable distribution requirements described

for the Redistributables, the following also applies. Your license

rights to the Redistributables are conditioned upon your not (i)

creating derivative works of the Redistributables in any manner that

would cause the Redistributables in whole or in part to become subject

to any of the terms of an Excluded License; or (ii) distributing the

Redistributables (or derivative works thereof) in any manner that would

cause the Redistributables to become subject to any of the terms of an

Excluded License. An "Excluded License" is any license that requires as

a condition of use, modification and/or distribution of software subject

to the Excluded License, that such software or other software combined

and/or distributed with such software be (x) disclosed or distributed in

source code form; (y) licensed for the purpose of making derivative

works; or (z) redistributable at no charge.

3.2 Additional Distribution Requirements for Certain

Redistributable Code. If you choose to redistribute the files discussed

in this Section, then in addition to the terms of Section 3.1, you must

ALSO comply with the following.

(a) Microsoft SQL Server Desktop Engine ("MSDE"). If you

redistribute MSDE you agree to comply with the following additional

requirements: (a) Licensee Software shall not substantially duplicate

the capabilities of Microsoft Access or, in the reasonable opinion of

Microsoft, compete with same; and (b) unless Licensee Software requires

your customers to license Microsoft Access in order to operate, you

shall not reproduce or use MSDE for commercial distribution in

conjunction with a general purpose word processing, spreadsheet or

database management software product, or an integrated work or product

suite whose components include a general purpose word processing,

spreadsheet, or database management software product except for the

exclusive use of importing data to the various formats supported by

Microsoft Access. A product that includes limited word processing,

spreadsheet or database components along with other components which

provide significant and primary value, such as an accounting product

with limited spreadsheet capability, is not considered to be a "general

purpose" product.

(b) Microsoft Data Access Components. If you redistribute

the Microsoft Data Access Component file identified as MDAC_TYP.EXE, you

also agree to redistribute such file in object code only in conjunction

with and as a part of a Licensee Software developed by you with a

Microsoft development tool product that adds significant and primary

functionality to MDAC_TYP.EXE.

3.3 Separation of Components. The Software is licensed as a

single product. Its component parts may not be separated for use by

more than one user.

3.4 Benchmark Testing. The Software may contain the

Microsoft .NET Framework. You may not disclose the results of any

benchmark test of the .NET Framework component of the Software to any

third party without Microsoft's prior written approval.

[excessive quoting removed by server]

©2003 Chet Gardiner
Back to top
Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Paul McNett

Posted: 2003-04-29 13:19:00   Link

John V. Petersen writes:

> Here is a question...what has NOT been resolved???

See my reply of an hour or so ago.

> If somebody wanted to monitor this thing, where could one go???

You can monitor the Visual FoxPro pages at the WineHQ:

http://appdb.winehq.com/appview.php?appId=3D296

but admittedly the content is a bit stale.

--=20

Paul McNett

©2003 Paul McNett
Back to top
RE: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Malcolm Greene

Posted: 2003-04-29 13:39:00   Link

Thanks John!

Malcolm

-----Original Message-----

From: profox-admin@leafe.com [mailto:profox-admin@leafe.com]On Behalf Of

John V. Petersen

Sent: Tuesday, April 29, 2003 12:16 PM

To: profox@leafe.com

Subject: RE: EULA question regarding distribution of VFP runtime files

to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

My take is this...the MSM is a wrapper for the distributable components.

IMO, if you wanted to distribute VFP without the MSM's, so long as the

contained runtimes were distributed only on a MS-Windows platform, you

would be fine. How you manage that process is up to you...

Again, just my opinion, but I think it is a reasonable one...

< JVP >

-----Original Message-----

From: profox-admin@leafe.com [mailto:profox-admin@leafe.com] On Behalf

Of Malcolm Greene

Sent: Tuesday, April 29, 2003 10:59 AM

To: profox@leafe.com

Subject: EULA question regarding distribution of VFP runtime files to

WINDOWS platforms (was off-topic: Preview of VFP/Europa)

JVP, others,

I'm looking for some opinions regarding the VFP 8 EULA agreement as it

relates to the distribution of VFP 8 runtime files to WINDOWS platforms.

1. Does the VFP 8 EULA agreement require us to distribute VFP runtime

files solely in an MSM format thereby restricting us from using 3rd

party Setup utilities not based on Windows Installer technology? The

text in question comes from section 2.3 "so long as you redistribute

such content in its entirety and do not modify such content in any way"

a) In other words, does that mean that we are also restricted from

distributing Self-Extracting zip file collections of our VFP 8

application? (We have several large corporate customers who request a

set of files vs. a formal setup. They review the individual files that

we distribute with our application and decide which files they want to

distribute in their environment and where these files should go)

b) Does this restriction mean that if one of our client's corrupts a VFP

8 runtime file that we are legally required to have the user re-install

our application from scratch vs. sending the user the corrupted or

deleted file?

c) Do you see any reasonable interpretation of the EULA that might allow

the distribution of VFP 8 runtime files separate from the MSM packaging,

i.e. if we redistribute the unmodified content of the MSM files vs. the

MSM files themselves?

2. Is there anything in the EULA agreement that restricts us from

distributing VFP 8 applications to the Windows 95 platform?

3. Is there resource at Microsoft where we can send such questions for

an unambiguous - yes or no answer?

Thanks!

Malcolm

-----Original Message-----

From: profox-admin@leafe.com [mailto:profox-admin@leafe.com]On Behalf Of

John V. Petersen

Sent: Tuesday, April 29, 2003 6:57 AM

To: profox@leafe.com

Subject: RE: [OT] Preview of VFP/Europa

But what about section's 2 and 3????? Yes, I can justify "that" in terms

of the EULA... <s>

2. ADDITIONAL LICENSE RIGHTS -- REDISTRIBUTABLE CODE. In addition

to the rights granted in Section 1, certain portions of the Software, as

described in this Section 2, are provided to you with additional license

rights. These additional license rights are conditioned upon your

compliance with the distribution requirements and license limitations

described in Section 3.

2.1 Sample Code. Microsoft grants you a limited,

nonexclusive, royalty-free license to: (a) use and modify the source

code version of those portions of the Software identified as "Samples"

in REDIST.TXT or elsewhere in the Software ("Sample Code") for the sole

purposes of designing, developing, and testing your software product(s),

and (b) reproduce and distribute the Sample Code, along with any

modifications thereof, in object and/or source code form. For

applicable redistribution requirements for Sample Code, see Section 3.1

below.

2.2 Redistributable Code-General. Microsoft grants you a

limited, nonexclusive, royalty-free license to reproduce and distribute

the object code form of any portion of the Software listed in REDIST.TXT

("Redistributable Code"). For general redistribution requirements for

Redistributable Code, see Section 3.1 below.=20

2.3 Redistributable Code-Microsoft Merge Modules ("MSM").

Microsoft grants you a limited, nonexclusive, royalty-free license to

reproduce and distribute the content of MSM file(s) listed in REDIST.TXT

in the manner described in the Software documentation only so long as

you redistribute such content in its entirety and do not modify such

content in any way. For all other applicable redistribution

requirements for MSM files, see Section 3.1 below.

2.4 Redistributable Code-Visual C++: Microsoft Foundation

Classes (MFC), Active Template Libraries (ATL), and C runtimes (CRTs).

If this EULA accompanies Visual C++, then in addition to the rights

granted in Section 1, Microsoft grants you a license to use and modify

the source code version of those portions of the Software that are

identified as MFC, ATL, or CRTs (collectively, the "VC

Redistributables"), for the sole purposes of designing, developing, and

testing your software product(s). Provided you comply with Section 3.1

and you rename any files created by you that are included in the

Licensee Software (defined below), Microsoft grants you a limited,

nonexclusive, royalty-free license to reproduce and distribute the

object code version of the VC Redistributables, including any

modifications you make. For purposes of this section, "modifications"

shall mean enhancements to the functionality of the VC Redistributables.

For all other applicable redistribution requirements for VC

Redistributables

3. DISTRIBUTION REQUIREMENTS AND OTHER LICENSE RIGHTS AND

LIMITATIONS. If you choose to exercise your rights under Section 2, any

redistribution by you is subject to your compliance with Section 3.1;

some of the Redistributable Code has additional limited use rights

described in Section 3.2.

3.1 General Distribution Requirements. =20

(a) If you choose to redistribute Sample Code, or

Redistributable Code (collectively, the "Redistributables") as described

in Section 2, you agree: (i) except as otherwise noted in Section 2.1

(Sample Code), to distribute the Redistributables only in object code

form and in conjunction with and as a part of a software application

product developed by you that adds significant and primary functionality

to the Redistributables ("Licensee Software"); (ii) that the

Redistributables only operate in conjunction with Microsoft Windows

platforms; (iii) that if the Licensee Software is distributed beyond

Licensee's premises or externally from Licensee's organization, to

distribute the Licensee Software containing the Redistributables

pursuant to an end user license agreement (which may be

"break-the-seal", "click-wrap" or signed), with terms no less protective

than those contained in this EULA; (iv) not to use Microsoft's name,

logo, or trademarks to market the Licensee Software; (v) to display your

own valid copyright notice which shall be sufficient to protect

Microsoft's copyright in the Software; (vi) not to remove or obscure any

copyright, trademark or patent notices that appear on the Software as

delivered to you; (vii) to indemnify, hold harmless, and defend

Microsoft from and against any claims or lawsuits, including attorney's

fees, that arise or result from the use or distribution of the Licensee

Software; (viii) to otherwise comply with the terms of this EULA; and

(ix) agree that Microsoft reserves all rights not expressly granted. =20

You also agree not to permit further distribution of the

Redistributables by your end users except you may permit further

redistribution of the Redistributables by your distributors to your

end-user customers if your distributors only distribute the

Redistributables in conjunction with, and as part of, the Licensee

Software, you comply with all other terms of this EULA, and your

distributors comply with all restrictions of this EULA that are

applicable to you.=20

(b) If you use the Redistributables, then in addition to

your compliance with the applicable distribution requirements described

for the Redistributables, the following also applies. Your license

rights to the Redistributables are conditioned upon your not (i)

creating derivative works of the Redistributables in any manner that

would cause the Redistributables in whole or in part to become subject

to any of the terms of an Excluded License; or (ii) distributing the

Redistributables (or derivative works thereof) in any manner that would

cause the Redistributables to become subject to any of the terms of an

Excluded License. An "Excluded License" is any license that requires as

a condition of use, modification and/or distribution of software subject

to the Excluded License, that such software or other software combined

and/or distributed with such software be (x) disclosed or distributed in

source code form; (y) licensed for the purpose of making derivative

works; or (z) redistributable at no charge.

3.2 Additional Distribution Requirements for Certain

Redistributable Code. If you choose to redistribute the files discussed

in this Section, then in addition to the terms of Section 3.1, you must

ALSO comply with the following.=20

(a) Microsoft SQL Server Desktop Engine ("MSDE"). If you

redistribute MSDE you agree to comply with the following additional

requirements: (a) Licensee Software shall not substantially duplicate

the capabilities of Microsoft Access or, in the reasonable opinion of

Microsoft, compete with same; and (b) unless Licensee Software requires

your customers to license Microsoft Access in order to operate, you

shall not reproduce or use MSDE for commercial distribution in

conjunction with a general purpose word processing, spreadsheet or

database management software product, or an integrated work or product

suite whose components include a general purpose word processing,

spreadsheet, or database management software product except for the

exclusive use of importing data to the various formats supported by

Microsoft Access. A product that includes limited word processing,

spreadsheet or database components along with other components which

provide significant and primary value, such as an accounting product

with limited spreadsheet capability, is not considered to be a "general

purpose" product.=20

(b) Microsoft Data Access Components. If you redistribute

the Microsoft Data Access Component file identified as MDAC_TYP.EXE, you

also agree to redistribute such file in object code only in conjunction

with and as a part of a Licensee Software developed by you with a

Microsoft development tool product that adds significant and primary

functionality to MDAC_TYP.EXE.

3.3 Separation of Components. The Software is licensed as a

single product. Its component parts may not be separated for use by

more than one user.

3.4 Benchmark Testing. The Software may contain the

Microsoft .NET Framework. You may not disclose the results of any

benchmark test of the .NET Framework component of the Software to any

third party without Microsoft's prior written approval.

[excessive quoting removed by server]

©2003 Malcolm Greene
Back to top
Re: EULA question regarding distribution of VFP runtime files to WINDOWS platforms (was off-topic: Preview of VFP/Europa)

Author: Paul McNett

Posted: 2003-04-29 13:50:00   Link

John V. Petersen writes:

> I see you have answered my question here...

>

> So, you can't print.... Doesn't this effectively knock this out as a

> viable alternative???

I didn't say you can't print, just that its a pain in the ass (currently)=

to=20

set it up. This is all experimental stuff, not ready for prime time.

> With respect to ActiveX controls, and the lack of support, that makes i=

t

> a non-starter too...

Well... only if you rely on ActiveX controls. I always thought that Activ=

eX=20

was a pain in the ass to maintain so I avoided it like the plague. I've m=

et=20

a few others that have followed the same advice.

And... just because ActiveX doesn't work right now, that doesn't mean it=20

won't work in the future. Same goes for HTML help. The Wine folks are=20

writing their own HTML Help viewer based on either Mozilla or KHTML=20

(Konqueror). They'll likely eventually get ActiveX working as well.

> <<

> however, its a simple matter to copy over your EXE along with

> the VFP8 runtimes (vfp8r.dll, vfp8renu.dll, and msvcr70.dll).

> <<

>

> Looks like a EULA violation to me...

Perhaps it is, I really don't know. Nothing has been clarified for me in=20

this regard. I'm currently learning other languages and will wean myself=20

from VFP development but will continue telling people how to get VFP/Linu=

x=20

working until I'm told specifically to stop it.

> Well...at least it is on record now as an admission....

An admission of what? I never proposed the VFP/Wine thing as a viable=20

solution for the masses now. Just as a heads-up/preview of what we'll be=20

able to do a year or 18 months from now as Wine matures.=20

--=20

Paul McNett

©2003 Paul McNett