The same guys that did VMS did NT, but that's the total extent of the similarity. Again, read Inside Windows NT for the scoop. Helen Custer was a member of the development team for Windows NT that was assigned the job of documenting the process that went on in building it.
OS/2 was developed with the master source code repositories running on Xenix for OS/2 1.0 and OS/2 1.1, but that's it. Actually to be technically accurate the master copies ran on MVS, since IBM considered their copies to be the masters and Microsoft's to be shadow copies, but....
Once the first IDW build of NT was done (sometime in 1989), NT ran 100% on NT.
So from 1988 to 1989 NT's source repository ran on OS/2, but it's been NT ever since.
Check out Helen Custer's Inside Windows NT or G Pascal Zachary's Showstopper! for more info.
The article completely fails to mention that WashTech is a union that's been trying to organize technical workers in Washington State for YEARS with absolutely no success.
Reading it carefully, the article appears to be a P.R. piece written by WashTech as a piece of propoganda to try to encourage people to join the union....
Yeah, it does. The other day WU sent me an update for the video driver on my machine, and the driver that was downloaded wasn't an MS driver, instead it came from Matrox.
In the early days of OS/2, IBM shipped a copy of Windows in in every OS/2 box (that's how they made it "better windows than windows"). But the license MS had with IBM required that they pay a royalty for every copy of Windows they shipped.
And IBM started claiming millions of copies of OS/2 sold but they only reported to MS that they had sold a couple of thousand copies.
Some bright lawyer at MS noticed the discrepency and asked IBM what was up...
And IBM magically reduced their number of units of OS/2 sold.
XP's anti piracy wasn't cracked. There were a half a dozen volume activation keys that were leaked, those got shut down with XP SP1. And someone reverse engineered the code in setup that validates the CD key - which is NOT the same thing as cracking the anti piracy. All that does is allow someone who already has a stolen CD to come up with a CD key of their own, after about 4 hours of crunching on their computer. Once they activate the computer with that key, the key is worthless to anyone else, since it won't work on another computer.
The ONLY keys that have any worth to pirates are the volume activation keys (since the work on multiple computers), and (as I said above) those keys haven't been cracked. Until someone cracks the algorithm to generate the volume activation keys, it hasn't been really cracked.
And M$ has NEVER EVER EVER said that the anti piracy stuff in XP was uncrackable. They've just said that it was harder than was worth the effort for most people.
But it wasn't done by the O/S, it was done by the linker that was shipped with the O/S. You could group modules together and the linker would link in a swapper that would swap them in and out into memory on demand.
Umm.. Word for Windows was known as "Opus" internally, and development started on it in 1982. It was NOT purchased. DOS Word was also done 100% in house, first for the Apple II then ported to the PC.
Simyoni was hired by MS to do most of the internal architecture of both products.
Nobody remembers, but hjkl were the arrow keys on an ADM-3A terminal. So VI was written using the arrow keys for one of the glass tty's available at the time.
First off. There WERE 5 releases of OS/2, none if which was successful:
OS/2 1.0: Console only version.
OS/2 1.1: Added a GUI called Presentation Manager
OS/2 1.2: Added installable filesystem support
OS/2 1.3: IBM redesigned the scheduler and the memory manager and released it as their own version
OS/2 1.3 (MS Version): Added support for SCSI drives
OS/2 2.0: Shipped after the MS/IBM divorce, 32 bit version of OS/2, also known as Warp.
Windows NT was originally called NT OS/2, and was intended to be OS/2 4.0. It was a complete bottom up rewrite of the operating system, the ONLY thing that came from OS/2 was the command interpreter. Win32 wasn't intended to be compatible with OS/2, it was intended to ease porting apps from Win16 to Win32. Since the OS went from a 16 bit OS to a 32 bit OS, there was never any intention of running 16 bit apps natively, they ran under a 16 bit emulation layer (called WoW, for Windows on Windows).
Win9x was always supposed to be released, but Win9x was based on the DOS codebase, which was designed from 1982-1987. Security was an irrelevance in those days. That's why it has crappy security - absolutely nobody cared about security back then, except on big-iron machines, and Windows wasn't a big iron type of product. Heck, the internet barely existed back then, and the web certainly didn't.
LanMan was ALWAY a Microsoft product, it was NEVER an IBM product (IBM licensed it and sold it, but it wasn't an IBM product - they did NONE of the development on it). NTLM describes the enhancements to the Lan Manager product for Windows NT, it wasn't "renamed".
The version numbers of Windows are irrelevant. Windows NT 1.0 shipped as version 3.1 to relate it to Windows 3.1. The version numbers mean NOTHING. If you want to get technical, they are:
Windows 1.0, 2.0, 3.0, 3.1, 3.11, WfW, NT 3.1, NT 3.5, NT 3.51, NT4, Win2K, WinXP.
The IBM DOS 4 or the Microsoft DOS 4?
There were two, you know. One was a 100% IBM product (PCDOS 4.0), one was a MS product (MS-DOS 4.0 and 4.1). The MS product was only ever sold by two OEMs.
It was co-developed with IBM from the MS-NET project back in 1984.
The actual protocol specification I have on my bookshelf is labeled "Microsoft Networks/OpenNET FILE SHARING PROTOCOL" INTEL Part Number 138446 Version 1.9 dated April 21, 1987, authored by Microsoft Corporation and Intel Corporation.
Actually that's not quite right - they have to open up the APIs that are used by their Middleware products. Which means IE, Media Player and I don't know what else (the list of middleware products is called out in the judgement).
If I lease my delivery trucks from Ford, then go out of business, I can't then turn around and sell the trucks as an asset of the firm. Instead, the trucks go back to Ford, which is the real owner of the truck.
This is the exact same situation - MS owns the software, KMart leases it, and MS wants to make sure that it gets paid by the new owners of blue light.
MAPI is a well specified set of API interfaces that Outlook uses to communicate to the Microsoft Exchange server. The MAPI provider that Outlook ships with use a propriatary protocol to communicate with the Exchange server. There's absolutely nothing stopping SUSE from producing their own MAPI provider and dropping that under Outlook.
Lotus does this for Notes, for example - Outlook runs against a Notes server without modifications because of the MAPI provider that Notes ships.
Judges aren't allowed to follow the normal rules that apply to other U.S. citizens.
They don't have free speech rights. They don't have a 5th amendment right to avoid testifying when that testimony would tend to incriminiate themselves (my grandfather went to jail for 6 months on that one, so I know what I'm talking about).
They have a REQUIREMENT that they judge the case in front of them impartially and make their decision based solely on the facts introduced into evidence and the law. They are NOT allowed to introduce their own personal feelings into the case, otherwise they make a mockery of the judicial process.
Jackson got slapped down because he violated that appearence of impartiality - he made it quite clear to the reporters that he had judged Microsoft guilty BEFORE the trial started.
And that's NOT ok.
It's either right in front of you when you click the "START" button, or it's at the top of the "PROGRAM'S" menu item, right next to the Windows Update entry.
Slashdot Mirror
The same guys that did VMS did NT, but that's the total extent of the similarity. Again, read Inside Windows NT for the scoop. Helen Custer was a member of the development team for Windows NT that was assigned the job of documenting the process that went on in building it.
That's flat out 100% wrong.
OS/2 was developed with the master source code repositories running on Xenix for OS/2 1.0 and OS/2 1.1, but that's it. Actually to be technically accurate the master copies ran on MVS, since IBM considered their copies to be the masters and Microsoft's to be shadow copies, but....
Once the first IDW build of NT was done (sometime in 1989), NT ran 100% on NT.
So from 1988 to 1989 NT's source repository ran on OS/2, but it's been NT ever since.
Check out Helen Custer's Inside Windows NT or G Pascal Zachary's Showstopper! for more info.
The article completely fails to mention that WashTech is a union that's been trying to organize technical workers in Washington State for YEARS with absolutely no success. Reading it carefully, the article appears to be a P.R. piece written by WashTech as a piece of propoganda to try to encourage people to join the union....
If I can't buy OSX without a browser, then it ain't a separate program. Same as Windows.
Yeah, it does. The other day WU sent me an update for the video driver on my machine, and the driver that was downloaded wasn't an MS driver, instead it came from Matrox.
Not quite right....
In the early days of OS/2, IBM shipped a copy of Windows in in every OS/2 box (that's how they made it "better windows than windows"). But the license MS had with IBM required that they pay a royalty for every copy of Windows they shipped.
And IBM started claiming millions of copies of OS/2 sold but they only reported to MS that they had sold a couple of thousand copies.
Some bright lawyer at MS noticed the discrepency and asked IBM what was up...
And IBM magically reduced their number of units of OS/2 sold.
Ummm...
XP's anti piracy wasn't cracked. There were a half a dozen volume activation keys that were leaked, those got shut down with XP SP1. And someone reverse engineered the code in setup that validates the CD key - which is NOT the same thing as cracking the anti piracy. All that does is allow someone who already has a stolen CD to come up with a CD key of their own, after about 4 hours of crunching on their computer. Once they activate the computer with that key, the key is worthless to anyone else, since it won't work on another computer.
The ONLY keys that have any worth to pirates are the volume activation keys (since the work on multiple computers), and (as I said above) those keys haven't been cracked. Until someone cracks the algorithm to generate the volume activation keys, it hasn't been really cracked.
And M$ has NEVER EVER EVER said that the anti piracy stuff in XP was uncrackable. They've just said that it was harder than was worth the effort for most people.
AFAIK, MS shipped a compliant JVM with extensions. Then Sun changed the compliance rules to make the MS JVM non compliant.
Sun then sued MS insisting that MS had violated their contract and insisted that MS ship the Sun JVM.
But it wasn't done by the O/S, it was done by the linker that was shipped with the O/S. You could group modules together and the linker would link in a swapper that would swap them in and out into memory on demand.
Umm.. Word for Windows was known as "Opus" internally, and development started on it in 1982. It was NOT purchased. DOS Word was also done 100% in house, first for the Apple II then ported to the PC. Simyoni was hired by MS to do most of the internal architecture of both products.
It was developed 100% in house, and was intended to be the premier application for the Apple Macintosh.
Nobody remembers, but hjkl were the arrow keys on an ADM-3A terminal. So VI was written using the arrow keys for one of the glass tty's available at the time.
It wasn't exposed through the UI, but powertoys for windows has had multiple desktop switching for 10 years now.
First off. There WERE 5 releases of OS/2, none if which was successful: OS/2 1.0: Console only version. OS/2 1.1: Added a GUI called Presentation Manager OS/2 1.2: Added installable filesystem support OS/2 1.3: IBM redesigned the scheduler and the memory manager and released it as their own version OS/2 1.3 (MS Version): Added support for SCSI drives OS/2 2.0: Shipped after the MS/IBM divorce, 32 bit version of OS/2, also known as Warp. Windows NT was originally called NT OS/2, and was intended to be OS/2 4.0. It was a complete bottom up rewrite of the operating system, the ONLY thing that came from OS/2 was the command interpreter. Win32 wasn't intended to be compatible with OS/2, it was intended to ease porting apps from Win16 to Win32. Since the OS went from a 16 bit OS to a 32 bit OS, there was never any intention of running 16 bit apps natively, they ran under a 16 bit emulation layer (called WoW, for Windows on Windows). Win9x was always supposed to be released, but Win9x was based on the DOS codebase, which was designed from 1982-1987. Security was an irrelevance in those days. That's why it has crappy security - absolutely nobody cared about security back then, except on big-iron machines, and Windows wasn't a big iron type of product. Heck, the internet barely existed back then, and the web certainly didn't. LanMan was ALWAY a Microsoft product, it was NEVER an IBM product (IBM licensed it and sold it, but it wasn't an IBM product - they did NONE of the development on it). NTLM describes the enhancements to the Lan Manager product for Windows NT, it wasn't "renamed". The version numbers of Windows are irrelevant. Windows NT 1.0 shipped as version 3.1 to relate it to Windows 3.1. The version numbers mean NOTHING. If you want to get technical, they are: Windows 1.0, 2.0, 3.0, 3.1, 3.11, WfW, NT 3.1, NT 3.5, NT 3.51, NT4, Win2K, WinXP.
The IBM DOS 4 or the Microsoft DOS 4? There were two, you know. One was a 100% IBM product (PCDOS 4.0), one was a MS product (MS-DOS 4.0 and 4.1). The MS product was only ever sold by two OEMs.
It was co-developed with IBM from the MS-NET project back in 1984. The actual protocol specification I have on my bookshelf is labeled "Microsoft Networks/OpenNET FILE SHARING PROTOCOL" INTEL Part Number 138446 Version 1.9 dated April 21, 1987, authored by Microsoft Corporation and Intel Corporation.
Actually that's not quite right - they have to open up the APIs that are used by their Middleware products. Which means IE, Media Player and I don't know what else (the list of middleware products is called out in the judgement).
If I lease my delivery trucks from Ford, then go out of business, I can't then turn around and sell the trucks as an asset of the firm. Instead, the trucks go back to Ford, which is the real owner of the truck. This is the exact same situation - MS owns the software, KMart leases it, and MS wants to make sure that it gets paid by the new owners of blue light.
MAPI is a well specified set of API interfaces that Outlook uses to communicate to the Microsoft Exchange server. The MAPI provider that Outlook ships with use a propriatary protocol to communicate with the Exchange server. There's absolutely nothing stopping SUSE from producing their own MAPI provider and dropping that under Outlook. Lotus does this for Notes, for example - Outlook runs against a Notes server without modifications because of the MAPI provider that Notes ships.
Judges aren't allowed to follow the normal rules that apply to other U.S. citizens. They don't have free speech rights. They don't have a 5th amendment right to avoid testifying when that testimony would tend to incriminiate themselves (my grandfather went to jail for 6 months on that one, so I know what I'm talking about). They have a REQUIREMENT that they judge the case in front of them impartially and make their decision based solely on the facts introduced into evidence and the law. They are NOT allowed to introduce their own personal feelings into the case, otherwise they make a mockery of the judicial process. Jackson got slapped down because he violated that appearence of impartiality - he made it quite clear to the reporters that he had judged Microsoft guilty BEFORE the trial started. And that's NOT ok.
It's either right in front of you when you click the "START" button, or it's at the top of the "PROGRAM'S" menu item, right next to the Windows Update entry.