Networking problem
-
I’ve come across an odd problem with file access in N++. I connected an old XP machine to my network - I had a heck of a time making it visible, needing to enable “SMB 1.0/CIFS File Sharing Support” for a newer machine. (I mention this because it probably has some bearing on the issue.) Anyway, I was copying files off the old machine, and happened to open one of the old files in N++ on my new machine. However, I found that whenever I switch to some other program with an XP file in the active N++ editor, when I come back to N++, it immediately spits out the two error messages below.
This must be some sort of XP or SMB1 problem, because I have no difficulty editing files from other machines - not that I do that very often; I tried it just to test. -
You really should have shared version information, or better the full Debug Info – as someone who’s been here years, you should know this is part of standard asking for help for esoteric issues. (I give this first, because after my first and second read of my post, I thought you were asking about running an ancient N++ on your ancient OS, and was going to chastise you for such… it wasn’t until I had started to draft a response and reread that I interpreted your question differently; I hope I’ve got it right, but since you were rather vague, I still may be misreading. Sharing Debug Info would have proven you were running N++ on the newer PC, and would have avoided confusion and misinterpretation.)
But, if I understand your text correctly, you are saying some modern(ish) Notepad++ on some modern(ish) OS is trying to access a SMB1 samba drive (that happens to be hosted on your XP machine).
Honestly, it doesn’t surprise me: MS stinks at networking, so given that SMB1 is pretty ancient and MS tries to avoid access them when at all possible, it is probably not sending Notepad++ up-to-date information.
IMO, your best bet is to use Explorer to copy from the SMB1 drive to a local drive on the machine before trying to access it with Notepad++, because I think it’s just too much of a leap for the OS to handle the connection between N++ and the barely-acknowledged SMB1 connection, otherwise.
-
Yeah, you’re right - I was just so frustrated with what at first seemed to be random error messages that I banged out the post without thinking. N++ is a big piece of my administrative arsenal, so when it seems to be failing me, I overreact. If you care anymore:
Notepad++ v8.7.1 (64-bit)
Build time : Oct 31 2024 - 00:48:56
Path : C:\Program Files\Misc. Shareware and Freeware\Notepad++\notepad++.exe
Command Line : “\\{REDACTED}”
Admin mode : OFF
Local Conf mode : OFF
Cloud Config : OFF
Periodic Backup : ON
OS Name : Windows 11 Home (64-bit)
OS Version : 23H2
OS Build : 22631.5768
Current ANSI codepage : 1252
Plugins :
ComparePlus (1.1)
DSpellCheck (1.5)
ExtSettings (1.3.1)
HexEditor (0.9.12)
HTMLTag (1.3.7)
JSMinNPP (1.2205)
mimeTools (3.1)
NppConverter (4.6)
NppEditorConfig (0.4)
NppExec (0.8.4)
NppExport (0.4)
PythonScript (2)
XMLTools (3.1.1.13)
_CustomizeToolbar (5.3)
One interesting, but equally pointless observation: if I switch N++ to showing a local file, I don’t get the errors, no matter how many XP files I have open in other tabs. -
Sounds like the bug I fixed for the v8.7.5, so try to update to any N++ v8.7.5+ (ideally to the latest, as of now v8.8.5)
