CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 11 of 11
  1. March 16th, 2017, 03:43 PM #1
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Testing for mess up

    Code:
    1.4
Supp ort
What
kind
of
supp ort
is
available
for
MX
Linux?
The
answer
to
this
question
dep ends
on
the
typ e
of
supp ort
you
mean:
ˆ
User-based
problems
.
A
raft
of
supp ort
mechanisms
exists
for
MX
Linux,
from
do cuments
and
videos
to
forums
and
search
engines.
See
the
Community
Supp ort
page
for
details.
ˆ
Hardware
.
Hardware
is
supp orted
in
the
kernel,
where
continuous
development
go es
on.
Very
new
hardware
may
not
yet
b e
supp orted,
and
very
old
hardware,
though
still
supp orted,
may
no
longer
b e
sucient
for
the
demands
of
the
desktop
and
applications.
ˆ
Desktop
.
Xfce4
is
a
mature
desktop
that
remains
under
development.
The
version
shipp ed
with
MX
Linux
is
considered
stable;
imp ortant
up dates
will
b e
applied
as
they
b ecome
available.
ˆ
Applications
.
Applications
continue
to
b e
develop ed
after
the
release
of
any
version
of
MX
Linux,
meaning
that
the
shipp ed
versions
will
get
older
as
time
passes.
This
problem
is
addressed
through
a
combination
of
sources:
Debian,
individual
Develop ers
including
MX
Devs,
and
the
Community
Packaging
Team.
ˆ
Security
.
Security
up dates
from
Debian
will
cover
MX
Linux
users
well
into
the
foreseeable
future.
Community
Do cumentation
Project.
2017.
Users
Manual
for
MX
Linux.
1.3
System
requirements
For
an
MX
Linux
system
installed
on
a
hard
drive,
you
would
normally
need
the
following
comp onents.
Minimum
ˆ
A
CD/DVD
drive
(and
BIOS
capable
of
b o oting
from
that
drive),
or
a
live
USB
(and
BIOS
capable
of
b o oting
from
USB)
ˆ
A
mo dern
i486
Intel
or
AMD
pro cessor
ˆ
512
MB
of
RAM
memory
ˆ
5
GB
free
hard
drive
space
ˆ
A
SoundBlaster,
AC97
or
HDA-compatible
sound
card
ˆ
For
use
as
a
LiveUSB,
4
GB
free.
Recommended
ˆ
A
CD/DVD
drive
(and
BIOS
capable
of
b o oting
from
that
drive),
or
a
live
USB
(and
BIOS
capable
of
b o oting
from
USB)
ˆ
A
mo dern
i686
Intel
or
AMD
pro cessor
ˆ
2
GB
of
RAM
memory
or
more
ˆ
At
least
10
p ersistence
    https://mxlinux.org/user_manual_mx16/mxum.pdf
    Last edited by Shay2; March 16th, 2017 at 04:36 PM.
    Reply With Quote Reply With Quote
  2. March 16th, 2017, 03:57 PM #2
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Code:
    
	
    
		
    
			
    
			
				 For an MX Linux system installed on a hard drive, you would normally need the following components.
Minimum

    A CD/DVD drive (and BIOS capable of booting from that drive), or a live USB (and BIOS capable of booting from USB)
    A modern i486 Intel or AMD processor
    512 MB of RAM memory
    5 GB free hard drive space
    A SoundBlaster, AC97 or HDA-compatible sound card
    For use as a LiveUSB, 4 GB free.

Recommended

    A CD/DVD drive (and BIOS capable of booting from that drive), or a live USB (and BIOS capable of booting from USB)
    A modern i686 Intel or AMD processor
    2 GB of RAM memory or more
    At least 10 GB free hard drive space
    A 3D-capable video card for 3D desktop support
    For use as a LiveUSB, 8 GB free if using persistence.
			
		
    
	
    

    All content is © 2017 by MX Linux and
released
under
GPLv3.
Citation

    
	
    
		
    
			
    
			
				 What kind of support is available for MX Linux? The answer to this question depends on the type of support you mean:

    User-based problems. A raft of support mechanisms exists for MX Linux, from documents and videos to forums and search engines. See the Community Support page for details.
    Hardware. Hardware is supported in the kernel, where continuous development goes on. Very new hardware may not yet be supported, and very old hardware, though still supported, may no longer be sufficient for the demands of the desktop and applications.
    Desktop. Xfce4 is a mature desktop that remains under development. The version shipped with MX Linux is considered stable; important updates will be applied as they become available.
    Applications. Applications continue to be developed after the release of any version of MX Linux, meaning that the shipped versions will get older as time passes. This problem is addressed through a combination of sources: Debian, individual Developers including MX Devs, and the Community Packaging Team.
    Security. Security updates from Debian will cover MX Linux users well into the foreseeable future.

			
		
    
	
    

    should
