CompuServe Messages

Yann, >> like the Apple commercial…. Remember, you are installing an OS, not an application<G>. If they ever do port MacOS to the Intel platform, I bet it will be harder to install than OS/2. It is a big peeve of mine that OS/2 requires you to change display modes from a GUI screen. So if you inadvertantly set the display mode to something your card or monitor can't really handle, then you are probably hosed because you can't run the GUI to change it back. I did this once, but fortunately I was able to see enough on the out-of-sync display to switch the driver back. Most people aren't this lucky. At least Windows lets you change display drivers from a text mode dos program, and even by editing system.ini. I think IBM has a complex about DOS. Why not make DOS the bootstrap loader for OS/2 (and why is MS trying to get rid of DOS for Windows 4.0)? It would be alot easier to deal with problems with OS/2 if the machine would go through a dos boot first and let you hit a key to abort the loading of OS/2. Then they could have dos utilities for modifying/repairing OS/2. The way they have it now, if OS/2 is hosed, you have to boot off two foppies, which seems to take about ten minutes, and then there's not a whole lot you can do. Also, if the OS/2 installation program were dos-based, then you could install OS/2 from any old CD that you were able to use under DOS. I hate running bare dos on a system, and I am now an OS/2 true believer, but I think DOS is a useful least common denominator and that OS/2 (and the Unix vendors for that matter) should look into taking advantage of this. It's too bad it looks like MS is giving this up for Win 4.0. Bailey