Crack-wifi.com FORUM

LE FORUM DU SITE

Wifi, Backtrack, crack WEP et WPA...

Vous n'êtes pas identifié(e).  

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

#1 03-10-2009 16:20:57

bigboss560
Membre Radioactif
Inscription : 18-09-2009
Messages : 80

Petit (ou gros) problème de démarrage.

Salut,
Lorsque je boot sur Backtrack j'ai un joli petit message d'erreur, je vous explique :
Au démarrage de BT, après avoir rentre le fameux root et toor, j'ai bêtement tapé xconf (zut), le souci c'est qu'après quand je tape startx pour démarrer en interface graphique j'ai ce message qui apparait :

(==)Log file: "/var/log/Xorg.0.log"
(==)using config file : "/etc/X11/xorg.conf
(II) Module already built in
(EE)VESA(0): No matching modes
(EE)Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
giving up.
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3): Server Error

La, j'ai tout essayer (si si) mais rien n'y fait. Je précise qu'avant cela tout fonctionnait bien. Si vous pouviez m'aider, je suis dans une impasse. (une vrai impasse)

Hors Ligne

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

#2 03-10-2009 16:30:56

sardineeMule
Membre Irremplaçable
Inscription : 05-12-2008
Messages : 1 139
Site Web

Re : Petit (ou gros) problème de démarrage.

essaie de booter en "vesa kde"


title.jpg N'oubliez pas le site http://www.crack-wifi.com/
  nux  hight.jpg

Hors Ligne

#3 03-10-2009 16:39:18

bigboss560
Membre Radioactif
Inscription : 18-09-2009
Messages : 80

Re : Petit (ou gros) problème de démarrage.

