Search found 3 matches
- Tue Jul 20, 2010 11:00 am
- Forum: QBASIC and QB64 Questions & Answers
- Topic: decompiling QuickBasic 2.0 compiled execuables
- Replies: 3
- Views: 13322
Above post is of a program compiled with debug on
When I compiled the program above, I had the DEBUG flag checked in the compiler. That is why all the lines start with CD 3F 59. If compiled without the DEBUG flag on, the code starting at CD 3F 59 to the next CD is not there.
- Tue Jul 20, 2010 6:15 am
- Forum: QBASIC and QB64 Questions & Answers
- Topic: decompiling QuickBasic 2.0 compiled execuables
- Replies: 3
- Views: 13322
More interesting finds (at least I think so)
I've further discovered that my original assumptions about what executes the Basic binary Code were wrong. After disassembling BRUN20.EXE a little further it seems that BRUN20.EXE pataches the INterrupt 3D, 3E and 3F vectors to intercept them. The Basic Binary code contained in segment 0 of the comp...
- Fri Jul 16, 2010 9:06 am
- Forum: QBASIC and QB64 Questions & Answers
- Topic: decompiling QuickBasic 2.0 compiled execuables
- Replies: 3
- Views: 13322
decompiling QuickBasic 2.0 compiled execuables
I have been working on a program to decompile .exe files that were compiled with QB20 (exe's that require BRUN20.EXE to run). I have come to the conclusion that the compiled program has a stub attached as the third segment of the exe that loads BRUN20.EXE and QUICKPAK.EXE (if used) and then starts t...