the load times would effect all software that you use often have a quick google on Intel Smart Response
New member, First build! What are your thoughts?
- Thread starter Rhyswh
- Start date
the load times would effect all software that you use often have a quick google on Intel Smart Response
There are new chipsets that will be released along side Ivybridge, the naming suggests that they will be a positioned below Z68 and hopefully cheaper there will also be higher Z** versions too..they use the same 1155.
Last edited:
My tips based on my build are:
If your PSU doesn't work... give it a bit of time and try again. Bizarrely mine wasn't working when first connected but after swapping around with another and replacing again it did!
Secondly, don't buy your Gigabyte motherboard from anyone except OCUK - my statistically significant sample of... erm... one has a 100% failure rate from another supplier.
All joking aside, it's pretty straightforward and after assembling, taking it all apart and reassembling a few times just to get the cable routing right, you'll feel like an expert!
If your PSU doesn't work... give it a bit of time and try again. Bizarrely mine wasn't working when first connected but after swapping around with another and replacing again it did!
Secondly, don't buy your Gigabyte motherboard from anyone except OCUK - my statistically significant sample of... erm... one has a 100% failure rate from another supplier.
All joking aside, it's pretty straightforward and after assembling, taking it all apart and reassembling a few times just to get the cable routing right, you'll feel like an expert!
My tips based on my build are:
If your PSU doesn't work... give it a bit of time and try again. Bizarrely mine wasn't working when first connected but after swapping around with another and replacing again it did!
Secondly, don't buy your Gigabyte motherboard from anyone except OCUK - my statistically significant sample of... erm... one has a 100% failure rate from another supplier.
All joking aside, it's pretty straightforward and after assembling, taking it all apart and reassembling a few times just to get the cable routing right, you'll feel like an expert!
Weird!!
Ok, the best deals usually are on OCUK anyway! And hopefully by the time I buy mobo I'll have the free delivery!
I'm not worried about the building part, I had to do a module in computer building for my degree, it's the bit after that I'm not sure about. I thought everything was plug-and-play, boot from CD drive, install windows onto SSD/HDD and off you go. But I so some ones post about fragmenting and defragmenting HDD and stuff! What exactly does that mean?
Defragmenting your HD is a necessary process with Windows (presume it's still the same with Win 7 because of NTFS?)
The slow bit of reading data off hard drives isn't getting the data, it's getting TO the data - i.e. the access/seek time to move the head to the right part of the disk.
If you imagine filling up your hard disk completely with data - not one byte free and then deleting 1/3 of the files randomly, chances are you'd be left with 1/3 of your space but all of the free space scattered all over the disk. In some cases (e.g. if you just deleted lots of tiny files) you'd have thousands of tiny gaps with no data but no big gaps left.
To get around this problem, when the hard disk starts getting a bit fuller, NTFS (the file system) begins to break up larger files into chunks so that it can squeeze it into the available space - otherwise you'd be limited not to the total free space on the disk, but the largest continuous free space block left.
The problem this causes is that if a file is split across 10 chunks, all on different bits of the disk, the time taken to read that file could well be 10x longer because it will have to seek to 10 different places (the slow bit) and read a tiny bit off each (the quick bit).
To get around this problem, there are defragmentation tools. These basically move chunks around (assuming you have enough free space) until most or all files are back in one piece. It then moves whole files around until all the free space is in one or two places, meaning fragmentation won't happen for a while.
The problem is this doesn't cure it forever - just for a while...
I tend to reinstall Windows every year or so... it's a pain but you get a nice clean install which definitely seems to speed things up. You can back up your profile to make it easier, too.
HTH.
The slow bit of reading data off hard drives isn't getting the data, it's getting TO the data - i.e. the access/seek time to move the head to the right part of the disk.
If you imagine filling up your hard disk completely with data - not one byte free and then deleting 1/3 of the files randomly, chances are you'd be left with 1/3 of your space but all of the free space scattered all over the disk. In some cases (e.g. if you just deleted lots of tiny files) you'd have thousands of tiny gaps with no data but no big gaps left.
To get around this problem, when the hard disk starts getting a bit fuller, NTFS (the file system) begins to break up larger files into chunks so that it can squeeze it into the available space - otherwise you'd be limited not to the total free space on the disk, but the largest continuous free space block left.
The problem this causes is that if a file is split across 10 chunks, all on different bits of the disk, the time taken to read that file could well be 10x longer because it will have to seek to 10 different places (the slow bit) and read a tiny bit off each (the quick bit).
To get around this problem, there are defragmentation tools. These basically move chunks around (assuming you have enough free space) until most or all files are back in one piece. It then moves whole files around until all the free space is in one or two places, meaning fragmentation won't happen for a while.
The problem is this doesn't cure it forever - just for a while...
I tend to reinstall Windows every year or so... it's a pain but you get a nice clean install which definitely seems to speed things up. You can back up your profile to make it easier, too.
HTH.
ivybridge will use the same socket, most z68 boards support ivybridge
I see. Cheers for clearing that up. So how often should you defrag a HDD?
Yeah I so that somewhere else too! Always good to know!
Damn! So they won't be cheaper!
Edit: Sorry, forgot to thank stulid for the videos, they will come in handy
Once a week must be sufficient.
I see. Cheers for clearing that up. So how often should you defrag a HDD?
Yeah I so that somewhere else too! Always good to know!
Damn! So they won't be cheaper!
Edit: Sorry, forgot to thank stulid for the videos, they will come in handy
Unless you have a SSD just let windows 7 manage the defrag for you
I thought it was going to be every month or so!
I will have an SSD. Why can't windows 7 manage it with a SSD?
Well the scheduler is automatically every Wednesday.
the more you write to a SSD the more you shorten its life span, defrag is a very write intensive task. SSD's are fast enough not to require defragmenting; im not even sure if the seek time changes when a SSD is fragged?
So... the disadvantages outweigh the advantages
Does it take a long time?
Can I not set it to just de-frag my HDD and not the SSD?
Not if you stay on top of it, I dont defrag my PC as I have a SSD, but my sisters with a 500Gb HDD takes I guess about 5-10mins, but there isnt that much on it.
Ok. Can you set it up to just defrag the HDD and not the SSD?
Click Start - Type "schedule"
this narrows you down to task scheduler, open it
Navigate to
Microsoft \ Windows \ Defrag \ Right click the task on the right, properties
Change to the Actions tab
Now defrag /? from the command line gives this:
So the defrag -c command that the scheduled task runs is for all volumes
Change this command to be defrag D:
(change D for whatever letter your 500GB is)
this narrows you down to task scheduler, open it
Navigate to
Microsoft \ Windows \ Defrag \ Right click the task on the right, properties
Change to the Actions tab
Now defrag /? from the command line gives this:
So the defrag -c command that the scheduled task runs is for all volumes
Change this command to be defrag D:
(change D for whatever letter your 500GB is)