Help w/ DOS foxbase app--won't start

Help. I am trying to get a program written in DOS foxbase about 6-7
years ago to start. It seems to start, but then I get a message that
says "Preparing files ... Please be patient"

Then it drops to a dos prompt. No other messages. I cannot get it to
do anything. The most puzzling part of this is that this program works
fine on an old computer running W98. That computer boots to dos and
then this legacy foxbase ap is used. When I copied all of the files
from that old computer to a new one, it did not work and is doing as I
described above.

I'm not sure this matters, but the new computer is using VirtualPC on
XPPro. The virtualPC boots to dos and only loads w98 when asked.

I duplicated the config.sys and autoexec.bat settings. I cannot think
of anything else.

Any help would be much appreciated.

PS: if you email an answer, use rob@drrws.com as the adr.

Thanks

Dan
Fri Sep 17 15:41:20 CDT 2004

That's not a Foxbase message, so you're getting at least far enough in to
have some code running.

Not MUCH help, I know, but it isn't failing because Foxbase isn't running.
Something inside the app is failing.

Is there any sort of error log?

Dan



Sam K wrote:
> Help. I am trying to get a program written in DOS foxbase about 6-7
> years ago to start. It seems to start, but then I get a message that
> says "Preparing files ... Please be patient"
>
> Then it drops to a dos prompt. No other messages. I cannot get it to
> do anything. The most puzzling part of this is that this program
> works fine on an old computer running W98. That computer boots to
> dos and then this legacy foxbase ap is used. When I copied all of
> the files from that old computer to a new one, it did not work and is
> doing as I described above.
>
> I'm not sure this matters, but the new computer is using VirtualPC on
> XPPro. The virtualPC boots to dos and only loads w98 when asked.
>
> I duplicated the config.sys and autoexec.bat settings. I cannot think
> of anything else.
>
> Any help would be much appreciated.
>
> PS: if you email an answer, use rob@drrws.com as the adr.
>
> Thanks

Sam
Fri Sep 17 15:51:00 CDT 2004

Not that I can find.

> That's not a Foxbase message, so you're getting at least far enough in to
> have some code running.
>
> Not MUCH help, I know, but it isn't failing because Foxbase isn't running.
> Something inside the app is failing.
>
> Is there any sort of error log?
>
> Dan
>
>
>
> Sam K wrote:
> > Help. I am trying to get a program written in DOS foxbase about 6-7
> > years ago to start. It seems to start, but then I get a message that
> > says "Preparing files ... Please be patient"
> >
> > Then it drops to a dos prompt. No other messages. I cannot get it to
> > do anything. The most puzzling part of this is that this program
> > works fine on an old computer running W98. That computer boots to
> > dos and then this legacy foxbase ap is used. When I copied all of
> > the files from that old computer to a new one, it did not work and is
> > doing as I described above.
> >
> > I'm not sure this matters, but the new computer is using VirtualPC on
> > XPPro. The virtualPC boots to dos and only loads w98 when asked.
> >
> > I duplicated the config.sys and autoexec.bat settings. I cannot think
> > of anything else.
> >
> > Any help would be much appreciated.
> >
> > PS: if you email an answer, use rob@drrws.com as the adr.
> >
> > Thanks
>
>
>

Leemi
Fri Sep 17 16:37:52 CDT 2004

Hi Sam:

This might be a manifestation of a problem we used to see if with FoxPro
for DOS apps running on NT 4.0. FoxPro 2.x for DOS would simply exit if
your code was in a tight loop and trying to monopolize the processor.

Here are is some more info:

If a FoxPro 2.6a for MS-DOS application executes a looping program
structure, Windows NT 4.0 terminates the FoxPro application without
warning. No error message or other information appears on the screen. This
happens both to FoxPro for MS-DOS executable files and programs running in
the development version of the product. The behavior also occurs on
machines upgraded to Service Pack 1 and 2.

You must add a new value to the Windows NT 4.0 registry. Under the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Wow key, add a new
value, DisableVme, by following the steps listed below:

1. Start Registry Editor (Regedt32) and go to the following subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Wow

2. From the Edit menu, select Add Value.

3. Enter the following Value name:


DisableVme

4. In the Add Value dialog box, make sure the Date Type is REG_SZ and click
OK.

5. Enter the following in the String Editor dialog box:

1

6. Shut down Windows NT, turn off the computer's power and then restart the
computer and boot into Windows NT.


I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here: http://msdn.microsoft.com/vfoxpro/

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003




>Not that I can find.

> That's not a Foxbase message, so you're getting at least far enough in to
> have some code running.
>
> Not MUCH help, I know, but it isn't failing because Foxbase isn't running.
> Something inside the app is failing.
>
> Is there any sort of error log?
>
> Dan
>
>
>
> Sam K wrote:
> > Help. I am trying to get a program written in DOS foxbase about 6-7
> > years ago to start. It seems to start, but then I get a message that
> > says "Preparing files ... Please be patient"
> >
> > Then it drops to a dos prompt. No other messages. I cannot get it to
> > do anything. The most puzzling part of this is that this program
> > works fine on an old computer running W98. That computer boots to
> > dos and then this legacy foxbase ap is used. When I copied all of
> > the files from that old computer to a new one, it did not work and is
> > doing as I described above.
> >
> > I'm not sure this matters, but the new computer is using VirtualPC on
> > XPPro. The virtualPC boots to dos and only loads w98 when asked.
> >
> > I duplicated the config.sys and autoexec.bat settings. I cannot think
> > of anything else.
> >
> > Any help would be much appreciated.
> >
> > PS: if you email an answer, use rob@drrws.com as the adr.
> >
> > Thanks

