debug an installing problems

[Johan Pfeiffer]

Hello lcc-win32 World!

I am learning programming in C and I found
a compact and useful develop system - lcc-win32.

Very thanks about this developsystem!
dear Jacob Navia

But i have a little trouble with installing.

The download is from http://www.cs.virginia.edu/~lcc-win32/
The WEDIt ist Version 4.0 and my Win32 is Xp (German) with Sp3.

In the helpfile is described the installing -
I can't found lcc2.exe, lcc3.exe, lccdoc.exe, fortran.exe, lccdb.exe

I install lccwin32, manual and win32hlp in path without space c:\lcc
with the automatic procedure.

The key F1 produce a error with the following message
Recovering from an error
Please save your work and exit
it ist not recommanded to continue :-(

The debugger with step in or key F8 run to the printf statmante
and open a dialog for search file in a directory.

so i was a little bit disappointed.

I am a novice in programming in C and i need the debugger more
then a compiler ;-)

What do i wrong - is the mistake before the screen?

I hope for help

greetings from south geramny
jopei

[L MATHAY]

Hello Johan,
> The key F1 produce an error message

I suppose you speak about the key in Wedit that is supposed to open
the HELP window.

I have found the same problem when installing the LCC version dated
02/02/2011 on my PC with XP SP1.
I thought this problem was specific to me, so I looked where the
problem comes from, and I found from where it comes and I tried to
report it to Jacob Navia (see below).
Meanwhile I have corrected it into my wedit.exe binary code, and now I
am running ok.

This is the bug report I sent somewhere last year to the mail address
ja...@jacob.remcomp.fr but I never had any answer :
/ Dear Jacob, or whom it may concern, I am proud to submit
you a correction for a bug in lcc.
/ The bug is as follows : on my computer, calling the menu
HELP->'WIN32API Help' produces a crash.

/ The reason for this is that for any reason the CLSID for
"DExplore.AppObj" cannot be found on my computer.

/ To correct for this problem in WEdit , do like following :
+ look in the code of WEdit for the procedure that
calls CLSIDFromProgID (probably named 'GetCLSID' for example)
+ go back one level to the procedure that called
'GetCLSID'
+ in this procedure, look at the nesting of the
'if' :
/ if 'GetCLSID' returns 0 you should leave the procedure,
and not jump to the sequence of calls to SysFreeString, because this
leads to a call to an invalid pointer because it is null.

/ As usual I am not sure you may read this message, so if
you do, please reply me to my mail address. Best regards, Lucien
MATHAY.

I think I have found now on this workgroup the way to resubmit this
bug report, hope there will be a connexion now.

Note that if I take the time to submit a bug report that is so
comprehensive (to my mind !) and to insist in submitting it, it is not
for my personal need, because as I said I overcame the problem.
if I insist in submitting this, it is as a sign of my personal respect
with regard to the work done by Jacob, which I consider so good that I
want this to be my little "thanks" and contribution to its author.
Johan, don't be stopped by your first impression ; Besides a few bugs
it works perfectly even for bigger applications. It is really a good
program to learn, and you will not be disappointed at the end.
Keep going further, Lucien.