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 : MSFT Internet Explorer vs. NSCP Navigator -- Ignore unavailable to you. Want to Upgrade?

To: miraje who wrote (16359)	1/19/1998 7:34:00 PM
From: nommedeguerre	Respond to of 24154

James, "Bill, I know a guy who set off an airbag during a stereo install. Blew him into the back seat. I'm not a techie but I would guess that integrating anything into an OS would be infinately more complicated." Was this one of the new Windows/CE AutoPak-equipped models? Sounds like what might happen if the cute little LaneChangeWizard "glitches" in heavy traffic. The real difficulty in integrating something into the OS is making sure you can pass it off on the Judge later on. Kind of like slamming your hand in the cell door on your way to the glove-fitting demo; you do not want the swelling to be too obvious so as to be seen from the jury box or the bench. Making MAJOR changes to 228 DLLs sounds like a lot of swelling just to gain better access to a network socket. Take it easy, Norm

To: miraje who wrote (16359)	1/19/1998 7:59:00 PM
From: Daniel Schuh	Read Replies (2) \| Respond to of 24154

Ok, I will make a polite request. Does anybody know what "integrating the browser with the OS" really means? I've posted plenty of times what I thought. The browser has a COM interface, and it can be called to display stuff from other programs. That is, it's "integrated with the OS" just like Word or Excel. I'd guess there's also a bunch of stuff in the various little utilities that constitute the GUI for the OS that generated the html. You can call it OS code if you want, I guess you can call everything in the bunch of the software that comes on the Windows disk OS code if you want, but it all runs at the application level, like Word and Excel, too. Of course, code is the wrong word these days too, now it's all "technology". System level stuff, the core OS kernel, the stuff that runs in system mode in the microprocessor and has access to memory mapping and the device registers, yup, you gotta be careful with that, that code screws up and your machine crashes or hangs. Which is why I tend to get annoyed with Windows 95, I figure that something that gets screwed up and can be fixed by reformat, reinstall must be something wrong with the OS. The way operating systems are supposed to work, anything running at app level can kill itself, but it shouldn't kill the machine. I'll even read something from www.microsoft.com, if it actually explains things and doesn't go off into purest marketese like the DNS/DNA stuff that's floating around these days. Integrated is just a word, and like most words in the Microsoft context it's a bit problematic pinning down what it means. Near as I can tell, integrated, bundled, tied are all pretty equivalent, but I'll accept correction. Cheers, Dan.

To: miraje who wrote (16359)	1/19/1998 9:17:00 PM
From: Bill Jackson	Respond to of 24154

James, That would get your immediate attention, as well as cost around $700. In a way people tell me integration gets easier in these loose code days. Years ago when you had only 8K of main memory you were forced into a lot more work to densify things and be bit efficient. Now with dirt cheap memory and the modular approach that part of the problem has been eased. I suspect that you would never have been able to make a modern complex OS work if you had to write the code the old way?, and you would need strange beings indeed to write it. Bill