Feung

[quote name='http://forums.xisto.com/no_longer_exists/ Does the X38 Like many manufacturers, Gigabyte showcased their upcoming Intel X38 based motherboards during last month's Computex 2007 trade show in Taipei. Today, we've managed to get a closer look at the board based on the first Intel chipset to replace the 975X Express in the enthusiast desktop segment. You may think that the P965 and P35 chipsets are hot, but they are really just Intel's mainstream offerings; The X38 is supposed to outclass them by a fair bit. Think PCI Express 2.0, dual PCIe x16 graphics (finally), quad core extreme edition processors and no overspeed protection on the chipset, which is essentially equal to a car manufacturer selling a car without the brakes. We can already see the hunger of anticipation in overclockers, but there's more good news for gaming as well. As the rumor mill spins, the X38 could have NVIDIA's blessing for SLI support as well, which would make the X38 the first chipset to have dual X16 PCIe graphics supporting both ATI CrossFire and SLI, a godsend for gamers worldwide. At the moment Gigabyte has announced two X38 boards in the pipelines, the GA-X38-DQ6 and the GA-X38T-DQ6. The former will be a strict DDR2 board while the latter will feature DDR3. As their names imply, both boards will be flagship models based on Gigabyte's extreme 6-Quad technologies. Interestingly, Gigabyte has chosen to back away from the extremely over-engineered design that last appeared on the NVIDIA nForce 680i SLI based GA-N680SLI-DQ6. In fact, as one of the highest end motherboards Gigabyte will have, the X38 DQ6 boards look incredibly nondescript with their 'regular' Silent-Pipe solution that looks tamer even than its 'mainstream' cousin, the GA-P35-DQ6. As their new and upcoming flagship enthusiast boards, the GA-X38-DQ6 and GA-X38T-DQ6 should both appear in retail channels by September 2007. We've also been told by Gigabyte that they will not focus entirely on the high-end market with the X38 and that they are readying additional motherboard SKUs based on this chipset for the mid-range segment too. No news on what these boards might be or how it would impact features, but this is another piece of good news for consumers as it may possibly put X38 motherboards within the reach of the average knowledgeable Joe. We will bring you more information as soon as we are able to. Till then, this little sneak peek should tide you over. Notice from vizskywalker: Be sure you place copied material in quote tags

https://www.google.com/codesearch Google Code Search helps you find function definitions and sample code by giving you one place to search publicly accessible source code hosted on the Internet. With Google Code Search, you can: * Use regular expressions to search more precisely * Restrict your search by language, license or filename * View the source file with links back to the entire package and the webpage where it came from

Windows Vista and OpenGL-the Facts April 20, 2007 The Khronos OpenGL ARB Working Group has received requests for clarification concerning the performance of OpenGL on Windows Vista. These questions are understandable as Microsoft has dramatically changed the user experience with the Windows Aero compositing desktop and introduced a completely new display driver architecture. This article will discuss how these changes affect OpenGL. The industry now has a growing body of real-world experience in shipping OpenGL on Windows Vista and the OpenGL ARB wishes to reinforce the positive synergy between OpenGL graphics and Windows Vista in three key areas Windows Vista fully supports hardware accelerated OpenGL; OpenGL applications can benefit from Window Vista•s improved graphics resource management; OpenGL performance on Windows Vista is extremely competitive with the performance on Windows XP. Windows Vista Fully Supports OpenGL Hardware-accelerated OpenGL is fully supported on Windows Vista with the Windows Aero compositing desktop user experience - just as with Direct3D. OpenGL hardware acceleration is handled in exactly the same way in Windows XP and Windows Vista - through an Installable Client Driver (ICD) provided by graphics card manufacturers. Without an OpenGL ICD installed, Windows XP and Windows Vista both revert to rendering OpenGL in software on the CPU rather than using GPU acceleration. Figure 1 shows the path through which OpenGL and Direct3D applications render their output under Windows Vista. Firstly, the OpenGL or Direct3D user-mode graphics drivers take the data from the application and use the graphics hardware to render one frame of content. That frame is then presented to the Desktop Window Manager (DWM) which composites the frame into the desktop using GPU acceleration. The DWM provides the desktop compositing functionality used by the Windows Aero and Windows Standard user experiences in Windows Vista. The DWM is a key element of the Windows Vista user experience and one of its main functions is to manage the presentation of the Windows desktop by compositing the outputs of multiple applications to the screen. As a complete 3D application in its own right, the DWM uses GPU memory and resources and places an additional load on the GPU, which impacts application graphics performance by approximately 10% for typical applications. End users should weigh the benefits of the DWM and the Windows Aero user interface against this performance cost. An easy way to experiment with a particular application is to disable the DWM, by selecting the Windows Classic or Windows Basic user interface style. During full-screen applications, such as games, the DWM is not performing window compositing and therefore performance will not appreciably decrease. Figure 1 - OpenGL, Direct3D and the Desktop Window Manager (DWM) OpenGL Benefits from Improved Resource Management The new Windows Display Driver Model (WDDM) in Windows Vista provides a firewall and the thunk layer (that handles communication between the graphics hardware/kernel mode graphics driver and the user-mode graphics driver) to increase overall system stability. This architecture differs from Windows XP, where the OpenGL ICD talked directly to the GPU hardware and handled many low-level functions, including memory management. WDDM affords some implicit benefits for OpenGL applications. For example, graphics resources previously managed by the OpenGL ICD, such as video memory, are now virtualized by the operating system. When multiple applications are running, the OpenGL ICD exposes maximum texture storage capacity to each application and Windows Vista takes care of resource allocation and scheduling, resulting in more efficient use of resources across applications. OpenGL Performance is Competitive on Windows Vista Some have suggested that OpenGL performance on Windows Vista is poor compared to Windows XP. This is not the case. A comparison between the performance on Windows XP and Windows Vista of the SPECviewperf professional OpenGL benchmark, two OpenGL game benchmarks, and two Direct3D game benchmarks are presented below. Professional OpenGL Application Performance The SPECviewperf figure below shows that the graphics performance of professional OpenGL applications on Windows Vista is very close to that on Windows XP. SPECviewperf runs in a window, and on Windows Vista the DWM was turned off, by selecting the Windows Classic color scheme, to achieve maximum graphics performance. These numbers are extremely impressive, given that the WDDM is a radical departure from the Display Driver model on Windows XP and the new Windows Vista drivers have not yet benefited from the years of tuning and optimization that the Windows XP OpenGL drivers have undergone. Software developers and graphics card manufacturers have had access to production-ready Windows Vista since November 2006, and graphics performance on Windows Vista will continue to improve over time as the drivers mature. As with any version of Microsoft Windows however, it is important to download the latest drivers from the graphics card vendor - particularly in the early lifetime of a new operating system. If DWM were enabled through enabling Windows Aero - performance would drop by about 10%. For many users this tradeoff is worthwhile in order to use the more advanced user interface. OpenGL Game Performance The Doom3 (demo1) and Prey (move.demo) figures below show that Windows Vista performance for full-screen OpenGL games is comparable to the performance delivered on Windows XP. As these applications are full screen, DWM is not active and there is no performance drop in Windows Aero. Direct3D Game Performance The diagram below shows how the Direct3D games Half Life 2 Episode One (demo1) and Oblivion (Outdoor, HDR off) perform on Windows XP and Windows Vista. These numbers were obtained on the same system and same driver versions as the OpenGL benchmarks. In all cases the benchmarks were run in full-screen mode. These figures show that Windows Vista performance for full-screen Direct3D games is comparable to the performance delivered on Windows XP • just as for OpenGL. As these applications are full screen, DWM is not active and there is no performance drop in Windows Aero. These results confirm that both Direct3D and OpenGL are excellent 3D APIs for Windows Vista. Conclusion OpenGL is fully integrated into the Windows Vista display architecture just like Direct3D -both interfaces are first-class graphics API citizens. OpenGL hardware acceleration is available on Windows Vista through highly optimized drivers provided by the graphics hardware vendor just as on Windows XP. OpenGL applications can benefit from the improved resource management provided by Windows Vista. OpenGL performance on Windows Vista is extremely competitive compared to Windows XP and will rapidly improve as support for this new operating system matures. The enhanced Windows Aero user interface can decrease graphics intensive application performance by about 10% but this performance drop can be eliminated by selecting Windows Classic or Windows Basic user interface style or using full-screen applications. To ensure maximum performance and stability on Windows Vista, users should regularly check for driver upgrades from their graphics hardware supplier. The third edition of the OpenGL Pipeline Newsletter, an OpenGL ARB publication, has included an article written by NVIDIA for software developers with tips to get the maximum out of their OpenGL application on Windows Vista. This article can be found here: https://www.opengl.org/pipeline/article/vol003_7/ For questions about this article, or about OpenGL in general, please contact Barthold Lichtenbelt at blichtenbelt@nvidia.com, Khronos OpenGL ARB Working Group chair.

this is a quick and dirty how-to to set up a working transparent proxy for small office use. this one is a custom install note. it is NOT compatible with the default RPM packages provided by your linux vendors. use it at your own risk. also note that all the values provided here should be modified according to your specifications. DO NOT use the values as is! overview you have an internet gateway in your office: a. eth0 - external interface (ISP-provided IP) b. eth1 - internal interface (192.168.0.1) you want to place advantages such as web access speed-up, web access monitoring and filtering capabilities to this gateway. i use squid 2.6 in this case and the setup here wouldn't work for versions prior to 2.6. here are the steps. 1. download source from squid-cache.org; create necessary directories; as root: mkdir -p /usr/local/var/squid /usr/local/var/squid/cache /usr/local/var/squid/logs chown -R nobody:nobody /usr/local/var/squid chmod 750 /usr/local/var/squid /usr/local/var/squid/cache /usr/local/var/squid/logs exit 2. ./configure with the following options (this was based on Fedora Core, with modifications) ./configure --prefix=/usr/local \ --sysconfdir=/etc/squid \ --enable-epoll \ --enable-snmp \ --enable-removal-policies="heap,lru" \ --enable-storeio="aufs,coss,diskd,null,ufs" \ --enable-ssl \ --with-openssl=/usr/kerberos \ --enable-delay-pools \ --enable-linux-netfilter \ --with-pthreads \ --enable-ntlm-auth-helpers="SMB,fakeauth" \ --enable-external-acl-helpers="ip_user,ldap_group,unix_group,wbinfo_group" \ --enable-auth="basic,digest,ntlm" \ --enable-digest-auth-helpers="password" \ --with-winbind-auth-challenge \ --enable-useragent-log \ --enable-referer-log \ --disable-dependency-tracking \ --enable-cachemgr-hostname=localhost \ --enable-underscores \ --enable-basic-auth-helpers="LDAP,MSNT,NCSA,PAM,SMB,YP,getpwnam,multi-domain-NTLM,SASL" \ --enable-cache-digests \ --enable-ident-lookups \ --enable-follow-x-forwarded-for \ --enable-wccpv2 \ --enable-fd-config \ --with-maxfd=163843. make 4. sudo make install 5. put the following in /etc/squid.conf (minimum configuration only, see squid.conf.default for more details): http_port 127.0.0.1:3128http_port 192.168.0.1:3128 transparentcache_dir ufs /usr/local/var/squid/cache 100 16 256pid_filename /usr/local/var/squid/logs/squid.pidvisible_hostname gw.office.interncache_mgr bl00d@gw.office.internlogformat combined %>a %ui %un [%tl] "%rm %ru HTTP/%rv" %Hs %<st "%{Referer}>h" "%{User-Agent}>h" %Ss:%Shaccess_log /usr/local/var/squid/logs/access.log squidcache_log /usr/local/var/squid/logs/cache.logcache_store_log /usr/local/var/squid/logs/store.loguseragent_log /usr/local/var/squid/logs/useragent.logreferer_log /usr/local/var/squid/logs/referer.logacl localhost src 127.0.0.1/255.255.255.255acl intern src 192.168.0.0/24acl all src 0.0.0.0/0.0.0.0acl manager proto cache_objectacl to_localhost dst 127.0.0.0/8acl SSL_ports port 443 563acl Safe_ports port 80 21 443 563 70 210 1025-65535acl CONNECT method CONNECThttp_access allow internhttp_access allow localhosthttp_access deny !Safe_portshttp_access deny allacl QUERY urlpath_regex cgi-bin \? asp jsp phpcache deny QUERYfollow_x_forwarded_for deny allhttp_reply_access allow all 6. put the follong in /etc/sysconfig/squid: # default squid options# -D disables initial dns checks. If you most likely will not to have an# internet connection when you start squid, uncomment thisSQUID_OPTS="-D"# Time to wait for Squid to shut down when asked. Should not be necessary# most of the time.SQUID_SHUTDOWN_TIMEOUT=100 7. put the following in /etc/logrotate.d/squid: /usr/local/var/squid/logs/access.log { weekly rotate 5 copytruncate compress notifempty missingok}/usr/local/var/squid/logs/cache.log { weekly rotate 5 copytruncate compress notifempty missingok}/usr/local/var/squid/logs/useragent.log { weekly rotate 5 copytruncate compress notifempty missingok}/usr/local/var/squid/logs/referer.log { weekly rotate 5 copytruncate compress notifempty missingok}/usr/local/var/squid/logs/store.log { weekly rotate 5 copytruncate compress notifempty missingok# This script asks squid to rotate its logs on its own.# Restarting squid is a long process and it is not worth# doing it just to rotate logs postrotate /usr/local/sbin/squid -k rotate endscript}[/quote]8. put the following in /etc/rc.d/init.d/squid:[code]#!/bin/bash# squid This shell script takes care of starting and stopping# Squid Internet Object Cache## chkconfig: - 90 25# description: Squid - Internet Object Cache. Internet object caching is \# a way to store requested Internet objects (i.e., data available \# via the HTTP, FTP, and gopher protocols) on a system closer to the \# requesting site than to the source. Web browsers can then use the \# local Squid cache as a proxy HTTP server, reducing access time as \# well as bandwidth consumption.# pidfile: /usr/local/var/squid/logs/squid.pid# config: /etc/squid/squid.confPATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/sbin:/bin:/usr/sbinexport PATH# Source function library.. /etc/rc.d/init.d/functions# Source networking configuration.. /etc/sysconfig/network# Check that networking is up.[ ${NETWORKING} = "no" ] && exit 0# check if the squid conf file is present[ -f /etc/squid/squid.conf ] || exit 0if [ -f /etc/sysconfig/squid ]; then. /etc/sysconfig/squidfi# don't raise an error if the config file is incomplete# set defaults instead:SQUID_OPTS=${SQUID_OPTS:-"-D"}SQUID_PIDFILE_TIMEOUT=${SQUID_PIDFILE_TIMEOUT:-20}SQUID_SHUTDOWN_TIMEOUT=${SQUID_SHUTDOWN_TIMEOUT:-100}# determine the name of the squid binary[ -f /usr/local/sbin/squid ] && SQUID=/usr/local/sbin/squid && SQUID1=squid[ -z "$SQUID" ] && exit 0prog="$SQUID"# determine which one is the cache_swap directoryCACHE_SWAP=`sed -e 's/#.*//g' /etc/squid/squid.conf | \grep cache_dir | awk '{ print $3 }'`[ -z "$CACHE_SWAP" ] && CACHE_SWAP=/usr/local/var/squid/cacheRETVAL=0start() {for adir in $CACHE_SWAP; doif [ ! -d $adir/00 ]; thenecho -n "init_cache_dir $adir... "$SQUID -z -F -D >> /usr/local/var/squid/logs/squid.out 2>&1fidoneecho -n $"Starting $prog: "$SQUID $SQUID_OPTS >> /usr/local/var/squid/logs/squid.out 2>&1RETVAL=$?if [ $RETVAL -eq 0 ]; thentimeout=0;while :; do[ ! -f /usr/local/var/squid/logs/squid.pid ] || breakif [ $timeout -ge $SQUID_PIDFILE_TIMEOUT ]; thenRETVAL=1breakfisleep 1 && echo -n "."timeout=$((timeout+1))donefi[ $RETVAL -eq 0 ] && touch /var/lock/subsys/$SQUID1[ $RETVAL -eq 0 ] && echo_success[ $RETVAL -ne 0 ] && echo_failureechoreturn $RETVAL}stop() {echo -n $"Stopping $prog: "$SQUID -k check >> /usr/local/var/squid/logs/squid.out 2>&1RETVAL=$?if [ $RETVAL -eq 0 ]; then$SQUID -k shutdown &rm -f /var/lock/subsys/$SQUID1timeout=0while :; do[ -f /usr/local/var/squid/logs/squid.pid ] || breakif [ $timeout -ge $SQUID_SHUTDOWN_TIMEOUT ]; thenechoreturn 1fisleep 2 && echo -n "."timeout=$((timeout+2))doneecho_successechoelseecho_failureechofireturn $RETVAL}reload() {$SQUID $SQUID_OPTS -k reconfigure}restart() {stopstart}condrestart() {[ -e /var/lock/subsys/squid ] && restart || :}rhstatus() {status $SQUID && $SQUID -k check}probe() {return 0}case "$1" instart)start;;stop)stop;;reload)reload;;restart)restart;;condrestart)condrestart;;status)rhstatus;;probe)exit 0;;*)echo $"Usage: $0 {start|stop|status|reload|restart|condrestart}"exit 1esacexit $? then issue the command: chmod 750 /etc/rc.d/init.d/squid 9. add the following rules in your existing iptables (nat section): A PREROUTING -p tcp -m tcp -i eth1 --dport 80 -j REDIRECT --to-ports 3128 if you have allowed only a selection of ports to be accepted in the INPUT section of iptables, make sure you also add te port 3128 in the allow list 10. now you can create startup and shutdown run level links to the squid run script: as root:chkconfig --add squidchkconfig --level 345 squid on and run the service: as root:service squid start it should initialize the cache directory and runs in background. that's all (see, it is simple isn't it? Wink). because the server is already the gateway of your internal network, all the web access from the internal network will be redirected to the squid port for processing.

I was damn frustrated when i get to know that Vista OS was not recognise by some of the old printer, camera and other things from Canon. Only certain printers are compatible as there is no new version of driver for this gadget that is compatible in Vista. Damn...

I am using mozilla firefox for a long time as my main browser...firefox is security strong then other~

i will choose kaspersky becouse its power full n friendy user .....easy to use also ...protection also strong