Announcement

**Jerry Mason** · 31 Aug 2001, 10:10 AM

Yes, Bernie, these problems will crop up once in a while in large
programs. I've found that the fastest way to get up and running
again is by using the $SEGMENT metastatement. Try breaking up your
program into smaller pieces by adding a $SEGMENT and moving your
existing ones. It often takes me several tries to get compilation
working again, but once it does it doesn't break again for a long
time.

Also, you do have a less memory available than I do. You might try
compiling in a pure DOS session, with no EMM or CDROM drivers or
any of the other windows gunk.

------------------

**Davide Vecchi** · 31 Aug 2001, 01:39 PM

Another thing you might try is moving several procedures to a separated file to be compiled as a PBU, and put a

Code:

 $CODE SEG “name”

at the top of the file, so that the resulting object code will end up in a separated code segment.
If your actually SHARED vars are used by the moved procedures too, you’ ll have to use PUBLIC instead of DIM SHARED for these vars in the main and put the same PUBLICs statements in the unit.

------------------

**Lance Edmonds** · 31 Aug 2001, 09:26 PM

You are using the 12/19/97 build, so the first question is this: is the problem repeatable on multiple computers. You have to test this with exactly the same source code.

If the problem cannot be reliably duplicated then the first suspect is the memory manager.

However, if it can be duplicated reliably, then PowerBASIC will be most interested to see the problem.

If you can please submit the problematic code to Tech Support (where it will be treated in strict confidence of course!), and we'll check into it.

If we do verify it to be a compiler problem, we'll take the matter up with R&D.

Thanks!

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

**Lance Edmonds** · 31 Aug 2001, 09:32 PM

One more point... the program should still be able to be compiled with the IDE, but without sufficient free memory it may not be able to be executed within the IDE.

When you next encounter the problem with PBC, please try compiling the exact same code in the IDE.

Also, do any of the compile options ($LIB, $OPTION, etc) have any effect at all?

Finally, does disabling EMS and XMS make any difference too? You can use PBINST.EXE to customize/disable the EMS/XMS memory usage of both PBC.EXE and PB.EXE.

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

**Bernie Lazette** · 1 Sep 2001, 11:57 AM

Thank you
Jerry, Davide and Lance for your suggestions and comments.
I now have some new ideas to pursue. I am out of the office
until next Tuesday but will certainly want to try to solve the
puzzle when I return.

Thanks again
Bernie

------------------
[email protected]

**Bernie Lazette** · 4 Sep 2001, 05:01 PM

Hello again
Further to suggestions from Lance and others, I have decided
to conduct a number of tests on a variety of computers to determine
the cause of Fixup Overflow errors (515). My first step was to
eliminate EMS/XMS from the picture. This was done on PB.EXE.
In order to create fixed environment and reduce as many variables
as possible DOS 6.22 boot disk was used.The boot disk contained the
following files

COMMAND.COM AUTOEXEC.BAT CONFIG.SYS HIMEM.SYS
PB.EXE SOURCE.EXE RAMDRIVE.SYS

The CONFIG.SYS file contained the following lines
DEVICE=HIMEM.SYS
DEVICE=RAMDRIVE.SYS 4096 512 128 /e

The AUTOEXEC.BAT file contained only the line
PROMPT $p$g

PB.EXE has EMS/XMS usage disabled

Computers Used

1. 486/33 DOS 6.22
2. P-233 MMX Windows ME
3. P3-450 Windows 98 SE
4. P54C-133 Windows 95 Version 4.00.1111
5. P-166 DOS 6.22
6. 386-33 DOS 6.22

***************** *Test No. 1 ************************************
Each computer was booted using the boot disk described above.The
self-extracting source file was extracted to the ramdrive. The
directory changed to ramdrive and source compiled to EXE (Alt-F9)
using PB.EXE. Two sources A and B were used.

Here are the results of test 1.