R
Sat Sep 18 06:22:15 CDT 2004

There are following possible cause for this behaviour :

1. Developer has put some kind of lock on hard disk no. etc. so that when
it can't find correct hard disk serial no., it hangs.

If this is the case than you should contact software developer.

2. Index files are corrupt : Try deleting IDX or CDX files and re creating
it.

3. Memory problem : Some times when EMM386 is not loaded than this type of
behaviour can occur.


"Sam K" <almasa3@optonline.net> wrote in message
news:MPG.1bb51851b756da26989681@news.optonline.net...
> Not that I can find.
>
> > That's not a Foxbase message, so you're getting at least far enough in
to
> > have some code running.
> >
> > Not MUCH help, I know, but it isn't failing because Foxbase isn't
running.
> > Something inside the app is failing.
> >
> > Is there any sort of error log?
> >
> > Dan
> >
> >
> >
> > Sam K wrote:
> > > Help. I am trying to get a program written in DOS foxbase about 6-7
> > > years ago to start. It seems to start, but then I get a message that
> > > says "Preparing files ... Please be patient"
> > >
> > > Then it drops to a dos prompt. No other messages. I cannot get it to
> > > do anything. The most puzzling part of this is that this program
> > > works fine on an old computer running W98. That computer boots to
> > > dos and then this legacy foxbase ap is used. When I copied all of
> > > the files from that old computer to a new one, it did not work and is
> > > doing as I described above.
> > >
> > > I'm not sure this matters, but the new computer is using VirtualPC on
> > > XPPro. The virtualPC boots to dos and only loads w98 when asked.
> > >
> > > I duplicated the config.sys and autoexec.bat settings. I cannot think
> > > of anything else.
> > >
> > > Any help would be much appreciated.
> > >
> > > PS: if you email an answer, use rob@drrws.com as the adr.
> > >
> > > Thanks
> >
> >
> >

Rob
Sat Sep 18 10:43:17 CDT 2004

But this code is being run under VirtualPC, not Windows directly. The
VPC window is set so that W98 does not start immediately. We use the
DOS environment to try to run this code. So this cannot be a registry
issue.

I would be interested in hearing another suggestion.

Thanks for answering



> This might be a manifestation of a problem we used to see if with FoxPro
> for DOS apps running on NT 4.0. FoxPro 2.x for DOS would simply exit if
> your code was in a tight loop and trying to monopolize the processor.
>
> Here are is some more info:
>
> If a FoxPro 2.6a for MS-DOS application executes a looping program
> structure, Windows NT 4.0 terminates the FoxPro application without
> warning. No error message or other information appears on the screen. This
> happens both to FoxPro for MS-DOS executable files and programs running in
> the development version of the product. The behavior also occurs on
> machines upgraded to Service Pack 1 and 2.
>
> You must add a new value to the Windows NT 4.0 registry. Under the
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Wow key, add a new
> value, DisableVme, by following the steps listed below:
>
> 1. Start Registry Editor (Regedt32) and go to the following subkey:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Wow
>
> 2. From the Edit menu, select Add Value.
>
> 3. Enter the following Value name:
>
>
> DisableVme
>
> 4. In the Add Value dialog box, make sure the Date Type is REG_SZ and click
> OK.
>
> 5. Enter the following in the String Editor dialog box:
>
> 1
>
> 6. Shut down Windows NT, turn off the computer's power and then restart the
> computer and boot into Windows NT.
>
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 Public Beta Now Available!! --*

Rob
Sat Sep 18 10:45:28 CDT 2004

I am a little rusty on the params of EMM386. What is the startup line
for this. Is it in config.sys or autoexec.bat? It's been so long since
I used it.

Thanks for answering

