Caro Studente, mi permetto di farti conoscere la seguente iniziativa didattica: Mercoledi' 21 gennaio 2004, 10.30-14.30, Aula 12C 4 ore su Embedded Model Control (Controllo a modello annidato) promosse da - LADISPE e dai corsi di - Controlli Digitali (IV anno, Ing. Informatica, Prof. C. Greco) - Principi di Controlli Automatici (III anno, Ing. Informazione, Prof. E. Canuto) Giovani Ingegneri presentano cinque applicazioni sperimentali o in via di sperimentazione. Troverai il programma in http://didattica.polito.it/mail/allegati/EmbeddedModelControl.pdf Cordialmente Enrico CANUTO scuderi 18/02/2004 16:00 6, 8, 12 sonza 26/01/2004 11:00 2-4-6-8 06/02/2004 13:30 bazzanella 16/02/2004 11:00 24/01/2004 08.30 1-2-3-6-8-12-12A laface 21/2/2004 8.30 2-4-6-8-12-10A-12A Upgrade Version: Last year a friend of mine upgraded GirlFriend 1.0 to Wife 1.0 and found that it's a memory hog leaving very little system resources for other applications. He is only now noticing that Wife 1.0 also is spawning Child-Processes which are further consuming valuable resources. No mention of this particular phenomena was included in the product brochure or the documentation, though other users have informed him that this is to be expected due to the nature of the application. Not only that, Wife 1.0 installs itself such that it is always launched at system initialization where it can monitor all other system activity. He's finding that some applications such as PokerNight 10.3, BeerBash 2.5, and PubNight 7.0 are no longer able to run in the system at all, crashing the system when selected (even though they always worked fine before). At installation, Wife 1.0 provides no option as to the installation of undesired Plug-Ins such as MotherlnLaw 55.8 and BrotherlnLaw Beta release. Also, system performance seems to diminish with each passing day. Some features he'd like to see in the upcoming Wife 2.0. - A "Don't remind me again" button - Minimize button - An install shield feature that allows Wife 2.0 be installed with the option to uninstall at any time without the loss of cache and other system resources. - An option to run the network driver in promiscuous mode which would allow the systems hardware probe feature to be much more useful. I myself decided to avoid all of the headaches associated with Wife 1.0 by sticking with GirlFriend 2.0. Even here, however, I found many problems. Apparently you cannot install GirlFriend 2.0 on top of GirlFriend 1.0. You must uninstall GirlFriend 1.0 first. Other users say this is a long standing bug which I should have been aware of. Apparently the versions of GirlFriend have conflicts over shared use of the I/O port. You think they would have fixed such a stupid bug by now. To make matters worse, the uninstall program for GirlFriend 1.0 doesn't work very well leaving undesirable traces of the application in the system. Another thing that sucks -- all versions of GirlFriend continually pop up little annoying messages about the advantages of upgrading to Wife 1.0 * * * * * * BUG WARNING * * * * * * Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.1 will refuse to install, claiming insufficient resources.