During the instalation of slackawre, there is an option of where to install the lilo i choose MBR insted (floppy and root) but there is an error.

after installatio the lilo loader doesnt prompt on the beggining. What is the problem

then where it took you ???
just black screen or do you have dual boot system so it took you to windows ???
its it generating any error ?

regards

Ok the problem is I alloted 1GB for /. I red the help and it said that it should be 2GB + and now my slack is working but had a problem in wine.

where you read this..??? Could you please forward that to me ???

regards

you can read this on the HELP menu during the installation.

You don't need to allocate 2 or even 1GB to install Slackware. You can install it in any size partition as long as it's big enough to contain all the components you choose. I run it in a 256M partition and there are people who use it in less than that.

It would help other people, if there was a problem, to know exactly what error messages you got and what you did. As it is, it's very difficult to understand your situation and people might read this thread and misunderstand.

Yes, true, you don't need that much space.
However, I'm assuming the OP opted for a full install of 10.2 which is the most painless way to install slack in which case he would need a little under 3 GB for /

It depends on your definition of "painless." I hate having to remove stuff, so I prefer to install only what I want in the first place.

Even so, I wanted to make a few points: 1, it's important to give facts clearly so people can understand and help. And 2, I bet if the installer runs out of space, it's not going to give you a chance to install lilo. It will just crash. So I don't think it was a space problem, or if it was, that wasn't the only problem.

We have many newbies on this forum. I should know, I am one. We should try to very clear because posts with incorrect or unclear information cost people time. When you want to fix a problem, it's nice if you can understand a post and fix your problem from it, instead of finding a guy with a similar symptom who either never tells how he fixed it, or the post is so cloudy you can't tell it it's the same problem or not.

Gimme the output of
$ df /