DLL files
Paul
I have just tried to run a exe file on a machine without VFP installed on, but it keeps poping up a message saying: Cannot locate the microsoft visual foxpro library. I am sure it is to do with missing library files, can anyone tell me when i am doing a build of a project, do i need to create any dll files, and despatch them with the exe.
Thanks
Paul
Eric den Doop
You wrote on Thu, 27 May 2004 00:11:02 -0700:
P> I have just tried to run a exe file on a machine without VFP installed
P> on, but it keeps poping up a message saying: Cannot locate the microsoft
P> visual foxpro library. I am sure it is to do with missing library files,
P> can anyone tell me when i am doing a build of a project, do i need to
P> create any dll files, and despatch them with the exe.
Visual FoxPro executables require the VFP runtime libraries. You must
include these in your setup.
For VFP7 and VFP8:
http://fox.wikis.com/wc.dll?Wiki~VFP7RuntimeFiles
http://fox.wikis.com/wc.dll?Wiki~VFP8RuntimeFiles~VFP
If you're talking about older VFP versions, let us know.
--
Eric den Doop
www.foxite.com - The Home Of The Visual FoxPro Experts - Powered By VFP8
Rick Bean
Just a bit of confusion on my part. Why are you creating a "new" install for such an old application? What happened to the original install?
It's likely the "Insufficient Memory" error is due to too much memory - more than 512MB or 768MB, depending on whether you are running VFP 3.0 or 3.0b See http://support.microsoft.com/default.aspx?scid=137809 for details.
VFP 3.0 is so old, that I doubt you'll find a reference on what files are required, but someone may remember. I believe it was last updated in 1995 or possibly 1996. (All I have left of it is the Help file and it's dated 6/21/1995.)
The VFP 9.0 free public beta will be released in a week or two, you may want to consider updating. See Ken Levy's newsletter at http://msdn.microsoft.com/vfoxpro/letters/ - also check out the prior months links listed on the right for even more details on 9.0!
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:EB816A59-8EEB-44E8...@microsoft.com...
> I have the same problem!!!
>
> I'm using VFP 3.0 and after creating an install with InstallShield, I get the same error mentioned by Paul.
>
> Since I cannot open VFP due to Insufficient Memory, nor do I have the source code for the FoxPro application, I am left in the dark here trying to figure out what the missing file(s) is.
>
> Thanks!
>
> Mel
Dan Freeman
Use it instead of Installshield.
Dan
Mel wrote:
> Hi Rick!!
>
> I had been trying to reply to your post in my other thread but kept
> running into the "Server Unavailable Temporarily" on my laptop so I
> am using a different computer and it works now.
>
> The application that was written in foxpro 3.0 - I don't have the
> source code and the client gave me their foxpro 3.0 so that is all I
> have to work with and the only thing I can do for them is to create
> an install for them is with InstallShield so they can have an install
> for their clients who still want that program (they don't have the
> setup files for it, either).
>
> They won't want to pay for the upgrade since there won't be any more
> programs written in FoxPro. I usually write programs in Visual Basic
> 6 for them. They don't even want me to re write the program in VB
> because it would take at least 3 months.
>
> I hope that clears things up?
>
> Mel
> ----- Rick Bean wrote: -----
Rick Bean
Just as guess, based on later versions of VFP, I'd start by looking for two files:
VFP300.DLL
VFP3ENU.DLL && the ENU implies the English Localization, other languages may have been supplied
Then I'd use DEPENDS.EXE (from MS in VS) to inspect these, to check if there were any other files that might be required that aren't "normally" on the end users' systems.
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:3812D5DF-19BF-4408...@microsoft.com...
>
> Hi Rick!!
>
> I had been trying to reply to your post in my other thread but kept running into the "Server Unavailable Temporarily" on my laptop so I am using a different computer and it works now.
>
> The application that was written in foxpro 3.0 - I don't have the source code and the client gave me their foxpro 3.0 so that is all I have to work with and the only thing I can do for them is to create an install for them is with InstallShield so they can have an install for their clients who still want that program (they don't have the setup files for it, either).
>
> They won't want to pay for the upgrade since there won't be any more programs written in FoxPro. I usually write programs in Visual Basic 6 for them. They don't even want me to re write the program in VB because it would take at least 3 months.
>
> I hope that clears things up?
>
> Mel
> ----- Rick Bean wrote: -----
>
Mel
As for DEPENDS.EXE, ithe only thing I see is:
Module Time STamp
! XXX.Exe No PE signature found. This is not a valid Win32 module
Does this mean there is no way to create an install for this app?
Rick Bean
First, I wasn't suggesting that you check the actual application .EXE with DEPENDS, just the associated runtime files. A VFP .EXE is really just a small set of code that looks for the VFP runtime files and then turns over control to it. (Most of the ,EXE is "data" - p-code for the VFP RT interpreter.)
VFP 3.0 was different than later versions, because it was the only one that could create Win 3.x apps - using Win32s - or true 32-bit apps (just NT 3.51 and Win 95 at that time). If you use a hex viewer on the VFP .EXE, and wnder down a ways in the code, you should see - in 32-bit characters - the name of VFP runtime file it's looking for.
I'll do some digging - I think I still have VFP 3.0 and/or 3.0b on a CD somewhere, maybe I can spot the RT files on the install. (I can't install it since I've got too much memory!)
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:E9DB83E8-AA18-4782...@microsoft.com...
Rick Bean
Look for VFP300.ESL - it's really a .DLL inside. VFP 3.0 is version 3.0.0.596, and VFP 3.0b is version 3.0.0.711. It doesn't look like they have any internalization on this one, so there isn't a second RT file.
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:F953C2B5-9B0F-440A...@microsoft.com...
>
> Rick,
>
> Thanks for replying and I am not really sure how to do what you said about the hex viewer, but I'll keep my fingers crossed when you find that 3.0 and finding out what the RT files are.
>
> Until then, have a great weekend - assuming you don't "work" this weekend. :)
>
> Thanks,
Leonid
Leonid
"Rick Bean" <rgb...@unrealmelange-inc.com> wrote in message news:ujRQ7VYR...@TK2MSFTNGP09.phx.gbl...
Rick Bean
Are you putting the .ESL file in the same directory as the application? If you are putting it in the system directory, did you install under a local administrator login, so that all users can "see" the file?
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:D21216A9-A0E6-4E9E...@microsoft.com...
> Rick,
>
> Yes, I know about VFP300.ESL, I even included that in InstallShield and when running the application after the install, I still get the "Cannot locate foxpro library support" error.
>
> Any more suggestions? I hope you do...
>
> Mel
>
> ----- Rick Bean wrote: -----
>
> Mel,
> Look for VFP300.ESL - it's really a .DLL inside. VFP 3.0 is version 3.0.0.596, and VFP 3.0b is version 3.0.0.711. It doesn't look like they have any internalization on this one, so there isn't a second RT file.
>
> Rick
>
> "Mel" <anon...@discussions.microsoft.com> wrote in message news:F953C2B5-9B0F-440A...@microsoft.com...
> >> Rick,
> >> Thanks for replying and I am not really sure how to do what you said about the hex viewer, but I'll keep my fingers crossed when you find that 3.0 and finding out what the RT files are.
> >> Until then, have a great weekend - assuming you don't "work" this weekend. :)
> >> Thanks,
> >> Mel
> > ----- Rick Bean wrote: -----
> >> Mel,
> > First, I wasn't suggesting that you check the actual application ..EXE with DEPENDS, just the associated runtime files. A VFP .EXE is really just a small set of code that looks for the VFP runtime files and then turns over control to it. (Most of the ,EXE is "data" - p-code for the VFP RT interpreter.)
Rick Bean
The one possibility we haven't explored is that it isn't a VFP 3.0 .EXE. Get out your Hex Viewer again, and check the table, or run the program at http://fox.wikis.com/wc.dll?Wiki~IdentifyFoxProVersionFromEXE. The code file will tell you what version it really wants! (You'll note that I couldn't find anyone with a VFP 3.0 .EXE to know the offset to look at, but it should be in that general area - only VFP 5.0 was really different - so far!
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:9A709445-44A3-4B1D...@microsoft.com...
>
> Rick,
>
> I tried both ways - putting it in the same directory as the application (program files) and the system directory (both system and system32).
>
> I have full rights on my laptop so I don't know if that is the problem...?
>
>
> ----- Rick Bean wrote: -----
>
> Mel,
> Are you putting the .ESL file in the same directory as the application? If you are putting it in the system directory, did you install under a local administrator login, so that all users can "see" the file?
>
> Rick
>
> "Mel" <anon...@discussions.microsoft.com> wrote in message news:D21216A9-A0E6-4E9E...@microsoft.com...
> > Rick,
> >> Yes, I know about VFP300.ESL, I even included that in InstallShield and when running the application after the install, I still get the "Cannot locate foxpro library support" error.
> >> Any more suggestions? I hope you do...
> >> Mel
> >> ----- Rick Bean wrote: -----
> >> Mel,
> > Look for VFP300.ESL - it's really a .DLL inside. VFP 3.0 is version 3.0.0.596, and VFP 3.0b is version 3.0.0.711. It doesn't look like they have any internalization on this one, so there isn't a second RT file.
> >> Rick
> >> "Mel" <anon...@discussions.microsoft.com> wrote in message news:F953C2B5-9B0F-440A...@microsoft.com...
> >>> Rick,
> >>> Thanks for replying and I am not really sure how to do what you said about the hex viewer, but I'll keep my fingers crossed when you find that 3.0 and finding out what the RT files are.
> >>> Until then, have a great weekend - assuming you don't "work" this weekend. :)
> >>> Thanks,
> >>> Mel
> >> ----- Rick Bean wrote: -----
> >>> Mel,
> >> First, I wasn't suggesting that you check the actual application ..EXE with DEPENDS, just the associated runtime files. A VFP ..EXE is really just a small set of code that looks for the VFP runtime files and then turns over control to it. (Most of the ,EXE is "data" - p-code for the VFP RT interpreter.)
Mel
Rick,
Okay, but I feel like a complete moron because I have no clue what Hex Viewer is, or even how to use it... and as you know I can't even open my foxpro 3.0 application due to Insufficient Memory so I can't copy and paste the code written at that site.
Is there a downloadable exe from that site that I can run to check the verision of the program that was supposedly to be written in foxpro 3.0? I have some bunch of .dbf datafiles as well, which I've managed to open with Excel - which means nothing to you, but I guess that should tell you that it IS a foxpro application for sure, right?
>>> First, I wasn't suggesting that you check the actual application ..EXE with DEPENDS, just the associated runtime files. A VFP ...EXE is really just a small set of code that looks for the VFP runtime files and then turns over control to it. (Most of the ,EXE is "data" - p-code for the VFP RT interpreter.)
Rick Bean
A "hex viewer" is simply a program that allows you to view any data file in both ASCII and hex format, so that you can find things that aren't always obvious in a text viewer (like notepad.exe). There are many freeware, shareware and commercial products that provide this capability. I use WinHex (http://www.x-ways.net/), but it's definitely overkill for this situation. Quick View Plus (http://www.avantstar.com/solutions/quick_view_plus/default.aspx) also has an option to show any file in hex format. I just did a Google search on "hex file viewer" (without the quotes), and got almost 65K hits. You could also check most any shareware download site.
The problem with an executable of the little program I wrote on the Wiki site, it that it would require a VFP Runtime installed (5 or greater). I don't have the resources right now to write this in C/C++ so that you wouldn't need a VFP RT.
Nope: Most any xBase (non-VFP) .DBF table can be opened in Excel with the Jet data engine. That includes dBase II -> IV, FoxBase, Alpha 4 & 5(?), FoxPro 1 -> 2.6, (most of) Clipper, and a number of others I've probably forgotten.
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:29A2D289-3F09-46AD...@microsoft.com...
<rush.strong]@[verizon.net>
- Rush
"Rick Bean" <rgb...@unrealmelange-inc.com> wrote in message
news:e$FvkwWSE...@TK2MSFTNGP11.phx.gbl...
Mel
I ran the Quick View Plus and here's what it said about the main app:
WINDOWS EXECUTABLE
16bit for Windows 3.x
Technical File Information:
Description: C:\dosdev\foxw.exe
Module Name: foxw
Operating System: Microsoft Windows
Expected Windows Version: 3.00
Signature: 454e
Linker Version: 5.01
Checksum: 00000000
Automatic Data Segment: 2
Initial Heap Size: 0400
Initial Stack Segment: 2000
Initial CS:IP: 1:09b4
Initial SS:SP: 2:0000
Segment Table: offset - 000000c0
entries - 0002
Resource Table: offset - 000000d0
segments - 0000
Resident-Name Table: offset - 000000d0
Module-Reference Table: offset - 000000d8
entries - 0002
Imported-Names Table: offset - 000000dc
Entry Table: offset - 000000e9
length - 001c
Nonresident-Name Table: offset - 00000105
length - 0016
Moveable Entry Points: 4
Alignment: 2 bytes
Flags: MULTIPLEDATA
WINDOWAPI
Additional Information: Contains a Fast-Load Area
Fast-Load Start: 00a0
Fast-Load Length: 11d0
Segment Table
Num Type offset - Length Alloc Flags
1 CODE 00000160 019b6 019b6 EXECUTEREAD, PRELOAD, NONCONFORMING, NOIOPL, relocs, (moveable), (nondiscardable), (nonshared)
2 DATA 00001bc0 00900 00900 READWRITE, NONSHARED, PRELOAD, NOEXPANDDOWN, NOIOPL, (moveable), (nondiscardable)
Resident-Name Table (Exported Functions)
Entry Table Index Name
0 foxw
Nonresident-Name Table (Exported Functions)
Entry Table Index Name
0 C:\dosdev\foxw.exe
Imported-Name Table (Link-Time Imports)
KERNEL
USER
Header Information
Signature: 5a4d
Last Page Size: 0080
Total Pages in File: 0001
Relocation Items: 0000
Paragraphs in Header: 0004
Minimum Extra Paragraphs: 0000
Maximum Extra Paragraphs: ffff
Initial Stack Segment: 0000
Initial Stack Pointer: 00b8
Complemented Checksum: 0000
Initial Instruction Pointer: 0000
Initial Code Segment: 0000
Relocation Table Offset: 0040
Overlay Number: 0000
Reserved: 0000 0000 0000 0000
0000 0000 0000 0000
0000 0000 0000 0000
0000 0000 0000 0000
Offset to New Header: 00000080
Memory Needed: 1K
I hope that helped??
Mel
Rick Bean
Now we are getting someplace! That description tells me it's a FoxPro for Windows .EXE! However, this won't tell us whether it's FPW 2.5 or FPW 2.6!
After, some further research, my different offset (00D1 vs. 0111) to determine if it's 2.5 or 2.6 is just plain wrong - the same program compiled in both versions causes these offsets to be the same. (Something else must be causing that offset change in some FPW .EXEs!) Yet there is something that causes the separate code files to look for either FOXW2500.ESL (or FOXW250A.ESL or FOXW250B.ESL depending on the patch level) or FOXW2600.ESL (no external difference between 2.6 and 2.6a!). <s>
Now your task is to locate one of these .ESL files on the "old" system and put that "next to" your .EXE!
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:D149B074-8ABF-4E82...@microsoft.com...
Rick Bean
WinZip allows you to span multiple floppies - and it's small enough to fit on a a single floppy! http://www.winzip.com/
Rick
"Mel" <anon...@discussions.microsoft.com> wrote in message news:3BBF42C2-4594-47D4...@microsoft.com...
>
>
>
> Rick!!
>
> Oh my goodness, we're getting somewhere!! I looked for the fox***.esl on the old system and there's FOXW2600.ESL on it!!
>
> Problem is I can't get it over to my laptop cuz the file is too large to copy onto a floppy disk(even tried zipping it up) and there's no internet set up on that old laptop (I mean really oollllddd laptop that was given to me by the client to try to figure out the problem). I'm going to see if they may have another old computer with that file so they can ftp me the file.
>
> Ohhhh I hope that solves everything!!!
>
> But it still puzzles me why they had foxpro 3.0 at their office...? Maybe it was never used, I don't know.
>
> I will let you know if getting that file solved the problem, I'm sure you'd want to know so you can move on! :)
>
> Thanks so much, Rick!!!
>
> Melissa
>
> ----- Rick Bean wrote: -----
>