Strong news out after the bell today. Big watch for Monday

This email started with some big .gif file of a load of writing about a music download service, then it had this at the bottom:

rude, but this is theory only....and it is Microsofts'. I admit Bill is one of the best marketing man, but he has no respect from me in the technical and theoritical sence. ( he is the man who was against And it is wrong in theory too. A good operating system will sparate its own Hi, For some time I've noticed the "Visual Basic Forms" when importing resources in MSVC6. Today, for no other reason then idle curiosity I Googled for a while with no results, so I imported a VB form into a new Win32 proj, from a previous VB project to see what I'd end up with. I know little about dialogs (amongst other things :) so much of what I saw was a little foreign to me. However, from the little I do know I was quite surprised to learn that I could use a VB frm in a win32 app at all. Of course, actually implementing that is another story. The test project was vanilla Win32. It appears, at a very quick inspection, that the form is a simply a dialog? Does anyone know of any doc's tut's, other stuff, that I could read about this? TIA, Vince Morgan This is why Windows conceptually f....d, and no matter what Microsoft does, untill they move to an architecture that separates completely the user installed stuff from the OS, windows will have stability problems. By the way, I dont care about fashion, but rather simplicity and reliability and usability. I can install 15 copies of my software and they will happily run on the same computer simultaneously, and I think it is quite a problem, if not impossible with a program relying on the registry. The reliability of the registry? I am working with windows for the last 5 years at least, windows networks, supporting building and maintaining. This is my business. The most re-installs I had because of the registry, and almost only because of the registry got screwed up. And no-one fiddled with things went funny... Since my programs don't install anything into the registry, they don't seem to cause these kind of problems, neither are prone to them. Further more, in five years I had no cases when my ini file would have became corrupted, but for that case, I ahve omplemented a self check, and it will recreate the ini file if it doesnt exist. So in the case of a corruption of'the ini file, I only have to tell the user how to get to the folder, and get him to delete it. Try the same exercise with a corrupted Registry.... By the way, the "16 bit" seem to be a well accepted technology since Linux uses it to, and it's reliability tops windows' a few fold... Anyway, as a conclusion, I think I stick to the INI file, and wish you good luck with the registry, Regards, Tom

What do you reckon? A few people's emails mushed into one? Goodness knows, and it all means nothing to me. A GCSE in IT I may have, but I still don't understand computers.