Foxpro Dos 2.6 and Windows XP - Lockups

#1

Hi all,

I wonder if you can help.

We have an in house App on a domain which is Foxpro for Dos 2.6

We have not had any problems in Windows NT and 2000. In one place we
have not had any problems in Windows XP.

It used to be one PC now it appears to be two. HP Compaq d530s Small
Form Factor PCs, with Windows XP SP2 on a Windows 2000 Domain, we also
use Network Associates Virus Scan Enterprise 8.

Now, these PCs will run perfectly ok, but the actual App it self will
completely freeze (Windows says 'Running' in the task manager).

Is this known to anyone ? It doesn't seem to affect a the HP DC5000
PCs as we have a whole office which seems un-effected.

Any ideas would be great.

Many thanks,

Karl.

#2

karl.oldman (AT) gmail (DOT) com wrote:

Quote:

Hi all,

I wonder if you can help.

We have an in house App on a domain which is Foxpro for Dos 2.6

We have not had any problems in Windows NT and 2000. In one place we
have not had any problems in Windows XP.

It used to be one PC now it appears to be two. HP Compaq d530s Small
Form Factor PCs, with Windows XP SP2 on a Windows 2000 Domain, we also
use Network Associates Virus Scan Enterprise 8.

Now, these PCs will run perfectly ok, but the actual App it self will
completely freeze (Windows says 'Running' in the task manager).

Does this happen when you leave the application alone (possibly in the
background) for some time? I have seen this but unfortunately never
found the cure. I spoke to my colleague here who says that Windows 2000
compatibility mode seems to help a bit.

We had until quite recently many 100s of XP PCs running Fox 2.6
applications without problems. It only seemed to occur occasionaly
here. It's never happened on my Laptop and I generally have Fox for DOS
open for at least a few hours a day (the legacy stuff never quite goes
away :-).

--
Paul

#3

Hi Paull,

Thanks for your reply. And yes I believe it is when the app is idling
for a short time.

Interestingly enough I had one of the PCs back for a rebuild, we are
running tests now. I left the app idle and went for a cup of water,
came back and it had frozen.

Its strange because we have an office of around 17 PCs with XP, but
they don't lockup (they are a different model).

Perhaps I'll run some more tests.

It has our FoxPro developers baffled !

Cheers.
Karl.
Paul wrote:

Quote:

karl.oldman (AT) gmail (DOT) com wrote:
Hi all,

I wonder if you can help.

We have an in house App on a domain which is Foxpro for Dos 2.6

We have not had any problems in Windows NT and 2000. In one place
we
have not had any problems in Windows XP.

It used to be one PC now it appears to be two. HP Compaq d530s
Small
Form Factor PCs, with Windows XP SP2 on a Windows 2000 Domain, we
also
use Network Associates Virus Scan Enterprise 8.

Now, these PCs will run perfectly ok, but the actual App it self
will
completely freeze (Windows says 'Running' in the task manager).

Does this happen when you leave the application alone (possibly in
the
background) for some time? I have seen this but unfortunately never
found the cure. I spoke to my colleague here who says that Windows
2000
compatibility mode seems to help a bit.

We had until quite recently many 100s of XP PCs running Fox 2.6
applications without problems. It only seemed to occur occasionaly
here. It's never happened on my Laptop and I generally have Fox for
DOS
open for at least a few hours a day (the legacy stuff never quite
goes
away :-).

--
Paul

#4

Hi Karl,

karl.oldman (AT) gmail (DOT) com wrote:

Quote:

Hi Paull,

Thanks for your reply. And yes I believe it is when the app is idling
for a short time.

Interestingly enough I had one of the PCs back for a rebuild, we are
running tests now. I left the app idle and went for a cup of water,
came back and it had frozen.

Its strange because we have an office of around 17 PCs with XP, but
they don't lockup (they are a different model).

Perhaps I'll run some more tests.

Try running in Windows 2000 compatibility mode - it might help.

Paul

Quote:

It has our FoxPro developers baffled !

Cheers.
Karl.
Paul wrote:

karl.oldman (AT) gmail (DOT) com wrote:

