Linux gets nocked out of the way

Linux gets nocked out of the way

[erik burggraaf]

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

Hi guys, I'm kind'a complacent with myself at the moment.  I've managed to install a hard drive without destroying cmos.  Smile.
Now, how do I get linux to run so I can format the windows drive?  I am sure I could do it with bootdisks, but I wonder if there's an easier way?
The puter will see either or on it's one, but together, it goes right to windows, even with that drive set to slave.
Thanks,
Erik

[-- Attachment #2: Type: text/html, Size: 916 bytes --]

Re: Linux gets nocked out of the way

[Lorenzo Prince]

Dud you try installing Lilo or Grub, whichever one is on the distro you
are running?  You need a boot loader to run Linux, although I don't know
how Windows is even booting on a drive that's set to slave.

Lorenzo

Oh, and this is another kernel in that great and venerable "BugFree(tm)"
series of kernels.  So be not afraid of bugs, but go out in the streets
and deliver this message of joy to the masses.
	-- Linus, in the announcement for 1.3.27

erik burggraaf staggered into view and mumbled:

> Hi guys, I'm kind'a complacent with myself at the moment.  I've managed to install a hard drive without destroying cmos.  Smile.
> Now, how do I get linux to run so I can format the windows drive?  I am sure I could do it with bootdisks, but I wonder if there's an easier way?
> The puter will see either or on it's one, but together, it goes right to windows, even with that drive set to slave.
> Thanks,
> Erik
>

Re: Linux gets nocked out of the way

[erik burggraaf]

Of course, I have lilo installed on the linux drive, but I assumed that with
the linux set master and the windows slave, lilo would pop up and ask what
to do with this new drive that isn't in it's config.
As to windows booting from slave, it should boot from anything set as a boot
device in bios.  I guess primary slave is listed as bootable.
----- Original Message -----
From: Lorenzo Prince <lorenzo@princenet.sytes.net>


> Dud you try installing Lilo or Grub, whichever one is on the distro you
> are running?  You need a boot loader to run Linux, although I don't know
> how Windows is even booting on a drive that's set to slave.

Re: Linux gets nocked out of the way

[jude dashiell]

Check msdos.sys on c:\ after you make it accessible with the atrib
command.  Also check autoexec.bat.  One or both have commands in them that
start windows up.  Boot-gui=1 in msdos.sys could be changed to Boot_gui=0
and any line like c:\windows\win in autoexec.bat can be commented out.
Actually you could probably comment out the Boot_gui line in msdos.sys too
now that I think of it.  That slows down windows.  If the CDROM is set to
boot first in your cmos, putting a linux disk into it and telling it to
boot with one of the speakup kernels and what and where your screen reader
is should be enough to get you started.  Good luck with your windows
cleaning!

Re: Linux gets nocked out of the way

[erik burggraaf]

Well, I don't want to clean it, I want to purdge it, smile.  Maybe it will
just have to be boot disk.
Thx,
Erik
----- Original Message -----
From: jude dashiell <dashielljt@gmpexpress.net>
To: <speakup@braille.uwo.ca>
Sent: Thursday, May 29, 2003 8:49 PM
Subject: Re: Linux gets nocked out of the way

Re: Linux gets nocked out of the way

[Lorenzo Prince]

Unfortunately not.  You will have to reinstall Lilo to get it to see all
the drives on your system.

Lorenzo

Go not unto the Usenet for advice, for you will be told both yea and nay (and
quite a few things that just have nothing at all to do with the question).
	-- seen in a .sig somewhere

erik burggraaf staggered into view and mumbled:

> Of course, I have lilo installed on the linux drive, but I assumed that with
> the linux set master and the windows slave, lilo would pop up and ask what
> to do with this new drive that isn't in it's config.
> As to windows booting from slave, it should boot from anything set as a boot
> device in bios.  I guess primary slave is listed as bootable.

Re: Linux gets nocked out of the way

[erik burggraaf]

Ah, but I never never want to boot from that windows drive.  Smile.  If once
I ever get back to linux, that windows configuration will be blown away, and
the drive it's on formatted for ext2, so I can use it as a data drive.
I don't need to re-install lilo in this case, right?  Just mount the drive
and fdisk it.
----- Original Message -----
From: Lorenzo Prince <lorenzo@princenet.sytes.net>


> Unfortunately not.  You will have to reinstall Lilo to get it to see all
> the drives on your system.

Re: Linux gets nocked out of the way

[Lorenzo Prince]

As far as I know, this is correct.  However, in that case I can't figure
out why your slave Windows drive is booting, unless it is set to boot
first in your bios.  You may need someone to look at the boot order in
your bios to be sure that the master boots and the slave doesn't.  These
drives may be referred to as either master and slave or disk 0 and disk 1
or something similar.  Otherwise, the only other thing to do before you
get the Windows drive formatted would be to use a boot floppy or CD.

Those who don't understand Linux are doomed to reinvent it, poorly.
	-- unidentified source

erik burggraaf staggered into view and mumbled:

> Ah, but I never never want to boot from that windows drive.  Smile.  If once
> I ever get back to linux, that windows configuration will be blown away, and
> the drive it's on formatted for ext2, so I can use it as a data drive.
> I don't need to re-install lilo in this case, right?  Just mount the drive
> and fdisk it.
> ----- Original Message -----
> From: Lorenzo Prince <lorenzo@princenet.sytes.net>
>
>
> > Unfortunately not.  You will have to reinstall Lilo to get it to see all
> > the drives on your system.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: Linux gets nocked out of the way

[jude dashiell]

Another idea, and this should be even easier.  Unprotect command.com on
the windows drive and then erase it.  Best way to do that is drop into dos
mode and use atrib on it.  Then reboot the computer, windows should be
sufficiently broken at that point Linux will come up unless windows
trashed your linux drive already.