Hi,
I recently upgraded my macbook hdd to 160GB from 80GB (it already has 2GB of RAM) and so I thought that I would make a large windows image of 25GB, up from the 8GB I used to have. I also put it in it's own 30GB partition on the hdd.
Now, this image takes a significantly longer to boot than the old 8GB image, to the point where it is almost not worth trying to open it up to do something quick in which is one of the major benfits of parallels. Has anyone else found this with large parallels images?
I guess the other thing that I might have done that was bad was that when I moved from the 80GB drive to the 160GB drive, all I did was create one 30GB partition and one 130GBish partition and then copy all the stuff that was on the 80GB directly to the 130GB partition via firewire. Everything seems to working okay though and osx detects the correct size of the drive.
Cheers
Jim
I recently upgraded my macbook hdd to 160GB from 80GB (it already has 2GB of RAM) and so I thought that I would make a large windows image of 25GB, up from the 8GB I used to have. I also put it in it's own 30GB partition on the hdd.
Now, this image takes a significantly longer to boot than the old 8GB image, to the point where it is almost not worth trying to open it up to do something quick in which is one of the major benfits of parallels. Has anyone else found this with large parallels images?
I guess the other thing that I might have done that was bad was that when I moved from the 80GB drive to the 160GB drive, all I did was create one 30GB partition and one 130GBish partition and then copy all the stuff that was on the 80GB directly to the 130GB partition via firewire. Everything seems to working okay though and osx detects the correct size of the drive.
Cheers
Jim