read:
MX
Linux
Community
Do cumentation
Project.
2017.
Users
Manual
for
MX
Linux.
1.3
System
requirements
For
    Last edited by Shay2; March 16th, 2017 at 04:03 PM.
    Reply With Quote Reply With Quote
  3. March 16th, 2017, 04:11 PM #3
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Quote Originally Posted by Shay2 View Post
    Code:
    1.4
Supp ort
What
kind
of
supp ort
is
available
for
MX
Linux?
The
answer
to
this
question
dep ends
on
the
typ e
of
supp ort
you
mean:
ˆ
User-based
problems
.
A
raft
of
supp ort
mechanisms
exists
for
MX
Linux,
from
do cuments
and
videos
to
forums
and
search
engines.
See
the
Community
Supp ort
page
for
details.
ˆ
Hardware
.
Hardware
is
supp orted
in
the
kernel,
where
continuous
development
go es
on.
Very
new
hardware
may
not
yet
b e
supp orted,
and
very
old
hardware,
though
still
supp orted,
may
no
longer
b e
sucient
for
the
demands
of
the
desktop
and
applications.
ˆ
Desktop
.
Xfce4
is
a
mature
desktop
that
remains
under
development.
The
version
shipp ed
with
MX
Linux
is
considered
stable;
imp ortant
up dates
will
b e
applied
as
they
b ecome
available.
ˆ
Applications
.
Applications
continue
to
b e
develop ed
after
the
release
of
any
version
of
MX
Linux,
meaning
that
the
shipp ed
versions
will
get
older
as
time
passes.
This
problem
is
addressed
through
a
combination
of
sources:
Debian,
individual
Develop ers
including
MX
Devs,
and
the
Community
Packaging
Team.
ˆ
Security
.
Security
up dates
from
Debian
will
cover
MX
Linux
users
well
into
the
foreseeable
future.
Community
Do cumentation
Project.
2017.
Users
Manual
for
MX
Linux.
1.3
System
requirements
For
an
MX
Linux
system
installed
on
a
hard
drive,
you
would
normally
need
the
following
comp onents.
Minimum
ˆ
A
CD/DVD
drive
(and
BIOS
capable
of
b o oting
from
that
drive),
or
a
live
USB
(and
BIOS
capable
of
b o oting
from
USB)
ˆ
A
mo dern
i486
Intel
or
AMD
pro cessor
ˆ
512
MB
of
RAM
memory
ˆ
5
GB
free
hard
drive
space
ˆ
A
SoundBlaster,
AC97
or
HDA-compatible
sound
card
ˆ
For
use
as
a
LiveUSB,
4
GB
free.
Recommended
ˆ
A
CD/DVD
drive
(and
BIOS
capable
of
b o oting
from
that
drive),
or
a
live
USB
(and
BIOS
capable
of
b o oting
from
USB)
ˆ
A
mo dern
i686
Intel
or
AMD
pro cessor
ˆ
2
GB
of
RAM
memory
or
more
ˆ
At
least
10
GB
free
hard
drive
space
ˆ
A
3D-capable
video
card
for
3D
desktop
supp ort
ˆ
For
use
as
a
LiveUSB,
8
GB
free
if
using
p ersistence
    https://mxlinux.org/user_manual_mx16/mxum.pdf
    Without something here I got a not enough characters error
    inxi -F
    System: Host: antix16 Kernel: 4.10.1-antix.1-amd64-smp x86_64 (64 bit)
    Desktop: IceWM 1.3.8
    Distro: antiX-16.1_x64-full Berta Cáceres 16 January 2017
    Machine: Device: laptop System: Dell product: Latitude E6430 v: 01
    Mobo: Dell model: 0H3MT5 v: A00 BIOS: Dell v: A17 date: 08/19/2015
    Battery BAT0: charge: 20.3 Wh 27.9% condition: 72.8/90.0 Wh (81%)
    CPU: Dual core Intel Core i5-3320M (-HT-MCP-) cache: 3072 KB
    clock speeds: max: 3300 MHz 1: 1199 MHz 2: 1199 MHz 3: 1199 MHz
    4: 1199 MHz
    Graphics: Card-1: Intel 3rd Gen Core processor Graphics Controller
    Card-2: NVIDIA GF108GLM [NVS 5200M]
    Display Server: X.Org 1.16.4 drivers: nouveau,intel (unloaded: modesetting,fbdev,vesa)
    Resolution: 1600x900@59.99hz
    GLX Renderer: Mesa DRI Intel Ivybridge Mobile
    GLX Version: 3.0 Mesa 10.3.2
    Audio: Card Intel 7 Series/C210 Series Family High Definition Audio Controller
    driver: snd_hda_intel
    Sound: ALSA v: k4.10.1-antix.1-amd64-smp
    Network: Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e
    IF: eth0 state: down mac: d4:be9:868:c7
    Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi
    IF: wlan0 state: up mac: 24:77:03f:1e:94
    Drives: HDD Total Size: 120.0GB (11.6% used)
    ID-1: /dev/sda model: SanDisk_SDSSDA12 size: 120.0GB
    Partition: ID-1: / size: 106G used: 8.9G (9%) fs: ext4 dev: /dev/sda1
    ID-2: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
    Sensors: System Temperatures: cpu: 56.0C mobo: N/A gpu: 52.0
    Fan Speeds (in rpm): cpu: N/A
    Info: Processes: 170 Uptime: 15 min Memory: 640.7/7893.1MB
    Client: Shell (bash) inxi: 2.3.8
    Reply With Quote Reply With Quote
  4. March 16th, 2017, 04:12 PM #4
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Quote Originally Posted by Shay2 View Post
    Code:
    All content is © 2017 by MX Linux and
