PC Toledo

Thanks!!!!!!!!!!!

Hi! I played with this all day yesterday and this morning. Apparently, I'm more confused than I thought. LOL!

Anyway, I worked with the sample code that you had sent me Alxsts. I have 2 link files, one named TestLnk.Lnk and the other named TestLnk2.Lnk. Within TestLnk.Lnk I have the following code:

Output Confr.exe
FI Confr @TestLnk2.Lnk

(Confr is the system's executable.)

Within TestLnk2.Lnk I have the following code:

FI co_main.obj
FI co_index.obj
FI co_rept.obj
FI co_nod.obj
FI co_sal.obj
FI co_list.obj
FI co_pend.obj
FI co_proc.obj
FI imprbmp.obj
Lib Clipper, Extend, Overlay, dgsutil, dor_util

These names are all the different programs that I am working with plus the imprbmp.
I set the DOS environment to SET OBJ=\Confr and SET LIB=\Confr because that is where my objects and libraries are stored. I posted the errors I am receiving in the Code tags.

Código: Selecionar todos

C:\CONFR>set obj=\confr

C:\CONFR>set lib=\confr

C:\CONFR>plink86 @testlnk
PLINK86plus ( Nantucket ) Version 2.24.
Copyright (C) 1987 by Phoenix Technologies Ltd.,
All Rights Reserved.


Warning 11:   Duplicate CO_PROC in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate PAUSE in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate NAMESTR in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate MEMLETLOG in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate PRLETTER in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate PRNT_ADDR in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate PICK_CASE in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate V_FILENAME in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate V_TAXTYP in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate DAYS_PEND in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate DAYS_PROT in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate PRNT_NOD in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate FILETRANS in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate CLEANUP in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate READCHAR in Module CO_PROC File CO_PROC.OBJ

Warning 11:   Duplicate ERRORSYS in Module ERRORSYS File DOR_UTIL.LIB

Warning 11:   Duplicate EXPR_ERROR in Module ERRORSYS File DOR_UTIL.LIB

Warning 11:   Duplicate UNDEF_ERRO in Module ERRORSYS File DOR_UTIL.LIB

Warning 11:   Duplicate MISC_ERROR in Module ERRORSYS File DOR_UTIL.LIB

Warning 11:   Duplicate OPEN_ERROR in Module ERRORSYS File DOR_UTIL.LIB

Warning 11:   Duplicate DB_ERROR in Module ERRORSYS File DOR_UTIL.LIB

Warning 11:   Duplicate PRINT_ERRO in Module ERRORSYS File DOR_UTIL.LIB

Warning 11:   Duplicate MENU in Module MENU File DOR_UTIL.LIB

The following 19 symbols are undefined:

Symbol SET was accessed from Module IMPRBMP File IMPRBMP.OBJ
Symbol QQOUT was accessed from Module IMPRBMP File IMPRBMP.OBJ
Symbol AADD was accessed from Module IMPRBMP File IMPRBMP.OBJ
Symbol CTON was accessed from Module IMPRBMP File IMPRBMP.OBJ
Symbol NTOC was accessed from Module IMPRBMP File IMPRBMP.OBJ
Symbol RAT was accessed from Module LINE_IO File DGS_UTIL.LIB
Symbol AINS was accessed from Module SCROLL File DGS_UTIL.LIB
Symbol SCROLL was accessed from Module SCROLL File DGS_UTIL.LIB
Symbol ADEL was accessed from Module SCROLL File DGS_UTIL.LIB
Symbol MEMOWRIT was accessed from Module REPORT File DGS_UTIL.LIB
Symbol MEMOEDIT was accessed from Module REPORT File DGS_UTIL.LIB
Symbol MEMOREAD was accessed from Module REPORT File DGS_UTIL.LIB
Symbol KEYNAMES was accessed from Module STANDARD File DOR_UTIL.LIB
Symbol DSETWINDOW was accessed from Module STANDARD File DOR_UTIL.LIB
Symbol GETE was accessed from Module SECURITY File DOR_UTIL.LIB
Symbol XTOC was accessed from Module ERRORSYS File DOR_UTIL.LIB
Symbol SHOWTIME was accessed from Module DISPLAY File DOR_UTIL.LIB
Symbol MENU_H was accessed from Module MENU File DOR_UTIL.LIB
Symbol DISKSPACE was accessed from Module WHOAMI File DOR_UTIL.LIB

Fatal error 51
Undefined symbols exist
C:\CONFR>

Here are my stupid questions..........
Do I need to use the -m and -l ?
Why do we use FI Test.obj instead of using the .prg?
And I need to tell you that I used notepad to create the .Lnk. Was that ok?

If you have time to look at this later that is fine, if not, I understand. Thanks!!

Hi!

You can save one .LNK file merging the two you've created:

Código: Selecionar todos

Output Confr.exe
FI Confr.obj
FI co_main.obj
FI co_index.obj
FI co_rept.obj
FI co_nod.obj
FI co_sal.obj
FI co_list.obj
FI co_pend.obj
FI co_proc.obj
FI imprbmp.obj
Lib Clipper, Extend, Overlay, dgsutil, dor_util, CT

Note that I've added an entry for CT.Lib (you'll need it).

