Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Cannonfodder

  1. Before you do anything, verify a few things (if you haven't yet)


    Look at the BIOS screen on boot up. Do you see the master/slave configuration you are expecting?


    If you boot off the Mandrake Install CD, do a customized partitioning option (where you make all the decisions), look at the configuration it shows you. Write it down (e.g. \ is HDA and is of file system X). Then reboot off the CD in rescue mode and view your /etc/lilo.conf file and /etc/fstab file and confirm that the info matches what you wrote down.


    If all of this is correct, re-install lilo. Matter of fact, you might want to skip to this step first and reinstall lilo first to see if it resolves your problem.


    If none of this works, you may want to try backing up your important files and re-installing Mandrake. Think of it as a time to re-evaluate your partitioning scheme, what software you installed, so on..

  2. 1. I've used Mandrake for a few years, never paid for a version. Sounds like free to me.


    2. You can take an open source projectd published under the GPL licence and use the source code to develop your own source (again under the GPL licence). That is collaboration and a very large number of projects have quickly expanded in such a fashion.


    3. Linux is still in a state of evolution. The "everyone does it there own way" is recognized as a problem and there are drives to move to a standard. Problem with M$ is the standard is their standard and only their standard. Take a look at the file systems offered by M$ (NTFS, FAT32 derivatives). Look at Linux... There's a list somewhere, a long list. M$'s OS works but in many cases has lead to stagnation. You can't distribute your own copy of windows with your own enhancements. You can't see the source code (unless its stolen).


    I personally think you are looking at a mountain with a magnifying glass. You spend more time with linux and learn the ropes and you will have a better understanding of it. It's a BIG field.


    Regarding Visual Studios, it is a very good piece of software. But you can't get around the fact that you are "trained" for VS. To program on Linux, you need to "train" for a different environment and you are not limited to just one of a few major players.


    Some places to look at..





    These are open source depositories where collaboration and storage of open source projects are managed. Available to all.


    BTW, you are not too happy with how responses are made to your problems. It's just communication. You have been working for 3 days on something and you have to describe where you are at so others can help you. But your descriptions are very general. If you give a summary of what you are doing, what you have tried (with copy/paste from your screen or screen snapshots), then you will get better quality responses.



  3. You may already have ImageMagick, go to the mandrake control panel (open a terminal and type MCC) and look for software and see if you can figure out whether you have image magick.


    also, open a terminal console and type


    rpm -qa image | more


    should list all software packages with image as part of the package.. (think I have this right)

  4. The hardware MMU...


    Short for memory management unit, the hardware component that manages virtual memory systems. Typically, the MMU is part of the CPU, though in some designs it is a separate chip. The MMU includes a small amount of memory that holds a table matching virtual addresses to physical addresses. This table is called the Translation Look-aside Buffer (TLB). All requests for data are sent to the MMU, which determines whether the data is in RAM or needs to be fetched from the mass storage device. If the data is not in memory, the MMU issues a page fault interrupt.


    one possibility is that they are currently emulating the memory management system and would rather allow the hardware to do it, kinda guessing.. would reduce the number of instructions they have to process to emulate the OS. It's the same with the math processor. They have to do all their math (floating point operations so on) with code rather than hardware.


    What speed CPU and memory are you guys working with (noting that its slow)?

  5. Basically, both of your win98 and win2k partitions are starting from the same location (the win98). The boot.ini file probably lists them both and if you check Win2k, it probably has links into the Win98 partition. If you were to clear your win98 partition, you would immediately realized you were snafu with your win2k as well.


    I used to do this though (run them both with linux lilo).. but I used a partition manager (system commander) that allowed me to hide win98

    while I was installing Win2k. Basically, whatever partition you picked the partition manager would make that the 1st available partition and each time you booted, it would do this for you (make it 1st). Lilo can do the same.


    Eventually, though I got rid of system command and win98 both. I couldn't figure any reason to keep win98 around.. win2k was more robust..

  6. Thank you for your replies but I think that, upon reflection, I owe you an apology for getting confused about what I was asking for. Let's try again.

      What I was really trying to ask about is the time period AFTER lilo selection when the screen just sits there with a blue band across it for no aparent reason before deciding to boot up.

      What is this waiting period for and is it possible to get rid of it ? It just seems to be a waste of time.


    60 milliseconds! Nice... but I prefer picoseconds (I'm a fast typer) :lol2:

  7. Basically, the format in fstab is


    <partition> <mount point> <file system type> <mount parameters>


    You may have just had your auto users in the wrong place. It was expecting the file system type.


    Open /etc/fstab and look at the current entry for hda3 that now works. See how the syntax is setup..

  8. Well, first of all, did you replace the MBR during the mandrake install? If so, you have to reinstall the windows MBR. If so, try hooking the linux drive back up and do a UNINSTALL of the lilo.


    lilo -U


    Should restore your previous MBR which is the windows MBR. THen swap them again and see if windows will startup.


    If you get there, then hook the linux drive up with the windows and run the Mandrake installer again. But this time do it over your mandrake partitions. Alternatively, you can skip installation and try to setup your /etc/fstab and /etc/lilo.conf files to point to the drives current address (HDA or HDB or HDC whatever).

  9. In a nutshell, you just have to be careful here. The MBR is a wee bit of startup code data that points to the partition that will run grub (or lilo, or windows). Since you have windows up and running, as you reported, you are trying to get grub to reinstall. I'm not very familiar with grub but basically, like lilo, its going to read the /etc/fstab file. It also (I'm assuming) has a config file. Both must match the current configuration you have. So, what you need to do is write down the current configuration partition by partition so you know what you are working with.




    HDA - first BIOS drive

    1 - is what? Windows

    2 - is what?

    3 - is what?

    4 - is what?

    5 and up are extended partitions.


    HDB - second BIOS drive - linux?

    1 - is what..


    so on


    Then you can go line by line through your fstab and grub config file and make sure the entries are correct.


    When ready, you need to run the grub program. Should check for errors and do not reboot until you are sure all errors have been resolved.


    Let us know how you make out.



  10. There can be other reasons for doing this. E.g. Windows is installed and you want to keep the family out of linux so timeout is very quick.


    Just make it a small value if you want..


    Remember to run lilo to process your changes to the file lilo.conf.

  11. Try this..


    1. boot linux

    2. uninstall lilo. Open a terminal window and type


    lilo -U


    3. Shutdown

    4. Unhook your linux drive.

    5. Startup and boot your Win2k or Winxp CD (may have to go to BIOS and set CD to come first)

    6. Very carefully, select the partition you want to install on. You can use Mandrake's DiskDrak utility to create this ahead of time if you like.

    7. Install into the partition.

    8. Make sure its up and running. Don't spend alot of effort afterwards customizing until you know this is going to work.

    9. Now shutdown and rehook your 1st hard drive.

    10. Boot off of the Mandrake CD1, hit F1, type rescue, and reinstall lilo.

    11. Reboot into linux.

    12. Now you need to edit your /ect/lilo.conf file to add your windows partition entry. I"m not at a linux box right now so you will have to google or search the board for some examples (or someone else can provide one?)

    13. Rerun the lilo program. Check for errors. Do not reboot until all errors are resolved.

    14. Reboot and see if windows can be selected and booted.


    Hopefully that will work :) There are other ways to go about it I'm sure..

  12. Some more ideas and explanations. BVC has beaten me to most of it though :headbang:


    1. URPMI works like this.. (someone correct me if I'm off)


    It is a terminal command that is used to make modifications to the URPMI database. This RPM (a type of installation protocal) database is used to keep track of what software packages you have installed on your computer. It keeps track of each package and its associated files and where they have been placed. It makes it very easy for someone to uninstall software as well as install it.


    In conjunction with published sources (which you can link too), you can also build a list of "possible" packages that you can install. This is where Easy URPMI comes in. It is a web site containing a list of sources. You can select a source, and then it will build a text command that you can type into the terminal. The command will add the source to the system and also build a database based on that source. Actually, its nice because you don't have to type the command, just copy it from the browser window and then paste it into the command terminal window (select with mouse and then switch to terminal window and hit middle button).


    2. Regarding images, check out Image Magick. Go to google and look for it or go to www.sourceforge.org or www.freshmeat.org (both open source project web sites).


    3. If you have any issues with command syntax, you can do the following..


    a. In a command terminal window, you can type part of the command and then hit the TAB button. The rest will fill in. If there is more than one possibility they will be listed.


    b. Type


    man <whatever command>


    This brings up the manual for that command. You can leave the manual by hitting escape or Q or (maybe Z).


    c. Google! Always a help.. just type


    linux <whatever command>


    They have all been around forever..


    d. Regarding display managers. If you want to continuously try different ones with out switching, you can just make more than one user account until you settle on one. One account can be KDE another Gnome so on... I personally prefer Gnome..


    e. Partitioning.. If you dual boot on the same hard drive, you want to avoid using Window's Disk Manager afterwards. Just use mandrake's diskdrak instead. Or risk losing everything.. If on separate hard drives, just use the disk manager for the OS you have installed. Reason is that Window's doesn't recognize some of the partition table formats that Linux will write..



    Hope that helps!


    :woot_jump: :woot_jump:

  13. Sorry ChrisM, I meant Pixiestix :drum:


    I don't recommend the Partition Magic or System Commander approach. Costs money and doesn't really do anything that you can' just do with Mandakes DiskDrak. Additionally, you are adding another element where something can go wrong with the partition table (if they don't all agree on the layout of the partition table, you can say good bye to it)


    Pixie, after download, did you actually run a checksum program on the ISO image? This checksum program is called md5sum and when they originally create the ISO file at Mandrake, they run the program against the CD and it produces a number. They publish the number to you and you can run the md5sum program against the ISO and make sure its EXACTLY identical to what they made.


    This is useful in case your download session screwed up and missed a few bytes :)


    Anytime someone has problems burning a CD, this is where we start asking questions. If you need the program for windows do a google for WINDOWS and MD5SUM. You also need to go to the Mandrake site and get the checksum file (same page you downloaded the ISO images from).

  • Create New...