Foxpro for DOS 2.0 Running Foxprox Under Windows XP

[BudgieMK]

I have an old (circa 1994) application written in FPD2.0 that I want to access/run. Can anyone help me with setting up the Windows XP shortcut property settings, config.nt, autoexec.nt and config.fp files to allow Foxprox to run.

I can get Foxpro to run but need the extended version because of the file sizes involved in the application.

I keep getting incompatible memory manager messages. I have tried most memory settings but none work. IT has been a while since I last used Foxpro and tried to set up the environment. Here is what I have at the moment.

CURRENT CONFIG.NT FILE

DOSONLY
ECHOCONFIG
dos=high, umb
device=%SystemRoot%\system32\himem.sys
FILES=99
LASTDRIVE=Z

CURRENT AUTOEXEC.NT FILE

@echo off
REM Install CD ROM extensions
lh %SystemRoot%\system32\mscdexnt.exe
REM Install network redirector (load before dosx.exe)
lh %SystemRoot%\system32\redir
REM Install DPMI support
lh %SystemRoot%\system32\dosx

CURRENT CONFIG.FP FILE

*!c:\vibra16\play.exe CD /T:1
DISPLAY = VGA25
DOSMEM = OFF
MVCOUNT = 1000
TIME = 1
_FOXDOC = ""
_FOXGRAPH = ""
*RESOURCE = c:\data\database\FOX2USER.DBF
*EDITWORK = c:\temp\
*SORTWORK = c:\temp\
*PROGWORK = c:\temp\
*TMPFILES = c:\temp\
*PDSETUP = "HP3P77CGL"
*COMMAND = DO c:\data\database\tools\mfkstart.prg
*COMMAND = DO c:\data\database\productn\network\focus.app
* added MEMLIMIT re possible problems with too much memory - tek-tips.com
MEMLIMIT=60,2048,16384

Older config data remmed out for now ...

Thanks for any help offered

Cheers

Martyn (Budgie)
UK

 

[bobmpalmer]

Hi Martyn

I have a 2.5 app running on 2K and XP so if it helps here are some snippets from my stuff.

CONFIG.NT yours looks fine
I have no changes in my AUTOEXEC.NT

CONFIG.FP
Similar to yours except:-
EMS=ON
MVARSIZ=64
MVCOUNT=640
FILES=99
BLOCKSIZE=64

The .BAT file I use to launch the .exe simply sets up the path and calls the .exe But fundamentaly in the properties of the exe under memory
Protected,Expanded,Extended and Initial are set to Auto and if I remember correctly NT systems set EMS to None by default!



Bob Palmer

http://www.resisystems.co.uk

The most common solution is H2O!

 

[vinczej]

See the topic "Invalid database number"

( Start with "program.exe +x" )

 

[BudgieMK]

Bob,

I think that with EMS SET ON in config.fp you can only run foxpro not foxprox. Perhaps this is the version you are running?

I have tried most memory settings but to no avail. It certainly worked under Win98 with 8192K in the XMS setting and EMS set to none.

P.S. I checked out foxpro's response by running the fox.exe with the -v switch which validates the version which will run.

My problem is in setting up the appropriate DOS environment to run foxprox.

Vinczej,

I could not see what you were suggesting. The search revealed a posting on database file headings which has no bearing on my problem. Is this what you intended?

Cheers

Martyn

 

[rob444]

thread182-54966 is not referring to a database header.
Have another look.

I use the following config.fp witn foxprox and xp pro sp2

CATMAN=OFF
talk=off
echo=off
date=italian
bell=off
century=on
mvar=1200
F10="QUIT;"
codepage=850

Rob.

 

[bobmpalmer]

The APP we run is compiled in FoxPro 2.5b (x) using the FOXDX25B.ESL Library.
Changing the EMS setting to OFF makes no difference with our APP I also tried the settings you quote for yr config.fp file and our app just runs. If I change the XMS setting on the exe and exclude the MEMLIMIT the app gives me an insufficient Memory error, likewise if I remove the MVCOUNT in the Config.fp otherwise it seems OK, so I'm a bit out of ideas. Sorry. Do I gather from your second post your having problems running fox.exe itself not just a stand alone app created in foxpro?


Bob Palmer

http://www.resisystems.co.uk

The most common solution is H2O!

 

[BudgieMK]

Rob444

I will take a look at the thread you mentioned.

You said that you are running foxprox under XP pro SP2. What version are you running? What settings have you used on the shortcut memory properties and autoexec and config files? Sounds as if you have cracked it ...

PS what does CATMAN=OFF do - cannot find this setting in my language reference manual.

Bob

As a first step I am simply trying to launch foxprox 2.0. Once in I can then play around with the App. I have all the code and could edit/recompile it as necessary.

P.S. I can run foxpro 2.0 OK.

Regards

Martyn

 

