Re: FreeBSD 5.2.1-RELEASE and Windows XP on one system

2004-08-27 Thread Marc van Woerkom
Go back to your old familiar drive configuration and do 
one of the following:

1 - Install the FreeBSD boot loader on *both* hard 
drives.  Also be sure
to set the FreeBSD slice (a/k/a "partition" in 
Windows-speak) bootable
during sysinstall. 
During installation I did set the FreeBSD slice with the / 
system bootable, I also set the Windows partition 
bootable.
I believe, I choose install the boot manager on both
disks. 
In other words I hoped I did exact that way.
But it won't work.


FYI: The '???' label will be for your 
Windows
partition, and it should work.
I hoped so. And old Windows versions (on a different box) 
booted. That is why I start to wonder if XP is different.


2 - Use the GAG boot loader.  It's simple as can be. 

http://gag.sourceforge.net/>.
Yes, I guess I should use that or GRUB.
Bye,
Marc
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 5.2.1-RELEASE and Windows XP on one system

2004-08-27 Thread Subhro
Are you sure it was ad2? If yes then you have fixed the drives on the
secondary controller. Even I made that mistake :-)

Regards
S.

On Fri, 27 Aug 2004 07:45:34 -0400, Jud <[EMAIL PROTECTED]> wrote:
> 
> On Fri, 27 Aug 2004 10:58:23 +0200, "Marc van Woerkom"
> 
> 
> <[EMAIL PROTECTED]> said:
> > >I use the FreeBSD boot manager which comes with the
> > >system.
> >
> > Is there a difference between the one that sysinstall
> > installs and the one in the tools directory of a
> > installation cdrom?
> >
> > Anyway, I put the 40GB drive as Master at the end of the
> > cable and the 2GB drive as Slave in the middle (everything
> > jumpered).
> > I also read the C/H/S values from the drive cases.
> >
> > Installation was ok (the 40GB shows up as ad2, the 2GB as
> > ad3). But the boot prompt showed
> >
> > F1: ??? (refers to XP I guess)
> > F2: FreeBSD
> >
> > F1 didn't do anything (except blanking some characters on
> > the screen).
> > F2 came up with a "no kernel  0:ad(0,a)/kernel" or so
> > message.
> >
> > And in the bloody bios I have to set the hd type to
> > 'none', using 'auto' nor 'user' with C/H/S lead to a hang.
> >
> > So I am close to buy a new mobo this evening.
> 
> Well, I wouldn't dissuade you from the joy of buying new hardware, but
> you can solve your problem more easily than that if you prefer.
> 
> Go back to your old familiar drive configuration and do one of the
> following:
> 
> 1 - Install the FreeBSD boot loader on *both* hard drives.  Also be sure
> to set the FreeBSD slice (a/k/a "partition" in Windows-speak) bootable
> during sysinstall.  FYI: The '???' label will be for your Windows
> partition, and it should work.
> 
> 2 - Use the GAG boot loader.  It's simple as can be.   http://gag.sourceforge.net/>.
> 
> Jud
> 


-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 5.2.1-RELEASE and Windows XP on one system

2004-08-27 Thread Jud

On Fri, 27 Aug 2004 10:58:23 +0200, "Marc van Woerkom"
<[EMAIL PROTECTED]> said:
> >I use the FreeBSD boot manager which comes with the 
> >system.
> 
> Is there a difference between the one that sysinstall
> installs and the one in the tools directory of a 
> installation cdrom?
> 
> Anyway, I put the 40GB drive as Master at the end of the 
> cable and the 2GB drive as Slave in the middle (everything 
> jumpered).
> I also read the C/H/S values from the drive cases.
> 
> Installation was ok (the 40GB shows up as ad2, the 2GB as 
> ad3). But the boot prompt showed
> 
> F1: ??? (refers to XP I guess)
> F2: FreeBSD
> 
> F1 didn't do anything (except blanking some characters on 
> the screen).
> F2 came up with a "no kernel  0:ad(0,a)/kernel" or so 
> message.
> 
> And in the bloody bios I have to set the hd type to 
> 'none', using 'auto' nor 'user' with C/H/S lead to a hang.
> 
> So I am close to buy a new mobo this evening.