released
under
GPLv3.
Citation

should
read:
MX
Linux
Community
Do cumentation
Project.
2017.
Users
Manual
for
MX
Linux.
1.3
System
requirements
For
    Code:
     inxi -F
System:    Host: antix16 Kernel: 4.10.1-antix.1-amd64-smp x86_64 (64 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-16.1_x64-full Berta Cáceres 16 January 2017
Machine:   Device: laptop System: Dell product: Latitude E6430 v: 01
           Mobo: Dell model: 0H3MT5 v: A00 BIOS: Dell v: A17 date: 08/19/2015
Battery    BAT0: charge: 20.3 Wh 27.9% condition: 72.8/90.0 Wh (81%)
CPU:       Dual core Intel Core i5-3320M (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 3300 MHz 1: 1199 MHz 2: 1199 MHz 3: 1199 MHz
           4: 1199 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF108GLM [NVS 5200M]
           Display Server: X.Org 1.16.4 drivers: nouveau,intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1600x900@59.99hz
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile
           GLX Version: 3.0 Mesa 10.3.2
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Sound: ALSA v: k4.10.1-antix.1-amd64-smp
Network:   Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e
           IF: eth0 state: down mac: d4:be:d9:86:d8:c7
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi
           IF: wlan0 state: up mac: 24:77:03:df:1e:94
Drives:    HDD Total Size: 120.0GB (11.6% used)
           ID-1: /dev/sda model: SanDisk_SDSSDA12 size: 120.0GB
Partition: ID-1: / size: 106G used: 8.9G (9%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 56.0C mobo: N/A gpu: 52.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 15 min Memory: 640.7/7893.1MB
           Client: Shell (bash) inxi: 2.3.8
    Reply With Quote Reply With Quote
  5. March 16th, 2017, 04:35 PM #5
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Quote Originally Posted by Shay2 View Post
    Code:
    All content is © 2017 by MX Linux and
released
under
GPLv3.
Citation

should
read:
MX
Linux
Community
Do cumentation
Project.
2017.
Users
Manual
for
MX
Linux.
1.3
System
requirements
For
    Code:
     inxi -F
System:    Host: antix16 Kernel: 4.10.1-antix.1-amd64-smp x86_64 (64 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-16.1_x64-full Berta Cáceres 16 January 2017
Machine:   Device: laptop System: Dell product: Latitude E6430 v: 01
           Mobo: Dell model: 0H3MT5 v: A00 BIOS: Dell v: A17 date: 08/19/2015
Battery    BAT0: charge: 20.3 Wh 27.9% condition: 72.8/90.0 Wh (81%)
CPU:       Dual core Intel Core i5-3320M (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 3300 MHz 1: 1199 MHz 2: 1199 MHz 3: 1199 MHz
           4: 1199 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF108GLM [NVS 5200M]
           Display Server: X.Org 1.16.4 drivers: nouveau,intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1600x900@59.99hz
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile
           GLX Version: 3.0 Mesa 10.3.2
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Sound: ALSA v: k4.10.1-antix.1-amd64-smp
Network:   Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e
           IF: eth0 state: down mac: d4:be:d9:86:d8:c7
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi
           IF: wlan0 state: up mac: 24:77:03:df:1e:94
Drives:    HDD Total Size: 120.0GB (11.6% used)
           ID-1: /dev/sda model: SanDisk_SDSSDA12 size: 120.0GB
Partition: ID-1: / size: 106G used: 8.9G (9%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 56.0C mobo: N/A gpu: 52.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 15 min Memory: 640.7/7893.1MB
           Client: Shell (bash) inxi: 2.3.8
    Last edited by Shay2; March 16th, 2017 at 04:57 PM. Reason: test
    Reply With Quote Reply With Quote
  6. March 16th, 2017, 04:57 PM #6
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Quote Originally Posted by Shay2 View Post
    Code:
    All content is © 2017 by MX Linux and
released
under
GPLv3.
Citation
Code:

1.4
Supp ort
What
kind
of
supp ort
is
available
for
MX
Linux?
The
answer
to
this
question
dep ends
on
the
typ e
of
supp ort
you
mean:
ˆ
User-based
problems
.
A
raft
of
supp ort
mechanisms
exists
for
MX
Linux,
from
should
read:
MX
Linux
Community
Do cumentation
Project.
2017.
Users
Manual
for
MX
Linux.
1.3
System
requirements
For
    Code:
    1.4
Supp ort
What
kind
of
supp ort
is
available
for
MX
Linux?
The
answer
to
this
question
dep ends
on
the
typ e
of
supp ort
you
mean:
ˆ
User-based
problems
.
A
raft
of
supp ort
mechanisms
exists
for
MX
Linux,
from
    Code:
     inxi -F
System:    Host: antix16 Kernel: 4.10.1-antix.1-amd64-smp x86_64 (64 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-16.1_x64-full Berta Cáceres 16 January 2017
Machine:   Device: laptop System: Dell product: Latitude E6430 v: 01
           Mobo: Dell model: 0H3MT5 v: A00 BIOS: Dell v: A17 date: 08/19/2015
Battery    BAT0: charge: 20.3 Wh 27.9% condition: 72.8/90.0 Wh (81%)
CPU:       Dual core Intel Core i5-3320M (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 3300 MHz 1: 1199 MHz 2: 1199 MHz 3: 1199 MHz
           4: 1199 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF108GLM [NVS 5200M]
           Display Server: X.Org 1.16.4 drivers: nouveau,intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1600x900@59.99hz
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile
           GLX Version: 3.0 Mesa 10.3.2
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Sound: ALSA v: k4.10.1-antix.1-amd64-smp
Network:   Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e
           IF: eth0 state: down mac: d4:be:d9:86:d8:c7
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi
           IF: wlan0 state: up mac: 24:77:03:df:1e:94
Drives:    HDD Total Size: 120.0GB (11.6% used)
           ID-1: /dev/sda model: SanDisk_SDSSDA12 size: 120.0GB
Partition: ID-1: / size: 106G used: 8.9G (9%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 56.0C mobo: N/A gpu: 52.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 15 min Memory: 640.7/7893.1MB
           Client: Shell (bash) inxi: 2.3.8
    Code:
     inxi -F
System:    Host: antix16 Kernel: 4.10.1-antix.1-amd64-smp x86_64 (64 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-16.1_x64-full Berta Cáceres 16 January 2017
Machine:   Device: laptop System: Dell product: Latitude E6430 v: 01
           Mobo: Dell model: 0H3MT5 v: A00 BIOS: Dell v: A17 date: 08/19/2015
Battery    BAT0: charge: 20.3 Wh 27.9% condition: 72.8/90.0 Wh (81%)
CPU:       Dual core Intel Core i5-3320M (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 3300 MHz 1: 1199 MHz 2: 1199 MHz 3: 1199 MHz
           4: 1199 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF108GLM [NVS 5200M]
           Display Server: X.Org 1.16.4 drivers: nouveau,intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1600x900@59.99hz
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile
           GLX Version: 3.0 Mesa 10.3.2
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Sound: ALSA v: k4.10.1-antix.1-amd64-smp
Network:   Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e
           IF: eth0 state: down mac: d4:be:d9:86:d8:c7
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi
           IF: wlan0 state: up mac: 24:77:03:df:1e:94
Drives:    HDD Total Size: 120.0GB (11.6% used)
           ID-1: /dev/sda model: SanDisk_SDSSDA12 size: 120.0GB
Partition: ID-1: / size: 106G used: 8.9G (9%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 56.0C mobo: N/A gpu: 52.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 15 min Memory: 640.7/7893.1MB
           Client: Shell (bash) inxi: 2.3.8
    Last edited by Shay2; March 16th, 2017 at 05:47 PM.
    Reply With Quote Reply With Quote
  7. March 16th, 2017, 05:48 PM #7
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Quote Originally Posted by Shay2 View Post
    Code:
    1.4
Supp ort
What
kind
of
supp ort
is
available
for
MX
Linux?
The
answer
to
this
question
dep ends
on
the
typ e
of
supp ort
you
mean:
ˆ
User-based
problems
.
A
raft
of
supp ort
mechanisms
exists
for
MX
Linux,
from
    Code:
     inxi -F
System:    Host: antix16 Kernel: 4.10.1-antix.1-amd64-smp x86_64 (64 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-16.1_x64-full Berta Cáceres 16 January 2017
Machine:   Device: laptop System: Dell product: Latitude E6430 v: 01
           Mobo: Dell model: 0H3MT5 v: A00 BIOS: Dell v: A17 date: 08/19/2015
Battery    BAT0: charge: 20.3 Wh 27.9% condition: 72.8/90.0 Wh (81%)
CPU:       Dual core Intel Core i5-3320M (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 3300 MHz 1: 1199 MHz 2: 1199 MHz 3: 1199 MHz
           4: 1199 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF108GLM [NVS 5200M]
           Display Server: X.Org 1.16.4 drivers: nouveau,intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1600x900@59.99hz
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile
           GLX Version: 3.0 Mesa 10.3.2
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Sound: ALSA v: k4.10.1-antix.1-amd64-smp
Network:   Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e
           IF: eth0 state: down mac: d4:be:d9:86:d8:c7
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi
           IF: wlan0 state: up mac: 24:77:03:df:1e:94
Drives:    HDD Total Size: 120.0GB (11.6% used)
           ID-1: /dev/sda model: SanDisk_SDSSDA12 size: 120.0GB
Partition: ID-1: / size: 106G used: 8.9G (9%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 56.0C mobo: N/A gpu: 52.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 15 min Memory: 640.7/7893.1MB
           Client: Shell (bash) inxi: 2.3.8
    Code:
     inxi -F
System:    Host: antix16 Kernel: 4.10.1-antix.1-amd64-smp x86_64 (64 bit)
           Desktop: IceWM 1.3.8
           Distro: antiX-16.1_x64-full Berta Cáceres 16 January 2017
Machine:   Device: laptop System: Dell product: Latitude E6430 v: 01
           Mobo: Dell model: 0H3MT5 v: A00 BIOS: Dell v: A17 date: 08/19/2015
Battery    BAT0: charge: 20.3 Wh 27.9% condition: 72.8/90.0 Wh (81%)
CPU:       Dual core Intel Core i5-3320M (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 3300 MHz 1: 1199 MHz 2: 1199 MHz 3: 1199 MHz
           4: 1199 MHz
Graphics:  Card-1: Intel 3rd Gen Core processor Graphics Controller
           Card-2: NVIDIA GF108GLM [NVS 5200M]
           Display Server: X.Org 1.16.4 drivers: nouveau,intel (unloaded: modesetting,fbdev,vesa)
           Resolution: 1600x900@59.99hz
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile
           GLX Version: 3.0 Mesa 10.3.2
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel
           Sound: ALSA v: k4.10.1-antix.1-amd64-smp
Network:   Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e
           IF: eth0 state: down mac: d4:be:d9:86:d8:c7
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi
           IF: wlan0 state: up mac: 24:77:03:df:1e:94
Drives:    HDD Total Size: 120.0GB (11.6% used)
           ID-1: /dev/sda model: SanDisk_SDSSDA12 size: 120.0GB
Partition: ID-1: / size: 106G used: 8.9G (9%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 4.69GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 56.0C mobo: N/A gpu: 52.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 170 Uptime: 15 min Memory: 640.7/7893.1MB
           Client: Shell (bash) inxi: 2.3.8
    Code: This originally had brackets, They were dropped and the : put in place.
    Code:
    1.4
Supp ort
What
kind
of
supp ort
is
available
for
MX
Linux?
The
answer
to
this
question
dep ends
on
the
typ e
of
supp ort
you
mean:
ˆ
User-based
problems
.
A
raft
of
supp ort
mechanisms
exists
for
MX
Linux,
from
    Last edited by Shay2; March 16th, 2017 at 07:35 PM.
    Reply With Quote Reply With Quote
  8. March 16th, 2017, 07:44 PM #8
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    <!DOCTYPE html>
    <html>
    <head>
    </head>
    <body>
    <script>
    var x = "dho";
    var y = "t";
    var z = "i";
    var toggle = true;

    function blackBlue()
    {
    if (toggle == true)
    {
    toggle = false;
    y = <span style="color:black">color </span>
    }
    else
    {
    toggle = true;
    y = <span style="color:blue">color </span>
    }

    document.getElementById("theText").innerHTML = x + y + z;
    }
    </script>

    <p id="theText">dhoti</p> // ALL THE SAME COLOR, FOR STARTERS.

    <button type="button" onclick="blackBlue()">Toggle</button>
    </body>
    </html>
    Code:
    <!DOCTYPE html>
<html>
<head>
</head>
<body>
<script>
var x = "dho";
var y = "t";
var z = "i";
var toggle = true;

function blackBlue() 
	{
	if (toggle == true)
    {
    	toggle = false;
    	y = <span style="color:black">color </span>    
    }
    else
    {
    	toggle = true;
    	y = <span style="color:blue">color </span>
    }  

    document.getElementById("theText").innerHTML = x + y + z;
}
</script>

<p id="theText">dhoti</p>  // ALL THE SAME COLOR, FOR STARTERS.

<button type="button" onclick="blackBlue()">Toggle</button>
</body>
</html>
    Reply With Quote Reply With Quote
  9. March 16th, 2017, 07:46 PM #9
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Quote Originally Posted by Shay2 View Post
    Code: This originally had brackets, They were dropped and the : put in place.
    [code]
    n
    Code:
    <!DOCTYPE html>
<html>
<head>
</head>
<body>
<script>
var x = "dho";
var y = "t";
var z = "i";
var toggle = true;

function blackBlue() 
	{
	if (toggle == true)
    {
    	toggle = false;
    	y = <span style="color:black">color </span>    
    }
    else
    {
    	toggle = true;
    	y = <span style="color:blue">color </span>
    }  

    document.getElementById("theText").innerHTML = x + y + z;
}
</script>

<p id="theText">dhoti</p>  // ALL THE SAME COLOR, FOR STARTERS.

<button type="button" onclick="blackBlue()">Toggle</button>
</body>
</html>
    Reply With Quote Reply With Quote
  10. March 21st, 2017, 01:25 PM #10
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Code:
    <html>
<head>
<script>
var imagesArray = [
'https://assets.entrepreneur.com/content/3x2/1300/20150827173347-test-google-adwords-campaign-search-engine-internet.jpeg', 'https://yt3.ggpht.com/-DvvzUuiYGos/AAAAAAAAAAI/AAAAAAAAAAA/YoUb-VzIovA/s900-c-k-no-mo-rj-c0xffffff/photo.jpg', 'https://www.google.com/logos/doodles/2015/tu-bav-2015-5651988540817408-hp2x.jpg', 'https://www.google.com/doodle4google/images/splashes/featured.png', 'http://www.onetechstop.net/wp-content/uploads/2016/01/google-logo.jpg',
];
var usedImages = {};
var usedImagesCount = 0;
function displayImage(){
var num = Math.floor(Math.random() * (imagesArray.length));
if (!usedImages[num]){
document.canvas.src = imagesArray[num];
usedImages[num] = true;
usedImagesCount++;
if (usedImagesCount === imagesArray.length){
usedImagesCount = 0;
usedImages = {};
}
}
else {
displayImage();
}
}
</script>
</head>

<body>
<center>
<form name="imageForm">

<tr align="center">
<td>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
    Reply With Quote Reply With Quote
  11. March 21st, 2017, 01:27 PM #11
    Shay2
    Shay2 is offline Member +
    Join Date
    Mar 2017
    Posts
    600

    Re: Testing for mess up

    Glad that was fixed.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

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

Forum Rules




Click Here to Expand Forum to Full Width

Featured