Hi all,

I wonder if you can help.

We have an in house App on a domain which is Foxpro for Dos 2.6

We have not had any problems in Windows NT and 2000. In one place

we

have not had any problems in Windows XP.

It used to be one PC now it appears to be two. HP Compaq d530s

Small

Form Factor PCs, with Windows XP SP2 on a Windows 2000 Domain, we

also

use Network Associates Virus Scan Enterprise 8.

Now, these PCs will run perfectly ok, but the actual App it self

will

completely freeze (Windows says 'Running' in the task manager).

Does this happen when you leave the application alone (possibly in

the

background) for some time? I have seen this but unfortunately never
found the cure. I spoke to my colleague here who says that Windows

2000

compatibility mode seems to help a bit.

We had until quite recently many 100s of XP PCs running Fox 2.6
applications without problems. It only seemed to occur occasionaly
here. It's never happened on my Laptop and I generally have Fox for

DOS

open for at least a few hours a day (the legacy stuff never quite

goes

away :-).

--
Paul

--
Paul

#5

On Fri, 11 Feb 2005 10:12:01 +0000 in comp.databases.xbase.fox,
Paul <paul.hill@[NOSPAM]clara.co.uk> wrote:

Quote:

Does this happen when you leave the application alone (possibly in the
background) for some time? I have seen this but unfortunately never
found the cure. I spoke to my colleague here who says that Windows 2000
compatibility mode seems to help a bit.

one thing that has helped with our old legacy dBASE for DOS 5.0

programs is to set the DOS session to turn off the screen saver
(my boss prefers to run the DOS session full screen, and most
others in the office except me do, too).

i've noticed that DOS sessions under XP seem to grab most of the
computer's cycles, unlike well behaved windoze programs. if
there's a dBASE-for-DOS session active, it takes a new windoze
program a loooong time to start, even on my 3.2 ghz machine with
a gigabyte of RAM.

heh. while he's on vacation i get to try to run his horrible
dBASE spaghetti code under Foxpro 7.0 to see how many changes
will be needed to convert. can't get new computers with win98
any more, so he's finally forced to convert.

To send an email, remove the nospam...

#6

On Thu, 17 Feb 2005 14:24:19 -0900, Dennis P. Harris
<wright.jnumgr (AT) alaska (DOT) nospam.com> wrote:

[ ... ]

Quote:

i've noticed that DOS sessions under XP seem to grab most of the
computer's cycles, unlike well behaved windoze programs. if
there's a dBASE-for-DOS session active, it takes a new windoze
program a loooong time to start, even on my 3.2 ghz machine with
a gigabyte of RAM.

Tame (www.tamedos.com) is your friend - it is not that DOS session or
DOS program grabs all cycles, it is dumb XP that gives it ;-)

--
[ When replying, remove *'s from address ]
Alexandre Peshansky, Systems Manager, RUH, NY

#7

Still no joy.

Its 2 out of about 20 WinXP machines.

HP don't really have anything with regards to the D530 Small Form
Factor.

#8

karl.oldman (AT) gmail (DOT) com wrote:

Quote:

Still no joy.

Its 2 out of about 20 WinXP machines.

HP don't really have anything with regards to the D530 Small Form
Factor.

Upgrade to Foxpro 2.6 for Windows? If you can find it...

--
Paul

#9

Try the .pif mouse 'exclusive' setting?

I've long had FPDos2.6 locking up under XP on my laptop. It seems to be
associated with mouse activity (dragging browse windows etc) -- so after
experimenting with various .pif settings I am currently running with the
mouse running in 'exclusive mode' (foxprof.pif:misc tab). So far - this
is this morning only - so good! (and other apps seem to work fine with the
mouse too).

cheers

#10

Try the .pif mouse 'exclusive' setting?

I've long had FPDos2.6 locking up under XP on my laptop. It seems to be
associated with mouse activity (dragging browse windows etc) -- so after
experimenting with various .pif settings I am currently running with the
mouse running in 'exclusive mode' (foxprof.pif:misc tab). So far - this
is this morning only - so good! (and other apps seem to work fine with the
mouse too).

cheers