[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Pan-users] To explain why I'm unwilling to up date my glib/gtk+/etc
From: |
Paul Crawford |
Subject: |
Re: [Pan-users] To explain why I'm unwilling to up date my glib/gtk+/etc libs ATM… |
Date: |
Wed, 06 Jul 2011 12:39:52 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 |
On 05/07/11 22:12, Duncan wrote <sniped>:
Don't forget the LiveCD/DVD/LivePlug that most distros have available
now. That lets you test them out far easier without installing, tho
especially the LiveCDs tend to work with high compression on the CD,
expanding parts of themselves into RAM to run, so the oldest, lowest-RAM
systems often can't run them when they can run an install to disk. But
certainly if you have a gig of RAM or more...
The 'live CD' (or its USB equivalent) is a great way of testing things
out, generally speaking if it works OK on a live CD then installing it
should be easy and no problems. However, there are some points also to note:
(1) If something won't quite work, in particular video or wifi, this can
sometimes be fixed using the propitiatory drivers. However, you can't
normally do this with a live CD as such a low level change involves a
reboot, and of course it resumes with the CD's copy...
(2) If you want to have a dual boot system with an old Windows install,
you need to have enough space on your main disk and be willing to
re-partition it.
Usually this works fine but *before* doing so please run Windows chkdsk
with the full surface scan option. This takes an hour or two normally to
complete and should make sure your system disk is OK and consistent
enough to be rearranged.
Windows will reboot at the end of this test, then go to the
Administrative tools' "event viewer" and under Application log (I think)
you can go back and see the results of chkdsk. Usually there is
something it complains about...
Also be *very suspicious* if it did not run as expect, as it possibly
indicates a root-kit infection.
(3) If you have more than one Windows-used HDD then disconnect all but
the primary (C:) one when re-partitioning and installing Linux. This
saves odd questions when installing the boot loader and difficult
behaviour if you don't give the correct non-intuitive answer... Once
installed, reconnect the extra HDD.
(4) Some nasty Windows software's DRM can use the boot area outside of
the NTFS file system (sectors 1-63) for storing its crap, this can break
grub, etc.
If you suspect this, install Linux on another HDD (Windows HDD
disconnected) and once installed and OK (all patches applied, etc),
reconnect the Windows HDD and in the PC's BIOS (usually you press the
'Del' or 'F2' key when booting) find the boot options section choose the
Linux HDD as the 1st boot choice. Save and reboot (usually F10 key).
Then when Linux has booted run 'sudo update-grub' (or the appropriate
command for your distro) to add Windows to the boot choice. Next reboot
should give you a short time to choose which OS you run.
Regards,
Paul
--
Dr. Paul S. Crawford
Satellite Station
Dundee University
Small's Wynd, Dundee,
DD1 4HN, U.K.
Tel: +44 (0)1382 38 4687
Email: address@hidden
The University of Dundee is a Scottish Registered Charity, No. SC015096
[Pan-users] what I need to do to "jump ship" (Re: To explain why I'm unwilling to update my g lib/gtk+/etc libs ATM…), SciFi, 2011/07/28