>>>>>I can corrected on the develop part. Mike says the dev environment will run on Win95, but it is not supported.
>>>>
>>>>Actually, it occured to me that we may have changed the setup since the last time I checked. If it installs, it should work. Beats me why anyone would be doing dev work on a six year old OS, though.
>>>
>>>Mike;
>>>
>>>I have worked at companies where you were required to develop on the OS used by your client. This gets interesting sometimes as you can imagine.
>>>
>>>I do believe in testing on the same OS as your client. If the client has a mix of say win95, 98 and NT, it is best to be sure it works on all before you "deliver the goods".
>>>
>>Tom,
>>
>>Your clients may be interested to note that after 12/31/2001 as I understand it, Win95 will no longer be a supported OS.
>
>George;
>
>There are about 4500 people in our building and the vast majority of computers have win 95 installed. Thus far there is no concern for dropping win 95 support. We all know it will continue to work on January 1, 2002, or will it? Maybe there is a time bomb - we will know shortly.

< g > Yes, we sure will

>One thing for sure it will work as well as win 95 was made to work. IMO moving to a newer OS is a good idea.

It makes a lot of sense and eliminates some problems. For example, is GetDiskFreeSpaceEx() available or not? Is the Active Desktop (with the Shell.Application object) installed or not? Is the WSH installed?

>The nice thing about "drop dead" hardware/software support dates is you can then be a part of that group that points fingers in several directions at once when a problem occurs. "It is not my problem because Microsoft dropped support of win 95 effective 12/31/2001!" Gee, I feel better already!!!
>
ROFL