View previous topic :: View next topic |
Author |
Message |
shippy n00b
Joined: 29 Sep 2002 Posts: 9
|
Posted: Mon Oct 07, 2002 5:55 pm Post subject: X so slow to start up w/NVidia drivers |
|
|
It seems like I've tried just about everything here, but when I start up X (my wm is fvwm2), it takes almost 30 seconds to start up and my monitor stays black with clicking noises the entire time. I've tried all sorts of options given in the different forums and webpages, but I'm just having no luck. I'm using Gentoo 1.4_rc1 w/kernel 2.4.19. Here are the relevant sections of my XF86Config-4
Code: |
Section "Monitor"
Identifier "Generic"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30.0-69.0
VertRefresh 50.0-120.0
ModeLine "1024x768@85" 99.511 1024 1056 1408 1440 768 769 777 813 -hsync -vsync
ModeLine "800x600@85" 56.566 800 824 1024 1048 600 601 607 635 -hsync -vsync
ModeLine "640x480@85" 34.199 640 656 776 792 480 481 486 508 -hsync -vsync
EndSection
Section "Device"
Identifier "Diamond Viper V550"
VendorName "Unknown"
BoardName "Unknown"
Driver "nvidia"
VideoRam 16384
# Uncomment following option if you see a big white block
# instead of the cursor!
# Option "sw_cursor"
Option "NvAGP" "3"
# Option "power_saver"
Option "DPMS"
Option "NoLogo" "TRUE"
EndSection
Section "Screen"
Identifier "screen1"
Device "Diamond Viper V550"
Monitor "Generic"
DefaultColorDepth 24
Option "IgnoreEdid" "1"
Option "GenerateRTList" "0"
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection
EndSection
|
When I run 'startx', I tail -f it from another machine and
this is what I get:
Code: |
(II) NVIDIA XFree86 Driver 1.0-2960 Tue May 14 07:45:20 PDT 2002
(II) NVIDIA: NVIDIA driver for: RIVA TNT, RIVA TNT2, Vanta,
RIVA TNT2 Ultra, RIVA TNT2 Model 64, Aladdin TNT2, GeForce 256,
GeForce DDR, Quadro, GeForce2 MX/MX 400, GeForce2 MX 100/200,
Quadro2 MXR/EX/Go, GeForce2 Integrated GPU, GeForce2 GTS,
GeForce2 Ti, GeForce2 Ultra, Quadro2 Pro, GeForce4 MX 460,
GeForce4 MX 440, GeForce4 MX 420, Quadro4 500/550 XGL,
Quadro4 200/400 NVS, GeForce3, GeForce3 Ti 200, GeForce3 Ti 500,
Quadro DCC, GeForce4 Ti 4600, GeForce4 Ti 4400, GeForce4 Ti 4200,
Quadro4 900 XGL, Quadro4 750 XGL, Quadro4 700 XGL, GeForce2 Go,
GeForce4 440 Go, GeForce4 420 Go, GeForce4 420 Go 32M,
GeForce4 440 Go 64M, Quadro4 500 GoGL
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset RIVA TNT found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0xf4000000 - 0xf4007fff (0x8000) MX[B]
[6] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B]
[7] -1 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[8] -1 0xf5000000 - 0xf5ffffff (0x1000000) MX[B](B)
[9] -1 0x0000ffff - 0x0000ffff (0x1) IX[B]
[10] -1 0x00000000 - 0x000000ff (0x100) IX[B]
[11] -1 0x00001000 - 0x0000103f (0x40) IX[B]
[12] -1 0x00001040 - 0x0000105f (0x20) IX[B]
[13] -1 0x00001060 - 0x0000106f (0x10) IX[B]
(II) resource ranges after probing:
[0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0xf4000000 - 0xf4007fff (0x8000) MX[B]
[6] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B]
[7] -1 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[8] -1 0xf5000000 - 0xf5ffffff (0x1000000) MX[B](B)
[9] 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[10] 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[11] 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[12] -1 0x0000ffff - 0x0000ffff (0x1) IX[B]
[13] -1 0x00000000 - 0x000000ff (0x100) IX[B]
[14] -1 0x00001000 - 0x0000103f (0x40) IX[B]
[15] -1 0x00001040 - 0x0000105f (0x20) IX[B]
[16] -1 0x00001060 - 0x0000106f (0x10) IX[B]
[17] 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[18] 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="The XFree86 Project"
compiled for 4.2.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "TRUE"
(**) NVIDIA(0): Option "NvAGP" "3"
(**) NVIDIA(0): Option "IgnoreEDID" "1"
(**) NVIDIA(0): Use of any AGP requested (try AGPGART, then try NVIDIA's AGP)
(**) NVIDIA(0): Ignoring EDIDs
(--) NVIDIA(0): Linear framebuffer at 0xFC000000
(--) NVIDIA(0): MMIO registers at 0xF5000000
# There is a small delay here
(--) NVIDIA(0): VideoRAM: 16384 kBytes
# There is a HUGE delay here after which it prints
# everything below this immediately and X starts up. I'm
# not sure where in this process it's hanging, though.
(--) NVIDIA(0): Detected TV Encoder: Brooktree 868
(--) NVIDIA(0): Display 0: maximum pixel clock at 8 bpp: 250 MHz
(--) NVIDIA(0): Display 0: maximum pixel clock at 16 bpp: 250 MHz
(--) NVIDIA(0): Display 0: maximum pixel clock at 32 bpp: 215 MHz
(II) NVIDIA(0): Not probing EDIDs.
(II) NVIDIA(0): Generic: Using hsync range of 30.00-69.00 kHz
(II) NVIDIA(0): Generic: Using vrefresh range of 50.00-120.00 Hz
(II) NVIDIA(0): Clock range: 12.00 to 215.00 MHz
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (bad mode clock/interlace/d
oublescan)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (bad mode clock/interlace/d
oublescan)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (bad mode clock/interlace/d
oublescan)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (bad mode clock/interlace/d
oublescan)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/d
oublescan)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (bad mode clock/interlace/d
oublescan)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(**) NVIDIA(0): Validated modes for Display Device 0:
(**) NVIDIA(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(**) NVIDIA(0): Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
(**) NVIDIA(0): Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
(==) NVIDIA(0): DPI set to (75, 75)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/X11R6/lib/modules/libfb.a
(II) Module fb: vendor="The XFree86 Project"
compiled for 4.2.0, module version = 1.0.0
ABI class: XFree86 ANSI C Emulation, version 0.1
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="The XFree86 Project"
compiled for 4.2.0, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.5
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/X11R6/lib/modules/libramdac.a
(II) Module ramdac: vendor="The XFree86 Project"
compiled for 4.2.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0xfc000000 - 0xfcffffff (0x1000000) MX[B]
[1] 0 0xf5000000 - 0xf5ffffff (0x1000000) MX[B]
[2] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[3] -1 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[4] -1 0x000f0000 - 0x000fffff (0x10000) MX[B]
[5] -1 0x000c0000 - 0x000effff (0x30000) MX[B]
[6] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[7] -1 0xf4000000 - 0xf4007fff (0x8000) MX[B]
[8] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B]
[9] -1 0xfc000000 - 0xfcffffff (0x1000000) MX[B](B)
[10] -1 0xf5000000 - 0xf5ffffff (0x1000000) MX[B](B)
[11] 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[12] 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[13] 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[14] -1 0x0000ffff - 0x0000ffff (0x1) IX[B]
[15] -1 0x00000000 - 0x000000ff (0x100) IX[B]
[16] -1 0x00001000 - 0x0000103f (0x40) IX[B]
[17] -1 0x00001040 - 0x0000105f (0x20) IX[B]
[18] -1 0x00001060 - 0x0000106f (0x10) IX[B]
[19] 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[20] 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(II) NVIDIA(0): AGP 2X successfully initialized
(II) NVIDIA(0): Setting mode "1024x768"
(II) NVIDIA(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid filled trapezoids
8x8 mono pattern filled rectangles
8x8 mono pattern filled trapezoids
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Offscreen Pixmaps
Driver provided FillSolidRects replacement
Driver provided FillSolidSpans replacement
Driver provided FillMono8x8PatternRects replacement
Driver provided WritePixmap replacement
Driver provided ReadPixmap replacement
Setting up tile and stipple cache:
16 128x128 slots
4 256x256 slots
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-GLX
(II) Loading extension NV-CONTROL
(WW) NVIDIA(0): Option "GenerateRTList" is not used
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) [GLX]: Calling GlxExtensionInit
(**) Option "Protocol" "IMPS/2"
(**) Mouse1: Protocol: "IMPS/2"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/mouse"
(**) Option "Buttons" "6"
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 6
(**) Option "Resolution" "1200"
(**) Mouse1: Resolution: 1200
(II) Keyboard "Keyboard1" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
|
I'm pretty stumped. If anyone has any ideas, please let
me know. Thanks! _________________ Jeff Shipman
shippy@nmt.edu |
|
Back to top |
|
|
Malakin Veteran
Joined: 14 Apr 2002 Posts: 1692 Location: Victoria BC Canada
|
Posted: Mon Oct 07, 2002 8:03 pm Post subject: |
|
|
You might want to list what you've tried so we don't all just repeat them to you, but the most obvious is adding "127.0.0.1 hostname" to your /etc/hosts file, where hostname is your actual hostname of course (echo $HOSTNAME if you're not sure). |
|
Back to top |
|
|
shippy n00b
Joined: 29 Sep 2002 Posts: 9
|
Posted: Mon Oct 07, 2002 8:33 pm Post subject: |
|
|
Malakin wrote: | You might want to list what you've tried so we don't all just repeat them to you, but the most obvious is adding "127.0.0.1 hostname" to your /etc/hosts file, where hostname is your actual hostname of course (echo $HOSTNAME if you're not sure). |
Yep, tried that. I kept it 192.168.0.3 (which is what it really is) and I've tried it as 127.0.0.1. Nada. localhost is still set to 127.0.0.1.
I can't even remember everything I've tried. I've done the hostname thing, making my own modeline and setting all the various options like IgnoreEdid and GenerateRTList and probably a bunch of other things, but I can't remember _________________ Jeff Shipman
shippy@nmt.edu |
|
Back to top |
|
|
MacMasta Guru
Joined: 18 Apr 2002 Posts: 545 Location: Anchorage, AK
|
Posted: Mon Oct 07, 2002 9:25 pm Post subject: |
|
|
Try specifying your resolution and vsync / hsync a little more tightly - the clicking noises mean the monitor & video card are trying to agree on a setting, and the startx output seems to agree.
~Mac~ |
|
Back to top |
|
|
shippy n00b
Joined: 29 Sep 2002 Posts: 9
|
Posted: Mon Oct 07, 2002 11:07 pm Post subject: |
|
|
MacMasta wrote: | Try specifying your resolution and vsync / hsync a little more tightly - the clicking noises mean the monitor & video card are trying to agree on a setting, and the startx output seems to agree.
~Mac~ |
Unfortunately this didn't help. I greatly reduced the vsync / hsync and I specified only a single resolution, but it still takes just as long. I don't remember it taking this long when I used the exact same config file and driver under Debian. _________________ Jeff Shipman
shippy@nmt.edu |
|
Back to top |
|
|
zepar Tux's lil' helper
Joined: 28 Jul 2002 Posts: 107
|
Posted: Tue Oct 08, 2002 12:30 am Post subject: |
|
|
Well, i have the same problem and it seems there is no fix. I also tried mandrake and redhat, the same problem. In the time of mandrake 8.0 the nvidia driver worked fine. Somebody broked something. |
|
Back to top |
|
|
amittp Tux's lil' helper
Joined: 02 Jul 2002 Posts: 123 Location: USA
|
Posted: Tue Oct 08, 2002 10:40 am Post subject: |
|
|
I think you should also enable MTRR in kernel. I thnk it might help.
[/quote] _________________ Believe in yourself |
|
Back to top |
|
|
shippy n00b
Joined: 29 Sep 2002 Posts: 9
|
Posted: Tue Oct 08, 2002 2:10 pm Post subject: |
|
|
amittp wrote: | I think you should also enable MTRR in kernel. I thnk it might help.
|
Sorry. Been there, done that. _________________ Jeff Shipman
shippy@nmt.edu |
|
Back to top |
|
|
helmers Guru
Joined: 16 Sep 2002 Posts: 553 Location: Stange, Norway
|
Posted: Sat Oct 19, 2002 9:12 am Post subject: |
|
|
Try with the "nv" driver. I have the same problem, a delay of about 14 seconds. I used to run Windows XP, the same thing there. What MB are you using? VIA?
--
Regards
Helmers |
|
Back to top |
|
|
Houdini Apprentice
Joined: 14 Jun 2002 Posts: 224 Location: New Mexico Tech, Socorro, NM
|
Posted: Sat Oct 19, 2002 10:22 am Post subject: |
|
|
Hi Jeff! (heh... NMT students congregate on the gentoo forums...)
Unfortunately, this seems to be a common problem. On my machine, it takes a good 30 seconds to startx. I seem to remember that it would go by faster if I ran at a crap resolution, but that's no help :/
Anyway, I have no fix. Just wanted to commiserate about the nvidia drivers. _________________ ^]:wq |
|
Back to top |
|
|
dioxmat Bodhisattva
Joined: 04 May 2002 Posts: 709 Location: /home/mat
|
Posted: Sat Oct 19, 2002 1:02 pm Post subject: |
|
|
I dont have such a problem with my nvidia driver.
what modules are you loading ?
(oh and I'm not using these :
Code: |
Option "IgnoreEdid" "1"
Option "GenerateRTList" "0"
|
) |
|
Back to top |
|
|
SlCKB0Y Tux's lil' helper
Joined: 07 Jul 2002 Posts: 105 Location: Sydney, Australia
|
Posted: Sun Oct 20, 2002 2:45 am Post subject: |
|
|
get rid of the mode lines. im willing to bet these are the cause.
as long as the v and h syncs are exactly as specified in your monitor manual, youll be fine.
and comment out the video ram line. it usually isnt needed either, it will normally be detected |
|
Back to top |
|
|
kappax Apprentice
Joined: 30 Aug 2002 Posts: 273 Location: The Moon
|
Posted: Sun Oct 20, 2002 2:48 am Post subject: |
|
|
Try this
modprobe NVdriver NVreg_SkipBiosPost=1 |
|
Back to top |
|
|
Houdini Apprentice
Joined: 14 Jun 2002 Posts: 224 Location: New Mexico Tech, Socorro, NM
|
Posted: Tue Oct 29, 2002 5:12 am Post subject: |
|
|
I've tried everything in this thread. My comments:
Code: |
Option "IgnoreEdid" "1"
Option "GenerateRTList" "0" |
No go here. There weren't there before, and adding them didn't help.
Code: | modprobe NVdriver NVreg_SkipBiosPost=1 |
I get this in response:
Code: |
Warning: loading /lib/modules/2.4.19-crypto-r7/video/NVdriver will taint the kernel: non-GPL license - NVIDIA
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Warning: ignoring NVreg_SkipBiosPost=1, no such parameter in this module
Module NVdriver loaded, with warnings
|
Uh... yeah. _________________ ^]:wq |
|
Back to top |
|
|
perra n00b
Joined: 10 Jun 2002 Posts: 20 Location: Canberra, Australia
|
Posted: Fri Nov 01, 2002 7:51 am Post subject: |
|
|
I just upgraded my GeForce2 to a GeForce4. Everything was fine with the GeForce2 card, I'm having the same problem as you with the GeForce4.
My log looks pretty much like yours with a lot of "hsync out of range". I guess my card decided to should use the following:
Code: |
(**) NVIDIA(0): Validated modes for Display Device 0:
(**) NVIDIA(0): Default mode "1152x864": 108.0 MHz, 67.5 kHz, 75.0 Hz
(**) NVIDIA(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(**) NVIDIA(0): Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
(**) NVIDIA(0): Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
|
If I were to out that down in the config file somehow, would that speed up the start-up? |
|
Back to top |
|
|
SlCKB0Y Tux's lil' helper
Joined: 07 Jul 2002 Posts: 105 Location: Sydney, Australia
|
Posted: Fri Nov 01, 2002 8:08 am Post subject: |
|
|
did u try getting rid of the mode lines in the config file as i suggested before? |
|
Back to top |
|
|
helmers Guru
Joined: 16 Sep 2002 Posts: 553 Location: Stange, Norway
|
Posted: Fri Nov 01, 2002 10:36 am Post subject: |
|
|
Oh, I was in touch with my manufacturers(MSI) tech support,
and they said that they had multiple complaints from people using NVidias drivers, in Windows. He said MSI don't support linux, but he believed it to be a problem with the NVidia driver itself. Do someone know of a way to contact nvidia about this? Because the "nv" driver have no such delay, perhaps they can look at it and figure out what they are doing wrong...
--
Regards,
Helmers |
|
Back to top |
|
|
blunt88 n00b
Joined: 03 Nov 2002 Posts: 22
|
Posted: Tue Dec 31, 2002 11:30 pm Post subject: |
|
|
I think this may help some people
look at my posting in this thread
sorry, I don't know how to get it to jump right to my post
good luck |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|