RE: A89: Fw: 32 bit TI Graph Link Software


[Prev][Next][Index][Thread]

RE: A89: Fw: 32 bit TI Graph Link Software




What about INtle's new processors such as the Katami (sp?) and Merced?

-- 
Bryan Rabeler <brabeler@ticalc.org>
   File Archives, News, Features, Newsletter, and HTML
   the ticalc.org project - http://www.ticalc.org/

On Tue, 6 Oct 1998, Clayton L. Workman wrote:

> 
> > programs that make 16bit calls will not run on an NT system.  Perhaps
> 
> This is incorrect.  NT on Pentium and Pentium II will run 16-bit programs
> but in a slower reserved memory space.  NT on a Pentium Pro will not run
> 16-bit at all, but this is due to the Pro processor, not NT.
> 
> Clayton
> 
> > MicroSoft will put some 16-bit support in NT 5, but that only slows down
> > an allready slow product.  If you want to run a 16-bit app, you'd better
> > stick with win98 or lower, or get ahold of the developer of that app,
> > and find out what options they have.  Otherwise you're up a creek
> > without a paddle.
> >
> > As long as the code is making 32-bit calls, it's ok.  If TI says it's NT
> > compatible, that means that you can run it on a clean installation of
> > NT(in other words, you shouldn't need any special drivers or other stuff
> > to get it working)
> >
> > -Adam
> >
> > Bryan Rabeler wrote:
> > >
> > > What about running 16-bit software on NT?
> > >
> > > --
> > > Bryan Rabeler <brabeler@ticalc.org>
> > >    File Archives, News, Features, Newsletter, and HTML
> > >    the ticalc.org project - http://www.ticalc.org/
> > >
> > > On Mon, 5 Oct 1998, Adam Davis wrote:
> > >
> > > >
> > > > The difference is not so much in the code(NT is comprised of a
> > > > 'surprising'(not really, hey, it's microsoft we're talking about
> > > > here...) amount of 16 bit code)  but in the way you call the code.
> > > >
> > > > Win31 supports 16-bit API calls.  The win32 extensions add a
> > few 32 api
> > > > calls, but mainly puts some alliases so that many 32-bit calls can be
> > > > rerouted to 16-bit code.
> > > >
> > > > Of course, microsoft knew 16-bit wasn't enough, and went to 32 bit API
> > > > calls with winnt.  It didn't support 16 bit calls.  win95 and
> > 98 support
> > > > both 16 and 32 bit calls.
> > > >
> > > > So the 16 and 32 is not so much a matter of code, but the way
> > > > universally-available code is called.
> > > >
> > > > I hope this helps.
> > > >
> > > > -Adam
> > > >
> > > > Bryan Rabeler wrote:
> > > > >
> > > > > I was under the impression that NT was pure 32-bit.
> > > >
> >
> 


Follow-Ups: References: