Blinker Executable Clipper

clipper

    Sponsored Links

    Next

  • 1. Vista can now do full-screen terminal
    On Wed, 23 May 2007 18:48:52 +0200, Norman Perelson wrote: > I installed Windows Vista Home Basic on a new computer today. Because this > was my first hands-on experiance with the operating system that 'everyone' > reported cannot switch to full screen textual mode, the first thing I did > was load one of my old Clipper programs and press Alt-Enter to see what > would happen. Surprise! It switched to full screen mode. I tried several > other programs, including Microsoft's 'Command Prompt' and an Xbase++ 1.82 > 'VIO' program, and they all behaved perfectly - switching to full-screen > and back again with Alt-Enter. > > Thank you Microsoft. Now if you would just stop decorating the desktop with > dumb widgets (who needs another clock or a miniature photo album), and stop > inventing new names for old features (for example 'My Computer' is now > called 'Computer', and desktop 'Properties' bacame 'Preferences'), I might > even like Vista. It has nothing to do with vista but with the video driver. What graphics card this PC has and what driver you use? Regards Mike Evans
  • 2. CPU hogging (again!)
    Hi.. I have an old clipper 5.2 app that I use only occasionally. It was hogging CPU. So I put in some code like this: ft_onIdle( { || ft_iamidle(30, .T.) } ) It worked like magic. NTVDM CPU utilisation dropped to around 25%. Then, to deal with a non-clipper DOS app which was hogging the CPU, I installed a trial of TameDOS, which would work for about 5 minutes and then lock cmd.exe altogether. So I decided to live with that one and remove TameDOS. The problem is that, now, my clipper 5.2 app which was working prior to the TameDOS eval, (with the help of ft_onIdle & ft_iamidle from NFPAT1A), now hogs 100% of the CPU ... regardless of the intensity parameter passed to ft_iamidle .. a range of values from 1 to 100 .. the app now hogs the CPU. I'm running XP SP2. Has anyone encountered this before? Any suggestions appreciated! Thanks Richard
  • 3. harbour and ADS from clipper
    I'm in the process of converting our big clipper application to harbour. We use ADS extensive and I have problems finding the correct coresponding syntax from clipper in harbour. Normal DBF access works fine but how can I translate the following clipper ADS Syntax to harbour: AX_DRIVER(),AX_TRANSACTION(), AX_UNLOCK(), AX_RLOCK(), AX_GETLOCKS(), AX_LOCKOWNER(), AX_KEYNO() and others Please help how can I convert clipper ADS in harbour ADS. Juergen
  • 4. ctod bug??
    I may have found a bug in xHarbour for MS-VC 6.0 binaries and Borland C ++ 5.5 binaries. x := "September 1, 2012" ? ctod( x ) ==> 01/20/2000 (should be an empty date, as in clipper and dbase) Oddly, using 'August 29, 2007' as x - result is an empty date. Odd, huh?

Blinker Executable Clipper

Postby julian1984 » Thu, 13 Jan 2005 11:23:05 GMT

Hi,

I use Clipper 5.2e + Blinker 5.1

Which command is correct ?

Blinker Executable Clipper F128
or
Blinker Executable Clipper F:128
or
Blinker Executable Clipper //F:128

My config.sys setting files open 40 and I use command blinker to open
files 128.
Why my application still error dos 4 ?
Which setting read first, config.sys or blinker ?

Thx,

Julian


Re: Blinker Executable Clipper

Postby rlb » Thu, 13 Jan 2005 16:37:47 GMT




So... you tell your system that (MS-DOS) programs can be allowed to have
40 files opened simultaneously; you tell Blinker to create your program
so that it opens up to 128 files simultaneously; and you wonder that
your application runs out of file handles? Gosh, I wonder _what_ could
be the problem...


Both. They have different purposes. The files= setting in config.sys
tells your system how many files can be opened, max. The Blinker setting
tells your _program_ how many files it may try to open. If the latter
exceeds the former, the result is often, as you've seen, a somewhat
predictable failure.

Richard

Re: Blinker Executable Clipper

Postby medsyntel » Fri, 14 Jan 2005 02:22:46 GMT

Julian says:


Julian:
   I use same Clipper and same Bliinker as you.

   The linker command I use is:

   BLINKER EXECUTABLE CLIPPER //E0;F100;

   However, my config.sys file on my Win98SE machine has: 
      FILESHIGH=127

   You must have your config.sys file declare at least five more files than
your bliinker link script requires.

   (I hope one of the gurus here can validate my statements)

-Mel Smith






Similar Threads:

1.need Blinker for Clipper .obj

I have a clean compile and .obj file, but have problems creating .exe
with blinker (circa CA Clipper Summer '87). I'm wanting everything
(New clipper.exe, overcl87.lib, clipper.lib,...I mean everything!) but
will settle for Blinker.exe. Maybe someone can link the .obj for me?
Let's chat....Mike

 XXXX@XXXXX.COM 

2.General batch file to compile Clipper/Blinker

Hi,
I have a general batch file to compile simple one programme clipper files, 
involed with:
CL <filename>

Contents are:
del %1.EXE
clipper %1 /D__IS52
if not errorlevel 1 blinker file %1,ctus,__wait_b lib ct,nanfor,cpmi,oslib

I have big make and link scripts for may main application that contains many 
files, this includes a:
BLINKER EXECUTABLE CLIPPER F101

My question is, how can I simply get the embedded files command into my 
exe's without building a big complicated make/link script? Has anybody got a 
good, simple method?

Thanks in advance

Ian Boys
DTE



3.SWPRUNCMD, Blinker and Clipper 5.3

4.Clipper 5.1 & Blinker 6.0 With XP: Unrecoverable error 650: Processor stack fault

Hi!
My App work fine under W9X. Under XP Pro, app. start normally but when I go
to start reindex proc. this messagess follow:
(b)Error (0) Unrecoverable error 650: Processor stack fault.
One month ago, I was use Blinker 3.xx with equal results.
(I make test environment: eg. COMMAND.COM with separate config.nt &
autoexec.nt with files=200, but problem is still.)

Please, help.
Regards


5.Clipper Decompiler fo 5.x with Exospace/Rtlink/Blinker

6. Clipper and BLinker under XP, 15.05.2003

7. Clipper + Blinker 4.10 + Fast computers problem (R6003)

8. path to the clipper executable



Return to clipper

 

Who is online

Users browsing this forum: No registered users and 48 guest