Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.msdos.programmer > #2327
| From | pete@nospam.demon.co.uk |
|---|---|
| Newsgroups | comp.os.msdos.programmer |
| Subject | Re: 16 bit code |
| Date | 2016-11-27 07:15 +0000 |
| Organization | PDL |
| Message-ID | <1480230920snz@nospam.demon.co.uk> (permalink) |
| References | <o1cv35$n1s$1@dont-email.me> <o1d437$14dp$1@gioia.aioe.org> |
On 26th Nov 2016 at 22:58 "Ross Ridge" <rridge@csclub.uwaterloo.ca> wrote:
> 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.
>
> It's not valid Intel code, either in 16-bit mode or 32-bit mode.
> It's probably some sort of data.
>
> Note that you can give any file an extension of .SYS, so it's not
> necessarily an MS-DOS device driver just because it has that extension.
>
> Ross Ridge
Agreed - CONFIG.SYS is no device driver! This certainly doesn't look
like any normal sort of DOS device driver, which would start with
FFFFFFFF, e.g.
org 0
;start of header
dd -1 ; link to next driver - set by DOS
dw ? ; device attribute
dw offset STRATEGY ; pointer to strategy routine
dw offset INTERRUPT ; pointer to interrupt routine
db 'ABCDEFGH' ; 8 bytes for device name
RHaddr dw ?, ? ; storage for request header address
etc...
For example, this is what the start of ANSI.SYS looks like (DOS 6.22):
C:\DOS>debug ansi.sys
-d
0C1D:0100 FF FF FF FF 53 C0 C1 00-CC 00 43 4F 4E 20 20 20 ....S.....CON
0C1D:0110 20 20 5E 10 70 01 70 01-70 01 83 03 43 04 70 01 ^.p.p.p...C.p.
0C1D:0120 D7 04 03 05 03 05 70 01-70 01 70 01 70 01 70 01 ......p.p.p.p.p.
0C1D:0130 70 01 70 01 70 01 70 01-27 0A 41 6B 06 42 73 06 p.p.p.p.'.Ak.Bs.
0C1D:0140 43 5B 06 44 66 06 48 2D-06 4A E7 06 4B 24 07 52 C[.Df.H-.J..K$.R
0C1D:0150 5D 07 66 2D 06 68 64 07-6C 60 07 6D B7 06 6E 38 ].f-.hd.l`.m..n8
0C1D:0160 07 70 A1 07 71 88 06 73-A5 06 75 AE 06 00 00 00 .p..q..s..u.....
0C1D:0170 07 01 FF 08 04 F8 01 05-FF 80 07 F8 70 08 88 00 ............p...
-q
So your code looks to me like it's some sort of data file used by some
proprietary application.
Pete
--
Believe those who are seeking the truth.
Doubt those who find it. - André Gide
Back to comp.os.msdos.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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