Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Debian "Testing" XF86Config

  1. #1

    Debian "Testing" XF86Config

    Ok my head really f**kin hurts right now I have been up all night trying to get debian to start. I have tried the ./xf86config soo many times it's not funny >

    here is the xf86config file

    Code:
    # File generated by xf86config.
    
    #
    # Copyright (c) 1999 by The XFree86 Project, Inc.
    #
    # Permission is hereby granted, free of charge, to any person obtaining a
    # copy of this software and associated documentation files (the "Software"),
    # to deal in the Software without restriction, including without limitation
    # the rights to use, copy, modify, merge, publish, distribute, sublicense,
    # and/or sell copies of the Software, and to permit persons to whom the
    # Software is furnished to do so, subject to the following conditions:
    # 
    # The above copyright notice and this permission notice shall be included in
    # all copies or substantial portions of the Software.
    # 
    # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
    # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
    # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
    # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    # SOFTWARE.
    # 
    # Except as contained in this notice, the name of the XFree86 Project shall
    # not be used in advertising or otherwise to promote the sale, use or other
    # dealings in this Software without prior written authorization from the
    # XFree86 Project.
    #
    
    # **********************************************************************
    # Refer to the XF86Config(4/5) man page for details about the format of 
    # this file.
    # **********************************************************************
    
    # **********************************************************************
    # Module section -- this  section  is used to specify
    # which dynamically loadable modules to load.
    # **********************************************************************
    #
    Section "Module"
    
    # This loads the DBE extension module.
    
        Load        "dbe"  # Double buffer extension
    
    # This loads the miscellaneous extensions module, and disables
    # initialisation of the XFree86-DGA extension within that module.
        SubSection  "extmod"
          Option    "omit xfree86-dga"   # don't initialise the DGA extension
        EndSubSection
    
    # This loads the Type1 and FreeType font modules
        Load        "type1"
        Load        "freetype"
    
    # This loads the GLX module
        Load       "glx"
    
    EndSection
    
    # **********************************************************************
    # Files section.  This allows default font and rgb paths to be set
    # **********************************************************************
    
    Section "Files"
    
    # The location of the RGB database.  Note, this is the name of the
    # file minus the extension (like ".txt" or ".db").  There is normally
    # no need to change the default.
    
        RgbPath"/usr/X11R6/lib/X11/rgb"
    
    # Multiple FontPath entries are allowed (which are concatenated together),
    # as well as specifying multiple comma-separated entries in one FontPath
    # command (or a combination of both methods)
    # 
    # If you don't have a floating point coprocessor and emacs, Mosaic or other
    # programs take long to start up, try moving the Type1 and Speedo directory
    # to the end of this list (or comment them out).
    # 
    
    #    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
        FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
        FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
        FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
        FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
        FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
        FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
        FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    
    # The module search path.  The default path is shown here.
    
    #    ModulePath "/usr/X11R6/lib/modules"
    
    EndSection
    
    # **********************************************************************
    # Server flags section.
    # **********************************************************************
    
    Section "ServerFlags"
    
    # Uncomment this to cause a core dump at the spot where a signal is 
    # received.  This may leave the console in an unusable state, but may
    # provide a better stack trace in the core dump to aid in debugging
    
    #    Option "NoTrapSignals"
    
    # Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
    # (where n is 1 through 12).  This allows clients to receive these key
    # events.
    
    #    Option "DontVTSwitch"
    
    # Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
    # This allows clients to receive this key event.
    
    #    Option "DontZap"
    
    # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
    # sequences.  This allows clients to receive these key events.
    
    #    Option "Dont Zoom"
    
    # Uncomment this to disable tuning with the xvidtune client. With
    # it the client can still run and fetch card and monitor attributes,
    # but it will not be allowed to change them. If it tries it will
    # receive a protocol error.
    
    #    Option "DisableVidModeExtension"
    
    # Uncomment this to enable the use of a non-local xvidtune client. 
    
    #    Option "AllowNonLocalXvidtune"
    
    # Uncomment this to disable dynamically modifying the input device
    # (mouse and keyboard) settings. 
    
    #    Option "DisableModInDev"
    
    # Uncomment this to enable the use of a non-local client to
    # change the keyboard or mouse settings (currently only xset).
    
    #    Option "AllowNonLocalModInDev"
    
    EndSection
    
    # **********************************************************************
    # Input devices
    # **********************************************************************
    
    # **********************************************************************
    # Core keyboard's InputDevice section
    # **********************************************************************
    
    Section "InputDevice"
    
        Identifier"Keyboard1"
        Driver"Keyboard"
    # For most OSs the protocol can be omitted (it defaults to "Standard").
    # When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
    # uncomment the following line.
    
    #    Option     "Protocol"      "Xqueue"
    
        Option "AutoRepeat" "500 30"
    
    # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
    #    Option"Xleds"      "1 2 3"
    
    #    Option "LeftAlt"     "Meta"
    #    Option "RightAlt"    "ModeShift"
    
    # To customise the XKB settings to suit your keyboard, modify the
    # lines below (which are the defaults).  For example, for a non-U.S.
    # keyboard, you will probably want to use:
    #    Option "XkbModel"    "pc102"
    # If you have a US Microsoft Natural keyboard, you can use:
    #    Option "XkbModel"    "microsoft"
    #
    # Then to change the language, change the Layout setting.
    # For example, a german layout can be obtained with:
    #    Option "XkbLayout"   "de"
    # or:
    #    Option "XkbLayout"   "de"
    #    Option "XkbVariant"  "nodeadkeys"
    #
    # If you'd like to switch the positions of your capslock and
    # control keys, use:
    #    Option "XkbOptions"  "ctrl:swapcaps"
    
    # These are the default XKB settings for XFree86
    #    Option "XkbRules"    "xfree86"
    #    Option "XkbModel"    "pc101"
    #    Option "XkbLayout"   "us"
    #    Option "XkbVariant"  ""
    #    Option "XkbOptions"  ""
    
    #    Option "XkbDisable"
    
        Option "XkbRules""xfree86"
        Option "XkbModel""pc101"
        Option "XkbLayout""us"
        Option "XkbVariant""us"
    
    EndSection
    
    
    # **********************************************************************
    # Core Pointer's InputDevice section
    # **********************************************************************
    
    Section "InputDevice"
    
    # Identifier and driver
    
        Identifier"Mouse1"
        Driver"mouse"
        Option "Protocol"    "IntelliMouse"
        Option "Device"      "/dev/mouse"
    
    # When using XQUEUE, comment out the above two lines, and uncomment
    # the following line.
    
    #    Option "Protocol""Xqueue"
    
    # Baudrate and SampleRate are only for some Logitech mice. In
    # almost every case these lines should be omitted.
    
    #    Option "BaudRate""9600"
    #    Option "SampleRate""150"
    
    # Emulate3Buttons is an option for 2-button Microsoft mice
    # Emulate3Timeout is the timeout in milliseconds (default is 50ms)
    
    #    Option "Emulate3Buttons"
    #    Option "Emulate3Timeout"    "50"
    
    # ChordMiddle is an option for some 3-button Logitech mice
    
    #    Option "ChordMiddle"
    
    EndSection
    
    
    # **********************************************************************
    # Other input device sections 
    # this is optional and is required only if you
    # are using extended input devices.  This is for example only.  Refer
    # to the XF86Config man page for a description of the options.
    # **********************************************************************
    #
    #
    # Section "InputDevice"
    #    Identifier "spaceball"
    #    Driver     "magellan"
    #    Option     "Device"        "/dev/cua0"
    # EndSection
    #
    # Section "InputDevice"
    #    Identifier "spaceball2"
    #    Driver     "spaceorb"
    #    Option     "Device"        "/dev/cua0"
    # EndSection
    #
    # Section "InputDevice"
    #    Identifier "touchscreen0"
    #    Driver     "microtouch"
    #    Option     "Device"        "/dev/ttyS0"
    #    Option     "MinX"          "1412"
    #    Option     "MaxX"          "15184"
    #    Option     "MinY"          "15372"
    #    Option     "MaxY"          "1230"
    #    Option     "ScreenNumber"  "0"
    #    Option     "ReportingMode" "Scaled"
    #    Option     "ButtonNumber"  "1"
    #    Option     "SendCoreEvents"
    # EndSection
    #
    # Section "InputDevice"
    #    Identifier "touchscreen1"
    #    Driver     "elo2300"
    #    Option     "Device"        "/dev/ttyS0"
    #    Option     "MinX"          "231"
    #    Option     "MaxX"          "3868"
    #    Option     "MinY"          "3858"
    #    Option     "MaxY"          "272"
    #    Option     "ScreenNumber"  "0"
    #    Option     "ReportingMode" "Scaled"
    #    Option     "ButtonThreshold"       "17"
    #    Option     "ButtonNumber"  "1"
    #    Option     "SendCoreEvents"
    # EndSection
    
    # **********************************************************************
    # Monitor section
    # **********************************************************************
    
    # Any number of monitor sections may be present
    
    Section "Monitor"
    
        Identifier  "My Monitor"
    
    # HorizSync is in kHz unless units are specified.
    # HorizSync may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
    
        HorizSync   31.5 - 48.5
    
    #    HorizSync30-64         # multisync
    #    HorizSync31.5, 35.2    # multiple fixed sync frequencies
    #    HorizSync15-25, 30-50  # multiple ranges of sync frequencies
    
    # VertRefresh is in Hz unless units are specified.
    # VertRefresh may be a comma separated list of discrete values, or a
    # comma separated list of ranges of values.
    # NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
    # USER MANUAL FOR THE CORRECT NUMBERS.
    
        VertRefresh 50-90
    
    EndSection
    
    
    # **********************************************************************
    # Graphics device section
    # **********************************************************************
    
    # Any number of graphics device sections may be present
    
    # Standard VGA Device:
    
    #Section "Device"
    #    Identifier"Standard VGA"
    #   VendorName"Unknown"
    #  BoardName"Unknown"
    
    # The chipset line is optional in most cases.  It can be used to override
    # the driver's chipset detection, and should not normally be specified.
    
    #    Chipset"generic"
    
    # The Driver line must be present.  When using run-time loadable driver
    # modules, this line instructs the server to load the specified driver
    # module.  Even when not using loadable driver modules, this line
    # indicates which driver should interpret the information in this section.
    
        Driver     "vga"
    # The BusID line is used to specify which of possibly multiple devices
    # this section is intended for.  When this line isn't present, a device
    # section can only match up with the primary video device.  For PCI
    # devices a line like the following could be used.  This line should not
    # normally be included unless there is more than one video device
    # intalled.
    
    #    BusID      "PCI:0:10:0"
    
    #    VideoRam256
    
    #    Clocks25.2 28.3
    
    EndSection
    
    # Device configured by xf86config:
    
    Section "Device"
        Identifier  "NVIDIA GeForce"
        Driver      "nv"
        #VideoRam    4096
        # Insert Clocks lines here if appropriate
    EndSection
    
    
    # **********************************************************************
    # Screen sections
    # **********************************************************************
    
    # Any number of screen sections may be present.  Each describes
    # the configuration of a single screen.  A single specific screen section
    # may be specified from the X server command line with the "-screen"
    # option.
    Section "Screen"
        Identifier  "Screen 1"
        Device      "NVIDIA GeForce"
        Monitor     "My Monitor"
        DefaultDepth 24
    
        Subsection "Display"
            Depth       8
            Modes       "640x480" "800x600" "1024x768" "1280x1024"
            ViewPort    0 0
        EndSubsection
        Subsection "Display"
            Depth       16
            Modes       "640x480" "800x600" "1024x768" "1280x1024"
            ViewPort    0 0
        EndSubsection
        Subsection "Display"
            Depth       24
            Modes       "640x480" "800x600" "1024x768" "1280x1024"
            ViewPort    0 0
        EndSubsection
    EndSection
    
    # **********************************************************************
    # ServerLayout sections.
    # **********************************************************************
    
    # Any number of ServerLayout sections may be present.  Each describes
    # the way multiple screens are organised.  A specific ServerLayout
    # section may be specified from the X server command line with the
    # "-layout" option.  In the absence of this, the first section is used.
    # When now ServerLayout section is present, the first Screen section
    # is used alone.
    
    Section "ServerLayout"
    
    # The Identifier line must be present
        Identifier  "Simple Layout"
    
    # Each Screen line specifies a Screen section name, and optionally
    # the relative position of other screens.  The four names after
    # primary screen name are the screens to the top, bottom, left and right
    # of the primary screen.  In this example, screen 2 is located to the
    # right of screen 1.
    
        Screen "Screen 1"
    
    # Each InputDevice line specifies an InputDevice section name and
    # optionally some options to specify the way the device is to be
    # used.  Those options include "CorePointer", "CoreKeyboard" and
    # "SendCoreEvents".
    
        InputDevice "Mouse1" "CorePointer"
        InputDevice "Keyboard1" "CoreKeyboard"
    
    EndSection
    I have a nVidia GeForceFX 5200
    Optiquest Q71 monitor
    and one M$ optical USE wheelmouse

    TIA
    Michael

  2. #2

    Re:Debian "Testing" XF86Config

    hi micheal - i am not sure if the xfree86 nv driver that ships with sid supports the fx5200 - infact i doubt it does if this page is correct... http://packages.debian.org/unstable/x11/xfree86-common

    xfree86 4.2 listed ... xfree86 4.3 has been out for a very long time.

  3. #3

    Re:Debian "Testing" XF86Config

    Hey I installed it but it said it was already there. Right now i'm not sure what I need to do. ???

  4. #4

    Re:Debian "Testing" XF86Config

    here is my xfree86 config, that is for a gf4
    http://home.covad.net/~pbharris/XF86Config

  5. #5

    Re:Debian "Testing" XF86Config

    Code:
    # File generated by xf86config and me.
    
    # **********************************************************************
    # Module section -- this  section  is used to specify
    # which dynamically loadable modules to load.
    # **********************************************************************
    #
    Section "Module"
    
    # This loads the DBE extension module.
    
        Load        "dbe"     # Double buffer extension
    Load  "extmod"
    Load  "fbdevhw"
    Load  "glx"
    Load  "record"
        Load        "type1"
        Load        "freetype"
    
    # This loads the GLX module
        Load      "glx"
    
    EndSection
    
    # **********************************************************************
    # Files section.  This allows default font and rgb paths to be set
    # **********************************************************************
    
    Section "Files"
    
    # The location of the RGB database.  Note, this is the name of the
    # file minus the extension (like ".txt" or ".db").  There is normally
    # no need to change the default.
    
        RgbPath   "/usr/X11R6/lib/X11/rgb"
    
    # Multiple FontPath entries are allowed (which are concatenated together),
    # as well as specifying multiple comma-separated entries in one FontPath
    # command (or a combination of both methods)
    #
    # If you don't have a floating point coprocessor and emacs, Mosaic or other
    # programs take long to start up, try moving the Type1 and Speedo directory
    # to the end of this list (or comment them out).
    #
    
    #    FontPath  "/usr/X11R6/lib/X11/fonts/local/"
        FontPath  "/usr/X11R6/lib/X11/fonts/misc/"
        FontPath  "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
        FontPath  "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
        FontPath  "/usr/X11R6/lib/X11/fonts/Type1/"
        FontPath  "/usr/X11R6/lib/X11/fonts/Speedo/"
        FontPath  "/usr/X11R6/lib/X11/fonts/75dpi/"
        FontPath  "/usr/X11R6/lib/X11/fonts/100dpi/"
    
    # The module search path.  The default path is shown here.
    
    #    ModulePath "/usr/X11R6/lib/modules"
    
    EndSection
    
    # **********************************************************************
    # Server flags section.
    # **********************************************************************
    
    Section "ServerFlags"
    
    # Uncomment this to cause a core dump at the spot where a signal is
    # received.  This may leave the console in an unusable state, but may
    # provide a better stack trace in the core dump to aid in debugging
    
    #    Option "NoTrapSignals"
    
    # Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
    # (where n is 1 through 12).  This allows clients to receive these key
    # events.
    
    #    Option "DontVTSwitch"
    
    # Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
    # This allows clients to receive this key event.
    
    #    Option "DontZap"
    
    # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
    # sequences.  This allows clients to receive these key events.
    
    #    Option "Dont Zoom"
    
    # Uncomment this to disable tuning with the xvidtune client. With
    # it the client can still run and fetch card and monitor attributes,
    # but it will not be allowed to change them. If it tries it will
    # receive a protocol error.
    
    #    Option "DisableVidModeExtension"
    
    # Uncomment this to enable the use of a non-local xvidtune client.
    
    #    Option "AllowNonLocalXvidtune"
    
    # Uncomment this to disable dynamically modifying the input device
    # (mouse and keyboard) settings.
    
    #    Option "DisableModInDev"
    
    # Uncomment this to enable the use of a non-local client to
    # change the keyboard or mouse settings (currently only xset).
    
    #    Option "AllowNonLocalModInDev"
    
    EndSection
    
    # **********************************************************************
    # Input devices
    # **********************************************************************
    
    # **********************************************************************
    # Core keyboard's InputDevice section
    # **********************************************************************
    
    Section "InputDevice"
    
        Identifier   "Keyboard1"
        Driver   "Keyboard"
        Option "AutoRepeat" "500 30"
        Option "XkbRules"   "xfree86"
        Option "XkbModel"   "pc101"
        Option "XkbLayout"   "us"
        Option "XkbVariant"   "us"
    
    EndSection
    
    
    # **********************************************************************
    # Core Pointer's InputDevice section
    # **********************************************************************
    
    
    Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option    "Protocol" "IMPS/2"
    Option    "Device" "/dev/input/mice"
    Option    "ZAxisMapping" "4 5"
    Option    "Emulate3Buttons" "no"
    EndSection
    
    # Any number of monitor sections may be present
    
    Section "Monitor"
        Identifier  "My Monitor"
        HorizSync  31.5 - 48.5
        VertRefresh 50-90
    
    EndSection
    
    Section "Device"
        Identifier  "NVIDIA GeForce"
        Driver      "nvidia"
        #VideoRam    4096
        # Insert Clocks lines here if appropriate
    EndSection
    
    
    # **********************************************************************
    # Screen sections
    # **********************************************************************
    
    # Any number of screen sections may be present.  Each describes
    # the configuration of a single screen.  A single specific screen section
    # may be specified from the X server command line with the "-screen"
    # option.
    Section "Screen"
        Identifier  "Screen 1"
        Device      "NVIDIA GeForce"
        Monitor    "My Monitor"
        DefaultDepth 24
    
        Subsection "Display"
            Depth      8
            Modes      "640x480" "800x600" "1024x768" "1280x1024"
            ViewPort    0 0
        EndSubsection
        Subsection "Display"
            Depth      16
            Modes      "640x480" "800x600" "1024x768" "1280x1024"
            ViewPort    0 0
        EndSubsection
        Subsection "Display"
            Depth      24
            Modes      "640x480" "800x600" "1024x768" "1280x1024"
            ViewPort    0 0
        EndSubsection
    EndSection
    
    # **********************************************************************
    # ServerLayout sections.
    # **********************************************************************
    
    # Any number of ServerLayout sections may be present.  Each describes
    # the way multiple screens are organised.  A specific ServerLayout
    # section may be specified from the X server command line with the
    # "-layout" option.  In the absence of this, the first section is used.
    # When now ServerLayout section is present, the first Screen section
    # is used alone.
    
    Section "ServerLayout"
    
    # The Identifier line must be present
        Identifier  "Simple Layout"
    
    # Each Screen line specifies a Screen section name, and optionally
    # the relative position of other screens.  The four names after
    # primary screen name are the screens to the top, bottom, left and right
    # of the primary screen.  In this example, screen 2 is located to the
    # right of screen 1.
    
        Screen "Screen 1"
    
    # Each InputDevice line specifies an InputDevice section name and
    # optionally some options to specify the way the device is to be
    # used.  Those options include "CorePointer", "CoreKeyboard" and
    # "SendCoreEvents".
    
        InputDevice "Mouse1" "CorePointer"
        InputDevice "Keyboard1" "CoreKeyboard"
    
    EndSection
    #c is for cookie - its good enough for me!
    #c is for cookie - its good enough for me!
    hopefully this will work with the nvidia module

  6. #6

    Re:Debian "Testing" XF86Config

    Code:
    #c is for cookie - its good enough for me!
    What is that???

  7. #7

    Re:Debian "Testing" XF86Config

    [quote author=trickster link=board=1;threadid=8610;start=0#msg77763 date=1075495116]
    Code:
    #c is for cookie - its good enough for me!
    What is that???
    [/quote]

    cookie monster

  8. #8
    Moderator
    Good Guru
    Compunuts's Avatar
    Join Date
    May 2001
    Location
    California
    Posts
    3,935

    Re:Debian "Testing" XF86Config

    [quote author=The Great Mojo Jojo link=board=1;threadid=8610;start=0#msg77753 date=1075480063]
    Code:
    Section "InputDevice"
    
    # Identifier and driver
    
        Identifier   "Mouse1"
        Driver   "mouse"
        Option "Protocol"    "IntelliMouse"
        Option "Device"      "/dev/mouse"
    and one M$ optical USE wheelmouse
    [/quote]
    I have no-name Optical mouse with scroll wheel and the mouse use IMPS/2 driver.

    I'm not sure it would help but you can give it a shoot.

  9. #9
    Guest

    Re:Debian "Testing" XF86Config

    I found that debian is extremely stupid... I had to manually modprobe mousedev to get my mouse running, it can be turned on in /etc/modules or something like that for automation joy and happiness..


  10. #10

    Re:Debian "Testing" XF86Config

    Try adding this to /etc/modules:

    mousedev
    psmouse

    Or the equivalent.

    I had to add them to mine, but I'm using an ordinary ps/2 mouse, no USB or Wheel.

Similar Threads

  1. Using K3b with Debian "Etch"
    By John_Deere_630 in forum Ubuntu / Debian
    Replies: 5
    Last Post: 04-18-2006, 01:35 AM
  2. "MicroHat" "SoftRed"
    By Fatal Error in forum General Chat
    Replies: 0
    Last Post: 05-12-2005, 09:03 PM
  3. "groupadd" and "tree" utilities are nowhere??
    By aromes in forum Redhat / Fedora
    Replies: 1
    Last Post: 10-05-2003, 03:50 AM
  4. Replies: 1
    Last Post: 10-25-2002, 01:04 PM
  5. Xlib:  extension "GLX" missing on display ":0.0".
    By ph34r in forum Linux - Software, Applications & Programming
    Replies: 5
    Last Post: 12-06-2001, 04:52 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •