Fix treatment of long file paths in Windows

3e5d171 (from November 2011) introduced this code to fix treatment
of long file paths in Windows. Then, one week later, this commit
fixed long file paths directly in Node's `fs` library:
nodejs/node-v0.x-archive@1f16a7b

So, the code currently in fstream actually /breaks/ long file
paths in Windows.

This fixes it, but keeps an additional mysterious line introduced
by that original commit that I don't understand.

Fixes npm#30. Thanks to @sdarnell for identifying the problem.

lib/reader.js

@@ -97,15 +97,8 @@ function Reader (props, currentStat) {
 
   self._path = self.path = path.resolve(props.path)
   if (process.platform === 'win32') {
+    // XXX What is this code for?
     self.path = self._path = self.path.replace(/\?/g, '_')
-    if (self._path.length >= 260) {
-      // how DOES one create files on the moon?
-      // if the path has spaces in it, then UNC will fail.
-      self._swallowErrors = true
-      // if (self._path.indexOf(" ") === -1) {
-      self._path = '\\\\?\\' + self.path.replace(/\//g, '\\')
-      // }
-    }
   }
   self.basename = props.basename = path.basename(self.path)
   self.dirname = props.dirname = path.dirname(self.path)

lib/writer.js

@@ -72,11 +72,8 @@ function Writer (props, current) {
 
   self._path = self.path = path.resolve(props.path)
   if (process.platform === 'win32') {
+    // XXX What is this code for?
     self.path = self._path = self.path.replace(/\?/g, '_')
-    if (self._path.length >= 260) {
-      self._swallowErrors = true
-      self._path = '\\\\?\\' + self.path.replace(/\//g, '\\')
-    }
   }
   self.basename = path.basename(props.path)
   self.dirname = path.dirname(props.path)