>> Yeah, 64bit nsiwrwapper cannot use a 32bit ndis driver for the same >> reason >> that 64bit mplayer cannot use win32codecs (though for the latter you can >> run a 32bit mplayer in a chroot). > > Actually that makes much more sense. I thought I was reading > ndiswrapper was not ported to 64bit so it couldn't access the proper > 64bit driver. In any case it is all a painful road which I will > eventually trod on. > >> Do you have the urge to allocate >4GB of a memory to a process? If not, >> most of the reason for using a 64bit OS are gone. In fact, running a >> 32bit OS on a 64bit amd64 processor is probably going to be slightly >> faster than a 64bit OS for many things. > > I would think (and I'm most likely wrong) that if you had >4GB of memory > you wouldn't be able to address it for even 4k of allocation in 32 bit > mode.
The OS can address 2^32 or around 8gigs on 32 bit systems. Most OSes limit the address space that can be used for applications. I believe it is about 4 gigs on XP and 32bit Linux and 6gigs on Windows 2003 Server. If you have more than 8gigs or memory you have to use overlays which is PITA. I suspect that those that actually need that much address space will use 64 bit processors. _______________________________________________ RLUG mailing list [email protected] http://lists.rlug.org/mailman/listinfo/rlug
