Comments on: "Path too Deep" Error Message – We have the Answer http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/ A server for the people !!! Sat, 21 Nov 2009 16:10:29 +0000 http://wordpress.com/ hourly 1 By: Fix Windows Vista Errors http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-16437 Fix Windows Vista Errors Thu, 07 May 2009 15:09:06 +0000 http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-16437 This might be a stupid question but can anyone advice how to fix error code 39 on windows xp ? This might be a stupid question but can anyone advice how to fix error code 39 on windows xp ?

]]> By: James http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-14147 James Sun, 04 Jan 2009 12:02:38 +0000 http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-14147 I am running Windows 2003 and would like to find all files and folders that exceed the 255 character limit. In your notes you say to open the console and click on the network health icon. Where is this icon you speak of? I am running Windows 2003 and would like to find all files and folders that exceed the 255 character limit. In your notes you say to open the console and click on the network health icon. Where is this icon you speak of?

]]> By: Joffa http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-7840 Joffa Tue, 11 Mar 2008 09:42:24 +0000 http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-7840 Nope this is not right, files should copy to the server and MS's file system should get over it. Opened the console and have no errors displayed. I have a file that's around 50 deep (total path) and it's causing issues. Gets the same error. Can be reproduced on an intermittent basis, well every 10 or so copies to the server. The other one that I get is the "cannot access the share" any longer error. I can reproduce this one on about the same frequency. While I really like the concept that is Home Server it staggers me that MS can release a product with so many simple to reproduce errors. Oh and by the way having to go to a 3rd party product to fix one of the deficiencies of the file system is totally stuffed. Copies between my laptop (WiFi) and home PC (LAN) run fine but using WHS stuffs up on a regular basis. WHS should play nice with large files if not then MS should add it to their list of test cases. Joffa. Nope this is not right, files should copy to the server and MS’s file system should get over it. Opened the console and have no errors displayed. I have a file that’s around 50 deep (total path) and it’s causing issues. Gets the same error. Can be reproduced on an intermittent basis, well every 10 or so copies to the server. The other one that I get is the “cannot access the share” any longer error. I can reproduce this one on about the same frequency.

While I really like the concept that is Home Server it staggers me that MS can release a product with so many simple to reproduce errors. Oh and by the way having to go to a 3rd party product to fix one of the deficiencies of the file system is totally stuffed.

Copies between my laptop (WiFi) and home PC (LAN) run fine but using WHS stuffs up on a regular basis. WHS should play nice with large files if not then MS should add it to their list of test cases.

Joffa.

]]> By: Subse7en http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-7263 Subse7en Mon, 18 Feb 2008 15:45:29 +0000 http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-7263 Carren W - U cant show me what home server does and how easy it is to use at setup on a linux OS. Yes windows has security issues but linkux is not bullet proof either. also on another note u replied with : And is WHS really safe and secure? How about how an attacker could exploit WHS? See Microsoft Security Bulletin MS08-001, which states, “Vulnerabilities in TCP/IP Could Allow Remote Code Execution”… I will bet you have know idea how to exploit this stack? or even where to go to find out. also I am using my WHS as a media server and HD streams perfect so you have no idea what you are talking about. Also I use Media Portal with WMP11... thats right I installed WMP11 on server based OS. So before you think you are all high and mighty just remember that there is always some faster, smarter, and stronger. Subse7en Carren W – U cant show me what home server does and how easy it is to use at setup on a linux OS.

Yes windows has security issues but linkux is not bullet proof either.

also on another note u replied with :
And is WHS really safe and secure? How about how an attacker could exploit WHS? See Microsoft Security Bulletin MS08-001, which states, “Vulnerabilities in TCP/IP Could Allow Remote Code Execution”…

I will bet you have know idea how to exploit this stack? or even where to go to find out.

also I am using my WHS as a media server and HD streams perfect so you have no idea what you are talking about. Also I use Media Portal with WMP11… thats right I installed WMP11 on server based OS.

So before you think you are all high and mighty just remember that there is always some faster, smarter, and stronger.

Subse7en

]]> By: Jon’s Geek Stuff … & Stuff » WHS “Path too Deep” Error Message http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-6962 Jon’s Geek Stuff … & Stuff » WHS “Path too Deep” Error Message Thu, 31 Jan 2008 15:59:51 +0000 http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-6962 [...] WHS “Path too Deep” Error Message [...] [...] WHS “Path too Deep” Error Message [...]

]]> By: Carren W. http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-6954 Carren W. Wed, 30 Jan 2008 23:23:12 +0000 http://mswhs.com/2008/01/30/path-too-deep-error-message-we-have-the-answer/#comment-6954 What do you call WHS locking up? BSOD or WOW experience? This is a major fault of using NTFS, reported many years ago, and it still remains an issue unresolved, just as the WHS data corruption serious fatal flaw... See Microsoft KB article posted at: www.support.microsoft.com/kb/946676 :( And by all means don't copy DVD movies, as WHS doesn't play nice. Doesn't this sound just like Vista DRM? And this problem is not solved even when Power Pack 1 is installed! So just like Vistaware, everyone WAITS for WHS PP2, just like Vistaware SP2 just to get things working... Linux doesn't have these issues and it's FREE. :) www.osliving.com (see for yourself) With proprietary source code, only relatively few 'privileged' individuals can review the code for problems or actually work on fixing them. Being closed source has not prevented the daily exploitation of security holes that never get fixed in Microsoft products, while the Linux holes come a few times a year and get fixed. Why can't Microsoft fix it's own buggy software programs? Why should Third Party Software need to Rescue WHS? Buy cripple WHS, insist upon third party solutions and praise Microsoft? You got to be joking... And is WHS really safe and secure? How about how an attacker could exploit WHS? See Microsoft Security Bulletin MS08-001, which states, "Vulnerabilities in TCP/IP Could Allow Remote Code Execution"... So who wants to use WHS when it's flawed with data corruption, security vulnerabilities and requires third party solutions, that lack basic functions such as a print server, wireless connectivity, lack of high definition streaming content, which Vista enforces HDCP that WHS doesn't support... Prove me wrong... What do you call WHS locking up? BSOD or WOW experience?

This is a major fault of using NTFS, reported many years ago, and it still remains an issue unresolved, just as the WHS data corruption serious fatal flaw…

See Microsoft KB article posted at:
http://www.support.microsoft.com/kb/946676 :(

And by all means don’t copy DVD movies, as WHS doesn’t play nice. Doesn’t this sound just like Vista DRM?

And this problem is not solved even when Power Pack 1 is installed! So just like Vistaware, everyone WAITS for WHS PP2, just like Vistaware SP2 just to get things working…

Linux doesn’t have these issues and it’s FREE. :)
http://www.osliving.com (see for yourself)

With proprietary source code, only relatively few ‘privileged’ individuals can review the code for problems or actually work on fixing them. Being closed source has not prevented the daily exploitation of security holes that never get fixed in Microsoft products, while the Linux holes come a few times a year and get fixed.

Why can’t Microsoft fix it’s own buggy software programs?
Why should Third Party Software need to Rescue WHS?

Buy cripple WHS, insist upon third party solutions and praise Microsoft? You got to be joking…

And is WHS really safe and secure? How about how an attacker could exploit WHS? See Microsoft Security Bulletin MS08-001, which states, “Vulnerabilities in TCP/IP Could Allow Remote Code Execution”…

So who wants to use WHS when it’s flawed with data corruption, security vulnerabilities and requires third party solutions, that lack basic functions such as a print server, wireless connectivity, lack of high definition streaming content, which Vista enforces HDCP that WHS doesn’t support…

Prove me wrong…

]]>