Good Evening All:
I decided it was time to get one of my apps running in Windows 7 Professional 64 bit SP1.
When I create the distribution disks in Window XP SP3 with the exact same set of source files I don't get any errors in Installshield that comes with VFP9.
When I create the same distribution disk set in Windows 7 I get 2 errors:
Error1: Files Not Found Error merging module _VC_SYSTEM_CRT for feature 'AlwaysInstall'
Error2: Cannot extract icon from source EXE file.
I looked in the alwaysinstall file listing and don't see the _VC... file.
I am not sure what error 2 even means...I do include the 3 ICO files for the app in the source files as the app is used for 3 teams with a system table changing report titles, BMPS and icos accordingly.
The EXE was compiled in VFP9 SP2 on the Windows 7 box with no errors.
I installed the distribution disk set made on the Windows 7 box on another Windows 7 box and all appears to work as it did in XP.
Any ideas on these 2 errors or since it appears to work should I disregard the error messages.
Thanks for any help.
Regards,
Jack Skelley
Jack Skelley
Senior Director, Programming/Computer Operations
New Jersey Devils
(973)757-6164
JSkelley@newjerseydevils.com
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/7D9E7F72B813014C8FD022CF04F820ED08AF18@EX08.drdad.thenewarkarena.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Jack Skelley <JSkelley@newjerseydevils.com> wrote:
>Good Evening All:
>I decided it was time to get one of my apps running in Windows 7
>Professional 64 bit SP1.
>When I create the distribution disks in Window XP SP3 with the exact
>same set of source files I don't get any errors in Installshield that
>comes with VFP9.
>When I create the same distribution disk set in Windows 7 I get 2
>errors:
>Error1: Files Not Found Error merging module _VC_SYSTEM_CRT for feature
>'AlwaysInstall'
>Error2: Cannot extract icon from source EXE file.
>I looked in the alwaysinstall file listing and don't see the _VC...
>file.
>I am not sure what error 2 even means...I do include the 3 ICO files
>for the app in the source files as the app is used for 3 teams with a
>system table changing report titles, BMPS and icos accordingly.
>The EXE was compiled in VFP9 SP2 on the Windows 7 box with no errors.
>I installed the distribution disk set made on the Windows 7 box on
>another Windows 7 box and all appears to work as it did in XP.
>Any ideas on these 2 errors or since it appears to work should I
>disregard the error messages.
>Thanks for any help.
>Regards,
>
>Jack Skelley
>
>Jack Skelley
Are the other Win 7 systems which successfully installed 32 bit?
--
Tracy Pearson
PowerChurch Software
Sent from my Android phone with K-9 Mail.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/f57555d3-84fc-41a4-964b-77953096f873@email.android.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Now is the time to change to Innosetup. We use it for everything from win2000 to Win7 (32 and 64 bit), same exe. no
problems. (except when the local hardware guy installs in some M$ recommended location).
We recommend installing directly to a folder on the C: drive of the server and share that folder (never the C: drive)
and then workstations work fine.
----- Original Message -----
From: "Jack Skelley" <JSkelley@newjerseydevils.com>
To: <profox@leafe.com>
Sent: Wednesday, September 07, 2011 4:03 PM
Subject: VFP9 SP2 Installshield Errors
Good Evening All:
I decided it was time to get one of my apps running in Windows 7 Professional 64 bit SP1.
When I create the distribution disks in Window XP SP3 with the exact same set of source files I don't get any errors in
Installshield that comes with VFP9.
When I create the same distribution disk set in Windows 7 I get 2 errors:
Error1: Files Not Found Error merging module _VC_SYSTEM_CRT for feature 'AlwaysInstall'
Error2: Cannot extract icon from source EXE file.
I looked in the alwaysinstall file listing and don't see the _VC... file.
I am not sure what error 2 even means...I do include the 3 ICO files for the app in the source files as the app is used
for 3 teams with a system table changing report titles, BMPS and icos accordingly.
The EXE was compiled in VFP9 SP2 on the Windows 7 box with no errors.
I installed the distribution disk set made on the Windows 7 box on another Windows 7 box and all appears to work as it
did in XP.
Any ideas on these 2 errors or since it appears to work should I disregard the error messages.
Thanks for any help.
Regards,
Jack Skelley
Jack Skelley
Senior Director, Programming/Computer Operations
New Jersey Devils
(973)757-6164
JSkelley@newjerseydevils.com
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/06d401cc6dbc$e5961800$7a00a8c0@w2k3s02
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Jack,
I would strongly encourage you to consider using the free Inno Setup
product vs. InstallShield.
I've had to use InstallShield on occassion and always found it awkward
and bulky.
On the other hand I've found InnoSetup to be simple but powerful.
There are a bunch of InnoSetup scripts for VFP apps floating around the
internet, on the wiki, and in the Profox mail archives.
Malcolm
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1315441149.27106.140258138557901@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
I agree that Inno Setup is the way to go. I have been using it for
years. I install everything in c:\users\public\applications\myapp (I
create the applications folder).
I works fantastic for me!
Jeff
---------------
Jeff Johnson
jeff@san-dc.com
(623) 582-0323
www.san-dc.com
On 09/07/2011 05:19 PM, Malcolm Greene wrote:
> Jack,
>
> I would strongly encourage you to consider using the free Inno Setup
> product vs. InstallShield.
>
> I've had to use InstallShield on occassion and always found it awkward
> and bulky.
>
> On the other hand I've found InnoSetup to be simple but powerful.
>
> There are a bunch of InnoSetup scripts for VFP apps floating around the
> internet, on the wiki, and in the Profox mail archives.
>
> Malcolm
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4E680D71.1000808@san-dc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: MB Software Solutions, LLC
Posted: 2011-09-08 11:42:02 Link
On 9/7/2011 8:18 PM, kamcginnis@gmail.com wrote:
> Now is the time to change to Innosetup. We use it for everything from win2000 to Win7 (32 and 64 bit), same exe. no
> problems. (except when the local hardware guy installs in some M$ recommended location).
>
> We recommend installing directly to a folder on the C: drive of the server and share that folder (never the C: drive)
> and then workstations work fine.
+1. Dump Installshield. Inno looks just as professional. It's not
"less" in any way except maybe filesize and complexity (which is good!).
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4E68E24A.5080009@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: MB Software Solutions, LLC
Posted: 2011-09-08 11:43:07 Link
On 9/7/2011 8:19 PM, Malcolm Greene wrote:
> Jack,
>
> I would strongly encourage you to consider using the free Inno Setup
> product vs. InstallShield.
>
> I've had to use InstallShield on occassion and always found it awkward
> and bulky.
>
> On the other hand I've found InnoSetup to be simple but powerful.
>
> There are a bunch of InnoSetup scripts for VFP apps floating around the
> internet, on the wiki, and in the Profox mail archives.
Rick Borup has some great whitepapers and examples on his website.
Search for him either in the Profox archives and/or online elsewhere.
He's great and his material is too.
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4E68E28B.4020401@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Good Afternoon All:
Thanks to all that responded to my 2 errors that are generated form Windows 7 64 bit and Installshield that shipped with VFP9.
I did not check it on a Windows 7 32 bit box as I don't have one to install Installshield on.
I am going to investigate Innosetup when I get a chance.
Installshield worked ok on my XP box and admittedly was awkward. I am not satisfied with 'seen' errors so the alternative will be investigated.
As usual, thanks for all the valuable input.
Best regards,
Jack
Jack Skelley
Senior Director, Programming/Computer Operations
New Jersey Devils
(973)757-6164
JSkelley@newjerseydevils.com ________________________________________
From: profoxtech-bounces@leafe.com [profoxtech-bounces@leafe.com] on behalf of kamcginnis@gmail.com [kamcginnis@gmail.com]
Sent: Wednesday, September 07, 2011 8:18 PM
To: profoxtech@leafe.com
Subject: Re: VFP9 SP2 Installshield Errors
Now is the time to change to Innosetup. We use it for everything from win2000 to Win7 (32 and 64 bit), same exe. no
problems. (except when the local hardware guy installs in some M$ recommended location).
We recommend installing directly to a folder on the C: drive of the server and share that folder (never the C: drive)
and then workstations work fine.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/7D9E7F72B813014C8FD022CF04F820ED08B498@EX08.drdad.thenewarkarena.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Jack,
While you may find the Innosetup scripts simple and easy to use, be
aware that there is a GUI front-end available for creating the Innosetup
scripts. It's not really similar to the Installshield setup screens, but
it works pretty well.
Mike
-------- Original Message --------
Subject: Re: VFP9 SP2 Installshield Errors
From: Jack Skelley <JSkelley@newjerseydevils.com>
To: profoxtech@leafe.com
Date: 9/8/2011 2:48 PM
Good Afternoon All:
Thanks to all that responded to my 2 errors that are generated form Windows 7 64 bit and Installshield that shipped with VFP9.
I did not check it on a Windows 7 32 bit box as I don't have one to install Installshield on.
I am going to investigate Innosetup when I get a chance.
Installshield worked ok on my XP box and admittedly was awkward. I am not satisfied with 'seen' errors so the alternative will be investigated.
As usual, thanks for all the valuable input.
Best regards,
Jack
Jack Skelley
Senior Director, Programming/Computer Operations
New Jersey Devils
(973)757-6164
JSkelley@newjerseydevils.com ________________________________________
From: profoxtech-bounces@leafe.com [profoxtech-bounces@leafe.com] on behalf of kamcginnis@gmail.com [kamcginnis@gmail.com]
Sent: Wednesday, September 07, 2011 8:18 PM
To: profoxtech@leafe.com
Subject: Re: VFP9 SP2 Installshield Errors
Now is the time to change to Innosetup. We use it for everything from win2000 to Win7 (32 and 64 bit), same exe. no
problems. (except when the local hardware guy installs in some M$ recommended location).
We recommend installing directly to a folder on the C: drive of the server and share that folder (never the C: drive)
and then workstations work fine.
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4E691DC1.8070805@ggisoft.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: MB Software Solutions, LLC
Posted: 2011-09-08 16:29:01 Link
On 9/8/2011 3:55 PM, Mike Copeland wrote:
> Jack,
>
> While you may find the Innosetup scripts simple and easy to use, be
> aware that there is a GUI front-end available for creating the Innosetup
> scripts. It's not really similar to the Installshield setup screens, but
> it works pretty well.
http://sourceforge.net/projects/istool/
Definitely use this as the front-end to Inno. +11111
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4E69258D.6080504@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.