I set the DOS environment to SET OBJ=\Confr and SET LIB=\Confr because that is where my objects and libraries are stored.

This is correct if the files are really where you ponted to.

About the duplicate symbols warnings: I haven't seen your source code but, as the messages state, you have doubly defined symbols in your code.
Look for them inside all .PRG files. If you use a good text editor (download one for free), you can issue a find in files command to do this. If you don't find duplicate symbols in source code, maybe someone have grouped them in one of the user libs you're requesting the linker to search in... Who knows? If your .PRG file has the same name of a Procedure or Function declared inside it, you must compile with /N compiler switch.

About the undefined symbols errors: it's very strange... are you sure you're using version 5.2 of Clipper? It seems you're using version Summer'87 and compiling version 5.xx
syntax. Check the version. You can download version 5.2e International version here. Unzip to C:\

marge0512 escreveu:Why do we use FI Test.obj instead of using the .prg?

In order to generate an executable file, the compiler reads .PRG files and generates .OBJ intermediate files which are linkedited by the linker to generate .EXE.

You know what Alxsts......I wonder if you are right and I am using that version instead. I am not really sure and will research. I found a very good site I am reading now that explains how to compile, what to use and so forth. I have tried a couple of different ways to compile the imprbmp.prg alone and I still get 36 errors so.........I have a feeling........just a feeling that you are right, it's the Summer'87 version, not 5.2 and that is why the 36 errors. It doesn't recognize {}, :=, and so on and so on.

Thank you so much for your info. I will check what version I am using (not sure how to find that) and if I'm using summer'87 I will download the version with the information you provided. Hopefully, I won't have any problems changing the version???

Thanks again!!!!!!!!!!!!!!!

Hi,

when you type Clipper in a Windows CMD window, Clipper's splash screen shows. The first line contains the version number. Lunch time! Finally...

Well, isn't this lovely..........

The Clipper Compiler, Summer '87
Copyright (c) Nantucket Corp 1985-1987. All Rights Reserved.
Microsoft C Runtime Library Routines,
Copyright (c) Microsoft Corp 1984-1987. All Rights Reserved.

Ok, time to download newer version. Yes, lunch time is here!! One of my favorite times of the day!!

Hi again.

This function is said to print a bitmap.

All I'd like to know is:
Will it be possible to print both text and graphics in the same page, side by side, for example?

Jairo: did you try it?

Good question!!

I can't wait until I get to the point where I can test this function. LOL!!

Hi All,

alxsts escreveu:All I'd like to know is:
Will it be possible to print both text and graphics in the same page, side by side, for example?

Alexandre, at morning I tried answer this question, so, I compiled the original routine on Clipper 5.2e including CT.LIB.

The executable file was created without error, but I could not printer. I tried to printer in dot-matrix, and no result, so, I tried on InkJet, and the printer no emits no signal. Maybe because I used an adapter LPT to USB.

Usually, detecting where the function print each line, after this can print a text, but I´m not sure on that in this case yet.

If this is possible, I like to remind that I know nothing about ClipperSammer87, I can try it on Clipper 5.2.

If anyone could test the executable, and report any positive result, this would help for now. I remember that the test should use the printer on LPT1.

Regards

Enviado: **07 Jun 2011 16:22**

Hello! I had to work on something else for a while, now I came back to this project a couple of days ago and I am having a hard time with this. I downloaded version 5.2 for now. RTLINK linker comes with this version. My question is (probably a dumb one but.....) do I need a specific type of software to create the .lnk files? I tried using Notepad and saving the file with the .lnk extension. It seems to make the file into a short cut.

Thanks in advance!