> There are following possible cause for this behaviour :
>
> 1. Developer has put some kind of lock on hard disk no. etc. so that when
> it can't find correct hard disk serial no., it hangs.
>
> If this is the case than you should contact software developer.
>
> 2. Index files are corrupt : Try deleting IDX or CDX files and re creating
> it.
>
> 3. Memory problem : Some times when EMM386 is not loaded than this type of
> behaviour can occur.
>
>
> "Sam K" <almasa3@optonline.net> wrote in message
> news:MPG.1bb51851b756da26989681@news.optonline.net...
> > Not that I can find.
> >
> > > That's not a Foxbase message, so you're getting at least far enough in
> to
> > > have some code running.
> > >
> > > Not MUCH help, I know, but it isn't failing because Foxbase isn't
> running.
> > > Something inside the app is failing.
> > >
> > > Is there any sort of error log?
> > >
> > > Dan
> > >
> > >
> > >
> > > Sam K wrote:
> > > > Help. I am trying to get a program written in DOS foxbase about 6-7
> > > > years ago to start. It seems to start, but then I get a message that
> > > > says "Preparing files ... Please be patient"
> > > >
> > > > Then it drops to a dos prompt. No other messages. I cannot get it to
> > > > do anything. The most puzzling part of this is that this program
> > > > works fine on an old computer running W98. That computer boots to
> > > > dos and then this legacy foxbase ap is used. When I copied all of
> > > > the files from that old computer to a new one, it did not work and is
> > > > doing as I described above.
> > > >
> > > > I'm not sure this matters, but the new computer is using VirtualPC on
> > > > XPPro. The virtualPC boots to dos and only loads w98 when asked.
> > > >
> > > > I duplicated the config.sys and autoexec.bat settings. I cannot think
> > > > of anything else.
> > > >

Bill
Mon Sep 20 06:51:09 CDT 2004

Make sure you copied any hidden (attrib +h) files that might be part of the
app.

Look for obscure files/folders that seem to belong to nothing...they may be
some sort of software key.

Did the original run on a networked PC?. It may be looking for a specific
drive mapping.

Is source code available? That would be the biggest help.

--
Bill Browne
www.edgefinderstudios.com


"Dan Freeman" <spam@microsoft.com> wrote in message
news:upA#xaPnEHA.3968@TK2MSFTNGP11.phx.gbl...
> That's not a Foxbase message, so you're getting at least far enough in to
> have some code running.
>
> Not MUCH help, I know, but it isn't failing because Foxbase isn't running.
> Something inside the app is failing.
>
> Is there any sort of error log?
>
> Dan
>
>
>
> Sam K wrote:
> > Help. I am trying to get a program written in DOS foxbase about 6-7
> > years ago to start. It seems to start, but then I get a message that
> > says "Preparing files ... Please be patient"
> >
> > Then it drops to a dos prompt. No other messages. I cannot get it to
> > do anything. The most puzzling part of this is that this program
> > works fine on an old computer running W98. That computer boots to
> > dos and then this legacy foxbase ap is used. When I copied all of
> > the files from that old computer to a new one, it did not work and is
> > doing as I described above.
> >
> > I'm not sure this matters, but the new computer is using VirtualPC on
> > XPPro. The virtualPC boots to dos and only loads w98 when asked.
> >
> > I duplicated the config.sys and autoexec.bat settings. I cannot think
> > of anything else.
> >
> > Any help would be much appreciated.
> >
> > PS: if you email an answer, use rob@drrws.com as the adr.
> >
> > Thanks
>
>

R
Wed Sep 22 00:32:05 CDT 2004

In config.sys write
device = c:\windows\emm386.exe
dos=high,umb

"Rob Solomon" <agent@drrob1.com> wrote in message
news:MPG.1bb622233fdb67f3989686@news20.forteinc.com...
> I am a little rusty on the params of EMM386. What is the startup line
> for this. Is it in config.sys or autoexec.bat? It's been so long since
> I used it.
>
> Thanks for answering
>
> > There are following possible cause for this behaviour :
> >
> > 1. Developer has put some kind of lock on hard disk no. etc. so that
when
> > it can't find correct hard disk serial no., it hangs.
> >
> > If this is the case than you should contact software developer.
> >
> > 2. Index files are corrupt : Try deleting IDX or CDX files and re
creating
> > it.
> >
> > 3. Memory problem : Some times when EMM386 is not loaded than this type
of
> > behaviour can occur.
> >
> >
> > "Sam K" <almasa3@optonline.net> wrote in message
> > news:MPG.1bb51851b756da26989681@news.optonline.net...
> > > Not that I can find.
> > >
> > > > That's not a Foxbase message, so you're getting at least far enough
in
> > to
> > > > have some code running.
> > > >
> > > > Not MUCH help, I know, but it isn't failing because Foxbase isn't
> > running.
> > > > Something inside the app is failing.
> > > >
> > > > Is there any sort of error log?
> > > >
> > > > Dan
> > > >
> > > >
> > > >
> > > > Sam K wrote:
> > > > > Help. I am trying to get a program written in DOS foxbase about
6-7
> > > > > years ago to start. It seems to start, but then I get a message
that
> > > > > says "Preparing files ... Please be patient"
> > > > >
> > > > > Then it drops to a dos prompt. No other messages. I cannot get
it to
> > > > > do anything. The most puzzling part of this is that this program
> > > > > works fine on an old computer running W98. That computer boots to
> > > > > dos and then this legacy foxbase ap is used. When I copied all of
> > > > > the files from that old computer to a new one, it did not work and
is
> > > > > doing as I described above.
> > > > >
> > > > > I'm not sure this matters, but the new computer is using VirtualPC
on
> > > > > XPPro. The virtualPC boots to dos and only loads w98 when asked.
> > > > >
> > > > > I duplicated the config.sys and autoexec.bat settings. I cannot
think
> > > > > of anything else.
> > > > >