Computing.Net > Forums > Linux > Linux Install

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Linux Install

Reply to Message Icon

Name: sandhya
Date: April 3, 2002 at 22:17:21 Pacific
Comment:

I am trying to install windows 98 into my existing Linux system.

I have created partition for linux (boot, swap and root) and windows FAT32 .

And then I have installed the Linux .

How do I install my windows 98 now ?
I tried to boot my system from A drive using Win Boot disk with no success as the system hung up.

Am I doing something incorrect .
Do I have to mount the win partition for installing Windows or do I need to change the lilo.conf.

Please help . I am trying to make a carrier out of linux ..


Sandhya



Sponsored Link
Ads by Google

Response Number 1
Name: Bill Heinz
Date: April 3, 2002 at 22:35:20 Pacific
Reply:

I just recently ran into the same issue trying to dual-boot a machine I made. If you aren't too far into changing your distribution of Linux, you may want to consider installing windows first after a complete reformat, then using FIPS from the dosutils file on your linux disk to make room for your linux. I'm planning this, and I'll use LILO for my boot manager. Incidentally, I'm using SuSE linux 6.3. Find out if there's a better way to do it, though, before trying my way. I'm pretty new to Linux.
"Using FIPS
Before using FIPS, you must read the FIPS.DOC text file which

accompanies the program. The use of the program is not entirely

obvious, and you may need the background information the documentation

provides. Also, while running FIPS you should carefully read all the

messages it displays. They will provide valuable information on the

steps you will need to take next. Most importantly, FIPS comes with no

warranty. Although it has been used safely many times, there is always

the chance it could damage the data on your hard drive. If you value

your data, back it up before you begin.

For safety, create a DOS or Windows boot disk to work from. To do

this, click Start -> Settings -> Control Panel. Double click

``Add/Remove Programs'' and select the tab called Startup Disk. Press

the button and follow the instructions.

Next, copy the working files for FIPS to the floppy. The files

FIPS.EXE, RESTORRB.exe and ERRORS.TXT are mandatory. You may also want

to copy the documentation files included with FIPS. When your data is

backed up, restart your computer and boot from the new floppy.

When you arrive at the A:> prompt, type FIPS and press enter. A

warning will appear about using FIPS in multitasking environments like

Windows. Since we booted from a floppy, we are safe, so press enter.

FIPS will analyze your existing partitions. It may pause for a long

time at ``Checking FAT'' and ``Searching for Free Space''; this is

perfectly normal, so just wait. The bigger your hard drive, the longer

it will take. When FIPS is done with its analysis, it will display the

results. You may get a warning of something being wrong with your FAT.

If you read the message carefully, you will find that this is normal

with large hard drives and will not prevent FIPS from working

properly.

FIPS will then demonstrate how it plans to split the existing

partition and you will have the opportunity to make changes. Do not

just press enter. By default, FIPS will take all of the available free

space for the new partition it creates, leaving your Windows partition

with no free space at all. Windows will not run if it has no free

drive space, so you must adjust the partitions. Use the up and down

arrow keys to make large changes (ten cylinders at a time) and the

left and right arrow keys for small adjustments (one cylinder at a

time). The size of the existing partition is shown on the left and the

size of your new empty partition is on the right. In the middle is the

cylinder number where the split will take place. I left about 1500MB

for my own Windows partition. Adjust yours according to your needs,

but I would recommend using at least 1024MB for Windows.

When you are satisfied, press enter. FIPS displays information on the

new partitions and asks permission to write it to disk. Your hard

drive has not been altered at this point. You may choose to write this

configuration to disk or re-edit the partition table. On my machine,

when I chose to re-edit I received an error message that said FIPS

couldn't find some files it needed. If this happens to you, just press

ctrl-alt-delete to reboot from the floppy and start over. This did not

cause me any trouble.

When you choose to write the new partitions, FIPS will offer to make a

backup of your existing boot sector--you should definitely do this.

The backup file it creates is only 1KB in size and will be invaluable

if anything goes wrong.

After FIPS completes its work, it will display another message stating

that you should run scandisk on your old partition. I found that

Windows will sometimes miscalculate the used and free space on your

drive after using FIPS, and Scandisk will correct this problem. If you

choose to restore your original partition scheme using the RESTORRB

utility, you should run Scandisk after this as well.

After FIPS was done, I received another error. This one said ``Memory

Allocation Error, Unable to Load COMMAND.COM''. If you see this, just

press ctrl-alt-delete to reboot and all is well. This should not

affect your hard drive.

Finally, you may want to run the Windows FDISK program from your

floppy. This is not necessary, since Linux has its own fdisk program

for manipulating partitions. You will find that your hard drive now

contains two ``Primary Partitions'' (or ``Primary DOS Partitions'').

