HELP ME WITH A BUG TEST OF EXPLORER.EXE IN WINDOWS:

(It's quickly done on YOUR part, & easy - takes less than a minute to test):

A.) HOW YOU CAN HELP ME TEST IF THIS IS A BUG IN WINDOWS THE OS, or, JUST UNIQUE TO MY PERSONAL MACHINE:

Create a file, anykind, a text file using notepad.exe should/will do fine... put hello in it (or whatever), & save it, first naming it TEST.TXT.

Then, rename it to this:

"http://www.thenewtech.com/forums/operating-systems/help-bug-rather-testing-one-4896/#post14901"

(That's the URL of THIS thread by the way IF you can't see the WHOLE thing, copy it from your webbrowser's address bar, or, what is between the quotes above (WITHOUT the quotes, mind you, lol))

And, once that .txt file you created is renamed to THAT url above?

Right click on it!

(& tell me what happens to your MyComputer (or, explorer.exe, whichever you use (same thing really, just diff. view of them))).

----

B.) OUTCOME (OF YOUR TEST) WILL TELL ME THIS:

IF you don't crash your instance of explorer.exe (or, MyComputer)? Then, it's unique to some shell extension for rightclicks on files/folders I have...

IF YOU DO crash your instance of explorer.exe (or, MyComputer)?? Then, it may appear that I have found a bug in Windows...

(Then, I'll just take the Assembly dump (from Delphi, my default debugger) & send it to MS with the conditions noted is all so its fixed in a service pack OR hotfix patch)...

----

C.)To "get around it", I opened a DOS prompt & issued a DEL command on htm*.* & that burnt it... Which WAS what I was trying to do, via rightclick on a file, popup menu, DELETE command via the Explorer.exe GUI... but, could not, due to crash!

(Today was a holiday in USA ("memorial day") no work, & thus, I have NO other system to test this out on)

APK

P.S.=> What I am trying to determine is, is if this is "unique" to some "right-click on file or folder" SHELL Extension program (I use a truckload of these things, & am attempting to see if it is one I use, or not!)... See - someone who uses little to NO SHELL EXTENSIONS, will most likely NOT see such a bug is why (IF it is due to some rightclick shell extension I use: & THAT is the why of why I need a tester to perform this with me also)...

Anyhow, thanks for the help, IF you have 30 seconds or so to spare & trying this... apk

Nobody is willing to try this, to help me out?



(It only takes around 30 seconds to a minute to try & test (& I have a way to get rid of the file too, IF you cannot delete it, very simple/easy too - IF you see the SAME "BUG" I do that is))

* Oh well... I'll figure it out on a work system if need be... today is a day where I have to report in (I work from home remotely 3 days a week).

APK

P.S.=> It's less than the 254 character NTFS/Fat32 filename character limit, so it isn't related to THAT...

It's also NOT named a "reserved name" (for device access) such as LPT1, PRN, CON, etc. either, so that's NOT it either...

( ... & it's halted on an Assembler RET instruction (& appears to be a function call variable value return) in the ASM dump debug I get from Delphi (my debugger, because I keep compilers online) - you'd see a DrWtsn32.exe one most likely instead)... apk

RESOLVED, today, finally... forget about this post, it's all good!

APK

This was the result of a "shell extension" I use (right-click Explorer.exe extender on right-clicks of Files &/or Folders) APK