>All
>
>Does 2.6 run on Windows 2000 without any more issues than there already are running it on Win95/Win98 <s>.
>

Yes, for both the DOS and Win16 versions, a good deal more care in setting up the memory environment is strongly recommended; I suggest that FPW run in a separate WOW/VDM if you can spare the memory; crashes tend to be less prone to taking out any other Win16 components, by lots. FPDOS 2.6 shoud be configured only to receive DPMI memory (no EMS/XMS) and I limit the total available RAM for the Win16 and FPDOS sessions to <16MB summing conventional memory and DPMI. FPW will likely need to have the speed patch applied, and I've had poor results doing that under Win2K; doing the patch under Win9x or WinNT and then upgrading to Win2K has been less troublesome. I wouldn't count on PLB or BIN files that try to get at the metal working. If you use Win16 API calls via FoxTools, it's likely that the Win16 DLLs won't be present if you don't put them in yourself, and you won't be allowed to write into the Windows and System directories yourself, so install processes based on copying things there will probably demand rethinking.

>I heard there was some issues where a 2000 upgrade had been performed but not on clean first time installs? However, I don't know it works for sure in any variation of 2000.
>
>I am getting a new laptop and whilst most work is in VFP, I still have to support a sizeable 2.6 system. I would like to get 2000 pre-installed but I know for sure they both run OK on Windows 95/98
>
>Any info would be much very appreciated.