> As a windows programmer who designs medical imaging graphics workstations, this is > a > problem I have had do deal with under windows for close to 10 years... This is > caused by the split between user space and kernel space which limits an > application > to 2GB kernel / 2GB user. The problem with this is once you factor in that every > windows application needs to map dlls to its user application space and these dlls > do not load in a manner that conserves application space (they actually load in a > scattered manner in the high user space area) the largest array that you can > allocate in 32 windows (without the 3GB switch) is about 1.2GB. Since windows 2000 > advanced server there is a new switch in your boot.ini file that enables a 3GB / > 1GB > split so it will be possible to load dlls a little higher in memory thus giving > you > a larger available address space. Now how does this all apply to wine. I believe > wine properly emulates windows design feature and I think there is also a way for > it to emulate the 3GB feature as well but I do not know the details of this on > wine. > Sorry. > > John > Oops, sorry I did not read your post clearly enough. Darn multitasking... John _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
