Help getting PCLinuxOS installed to your computer.

Moderators: slax, sarcastic_bastard

GRUB error codes

Postby don_crissti » Sun May 24, 2009 5:10 am

ERRORS REPORTED BY THE STAGE 1
The general way that the Stage 1 handles errors is to print an error string and then halt. Pressing CTRL-ALT-DEL will reboot.

The following is a comprehensive list of error messages for the Stage 1:
  • "Hard Disk Error"
    This error message will occur if the Stage 2 or Stage 1.5 is being read from a hard disk, and the attempt to determine the size and geometry of the hard disk fails.
  • "Floppy Error"
    This error message will occur if the Stage 2 or Stage 1.5 is being read from a floppy disk, and the attempt to determine the size and geometry of the floppy disk fails. It's listed as a different error since the probe sequence is different than for hard disks.
  • "Read Error"
    This error message will occur if a disk read error happens while trying to read the Stage 2 or Stage 1.5.
  • "Geom Error"
    This error message will occur if the location of the Stage 2 or Stage 1.5 is not in the area supported by reading the disk with the BIOS directly. This could occur because the BIOS translated geometry has been changed by the user or the disk is moved to another machine or controller after installation, or GRUB was not installed using itself (if it was, the Stage 2 version of this error would have been seen during that process and it would not have completed the install).
ERRORS REPORTED BY THE STAGE 1.5
The general way that the Stage 1.5 handles errors is to print an error number in the form "Error: " and then halt. Pressing Ctrl-Alt-Del will reboot.

The error numbers correspond to the Errors Reported by the Stage 2 in the listed sequence.

ERRORS REPORTED BY THE STAGE 2
The general way that the Stage 2 handles errors is to abort the operation in question, print an error string, then (if possible) either continue based on the fact that an error occurred or wait for the user to deal with the error.

