#BLOAT problem

[John McClain]

Any attempt to use #BLOAT in a program results in the following error:

Error 496 in C:\PBCC40\Samples\Hello\Hello2.bas(0:000): Destination file write error

Source code is:

#BLOAT 65536
#COMPILE EXE
#DIM ALL

FUNCTION PBMAIN () AS LONG
? "Hello, World!"

WAITKEY$

END FUNCTION

[Mike Doty]

Same here. This is the highest it will go.
#BLOAT 10752
#RESOURCE "HELLO.PBR"

[Rodney Hicks]

#BLOAT 8192 was the largest I got to work.
16384 and up give the error you state.

I didn't try anything between these two.

[Barry Erick]

this works for me

#bloat 1024*1024*4*92 'make a 385,875,968 byte file

as well as

#bloat 385875968&

and

#bloat 385875968

[Dave Biggs]

This was an issue with PBWin804, See this thread..

http://www.powerbasic.com/support/pbforums/showthread.php?t=35458

It has been fixed in PBWin90.

[Michael Mattias]

This was an issue with PBWin804, See this thread..
It has been fixed in PBWin90

File, open, history.txt
See:

------------------------------------------------------------------------------
                Changes/Updates to PowerBASIC For Windows Compiler 9
------------------------------------------------------------------------------


                          Changes since PB/Win 8.04

Find 'bloat.'

"Text not found"

MCM

[Mike Doty]

Should have tried with PBCC 5. Time to update.
11264 is the minimum with PBCC 5. Works, fine.

[Ken Deitz]

Usage of #BLOAT {expression} yields "Destination file write error"

It may be a stupid question as I am still using and satisfied with PBCC 4.
Is this fixed now? What release was it fixed under? I have a need for obfuscation, so I was finally looking at this compiler directive, only to find it isn't functional. Apparently the only function of it in PBCC 4 is that Bob Zale got me to laugh? Seriously, I can use it...

[John Gleason]

Using pbcc 4.04 and the below metastatement order it worked ok for me.

#COMPILE EXE
#DIM ALL
#BLOAT 16777234