Mail Archives: djgpp/1997/02/02/02:07:33
Robert Vasquez <digital DOT fx AT worldnet DOT att DOT net> wrote:
>> Linux is obviously not for me. Maybe I'll try FreeBSD, or the Que
>> Linux CD-ROM one day. Que book+products always seem to work well
>> for me. However, I'm not going to claim Linux is an absolute piece
>> of junk. Now, are you going to claim Borland's is because you
>> couldn't get it working right? Only if your 3 years old maybe.
>Well, sorry to break it to ya, but other than maybe Symantec, Borland's
>C/C++ products are about the worst. Their glory days of TurboC 3.1 are
>over man . . .
Hmm, are you sure? or did *YOU* just have a bad experience. I still
hear good things about BC++ everywhere I turn. Like I mentioned, some
bugs are actually windows API bugs borland can do nothing about, and
the others are generally patched within 3-4 weeks at most.
>>>What planet are you from?
>> You might want to answer this one yourself after your two false
>> assumptions there, Mac. I have patched commercial software using3
>> debug before, it is POSSIBLE! In fact, I patched EDIT using ASCII
>> coding techniques for machine code in EDIT. It is utterly amazing
>> what one do when one is determined. Granted I would have preferred
>> HLL src code to patch, I got the task accomplished just the same.
>What exactly did you patch? Sounds kinda funny to me
In reguards to Edit, I patched the QBASIC.EXE file so that *.TXT was no
longer the default file type, but rather *.* was.
As to what I patched with debug? I've patched old releases of
command.com, MORE, and old version of sys.comm products like uu.com,
grep.com, etc.. debug is merely x86 asm without labels. TYhe EDIT trick
was a bit more difficult. I had lost debug somehow, found it the day
after, of course. I had an old 8088 opcode-mnumonic manual a frined let
me borrow, and I usd CTRL+P and ALT + ??? to write machine code uasing
ASCII character.
- Raw text -