15 ms·
Microsoft Word for Windows Version 1.1a Source Code (2014)
- dsp1234 10y agosp2tab.bat which calls tabify.sed to replace spaces with tabs. Nice to know that some things never change. Edit: Also a 16bit windows executable version of GREP, just tested on a 32bit version of Windows and it still works (but not on 64bit)
- umanwizard 10y agoUnfortunately no 16-bit Windows executables work on 64 bit, since x86-64 processors lack the ability to run in 16-bit mode.
- derefr 10y agoI keep seeing this statement, and it's making me wonder: how hard would it have been for Windows 10 to simply ship with a 16-bit WinAPI-binary transpiler (ala Rosetta) or emulator (ala DOSBox)?
- raverbashing 10y agoThere was something called WoW, not sure it did that But at this point I can see why MS would not bother with it
- mishac 10y agoIIRC WoW just provided a layer to point 32bit binaries to 32bit libraries on 64bit systems. So you have the ass-backwards situation where %WINDIR%\System32 is full of 64bit dlls, and %WINDIR\SysWOW64 is full of 32bit dlls.
- akira2501 10y agoIn traditional Microsoft fashion, it's both [0]. WoW is the 16bit compatibility layer on 32bit systems, WoW64 is the 32bit compatibility layer on 64bit systems. [0]: https://en.wikipedia.org/wiki/Windows_on_Windows https://en.wikipedia.org/wiki/Windows_on_Windows
- blakeyrat 10y agoThe original WOW was doing a 16-bit to 32-bit layer. WOW64 (in 64-bit Windows OSes) does 32-bit to 64-bit. The naming of System32 made sense back when they came up with it, but now it's a bit ridiculous. However, since there are so many incompetent Windows programs using hard-coded paths instead of SHGetFolderPath (including, BTW, literally every Java desktop app that doesn't include its own shim-- the JVM itself has this bug!), it's something Microsoft doesn't have the ability to fix.
- maxlybbert 10y agoI doubt it would be hard, but I don't see why anyone would bother. At my last job, we would occasionally need to dig up old code because Microsoft finally removed something they had deprecated several years before. I think it was always amusing. One case that stands out was a utility program that would update data for our users each month. I needed to change something about the string handling. After updating the data, the program would enumerate all running software and kill any copies of our program (so that they would need to read the new data on startup). I noticed that we went through the trouble of enumerating 32-bit and 16-bit programs. Since we hadn't shipped a 16-bit version of our software since the '90s, and we had changed our data format significantly since then, I happily ripped that code out. I don't think you can find information on 16-bit Windows on MSDN anymore. I guess, to put it another way, who's shipping 16-bit programs?
- 0x0 10y agoPretty hard. It's not just a matter of executing 16bit assembly, you also need to handle mapping every single window message and callback between 16bit handles and the real native handles, of which there are thousands and the meaning/interpretation of parameters are unique for each one. This guy is doing just that in .NET. While he uses a full blown CPU emulator for executing 16bit x86, the hard part is all the thunking and bidirectional mapping of handles and memory pointers and stuff: https://medium.com/@CantabileApp/implementing-window-messaging-in-win3mu-979a0ea31571 https://medium.com/@CantabileApp/implementing-window-messagi...
- derefr 10y agoThis seems like the harder strategy of the two. What about simply having a small Windows 3.1 or 95 VM that gets run in the background under HyperV, with fresh VXDs written for it to allow it to use paravirtualized resources, so as to allow it to do the same sort of "infinite framebuffer canvas used to back native windows for the compositor" tricks VMWare's Unity mode and the like do?
- 0x0 10y agoDoesn't MS already ship this as a "Virtual Windows XP Mode" based on VirtualPC? The huge downside is of course the lack of integration with your main OS - copy&paste and drag&drop of rich/dynamic content, OLE embedding, keyboard settings, shared file systems and drive letters, printer drivers, all sorts of windows preferences, applications installing random global windows hooks, etc etc.
- beached_whale 10y agoPretty sure it was MS cutting the 16bit API and amd64 has 16bit real and protected modes Yup! https://en.wikipedia.org/wiki/X86-64 https://en.wikipedia.org/wiki/X86-64
- Aloha 10y agothe VDM used for 16-bit Windows on WinNT required "Virtual 8086 Mode" which is not accessible while in long mode (64 bit)[1] Now Microsoft probably could have engineering a real solution to continue DOS/16-bit support - either via VT-x or just a different solution. But it would have cost engineering hours - for what is a diminishing return. [1] - https://en.wikipedia.org/wiki/Virtual_8086_mode#64-bit_and_VMX_support https://en.wikipedia.org/wiki/Virtual_8086_mode#64-bit_and_V...
- amluto 10y ago> Unfortunately no 16-bit Windows executables work on 64 bit, True. But the do work on Wine on modern 64-bit Linux. :) In fact, even DOSEMU works on modern 64-bit Linux -- take that, Windows backwards compatibility! (But use DOSEMU2 if you do this -- it's better supported.) > since x86-64 processors lack the ability to run in 16-bit mode. Not true. 64-bit processors running in "long mode" (i.e. running a 64-bit kernel) can't enter "virtual 8086" mode, which makes various real mode emulation (DOS non-protected mode, for example) awkward. But modern CPUs are so fast that they can emulate this kind of code very well, and CPUs with virtualization extensions can run real mode or virtual 8086 mode code in a VM even when the host is 64-bit. (64-bit kernels can, in theory, switch out of long mode temporarily, but this is an incredible mess. Linux used to do it for certain UEFI compatibility scenarios, but this proved to be deeply problematic, and Linux doesn't do that any more.)
- andrewf 10y agoCould you talk a little more about DOSEMU2 versus DOSEMU? I'm literally spinning up DOSEMU today to run a bunch of old DOS compilers (Watcom). I can't find much on DOSEMU2 other than its release logs, which seem focused on games and amd64. I think that Lredir/emufs (access to the Linux filesystem) and "dumb" stdin/out are important features to me.
- stuaxo 10y agoI think Stas Sergeev wanted a place to do bigger changes to dosemu at the same time as Bart Oldeman has been stepping back / busy with other things. So Stas made a dosemu2 repo on github, with the additional benefits of being a more modern development environment than sourceforge. It's worth having a play with, some of the older more knarly parts of the source are getting dealt with.
- amluto 10y agoStas also tells me when I accidentally break dosemu2, and dosemu gets updated to take advantage of newer kernel features. Headline features include espfix64 (for more accurate returns to DOS code from interrupts) and proper SS sigcontext support (ditto). Lifechanging, I know :)
- jaclaz 10y ago[2014] http://www.computerhistory.org/press/ms-source-code.html http://www.computerhistory.org/press/ms-source-code.html
- eb0la 10y agoIs this the first source code with Hungarian notation released to the public?(https://en.m.wikipedia.org/wiki/Hungarian_notation https://en.m.wikipedia.org/wiki/Hungarian_notation)
- joshstrange 10y agoEarliest code? Maybe but there are other codebases that are open source that use hungarian notation.
- eb0la 10y agoI meant the earliest code written in that notation released to the public. It could be interesting to list them here. If you know one ancient piece of code with Hungarian notation please tell!
- raverbashing 10y agoWith the wrong way or the right way of doing it?
- zamalek 10y agoSimonyi invented the correct way, so it's most likely to be correctly used. Supposedly the Windows team tried to implement Hungarian notation (because it worked so well for the Office guys), which is where the incorrect usage originates. So not only is this one of the earliest examples, but probably the largest example of correct Hungarian.
- bprieto 10y agoThe oldest maybe, unless there is other code written previously by Simony on the wild. It's called hungarian notation because Charles Simony is hungarian and he was the father of both hungarian notation and Word's source code.
- WaxProlix 10y agoSimonyi, I think he goes by. His example code from his dissertation where (again - I think) he first espoused the theory would have earlier examples still. Word was his first major project, though, and probably the most canonical "first exemplar", if such a thing is meaningful.
- eggoa 10y agoThe 1984 BYTE magazine review said it was "clever, put together well, and performs some extraordinary feats" but "extremely frustrating to learn and operate efficiently." This still describes Word, 32 years later.
- curiousgal 10y agoWord is far from being frustrating to learn nowadays but it does remain frustrating to operate efficiently.
- Retric 10y agoI get annoyed learning every new version of word. Change for change sake while annoying 1+ Billion people requires some serious sadists to be working for Microsoft.
- ocdtrekkie 10y agoThe ribbon was the UI change that got the most people upset, but in retrospect, I feel it was complaint for complaint's sake. Once you learned to use it, I'd argue the ribbon is a vastly superior UI. While it is less customizable, and very obscure features can be harder to find, the most common features are better arranged, better presented, and more usable. There are some changes I dislike in newer versions of Office since, but I wonder how I'll feel about them down the line too.
- greglindahl 10y agoAs an intermittent Word user, I've never learned the ribbon. I could see how you could conclude that your complaining was for complaint's sake, but mine?
- TylerH 10y agoI think he would probably say "I don't like it because I haven't taken any time to learn it" is complaining for complaining's sake.
- davidw 10y agoMorristown, NJ 07960 That's Bell Labs isn't it? The 'obscure language' used is troff: https://en.wikipedia.org/wiki/Troff https://en.wikipedia.org/wiki/Troff
- jejones3141 10y agoNot necessarily. Wasn't _Creative Computing_ magazine based there?
- vdnkh 10y agoBell Labs is in Murray Hill, Morristown is ~30mins away.
- davidw 10y agoThis mentions Morristown: https://en.wikipedia.org/wiki/Telcordia_Technologies https://en.wikipedia.org/wiki/Telcordia_Technologies Seems somehow related though, what with the troff commands. Here's where the example is from, it appears: http://cmd.inp.nsk.su/old/cmd2/manuals/unix/UNIX_Unleashed/ch08.htm http://cmd.inp.nsk.su/old/cmd2/manuals/unix/UNIX_Unleashed/c... Also: http://articles.chicagotribune.com/1986-05-14/business/8602030927_1_bellcore-bell-communications-research-bell-labs http://articles.chicagotribune.com/1986-05-14/business/86020... So... not Bell Labs, I guess, but maybe something related?
- nemild 10y agoSee my comment in this thread. Telcordia/Bellcore was a spinout from Bell Labs after the DOJ antitrust action in the early 1980s. Bell Labs stayed with AT&T and Bellcore was the R&D lab for the newly created Baby Bells composed of many staff from Bell Labs.
- nemild 10y agoBellcore/Telcordia was spun out from Bell Labs as the R&D lab of the Baby Bells after the early 1980s antitrust suit against AT&T. Before the breakup, there were a number of labs that composed Bell Labs in NJ, not only in Holmdel. My father worked in Morristown at Telcordia Technologies/Bellcore in the 1980s/90s and before that at Bell Labs in the 70s.
- TAForObvReasons 10y ago> To access this material you must agree to the terms of the license displayed here, which permits only non-commercial use and does not give you the right to license it to third parties by posting copies elsewhere on the web. Does this conflict with the terms of the Open Specification Promise? https://en.wikipedia.org/wiki/Microsoft_Open_Specification_Promise https://en.wikipedia.org/wiki/Microsoft_Open_Specification_P... If so, does that taint anyone working on a project involving DOC word documents?
- faragon 10y agoOpus/sort.c implements Merge Sort, limited to 16383 records.
- mizzao 10y ago> We are grateful to Roy Levin, Managing Director of Microsoft Research, Silicon Valley, for working hard to find the source code and getting permission for us to release it. Ironic as MSR-SVC was shut down a few months after this article was written.
- ungzd 10y agoIt's still dark ages of word processing today but "cryptic commands" are in markdown and html.
- lewisjoe 10y agoNaive question: Is it possible to build/run this source in a simulator, VM or something? Is there any way, we can run windows 1.1, and get this up and running as of today?
- kyberias 10y agoYes. You can take ms-dos with Windows 1.1, run it in a VM and build this using the compiler tools included in the package. I've done it and it works. If I remember correctly, there are instructions in some blogs to do this. UPDATE: This is the thread from the time of the release: https://www.betaarchive.com/forum/viewtopic.php?t=31096 https://www.betaarchive.com/forum/viewtopic.php?t=31096 (see my question in the thread)
- pcunite 10y agoA file "filewin.c" has the following comment: FUTURE: MacWord does a DoJump(&venvMainLoop) !! (which,according to DavidLu is "guaranteed to crash soon there after"). we should really figure out a better way... Who is DavidLu and did this ever get fixed? :-)
- pcunite 10y agoLooks like it was David Luebbert. https://storify.com/leonzandman/ex-microsoft-engineer-insightful-comments https://storify.com/leonzandman/ex-microsoft-engineer-insigh...
- albertgao 10y agoreading comments gave me a illusion that only the smartest people deserve to use Word. seems I can get a Mensa certification on using every editions of Word well without too much learning.....God I need to test my IQ, should be 9999.
- x0 10y agoThere's a whole bunch of sed files in the source code!
- iconjack 10y agoComes on 33 disks, 28 of which are printer drivers.
- deleted 10y ago[deleted]
- olav 10y agoI remember the joy of writing a 200 page book in FrameMaker on a smallish SPARCstation in 1994. Even in 1998 it was easy to convince my boss to license FrameMaker for Windows as writing software. Word was still too buggy to write anything exceeding a few pages or with embedded images with it. Sadly, Adobe never marketed FrameMaker to a mass market.
- dragonwriter 10y agoThey didn't because competing with the numerous low-end DTP solutions at a price that would make it remotely competitive in the mass market would have been fairly pointless for them. And they still would probably have lost that market to Word for the same reason the whole stack of players that did compete in that market did: no one in the mass market is regularly writing and laying out books, they are either mostly writing documents of a few pages with the occasional longer work, or preparing copy and art.that ia going to be fed into some publisher's layout system.
- coldcode 10y agoThe article is missing a bit, since Word for Mac (1985) was more the model for the eventual Windows 1.X version, but isn't even mentioned in the article. There were also versions for other "windowed" OS's during the same 5 year period before Windows was sufficiently viable to make it work. People often forget that new apps appeared first on the Mac until around 1990 or so when Windows 3.0 shipped (Word appeared a bit before); basically MacOS was much more advanced than Windows up until that point. After Windows 3 the first platform flipped completely to Windows. I shipped my first MacOS app in 1987.
- bluedino 10y agoI'd be interested in learning about the DOS version. I remember using it but it was a text mode application as far as I can remember (2.0?)
- lobster_johnson 10y agoIt was text only. The article says it was WYSIWYG, but that was only the later Mac and Windows versions. The early text versions only did some stuff like underlining, bold and alignment. Microsoft released Word for DOS even after the Windows version came out, and I remember a lot of people were surprised that they bothered -- 5.5 was even transformed into a curses-style "graphical" DOS app [1] with colour, drop down menus (with shadows!) and mouse support (but drawn with ASCII characters), similar to Borland's DOS apps, but it seemed like a perfunctory release -- at that point it was obvious DOS was legacy and that Windows was the future of Microsoft. [1] https://www.google.com/search?q=microsoft+word+5.5+dos&num=30&safe=off&client=safari&hl=en-us&prmd=sivn&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiy3PCcpZjRAhUP6WMKHVcMB1IQ_AUICCgC&biw=375&bih=559 https://www.google.com/search?q=microsoft+word+5.5+dos&num=3...
- anonymfus 10y ago>similar to Borland's DOS apps And to Visual Basic for DOS.
- 10y ago
- chris_wot 10y agoThis actually might be useful in rendering old documents for The Document Foundation's file format project.
- sytelus 10y agoIt seems that Microsoft Word unseated far more established player WordPerfect even before OS dominance. Any insights on how this happened?
- Spooky23 10y agoMicrosoft was the office suite for the masses. WordPerfect acolytes were secretaries, writers, attorneys, etc who had mastered the keyboard shortcut system. WordPerfect broke some of that when they went GUI. They also had a weaker spreadsheet. There are still grumpy graybeard lawyers today using WordPerfect v.whatever from 1996. Later on they got squeezed between IBM muscling their customers onto Lotus Notes and Microsoft. That put them in the grave and Exchange filled it in.
- raesene9 10y agoSo I was an IT manager (well the only IT person for a ~50 person accountancy firm) back in 1995 and I can tell you how it unseated wordperfect in my org. Easy really... it was free! So basically if you bought Gateway PCs with Windows 95 you got Office 95 Pro for free with them. In a cost-constrained environment it was a no brainer compared to spending money on Wordperfect licenses. When I got there it was mainly Wordperfect for DOS and Lotus 1,2,3 for spreadsheets but when we rolled out new PCs with Windows 95 we migrated to Excel and Word. In terms of productivity there was a definite hit for "pro" users where they were faster with Wordperfect than Word but it was possible to get past that and Word used to have a pretty useful compatibility layer so you cold use Wordperfect commands in Word.
- mark-r 10y agoWord 1.1 is the catalyst that got me to try Windows. I was familiar with word for DOS at the time, and the potential of proportional fonts and OS-level printer drivers caught my imagination - it was the future, I was sure. It didn't hurt that I got a promotional copy for cheap with Windows bundled. I still have the floppies around somewhere. Many years later, and I'm still writing Windows programs. Excellent strategy on Microsoft's part. Nice to see this hugely transformative software available in an archive.
- peterburkimsher 10y ago"Will Office be open source in future?" "Yes. I give you my Word."
- pritambarhate 10y agoWe use GSuite (Google Apps and Email) at work. Though I have MS Word installed on my machine, I find that I increasingly use Google Docs for most of my document needs. Only when I need to something that just can't be done in Google Docs, I open MS Word. This is becoming increasingly rare. I mainly use MS Word to open documents shared by Clients and to check the resumes of candidates which are generally in MS Word format in India. Google Sheets also have improved a lot over the past year or so.
- HNSucksAss 10y agoThe inclusion of a full programming language, and one capable of raising custom dialog boxes, was a stroke of genius that changed the way my colleagues and I worked. I spent nearly as much time writing Word macros as I did the technical documentation I was hired to create... which launched my programming career.
- xurukefi 10y agoProfanity check: $ grep -i fuck * -r Opus/asm/wordgrep.asm:; BP is used as always, the other registers are free to fuck with. Opus/asm/wordgrep.asm: je another_fucking_out_of_range_jump Opus/asm/wordgrep.asm:another_fucking_out_of_range_jump:
- erdemozg 10y agohaha, good one.
- the_mitsuhiko 10y agoI wonder how much of this code still lives on in current generation Word.
- cja 10y agoWhat was "PC Word" and how did it relate to "Microsoft Word"? Was it also for Windows? (References to both found in http://antitrust.slated.org/www.iowaconsumercase.org/011607/8000/PX08875.pdf http://antitrust.slated.org/www.iowaconsumercase.org/011607/...)