Well, I wouldn't dissuade you from the joy of buying new hardware, but
you can solve your problem more easily than that if you prefer.

Go back to your old familiar drive configuration and do one of the
following:

1 - Install the FreeBSD boot loader on *both* hard drives.  Also be sure
to set the FreeBSD slice (a/k/a "partition" in Windows-speak) bootable
during sysinstall.  FYI: The '???' label will be for your Windows
partition, and it should work.

2 - Use the GAG boot loader.  It's simple as can be.  http://gag.sourceforge.net/>.

Jud
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 5.2.1-RELEASE and Windows XP on one system

2004-08-27 Thread Marc van Woerkom
I use the FreeBSD boot manager which comes with the 
system.
Is there a difference between the one that sysinstall
installs and the one in the tools directory of a 
installation cdrom?

Anyway, I put the 40GB drive as Master at the end of the 
cable and the 2GB drive as Slave in the middle (everything 
jumpered).
I also read the C/H/S values from the drive cases.

Installation was ok (the 40GB shows up as ad2, the 2GB as 
ad3). But the boot prompt showed

F1: ??? (refers to XP I guess)
F2: FreeBSD
F1 didn't do anything (except blanking some characters on 
the screen).
F2 came up with a "no kernel  0:ad(0,a)/kernel" or so 
message.

And in the bloody bios I have to set the hd type to 
'none', using 'auto' nor 'user' with C/H/S lead to a hang.

So I am close to buy a new mobo this evening.
Regards,
Marc
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 5.2.1-RELEASE and Windows XP on one system

2004-08-26 Thread FreeBsdBeni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday 26 August 2004 10:13, Marc van Woerkom wrote:
> Hello,
>
> I am trying to run both FreeBSD 5.2.1-RELEASE and Windows
> XP on one system and had no success yet.

I'm having FreeBSD 5.2.1-REL-p9, WinXP and Mandrake 10.0 on my 200 GB drive. 
My bootmanager is GAG (http://gag.sf.net) wich works wonderful with all 3 
systems.

Hope this helps,

Beni.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBLiloU1uWMKLNG5ARAgJgAJ0Y8Y2ZbFrGCaxkXSVv9XEEPv5riQCdG+zj
PQo+bKa6PMdpWn9uHle3Rwo=
=eDcj
-END PGP SIGNATURE-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 5.2.1-RELEASE and Windows XP on one system

2004-08-26 Thread Subhro
On Thu, 26 Aug 2004 14:08:42 +0200, Marc van Woerkom
<[EMAIL PROTECTED]> wrote:
> >Well FreeBSD 5.2.1-RELEASE-p9 is running on my box with
> >Windiws XP in
> >dual boot. So the installation definitely works.
> 

> Ok, that is already a good hint.
> What boot manager do you use for that dual boot system?
> 
> 

I use the FreeBSD boot manager which comes with the system.

> >First of all, have u
> >fixed the master
> >drive at the end of the cable and the slave drive in the
> >middle
> >connector?.
> 
> I need to check that. I did not know about such a
> preference, and assumed both connectors are equal.
> 

For Winshit (read Windows) or Linshit (read Linux), they are indeed
equal, but as I indicated, FreeBSD is *very* *very* fussy about
hardware. So you need to maintain that order.


> 
> >probability you have already guessed. Yes it may be the
> >BIOS. Its a
> >good move to search the manufacturer site for updated
> >BIOS and flash
> >it. However be careful.
> 
> Perhaps I better try to get a newer board.. but then I
> need newer ram, newer proc.. the usual upgrade madness. :)
> 
> > Thirdly, I would say put the 40G
> >drive as
> >master as olders drives have buggy controller firmware
> >and they *may*
> >create troubles in case of newer slaves.
> 
> OK, I'll try that.
> 
> >Fourtly, Jumper
> >the drives
> >explicitly to be master and slave. Do not rely on the CS.
> 
> I hope, I did that. But I check.
> 
> Thanks a lot for the hints!
> Marc
> 

