1) How do I see the directory where I have FoxPro?

msdos only can ever see imgmounted drives, so if you want to go that
way you'll need some msdos installation on a .img file (there should be
some hints on the guides forum i think).
Reguar mounts are not visible from msdos, feel free to complain to
microsoft but i doubt they'll update their dos.

2) How do I get this image to use a different autoexec.bat and config.sys?

I'm not aware that you can select any different autoexec/config pair as
once msdos boots, it'll use the ones from the boot partition/disk.

msdos only can ever see imgmounted drives, so if you want to go that way you'll need some msdos installation on a .img file (the […]
Show full quote

msdos only can ever see imgmounted drives, so if you want to go that
way you'll need some msdos installation on a .img file (there should be
some hints on the guides forum i think).
Reguar mounts are not visible from msdos, feel free to complain to
microsoft but i doubt they'll update their dos.

I don't understand. How do I boot MS-DOS under DosBox and still
be able to see my FoxPro application?

Ignore the above question. I found the guides message. I'll give that
a try, and come back when I get stuck 😀 But the following question
still remains valid - I think!

Do you think there is a possibility to get FoxPro to run under
DosBox without booting MS-DOS? Any idea what the magic settings
are, e.g., that correspond to the native MS-DOS settings:

dos=umb,high
devicehigh=himem.sys
devicehigh=emm386.exe

and:

dos=umb,high
devicehigh=himem.sys /int15=4800

Note: just plain "devicehigh=himem.sys" won't work - it has to
either have the int15 parameter or also load emm386.

and still be able to see my FoxPro application?

Well you can copy that app on the image disk before booting it.

Do you think there is a possibility to get FoxPro to run under
DosBox without booting MS-DOS?

Don't know, not much you can do besides playing with the ems/xms
settings in dosbox.conf, or using loadfix.
2.0 seems to be a rather old foxpro version, do you have any newer
one accessible? Or maybe there's an upgrade for 2.0?

It looks like the program requires EXTENDED memory instead of XMS memory.

I want to say that when you load himem.sys (without the INT15 switch) and EMM386.exe then extended memory is provided and your program is happy.

When you load Himem.sys with the INT15 switch and allocate 4800 meg of Extended memory (Himem by default supplies the newer XMS memory) then your program is happy.

AFAIK, DosBox only supplies XMS memory. Don't think it supports INT15 (unless you boot MS-DOS in DosBox).

if you disable both xms and ems then you have extended memory (int 15)

Mabye FoxPro requires a memory manager to be loaded?

I noticed that if I disabled XMS/EMS in dosbox.conf and then executed JEMMEX (Command: JEMMEX LOAD), then JEMM would actually load in DosBox.

JEMM Download: http://www.japheth.de/

JEMM is an EMM386 replacement.

I don't have FoxPro to test it out with.

Mabye FoxPro requires a memory manager to be loaded?

That's what ems/xms=true is for.
jemmex might of course check if another memory manager is present,
thus not work if you have ems or xms enabled in dosbox.

Jemmex doesn't find a page frame in dosbox. I tried it for getting megaem going, unsuccessfully..

Think the freedos emm386 (jemm386 is based on their sources)
worked for me, but don't remember if some parameter was needed.

Sorry for the very long delay in replying. Life happens
sometimes ...

I still have not been able to get Foxpro v2 to work in DosBox.
But I do have some more information:

To WD:

I do have a newer version of Foxpro (that runs well under XP),
but the foxpro application program that I need to run won't work
with it.

Here is the config.sys that works under plain DOS:

dos=umb,high
devicehigh=himem.sys
devicehigh=emm386.exe

When I run DosBox .72 with:

xms=true
ems=true
umb=true

And run foxpro:

foxr +x

The DosBox window just goes away.

If I set xms=false, ems=false, and then run foxr +x, the same thing
happens, DosBox window just goes away.

