I tried to install Slackware on another partition on my Toshiba laptop. XP
was on the other partition. Neither Windows or Slack would boot after that
so I ran the restore DVD and figured I'd start over. Somehow The boot loader
(GRUB) did not get erased when the restore DVD was supposedly wiping out all
the other data on the disk. Now I can't boot windows. Is there a prompt
for GRUB to load windows?? This is not a happy thing since no installable
Linux version recognizes my wireless set up and I relied on Windoze to
download and burn Linux ISOs. Anybody have a suggestion?

Rick Slackware does not use GRUB it uses Lilo....

you might want to boot your box with a slackware CD, and then hit lilo
-u to uninstall it from the master boot record ...

On 2005-06-01, Rick Morris <wmorris@neb.rr.com> wrote:

> I tried to install Slackware on another partition on my Toshiba laptop. XP
> was on the other partition. Neither Windows or Slack would boot after that
> so I ran the restore DVD and figured I'd start over. Somehow The boot loader
> (GRUB) did not get erased when the restore DVD was supposedly wiping out all
> the other data on the disk. Now I can't boot windows. Is there a prompt
> for GRUB to load windows?? This is not a happy thing since no installable
> Linux version recognizes my wireless set up and I relied on Windoze to
> download and burn Linux ISOs. Anybody have a suggestion?

Your restore disk might have left the boot sector alone because you
want to leave intact any disk managers that must be used to access a
hard disk. My experience with laptop restore CDs has been that they
wipe out everything. The standard Slackware installation installs the
lilo boot manager. How did you get grub?

You can solve the boot sector problem in several ways. If you can
run the Windows recovery console you can repair the boot sector with
it. If you can boot an MS-DOS startup floppy disk, running "fdisk /mbr"
might solve your problem. You can start Slackware using a bootable CD
or a bootable floppy and see what "lilo -u" (assuming you really have
lilo) or the grub restore master boot record procedure will do for you
(assuming you really have grub).

Hi

On Wed, 01 Jun 2005 00:01:41 +0000, Rick Morris wrote:

> I tried to install Slackware on another partition on my Toshiba laptop. XP
> was on the other partition. Neither Windows or Slack would boot after that
> so I ran the restore DVD and figured I'd start over. Somehow The boot loader
> (GRUB) did not get erased when the restore DVD was supposedly wiping out all
> the other data on the disk. Now I can't boot windows. Is there a prompt
> for GRUB to load windows?? This is not a happy thing since no installable
> Linux version recognizes my wireless set up and I relied on Windoze to
> download and burn Linux ISOs. Anybody have a suggestion?

You can try :

title Windows
root (hd0,0)
makeactive
chainloader +1

Hope this helps.

Pierre.

On Tue, 31 May 2005 20:44:52 -0500, William Hamblen <wrhamblen@comcast.net> wrote:

>You can solve the boot sector problem in several ways. If you can
>run the Windows recovery console you can repair the boot sector with
>it.
What I'd do first... When that fails, plan B:

I have an older Toshiba laptop, and would expect recovery CD/DVD to
recover --> you may need to write a block of zeroes to start of HDD
to convince your recovery DVD that you have a brand new HDD, it
overwrites the rest anyway, or rather, mine did --> Win98 on 40GB...

--Grant.

On 5/31/05 7:45 PM, in article
1117586745.420100.172010@g14g2000cwa.googlegroups. com, "Mr. Boy"
<mrboy77@gmail.com> wrote:

> Rick Slackware does not use GRUB it uses Lilo....
>
> you might want to boot your box with a slackware CD, and then hit lilo
> -u to uninstall it from the master boot record ...
>


It must be a leftover from another distro. I have tried a couple but the
problem started with the failed install of Slack.

Thanks!

Rick Morris <wmorris@neb.rr.com> wrote:
>On 5/31/05 7:45 PM, in article
>1117586745.420100.172010@g14g2000cwa.googlegroups .com, "Mr. Boy"
><mrboy77@gmail.com> wrote:
>
>> Rick Slackware does not use GRUB it uses Lilo....
>>
>> you might want to boot your box with a slackware CD, and then hit lilo
>> -u to uninstall it from the master boot record ...
>>
>
>It must be a leftover from another distro. I have tried a couple but the
>problem started with the failed install of Slack.

