Technology, Support, and News Forum

[Ztrl Profile Website]

Some of you may recall that I discovered this in Vista. And, well...here it is again.

sysedit from the run dialog box...




Again I ask, WHY!?

[JabbaPapa Profile]

It is one of a very short list of DOS-derived files that are absolutely central to Windows.

[Ztrl Profile Website]

So you're saying without it Windows wouldn't work?

[JabbaPapa Profile]

So you're saying without it Windows wouldn't work?

Y I think that's the gist of it, I mean DOS > WinDOS > Windows ... These core files are so deeply embedded in the codebase, they would likely be quite nightmarish to expurgate. Well, I guess they could get rid of it -- but what for ?

autoexec.bat is btw also used to ensure compatibility with legacy applications.

Anyway, you can still use autoexec.bat to execute scripts at boot AFAIK -- although iirc the last time I've done this myself was during the Longhorn pre-beta period to speed up Longhorn 4074 on my rig, and Longhorn 4xxx was founded on the Windows Server 2003 codebase...

[Ztrl Profile Website]

My biggest complaint is how old it is. And all of the old vulnerabilities it had...

[JabbaPapa Profile]

My biggest complaint is how old it is. And all of the old vulnerabilities it had...

DOS is no longer a part of either Vista or W7, and any old command protocols that are included in any autoexec.bat will be interpreted by PowerShell instead -- just as the old boot.ini files are used during boot by the Vista/W7 BCD store instead of by the DOS/9x/Me/NT/XP boot environment.

Old code, new language

[Ztrl Profile Website]

At least they seem to be moving in the right direction.