Blinker Executable Clipper

clipper

    Sponsored Links

    Next

  • 1. Help! FILESEEK Does not work under XP
    Hi! The next codes works fine under Win98. If there is directories: D1, D2, D3, D4... on a disk than: cFile := FILESEEK(cPath + "*.*", 16,.T.) //cFile = 'D1' cSeekEnv := SAVEFSEEK() cFile := FILESEEK() // cFile = 'D2' RESTFSEEK(cSeekEnv) cFile := FILESEEK() // cFile = 'D2' !!! - and so it should be! But under XP I have: cFile := FILESEEK(cPath + "*.*", 16,.T.) //cFile = 'D1' cSeekEnv := SAVEFSEEK() cFile := FILESEEK() // cFile = 'D2' RESTFSEEK(cSeekEnv) cFile := FILESEEK() // cFile = 'D3' !!????? Why not 'D2'? RESTFSEEK(cSeekEnv) cFile := FILESEEK() // cFile = 'D4' !!????? Same ... Why? Why RESTFSEEK() is ignored? What can I do with this? Thank you. Valery
  • 2. MD5 Checksums for Clipper EXEs
    I'm involved in a project to extend the life of some legacy Clipper applications. As a first step, I'm cleaning up the development environment -- cleaning up directories, importing code into subversion, and migrating the build process from a series of DOS batch files to an NMAKE makefile. I was asked if there was any way I could verify that I had not introduced any errors into the process. My first thought was that if I am using the same source code, the same compiler (with the same switched), and the same linker (with the same linking files and switches), the EXEs should be identical, so I should be able to do a binary diff on them. I then "revised" my thoughts, and decided that generating MD5 signatures for the new EXEs and comparing them to the legacy EXE MD5 signatures would give me the same results. Imagine my surprise when the signatures did not match! I eventually tried generating an EXE, renaming it, and then generating the EXE again... the signatures do not match. Pulling them up in a hex editor shows that they are identical up to a point, then differ. I had the legacy developer generate an EXE with the batch scripts, remove the OBJs and regen, then remove the EXE, and regen, and all three were different. Does Clipper 5.3/Blinker 6.0 introduce something? Is there uninitialized memory which is written to the files? Something I'm just missing?
  • 3. 6313/6612 Errors
    I support a Clipper 5.2e application that uses Advantage 5.7. This is running on a Novel Network. In the last month, we have started to receive about 10-20 6313 subcode 6612 errors (general communication error, packet out of range) a day. This issue has us all stumped. We have tried turning off advantage caching, stopped running the application across multiple servers, and switched the process time to a quiet time between midnight and 0600, but we continue to get the error. We can't get any help from Extended Systems, as this version of Advantage is no longer supported. Does anyone have any suggestions as to what we might try to do isolate this error and possibly eliminat it? Thank you.

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