Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: QwikSand who wrote (28457)	3/2/2000 2:25:00 PM
From: cfimx	Respond to of 64865

qwik, i think that problem will be solved when a new generation of w2k software gets developed. And supposedly the server version doesn't need to be rebooted when an install is done. Hey it was worth the $2 billion they spent just to get rid of the BSOD. <g>

To: QwikSand who wrote (28457)	3/3/2000 4:26:00 PM
From: Prognosticator	Respond to of 64865

I think it goes way back to the time when once a DLL with its 8.3 filename got into Windows memory, subsequent applications would share the same code, AND DATA, inside the DLL. This was propagated forward into Win32, although I believe that applications now get their own unique data, but the code is shared. So a DLL is global, and hence can't be removed if it is locked by any application on the system. Many products conduct a stealth install of system critical DLL's, expecially MS Internet Explorer, hence the reboot. Solaris allows each application to load its own versions of shared libraries (DLL's), so you don't have this potentially global coupling, and no need to reboot when a new application comes in. Corrections from the more technically aware appreciated. P.

To: QwikSand who wrote (28457)	3/3/2000 7:37:00 PM
From: rudedog	Read Replies (2) \| Respond to of 64865

QS - the need to reboot when you install an app I think this was one of the features that got whacked in order to reduce application breakage - the changes needed to force every app to carry its own weight would have meant that Win2K launched with 800 apps instead of 8000 or something like that. Apps which do not require a change in core system setup don't need a reboot, and that is a larger class of apps than in the past... but still not every app. I have seen some info that suggests they now plan to start imposing restrictions on programming practice for Win2K apps which will move the apps to this model. It may be a part of the "Win2K certification" process - I'm not yet familiar with the details of that, but I know that of the 8000 apps which are called "compatible" only a few hundred are certified. It is certainly not a technology problem at this point, it is relatively simple to write an application, even one which needs deep system support, which can be installed without a re-boot. as a Unix lifer I don't understand the DLL structure of Win32 apps Well, I don't have to go back TOO far to remember when a lot of the key big Unix apps - in particular the database engines - required kernel mods and a re-boot to intstall. That was because features like multi-threading and asynchronous I/O were not commonly available - not in either HP-UX or SunOS, for instance. But then at my age, 5 years is like the blink of an eye...