The following is a comprehensive list of error messages for the Stage 2 (error numbers for the Stage 1.5 are listed before the colon in each description):
  • Error 1 : Filename must be either an absolute filename or blocklist
    This error is returned if a file name is requested which doesn't fit the syntax/rules listed in the Filesystem.
  • Error 2 : Bad file or directory type
    This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO.
  • Error 3 : Bad or corrupt data while decompressing file
    This error is returned if the run-length decompression code gets an internal error. This is usually from a corrupt file.
  • Error 4 : Bad or incompatible header in compressed file
    This error is returned if the file header for a supposedly compressed file is bad.
  • Error 5 : Partition table invalid or corrupt
    This error is returned if the sanity checks on the integrity of the partition table fail. This is a bad sign.
  • Error 6 : Mismatched or corrupt version of stage1/stage2
    This error is returned if the install command points to incompatible or corrupt versions of the stage1 or stage2. It can't detect corruption in general, but this is a sanity check on the version numbers, which should be correct.
  • Error 7 : Loading below 1MB is not supported
    This error is returned if the lowest address in a kernel is below the 1MB boundary. The Linux zImage format is a special case and can be handled since it has a fixed loading address and maximum size.
  • Error 8 : Kernel must be loaded before booting
    This error is returned if GRUB is told to execute the boot sequence without having a kernel to start.
  • Error 9 : Unknown boot failure
    This error is returned if the boot attempt did not succeed for reasons which are unknown.
  • Error 10 : Unsupported Multiboot features requested
    This error is returned when the Multiboot features word in the Multiboot header requires a feature that is not recognized. The point of this is that the kernel requires special handling which GRUB is probably unable to provide.
  • Error 11 : Unrecognized device string
    This error is returned if a device string was expected, and the string encountered didn't fit the syntax/rules listed in the Filesystem.
  • Error 12 : Invalid device requested
    This error is returned if a device string is recognizable but does not fall under the other device errors.
  • Error 13 : Invalid or unsupported executable format
    This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).
  • Error 14 : Filesystem compatibility error, cannot read whole file
    Some of the filesystem reading code in GRUB has limits on the length of the files it can read. This error is returned when the user runs into such a limit.
  • Error 15 : File not found
    This error is returned if the specified file name cannot be found, but everything else (like the disk/partition info) is OK.
  • Error 16 : Inconsistent filesystem structure
    This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
  • Error 17 : Cannot mount selected partition
    This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB.
  • Error 18 : Selected cylinder exceeds maximum supported by BIOS
    This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general).
  • Error 19 : Linux kernel must be loaded before initrd
    This error is returned if the initrd command is used before loading a Linux kernel.
  • Error 20 : Multiboot kernel must be loaded before modules
    This error is returned if the module load command is used before loading a Multiboot kernel. It only makes sense in this case anyway, as GRUB has no idea how to communicate the presence of such modules to a non-Multiboot-aware kernel.
  • Error 21 : Selected disk does not exist
    This error is returned if the device part of a device- or full file name refers to a disk or BIOS device that is not present or not recognized by the BIOS in the system.
  • Error 22 : No such partition
    This error is returned if a partition is requested in the device part of a device- or full file name which isn't on the selected disk.
  • Error 23 : Error while parsing number
    This error is returned if GRUB was expecting to read a number and encountered bad data.
  • Error 24 : Attempt to access block outside partition
    This error is returned if a linear block address is outside of the disk partition. This generally happens because of a corrupt filesystem on the disk or a bug in the code handling it in GRUB (it's a great debugging tool).
  • Error 25 : Disk read error
    This error is returned if there is a disk read error when trying to probe or read data from a particular disk.
  • Error 26 : Too many symbolic links
    This error is returned if the link count is beyond the maximum (currently 5), possibly the symbolic links are looped.
  • Error 27 : Unrecognized command
    This error is returned if an unrecognized command is entered on the command-line or in a boot sequence section of a configuration file and that entry is selected.
  • Error 28 : Selected item cannot fit into memory
    This error is returned if a kernel, module, or raw file load command is either trying to load its data such that it won't fit into memory or it is simply too big.
  • Error 29 : Disk write error
    This error is returned if there is a disk write error when trying to write to a particular disk. This would generally only occur during an install of set active partition command.
  • Error 30 : Invalid argument
    This error is returned if an argument specified to a command is invalid.
  • Error 31 : File is not sector aligned
    This error may occur only when you access a ReiserFS partition by block-lists (e.g. the command install). In this case, you should mount the partition with the `-o notail' option.
  • Error 32 : Must be authenticated
    This error is returned if you try to run a locked entry. You should enter a correct password before running such an entry.
  • Error 33 : Serial device not configured
    This error is returned if you try to change your terminal to a serial one before initializing any serial device.
  • Error 34 : No spare sectors on the disk
    This error is returned if a disk doesn't have enough spare space. This happens when you try to embed Stage 1.5 into the unused sectors after the MBR, but the first partition starts right after the MBR or they are used by EZ-BIOS.
Those who cling to life, die; those who defy death, live.
Uesugi Kenshin
don_crissti
User avatar
Hero Member
Hero Member
 
Posts: 2261
Joined: Thu Nov 15, 2007 2:16 pm

Re: GRUB error codes

Postby cousinlucky » Mon Oct 29, 2012 12:03 pm

don_crissti wrote:ERRORS REPORTED BY THE STAGE 1
The general way that the Stage 1 handles errors is to print an error string and then halt. Pressing CTRL-ALT-DEL will reboot.

The following is a comprehensive list of error messages for the Stage 1:
  • "Hard Disk Error"
    This error message will occur if the Stage 2 or Stage 1.5 is being read from a hard disk, and the attempt to determine the size and geometry of the hard disk fails.
  • "Floppy Error"
    This error message will occur if the Stage 2 or Stage 1.5 is being read from a floppy disk, and the attempt to determine the size and geometry of the floppy disk fails. It's listed as a different error since the probe sequence is different than for hard disks.
  • "Read Error"
    This error message will occur if a disk read error happens while trying to read the Stage 2 or Stage 1.5.
  • "Geom Error"
    This error message will occur if the location of the Stage 2 or Stage 1.5 is not in the area supported by reading the disk with the BIOS directly. This could occur because the BIOS translated geometry has been changed by the user or the disk is moved to another machine or controller after installation, or GRUB was not installed using itself (if it was, the Stage 2 version of this error would have been seen during that process and it would not have completed the install).
ERRORS REPORTED BY THE STAGE 1.5
The general way that the Stage 1.5 handles errors is to print an error number in the form "Error: " and then halt. Pressing Ctrl-Alt-Del will reboot.

The error numbers correspond to the Errors Reported by the Stage 2 in the listed sequence.

ERRORS REPORTED BY THE STAGE 2
The general way that the Stage 2 handles errors is to abort the operation in question, print an error string, then (if possible) either continue based on the fact that an error occurred or wait for the user to deal with the error.

The following is a comprehensive list of error messages for the Stage 2 (error numbers for the Stage 1.5 are listed before the colon in each description):
  • Error 1 : Filename must be either an absolute filename or blocklist
    This error is returned if a file name is requested which doesn't fit the syntax/rules listed in the Filesystem.
  • Error 2 : Bad file or directory type
    This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO.
  • Error 3 : Bad or corrupt data while decompressing file
    This error is returned if the run-length decompression code gets an internal error. This is usually from a corrupt file.
  • Error 4 : Bad or incompatible header in compressed file
    This error is returned if the file header for a supposedly compressed file is bad.
  • Error 5 : Partition table invalid or corrupt
    This error is returned if the sanity checks on the integrity of the partition table fail. This is a bad sign.
  • Error 6 : Mismatched or corrupt version of stage1/stage2
    This error is returned if the install command points to incompatible or corrupt versions of the stage1 or stage2. It can't detect corruption in general, but this is a sanity check on the version numbers, which should be correct.
  • Error 7 : Loading below 1MB is not supported
    This error is returned if the lowest address in a kernel is below the 1MB boundary. The Linux zImage format is a special case and can be handled since it has a fixed loading address and maximum size.
  • Error 8 : Kernel must be loaded before booting
    This error is returned if GRUB is told to execute the boot sequence without having a kernel to start.
  • Error 9 : Unknown boot failure
    This error is returned if the boot attempt did not succeed for reasons which are unknown.
  • Error 10 : Unsupported Multiboot features requested
    This error is returned when the Multiboot features word in the Multiboot header requires a feature that is not recognized. The point of this is that the kernel requires special handling which GRUB is probably unable to provide.
  • Error 11 : Unrecognized device string
    This error is returned if a device string was expected, and the string encountered didn't fit the syntax/rules listed in the Filesystem.
  • Error 12 : Invalid device requested
    This error is returned if a device string is recognizable but does not fall under the other device errors.
  • Error 13 : Invalid or unsupported executable format
    This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).
  • Error 14 : Filesystem compatibility error, cannot read whole file
    Some of the filesystem reading code in GRUB has limits on the length of the files it can read. This error is returned when the user runs into such a limit.
  • Error 15 : File not found
    This error is returned if the specified file name cannot be found, but everything else (like the disk/partition info) is OK.
  • Error 16 : Inconsistent filesystem structure
    This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
  • Error 17 : Cannot mount selected partition
    This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB.
  • Error 18 : Selected cylinder exceeds maximum supported by BIOS
    This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general).
  • Error 19 : Linux kernel must be loaded before initrd
    This error is returned if the initrd command is used before loading a Linux kernel.
  • Error 20 : Multiboot kernel must be loaded before modules
    This error is returned if the module load command is used before loading a Multiboot kernel. It only makes sense in this case anyway, as GRUB has no idea how to communicate the presence of such modules to a non-Multiboot-aware kernel.
  • Error 21 : Selected disk does not exist
    This error is returned if the device part of a device- or full file name refers to a disk or BIOS device that is not present or not recognized by the BIOS in the system.
  • Error 22 : No such partition
    This error is returned if a partition is requested in the device part of a device- or full file name which isn't on the selected disk.
  • Error 23 : Error while parsing number
    This error is returned if GRUB was expecting to read a number and encountered bad data.
  • Error 24 : Attempt to access block outside partition
    This error is returned if a linear block address is outside of the disk partition. This generally happens because of a corrupt filesystem on the disk or a bug in the code handling it in GRUB (it's a great debugging tool).
  • Error 25 : Disk read error
    This error is returned if there is a disk read error when trying to probe or read data from a particular disk.
  • Error 26 : Too many symbolic links
    This error is returned if the link count is beyond the maximum (currently 5), possibly the symbolic links are looped.
  • Error 27 : Unrecognized command
    This error is returned if an unrecognized command is entered on the command-line or in a boot sequence section of a configuration file and that entry is selected.
  • Error 28 : Selected item cannot fit into memory
    This error is returned if a kernel, module, or raw file load command is either trying to load its data such that it won't fit into memory or it is simply too big.
  • Error 29 : Disk write error
    This error is returned if there is a disk write error when trying to write to a particular disk. This would generally only occur during an install of set active partition command.
  • Error 30 : Invalid argument
    This error is returned if an argument specified to a command is invalid.
  • Error 31 : File is not sector aligned
    This error may occur only when you access a ReiserFS partition by block-lists (e.g. the command install). In this case, you should mount the partition with the `-o notail' option.
  • Error 32 : Must be authenticated
    This error is returned if you try to run a locked entry. You should enter a correct password before running such an entry.
  • Error 33 : Serial device not configured
    This error is returned if you try to change your terminal to a serial one before initializing any serial device.
  • Error 34 : No spare sectors on the disk
    This error is returned if a disk doesn't have enough spare space. This happens when you try to embed Stage 1.5 into the unused sectors after the MBR, but the first partition starts right after the MBR or they are used by EZ-BIOS.


I get an error 15 from grub :

title linux
kernel /boot/vmlinuz BOOT_IMAGE=linux root=UUID=724d4a16-ba54-4fd5-9baf-31eda641e342 resume=UUID=9307dbd7-b13b-46b2-b330-caa85f5b9bd4 splash=silent vga=788
initrd /boot/initrd.img

Can anyone here give me the correct filename for my new install of PCLinuxOS Gnome 2010.12? Thank You!!
cousinlucky
Full Member
Full Member
 
Posts: 67
Joined: Mon Oct 29, 2012 10:52 am

Re: GRUB error codes

Postby ongoto » Mon Oct 29, 2012 5:01 pm

cousinlucky wrote:I get an error 15 from grub :

title linux
kernel /boot/vmlinuz BOOT_IMAGE=linux root=UUID=724d4a16-ba54-4fd5-9baf-31eda641e342 resume=UUID=9307dbd7-b13b-46b2-b330-caa85f5b9bd4 splash=silent vga=788
initrd /boot/initrd.img

Can anyone here give me the correct filename for my new install of PCLinuxOS Gnome 2010.12? Thank You!!


/boot/vmlinuz ( and possibly /boot/initrd.img ) would be the only filenames grub would know about.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
--Only a penguin could make a nest out of some rocks--
--Twitter--
--An eternal gem ala Joble--
ongoto
User avatar
Hero Member
Hero Member
 
Posts: 1192
Joined: Sun Mar 01, 2009 12:53 pm
Location: California, USA

Re: GRUB error codes

Postby cousinlucky » Tue Oct 30, 2012 10:49 pm

Below is the file grub uses to start my Antix distro and I need the file that will start my PCLinuxOS gnome 2010.12 distro.

title antiX at sda1, kernel 3.5.0-antix.2-486-smp
kernel /boot/vmlinuz-3.5.0-antix.2-486-smp root=/dev/sda1 nomce quiet nosplash nouveau.modeset=0 vga=791
initrd /boot/initrd.img-3.5.0-antix.2-486-smp
cousinlucky
Full Member
Full Member
 
Posts: 67
Joined: Mon Oct 29, 2012 10:52 am

Re: GRUB error codes

Postby ongoto » Wed Oct 31, 2012 2:48 am

Maybe you meant this?

vmlinuz is a link which points to a file in the /boot/ directory.
Open a terminal and run ls -al /boot.

On my system I see vmlinuz points to this file...
vmlinuz -> vmlinuz-2.6.38.8-pclos3.a64
Yours may differ.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
--Only a penguin could make a nest out of some rocks--
--Twitter--
--An eternal gem ala Joble--
ongoto
User avatar
Hero Member
Hero Member
 
Posts: 1192
Joined: Sun Mar 01, 2009 12:53 pm
Location: California, USA

Re: GRUB error codes

Postby cousinlucky » Wed Oct 31, 2012 12:03 pm

cousinlucky@antiX1:~
$ ls -al /boot
total 17808
drwxr-xr-x 4 root root 4096 Oct 26 17:23 .
drwxr-xr-x 20 root root 4096 Oct 25 14:01 ..
-rw-r--r-- 1 root root 137197 Jul 31 07:32 config-3.5.0-antix.2-486-smp
drwxr-xr-x 2 root root 4096 Aug 6 14:57 extlinux
drwxr-xr-x 2 root root 4096 Oct 31 00:39 grub
-rw-r--r-- 1 root root 12555406 Oct 26 17:23 initrd.img-3.5.0-antix.2-486-smp
-rw-r--r-- 1 root root 176764 Oct 24 2011 memtest86+.bin
-rw-r--r-- 1 root root 178944 Oct 24 2011 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 1763082 Jul 31 08:29 System.map-3.5.0-antix.2-486-smp
-rw-r--r-- 1 root root 3392528 Jul 31 08:29 vmlinuz-3.5.0-antix.2-486-smp
cousinlucky@antiX1:~
$
cousinlucky
Full Member
Full Member
 
Posts: 67
Joined: Mon Oct 29, 2012 10:52 am

Re: GRUB error codes

Postby ongoto » Wed Oct 31, 2012 12:24 pm

Ok I see what you are up against. Can you show me this file please?
/boot/grub/menu.lst
And tell me which partition you installed PCLOS on.
I think you may need to add an entry for it in Antix.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
--Only a penguin could make a nest out of some rocks--
--Twitter--
--An eternal gem ala Joble--
ongoto
User avatar
Hero Member
Hero Member
 
Posts: 1192
Joined: Sun Mar 01, 2009 12:53 pm
Location: California, USA

Re: GRUB error codes

Postby cousinlucky » Wed Oct 31, 2012 12:48 pm

cousinlucky@antiX1:~
$ cat /boot/grub/menu.lst
timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title antiX at sda1, kernel 3.5.0-antix.2-486-smp
kernel /boot/vmlinuz-3.5.0-antix.2-486-smp root=/dev/sda1 nomce quiet nosplash nouveau.modeset=0 vga=791
initrd /boot/initrd.img-3.5.0-antix.2-486-smp
boot

title linux
kernel /boot/vmlinuz BOOT_IMAGE=linux root=UUID=724d4a16-ba54-4fd5-9baf-31eda641e342 resume=UUID=9307dbd7-b13b-46b2-b330-caa85f5b9bd4 splash=silent vga=788
initrd /boot/initrd.img

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=f414e622-c48e-4f81-9983-95f358629646 ro
# kopt_2_6=root=UUID=f414e622-c48e-4f81-9983-95f358629646 ro nosplash quiet

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(init-3) 3

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title antiX-12, kernel 3.5.0-antix.2-486-smp
root (hd0,0)
kernel /boot/vmlinuz-3.5.0-antix.2-486-smp root=UUID=f414e622-c48e-4f81-9983-95f358629646 ro
initrd /boot/initrd.img-3.5.0-antix.2-486-smp

title antiX-12, kernel 3.5.0-antix.2-486-smp (init-3)
root (hd0,0)
kernel /boot/vmlinuz-3.5.0-antix.2-486-smp root=UUID=f414e622-c48e-4f81-9983-95f358629646 ro 3
initrd /boot/initrd.img-3.5.0-antix.2-486-smp

title antiX-12, kernel memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST
cousinlucky@antiX1:~

PCLinuxOS gnome is installed on sda3 on my computer.
Thanks for your help.

I think that if I replace my grub menu list PCLinux file with yours my problem will be solved.
cousinlucky
Full Member
Full Member
 
Posts: 67
Joined: Mon Oct 29, 2012 10:52 am

Re: GRUB error codes

Postby ongoto » Wed Oct 31, 2012 1:24 pm

Grub needs a "root" statement so it can find the right (disk,partition).
The "configfile" statement will display the PCLOS menu.lst and you can go from there.

Make these changes ( in red ) and let us know what happens.

timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu (hd0,0)/boot/grub/message

title antiX at sda1, kernel 3.5.0-antix.2-486-smp
root (hd0,0)
kernel /boot/vmlinuz-3.5.0-antix.2-486-smp root=/dev/sda1 nomce quiet nosplash nouveau.modeset=0 vga=791
initrd /boot/initrd.img-3.5.0-antix.2-486-smp
boot

title PCLinuxOS
root (hd0,2)
configfile /boot/grub/menu.lst



### BEGIN AUTOMAGIC KERNELS LIST
...
...
...
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
--Only a penguin could make a nest out of some rocks--
--Twitter--
--An eternal gem ala Joble--
ongoto
User avatar
Hero Member
Hero Member
 
Posts: 1192
Joined: Sun Mar 01, 2009 12:53 pm
Location: California, USA

Re: GRUB error codes

Postby cousinlucky » Wed Oct 31, 2012 2:50 pm

10,000 Thank You's, Ongoto!! It worked perfectly!!
I am Forever In Your Debt!!
cousinlucky
Full Member
Full Member
 
Posts: 67
Joined: Mon Oct 29, 2012 10:52 am

Forum Statistics

Who is online

Users browsing this forum: No registered users and 1 guest

Options

Return to PCLinuxOS Gnome HD Installation

cron