C:\Program Files\Common Files\McAfee\Engine\avv*.dat
Nuff said

BESM-4 manuals (pdf):
Manual chapter: external devices code table is on PDF page 13
Machine command poster Printer self-test output is at the top of page 2
BESM-4 is M-220 and M-20 compatible. M-20 was released to production in 1958.

I live in belgium, one exploded here too. I also heard about one exploding the Netherlands.

In Microsoft's defense (dangerous here I know) the vast majority of Vista problems HAVE been resolved months if not years ago. Further, most of those were hardware issues (nVidia..) and sloppy programming of other programs and thus NOT Microsofts fault. The single biggest obstacle it faces now are uninformed customers who heard "their computer guy" tell them two years ago that vista = evil and now refuse to listen to anything otherwise.

Sure there are some that still have problems, but most of them would have problems on a computer no matter the OS. Vista as it is today and during the mojave ads is actually very nice.

Microsoft acknowledged their problems (even though they weren't actually at fault), resolved them, and then tried to inform consumers that they had been fixed. Apple is rather just saying its not our fault to begin with.

I take it you've missed the last twenty Slashdot articles about this. The problem is that many of these books are rare (so the library won't have a physical copy) and still in copyright (so the library can't provide a digital copy legally). Google gets around the second point by having settled a class-action lawsuit which allows them to copy any books that they like. No other organisation has this, and until copyright law is sufficiently reformed or the settlement is thrown out under antitrust legislation (it's currently under review) this will continue to be a problem.

Extra extra: the reason 32-bit XP-SP2|Vista limit address space to 4GB (that is, PCI space combined with memory) is because they don't trust driver writers to do the right thing when DMA buffers straddle 4G boundary.

Who modded parent up? Totally misleading.

Windows /3GB switch controls amount of virtual memory available to a process. Not physical. Virtual. The rest of virtual memory space goes to OS. Low memory (2 or 3 GB) is user process visible (ring3) memory. The upper 2 or 1 GB are ring0 memory. No need to change memory mapping (no need to flush TLB) on a simple syscall that goes back to the same process. Linux does the same thing. [OSX prefers to give userland 4GB virtual memory]

The fact you need /3GB switch illustrates that there are applications that need more than 2GB of virtual space per process. What if you run a number of these apps? Does 4GB look like a lot of memory now?

In fact, Crysis on 64bit Vista with very high settings and res can start swapping to disk because it outgrows 4GB. This is a single app plus graphics drivers.

And, the #1 reason to have virtual memory: memory-mapped files.

Looks a lot like Spiral without wings (or Spiral with wings folded during reentry)