Hi,
I am running a flashed MP 2009 4,1/5,1 with the Xeon 3680. According to the system profile and Geekbench results everything goes right so far.
I also added 16GB 1333 MhZ Hynix RAM, replaced the GT120 with the HD5780 and the orignial DVD-drive with a Sony Optiarc. I then installed OSX 10.8 clean on a Samsung MZ-7PC 256 GB SSD, swapped the original 640GB HD to bay 2, in bay 3 is a 1TB WD and in bay 4 a 2TB WD harddisk. I then installed a bootcamp Win7.
Now I am wondering: I figured out, that the increased delay to the startup chime is due to the RAM and probably the 4 harddrives and may be due to the ATI. BUT, I have a long delay (20-30secs), after pressing the Option key on boot until I can select the boot drive. I found one report stating the same; but I did not find out, whether this is unchangeable or whether there is some issue.
Also, sometimes, I cannot boot into Win7 after selecting the boot camp drive.
I would appreciate help, what I could still do to improve the situation - maybe without installing everything again.
Is this a known issue with Samsung SSDs?
Thanks in advance,
Leif
I am running a flashed MP 2009 4,1/5,1 with the Xeon 3680. According to the system profile and Geekbench results everything goes right so far.
I also added 16GB 1333 MhZ Hynix RAM, replaced the GT120 with the HD5780 and the orignial DVD-drive with a Sony Optiarc. I then installed OSX 10.8 clean on a Samsung MZ-7PC 256 GB SSD, swapped the original 640GB HD to bay 2, in bay 3 is a 1TB WD and in bay 4 a 2TB WD harddisk. I then installed a bootcamp Win7.
Now I am wondering: I figured out, that the increased delay to the startup chime is due to the RAM and probably the 4 harddrives and may be due to the ATI. BUT, I have a long delay (20-30secs), after pressing the Option key on boot until I can select the boot drive. I found one report stating the same; but I did not find out, whether this is unchangeable or whether there is some issue.
Also, sometimes, I cannot boot into Win7 after selecting the boot camp drive.
I would appreciate help, what I could still do to improve the situation - maybe without installing everything again.
Is this a known issue with Samsung SSDs?
Thanks in advance,
Leif