This is a companion discussion topic for the original blog entry at: http://www.codinghorror.com/blog/2005/06/phantom-dos-files-in-my-root.html
It’s the ghosts of operating systems past! Interestingly - I dont’ see these files on my XP or 2003 systems. What in the world is putting them there?
My guess is, older installers. I remember reading from the x86-64 migration stuff that Microsoft was shocked to find out how many companies are still using 16-bit installation programs (eg, ancient versions of InstallShield, etc). They found this out the hard way – x86-64 can’t run 16-bit apps.
Just a guess though. If anyone has a better idea, let me know!
It’s not an installer – it’s a backwards compatibility feature. Windows XP (and I think 2000) puts those zero-byte files there on purpose because some old DOS apps check for their presence to determine the DOS boot drive.
Scott: They are hidden system files, of course. Have you enabled display of those files in Explorer? They should be present on any clean Windows installation.
Oh yeah - duh.
The used to be one of the first things I’d do to Windows after an install - customize all the explorer settings so I can see what’s on the drive. I haven’t done that lately it looks like. Must be getting old…
I actually do have AUTOEXEC.BAT and CONFIG.SYS in my root directory. And this is also on an XP Pro system.
It does make me feel nostalgiac for the days of manually managing my XMS so those crappy dos games would run.