Thanks for the background. I confused shortcuts and PIFs because the only way I know to make a PIF under W95+ is to make a shortcut and manipulate its properties. There no longer seems to be a PIF editor a la Win3x...

>BTW, I have a suicidal user who wants to run an FPDOS app over W2K WTS; there's no equivalent of TameDOS available AFAIK for W2K WTS SP3, and while there are registry hacks to handle DOS apps idling at a READ, they are not dynamic. All this after making the commitment to a completely native AD environment, forcing the upgrade of their sole remaining NT 4.0 WTS to Win2K, where their Canadian distributor uis running a kludged-up SBT Series 6 under FPDOS 2.6, interfaced to CrippleShip...erm...ClipperShip, which lacks good tools for integration (even compared to the ODBC Hell of products like UPS WorldShip; the US distributor uses Ascent with ODBC file integration and both custom scripting and DCOM interfaces and are very happy campers.) Other than allocating the app to a specific terminal server and limiting the number of sessions to avoid bogging down everything (or forcing them into MetaFrame) I'd appreciate any ideas, even just the address of a good hit man in Vancouver...

I thought everyone knew there are no hit men in Vancouver... or even in Canada, for that matter < g >

An idea almost as evil (would probably qualify for BOFH status if you were to try it) would be to run multiple instances of W2K on top of VMWare. This would only really have value if VMWare is capable of allocating % of timeslices on a per-OS-instance basis (I don't know if it can), so you could force each of (say 5) instances to hog no more than 20% CPU. You could then limit TS sessions per OS instance (even to 1) and/or tweak away to your heart's content!

Of course, there would be some interesting challenges like multi-homing the NIC(s) and routing incoming TS sessions appropriately...