Computer Source A Source B
-------------------------------------------
1. Error 515 Error 515
2. Success Success
3. Success Success
4. Success Error 515
5. Success Error 515
6. Error 515 Error 515

***************** *Test No. 2 ************************************
In this test each computer was booted using it's own operating system
The self-extracting source file was placed in its own directory on each
computer. Sources were compiled to EXE (Alt-F9) using PB.EXE.
Again two sources were used.

Here are the results of test 2.

Computer Source A Source B
-------------------------------------------
1. GFP Error 515
2. Hung * Hung * Note 1
3. Success Success * Note 2
4. Error 515 Success
5. Error 515 Error 515
6. Error 449 * Error 477 * Note 4
Note 5.

***************** *Test No. 3 ************************************
Each computer was booted using it's own operating system
The self-extracting source file was extracted to directory on each
computer. Sources were compiled using PBC.EXE.
Again two sources were used.

Here are the results of test 3.

Computer Source A Source B
-------------------------------------------
1. Error 515 Success * Note 2
2. Error 515 Error 515
3. Error 515 Hung * Note 3
4. Error 515 Error 515
5. Error 515 Error 515
6. Error 515 Error 515

Note 1. This computer hung while compiling and could only be
interrupted using Ctrl-Alt-Del.

Note 2. Although this source compiled without error, the EXE failed on
execution (Run time error 5). The length of the EXE was 171,586, which
is 3 bytes longer than the other successful compiles of the same source.

Note 3. This computer hung while compiling and was interrupted
by pressing <enter> a couple of times. However PBC spilled
to the screen what appeared to be random memory followed by Error 538

Note 4. This compile failed with 477 Syntax error. Indicating the following
error location which of coarse makes no sense
DIM MItem(20) AS LOCAL STRING

Note 5. This compile failed with 449 SELECT Expected. Indicating
the following error location which also makes no sense.

Select Case ASCII(Right$(Choice,1))
Case %SF11
Bit Toggle Options1, %NoExtPrint
Case %ALTL
**********************************************************************

Anyone got any ideas?

Thank you for reading this

Bernie Lazette

------------------
[email protected]

**Davide Vecchi** · 5 Sep 2001, 02:16 PM

Bernie,

by using 6 PCs in 3 different tests and classifying the results that way, you did a very good work, really; it’ s what everybody should do when suspecting a bug of this kind. The fact that the problem arises with some PCs and not with some others IMO says very much.

However, trying to understand the exact cause of your problem IMO is a losing mission. The elements involved are too many. It would be much better going for the ways that are proven to solve this kind of problems, that is $SEGMENT or units with $CODE SEG. Other possibilities are creating separates EXEs to be CHAINed or RUN one another, or reducing the amount of global vars, or other things that affect memory usage.

I know that this might be hard to accept (even though it shouldn’ t), however IMO the reality is that if you suppose to magically eliminate every bug from every OS and mem manager, some programs that have always worked very fine that far, would start to crash, and some programs that have been sometimes crashing would stop crashing forever.
It’ s more or less similar to the problem of the many web pages that work fine with the bugs of the most common browser: they won’ t work if accessed with a browser which hasn’ t those bugs.

So, IMO, rather than trying to detect “where is the problem”, the most realistic thing to do in these cases is detecting “where isn’ t the problem”, that is staying away from unclear limits of the system. This way your code will be compiled and will run fine virtually ever. So my suggestion is, don’ t worry, make your program use memory differently.

------------------

**Lance Edmonds** · 5 Sep 2001, 09:59 PM

Bernie, you have gone to great length, sure enough. However, You have not submitted the code to Tech Support as of yet.

Until PowerBASIC, Inc. can duplicate the problem and work out what is going wrong, we cannot give you any explicit answers as to the cause.

I hope to hear from you soon...

Thanks!

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

**Bernie Lazette** · 6 Sep 2001, 10:05 AM

