Erik,
After reading all the UT messages I did a THOROUGH backup and Ghost for my NT4 workstation and installed NET Beta. Final result: No problems with the WS or with my server which ran happily through all my install problems.

First problem: Component Updates - SP 6a didn't install since I have 128 bit encryption, but it didn't give any error messages until 6 reboots and 2 hours later - AND a slew of error messages which I carefully copied down. THEN it told me I needed to install the correct SP6a and re-do the Component Updates. Worked beautifully the second time after I searched the MS site for the right files and downloaded a 35 MB file. The URL the Beta gave was out of date.

Second problem: Even though I had 700 MB clear on my boot disk it filled up my Temp file with stuff and then said I didn't have enough space to complete the install. Changing my Temp file to D drive solved that problem.

I've made a small form in VFP7 but also done some "real" work in VFP6 including a setup disk and compiling for a project that was installed today. No problems at all.

All in all I wasted about 3 or 4 hours repeating stuff that a 'well behaved' program should have told me about up front. But I ALSO learned a lot about moving programs from one HD to another, updating Registry keys, etc.

HTH
Barbara


>
>To John and anyone else that has installed the .NET beta (especially you, Mike).
>
>I would like to install at least the VFP Beta on a production machine. I find that if I put Beta software on a throwaway box, I don't get any _real_ testing time in. IOW, I play around with it, but never really get neck deep.
>
>I have been using the Miami release almost exclusively since September, and have had no problems whatsoever.
>
>What are my chances of installing this on a production machine and escaping total disaster?