After some more thinking and extensive tests, it seems that my problem is
gone for good. It was a very silly problem. Because I am a silly silly
man... :-(
The problem is that I am booting with Grub, The Great. And I have Windows
in a slice. And OpenBSD now lives in a slice where a second (back-up)
Windows installation used to live. And you can't have more than one visible
Windows partitions at the same time. Need I say more?
Well, actually, it was more like that:
- I had these three primary partitions: Windows, Windows then NetBSD.
- All that Grub needed to boot NetBSD (hd0,2) was chainloader +1. So I
didn't change that because it should be enough to boot OpenBSD too.
- But Grub had to hide the second Windows (hd0,1) to boot the first one
(hd0,0):
hide (hd0,1)
unhide (hd0,0)
rootnoverify (hd0,0)
makeactive
chainloader +1
- When I decided to try OpenBSD, I deleted (hd0,1) and (hd0,2) and made one
single slice for it. OpenBSD thus became (hd0,1). And the Windows boot on
(hd0,0) was set to *hide* (hd0,1). So that slice was simply hidden every
time I booted into Windows.
Duh!
The help I received here actually helped because I had this idea after
re-reading Stuart's words:
"Are you loading the OpenBSD boot directly from MBR, or is there some other
bootmanager in the way? Any chance some program might have decided that the
OpenBSD partition is bogus because it doesn't know the type, and decides to
change it?"
Thank you all for the time and attention given to my silly problem. Now, if
you'll excuse me, I have to kick myself...
--
Luciano ES
Santos, SP - Brasil
>
<-quote-> **************************************************
On 09/06/05 at 19:00, Tobias Weingartner wrote in 2K:
>Something is overwriting it. Where does your 'a' slice begin?
>What is the output of 'disklabel wd0'?
********* END OF ORIGINAL MESSAGE *********</-quote->
