There is nothing nastier or more frustrating than designing a website on a Windows platform and uploading it only to realize that something isn't right. The links don't work. The code is in one line. These are all common mistakes made by web designers. There are a couple of things you should prepare for before you you get upset and disgusted. You need to look at your editor, FTP client, and link case sensitive conflicts. 

"What You See Is What You Get" (WYSIWYG) can apply all types of crazy things to your code. This occurs because the editors want to simulate the server on a platform level, where root has a different structure. Microsoft's FrontPage 2000 will place file tags in your code, if you use some of their buttons to edit your code. It is actually trying to help allocate files to your server, because it searches for the file when using its Publisher Page feature to upload them. HotMetal pro is another WYSIWYG that will applies things to your code because of it's publishing habits. You can avoid this type of problem by doing one of two things. You can use there publishing feature. If you persist on using the program, but don't want to use their publishing feature, you can hard code it, even in their dialog boxes (example 1.0). This will tell the editor exactly where to place the file, instead of root (reference from drive root).In order to fix the links that look like example 2, you'd have to do an entire search and replace, and on a big site, that's no problem, (yeah right).

Example 1

Notice in the dialog box that there is some instruction on where the file is in reference to the file open.

Example 2.0

file:///C:/Documents and Settings/administrator/My Documents/htmlstuff/frontpage.html

Second thing to lookout for is the code tampering by your FTP client. FTP clients are notorious for messy code tampering because of the file transfer protocol mode. If it's in binary mode all the lines in a text file will be one. It happens because Windows uses "carriage return, linefeed" characters whereas UNIX type machines just use a "carriage return". When you transfer using ASCII, the FTP program converts these, but when you transfer with binary, it doesn't. If you use CuteFTP you don't have to worry about it because it has an automatic feature that adjusts the modes for text files. Example 3.0 shows WS-FTP with radio buttons that let you select. In WS-FTP there's also a file filter that you can declare the type of files that you want to transfer as ASCII.

Example 3.0

Click on the image to get a better look.

last but not least you need to keep an eye on the file and directory name's case. It's usually easy to set up a standard in the planning stages of your web pages. I usually keep everything lower case, but what I notice is that sometimes when you transferring files to floppy disk or some other places the directories copy full caps. The only thing you can do about that is watch it. Remember when coding to follow the standard, or else you'll be in for a good search and replace.