Re: Looking for a Library Disassembler for X86

On Dec 20, 12:17 am, "Wolfgang Kern" <spamt...@xxxxxxxxxx> wrote:

Thanks Arargh, but my OS wont execute 'foreign' code.
So I'd need just the information to complete my source converter ...

__
wolfgang

Wolfgang,
There may be a problem executing old DOS programs on Windows 2000 NT
or Windows XP.

If you see "Error: Stack Overflow 2000" or the equivalent, you may
need to give the .exe file more stack space than the usual 8K (#0800).
I modify bytes 16 and 17 of the header to 00 C0, using exemod.exe
(which itself needs the same treatment, so you need another earlier
computer or ask me for a modified copy).

That problem comes from Microsoft using the user stack for security
purposes.

.

Relevant Pages

  • Re: Looking for a Library Disassembler for X86
    ... So I'd need just the information to complete my source converter ... ... There may be a problem executing old DOS programs on Windows 2000 NT ...
    (comp.lang.asm.x86)
  • Re: singe thread per connection
    ... process is about 2000, with the practical maximum somewhat lower, and performance suffering significantly before that. ... If you use a different stack size than the default, or don't actually allocate one OS thread per Java thread, then the actual limit would be different. ... But in Windows, both in the regular Win32 API and under .NET, there are i/o mechanisms that can be used that allow a single thread to service an arbitrarily large number of i/o tasks. ... This allows a program to create just enough threads to keep all the CPU cores busy, and the Windows scheduler knows to treat those threads specially so that if the only other runnable thread is one that would do the same thing that the currently running thread would do, the currently running thread is allowed to just keep running, rather than being preempted for no good reason. ...
    (comp.lang.java.programmer)
  • Re: Iczelions tutorials revisited.
    ... By "local" variables on the stack I assume something like this? ... access parameters and locals that way. ... The Windows API uses "stdcall" in which "callee cleans up stack" - the Windows functions end with "ret N". ... Being an old dos-head, I'm used to using cx as a "counter", and it annoys me that calling libc or the Windows API is allowed to trash it, but that's life... ...
    (alt.lang.asm)
  • Re: Is MASM32 an evil Microsoft plot?
    ... Now your next blunder is to call the default windows message handler ... > you could use most any assembler and the whole advocacy for MASM disappears. ... C3;; retn ... Is there supposed to be some profundity at addressing the stack ...
    (alt.lang.asm)
  • Re: Need some help understanding array definitions
    ... their Windows product, ... Windows and DLL calls, and I'm sure MPE's equivalents address the same ... space available on the return stack at any given time. ... We don't have ALLOCATE or local buffers, ...
    (comp.lang.forth)