Arch Linux

elliott

Member

Registered: 2006-03-07

Posts: 296

Re: Getting back in Vista

Probably because you need to add logical partitions, you can only have 4 primary partitions.

Last edited by elliott (2007-11-04 23:32:29)

peets

Member

From: Montreal

Registered: 2007-01-11

Posts: 936

Website

Re: Getting back in Vista

Maybe something to do with primary and logical partitions? If I remember, you are allowed only four primary partitions, or 3 primary and a large (let's say infinite as an approximation) amount of logical partitions. I really don't know what the difference between them is though - linux and windows don't care wether it's primary or logical (I think?)

Edit: oops, hadn't read second page!

Last edited by peets (2007-11-05 00:21:32)

fumbles

Member

Registered: 2006-12-22

Posts: 246

Re: Getting back in Vista

I've got:

title Windows
rootnoverify (hd1,0)
makeactive
chainloader +1

Which does the job for my Vista (my XP doesn't work with Grub, but thats another story).

Grub might of overwritten the Vista boot loader.
Boot with Vista DVD and open the recovery cmd prompt and:

> bootrec /fixmbr
> bootrec /fixboot

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,154

Re: Getting back in Vista

It's likely you made all partitions primary partitions.

Drives can have max 4 primary partitions, although one of them can be of 'extended' type.
In an extended partition you can create logical partitiions, thus getting more than 4 partitions on a drive.

You have  2 options : 
- make one of the partitions (sda4 seems a good candidate) an extended partition that uses all remaining space and create logical partitions for home and swap and others.
This will work with all OS .

- make sda4 a primary partition using all remaining space and configure it with lvm2 (check the archwiki for details) .
This will only work for linux.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky