FiveTech Software tech support forums

Dear Friends,

Some years ago Clipper apps failed with newer faster processors.
At that time a solution became available that solved the problem.
I beleive a kind of WAIT programme.
That was implemented in the Clipper programs and the problem was gone.

My question is, do we have a similar problem today and if so is there a new solution.

I have a cusomer that bought new P.C.'s with XP PRO and only two MS-DOS apps running from a server fail intermittently on the new P.C.'s.
Same programs work OK on the older PC's.

Any suggestion is welcomed.

Jules de Pierre

Hello!

Some suggestions:
1. Disable DEP:
http://www.sysinternals.com/Information/bootini.html
(Use /execute instead of /noexecute=OPTIN)

2. Disable hyper-threading in BIOS

3. If CPU has two cores, this might me helpful:
http://www.markwilson.co.uk/blog/2005/0 ... cation.htm
http://www.informit.com/articles/articl ... Num=2&rl=1

By default, the Windows operating systems set processes to run on all available processors. If you have multiple processors or one or more dual-core processors in your system, you can control the processor(s) on which an application runs.

http://www.hardforum.com/showthread.php?t=983781

4. Is your application running with administrator or limited user rights?

Cheers, Roman

Thanks Roman,
Very interesting but I did not see a problem related to a Clipper app.
Since Antonio is not responding I think that Clipper does not have this problem.

Questions:
What is NTDVM and DEP

Jules de Pierre

NTVDM is the Windows NT Virtual Dos Machine, a program that allows 16 bit apps to run under Windows NT-2000-XP.

EMG

2 steps to avoid runtime error for Clipper exe in high performance processor pc :

- link this obj : http://hyperupload.com/download/022a123 ... b.obj.html

- upgrade to Blinker v7.0

Hello!

http://h10025.www1.hp.com/ewfrf/wc/gene ... =c00223284

The Data Execution Prevention (DEP) feature in the Windows operating system is designed to help prevent damage from viruses and from other security threats. DEP works alone or with compatible microprocessors to mark some memory locations as "non-executable." If a program tries to run code from a protected location, DEP closes the program and displays a message.

Jules, are your two DOS apps working in Windows XP SP2 on older computers?

Regards, Roman

Dear Roman,

It are new PC's with WIN XP PRO Inclusive SP2
I do not have the processor specs yet.
But it are new computers.

Dear Who,
I included _Wair_B already in 1996.

I think I come to the conclusion that the problems my customer has is not because of Clipper apps.
I heard that they had frequently Corruption Errors on an index file.

I believe that that can only be a hardware probblem.


Dear Antonio,

Do you have any experience on problems with Clipper apps in XP


Thanks to all,

Jules de Pierre

Jules!

We have a DOS Clipper app running in Windows XP SP2 on several PC-s
with Pentium 6xx CPU-s without problems. They are linked with Blinker
(extended mode). Which version of Clipper is used in your case?
What linker? Are DBF-s located on server or on local disk?

If your Clipper app directly access hardware (like COM
ports), this might be a problem!
http://www.beyondlogic.org/porttalk/porttalk.htm
Maybe this thread can help:
http://forums.wugnet.com/NTVDM-100-CPU- ... 10387.html

Last three questions:
Is this pure Clipper app? Do you use Nanfor library?
How do you set FILES= and CLIPPER= ?

Regards, Roman

Jules,

We use just one Clipper app in msdos and works ok on XP

Go through the OPTEDIT.EXE commands and try to link your applicaiton
with protected mode linker EXOSPACE.

We have several applications compiled with Clipper 5.3b and linked with
EXOSPACE and subsequently using OPTEDIT.EXE commands to change
the behaviour of the Executable to suit to your requirements. They are
all working OK with latest hi-speed processors also without any problem.

- Ramesh Babu P

Dear collegues,

Thanks for your cooperation.
I am convinced now that my customer has no Ckipper XP PRO problem.
I used Blinker and Clipper 5.3b
Databases are on the server.
Files and Buffers are OK.

So I advised my customer to look at his installation of XP PRO workstations in a Windows 2000 server environment.
There is a rumour that that is the problem.

For me the case is closed.

Thanks everybody ofr your help.

Friendly regards,

Jules de Pierre

Hello!

Jules de Pierre wrote: So I advised my customer to look at his installation of XP PRO workstations in a Windows 2000 server environment.
There is a rumour that that is the problem.

In our case DBF-s are on Netware 4.2 server, which is more Clipper friendly. Anyhow, when dealing with Windows server environments, I use
this two utilities: NetSafe and RedrTest
http://www.datafastsoftware.com/download.htm
http://www.support.tabs3.com/main/R10200.htm

OT, but here is another link for Samba 3 and 2.2 servers:
http://www.drouillard.ca/Tips&Tricks/Samba/Oplocks.htm

Cheers, Roman

Jules de Pierre wrote:Dear Friends,

Some years ago Clipper apps failed with newer faster processors.
At that time a solution became available that solved the problem.
I beleive a kind of WAIT programme.
That was implemented in the Clipper programs and the problem was gone.

My question is, do we have a similar problem today and if so is there a new solution.

I have a cusomer that bought new P.C.'s with XP PRO and only two MS-DOS apps running from a server fail intermittently on the new P.C.'s.
Same programs work OK on the older PC's.

Any suggestion is welcomed.

Jules de Pierre

See my posts very useful for wait state (CPU time used by Clipper
with Fivewin) here :
http://fivetechsoft.com/forums/viewtopic.php?t=1103

If you want reduce your 100 % CPU time to 3 % !

Regards,