Touchscreen dual head setup help needed

I'm trying a rather complicated screen setup, with a 17" touchscreen (1280x1024) and a 24" widescreen (1920x1080). Using the opensource ATI driver.
The touchscreen works on it's own, and cloning works, but looks ugly on the 24". An extended desktop works too, but then the touchscreen's coordinates are scaled over the vitual screen, so touching on the middle causes the cursor to move somewhere on the 24".
Currently I'm trying a separate X screen setup, but it appears to be broken in the latest Xorg, which seems to require using xrandr. Can someone confirm this?
Is there any way of limiting the touchscreen cursor input to the 17"?
This is a new system, so I'm also open to WM suggestions.

Looks like I'm missing an option "screen" in evtouch. I'll test it tomorrow. And post the details if I'm successful, because there is not much information to be found.

Similar Messages

  • Frozen system when booting with dual-head setup (updates)

    Hi guys,
    I made a fresh install a couple of weeks ago and I configured my system for a dual-head setup following the wiki. I activated KMS and added radeon to the kernel parameters.
    My xorg.conf looks like this:
    Section "Monitor"
    Identifier "DVI-0"
    Option "PreferredMode" "1920x1080"
    Option "Position" "0 0"
    EndSection
    Section "Monitor"
    Identifier "HDMI-0"
    Option "PreferredMode" "1920x1080"
    Option "Position" "1920 0"
    EndSection
    I was having random freezes for a couple of days, but I didn't pay too much attention to it. I hard rebooted my computer when it froze and it could boot normally that second time.
    But after yesterday, last update to the open source drivers xf86-video-ati (1:7.5.0-2) and lib32-mesa-libgl (10.5.2-1), my system doesn't boot unless I disconnect one of the screens. When only one screen it's connected everything is fine. If I plug the second screen, it pops up the KDE service to configurate the second screen but as soon I press 'apply the chages' my system freezes and I had to hard reboot.
    I've tried all possible combinations usingt different outputs from the screens, getting the same results. Two of them connected --> freezes after grub loading. One connected --> boot Ok, but as soon as I plug the second one and I apply changes, freezes.
    I found one configuration that doesn't freeze my system. When I plug the second screen, as I said, KDE service automatically pops up. Before I was changing the positions of the screen, one beside the other one, and my system freezes when I apply the changes. If I just left the default configuration (one screen in top of the other), it doesn't freeze my system. After that, I can rearrange the screens, as I need them, and it doesn't freeze.
    Here it is my grub.cfg
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 e36984ca-21d8-4191-ba2f-a09bf8ce6f88
    else
    search --no-floppy --fs-uuid --set=root e36984ca-21d8-4191-ba2f-a09bf8ce6f88
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
    set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
    else
    search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
    menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
    else
    search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
    else
    search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    And my fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/sda2 resto del disco
    UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 / ext4 defaults,noatime,discard 0 1
    # /dev/sda1 100MB
    UUID=128c8e95-9496-49d1-9a9e-bc886662258d /boot ext4 defaults,noatime,discard 0 2
    # /dev/sdc2 10GB
    UUID=3959515c-30e4-4749-bc30-5babba3311e8 /var ext4 defaults 0 2
    # /dev/sdc3 resto del disco
    UUID=8ccc2ed9-35e5-4a4f-81f1-98cc8bfc4ed1 /home ext4 defaults,noatime 0 2
    # /dev/sdc1
    UUID=35e39da9-c942-434d-bbfc-deb5e40ee8be none swap defaults 0 0
    #montaje de temp en ram
    tmpfs /tmp tmpfs nodev,nosuid,size=3G 0 0
    # External HDD
    UUID=0ae5eb6a-8c4c-480c-8efe-609ae83f2bdc /media/External\040HDD ext4 defaults 0 0
    # Seagate Expansion Drive
    UUID=16668D4B668D2C95 /media/Seagate\040Expansion\040Driventfs-3g defaults,nofail 0 0
    What else should I check?
    Thanks in advance.
    Edit: added info
    Edit2: more tests.
    Last edited by doblerone (2015-03-31 08:12:38)

    Rexilion wrote:Maybe try looking at /var/log/pacman.log and see if you can downgrade packages (start with the kernel). See if that works around the problem.
    Downgrading catalyst to 14.3 seems to have done the job. Thanks for the suggestion, marking as solved.
    Inxsible wrote:bheinks, you have been on the forums long enough to be aware of the forum rules. Make use of an image hosting site.
    Sorry, I don't post often and wasn't aware of the rules on images. I'll keep that in mind next time.

  • Nouveau graphical tearing, dual-head setup

    I currently experience tearing while using the Nouveau drivers for my NVidia card. I experienced the same (or a similar) tearing issue while using the proprietary drivers, which, along with the inherent incompatibility with most of the linux graphics stack, led me to switch to Nouveau.
    I'm using the 3D support from nouveau-dri along with xf86-video-nouveau and the most recent Gnome 3 build in the official repositories.
    I have a dual-head setup with one 1024x768 IBM monitor to the left of a 1920x1080 Dell monitor. Both report 60Hz vertical refresh rate in their configuration menus.
    So far, my attempts to solve this problem have consisted of the following steps:
    1. Use a minimal xorg.conf and configure everything using the integrated Gnome display settings utility. The minimal xorg.conf was as follows:
    Section "Device"
    Identifier "nvidia"
    Driver "nouveau"
    Option "GLXVBlank" "true"
    EndSection
    2. Enable/disable the GLXVBlank flag in xorg.conf.
    I do not experience the same issue when booted to Windows 7, using the most recent official NVidia drivers.
    I would greatly appreciate any help anyone could offer on this issue, it is quite frustrating to boot into Windows to watch videos without horizontal breaks in every frame. Thanks!
    Output from xrandr --current is as follows:
    [ifx@melancholy ~]$ xrandr --current
    Screen 0: minimum 320 x 200, current 2944 x 1080, maximum 8192 x 8192
    DVI-I-1 connected 1920x1080+1024+0 (normal left inverted right x axis y axis) 477mm x 268mm
    1920x1080 60.0*+
    1280x1024 75.0 60.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DVI-I-2 connected 1024x768+0+312 (normal left inverted right x axis y axis) 304mm x 228mm
    1024x768 60.0*+ 75.1 70.1
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 72.8 75.0 60.0 59.9
    720x400 70.1
    My current xorg.conf is as follows:
    Section "Monitor"
    Identifier "Monitor0"
    Option "PreferredMode" "1920x1080_60.00"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    Option "PreferredMode" "1024x768_60.00"
    Option "LeftOf" "Monitor0"
    EndSection
    Section "Device"
    Identifier "nvidia"
    Driver "nouveau"
    Option "Monitor-DVI-I-1" "Monitor0"
    Option "Monitor-DVI-I-2" "Monitor1"
    Option "GLXVBlank" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Virtual 2944 1080
    EndSubSection
    Device "nvidia"
    EndSection
    Section "ServerLayout"
    Identifier "Layout0"
    Screen "Screen0"
    EndSection
    Other information can be provided on request.

    Hello. I have the same problem. Not just on Arch. I've had this problem with many distros, graphics cards, and drivers across the board. Installing the proprietary nvidia driver fixes the video tearing (vsync) issue for me. However; A) it's Linux, I don't want to use proprietary anything (otherwise I'd be on a Mac); and B) the proprietary driver will not flip my display to portrait anyway.
    I basically have the same setup as Meyermagic. One GeForce 8600 GT, Two monitors (identical acers) 1680x1050 (oriented in portrait so 1050x1680 if you like), using open source Nouveau driver, created a minimal xorg file in /etc/X11/xorg.conf.d/20-nouveau.conf
    Section "Module"
    Load "glx"
    EndSection
    Section "Device"
    Identifier "Nvidia card"
    Driver "nouveau"
    Option "GLXVBlank" "true"
    EndSection
    Both monitors have a refresh rate of 60Hz. I still get really bad tearing as I drag windows across the screens.
    Again, I've had this issue with almost every Linux box I've built (the only time this is not even remotely an issue is on my Thinkpad T400 using the Intel graphics). I'm guessing I'm doing something wrong or I've just had bad luck because it is nearly impossible to find any support for this on any forum anywhere. Anything I do find is either a thread like this where someone asked the question and simply never got a response. Or it is some out-of-date forum that give you 10 ways to modify the xorg.conf none of which make any sense or don't work. Not to mention that xorg.conf is now depreciated anyways.
    Seriously, even if there is a wiki that concisely explains in excruciating detail how to actually modify the xorg conf files then I could figure it out for myself but I can't find that anywhere which makes me feel really stupid because I know it has to be out there. If there isn't an xorg wiki or xorg.com site or something that explains how to use the thing then I'm not sure I want to live on this planet anymore.
    If anyone can help in any way please do.

  • [Solved] Catalyst graphical glitches with dual head setup

    Hello all, having a weird issue with my dual monitor setup where graphical glitches make my primary monitor completely unusable. The Tear Free feature of the proprietary catalyst driver is what seems to be causing it:
    Tear Free enabled:
    Tear Free disabled:
    I can safely enable it with one monitor disabled also. The issue is that without Tear Free enabled, I'm experiencing some serious screen tearing when watching videos and playing games.
    My video card is the XFX HD 7970 Double D and I'm using the latest version of catalyst (14.4), installed from Vi0L0's repo. The monitors are the same model with the same specs (1920x1200 @60Hz). I definitely used to be able to use Tear Free with my dual head setup at most a month ago, so some update at some point must have broken it. I temporarily switched back to the open source driver before I had found Tear Free to be the culprit and the performance is still hardly comparable.
    Any ideas? Thanks in advance.
    Last edited by bheinks (2014-05-15 02:38:45)

    Rexilion wrote:Maybe try looking at /var/log/pacman.log and see if you can downgrade packages (start with the kernel). See if that works around the problem.
    Downgrading catalyst to 14.3 seems to have done the job. Thanks for the suggestion, marking as solved.
    Inxsible wrote:bheinks, you have been on the forums long enough to be aware of the forum rules. Make use of an image hosting site.
    Sorry, I don't post often and wasn't aware of the rules on images. I'll keep that in mind next time.

  • Dual head setup (mach64 - ATI Rage Mobility)

    hello everyone!
    I want to use a new extra monitor I got recently, with my laptop, I use aweosme.
    I have installed:
    xf86-video-mach64 (recompiled with dri support)
    mach64-dri (from community)
    mach64drm (from AUR)
    https://wiki.archlinux.org/index.php/Mach64
    Still I can't get OpenGL to work:
    ismaelvc@toybox ~ $ glxinfo | egrep "direct rendering|OpenGL renderer"
    direct rendering: Yes
    OpenGL renderer string: Gallium 0.4 on softpipe
    I don't really know if it got something to do with this but I post it anyway in case it is.
    xrandr doesnt detect the other monitor:
    ismaelvc@toybox ~ $ xrandr -q
    xrandr: Failed to get size of gamma for output default
    Screen 0: minimum 320 x 175, current 1024 x 768, maximum 1024 x 768
    default connected 1024x768+0+0 0mm x 0mm
    1024x768 87.0* 85.0 75.0 70.0 60.0 81.0
    832x624 75.0
    800x600 85.0 75.0 72.0 60.0 56.0
    640x480 85.0 75.0 73.0 60.0
    720x400 85.0
    640x400 85.0
    640x350 85.0
    512x384 87.0 85.0 75.0 70.0 60.0
    416x312 75.0
    400x300 85.0 75.0 72.0 60.0 56.0
    320x240 85.0 75.0 73.0 60.0
    360x200 85.0
    320x200 85.0
    320x175 85.0
    Still it displays exactly the same that gets displayed at my laptop.
    I used to had problems with the drivers, I needed both mach64 and radeon for it to detect the screen properly, until I created a "20-mach64.conf" with this:
    Section "Device"
    Identifier "Card0"
    Driver "mach64"
    Card "ATI Rage Mobility - Mach64"
    Option "DMAMode" "async"
    Option "ForcePCIMode" "false"
    Option "AgpMode" "2"
    Option "AgpSize" "32"
    Option "BufferSize" "2"
    Option "LocalTextures" "true"
    Option "EnablePageFlip" "true"
    EndSection
    Section "Module"
    #<Your modules>
    Load "glx"
    Load "dri"
    EndSection
    Section "DRI"
    Group "video" #change to any desired group to restrict access
    Mode 0660
    EndSection
    I have a doubt regarding the commented line that came as example in the mach64 wiki that reads <your modules>, I don't know what goes in there.
    Also I red this for some mach64 related xorg info:
    http://www.x.org/archive/X11R6.8.0/doc/ati5.html
    http://forums.fedoraforum.org/showthread.php?t=201482
    The last one is for a cursor problem I have, but it wont get fixed, neither, anyway the default xcursor looks good in awesome, I switched to cli apps form many tasks, and use uzbl now! all this plus arch is now so minimmal I love it lol!
    I red in a post (not in this one) mach64 chips supported dual head, but I can't find it again, I will post it when I find it.
    Thanks in advance!
    EDIT: ok here it is, where it say its supported: I don't understand all the configs.
    http://cgit.freedesktop.org/xorg/driver … ff432c36bf
    Last edited by ismaelvc (2012-06-29 03:52:09)

    Sorry to necrobump but I was seeing you get a lot of incorrect information on LinuxQuestions.
    The mach64 driver does NOT support dualhead. Some chips are capable of it but this feature has yet to be added to the driver. It is also not compatible with xrandr. The man page you linked to mentioning dualhead support is for xf86-video-ati. It is only accessible from the git history of xf86-video-mach64 because those drivers used to live in the same source tree.
    I can try to help with DRI if that's still not working for you.

  • Bootsplash on a dual-head setup without KMS?

    Hello!
    I have been wanting to get a bootsplash working on my system, to get a feeling of a more polished system, but sadly I'm running the catalyst drivers for decent 3D game framerate, and it doesn't support KMS. It seemed like that would have been okay, and that for example plymouth could work through a framebuffer, but sadly I have dual-head with two different resolutions(1920x1200 and 1020x1280), and I couldn't get Uvesafb/v86d to work with that. I really want to get a bootsplash and I am willing to sacrafise some time to get it working. The main goal is just to get it working, but ideally I'd like it without any resolution changing or black flicker, as it's described here.  So Plymouth is my first-pick, as it looks "best".
    So far I have tried Splashy, FBsplash and Plymouth, with different degrees of success:
    FBsplash:
        Miscsplashutils(dependency) didn't build because freetype had been built without static linking(I don't know anything about this). I got it working with something I found in the comments though.
        But then FBsplash wouldn't build. And I gave it up.
    Splashy:
        Installation worked(splashy-full) after I modified the PKGBUILD with some automake patches so it should work with automake 1.14. But when I booted it the screen was just flickering black
    Plymouth:
        I got it installing, can't remeber if I needed some patches. And it worked, although only with a text-bootsplash. I also installed a framebuffer(Uvesafb/v86d) but that didn't work properly.
        The Plymouth loading anymation(spinfinity) continued into gdm.
    I am willing to retry everything and clearify what doesn't work, and why.
    Thanks to anyone who can help!
    Last edited by totokaka (2013-08-21 16:21:23)

    So I've been trying to get some development on this, and used most of the day to get uvesafb working.
    It is working quite good, but I don't get the native resolution of the screen(1920x1200), I only get 1600x1200.
    And my secound monitor is disabled, I suspect it's because the computer sends a resolution to big to both the screens, but it's really a a feature for me, as the terminal would be sideways on the secound monitor anyways.
    During my testing I also came to a new idea: Have the framebuffer, X and GDM originally only start the main monitor, and then leave it up to gnome to enable it. that way I would only get the flicker between GDM and gnome-shell, which I will get anyway, because it seems like everything ignores X's rotation of the screens, or at least doesnt support sideways. However I didn't find a way to get this working, any ideas?
    EDIT; My card is an HD6790, and as far as I can understand the GPU's bios is sending supported modes to uvesafb?
    Last edited by totokaka (2013-08-22 19:22:52)

  • Lackluster Dual Network Setup - HELP!

    Here's my setup:
    DSL
    I
    I
    AXBS (UFO) 2.4Ghz b/g --> PowerBook G4 (10.4.11); iPhone (Original)
    I
    I
    Time Capsule 5Ghz n (Bridged) --> MacBook Pro (10.5.4); MacBook (10.4.11 - n enabled)
    The Time Capsule's Strength and Range is suppose to far exceed that of the older Base Station. When I'm near the location of the two transmitters the 5Ghz n is barely twice as fast as the 2.4Ghz b/g (tested with large file transfers between the 2 newer laptops, and then file transfers between the MacBook Pro and the older Powerbook). When I'm farther away the 5Ghz n drops away and the 2.4Ghz b/g remains relatively strong. Switching between the two networks when I'm at a distance strangely still shows full solid bars for both networks.
    So does anyone have any suggestions or further question that might help me improve the speed and range of the newer Time Capsule? Thanks

    Just to update everyone:
    Today I moved my whole dual network setup to a more centrally located spot in the house. This has definitely improved the coverage of the 2 network bands (n & b/g).
    Additionally, since I only recently acquired the TC, I originally just added ("bridged") it off of my existing b/g network. With todays move, I decided to switch the 2 base stations and have the TC and its' "n" network the first connection off of the DSL router. Then reconfigured the older ABS Extreme (UFO) to "bridge" off the the TC. While I am convinced that I did not originally have the 2 networks co-mingled (as early speed tests confirmed), I seem to be experiencing improved internet speeds in the 5Ghz ("n") network. Could this be due to no longer "bridging" the TC through the older ABS Extremes' internal Ethernet switch?
    As per Tesserax suggestion, I then did a Signal-to-Noise ration (SNR) survey of the house, and came up with some good results based on the SNR Guidelines in Tesserax comments above.
    35 to 45 SNR throughout most of the house. About 25 SNR just outside in the patio where I was barely getting a connection before. Things have definitely improved. And I am very pleased. Clearly network speed is the advantage of 802.11n technology.
    Nevertheless, my original observation still seems to apply. Here's why: Detached from the house is the garage and an office. As I moved out toward the office during the SNR survey (about 50 ft. away), the strength of the 5Ghz ("n") network dramatically dropped off, and was eventually non-existent inside the office. Yet I could switch over to the 2.4Ghz ("b/g") network and easily browse the internet.
    Apple's marketing claims "AirPort Extreme delivers data transfer speeds up to five times those of previous-generation 802.11g wireless networks — while achieving up to twice the range."
    Now I fully accept, as Apples' footnote states, "Based on a comparison with Apple's 802.11g products. Comparison assumes AirPort Extreme network with 802.11n-enabled computer. Speed and range will be less if an 802.11a/b/g product joins the network. Accessing the wireless network requires an AirPort- or AirPort Extreme-enabled computer or other Wi-Fi Certified 802.11a/b/g-enabled computer. Actual performance will vary based on range, connection rate, site conditions, size of network, and other factors. Range will vary with site conditions." If "site conditions" are limiting the range of the 5Ghz band, why aren't those same site conditions limiting the 2.4Ghz band as well. While I don't realistically expect a full doubling of range between the 2 bands, couldn't I expect SOME? Otherwise the marketing claims are meaningless.
    Can the disparity be explained by Tesserax' observation above, "we know the stricter the wireless security employed, the more overhead is "eating away" the overall bandwidth so we would expect poorer performance when using WPA2 vs. WEP." Now the TC only has WPA2 security available. Are we to assume that Apple's range claims do not apply to the TC then? If I switch my older ABS Extreme (UFO) from WEP to WPA2 will the result match Apple's marketing claims? I'd rather not chop off my good right leg just so it will match my missing left leg. Perhaps my expectations for 802.11n technology were a little too high. Don't get me wrong. I'm very happy with the results. And I am thankful for Tesserax advise. I also appreciate the fact that I am not (yet) experiencing the difficulties that others here are having with the Time Capsule.
    Ultimately, I assume that picking up an Airport Express "n" will extend the 5Ghz network into the office. Is this correct? If anyone has observations on this or my thoughts above, feel free to share them with the rest of us.

  • Xorg 6.8 and dual head setup

    Hello,
    I have a laptop with an ATI 9600 mobile chip which ran in xinerama mode fine for the previous release of xrog or xfrree86 but with the new xorg reslease 6.8 I can no longer run 2 monitors. It will run fine in single head mode, but it will no longer run in dual mode. In fact, it "seems" to run faster and take less memory in single head mode,
    I am posting my xorg.conf in the hope that someone can help!
    Section "ServerLayout"
    Identifier "Single"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "ServerLayout"
    Identifier "Dual"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" LeftOf "Screen0"
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "ServerFlags"
    Option "Xinerama"
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    Section "Files"
    RgbPath "/usr/X11R6/lib/X11/rgb"
    ModulePath "/usr/X11R6/lib/modules"
    FontPath "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath "/usr/X11R6/lib/X11/fonts/local"
    FontPath "/usr/X11R6/lib/X11/fonts/TTF"
    FontPath "/usr/X11R6/lib/X11/fonts/truetype"
    FontPath "/usr/share/fonts/corefonts"
    FontPath "/usr/X11R6/lib/X11/fonts/terminus"
    EndSection
    Section "Module"
    Load "extmod"
    Load "dri"
    Load "dbe"
    Load "record"
    Load "xtrap"
    Load "glx"
    Load "speedo"
    Load "type1"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    #Option "Protocol" "auto"
    Option "Protocol" "ImPS/2"
    #Option "Protocol" "ExplorerPS/2"
    Option "Device" "/dev/input/mice"
    Option "Emulate3Buttons" "true"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "Monitor"
    Identifier "LCD"
    VendorName "Laptop"
    ModelName "Monitor Model"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    Option "DPMS" "true"
    VendorName "GWY"
    ModelName "GWY00c0"
    HorizSync 30 - 96 # DDC-probed
    VertRefresh 50.0 - 76.0 # Very conservative. May flicker.
    # Default modes distilled from
    # "VESA and Industry Standards and Guide for Computer Display Monitor
    # Timing", version 1.0, revision 0.8, adopted September 17, 1998.
    # $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
    # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
    # 640x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
    # 720x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
    # 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
    ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
    # 640x480 @ 72Hz (VESA) hsync: 37.9kHz
    ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
    # 640x480 @ 75Hz (VESA) hsync: 37.5kHz
    ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
    # 640x480 @ 85Hz (VESA) hsync: 43.3kHz
    ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
    # 800x600 @ 56Hz (VESA) hsync: 35.2kHz
    ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    # 800x600 @ 60Hz (VESA) hsync: 37.9kHz
    ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    # 800x600 @ 72Hz (VESA) hsync: 48.1kHz
    ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
    # 800x600 @ 75Hz (VESA) hsync: 46.9kHz
    ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
    # 800x600 @ 85Hz (VESA) hsync: 53.7kHz
    ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
    # 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
    ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
    # 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
    ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
    # 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
    ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
    # 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
    ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
    # 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
    ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
    # 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
    ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
    # 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
    ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
    # 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
    ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
    # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
    # 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    # 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    # 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    # 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    # 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    # 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    # Additional modelines
    ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    # Extended modelines with GTF timings
    # 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
    ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
    # 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
    ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
    # 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
    ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
    # 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
    ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
    # 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
    ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
    # 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
    ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
    # 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
    ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
    # 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
    ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
    # 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
    ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
    # 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
    ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
    # 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
    ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
    # 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
    ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
    # 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
    ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
    # 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
    ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
    # 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
    ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
    # 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
    ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
    # 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
    ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
    # 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
    ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
    # 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
    ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
    # 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
    ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
    # 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
    ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
    EndSection
    Section "Device"
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ### [arg]: arg optional
    #Option "NoAccel" # [<bool>]
    #Option "SWcursor" # [<bool>]
    #Option "Dac6Bit" # [<bool>]
    #Option "Dac8Bit" # [<bool>]
    #Option "ForcePCIMode" # [<bool>]
    #Option "BusType" # [<str>]
    #Option "CPPIOMode" # [<bool>]
    #Option "CPusecTimeout" # <i>
    #Option "AGPMode" # <i>
    #Option "AGPFastWrite" # [<bool>]
    #Option "AGPSize" # <i>
    #Option "GARTSize" # <i>
    #Option "RingSize" # <i>
    #Option "BufferSize" # <i>
    #Option "EnableDepthMoves" # [<bool>]
    #Option "EnablePageFlip" # [<bool>]
    #Option "NoBackBuffer" # [<bool>]
    #Option "DRIReinit" # [<bool>]
    #Option "PanelOff" # [<bool>]
    #Option "DDCMode" # [<bool>]
    #Option "MonitorLayout" # [<str>]
    #Option "IgnoreEDID" # [<bool>]
    #Option "OverlayOnCRTC2" # [<bool>]
    #Option "CloneMode" # [<str>]
    #Option "CloneHSync" # [<str>]
    #Option "CloneVRefresh" # [<str>]
    #Option "UseFBDev" # [<bool>]
    #Option "VideoKey" # <i>
    #Option "DisplayPriority" # [<str>]
    #Option "PanelSize" # [<str>]
    #Option "ForceMinDotClock" # <freq>
    Identifier "Card0"
    #Driver "fglrx"
    #Driver "ati"
    Driver "radeon"
    VendorName "ATI Technologies Inc"
    BoardName "Radeon Mobility 9600"
    Screen 0
    #Option "AGPMode" "2"
    BusID "PCI:1:0:0"
    EndSection
    Section "Device"
    Identifier "Card1"
    #Driver "fglrx"
    #Driver "ati"
    Driver "radeon"
    VendorName "ATI Technologies Inc"
    BoardName "Radeon Mobility 9600"
    Screen 1
    #Option "AGPMode" "2"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "LCD"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Card1"
    Monitor "Monitor0"
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Thanks,
    Jason

    Hello,
    I have a laptop with an ATI 9600 mobile chip which ran in xinerama mode fine for the previous release of xrog or xfrree86 but with the new xorg reslease 6.8 I can no longer run 2 monitors. It will run fine in single head mode, but it will no longer run in dual mode. In fact, it "seems" to run faster and take less memory in single head mode,
    I am posting my xorg.conf in the hope that someone can help!
    Section "ServerLayout"
    Identifier "Single"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "ServerLayout"
    Identifier "Dual"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" LeftOf "Screen0"
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "ServerFlags"
    Option "Xinerama"
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    Section "Files"
    RgbPath "/usr/X11R6/lib/X11/rgb"
    ModulePath "/usr/X11R6/lib/modules"
    FontPath "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath "/usr/X11R6/lib/X11/fonts/local"
    FontPath "/usr/X11R6/lib/X11/fonts/TTF"
    FontPath "/usr/X11R6/lib/X11/fonts/truetype"
    FontPath "/usr/share/fonts/corefonts"
    FontPath "/usr/X11R6/lib/X11/fonts/terminus"
    EndSection
    Section "Module"
    Load "extmod"
    Load "dri"
    Load "dbe"
    Load "record"
    Load "xtrap"
    Load "glx"
    Load "speedo"
    Load "type1"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    #Option "Protocol" "auto"
    Option "Protocol" "ImPS/2"
    #Option "Protocol" "ExplorerPS/2"
    Option "Device" "/dev/input/mice"
    Option "Emulate3Buttons" "true"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "Monitor"
    Identifier "LCD"
    VendorName "Laptop"
    ModelName "Monitor Model"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    Option "DPMS" "true"
    VendorName "GWY"
    ModelName "GWY00c0"
    HorizSync 30 - 96 # DDC-probed
    VertRefresh 50.0 - 76.0 # Very conservative. May flicker.
    # Default modes distilled from
    # "VESA and Industry Standards and Guide for Computer Display Monitor
    # Timing", version 1.0, revision 0.8, adopted September 17, 1998.
    # $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
    # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
    # 640x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
    # 720x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
    # 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
    ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
    # 640x480 @ 72Hz (VESA) hsync: 37.9kHz
    ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
    # 640x480 @ 75Hz (VESA) hsync: 37.5kHz
    ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
    # 640x480 @ 85Hz (VESA) hsync: 43.3kHz
    ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
    # 800x600 @ 56Hz (VESA) hsync: 35.2kHz
    ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    # 800x600 @ 60Hz (VESA) hsync: 37.9kHz
    ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    # 800x600 @ 72Hz (VESA) hsync: 48.1kHz
    ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
    # 800x600 @ 75Hz (VESA) hsync: 46.9kHz
    ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
    # 800x600 @ 85Hz (VESA) hsync: 53.7kHz
    ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
    # 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
    ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
    # 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
    ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
    # 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
    ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
    # 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
    ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
    # 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
    ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
    # 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
    ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
    # 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
    ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
    # 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
    ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
    # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
    # 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    # 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    # 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    # 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    # 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    # 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    # 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    # Additional modelines
    ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
    # Extended modelines with GTF timings
    # 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
    ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
    # 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
    ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
    # 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
    ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
    # 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
    ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
    # 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
    ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
    # 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
    ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
    # 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
    ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
    # 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
    ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
    # 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
    ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
    # 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
    ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
    # 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
    ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
    # 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
    ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
    # 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
    ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
    # 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
    ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
    # 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
    ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
    # 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
    ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
    # 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
    ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
    # 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
    ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
    # 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
    ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
    # 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
    ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
    # 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
    ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
    EndSection
    Section "Device"
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ### [arg]: arg optional
    #Option "NoAccel" # [<bool>]
    #Option "SWcursor" # [<bool>]
    #Option "Dac6Bit" # [<bool>]
    #Option "Dac8Bit" # [<bool>]
    #Option "ForcePCIMode" # [<bool>]
    #Option "BusType" # [<str>]
    #Option "CPPIOMode" # [<bool>]
    #Option "CPusecTimeout" # <i>
    #Option "AGPMode" # <i>
    #Option "AGPFastWrite" # [<bool>]
    #Option "AGPSize" # <i>
    #Option "GARTSize" # <i>
    #Option "RingSize" # <i>
    #Option "BufferSize" # <i>
    #Option "EnableDepthMoves" # [<bool>]
    #Option "EnablePageFlip" # [<bool>]
    #Option "NoBackBuffer" # [<bool>]
    #Option "DRIReinit" # [<bool>]
    #Option "PanelOff" # [<bool>]
    #Option "DDCMode" # [<bool>]
    #Option "MonitorLayout" # [<str>]
    #Option "IgnoreEDID" # [<bool>]
    #Option "OverlayOnCRTC2" # [<bool>]
    #Option "CloneMode" # [<str>]
    #Option "CloneHSync" # [<str>]
    #Option "CloneVRefresh" # [<str>]
    #Option "UseFBDev" # [<bool>]
    #Option "VideoKey" # <i>
    #Option "DisplayPriority" # [<str>]
    #Option "PanelSize" # [<str>]
    #Option "ForceMinDotClock" # <freq>
    Identifier "Card0"
    #Driver "fglrx"
    #Driver "ati"
    Driver "radeon"
    VendorName "ATI Technologies Inc"
    BoardName "Radeon Mobility 9600"
    Screen 0
    #Option "AGPMode" "2"
    BusID "PCI:1:0:0"
    EndSection
    Section "Device"
    Identifier "Card1"
    #Driver "fglrx"
    #Driver "ati"
    Driver "radeon"
    VendorName "ATI Technologies Inc"
    BoardName "Radeon Mobility 9600"
    Screen 1
    #Option "AGPMode" "2"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "LCD"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Card1"
    Monitor "Monitor0"
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 15
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 16
    EndSubSection
    SubSection "Display"
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Thanks,
    Jason

  • Network setup, help needed..

    Since i am getting a new internet connection (100mbit glass-fibre) i want to make a perfect setup network. Since im not entirely sure how to set it up i ask for some help.
    First off, what i have on the network (or want to have):
    -Several Macs (100/1000 base)
    -Several Windows machines (100/1000 base)
    -FTP server (maybe more than just FTP)
    -Wireless connectivity
    -Printers
    Network stuff i already have:
    -router (10/100m)
    -8 port 1000 base ethernet switch
    -Airport express
    -I am getting another ethernet switch since i am losing 4 ports that are on the old modem.
    I am guessing that if i just hook the router up to the switch, and then the AE to the switch i wont have any trouble.
    But now sometimes have trouble in my current setup, that is modem/router/hub (in one device) and then plugged into this an AE and switch. But but some PC's cant see each other, is that caused by the modem device (the hub inside it)? And so will i have that problem with the new setup i described?
    If u think i need other devices please say so, i just want everything to work at the highest speed possible.
    Thanks in advance.

    A long time ago, I worked on a print spooler and was lent a JetDirect
    box from HP to test with. A JetDirect card is in your LaserJet, I believe.
    (One of the protocols it supported was localtalk, BTW). I think the
    d-link isn't forwarding your localtalk packets. Anyway, one of the
    things I remember is that the JetDirect spoke PCL, so that's another
    consideration a driver has to deal with. The garbage you're seeing
    is raw postscript. It needs to be rasterized and translated to PCL.
    Please bear with me, my experience is very old, and there are gaps
    in my knowledge. But I think this is do-able. I think the first step is
    to add the printer directly by clicking here,
    The location of the printer should be the address of the print server
    (or canonical name if you're ever going to change addresses). The
    device should be appsocket/jetdirect. The device uri should be
    socket://nameoripaddressofdevice. The make should be HP and
    the model/driver should be one of the Laserjet series, gimp-print.
    I don't know which one, my experience ended around Laserjet 5, and
    so do the drivers! But fundamentally they have to do the same thing.
    They use the gimp-print package to rasterize the postscript and
    encapsulate it into PCL. So I would bet the LaserJet 6 driver will work.
    I'm sure everything posted here is correct, and that my experience
    is too old and I don't know enough to know why this won't work,
    but it's not a lot of effort, and if I were you I'd give it a try.
    -Phil
    Powerbook G4, iMac (Intel), and tons of hardware sitting in the closet   Mac OS X (10.4.8)  

  • WRT54G Wireless Router Setup Help Needed

    Hi,
    I have a WRT 54G router I want to set up on my network.
    What I want to be able to do is have the router allow wireless laptops to connect via wireless, but I want the router to assign the IP automatically through DHCP. Is this possible?
    My Network information is as follows:
    Router would be assigned IP 192.168.72.10
    Network information for Office where this is going:
    Subnet: 255.255.255.0
    Default Gateway: 192.168.72.1
    Primary DNS: 192.168.1.59
    Secondary DNS: 192.168.1.52
    any help would be appreciated...

    First of all, let me say that, assuming you have a Linksys router in the main office, that there is no reason why that router could not use both fixed LAN IP addresses, and have its DHCP server turned on and give out DHCP addresses also.  So, it seems like you could setup the system in the manner I mentioned in my previous post.   Unless, for some reason, you prefer not to do it this way.
    If you really want to set it up with the WRT54G giving out DHCP addresses, then read on:
    If you want to use the DHCP server in the WRT54G, you will need to place it on a separate subnet.
    I'm still a bit confused by what you have written.  You said that the WRT54G router "would be assigned IP 192.168.72.10".  And later you said that my assumption was correct that you set the "Local IP Address" to this value.   However, if you want to use the DHCP server in the WRT54G, this will not work, because to use the DHCP server, the WRT54G needs to be on a separate subnet.
    Instead, in the WRT54G, you would need to set the "Internet Connection Type" to "Static", then give the WRT54G the WAN address (not local IP address) of 192.168.72.10.   (You will also need to specify the subnet mask 255.255.255.0 , default gateway 192.168.72.1 , and DNS (proxy) server 192.168.72.1 )  You would need to reset the WRT54G's  "Local IP address" to a subnet that is not used elsewhere in your network.  Since you apparently already use 192.168.1.x  and  192.168.72.x  subnets, you will need to pick something else, perhaps 192.168.54.1 for the "local IP address" of the WRT54G.
    In this type of setup, you would leave the DHCP server of the WRT54G enabled, and wire a LAN port from the office router to the Internet port of the WRT54G.
    In this case, the WRT54G is in control of all your router settings, including port forwarding, DHCP server, and wireless settings.  Also note that if you need to forward a port, you will need to forward the port through your entire network, not just the WRT54G.
    One additional warning.  I have not personally used a "3 subnet" system with Linksys routers.  So I am not certain that all your DNS addresses will flow through the system properly.  If it doesn't work, you may need to enter some of you actual Internet based DNS addresses (or perhaps your Primary and Secondary 192.168.1.59 and .52 DNS servers) into the WRT54G router by hand, rather than using the built in Linksys DNS proxy at 192.168.72.1 
    Hope this helps.
    Message Edited by toomanydonuts on 12-04-2007 04:34 PM

  • How to configure a P2000 MSA Array System Dual I/O - Help Needed

     Hi, Tried to install a new HP P2000 MSA for a client today.  We are connecting the P2000 directly to SAS Card in our HP Server.
    Installed 2 x 3TB drives no problem. Drives show up in the BIOS and in VSphere no problem.
    We want to setup a new RAID 1 array using the new SAN. I assumed running the array config (F5) on boot would allow me to create the array, but HP Smart Storage does not see the new device or drives.
    I spent hours looking online for assistance. Any HP docs mention connecting to the SAN by CLI or Ethernet port.  Neither of which we have on the SAN. We have two separate IN/OUT SAN connections which we have connected to our SAS card in the Server. I have also seen suggestions to use the SMU to configure RAID in the new array. Again, I cannot see how to access or run the SMU.
    How can we configure RAID on the device if the HP SMart Storage software cannot see the device. Completely stuck here so any help appreciated!
    Thanks.

    Hi:
    You may also want to post your question on the HP Business Support Forum -- Storage Area Networks (SAN) (Small and Medium Business) section.
    http://h30499.www3.hp.com/t5/Storage-Area-Networks-SAN-Small/bd-p/bsc-257#.VQoKWDgtHGg

  • Java Wireless Toolkit Setup Help Needed

    I am interseted in mobile application development, and I have recently tried to set up the Java Wireless toolkit 2.0 on my laptop.
    I have spent gours trying to get it to work correctly - still nothing!!
    When it's all installed, I have opened up the sample projects -- e.g. Games.
    When I hit 'Build' I am given the following error:
    Project "games" loaded
    Project settings saved
    Building "games"
    C:\WTK20\apps\games\src\example\pushpuzzle\PushPuzzle.java:145: cannot access java.lang.StringBuilder
    file java\lang\StringBuilder.class not found
    alert.setString("Could not load level " +
    ^
    com.sun.kvem.ktools.ExecutionException
    Build failed
    Can someone please tell me what to do?!?
    Is it to do with setting the classpath?? How do I do that??
    What other Java tools do I need to have prior to installing the Wireless toolkit?? JVM?? Where do I get this? How do I install it correctly and set paths correctly??
    Any help would be HUGELY appreciated as I have downloaded so much stuff at this stage I have compleely confused myself!!

    Hey.
    Right, last night I downloaded the latest version of JDK - version 1.5.
    I installed it successfully.
    So in the folder C:\ Java there are two folders: Jdk-1.5_etc and JRE-1.5_etc.
    Next I downloaded and installed the latest version of the wireless toolkit.
    It saw that I had the JDK installed at th correct folder, and it installed at C:\WTK20 - said it installed correctly.
    So, next I select create project - call it hello world.
    Then I place the following code in the src folder of the helloWorld folder:
    * Copyright 2000-2001 by Sun Microsystems, Inc.,
    * 901 San Antonio Road, Palo Alto, California, 94303, U.S.A.
    * All rights reserved.
    package examples.helloworld;
    import javax.microedition.midlet.*;
    import javax.microedition.lcdui.*;
    public class HelloWorld extends MIDlet implements CommandListener {
    private Command exitCommand;
    private TextBox tb;
    public HelloWorld() {
    exitCommand = new Command("Exit", Command.EXIT, 1);
    tb = new TextBox("Hello MIDlet", "Hello, World!", 15, 0);
    tb.addCommand(exitCommand);
    tb.setCommandListener(this);
    protected void startApp() {
    Display.getDisplay(this).setCurrent(tb);
    protected void pauseApp() {}
    protected void destroyApp(boolean u) {}
    public void commandAction(Command c, Displayable d) {
    if (c == exitCommand) {
    destroyApp(false);
    notifyDestroyed();
    I hit build and it builds correctly - no errors - YAY!!.
    I hit run, the phone emulator pops up. I hit launch and:
    An error pops up on the screen of the phone.
    The error below appears in the Wireless toolkit window:
    Project "HelloWorld" loaded
    Project settings saved
    Building "HelloWorld"
    Build complete
    Running with storage root DefaultColorPhone
    Unable to create MIDlet HelloWorld
    java.lang.ClassNotFoundException: HelloWorld
         at com.sun.midp.midlet.MIDletState.createMIDlet(+14)
         at com.sun.midp
    I'm using version 1.5 of JDK - what have I not done - why won't it run.
    I keep getting Java.lang errors!!!!
    AAAGGGHHHHH!!!!!!!!!!!!!!!

  • Time Capsule Setup Help Needed

    Hi there
    I have a new 27" iMac and I'm trying to connect Time Capsule to it for Time Machine Backups.However when I turn TC on I am bewildered by an array of confusing networking type questions by the TC setup wizzard
    All I want to do is back up my iMac wirelessly. I don't want to do anything else with my TC.
    I have a wireless Linksys router that I use for the internet and no other users need to share my TC.
    I don't want my TC to have anything to do with other users or my internet connection.
    How can I do this?
    Thanks.

    Paul McLaren wrote:
    Hi there
    I have a new 27" iMac and I'm trying to connect Time Capsule to it for Time Machine Backups.However when I turn TC on I am bewildered by an array of confusing networking type questions by the TC setup wizzard
    All I want to do is back up my iMac wirelessly. I don't want to do anything else with my TC.
    I have a wireless Linksys router that I use for the internet and no other users need to share my TC.
    I don't want my TC to have anything to do with other users or my internet connection.
    How can I do this?
    click here and follow the instructions to set up the TC.
    i would recommend that you connect your Mac and the TC by ethernet cable for the initial setup as well as to perform your initial backup (which can take quite a while). once that is done the ethernet cable can go as the next backups will be incremental.
    you may also want to browse through the Time Machine FAQ - just for the heck of it.
    post back if you need further information.
    good luck !

  • Header autonumbering help needed

    I am using FrameMaker v7.1p114 and I would like to create headings and subheadings within book chapters that have auto numbering such as the following assuming that this is Chapter 5:
    5.1 Main heading 1
    5.1.1 Sub heading 1
    5.1.2 Sub heading 2
    5.2 Main heading 2
    5.2.1 Sub heading 1
    5.2.2 Sub heading 2
    I believe that I have the main heading figured out by using a paragraph format that uses the autonumber format as follows: <$chapnum>.<n+>iu
    However, in order to get the desired autonumbered sub heading, what is a good method?  One method that should work, but that requires me to create a lot of paragraph definitions, and that is not a completely autonumbered solution is as follows:
    * create as many paragraph definitions as sub headings needed
    * just put the <n+> on the end
    For example, I could create a subheading #1 as: <$chapnum>.<n=1>.<n+>
    a subheading #2 as: <$chapnum>.<n=2>.<n+>
    a subheading #3 as: <$chapnum>.<n=3>.<n+>
    The problem is that if I insert/move one of the sub headed sections, I would have to manually change the paragraph format and then go through the document and correct any text referenences that mention the specific section that now has a new sub heading number.

    I used Dan's paper to create a test file in about 10 minutes and believe that I have come up with a solution.  I crated 3 paragraph definitions and the code is as follows:
    5.1    main 1-1    H:<$chapnum>.<n+>< =0>
    5.1.1    sub 1-1-1  H:<$chapnum>.<n>.<n+>< =0>
    5.1.1.1   sub 1-1-1-1  H:<$chapnum>.<n>.<n>.<n+>< =0>
    5.1.1.2   sub 1-1-1-2
    5.1.2    sub 1-1-2
    5.1.3    sub 1-1-3
    5.1.1.3.1   sub 1-1-3-1
    5.1.3.2   sub 1-1-3-2
    5.2  main 2
    5.2.1  sub 1-2-1
    5.2.1.1  sub 1-2-1-1
    5.2.1.2  sub 1-2-1-2
    I should have been using FrameMaker years ago .

  • Dual Layer DVD HELP needed

    I have a project that is a little over 3 hours long, that I need on one DVD. I own a Lacie Dual Layer external burner, but, I've never burned dual layers on it. Can it be done with iDVD 6 or in iMovie HD? I know where the button is for the Dual Layer feature in the Toast Lite software, what else do I need to do.(or buy?) What should I use DVD + or - R Dual Layer media? (is Verbatim best?)
    Thanx,
    idiotpuppy

    Hello,
    Your computer is fine for support of a double-layer superdrive. Just make sure to plug it into the ATA-66 port on the logic board if you plan to burn in speeds of 16-20x or more.
    ATA-3 won't handle full burns at 20x.

Maybe you are looking for