Ted Miller

Proud husband, father, traveler.

[Ted Miller @ted_miller]

@davepl1968 I was right there too during that period (OS/2 1.x, 2.x, NT), though I don't recall us having interacted.

I agree it was a dream job at that time.

[Ted Miller @ted_miller]

@davepl1968 I can feel some WPARAMs, LPARAMs, and the resource compiler jumping off the screen.

[Ted Miller @ted_miller]

@TheBobPony @wowstartsnow I don't recall why we brought this into Windows NT, but I vaguely remember doing it.

[Ted Miller @ted_miller]

@virtuallyfun I wrote all the Windows NT setup code visible on that screen. It executed as a special device driver, which was loaded/used only for that phase of setup.

[Ted Miller @ted_miller]

@jvert @davepl1968 I can recall reading a spec circa 1991 where someone was proposing using that bit for something else* in what was then known as NT OS/2, because "there are no known users of that bit".

* Possibly relating to whether boot failed, but my memory fails as to specifics.

[Ted Miller @ted_miller]

@marklucovsky @ibuildthecloud @Windows Another tidbit: at one point the idea of re-writing cmd.exe as a clean-room Microsoft-originated implementation was being considered, due to licensing or contractual issues with IBM in the wake of the divorce. Eventually this got sorted out and the project wasn't needed.

[Ted Miller @ted_miller]

@marklucovsky @ibuildthecloud @Windows My recollection of this is that we ported cmd.exe directly from OS/2 so it could fulfill the same "be ultra-compatible with 16-bit Windows" requirement on the command line, analogously to the compatibility we were going for with for Win32 and the GUI.