In your original article you stated,

"This is not a happy thing since no installable Linux version
recognizes my wireless set up and I relied on Windoze to
download and burn Linux ISOs. Anybody have a suggestion?"

If that is entirely true, the fix is to wipe Windows off your disk
and do a regular Slackware installation, which will cure your boot
time problems.

Then it is almost a certainty that we can also get your wireless
up and running. I'm not sure what the latest Slackware distribution
comes with, but latest versions of ndiswrapper and the wireless tools
are easily available on the net if Slack doesn't have the latest (and
it probably does).

You simply install them and use ndiswrapper to install the very same
ndis wireless driver you use for your existing Windows. Bingo, you
then have Linux with a wireless on you laptop, with no space wasted
for Windows.

What chip set is the wireless in your Toshiba? With any luck it is
a Broadcom, but others work well too.

--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@barrow.com

Floyd L. Davidson wrote:
....
> --
> Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
> Ukpeagvik (Barrow, Alaska) floyd@barrow.com

Dear Mr. Davidson,

We would like to contact you in connection with the almost ready
issue of The Slack World <http://slackworld.berlios.de/>. The main
point is that we would like to include a post of yours in the issue.

Does the e-mail address that appears in the headers of your posts
(fl....@barrow.com) work? If not, could you please let us know
a working one. The current editors of The SW can be reached as
user "ayaz" registered at host "fast-ce.org" (Ayaz Ahmed Khan) and
user "e-boogie" registered at host "yandex.ru" (me).


Regards,

Mikhail Zotov

On Tue, 31 May 2005 17:45:45 -0700, Mr. Boy wrote:

> Rick Slackware does not use GRUB it uses Lilo....
>
> you might want to boot your box with a slackware CD, and then hit lilo
> -u to uninstall it from the master boot record ...
>
It /* can */ use grub. Grub is in the extra packages set:
http://www.slackware.at/data/slackware-10.1/extra/grub/

Your definitive statement makes it sound like slackware depends
exclusively on lilo. The bootstrap can be controlled by a variety
of bootloaders, including grub.

On Wed, 01 Jun 2005 06:35:46 +0200, Pierre M wrote:

> Hi
>
> On Wed, 01 Jun 2005 00:01:41 +0000, Rick Morris wrote:
>
>> I tried to install Slackware on another partition on my Toshiba laptop. XP
>> was on the other partition. Neither Windows or Slack would boot after that
>> so I ran the restore DVD and figured I'd start over. Somehow The boot loader
>> (GRUB) did not get erased when the restore DVD was supposedly wiping out all
>> the other data on the disk. Now I can't boot windows. Is there a prompt
>> for GRUB to load windows?? This is not a happy thing since no installable
>> Linux version recognizes my wireless set up and I relied on Windoze to
>> download and burn Linux ISOs. Anybody have a suggestion?
>
> You can try :
>
> title Windows
> root (hd0,0)
> makeactive
> chainloader +1
>
> Hope this helps.
>
> Pierre.
>

I recently built a dual boot XP/Slackware computer. BTW, it wasn't for
me- I have no use for XP. To make space for Slackware, I had to resize
and repartition, etc. To make a long story short, XP would only boot if
it was physically installed on the first primary partition. Grub at the
MBR can successfully "chainload" to the OS, but caution with Windows is
always in order (read below).

I also had trouble with another computer with an older 40G drive on
another dual boot computer. This drive has grub installed at the MBR, and
loads the grub menu. It also loads Slackware with no problem, but hangs
when trying to load Windows 2000 using a similar grub menu sequence:

title Windows 2000
rootnoverify (hd0,0)
makeactive
chainloader +1

I decided it had to be some problem specific to that 40G drive. When the
BIOS "autodetects" the drive, it's default mode is CHS. I switched to
LBA, but that had no effect. It seemed like the Windows loader was
switching back to the default mode as specified by the drive. I finally
gave up and made a Windows boot floppy.

--
No, I have to do this my way. You tell me what you know, and I'll confirm.
I'll keep you in the right direction if I can, but that's all.
Just...follow the money.
http://us.imdb.com/title/tt0074119/quotes