Let us know if that worked out.

-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 5.2.1-RELEASE and Windows XP on one system

2004-08-26 Thread Marc van Woerkom
Well FreeBSD 5.2.1-RELEASE-p9 is running on my box with 
Windiws XP in
dual boot. So the installation definitely works.
Ok, that is already a good hint.
What boot manager do you use for that dual boot system?

First of all, have u 
fixed the master
drive at the end of the cable and the slave drive in the 
middle
connector?. 
I need to check that. I did not know about such a 
preference, and assumed both connectors are equal.


probability you have already guessed. Yes it may be the 
BIOS. Its a
good move to search the manufacturer site for updated 
BIOS and flash
it. However be careful.
Perhaps I better try to get a newer board.. but then I 
need newer ram, newer proc.. the usual upgrade madness. :)

Thirdly, I would say put the 40G 
drive as
master as olders drives have buggy controller firmware 
and they *may*
create troubles in case of newer slaves. 
OK, I'll try that.
Fourtly, Jumper 
the drives
explicitly to be master and slave. Do not rely on the CS.
I hope, I did that. But I check.
Thanks a lot for the hints!
Marc
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD 5.2.1-RELEASE and Windows XP on one system

2004-08-26 Thread Subhro
Well FreeBSD 5.2.1-RELEASE-p9 is running on my box with Windiws XP in
dual boot. So the installation definitely works. Now in your case
there may be a few posiblities. First of all, have u fixed the master
drive at the end of the cable and the slave drive in the middle
connector?. FreeBSD has been very fussy about hardware. The other
probability you have already guessed. Yes it may be the BIOS. Its a
good move to search the manufacturer site for updated BIOS and flash
it. However be careful. Thirdly, I would say put the 40G drive as
master as olders drives have buggy controller firmware and they *may*
create troubles in case of newer slaves. Fourtly, Jumper the drives
explicitly to be master and slave. Do not rely on the CS.

S. 

On Thu, 26 Aug 2004 10:13:55 +0200, Marc van Woerkom
<[EMAIL PROTECTED]> wrote:
> Hello,
> 
> I am trying to run both FreeBSD 5.2.1-RELEASE and Windows
> XP on one system and had no success yet.
> 
> The system is a rather old PIII-400 with one 4 GB IDE hard
> disk (recognized by the BIOS) as master and one 40 GB IDE
> hard (where I have to disable the BIOS recognition) as
> slave hard disk.
> 
> So far I managed to run Windows XP on that box, when I put
> a little start partition on the master drive and the XP
> installation on the slave drive.
> Windows XP was able to work with the 40 GB disk, while the
> BIOS hangs while autodetecting it.
> 
> Then I tried to install FreeBSD 5.2.1-RELEASE in another
> partition of the 40 GB disk.
> 
> Sysinstall complained about the geometry of the 40 GB
> disk, saying that the values it read were impossible and
> it would continue with something more appropriate.
> Except for that bit the installation went as usual.
> 
> However booting the system was not successful.
> The boot manager installed by sysinstall was neither able
> to boot Windows XP nor the FreeBSD installation.
> 
> Is it possible that the standard FreeBSD boot manager
> doesn't work with Windows XP?
> 
> Yesterday I tried to just install FreeBSD on that system,
> and maybe after that doing a new installation of Windows
> XP.
> But even this didn't work.
> 
> So I now think that FreeBSD has big trouble with my disks.
> Perhaps the on board controller of the PIII-400 board is
> too  old for 40 GB IDE drives?
> 
> It is a bit frustrating that I managed to get both Windows
> XP and some older SuSE linux running on that system and
> not old faithful FreeBSD. :(
> 
> I also bought the complete FreeBSD recently, it has really
> progressed from my old Walnut creek edition, but it
> doesn't cover systems running both FreeBSD and any Windows
> >= Windows 2000.
> 
> Any idea what is going on?
> Help would be very welcome!
> 
> Regards,
> Marc
> 
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 


-- 
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"