[Aijaz Akhtar]

Quote:
Use some deb distro, and get the deb packages
as mentioned above.

I use knoppix, and I have recommended it to ye tooo ....
so use it atleast now. Knoppix is very suitable for troubleshooting.

I am at dial up and it may be difficult to download .deb for various programs. Knoppix is also cool, but I have only Live CDs, not installable ones.

Quote:
Lol .. I edited the thread title to Woes instead of Woves .. Earlier I thought it was some typo of wives.. ...

Yes, my typo. I typed all the woes simultaneously, wil post some now, and this mistake was on the first only

That problem started after PCQLinux na .. ?.
Yes, but now yesterday I got the Win loader from my laptop recovery CD and repaired the Windows, and deleted the partitions of PCQ. Wil try some other distro.

Quote:
Plus .. you could try using OSLoader and see if the Linux partition boots with it.
No OS loader was available in my CD collection here at Nagpur, I might have left them at Hyderabad fropm where I have come here (and have not changed my profile as I am now trying to get a transfer back to Hyderabad.
Quote:
PS: After reading your woes i tried installing grass myself on my comp. Just issuing # apt-get install grass got grass60 application working on my machine.
After apt-get what? The whole package I have has a mail shell script, a tar ball, and many lib files (rpms). Do I mention the rpms name after apt-get? or the grass tar ball name?
Besides I could succeed too many a time in installing Grass. But the Grass is not properly installed. To check it, there are three steps, all after loading spearfish, the sample data. 1. Load this and when the d.m (Display Manager) starts, add vectors and rasters from the given data – soil, geology, road etc and ask it to display map. If the DM disappears and the console gives some error, Grass is not correctly installed. 2. Go for Display, nviz. If it must show the 3-d map all right if it is properly instaled. And 3. if a query succeeds. Will you please check this in your installations?

Quote:
You need to know the partition where /boot is mounted (for example /dev/hda1) for your distro. Once you are booted into a working linux system (using any live cd), mount this partition on a directory, say /mnt/system, and then chroot to it (chroot /mnt/system), after that follow the rescue instructions for GRUB in the Linux Tips & Tricks thread
I mentioned this. The Live CD suggested to chroot/sysimage/hdX. And I did issue this giving it hda1 in my case, but chroot did not work. It never gave any other instructions to be followed. I did not try mnt/system however.
Tips and Trickes thread I tried too for LILO. It said "Fatal error: rootfs …(some thing, I forgot). I did edit lilo.config too, but it continued saying that there is an error in Lilo.config. The same thing happens with Yoper as well as in another system (laptop) with Vector Linux. Leave aside /sbin/lilo, I did edit lilo.config, but it resulted in the same errors.
/sbin/lilo also does not result in any response. And no man pages have been installed nor available with the distros. I did not check this with PCQ/Mandrake where I installed 'everything'