quote:
32-bit mode with respect to IDE refers to transfers that occur over the PCI bus to the host system memory. PATA is limited to reading 16-bit chunks of data at a time from a drive. If you enable 32-bit mode, the controller will be set to temporarily store the data from one read until the data is available from the next read before mastering a transfer over PCI. So it can collapse two transactions on the IDE side of the controller to one transaction on the PCI side of the controller.

SATA doesn’t require a mode like this. It could be said that it’s always running in 32-bit mode, I guess — basically SATA transfers data in serialized packets across the interface to the drive and the controller will just buffer the data until it has enough to send across the PCI bus. There is no need to enable this specifically with a SATA controller.

source: http://hardforum.com/showthread.php?t=1287459

Quote:
Hey guys, according to everything that i can research about the whole 32-bit setting in some bios’s, its kinda a joke because the whole sata channel is a 16×2 stepping transfer, when you turn on the 32 bit transfer it in a way simulates 32 bit, and as someone said, once you get to you OS of choice it takes over.

As a little info to people who dont know, you can go under device manager in the control panel, and pull up the device SATA or depending on how old your machine is, IDE controller and check to make sure that your system is designating your drive to the correct UDMA, since this is what system xp uses to regulate disk access(hence, why it doesnt matter if you tag 32 bit or not). UDMA scales between 1-6(Im fairly sure theres no 0 :> ) and if you are running a sata drive with 3.0 it should be UDMA 6.

The only reason i gave the beginner course in device management is because i have seen a lot of new computers hear lately where xp picked PIO mode, dont know the official reason why, but it seems to happen on newer drives more than mid range drives, in my experience.

Also, even though i have heard from multiple sources it doesnt matter, I always bind my IDE and SATA controllers, mostly because xp associates them as one, and once less process to get to what it needs microscopically must make a difference.

source: http://www.tomshardware.co.uk/forum/149914-12-enable-transfer-bios-setting

Installed the WordPress blog/content management system.

I found it to be very easy to handle, and was setup in almost 10min including importing the blogs from an other provider (blogger.com).

Here are some links: http://www.wordpress.org , http://www.wp-wiki.org

Changes

WordPress modifications

2013-02-03: Theme iFeature

style.css

remote Tagline social icons

.container-full
display: none;

remove Header title

header#cc-header
margin-bottom: 3px;
header#cc-header h1.site-title
margin-bottom: 5px;
header#cc-header h1.site-title {
display: none;

Securing

http://www.askapache.com/security/stop-wordpress-exploits-spam.html

http://www.askapache.com/htaccess/htaccess.html

Plugins

Akismet

Allow PHP in Post and Pages

Autolink URI

Duplicator

Easy Sign Up

G-Lock WPNewsman Lite

GhSHI Syntax Highlighting Shortcode

Google Authenticator

Hello Dolly

include-file

Include HTML and PHP

Postie

Responsive Add Ons

SI Captcha Anti-Spam

Sidebar Login

SyntaxHighlighter Evolveld

SyntaxHighlighter TinyMCE Button

Tagspace

WordPress Importer

WP-Cirrus

WP-Cumulus

WP-GeSHi-Highlight

WP-Syntax

WP-Syntax Hacktify

Youtube Feeder

Deploy WDS XP/pre-Vista/7 images using WDS

source: http://social.technet.microsoft.com/forums/en-US/winserversetup/thread/592025de-8566-4660-8c57-ecb83bf4629a/

You can use the WDS capture utility to deploy XP or any other pre-Vista Windows images using WDS.

More information in the WDS whitepaper here: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1393400&SiteID=17

See chapter ‘working with images‘, ‘Deploying Earlier Versions of Windows‘.

1. Install XP to a reference computer
2. On the server, add a boot image and create a ‘capture image’
3. sysprep the reference computer. Reboot it to download the ‘capture image’ from the WDS server
4. Follow the instructions to upload the XP image from the reference computer to the server

One key challenge is that XP images are HAL-dependent, so you’ll need multiple images for deploying to computers with different HALs.

WDS in Windows Server 2003:

• WDS 2003 Step by Step Guide – http://go.microsoft.com/fwlink/?LinkId=66145
• Deploying and Managing the Windows Deployment Services Update on Windows Server 2003 – http://go.microsoft.com/fwlink/?LinkId=81031

WDS in Windows Server 2008

You can download this content at http://go.microsoft.com/fwlink/?LinkId=89381, or you can browse it using the following links:

• WDS 2008 Step by Step Guide – http://go.microsoft.com/fwlink/?LinkId=84628
• Deployment content – http://go.microsoft.com/fwlink/?LinkId=81873
• Technical Reference content – http://technet2.microsoft.com/windowsserver2008/en/library/80e4c10d-bb4b-4337-81dd-aa98fe6db7351033.mspx?mfr=true
  

Moving default image store in WDS

source: http://www.techtalkz.com/windows-deployment/197581-moving-default-image-store-wds.html

You can move the drive and files from a command prompt:

C:\>  wdsutil /uninitialize-server

Move the remoteinstall directory to another drive.

C:\> wdsutil /initialize-server /reminst:drive\remoteinstall

http://www.anandtech.com/show/2888/2

Now that we’ve dealt with what 4K sectors are, why Western Digital and other drive manufacturers are switching to them, and what the potential pitfalls of 512B emulation are, we can look at the specific cases where there are potential problems.