Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.msdos.programmer > #2333

Re: 16 bit code

From rridge@csclub.uwaterloo.ca (Ross Ridge)
Newsgroups comp.os.msdos.programmer
Subject Re: 16 bit code
Date 2016-11-27 20:59 +0000
Organization Aioe.org NNTP Server
Message-ID <o1fhg1$rgd$1@gioia.aioe.org> (permalink)
References <o1cv35$n1s$1@dont-email.me> <o1d437$14dp$1@gioia.aioe.org>

Show all headers | View raw


Bill Cunningham <nospam@nspam.invalid> wrote:
>    This is a disasssembly of a driver code. The ext was .sys. Which is DOS 
>is probably always a driver. Does anyone know what it's saying. There's no 
>ints called. This isn't source code. Maybe you can't get that from a 
>disassembly.

Ross Ridge <rridge@csclub.uwaterloo.ca> wrote:
>It's not valid Intel code, either in 16-bit mode or 32-bit mode.
>It's probably some sort of data.

I think I figured out what it is.  As it happens, I ran DEBUG under
MS-DOS 6.22 (running in a VM) and saw the exact same disassembly despite
the fact that I didn't give it a file name to load, let alone that of
the file you're trying to disassemble.  That means the "code" that I
disassembled is just whatever happened to be left in memory by whatever
else was using it before.

That "code" is probably a transient data buffer allocated by COMMAND.COM,
which freed it (but didn't erase it) before running DEBUG (or any other
command).  That frees up space for the program being run.

I'm guessing your problem is either DEBUG wasn't able to load your driver,
or you didn't actually specify a file on the command line for it to load.

					Ross Ridge

-- 
 l/  //	  Ross Ridge -- The Great HTMU
[oo][oo]  rridge@csclub.uwaterloo.ca
-()-/()/  http://www.csclub.uwaterloo.ca/~rridge/ 
 db  //	  

Back to comp.os.msdos.programmer | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

16 bit code "Bill Cunningham" <nospam@nspam.invalid> - 2016-11-26 16:34 -0500
  Re: 16 bit code Harry Potter <rose.joseph12@yahoo.com> - 2016-11-26 14:38 -0800
    Re: 16 bit code Harry Potter <rose.joseph12@yahoo.com> - 2016-11-26 14:40 -0800
  Re: 16 bit code rridge@csclub.uwaterloo.ca (Ross Ridge) - 2016-11-26 22:58 +0000
    Re: 16 bit code pete@nospam.demon.co.uk - 2016-11-27 07:15 +0000
    Re: 16 bit code rridge@csclub.uwaterloo.ca (Ross Ridge) - 2016-11-27 20:59 +0000
  Re: 16 bit code Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2016-11-26 20:08 -0500
  Re: 16 bit code "R.Wieser" <address@not.available> - 2016-11-27 09:38 +0100
    Re: 16 bit code "Bill Cunningham" <nospam@nspam.invalid> - 2016-11-27 14:37 -0500
      Re: 16 bit code "R.Wieser" <address@not.available> - 2016-11-27 21:42 +0100
      Re: 16 bit code Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2016-11-27 21:20 -0500
    Re: 16 bit code "Bill Cunningham" <nospam@nspam.invalid> - 2016-11-27 14:47 -0500
      Re: 16 bit code "R.Wieser" <address@not.available> - 2016-11-27 21:59 +0100
        Re: 16 bit code "Bill Cunningham" <nospam@nspam.invalid> - 2016-11-27 16:40 -0500
          Re: 16 bit code "R.Wieser" <address@not.available> - 2016-11-28 08:34 +0100
        Re: 16 bit code rugxulo@gmail.com - 2016-11-27 14:08 -0800
          Re: 16 bit code "Bill Cunningham" <nospam@nspam.invalid> - 2016-11-27 17:47 -0500
            Re: 16 bit code "Bill Cunningham" <nospam@nspam.invalid> - 2016-11-27 17:49 -0500
      Re: 16 bit code Jim Leonard <MobyGamer@gmail.com> - 2017-01-04 11:05 -0800

csiph-web