PC Toledo

.:-O
Oi, Se he/it o agrada que eu não tive uma resposta novamente, preocupado o
uso do overlays. Eu trabalho DOS com as Win 98. o clipper versão 5.01
com como publicador de gravatas o RTlink versão 3.13.To tem meu arquivo. exe
Eu uso o cl bat. c:\clipper\bin.
cl.bat = clipperr %1
if not errorlevel %1 rtlink file %1
Minha aplicação inclui o equivalente de 120 files. executant de prg.en ordena isto cl
há criação de meu arquivo de exe.qui funciona good.i chegou a uma fase
onde se eu não somo seria que que só um arquivo pequeno para minha aplicação a compilação não se faz e não tem o exe de arquivo. eu li em algum lugar que curar este problema para usar algunsoverlays ligar alguns arquivos entre eles e economizar a memória é então necessary.Is o que alguém pode me contar como alcançar estes overlays, eu sei que o rtlink apóia o overlays aquele chama dinâmico.
Eu tentei só trabalhar com o blinker7 debaixo das mesmas condições com
a ordem cl.bat que se torna: clipper %1
if not errorlevel %1 blinker file %1
trabalha o exe de arquivo é criado, mas quando eu o éxecute tem uma mensagem que ressort:Not enough memory: não suficientemente de memoire.but eu tenho bem bastante memória em meu computer.i tem que remover se você ou pode me ajudar que a primeira solução para fazer alguns overlays com o rtlink ou o segundo poder de solução para executar meu exe cria com o blinker 07. Um grande obrigado .you é Grande.desculpa pode traduction de "prtugais" com computador

Hello, Menjras
Wellcome to our board.
Unfortunately we don't speak Arabic, but we can try to talk in English.

The use of overlays (real mode only) looks like a good solution to solve the problem related to low memory in older machines when you're using RTLink or even an ancient version of BLinker. But the most modern solution is to create a program to work in protected mode. And it's possible even in ancient versions of BLinker. The result is fantastic and your program can continue growing up without any problem. By the way you will notice your program running faster and with no memory swaps or any other disk access.

This special way of execution forces your program to run in the extended memory area (above the first 1MB). Naturally, your operating system needs to load in boot-time a special memory management driver. In pure DOS it's mandatory in config.sys. Of course, work in pure DOS is a deprecated way to work. So, I'll forget this and I'll talk considering you're using Windows in (not)NT-kernel (95/98/Me/2K/XP). In this case, don't worry about that driver. Automatically it's available by your OS when you open a new DOS session.

If you're interested in this special running mode, the good new is: there are only 2 basic steps to follow. Let's see:

1) The BLinker needs to know what is your intention. Insert the command BLINKER EXECUTABLE EXTENDED in your linkage script to activate the protected mode.

2) Include a special library to permit BLinker to work appropriately with the many special features envolved in protected mode (and many new functions). What library depends what is your version of the Clipper. Basically there are only 2 options:

LIBRARY BLXCLP52 ---> version 5.2x
LIBRARY BLXCLP53 ---> version 5.3x

Pay attention to the unique possible bad new. Some libraries are not prepared to run in protect mode. What this means? Some libraries make direct memory access (like video RAM) and this is not allowed. Remember: the name is "protected mode". So, the memory is protected and any memory access needs an OS authorization through an element called "memory selector". Ancient libraries, many times, makes direct access. Therefore, running in protected mode, when the program tries to access directly a protected memory area, it always triggers a GPS (General Protection Fault) and crashes.

Download the BLinker 7 (last version), install it and study its help. You will note many interesting features (commands and functions) that will help you to work in a much better way. By the way, I want to detach two interesting functions: BliCPURel() that reduce the CPU consumption and SwpRunCmd() that substitute (much) more efficiently the RUN command.

I hope this message helps you to see more clearly how this execution mode works and which benefits you could gain. Despite some few inconveniences with one or another ancient library, this is the preferred mode to work by 9 of each 10 Clipper programmers.

One more time: be wellcome. Feel free to talk us in any language you want. Except arabic, of course.

:xau :{ Merci Beaucoup Maligno,pour tous tes conseils.Voilà après le portugais traduit par ordinateur,je me met au français en fait c'est ma deuxieme langue après l'arabe.
J'espère que le français ne te pose pas trop de problèmes .En fai tout ceci pour te dire que j'ai bien lu ton méssage que 'ai trové très interessant.il me reste à trouver l'aide sur le Blinker,et un peu de cours sur le Clipper 5.2 ou 5.3 ,car il faut dire que j'ai arrêté la programmation en Clipper depuis l'an 2000, et je constate
après avoir voulu ajouter quelques procédures à mon ancienne application qu'il faut se mettre à jour sur quelques points, et je vous remercie beaucoup tous et toi maligno en particulier pour vôtre aide.Je vais essayer ce que vous m'avez suggeré ,et je vous dis à très bientôt.Si vous avez quelques chose d'aure à me
faire conaîte n'hesitez surtout pas .Merci

J'espère que le français ne te pose pas trop de problèmes

I have some difficult to understand french. Actually I was thinking to talk in english or spanish.

Je vais essayer ce que vous m'avez suggeré ,et je vous dis à très bientôt

Ok. Indeed, after some time it's natural to forget many things about programming in any language. Therefore, in case of doubts come back to here. Will be a pleasure to help you to return to xbase programming.

:xau
Hello
Please, someone can tell me, a means of crypter the file dbf so that them not legible by a dbu.exe or other, while keeping the possiblié to be use by an application with Clipper-CA.because I have try but the files become illegible for the application too. Grand Thank you for advance.

There are two ways to do that. You can simply modify a single byte in the DBF data control block. This trick will turn your file unreadable through DBU or any other data explorer. The second way envolves a external function (eg. SIX library) to encrypt all data. In execution time you decrypt and befere leave the program encrypt again.
These two ways has the same problem: in a network environment will be very difficult control or share the read control between two or more users because both envolves exclusive access to file. Particularly I never used anyone.

A third option would be encrypt only sensible data (some fields) to hide it to any snooper. It's a less "aggressive" way.

HTH