Enviado: **08 Jun 2011 15:46**

Hi Marge,

You don´t need a specific software type. You can to use the notepad.

marge0512 escreveu:It seems to make the file into a short cut.

I don´t understand why. You can post the result so we can try to help?

Enviado: **08 Jun 2011 16:09**

Hi,

NotePad, by default, saves files with .TXT extension. Isn't you file with a ".LNK.TXT" extension?

Select "All Files" instead of "Text Files" in the Save As dialog box.

During the time you were away, we´ve found out nobody who tried to use this routine got successfull. I Think we're loosing our time. Better to find another solution...

Enviado: **08 Jun 2011 16:30**

Thank you both for replying!!

I selected "all files" in Notepad when saving the .lnk but I took off the .txt extension and added the .lnk instead. If I go to change the coding in the .lnk, the file does not open because it shows as type "shortcut" in explorer so I am definitely doing something wrong. Now, I try to do this in a .bat file like what we use to link in summer87 before using this code:

clipper co_main.prg /m /l
clipper co_index.prg /m /l
clipper co_rept.prg /m /l
clipper co_nod.prg /m /l
clipper co_sal.prg /m /l
clipper co_list.prg /m /l
clipper co_pend.prg /m /l
clipper co_proc.prg /m /l

RTLINK FI CO_MAIN.OBJ, CO_INDEX.OBJ, CO_REPT.OBJ, CO_NOD.OBJ, CO_SAL.OBJ, ^
CO_LIST.OBJ, CO_PEND.OBJ, CO_PROC.OBJ ^
LIB CLIPPER.LIB, OVERLAY.LIB, DGS_UTIL.LIB, DOR_UTIL.LIB ^
OUTPUT CONFR.EXE

and I receive these results............I took off the top compiles for simplicity sake.......

Código: Selecionar todos

C:\CONFR>clipper co_proc.prg /m /l
Clipper (R) Version 5.2
Copyright (c) 1985-1993, Computer Associates International, Inc.
Microsoft C Floating Point Support Routines
Copyright (c) Microsoft Corp 1984-1987.  All Rights Reserved.
314K available
Compiling CO_PROC.PRG
Code size 5148, Symbols 2432, Constants 2084

C:\CONFR>RTLINK FI CO_MAIN.OBJ, CO_INDEX.OBJ,  CO_REPT.OBJ, CO_NOD.OBJ, CO_SAL.OBJ,
CO_LIST.OBJ, CO_PEND.OBJ, CO_PROC.OBJ  LIB CLIPPER.LIB, OVERLAY.LIB, DGS_UTIL.LIB,
DOR_UTIL.LIB      OUTPUT CONFR.EXE
The system cannot execute the specified program.

I did notice that if I make this into a smaller amount to link, I get unrecognized symbols. For example, I took off all .prg and .obj leaving only three of them so I'm wondering if it is size issue. I do understand why I get the unrecognized symbols error.

I am so used to object oriented programming that I am really confused. However, I did find another download that may also print the letterhead out. If you are interested in it let me know and I will send you both the site. I can't wait to get to the point to try these out!

If these do not work then I will have to let the users know that they may be stuck switching paper. I will be rewriting this system in Delphi soon but meanwhile, they would like this to work.

Thanks so much for your help!

Enviado: **08 Jun 2011 16:59**

Hi,

in the ancient times, when someone created the .LNK extension and assigned it to PLINK link scripts, MS-Windows was not born yet! Later, WIndows became a strong boy and started to command. Then, it created the shortcut mechanism (a file on disk which points to another) and decided to give it the .LNK extension without taking care of the obsolete PLINK.

Windows Explorer, in it´s FIle Associations, has this extension as a reserved one and thus prevents itself from opening such a file with the associated program, executing it instead.

To edit this old .LNK file, at the CMD prompt, type EDIT <your file name>. It will work.

This link shows a brazilian software product which says to do what you need. I've never used it. There is a download link to a demo version. What about trying it?

While you can´t run this appication in Delphi, you shoud also consider to compile it with [x]Harbour as written in my first post.

Enviado: **09 Jun 2011 15:49**

Thanks so much! That makes sense and helps quite a bit. Now I know how to edit that .lnk file. I will play around more with this. I downloaded that software product so hopefully one of these will work when i get this thing up and running. Maybe XHarbour is the way. There seems to be a lot of people using it I found when I research.

Thanks again!!

PC Toledo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo

Clipper 5.2 and Printing Logo