@ChickenLadyLovesLife@lemmy.world
Post #1305528
2026-02-12 11:26 UTC
Back in the year 2000 I was writing intranet apps for a big corporation, using Visual Basic and classic ASP (lol) and IE6 (lolol) for the UI. A very handy if not indispensable tool for this sort of work is the ability to View Source on the generated pages, which popped up the HTML in Notepad. One day for me this simply stopped worked entirely -- hitting View Source did nothing and I couldn't fix the problem on my computer no matter what I did (other people's computers still worked fine). I even switched to a different computer, set up all my tools and programs as normal, and got the same problem with View Source not working at all. I went like this for six months, and it was a real challenge to debug problems.
Eventually I discovered the problem from a forum post: I had a shortcut to Notepad on my desktop. For no reason I can possibly imagine, this prevented View Source from doing anything at all. It didn't even have to be a shortcut to Notepad proper; any shortcut that happened to be named "Notepad" would cause the break even if it was a shortcut to some other program. Renaming my shortcut to "NotepadX" fixed the problem. I would LOVE to have some old MS engineer explain to me what the living fuck was going on here.
Replies (2)
-
@Liketearsinrain@lemmy.ml 2026-02-12 14:31
I have a pretty good guess. They were using ShellExecute or a similar API with only "notepad” as a name or "edit" as a verb. The search order would end up finding your shortcut first. This would be odd behavior (the path should be be the full path and start at system32) but I don't have IE6 and Windows 95 to find the exact API lol.
-
@limelight79@lemmy.world 2026-02-12 11:30
That has to be some kind of special exception in IE6 that they were doing for debugging, and they failed to remove it. Crazy.