Blinker Executable Clipper


    Sponsored Links


  • 1. Holding locks with Windows 98 & 2003 "Server"
    I am creating files using SET DEVICE TO PRINT and SET PRINTER TO filename - (ok actually I am using SET(24 ) ect as I can understand the code better!) However on Win98 with 2003 Server the files are occasionally held open despite me closing them XP WS is fine all the time. I force a close by SETting to a dummy name Any ideas ? Is it a client setting in WIndows?
  • 2. NTX & PMS Files
    I have been given the task to migrate an application to Access. The only info I have is that each file has an NTX and PMS type file. My research has led me to believe that the NTX file is a Clipper file, but the PMS file is a mystery. There are no DBF file types. Any ideas please. Thanks
  • 3. Clipper on XP (setting Shortcut/Link Parameters and Environment Variables)
    I am getting ready (and testing) my Clipper applications on an XP Pro workstation. Does anyone have any experience, suggestions, or seen any benefits by doing the following: Creating a shortcut on the desktop directly to the Clipper EXE and going to the Memory Tab on the Shortcut Properties. Any suggested settings here? Creating a shortcut to a batch file that calls the Clipper EXE. The Shortcut properties are different and does not have the Memory tab. Has anyone ever noticed an advantage or disadvantage of this type compared a direct shortcut to an EXE? Finally, has anyone ran into problems where the TMP and TEMP environment variables are set to long filename path's? Will Clipper be OK? Or should we set these variables to something like C:\TEMP? For example, the TMP and TEMP environment variables are currently set to "C:\Documents and Settings\UserID\Temp". My only concern on the above is with old EXE's. I have burnt the SWAPPATH and TEMPPATH Environment Variables into the EXE's linked within the last fews years. Thanks in advance. John W
  • 4. I need Help with XP and clipper and slow printing
    I have an application which I just switched to a DOS window on XP for a client. I have tried adding IAMIDLE but am still having the same problem with the printer pausing during printing. The IAMIDLE.OBJ file that I'm using(supposedly the latest with all the "bugs" fixed is dated 05/01/1997 3:05AM 297 Bytes Below is the call to in the main program, PBMAIN and the linker script This is where I've entered the call to FT_ONIDLE in the main program, PBMAIN ** << PBMAIN - MAIN MENU >> ** FT_ONIDLE({FT_IAmIdle(99,.T.)}) oldcolor := setcolor() ForSale := { ||ChkType() } mFAILEDM := SETUP(mmHELP) DO WHILE .NOT. mFAILEDM program loop ............. I use RTLINK as my linker FI PBMAIN FI IAMIDLE FI PBPRO, PBPRO1, PBPRO2, PBPRO3, PRO_FUNC, PB501 FI PBA, PBA1, PBB, PBC, PBD, PBE, PBF, PBH, PBI, PBJ, PBK, PBK1, PBL, PBM FI PBY, PBZ, P_ERR LIB C:\CLIP52\lib\clipper LIB C:\CLIP52\lib\extend LIB C:\CLIP52\lib\nanfor LIB C:\CLIP52\lib\nt250 LIB C:\CLIP52\lib\cpmi OUTPUT PAWN501K Any help or suggestions would be greatly appreciated by me and especially by my client. Al Nystrom in Sacramento, CA

Blinker Executable Clipper

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


I use Clipper 5.2e + Blinker 5.1

Which command is correct ?

Blinker Executable Clipper F128
Blinker Executable Clipper F:128
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 ?



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.


Re: Blinker Executable Clipper

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

Julian says:

   I use same Clipper and same Bliinker as you.

   The linker command I use is:


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

   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


2.General batch file to compile Clipper/Blinker

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:

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

3.SWPRUNCMD, Blinker and Clipper 5.3

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

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.

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 25 guest