[bobmpalmer]

hmm, silly one this but just browsing through my old bible by Slater and Arnott first thing is, no spaces around the "=" sign in the config.fp file i.e MVCOUNT = 1000 shld be MVCOUNT=1000 or was that just a typo?
Heres the extract on starting up Fox:-

Loader Switches

You can force or prevent the execution of certain FoxPro versions by including optional command line switches after the loader name. Separate the loader name and the first switch with a space. More than one switch can be included -- be sure to separate multiple switches with spaces.

The following table lists the names of the four loaders, the versions of FoxPro that they invoke, and the command line switches that can be included.

File Loads Switches
FOX.EXE All +R Load Runtime versions
versions -R Don't load Runtime version
+X Load Extended version
-X Don't load Extended version
/? Display help text
-Y Set MS-DOS error level
0 = load Standard
1 = load Extended
-M <n> with <n> K free, run Extended version (default = 2000)
FOXR.EXE FoxPro +X Load Extended version
Runtime
-X Don't load Extended version
/? Display help text

You can also see a listing of switches available for a loader by typing the loader's name at the MS-DOS prompt followed by a space, /?, and then press Enter.

To force a version to execute, include + before the switch. To prevent a version from executing, include - before the switch.

Loader Examples

FOX.EXE can be used to execute any FoxPro version. In this MS-DOS command line example it is used without any of the optional switches to run the most advanced version of FoxPro available:

FOX

The following example uses /? to display the switches that are available for the FOX.EXE loader:

FOX /?

In this example, FOX.EXE is used with the +X switch to force the Extended version of FoxPro to run:

FOX +X

This example uses the runtime loader FOXR.EXE to run the Standard version of runtime FoxPro:

FOXR -X

Other FoxPro MS-DOS command line switches (-C, -E, -K and -T) can be combined with the loader switches. After the switches, you can also include the name of a FoxPro program to execute after FoxPro is loaded. The following example uses the loader FOX.EXE to run the Standard version of FoxPro, suppress the sign-on screen (-T option) and run the program ORGANIZE:

FOX -X -T ORGANIZE

Specifying Loader Switches
with FOXPROSWX

Switches can be specified with the MS-DOS environment variable named FOXPROSWX. You can create this MS-DOS environment variable with the DOS SET command.

If FOXPROSWX exists, the loader uses the switches it contains. Other FoxPro MS-DOS command line switches (-C, -E, -K and -T) can be combined with the loader switches in FOXPROSWX. You can also include the name of a FoxPro program to execute after FoxPro is loaded. Switches can be specified using both FOXPROSWX and command line arguments. If a conflict exists, the command line arguments prevail.

In the following example, FOXPROSWX is created at the MS-DOS prompt and the switches +X -T (Extended version, suppress the sign-on screen) are stored in it. The loader FOX.EXE is executed. Since switches are not included after the loader, the loader uses the switches in FOXPROSWX.

SET FOXPROSWX= +X -T
FOX

The Extended version of FoxPro is invoked and the sign-on screen is suppressed.
Do not include spaces between FOXPROSWX and the equal sign.




Bob Palmer

http://www.resisystems.co.uk

The most common solution is H2O!

 

[BudgieMK]

Hi Bob,
I have a well thumbed copy of Salter and Arnott too!
Re systax I will just check that as I just copied it using Notepad. Should be fine though.
Running fox +x brings up the message incompatible memory manager.
Any more ideas?
CHeers
Martyn

 

[bobmpalmer]

Aha!!

Microsoft KB article:-
If you run version 2.0 or 2.5 of Microsoft FoxPro for MS-DOS in extended mode with MS-DOS 6.x, you may receive an error message stating that the memory manager is incompatible.
WORKAROUND
To work around this problem, do one of the following:


Edit your CONFIG.SYS file to add the RAM parameter to the command for EMM386.EXE and remove the NOEMS parameter. For example: device=c:\dos\emm386.exe ram
-or-


Run MemMaker. When you are asked if you use any programs that need expanded memory, set the option to "Yes."
This problem does not occur if you are running FoxPro 2.0 for MS-DOS in standard mode, FoxPro for MS-DOS 2.5 in any mode, or FoxPro for Windows.

Bob Palmer

http://www.resisystems.co.uk

The most common solution is H2O!

 

[bobmpalmer]

I realise thats for DOS but I seem to recall that when I first configured a win 2K machine this was a problem and on the properties of foxprox I set EMS to None and xms to 0 and it worked. Worth a shot? !!

Bob Palmer

http://www.resisystems.co.uk

The most common solution is H2O!

 

[rob444]

Martyn,

Version 2.6a and the desktop link has all default options, no modifications there.

Rob.

 

[rob444]

Additional:

Catman is the catalog manager of 2.6
I only run foxprox the 386 version of foxpro.

Rob.