• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

hell yea

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: Hyperblaze
Not to be a thread crapper, but wouldn't you believe that a REAL operating system shouldn't need a fresh install on a periodic basis to keep it going fast?

The OS doesn't need to be reloaded, the user's need more education/experience. See my above posts.

User's ability to destroy something > OS' ability to prevent it.

ANY OS.

edit: oh, Kaido, didn't see your reply (some 8 posts up... 🙁 ), anytime. I do this stuff quite a bit. 😀

If you want another, I'd also consider recommend running sysprep before you image as well. This will make the image work on any* hardware, not just the PC you built it on. However, it also means you need to install drivers at the time of setup as opposed to them all being there. The up-side to that is, if the image has old drivers (which happens after say a month or two) you are forced to load new ones. See the link I posted above for a description (though the link isn't aimed at imaging, you can read between the lines).
 
Originally posted by: Phoenix86
Originally posted by: Hyperblaze
Not to be a thread crapper, but wouldn't you believe that a REAL operating system shouldn't need a fresh install on a periodic basis to keep it going fast?

The OS doesn't need to be reloaded, the user's need more education/experience. See my above posts.

User's ability to destroy something > OS' ability to prevent it.

ANY OS.

edit: oh, Kaido, didn't see your reply (some 8 posts up... 🙁 ), anytime. I do this stuff quite a bit. 😀

If you want another, I'd also consider recommend running sysprep before you image as well. This will make the image work on any* hardware, not just the PC you built it on. However, it also means you need to install drivers at the time of setup as opposed to them all being there. The up-side to that is, if the image has old drivers (which happens after say a month or two) you are forced to load new ones. See the link I posted above for a description (though the link isn't aimed at imaging, you can read between the lines).

cool, thanks! most of my work right now is plain old Windows PCs. For people whose computers I work on, I just do a fully-loaded "perfect" version of Windows. For my own, I usually do a couple Ghosts sets. One is just the basic Windows install with the serial number activated, no drivers. The other is the full one with software and drivers. I usually use the same software for 3 - 4 months, so during that time I use the full Ghost set. Then, new drivers and software updates come out, so I just load the basic version, which is basically a Windows installation but a bit faster and less of a headache. Plus it's activated, so you can avoid having to call MS every month to reactivate it.
 
Back
Top