Run-time Error R6003

[kittyshack]

Hi all,

Just wondering if anyone has a resolution for getting by this error message.

Just installed a new Maxtor 40 GB drive into a Compaq Presario 5204, disconnected the original drive (Seagate 4GB) and was about to load Win98 SE until I received this error message. I also install another 128 MB SD-Ram.
If anyone has any comments on this issue, I'd love to hear from you.

 

[lbpsfl]

message?

 

[biglar2002]

thread288-464614
How can I use clipper applications under Windows XP to avoid error message : "run-time error R6003 - integer divide by 0"?
Reponses Summarized
Take a look at Dave P's FAQs

http://www.davep.org/clipper/FAQ/

You should also check the CPU hogging FAQs
Your applications should compile with __wait.obj file.
Example:
Clipper myapp
blinker file myapp,__wait.obj



5.7 What is "runtime error R6003"?
FROM CLIPPER FAQ:

http://www.davep.org/clipper/FAQ/

The R6003 error occurs when you run a Clipper program on a machine that is 'too fast'. Part of the startup procedure in every executable is used to determine a value. That value is used in a timing loop. On very fast machines, the timing routine returns 0, causing an error in the program's initialization, since your software then fails with a divide by 0 error.
To fix this problem, there are two possibilities.
First, by the time that 5.3 was released, CA included the object that fixed the problem in that version. So, if you have 5.3, you need to link in __wait_4.obj to every executable you produce.
If you use Clipper 5.0-5.2e, there is another object, available from The Oasis. The file is named R6003FIX.ZIP, and is in the patch area. There are complete instructions included for it's use, but it is essentially the same as the 5.3 fix, just link it in on every executable you produce.

R6003fix.zip

http://www.the-oasis.net/ftpmaster.php3?content=ftppatch.htm

r6003fix.zip

http://www.the-oasis.net/files/patch/r6003fix.zip

Bytes: 3,634 Date: 1998-12-12
The enclosed object file __WAIT_B.OBJ is used to fix a problem with
Clipper applications terminating at start up with either an "R6003
divide by zero" message or no error message at all. This problem has
recently reared it's head with the advent of new advanced design
microprocessors. These new design CPUs run "software timing loops" so
rapidly that a software timing loop module which is part of Nantucket
Tools II and CA-Tools III cannot work as designed. Not all Tools
functions use the software timing loop, but it appears to be linked
into your application if you're using either the CTUS.OBJ or CTUSP.OBJ
extended drivers. A few people have reported this problem without
having CTUS.OBJ or CTUSP.OBJ linked in.
The two processors currently exhibiting this condition are the AMD K5
and Cyrix 6x86. As of this writing, AMD apparently has no "fix" of
their own, while Cyrix has a "fix" posted on their web site at

http://www.cyrix.com

. Their fix consists of an executable named
PIPELOOP.EXE that is run from the AUTOEXEC.BAT file and causes timing
loops to be slowed down. Another "fix" is to turn off the internal
cache, which will significantly degrade all performance. Please note
this problem is not caused by a defect in the CPUs.
Just add it to your link script ahead of the libraries and ahead of
the extended driver file, if used. PIPELOOP.EXE from Cyrix is no
longer needed. It's been tested on Clipper 5.2 and 5.3. It should work
on 5.01a as well, but no one has reported using it on that version.
There's no need to maintain a separate program version for Intel
processors. It works fine on all brands of CPUs. So far.
The file name itself isn't significant. It's just a new name to
differentiate it from earlier versions.