Creating a Folder Named "Print" Makes Networked Computer Crash
 

So this probably sounds a little strange, but I've been able to replicate it consistently 3 times. I'm wondering if anybody else is able to replicate it as well? I'm in doubt that there's something wrong with my computer configuration, because this is the only really odd occurance that I've had on my computers.

Below I'll give the specifics of my setup, but I think it might be possible that the bug can be replicated without the exact environment I have.

Both computers are Windows XP SP2, and are connected through a router to each other. My laptop is connected via WiFi, and the desktop is connected via an ethernet cable.

On the desktop, the hard drive where I'm trying to make the folder is mapped as D:, and it is just used for personal files (no programs, system files, or anything). On my laptop, it shows up as a network drive mapped as Y:.

So, all I have to do is, on my laptop, navigate to Y:, create a new folder, and name it "Print" (without the quotation marks, of course). Once I do that, the desktop computer restarts.

EDIT: I logged in as admin on the computer that crashed, and apparently making the folder named "Print" caused a BSOD.

Well, We've got 4 computers networked at my house, and creating a folder named Print, both on the dekstop and on drive D:\ didn't appear to do anything to any of the other computers.

This could be a fault in one of your TSR apps.

TSR apps? What does that stand for?

Terminate and Stay Resident; I don't really know why he used the term when I consider that those were something back during the DOS days...
Perhaps he is referring to any application running in the background which is not performing a function, per se. (Either that or any background application.)