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

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

Re: 16 bit code

From Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem>
Newsgroups comp.os.msdos.programmer
Subject Re: 16 bit code
Date 2016-11-27 21:20 -0500
Organization Aioe.org NNTP Server
Message-ID <20161127212001.74258b3e@_> (permalink)
References <o1cv35$n1s$1@dont-email.me> <583a9ad7$0$21545$e4fe514c@news.xs4all.nl> <o1fcjg$ht2$1@dont-email.me>

Show all headers | View raw

On Sun, 27 Nov 2016 14:37:35 -0500
"Bill Cunningham" <nospam@nspam.invalid> wrote:

> oakcdrom.sys. Tht came with win98. So that would be 32 bit.

No.

Windows 98/SE starts with 16-bit MS-DOS which has been modified to work
with Windows 98/SE.  This DOS uses some undocumented M$ APIs to
transfer control to 32-bit Windows.  Windows has it's own device drivers
that can't be used with DOS.  So, any standalone device driver is going
to be 16-bit DOS code.

AFAIK, there is no 32-bit device driver format for DOS.  Although, in
theory, it's possible to have 32-bit drivers for DOS, which would work
with 32-bit DPMI apps.  These drivers, of course, likely wouldn't be
coded to work with regular 16-bit DOS apps.  The DPMI host and XMS
drivers would need to support some additional protocols, like GEMMIS.
This might also be possible with a VCPI host.  The DPMI protocols were
originally developed by M$ for a 32-bit DOS, but they killed that DOS
before it was ever released, and went with developing Windows.

Albeit, at this point in time, it appears no one is going to develop a
32-bit DOS.  FreeDOS-32 was a decent attempt while it lasted.


Rod Pemberton

Back to comp.os.msdos.programmer | Previous | Next — Previous 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