> What are the problems around root > 3.02 bins on win98? I've been quite successful with making my libs > under win98 and running exe and scripts, although I have noted that > root crashes on some actions with canvas etc. Nick may have run into some additional problems I haven't seen, but frequent application crashes when doing Root graphics are not unique to Win98. They happen all the time on Win2K as well. My non-graphical applications work fine though (if I don't link to libNew). In response to Nick, the main flexibility I recall in Win98 is the wide variety of lovely blue screens you can look at before hitting the power switch... Win2K on the other hand never crashes (for me at least). I have two machines which have a combined running time of about a year on Win2K without a single OS crash. And this includes any number of times when I have really screwed up with some debugging session and tried to allocate or nuke the entire address space from C or C++, which would without a doubt have brought Win98 to its knees. Personally I would never go back; I wouldn't presume to tell you what's right for your situation, but you might want to reconsider whether to stick with the older OS if your machines have the specs to run the newer one. > PS. to "installshield" discussion. I checked out InstallShield coming > with MSVC... It has "change registry" part in the install script, so > what's the problem with setting paths under install? On the other hand > what prevents you from writing a few lines in the shield script which > will manually add two lines in autoexec.bat file? You have to restart > com then but who cares... It has been reported that the VStudio version of InstallShield has limitations on the size of the installation which are too small to accomodate Root. Also note (as Valeri recently pointed out) that Win9x and Win2K handle environment variables in different ways. Changing autoexec.bat on Win2K will not accomplish the desired result (in fact it doesn't even exist). Perhaps we should form a Win32 Root users group and try to mount a more organized attack on the various problems. There are probably others, but in order of importance I would say: 1) GUI 2) GUI 3) GUI 4) VStudio Projects and build procedures 5) Documentation (in particular, what is known not to work) 6) Memory management and libNew 7) Installation 8) Threads (this reflects the irrelevance of the topic to me personally; it may well be more important to others) Dave dcasper@uci.edu
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:34 MET