Hello Lance
A test suite is on it's way
Thanks for your help so far

Bernie Lazette

------------------
[email protected]

**Daniel Raymer** · 14 Mar 2002, 03:06 AM

Any further progress on the 515 Fixup error? I'm finishing a PHD in the next two weeks, and can't add another line of code !

I tried the tricks with EMM, XMS and $segment. I'm not using any of the pointers or other possible causes mentioned in the documentation. It would be very difficult to break my code apart any further.

It happened once before and I "fixed" it by moving a $segment statement, but now that doesn't work.

Help! Any further ideas?

------------------

**Jerry Fielden** · 14 Mar 2002, 07:51 AM

Originally posted by Daniel Raymer:
Help! Any further ideas?

[/B]

Would any of you care to try a program that strips the comments
and extra spacing to further reduce source size. It also finds
needed functions, subs, types, unions, constants in Include files
and writes them to the Source and eliminates the include file. The
results is written to another Bas file leaving the Original Source
as is.

The PBCC source is in the BBS's Source thread, But I can Email you
a compiled version if you are interested.

I've used it on PBNOTE.BAS and a few others, but not on any large
files. I haven't got any reports that it doesn't work. I don't see
why it wouldn't work with PBDOS source. Email me if you want to give
it a try........ [email protected]

------------------

**Bernie Lazette** · 14 Mar 2002, 11:58 AM

Hello Daniel & Jerry
Thank you for your interest in my posting. The 515 error has been a real problem for me as well. One thing I have found to sometimes get rid of the 515 error by adding a dummy label just before the line which appears to cause the error. This may get you by the compile process but not neccesarily out of trouble. I have found in some cases an area of the program which previously worked perfectly will crash with windows reporting a GFP or illegal opertion error. In other words when PBC reports 515 something serious is going wrong. As you have probably noted back in Sept 2001, I did extensive testing in an effort to demonstrate this and other problems I encountered with PBC. I sent a test suite to PowerBasic Support but I am still waiting patiently for a reply.
An other thing I have done is to combine all incude files into a single source. As above this may get you past the 515 compile error but it does not mean you have a good compile.

Anyone else got any ideas

Thank you and have a good day
Bernie

------------------
[email protected]

[This message has been edited by Bernie Lazette (edited March 14, 2002).]

**OTTO WIPFEL** · 16 Mar 2002, 12:47 PM

Bernie,

I had similar experiences compiling larger programmes with PB 3.5 in DOS 6.22,
I still work in, years ago.

The moment the compiled *.EXEs would get close to 400 Kb all sorts of weird
things happen. Like a Label suddenly being complained about by the Compiler
as an Error 466 - "Duplicate Name Definition" !

A Norton Text Search in all files on the disk can find no other occurance
of the label or other variable with the same name anywhere.

So I decided to keep my compiled *.EXEs below 300 Kb, not a bad idea as some
of them need the limited Dos for Programmes Memory for Arrays, etc.

No more problems in DOS or in any flavour of Windows up to 98 SE since.

PB for DOS compiled programmes can "EXECUTE" from one to the other and back
again and the only memory overhead is a 1 Kb Stub to stop them getting lost,
ahhhh

BLOATWARE is the prerogative of WINDOWS ! Lets stick to lean, mean and fast
EXECUTABLES PowerBasic for DOS is famous for !!!

------------------

**Bernie Lazette** · 19 Mar 2002, 06:22 AM

Hello Otto
Thank you for your reply. I have executables as low as 220k in size
which I have had problems of one sort or another compiling.
Over the years there have been several posts regarding this
kind of problem. It may some line of code I'm using which is
confusing the compiler. If I only knew how to avoid it.
Thanks for your help.

Bernie

------------------
[email protected]

[This message has been edited by Bernie Lazette (edited March 19, 2002).]

Announcement

PBC Errors 515,611 and hanging

PBC Errors 515,611 and hanging

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment