Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Unused routines still result in huge .EXE
#21
(08-07-2024, 11:10 PM)Pete Wrote: @TerryRitchie

It would have been a blast having you at the QBasic Forum back then. Most people during that time wouldn't believe big projects like ours were possible in QB. I lost track of another good guy named Dale Harris, no relation to Knee Pads Harris. He wrote a similar large business app in QB for point of sale. He called it his POS project. I told him it wasn't a POS project, because he needed FreeBAISC for that!

Pete
I remember that project. Didn't he ask for assistance around 2010 or so on the QB64 forum because he was working on converting it?

Unfortunately when I left the admin position I was no longer working on large Qbasic projects and had moved onto VB for windows until .NET came out. Then I dabbled in Delphi, Python, and PHP until I discovered QB64 in 2010.
New to QB64pe? Visit the QB64 tutorial to get started.
QB64 Tutorial
Reply
#22
(08-09-2024, 07:47 PM)TerryRitchie Wrote:
(08-07-2024, 11:10 PM)Pete Wrote: @TerryRitchie

It would have been a blast having you at the QBasic Forum back then. Most people during that time wouldn't believe big projects like ours were possible in QB. I lost track of another good guy named Dale Harris, no relation to Knee Pads Harris. He wrote a similar large business app in QB for point of sale. He called it his POS project. I told him it wasn't a POS project, because he needed FreeBAISC for that!

Pete
I remember that project. Didn't he ask for assistance around 2010 or so on the QB64 forum because he was working on converting it?

Unfortunately when I left the admin position I was no longer working on large Qbasic projects and had moved onto VB for windows until .NET came out. Then I dabbled in Delphi, Python, and PHP until I discovered QB64 in 2010.
He did, and I think as QB64 improved, he was able to make the conversion.

Pete
Shoot first and shoot people who ask questions, later.
Reply
#23
upx unzips the exe and then runs it, if I remember correctly. So, technically, the exe is still the same size. Actually, it's larger. Because you're storing the compressed exe and then upx dumps the uncompressed to a temp folder. So now you're storing 1.5x the size.
Tread on those who tread on you

Reply
#24
(08-16-2024, 12:22 PM)SpriggsySpriggs Wrote: upx unzips the exe and then runs it, if I remember correctly. So, technically, the exe is still the same size. Actually, it's larger. Because you're storing the compressed exe and then upx dumps the uncompressed to a temp folder. So now you're storing 1.5x the size.

That depends on the executable format and the environment. For example, UPX decompresses Linux ELF and Windows PE/COFF executables directly to the RAM. In most cases, UPX compressed executables can run without issues in a read-only and limited storage environment.

However, there are some quirks that users should be aware of on certain platforms - https://github.com/upx/upx/blob/devel/doc/upx-doc.txt
Reply




Users browsing this thread: 1 Guest(s)