The second one was created by FIPS out of the free space on your

drive. For Linux installation, delete this second partition, freeing

up the space for allocating Linux partitions. (Be careful not to

delete the first one, where Windows lives.)


Linux Install Tips for Large Drives
Once you've made room for Linux on your drive with FIPS, you should be

able to install Linux by following the steps in the installation guide

that accompanied your Linux distribution. Here are a few tips that

should help you with the areas where dual booting might make a

difference.


Planning your Partitions
Both the Red Hat and SuSE installation guides have excellent chapters

on how to divide up your hard drive for use by Linux. Personally, I

favor the ``Keep It Simple'' principle, especially for beginners. I

let Windows keep the first partition, create a second for the entire

Linux install, a third for Linux swap space and the fourth for my

/home directory (where data is kept). Having /home on a separate

partition will make things much easier, if you ever have to reinstall

Linux. The size of each partition will depend on your individual

situation, but this should suffice for most folks. However, if your

hard drive is larger than 8GB, there is something else to think

about--LILO.


Booting with LILO
The usual and recommended method to boot into Linux is using LILO (the

LInux LOader). LILO can install itself in your boot sector and allows

you to choose which operating system you would like at boot time. Due

to a technical limitation, LILO is unable to read data from the hard

drive past the 1024th cylinder--the 8GB mark for modern LBA (Logical

Block Addressing) hard drives.

Does this mean you can't use the rest of your drive? Not at all. What

it does mean is that your boot partitions must all live below the 8GB

mark, that is, below cylinder 1024. Thus, if you want Windows to use

the first 9GB of your fancy new 18GB drive, you won't be able to use

LILO to boot Linux. Because of this limitation, Red Hat's Disk Druid

tool for partitioning the hard drive will not allow you to create your

Linux boot partition past cylinder 1024. You can still create the

partitions using fdisk, but Red Hat setup will not install LILO if you

do.


Booting from Floppy
It is possible to avoid the entire problem of the 8GB barrier by

booting from a floppy disk. Although this may sound inefficient, it

actually works quite well. The kernel loads into memory from the

floppy disk and never accesses the floppy again, so loading the kernel

is slower; but after that, the system runs the same as if it had

booted from the hard drive. The Linux kernel has no difficulty

accessing the end of large hard drives, so it can still reach all the

files of your Linux installation.

The setup program for your distribution will almost certainly ask you

to create a boot floppy during installation. Even if you don't plan to

boot from floppy regularly, you should definitely make a boot disk. If

for some reason LILO fails to install or becomes corrupted, you will

have no other way to access the files on your Linux installation.


Booting with Loadlin
Loadlin is a program that runs under DOS (or Windows 95 in MSDOS

mode). It can load the Linux kernel into memory from the DOS

partition. Because it loads the Linux kernel from the hard drive,

there is still a possibility the 8GB barrier could cause problems, but

only if your Windows partition is larger than 8GB and is almost full.

That's not likely at the time of this writing, but who knows--the next

release of Windows might take up that much space by itself.

Frankly, I wouldn't recommend Loadlin to Linux novices because it can

be difficult to configure correctly. If you simply must use it, an

excellent Loadlin + Win95 Mini-HOWTO document available from the Linux

Documentation Project should get you up and running.


Conclusion
Giving Linux a try does not mean you have to buy a whole new computer

or even a new hard drive. With just a little extra effort, you can run

both Linux and Windows without losing any data or any productivity

while you learn Linux. I think you will find it is well worth the

effort. "

I found this at a website on dual booting. hope it helps. Sorry for not citing the source, the cache expired on my browser. --bh.


0

Response Number 2
Name: bart
Date: April 4, 2002 at 02:52:33 Pacific
Reply:

Have your linux bootdisk ready and install windows. If you do not have your linux bootdisk you can make one by typing the following in the command line:

mkbootdisk --device /dev/fd0 your.kernel.ver

The windows installation process will overwrite the MBR so you will not be able to boot into linux anymore. This is the purpose of your boot disk. Boot your computer using your linux boot disk and reinstall lilo by issuing the following command after you boot:

#/sbin/lilo

This will reinstall the boot loader into the MBR and you should be whistling your favorite bathroom song after you reboot. If you don't want to go through all this just install windows and after you do so reinstall linux. You don't have to use the fips program since you have already set aside a partition for linux, the swap partition and FAT32



0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Linux Forum Home


Sponsored links

Ads by Google


Results for: Linux Install

bought used comp,it has linux installed www.computing.net/answers/linux/bought-used-compit-has-linux-installed-/10816.html

Linux Installation www.computing.net/answers/linux/linux-installation/3862.html

Linux installed, but.... www.computing.net/answers/linux/linux-installed-but/3622.html