Enabling Windows 2000 at startup using Slackware
 

Hi, I just installed Slackware, and I needed help for that, so I guess I'm a newbie.

Before I installed Linux Slackware, I already had Windows 2000 Pro installed(On my D:\ drive)

So when I installed Slackware I formated my C:\ drive contaning the MBR, and now I can only boot Linux.

How can I make LILO, Slackware, MBR or whatever is managing the OS system support Windows 2000 at startup?

Thanks in advance.

- Julian

All you need to do is add an entry to /etc/lilo.conf

Something like

other = /dev/hdb1
label = Windows2000
table = /dev/hdb

Then run /sbin/lilo to write it to the mbr

I'm assuming here that your D: drive is located on another harddisk, in case it isn't
replace /dev/hdb by /dev/hda and also change the 1 to the correct partition number.

I am all new to Linux, I don't even know how to edit a text file or alike, from dos.
:newbie:
Could you direct me to an article explaining this? :study:

Thanks for the quick reply anyway.

- Julían

I don't know of any posts that explain how to use editors, but a simple editor that you might start using is Pico.

At the command prompt, type "pico" and then the file name you want to edit (in this case, /etc/lilo.conf)

If you get stuck, you can always read the man files by typing "man pico".

Good luck!

Oh, I almost forgot...

You probably have to be logged in as root in order to edit anything in the /etc directory. You can do this by typing "su" and then the root's password when it asks you.

agiacalone, are you sure we are talking about the same slackware here?

I installed all the applications that came with Slackware, and yet I don't have Pico. Can I download a texteditor somewhere then?

I didn't use "su" to login. I just entered "login", and then said root... Do they both work?

- Julian

i dont think slackware has pico in a normal install
if you use kde you should have kedit or if nothing else xedit is fairly easy to use

I thought that Slackware came with the pico/pine packages. Oh well.

Logging in as root works too, but it's a bad habit to get in to. Try to use your normal login most of the time, and use "su" to superuser when you need to.

If you're using X-Windows, I believe that Slackware has X versions of emacs and vi, both good text editors.

Pico is installed by default as far as I know (it's my basic choice for non-X editing of textfiles). Other editors are for example vi and emacs, but those are probably not to recommend for a newbie. Pico should be there.

If you're in X it's even easier, as moojuece said...KDE probably gives you a couple of hundred editors to choose from. :)

Well, do you know how I can install an editor for text editing then? I mean can't I download it and run some script?

- Julian

You don't really need to download anything. If you have a standard install of Slackware, there are already lots of text editors on your system...you just have to pick one and try it out.

I just checked Slackware's webpage, and it does come with the Pine/Pico packages. Try just typing "pine" at a command prompt and see what happens. If it's not there, than you can install it off of your Slack CD's, via the "installpkg" command.

Oops.

That would be: type "pico" at the command prompt.

Me bad. :)

Well vi will most likely be there, although it is difficult to use. Pico is very easy. Pico is at least on the Slack cd.

zillions of editors out there. try nano. its like pico and its almost available with every major distro. jed is easy to use and can be configured to act like other editors. There's nedit, emacs, vi, vim, xedit, cooledit,.....

BTW, your question:

George666 is close. With that line, you'll need to map-drive as well. An easy new way is:

other=/dev/hdb1
label="windows"
boot-as=0x80 #that's the BIOS name for the first drive

You have to fool windows into thinking its first in line. I've answered this question quite a few times (since I had to figure it out for sure lately, due to my own dual-drive-dual-boot issues). If you hit the search button below this post, you'll come across it. I answered it recently.

vi will be on your system. All*nix's seem to have it. You'll have to do a "man vi" and read the manual on that one. There's no way of guessing yoru way into that one. The commands are a bit obscure, but its quite powerful (but like learning a new language). Good to learn, though. Its on everyone's unix