Comment booter en vesa kde ? (je ne suis pas en live-CD et je n'ai que Windows d'installer (aussi Ubuntu, mais j'avais mal configurer Lilo) donc je ne peux pas modifier le fichier xconf.conf ou autres.)

Dernière modification par bigboss560 (03-10-2009 17:42:00)

Hors Ligne

#4 03-10-2009 18:29:05

bigboss560
Membre Radioactif
Inscription : 18-09-2009
Messages : 80

Re : Petit (ou gros) problème de démarrage.

Up.

Hors Ligne

#5 03-10-2009 21:32:44

qwertazert
Membre Irremplaçable
Inscription : 20-09-2009
Messages : 1 057

Re : Petit (ou gros) problème de démarrage.

pour modifier xconf.

tu reste en console.

Tu tape : (attention je suis pas sur du chemin, j'ai trouvé le chemin sur le net)

nano /etc/x11/xorg.conf

nano est la commande éditeur de de fichiers texte en mod console wink


Sinon, vesa KDE, je peux pas t'aider, je suis sous gnome

Dernière modification par qwertazert (03-10-2009 21:33:52)


[img align=g]http://imagik.fr/thumb/133444.jpeg[/img]Moïse dit à Dieu, 10 commandements !!! gravé sur des tablettes en pierres !!! C'est lourd !!!
Vous n'auriez pas une clé usb plutôt ? Dieu lui répondit.
Regardes moi droit dans les cieux et redis moi ça si tu ose !!!
Commandement N'11 : Ton voisin tu ne piratera point (Ceci n'est pas un lien)

Hors Ligne

#6 04-10-2009 19:22:10

bigboss560
Membre Radioactif
Inscription : 18-09-2009
Messages : 80

Re : Petit (ou gros) problème de démarrage.

Non , ce n'est plus la peine.  J'ai réussi a tout remettre en place (heureusement) et le boot de BackTrack et celui de Windows ainsi que celui d'Ubuntu (ca ma quand même pris 9h).

Hors Ligne

#7 04-10-2009 19:28:16

sardineeMule
Membre Irremplaçable
Inscription : 05-12-2008
Messages : 1 139
Site Web

Re : Petit (ou gros) problème de démarrage.

bigboss560 t'as fait comment ??? sa servira a d'autres wink


title.jpg N'oubliez pas le site http://www.crack-wifi.com/
  nux  hight.jpg

Hors Ligne

#8 05-10-2009 17:51:05

bigboss560
Membre Radioactif
Inscription : 18-09-2009
Messages : 80

Re : Petit (ou gros) problème de démarrage.

Bah je sais pas vraiment, j'ai un peu bidouiller le fichier Lilo.conf et xorg.conf (j'ai reconfiguré le fichier xorg pour qu'il lance fbdev a la place de vesa, la commande xconf (la plus horrible qui soit) me l'avait complètement bousiller, c'est donc la seule façon que j'ai pu trouver pour arranger le problème.)
Leurs contenus :

Lilo.conf:
boot = /dev/sda
prompt
timeout = 60
bitmap=/boot/fingerprint-lilosplash.bmp
bmp-colors = 5,,239,239,,5
bmp-table = 128p,313p,1,3
bmp-timer = none
change-rules
reset
#vga = 773,795/789/799
vga = 789
lba32
large-memory
image = /boot/vmlinuz
  vga = 792
  root = current
  label = BackTrack
  read-only


other = /dev/sda1
   label = Windows

image = /mnt/sda2/boot/vmlinuz-2.6.28-15-generic
  vga = normal
  initrd=/mnt/sda2/boot/initrd.img-2.6.28-15-generic
  label = Ubuntu
  root = /dev/sda2



PS: (le splash au début ne compte pas dans la configuration, c'était rajouter après pour le rendre bien plus jolie, le lien : http://www.kde-look.org/content/show.ph … tent=29675 )



Et le Xorg.conf :

Section "ServerLayout"
Identifier     "X.org Configured"
Screen      0  "Screen0" 0 0
InputDevice    "Mouse0" "CorePointer"
InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath      "/usr/share/X11/rgb"
ModulePath   "/usr/lib/xorg/modules"
FontPath     "/usr/share/fonts/TTF"
FontPath     "/usr/share/fonts/OTF"
FontPath     "/usr/share/fonts/Type1"
FontPath     "/usr/share/fonts/misc"
FontPath     "/usr/share/fonts/75dpi/:unscaled"
EndSection

Section "Module"
Load  "glx"
Load  "extmod"
Load  "xtrap"
Load  "record"
Load  "GLcore"
Load  "dbe"
Load  "dri"
Load  "freetype"
Load  "type1"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver      "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver      "mouse"
Option        "Protocol" "auto"
Option        "Device" "/dev/input/mice"
Option        "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName    "Monitor Model"
EndSection

Section "Device"
Identifier  "Card0"
Driver      "fbdev"
VendorName  "Intel Corporation"
BoardName   "Unknown Board"
BusID       "PCI:0:2:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device     "Card0"
Monitor    "Monitor0"
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

et pour terminer le fichier xorg.conf-fbdev (pas modifier je crois mais il ya le tableau, trés utile, j'ai pu modifier ces fichiers grace a la commande "mc")

xorg.conf-fbdev:

# 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.
# **********************************************************************

# This XF86Config file is designed for use with the Linux framebuffer console.
# This generic interface should work with nearly all video cards (although
# not every card will support every resolution).  To use the Linux framebuffer
# console, you need to enable these kernel options:
# Using 'make menuconfig', in 'console drivers', enable:
#   [*] VGA text console
#   [*] Video mode selection support
#   [*] Support for frame buffer devices (EXPERIMENTAL)
#   [*] VESA VGA graphics console
#   [*] Advanced low level driver options
#   <*> 8 bpp packed pixels support
#   <*> 16 bpp packed pixels support
#   <*> 24 bpp packed pixels support
#   <*> 32 bpp packed pixels support
#   <*> VGA characters/attributes support
#   [*] Select compiled-in fonts
#   [*]   VGA 8x8 font
#   [*]   VGA 8x16 font
# If you have a Matrox or ATI Mach64, you might try enabling the options having
# to do with those cards as well.  However, if the card is VESA compliant, you
# don't really need to (and it might cause problems, possibly)
#
# Next, if this file is not already named /etc/X11/XF86Config, make a copy
# with that name.  This file ships with the name XF86Config-fbdev to avoid
# overwriting an existing config file.
#
# To get the kernel to start in VESA framebuffer mode, you need to pass it
# a vga= init string at boot time.  For example, if you use LILO you'll
# probably find a vga=normal string in your /etc/lilo.conf.  If you edit that
# to one of the values in this table:
#
#   Colours   640x480 800x600 1024x768 1280x1024 1600x1200
#  --------+---------------------------------------------
#  256     |   769     771      773      775       796
#  32,768  |   784     787      790      793       797
#  65,536  |   785     788      791      794       798
#  16.8M   |   786     789      792      795       799
#
#  ...such as this for 1280x1024x64k:
#  vga = 795
#  and then reinstall LILO by running 'lilo' as root, then at the next boot
#  Linux should start in a VESA framebuffer console mode.
#
# For more information on how to activate the Linux frame buffer, see
# /usr/src/linux/Documentation/fb/vesafb.txt.
#
# Enjoy! smile
# -- [email protected]
#

# **********************************************************************
# 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 font modules
    Load        "type1"
    Load        "freetype"
    #Load        "speedo"

# 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/share/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/share/fonts/local/"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/Type1/"
    FontPath   "/usr/share/fonts/OTF/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
    FontPath   "/usr/share/fonts/100dpi/:unscaled"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

#    ModulePath "/usr/lib/xorg/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     "DontZoom"

# 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"

# Set the basic blanking screen saver timeout.

#    Option      "blank time"    "10"    # 10 minutes

# Set the DPMS timeouts.  These are set here because they are global
# rather than screen-specific.  These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

#    Option      "standby time"  "20"
#    Option      "suspend time"  "30"
#    Option      "off time"      "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option   "EstimateSizesAggresively" "0"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier    "Keyboard1"
    Driver    "kbd"
# 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"

# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.

#    Option     "AutoRepeat"    "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

#    Option     "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#    Option     "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option     "XkbModel"      "pc102"
#    Option     "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option     "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option     "XkbModel"      "pc104"
#
# 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 X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc105"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier    "Mouse1"
    Driver    "mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

#    Option     "Protocol"      "Auto"

# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
    Option "Protocol"    "PS/2"

# The mouse device.  The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

    Option "Device"      "/dev/mouse"
#   Option "Device"      "/dev/psaux"
#   Option "Device"      "/dev/ttyS0"
#   Option "Device"      "/dev/ttyS1"

# 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

# Some examples of extended input devices

# 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 - 50.0

#    HorizSync    30-64         # multisync
#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync    15-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 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "fbdev"
    #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      "VESA Framebuffer"
    Monitor     "My Monitor"

# You shouldn't need to set a default depth as the server will use
# whatever the framebuffer is set to.  If you insist on setting it, make
# sure it matches the setting for your framebuffer.
#   DefaultDepth 32

    Subsection "Display"
        Depth       8
    EndSubsection
    Subsection "Display"
        Depth       16
    EndSubsection
    Subsection "Display"
        Depth       24
    EndSubsection
    Subsection "Display"
        Depth       32
    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


Voila tout. Mais bon ce probleme n'as pas l'air trés populaire.

Hors Ligne

#9 24-02-2010 22:36:21

spyman
Membre
Inscription : 23-02-2010
Messages : 10

Re : Petit (ou gros) problème de démarrage.

ba voila j'ai se problème mai je vais renoncer a bt4 si il faut 9h pour le résoudre ...sniff

Hors Ligne

#10 26-02-2010 00:02:48

nxxo
Membre
Inscription : 31-01-2010
Messages : 24

Re : Petit (ou gros) problème de démarrage.

tape la commande "fixvesa" et ensuite tape "startx" voilà

Hors Ligne

Annonce

Visitez la boutique Wifi-highpower.com, votre revendeur agr Alfa Network: du matriel Wifi slectionn, cartes Wifi USB Awus036h et Awus036nh, antennes omnis, yagis, panel, amplis wifi, accessoires...

Sujets similaires

Discussion Réponses Vues Dernier message
4 92 Aujourd'hui 16:20:59 par pwerrick
Problème reaver par Antho3674
4 297 15-11-2016 22:05:12 par kcdtv
petit nouveau par drhouse
5 165 07-11-2016 18:31:17 par coyotus
3 333 14-08-2016 10:22:07 par MiscL
5 728 18-07-2016 23:13:58 par kcdtv

Pied de page des forums


Le coin des bonnes affaires, achats informatiques:


|   Alfa 1000 mW AWUS036H   |    Linksys WRT54GL   |    Misco, informatique   |   
 |    Ebay   |    PC portables   |    PC Gamers & Tuning   |    Cles USB   |   
|   Disques durs externes 2 To   |   
|   Wifi-highpower.com   |   


Server Stats - [ Generated in 0.029 seconds ]   Forum Stat - [ Most users ever online on the forum was : 150 on 20-09-2009 17:06:59 ]