>>> ... Best suggestion is to have a second *sub-standard* computer to test on. This is great for testing installation process, apps, etc., with no fear of crapping-out your own computer. I used GHOST software to create an ititial image of my test computer and burned this onto a CD. Then, I can re-dump this image onto the test machine whenever I want to start it over with nothing but Win9x, and the basic software -- i.e., no ODBC drivers, no ODBC connections, no DCOM, no VFP runtime. That way I can find the holes after I install an app for the first time. Dumping the basic image back to the hard drive takes less than 30 minutes!
>>
>>Great ideal Mark. It seems we can't have enough machines anymore. I have a test server, a regular test machine, and now crappy test machine. Thanks.
>
>LOL :). How about crappy test server? :)
Well, since you've got me thinking this way :)), this is what I'm going to do. I'll have a super-fast, regular, and crappy machines (both in server and workstation versions of course.) This way, I'll cover most bases. Now, all I have to do is talk to my boss, HR, IT team, Interior decorating dept. (a must have dept. for any serious company) and I'm on my way.
It's "my" world. You're just living in it.