If I set xms=true, and ems=false, the same thing happens.

However (!) if I set xms=false, and ems=true, I get the
following:

I get a message: No extended memory available, using real memory

and then the following screen:

FoxPro/LAN 2.0 EXE Support Library (X)
(c) 1989-1992 Microsoft Corporation
Worldwide Edition
(Demand Paging Enabled)

Dos Extension Technology Copyright 1988-1990,
ERGO Computing, Inc. All Rights Reserved.

And then it crashes with "DOSBox DOS Emulator has encountered a
problem and needs to close. We are sorry for the inconvenience."

More info:

AppName: dosbox.exe AppVer: 0.72.0.0 ModName: dosbox.exe
ModVer: 0.72.0.0 Offset: 0000a6f3

As suggested by DosFreak, I tried running DosBox with xms=false,
ems=false, and then loading jemmex: jemmex load

This also immediately closes the DosBox window.

Any ideas what to try next?

Thanks!

Tried playing with the core=... setting?

A more desperate attempt would be to try older versions of DOSBox.

MiniMax wrote:

>Tried playing with the core=... setting?
>
>A more desperate attempt would be to try older versions of DOSBox.

Hmmm. This gave me the idea to try the latest CVS build that I
could find.

I downloaded dosbox_17.08.2008.exe and ran it, using xms=false,
ems=true.

Now Foxpro no longer crashes, but besides the "No extended memory
available, using real memory", after the signon screen, I get
"Insufficient memory.", which appears to be a Foxpro message.

Well, at least it doesn't crash.

But, just like 0.72, if I enable both xms and ems, or just enable
xms, when I run Foxpro, the DosBox window immediately closes.

Yup - latest CVS has some changes to the CPU emulation. Something about prefetch. Maybe changing to one of the new core-types will do even better?

Edit: See this thread:
Fifa International Soccer 1994, first fifa

xms=false +ems=true is indeed likely to result in no extended memory available as both the xms and the in15 pool are unavailable then.
Might be an interresting program to debug at one point then.

Qbix wrote:

>xms=false +ems=true is indeed likely to result in no extended
>memory available as both the xms and the in15 pool are
>unavailable then.
>
>Might be an interresting program to debug at one point then.

It would be great if I could somehow get it to work. What is the
next step? Should I download the DOSBox debugger referenced
here?

http://rapidshare.com/files/52433778/DOSBox0. … 2-installer.exe

Or is there a later one I should try?

What about trying MS Virtual PC, Bochs, or VirtualBox?

swaaye wrote:

>What about trying MS Virtual PC, Bochs, or VirtualBox?

I downloaded Virtual PC, and installed Windows 98 DOS (the same
thing my real machine that works runs).

I used the same autoexec.bat and config.sys that are on my real
machine, and used the same amount of memory that is on my real
machine.

Unfortunately, Foxpro crashes <sigh>.

There were some differences between the real and virtual machine,
that look like they may have something to do with the problem.
But I'm not sure how to reconcile them. Here they are, just in
case anyone has any ideas:

Booting message differences:

In the real machine:

Installed A20 handler number 1.

In the virtual machine

Installed A20 handler number 2.

mem message differences (under Memory Type):

In the real machine:

Reserved: 384k total 384k used 0k free

In the virtual machine

Reserved: 0k total 0k used 0k free

pmap (old Chris Dunford DOS mem-like utility) message differences
(under Expanded memory summary):

In the real machine:

Page frame segment: E000h

In the virtual machine

Page frame segment: D000h

I wonder if these differences are what is causing the problem?
Any ideas how I can make the two machines more alike?

Interestingly, both machines (the real and the virtual) have AMI
BIOS's - the real one dated 1996, and the virtual one dated 2006.

could this be a Y2K problem? Kinda doubt it, but who knows....

It sure sounds like a very picky app. I'm not sure what to suggest other than an even more thorough emulator such as Bochs perhaps.