Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!rochester!kodak!uupsi!sunic!sics.se!fuug!fuug.fi!pena From: pena@brainware.fi (Olli-Matti Penttinen) Newsgroups: comp.windows.ms.programmer Subject: Re: UAE's - how are they detected Message-ID: Date: 29 May 91 11:23:13 GMT References: <1991May25.054957.1151@mnemosyne.cs.du.edu> <1991May28.173139.8139@hyper.hyper.com> Sender: usenet@fuug.fi (USENET News System) Organization: Brainware Oy, Espoo, Finland. Lines: 27 In-Reply-To: bonneau@hyper.hyper.com's message of 28 May 91 17: 31:39 GMT Nntp-Posting-Host: brainw.brainware.fi In article <1991May28.173139.8139@hyper.hyper.com> bonneau@hyper.hyper.com (Paul Bonneau) writes: Once we have win32 (now called Windows 4 apparently) where an application will have a virtual address space of several gigabytes, wild writes will be much harder to detect. cheers - Paul Bonneau. Quite the opposite, I think. In Windows 3.0 all applications except for DOS boxes share the same address space, thus allowing an application to merrily overwrite any data, including Windows' itself. With a full 386 addressing scheme, this becomes impossible. By the same token, a 32 bit virtual address space DOES NOT mean that all addresses are valid. You can only use memory that the operating system gave you and none else. Think about it: virtual memory is not endless, either. For a virtual address to be valid, the page must be in RAM or stored in the swappping/paging device. I doubt very many machines have the luxury of being able to allocate 4 GB RAM/diskspace for each task :-) ==pena -- Olli-Matti Penttinen | "When in doubt, use brute force." Brainware Oy | --Ken Thompson P.O.Box 330 +---------------------------------- 02151 ESPOO, Finland Tel. +358 0 4354 2565 Fax. +358 0 461 617