>Conclusions - bet wary of tech support J If I had thought to use non >Microsoft registry fix and uninstaller before hand, I probably could >have avoid days of frustration and hours of work, yet on all the message >boards I read of people with the same .NET errors, this never came up.
Is there any sign that MS is going to give up on this stupid Registry thing? It is a colossal source of hard to solve problems. Neither Mac not Xnix use this kind of thing and they are both better off fof it. ************************************************************************ * ==> QUICK LIST-COMMAND REFERENCE - Put the following commands in <== * ==> the body of an email & send 'em to: [EMAIL PROTECTED] <== * Join the list: SUBSCRIBE COMPUTERGUYS-L Your Name * Too much mail? Try Daily Digests command: SET COMPUTERGUYS-L DIGEST * Tired of the List? Unsubscribe command: SIGNOFF COMPUTERGUYS-L * New address? From OLD address send: CHANGE COMPUTERGUYS-L YourNewAddress * Need more help? Send mail to: [EMAIL PROTECTED] ************************************************************************ * List archive at www.mail-archive.com/[email protected]/ * RSS at www.mail-archive.com/[email protected]/maillist.xml * Messages bearing the header "X-No-Archive: yes" will not be archived ************************************************************************
