Announcement

Collapse
No announcement yet.

#BLOAT problem with PBWIN 8.04

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #BLOAT problem with PBWIN 8.04

    I can't get compiled simple program with #BLOAT statement using PBWIN 8.04
    The error message is:
    Error 496 in C:\PBWin80\test.bas(0:000): Destination file write error

    It compiles without #BLOAT and with older versions of compiler.

    Can somebody check that out?

    Thanks,
    Aslan.

  • #2
    Here too

    Hi Aslan,
    Did you report it to [email protected] ?

    #BLOAT size_expression seems to be broken on my machine too.
    AMD Athlon 64 X2 Dual Core
    WinXP SP2
    PBWin804

    FWIW Compiler error 496 occurs when size_expression is larger than the "Disk image"
    reported by the log when program is compiled without the #BLOAT statement:
    Code:
    #BLOAT 5633
    Function PbMain()
     
      MsgBox ""
     
    End Function
    '------------------/PBMain
    Log using #BLOAT 5633
    PowerBASIC for Windows
    PB/Win Version 8.04
    Copyright (c) 1996-2007 PowerBasic Inc.
    Venice, Florida USA
    All Rights Reserved

    Error 496 in C:\PBWin804\Noname1.bas(0:000): Destination file write error
    Log W/Out #BLOAT or with #BLOAT 5632
    PowerBASIC for Windows
    PB/Win Version 8.04
    Copyright (c) 1996-2007 PowerBasic Inc.
    Venice, Florida USA
    All Rights Reserved

    Primary source: C:\PBWin804\Noname1.bas {60 total lines}
    Target compilation: Noname1.exe
    Compile time: 0.1 seconds, at 72000 lines/minute

    260 bytes compiled code, 1716 bytes RTLibrary,
    8 bytes string literals, and 1364 bytes dgroup.
    Executable stack size: 1048576 bytes.
    Disk image: 5632 bytes Memory image: 3088 bytes.

    Component Files:
    ----------------
    C:\PBWIN804\NONAME1.BAS
    (Reported number of lines in source includes comments etc)
    Rgds, Dave

    Comment


    • #3
      Yes, already reported to PB Support desk.

      Comment


      • #4
        Until I can find my install disks so I can get my serial number to upgrade, I am curious just out of coincidence if you use #BLOAT 6144 and that it works, but #BLOAT 6143 or #BLOAT 6145 do not work?
        Engineer's Motto: If it aint broke take it apart and fix it

        "If at 1st you don't succeed... call it version 1.0"

        "Half of Programming is coding"....."The other 90% is DEBUGGING"

        "Document my code????" .... "WHYYY??? do you think they call it CODE? "

        Comment


        • #5
          I confirmed this also in both PB/WIN 8.04 and PB/CC 4.04

          If the compiled program disk image size < #bloat size. It needs to be bloated. The compiler gives a destination file write error

          If the disk size >= #bloat size then there is no reason to #bloat the file and no error occurs.

          Or simply put #bloat can't bloat any more.

          Comment


          • #6
            If writen in PB, I would expect the error is like this

            'finished compiling
            CLOSE #f

            'if #Bloat
            Write #f,stuff

            oops... file is closed. I forgot to leave it open if there was a bloat statement...
            Barry

            Comment


            • #7
              >Or simply put #bloat can't bloat any more.

              #BLOAT broke?
              Heart broke.
              Not.
              Michael Mattias
              Tal Systems Inc. (retired)
              Racine WI USA
              [email protected]
              http://www.talsystems.com

              Comment


              • #8
                Where is my "Warm Fuzzy Feeling" that I can make a 32K program into 7 gig so I can stay on par with other Microsoft programs?

                (Sorry, couldn't help myself)
                Engineer's Motto: If it aint broke take it apart and fix it

                "If at 1st you don't succeed... call it version 1.0"

                "Half of Programming is coding"....."The other 90% is DEBUGGING"

                "Document my code????" .... "WHYYY??? do you think they call it CODE? "

                Comment


                • #9
                  Originally posted by Michael Mattias View Post
                  >Or simply put #bloat can't bloat any more.

                  #BLOAT broke?
                  Heart broke.
                  Not.
                  Poor bloke.
                  <b>George W. Bleck</b>
                  <img src='http://www.blecktech.com/myemail.gif'>

                  Comment


                  • #10
                    Until fixed, one could open the resulting .exe file and append tons of garbage to it.
                    pseudo code:
                    Code:
                    open "MyExeFile" for binary as #foo
                    seek #foo eof
                    for i = 1 to 543212
                     write #f,chr$(i mod 127)
                    next
                    close
                    Barry

                    Comment


                    • #11
                      Customer can't belief that one huge database project might fit into floppy disk. Just put bloat and program burned on 1/4 of CD

                      This is not the first time, when my customers want to see big project fitted on big exe file. Kind of approval for serious projects....

                      Comment


                      • #12
                        You must have the wrong kind of customers. I have NEVER had ANY client say one word about the size of any program I've created. NEVER.

                        Worst case scenario? Tell them you use a proprietary technology to reduce EXE/DLL sizes. This is course has the benefit of being absolutely true... but you really don't have to tell them WHOSE 'proprietary technology' it is, do you?
                        Michael Mattias
                        Tal Systems Inc. (retired)
                        Racine WI USA
                        [email protected]
                        http://www.talsystems.com

                        Comment


                        • #13
                          wrong kind of customers
                          There're a small number of customers who interested in size of programs. They're always asks many questions :laugh:

                          But, every third customer (from my experience) interested in what language program was writen. I'm saying PowerBASIC and explain what is this. (here link to 'proprietary technology')

                          Comment

                          Working...
                          X