Re: [osol-discuss] Duel boot b134 and Windows 7
> On 07/26/10 04:45 AM, Mike DeMarco wrote: > > I installed build 134 first on disk c4d0p1 then > installed Windows 7 which it put on c4d0p2 sector> and c4d0p3 Windows 7. Using the LiveCD for > b134 I went back in and changed the active partition > back to c4d0p1 so I am now able to boot back to b134. > I then modified the menu.lst adding: > > > > title Windows 7 64 bit > >rootnoverify (hd0,3) > >chainloader +1 > > > > Then running > > installgrub /boot/grub/stage1 /boot/grub/stage2 > /dev/rdsk/c4d0s0 > > > > Grub now comes up with the Windows 7 but when I > select it the screen repaints and that is it. > > > > Can someone tell what went wrong? > > > I ran into this same issue when I set up my grub > (triple boot now with > Fedora and rhel v6 beta2). The file you want to > modify is > /rpool/boot/grub/menu.lst then add your chainloader > entry to the bottom > of the file. > > I see you subsequently re-installed, so this should > work for future > reference. Though a menu.lst file comes up under > /boot/grub, you need to > edit the one in /rpool/boot/grub. > > Cia > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > I did modify the menu.lst out of the /rpool/boot/grub/menu.lst. /boot/grub/menu.lst only had a entry in it for default and timeout. Since the stage1 and stage2 files only live in /boot/grub/menu.lst that is where I did the installgrub from. Still a mystery. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Duel boot b134 and Windows 7
On 07/26/10 04:45 AM, Mike DeMarco wrote: I installed build 134 first on disk c4d0p1 then installed Windows 7 which it put on c4d0p2 and c4d0p3 Windows 7. Using the LiveCD for b134 I went back in and changed the active partition back to c4d0p1 so I am now able to boot back to b134. I then modified the menu.lst adding: title Windows 7 64 bit rootnoverify (hd0,3) chainloader +1 Then running installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c4d0s0 Grub now comes up with the Windows 7 but when I select it the screen repaints and that is it. Can someone tell what went wrong? I ran into this same issue when I set up my grub (triple boot now with Fedora and rhel v6 beta2). The file you want to modify is /rpool/boot/grub/menu.lst then add your chainloader entry to the bottom of the file. I see you subsequently re-installed, so this should work for future reference. Though a menu.lst file comes up under /boot/grub, you need to edit the one in /rpool/boot/grub. Cia ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Duel boot b134 and Windows 7
I wound up re-installing b134, afterwards The Windows partition came up in the grub menu. I still can not understand what was wrong with the definition that I put into the menu.lst as it was identical to the one that the re-install put in. Guess it will have to remain another mystery. My new procedure is to install Windows first Thanks for the help mike -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Duel boot b134 and Windows 7
I may just do that and re-install everything if I can't get grub configured. Thanks -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Duel boot b134 and Windows 7
> I have actually tried each of the partitions hd0,1-4 > with no luck. I don't know; I can still boot W7 from my OpenSolaris GRUB menu ( it points to (hd0,0), which is the first primary partition, so in your case should be (hd0,1) ). As I said, it works the other way round. I usually install Windows first; then when you install OpenSolaris, it will recognize your Windows installation and setup menu.lst accordingly. Chavdar -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Duel boot b134 and Windows 7
I have actually tried each of the partitions hd0,1-4 with no luck. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Duel boot b134 and Windows 7
I always do it the other way round. On my laptop I have Windows 7/64 (two partitions, as you said), NetBSD-current/AMD64 (third primary partition), and on an extended partition I have two logical partitions, one 15GB FAT32 common data to all of them, one OpenSolaris (which has been able to boot from extended partition for some time). Initially this was lead by OpenSolaris GRUB, but when I formatted the FAT32 partition this changed the partition number and grub failed, so I installed NetBSD boot manager, which then selects either of the three partitions (OpenSolaris still shows it's GRUB menu, though). In your case my guess is you should change the (hd0,3) to (hd0,2),as the boot partition for W7 is actually the small 100MB partition it created during the installation. Cheers, Chavdar Ivanov -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Duel boot b134 and Windows 7
I installed build 134 first on disk c4d0p1 then installed Windows 7 which it put on c4d0p2 and c4d0p3 Windows 7. Using the LiveCD for b134 I went back in and changed the active partition back to c4d0p1 so I am now able to boot back to b134. I then modified the menu.lst adding: title Windows 7 64 bit rootnoverify (hd0,3) chainloader +1 Then running installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c4d0s0 Grub now comes up with the Windows 7 but when I select it the screen repaints and that is it. Can someone tell what went wrong? TIA mike -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
