#Bloat

[Egbert Zijlema]

Much Adoe About Nothing?

Me thinks, my fellow-countryman Edwin is right. Not the size of the exe but the quantity of the items that your proggie should move/copy (i.e. the "mega-size" of the array) is the important thingy here.

By the way: in Dutch we have a word that's exactly pronounced as "bloat" (written as "bloot") but its meaning is "naked". Coincidence PB-folks? Because in fact: bloat is Much Adoe About Nothing (Shakespearian spelling), isn't it?

[Edwin Knoppert]

No, increase the exe's size to see some progressbar??

I assume it was for testing purposes?

[Mr. Kevin Diggins]

Wrong tool???

For Gary's purposes, what's wrong with writing a "Hello World" program and #BLOATing it up to a gig or so file size?

Quick-n-easy.

I suspect EB was making a joke - implying VB would be the "right tool" for creating bloated applications.

[Erich Schulman]

For Gary Beene's purpose, I would probably use dd, but I am used to the Unix command line.

I could see #BLOAT as useful for steganography purposes, but then you would have to know exactly where the bloat is located so you can insert the payload.

[Mel Bishop]

Wrong tool???

For Gary's purposes, what's wrong with writing a "Hello World" program and #BLOATing it up to a gig or so file size?

Quick-n-easy.

[Edwin Knoppert]

The wrong tool for the job it seems..

[Gary Beene]

Because of the humorous content in Help for #Bloat, I dismissed the option.

But today, I actually needed found a use for it. I wanted to test out some download code but the EXE to download was only 20K or so. To make it big enough to see the download code (progressbar) in action, I used #Bloat to make the EXE bigger.

I could have made a simple text file that was huge, but #Bloat turned out to be convenient.

Cool beans.