ðòïåëôù 


  áòèé÷ 


Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 

  óôáôøé 


  ðåòóïîáìøîïå 


  ðòïçòáííù 



ðéûéôå
ðéóøíá












     áòèé÷ :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

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

[filmscanners] Re: Windows Memory Mgt.




"Tom Scales" <tscales@attglobal.net> wrote:
>>>>>>>>>>

It's fairly common knowledge to anyone that works in the field (which I do).
Actually, it goes back a touch farther, as NT's memory management is an
evolution of both OS/2 and Vax VMS.  Best of both worlds, so to speak.

As NT (and subsequently 2000 and XP) were never built on top of DOS, nor did
they attempt backwards DOS compatability, they were true 32-bit operating
systems right from the start.  Memory addressing is well beyond what we have
in our PCs.  Memory management was always a strength, as was the fact that
they were true premptive multitasking operating systems for many years
before it was a feature available in a Mac OS.
<<<<<<<<<<<

All very true, but NT/2k/XP give the user a single, flat 2GB address space,
which is getting a bit cramped in this day and age of 4000dpi MF scanners.
(Hmm. I wonder if that can be gotten around by having a thread object with
it's own address space for each image.)

David J. Littleboy
davidjl@gol.com
Tokyo, Japan



----------------------------------------------------------------------------------------
Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe 
filmscanners'
or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or 
body



 




Copyright © Lexa Software, 1996-2009.