search for: _generally_

I haven't done much with Folder Redirection yet (gosh, I really need to), but are Junctions and Symlinks _generally_ redirected/transferred cleanly?

...t be paired with a 16-bit depth format, and a 32-bit color format must be paired with a 32-bit depth format (well, Z24S8). This HW also can't handle different per-attachment sizes, and also the "linearity" of all the attachments must be the same. (Whether a surface is linear or not is _generally_ dictated by its w/h, but not always -- POT textures can sometimes end up allocated linearly by e.g. the ddx, or something else.) The different sizes are handled by not exposing ARB_fbo. However the rest of the cases remain. Now that I kinda understand how things are structured, I was thinking of d...

...epth format, and a 32-bit color format must be paired with a >> 32-bit depth format (well, Z24S8). This HW also can't handle different >> per-attachment sizes, and also the "linearity" of all the attachments >> must be the same. (Whether a surface is linear or not is _generally_ >> dictated by its w/h, but not always -- POT textures can sometimes end >> up allocated linearly by e.g. the ddx, or something else.) The >> different sizes are handled by not exposing ARB_fbo. However the rest >> of the cases remain. >> >> Now that I kinda unde...

...t color format must be paired with a >>>> 32-bit depth format (well, Z24S8). This HW also can't handle different >>>> per-attachment sizes, and also the "linearity" of all the attachments >>>> must be the same. (Whether a surface is linear or not is _generally_ >>>> dictated by its w/h, but not always -- POT textures can sometimes end >>>> up allocated linearly by e.g. the ddx, or something else.) The >>>> different sizes are handled by not exposing ARB_fbo. However the rest >>>> of the cases remain. >&gt...

...aired with a >>>>>> 32-bit depth format (well, Z24S8). This HW also can't handle different >>>>>> per-attachment sizes, and also the "linearity" of all the attachments >>>>>> must be the same. (Whether a surface is linear or not is _generally_ >>>>>> dictated by its w/h, but not always -- POT textures can sometimes end >>>>>> up allocated linearly by e.g. the ddx, or something else.) The >>>>>> different sizes are handled by not exposing ARB_fbo. However the rest >>>>>&...

Hi, How can you modify the pre-login message with ssh, before the "login as:"? In Unix this can be done with herald variable in /etc/security/login.cfg. Thanks Philip _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

...; a 16-bit depth format, and a 32-bit color format must be paired with a > 32-bit depth format (well, Z24S8). This HW also can't handle different > per-attachment sizes, and also the "linearity" of all the attachments > must be the same. (Whether a surface is linear or not is _generally_ > dictated by its w/h, but not always -- POT textures can sometimes end > up allocated linearly by e.g. the ddx, or something else.) The > different sizes are handled by not exposing ARB_fbo. However the rest > of the cases remain. > > Now that I kinda understand how things are st...

To reduce the space occupied by Thunderbird IMAP Cache, i've found this: https://bugzilla.mozilla.org/show_bug.cgi?id=517425#c49 and seems works as expencted. I've a bit extended to link also global-messages-db.sqlite (eg, global search index). But after that, i don't find in roaming profile (server side) the link created with mklink. Link are not supported by samba? Thanks. --

...and a 32-bit color format must be paired with a >>> 32-bit depth format (well, Z24S8). This HW also can't handle different >>> per-attachment sizes, and also the "linearity" of all the attachments >>> must be the same. (Whether a surface is linear or not is _generally_ >>> dictated by its w/h, but not always -- POT textures can sometimes end >>> up allocated linearly by e.g. the ddx, or something else.) The >>> different sizes are handled by not exposing ARB_fbo. However the rest >>> of the cases remain. >>> >>&g...

...at must be paired with a >>>>> 32-bit depth format (well, Z24S8). This HW also can't handle different >>>>> per-attachment sizes, and also the "linearity" of all the attachments >>>>> must be the same. (Whether a surface is linear or not is _generally_ >>>>> dictated by its w/h, but not always -- POT textures can sometimes end >>>>> up allocated linearly by e.g. the ddx, or something else.) The >>>>> different sizes are handled by not exposing ARB_fbo. However the rest >>>>> of the cases...

I do lots of analyses on large microarray data sets so memory use and speed and both important issues for me. I have been trying to estimate the overheads associated with using formal S4 data objects instead of ordinary lists for large data objects. In some simple experiments (using R 1.7.1 in Windows 2000) with large but simple objects it seems that giving a data object a formal class