Error 35: Unexpected Interrupt=000B

Meeting place for R&R customers and clients to share tips and ideas. Post your questions, messages or problems here.
Post Reply
Garnett
Posts: 3
Joined: Tue Oct 10, 2017 12:44 pm

Error 35: Unexpected Interrupt=000B

Post by Garnett » Tue Apr 02, 2002 8:04 am

I^m using using a program which was written in Paradox 4.5 and Report Writer 4 under windows 95. It worked fine until I moved it to a new machine. All the reports works except for 3. The reports are called from a Paradox script. The error I receive is:__Error[35]: Unexpected Interrupt=000B in RPRun.exe at 14E7:02B5 code=0344 ss=1687 ds=1687 es=1687 ax=0346 bx=7d7e cx=0346 dx=5400 sp=7d46 bp=7d58 si=7d89 di=4241.____Any clues on what is causing this and how to rectify it. All reports worked fine on the old machine and I have limited the new machine to 32meg RAM and partioned the drive as 1 gig.

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

=> Error 35: Unexpected Interrupt=000B

Post by kfleming » Tue Apr 02, 2002 8:52 am

Since we have not shipped this product for many years, my recall of this condition is reasonably vague other than it has to due with a problem using the protected mode runtime. Can you run these reports on the problem machine using RP.EXE?__Does the new machine have less memory than the old machine?____Kathleen__R&R Support

kfleming
Posts: 5795
Joined: Tue Oct 10, 2017 12:44 pm

=> Error 35: Unexpected Interrupt=000B

Post by kfleming » Tue Apr 02, 2002 8:38 pm

I found some old documentation that discusses starting paradox using the -emk and -extk switches.____It says:__We recommend that you set -emk to 0 and -extk to the amount of memory you want to reserve for paradox, leaving the balance for R&R.____For example your command line to start paradox might look like:__paradox -emk 0 -extk 2000____Maybe this will help?____Kathleen__R&R Support

Post Reply