(Part 2) Reddit mentions: The best microsoft os guides
We found 162 Reddit comments discussing the best microsoft os guides. We ran sentiment analysis on each of these comments to determine how redditors feel about different products. We found 53 products and ranked them based on the amount of positive reactions they received. Here are the products ranked 21-40. You can also go back to the previous section.
21. Inside the Windows NT File System
- Used Book in Good Condition
Features:
Specs:
Height | 9.2 Inches |
Length | 7.4 Inches |
Weight | 0.56438339072 Pounds |
Width | 0.38 Inches |
Number of items | 1 |
22. Windows 3.1 secrets (The Secrets Series)
Used Book in Good Condition
Specs:
Height | 9.2 Inches |
Length | 2.34 Inches |
Weight | 3.19890742162 Pounds |
Width | 7.41 Inches |
Number of items | 1 |
23. Microsoft Windows PowerShell: TFM
- Used Book in Good Condition
Features:
Specs:
Height | 9.01573 Inches |
Length | 5.98424 Inches |
Weight | 1.80558592578 Pounds |
Width | 1.2562967 Inches |
Release date | January 2007 |
Number of items | 1 |
24. Alan Simpson's Windows? 98 Bible
Specs:
Height | 9.4995873 Inches |
Length | 7.40156 Inches |
Weight | 3.8029740195 Pounds |
Width | 2.118106 Inches |
Release date | June 1998 |
25. C# Cookbook
- Used Book in Good Condition
Features:
Specs:
Height | 9.19 Inches |
Length | 7 Inches |
Weight | 2.6014546916 Pounds |
Width | 1.53 Inches |
Number of items | 2 |
26. Programming Windows 95 with MFC: Create Programs for Windows Quickly with the Microsoft Foundation Class Library (Microsoft Programming Series)
Specs:
Height | 9.24 Inches |
Length | 7.42 Inches |
Weight | 3.4 Pounds |
Width | 1.83 Inches |
Number of items | 1 |
27. New Windows Interface
- Provides smooth upper and lower-body cardiovascular workout with 16 resistance levels
- 12 Workout programs, including 6 course profiles, fitness test and custom workout
- Integrated grip heart rate system for easy fitness monitoring
- Ergonomic handles for multiple workout positions, natural-feeling 18-Inch stride
- 300-Pound maximum user weight, 5-year warranty on frame, 1 year on parts and electronics
Features:
Specs:
Height | 8.99 Inches |
Length | 7.39 Inches |
Weight | 3.3 Pounds |
Width | 1.47 Inches |
Number of items | 1 |
28. Advanced Windows
- Used Book in Good Condition
Features:
Specs:
Height | 9 Inches |
Length | 7.5 Inches |
Weight | 3.7 Pounds |
Width | 1.75 Inches |
Number of items | 1 |
30. Undocumented Windows: A Programmers Guide to Reserved Microsoft Windows Api Functions (The Andrew Schulman Programming Series/Book and Disk)
Specs:
Height | 9.25 Inches |
Length | 7.5 Inches |
Weight | 2.67200261544 Pounds |
Width | 1.5 Inches |
Number of items | 1 |
31. Windows via C/C++ (softcover) (Developer Reference)
Specs:
Height | 9 Inches |
Length | 7.38 Inches |
Weight | 3.4392112872 Pounds |
Width | 1.69 Inches |
32. iOS 7 Programming Pushing the Limits: Develop Advance Applications for Apple iPhone, iPad, and iPod Touch
Specs:
Height | 9.299194 inches |
Length | 7.421245 inches |
Weight | 1.86070149128 pounds |
Width | 0.960628 inches |
Number of items | 1 |
33. Pathfinder: Kingmaker. Für Windows 8/10
- Go it alone, or team-up with up to three friends as you collaborate and combine your unique skills to take down enemies. As you shape your appearance and load-out, your gameplay experience will also evolve
- All enemies are persistently simulated in the world, and roam the landscape with intent and purpose. When you manage to destroy a specific enemy component, be it armor, weapons or sensory equipment, the damage is permanent;Genre: Action and Adventure|First Person Shooter
- Experience a full day/night cycle with dynamic weather effects like snowfall, rainstorms and violent winds, all simulated through the award-winning open world engine Apex
- Among the loot, you will find outfits and hairstyles to recreate your favorite 1980s style to take on the machines in style
- Some enemies are too powerful to attack head-on. Instead, adopt stealth tactics by moving silently, exploiting the enemy's senses and using the environment to your advantage
Features:
Specs:
Height | 7.63778 Inches |
Length | 5.47243 Inches |
Width | 0.70866 Inches |
Release date | September 2018 |
34. Visual Models for Software Requirements (Developer Best Practices)
- Used Book in Good Condition
Features:
Specs:
Height | 8.97636 Inches |
Length | 7.51967 Inches |
Weight | 1.75047036028 Pounds |
Width | 1.02362 Inches |
Number of items | 1 |
35. Windows Forms Programming in C#
Specs:
Height | 9.21 Inches |
Length | 7.01 Inches |
Weight | 2.4691773344 Pounds |
Width | 1.66 Inches |
Release date | September 2003 |
Number of items | 1 |
36. Developing Windows Error Messages: Error Messages that Communicate
Used Book in Good Condition
Specs:
Height | 9.19 Inches |
Length | 7 Inches |
Weight | 1.1904962148 Pounds |
Width | 0.76 Inches |
Number of items | 1 |
37. MS-DOS Encyclopedia: Versions 1.0 Through 3.2
- Used Book in Good Condition
Features:
Specs:
Weight | 7.40312275796 Pounds |
Number of items | 1 |
38. The Mother of All Windows 98 Books
Specs:
Height | 9.25 Inches |
Length | 7.5 Inches |
Weight | 2.755778275 Pounds |
Width | 1.25 Inches |
Number of items | 1 |
39. Debugging Windows Programs: Strategies, Tools, and Techniques for Visual C++ Programmers
Specs:
Height | 9 Inches |
Length | 7 Inches |
Weight | 2.10100535686 Pounds |
Width | 1 Inches |
Number of items | 1 |
40. Deployment Fundamentals, Vol. 4: Deploying Windows 8 and Office 2013 Using MDT 2012 Update 1
Specs:
Release date | January 2013 |
🎓 Reddit experts on microsoft os guides
The comments and opinions expressed on this page are written exclusively by redditors. To provide you with the most relevant data, we sourced opinions from the most knowledgeable Reddit users based the total number of upvotes and downvotes received across comments on subreddits where microsoft os guides are discussed. For your reference and for the sake of transparency, here are the specialists whose opinions mattered the most in our ranking.
Here is how I go about trying to become an "expert":
In short, if you have ever read Alan Perlis's "Epigrams on Programming", most of the things there are pithy explanations of what I'm about to say. Probably my favorite epigram as it relates to being a "language lawyer" is:
​
>10. Get into a rut early: Do the same process the same way. Accumulate idioms. Standardize. The only difference(!) between Shakespeare and you was the size of his idiom list - not the size of his vocabulary.
​
This is critical, because, as most here will tell you, it's nearly impossible to keep every aspect of C# - both how and why - in your head at all times.
​
That said, at one point I was an awful engineer. Let's get into how I became a significantly better engineer.
> Years ago Lotus Notes was very popular as an email client, but it was garbage.
Because DOS ain't done 'till Lotus won't run
> There is nothing stopping you from releasing competing office software.
Other than not having proper documentation on the secret interfaces that will let it interface efficiently with the underlying operating system.
It's very interesting and telling why you refuse to make any comments on why MS-Office has not created any new, interesting technology for well over a decade.
Don't worry, I understand your motives
Oh, really ? Well, when NTFS first came, it held so many promises. However, I remember reading [the book] (http://www.amazon.com/Inside-Windows-NT-File-System/dp/155615660X) and finding many things that were not in the implementation running on my NT3.1/3.5
So, well, when the first version of your file system promises stuff in its accompaning "inside" documentation, that are not delivered, it is hard to believe that it is due to compatibility.
And the impact on every company's security? Well, this is 1994 we are talking about. Very different times...
The ONLY reason I'm making the money I am today is because of Brian Livingston's "Windows 3.1 Secrets". I read that book all 1000 pages cover to cover and then started fixing every computer I could get my hands on. Through a friend of friend I got hired at a tech support job and it's all history from there.
As everyone has said, PowerShell, but also take advantage of your remote management tools. Grab the Remote Server Administration Tools for your version of Windows from MS and do everything you can remotely. Even better, if you're running Windows 8+ (I know, we all miss the start menu) you can use the new 2012 version of Server Manager (also in the RSAT for Windows 8) to manage them remotely including installing and configuring most roles and features using GUIs.
For PowerShell resources, most of that you can find via Google. I learned my basic knowledge from this book. I also follow this blog to learn some random tips and tricks that I wouldn't learn otherwise.
Most of the value will be for companies trying to make software that will compete against Microsoft products.
Remember the sentence "DOS Ain't Done til Lotus Won't Run"? It has always been a Microsoft speciality, make a public API for the OS that's less efficient than the secret API they use in their own products.
That's why books like this have to be published.
I remember seeing TV ads for the N64, is that good enough? My family didn't even get a computer until 1998 (Win98!) let alone a game console. And I decided it would be fun to read through the Windows 98 Bible, a ~1,000-page book that led me to play around with the OS and become the resident computer expert. (I switched to OS X ten years later, though, after a few years of reading about Linux/OS X/OS9)
Something like this > https://www.amazon.com/C-Cookbook-Stephen-Teilhet/dp/0596003390
Yes. It's like baking recipes. But for C# (or whatever lang you like). You bake/code-along
If you simply must learn MFC, the best books remain the two editions of Jeff Prosise's book on the subject.
The first edition is better, in my opinion. It's available for less than a dollar on Amazon US ( https://www.amazon.com/Programming-Windows-MFC-Microsoft-Foundation/dp/1556159021 ).
It's not "up to date" in that it wasn't written recently and doesn't cover the last two decades' worth of additions to the MFC libraries. It is "up to date" in that it explains slowly and carefully the thinking behind MFC, and how to actually write for it yourself (i.e. not just pushing buttons on a wizard). If you learn form this book, you'll know what you're doing and you can then just browse through the current MFC API to see what additions have been made available to you. Also, by learning from Jeff Prosise, you'll actually have a better understand of MFC than the vast majority of people writing code in it, and you'll be horrified at how ugly and wasteful the wizard generated code is compared to what you can bang out yourself. People with many years' of MFC wizard experience will stand in slack-jawed awe as you craft tight MFC code with the power of your own mind.
Think carefully about why you want to learn it, though. The good reason for learning it would be that you've got to maintain a set of code that use it. If you're looking to get started with GUI programming, it's a bad choice.
Yes, there is.
New Windows Interface (Microsoft Corporation)
http://www.amazon.com/dp/1556156790/ref=rdr_ext_sb_pi_sims_1
One caveat: My copy of this book is at work, so I am relying on my memory. I think this is the one that contains a numbered list of terms in English. The following pages contain the terms that MS uses when they translate to other languages. These lists are not in later editions.
So the English list might have 85. Help If you look at the Spanish page: 85 Ayuda. Look at the German page: 85 Hilfe
Is this what you're looking for?
edit: I'm at work: This is the correct book. The International Word Lists is in Appendix E
It’s gonna be hard to give you much without picking a specific OS—details can vary widely even within a single OS family line—but an OS book is probably a good place to start. Tanenbaum’s book is the go-to.
Alternatively, there are books on specific techniques like garbage collection, or books more generally on programming for UNIX/POSIX/Linux or Windows (via Win16/32/64 API, not the six-mile-high shitheap piled atop), which would tell you some about how memory management works in down at least to whatever abstract hardware interface the kernel uses.
Wow, this totally brought me back to my high school days, when for a time I was carrying around the Waite Group's MS-DOS Bible. (My mom thought I was carrying around a real Bible and that MS-DOS was some new translation...)
If you really want to see how windows actually works there is a really good book called "Windows Via C++". It breaks down almost every base system.
http://www.amazon.com/Windows-via-Edition-Developer-Reference/dp/0735663777
Advanced topics. We're flooded with entry level stuff, don't need more of the same. Advanced isn't just digging deeper into things that re-define the language, we have tons of protocol programming and overriding operators.
There was a "pushing the limits" book years ago... make one like that.
https://www.amazon.com/iOS-Programming-Pushing-Limits-Applications/dp/1118818342
Stopped at iOS 7, make a new version that covers modern things.
I mostly buy physical editions, there are a lot on PC, also collectors editions, but as you said, there is most of the time a Steam key in it besides the Disks.
You can collect on PC quite well, but reselling is history.
As example I bought these three in march (all of them came with a Steam key):
Generation Zero CE
Frostpunk
Pathfinder: Kingmaker
There is a whole sub-profession built around requirements engineering/management that may be of use:
https://www.amazon.com/Requirements-Engineering-Projects-Management-Industrial/dp/3319185969/ref=mt_hardcover?_encoding=UTF8&me=
http://dl.acm.org/citation.cfm?id=2227400
Also, UML and SysML have helped me a whole lot to clarify design elements to junior devs throughout my career. If you aren't expert-level in those, you may want to consider bootstrapping up some expertise ;)
Edit - Books more relevant to Software Requirements Management:
https://www.amazon.com/Visual-Software-Requirements-Developer-Practices/dp/0735667721/ref=sr_1_5?s=books&ie=UTF8&qid=1478992958&sr=1-5&keywords=software+requirements+management
https://www.amazon.com/Writing-Effective-Cases-Alistair-Cockburn/dp/0201702258/ref=pd_sim_14_4?_encoding=UTF8&psc=1&refRID=7273H45W7ZCJHCFZVP7M
Edit 2 - TL;DR - Build out your internal Software Requirements Process.
My first thought was "shopped" but I was surprisingly wrong
If you're interested in this, try and get a copy of the MS DOS Encyclopedia: http://www.amazon.com/dp/1556150490/ - it contains a big chunk of the whys and the hows. It's about 5 inches thick.
I've got a copy of this signed by Mr Gates himself when he attended the IBM PC User Group in 1988. Now I feel old.
Haha. I'd agree except he doesn't really realize it. I think part of it is that he doesn't really have a good understanding of how to wade through forums, as well as his tendency to have gone for more thorough information on stuff rather than specific issues. He could read a modern version of this and be useful, or he can help track down drivers that will work with a laptop that isn't meant for a specific OS, but if he wants to know what kind of extension to download or has some kind of non-obvious error then he goes into 'help me' mode.
Yeah, schools ought to teach debugging, along with source control, how to write tests, how to write documentation, ...
Hard to figure how you'd cram that into a four-year degree curriculum, though. It already seems fairly packed.
Debugging Windows Programs was very helpful to me when I started writing larger applications after college. Not only for Windows-specific stuff, but for developing the attitude of a debugger.
It is standard practice to build the reference image in a VM. Installing applications in the base image it not a good idea. Only do this if you HAVE to. It is better to add all your applications as packages and install via task sequence or as selectable application list during deployment. I would suggest you check out this book:
https://www.amazon.com/Deployment-Fundamentals-Vol-Deploying-Windows-ebook/dp/B00B9IB286/ref=sr_1_5?ie=UTF8&qid=1520347968&sr=8-5&keywords=johan+arwidmark
Ukratko, WPF aplikaciju praviš deklarativnim UI-jem u XML-u i kodom iza koji reaguje na ivente, radi pos'o, itd.. Windows Form aplikacija je sasvim drugi frejmvork sa sopstvenim apstrakcijama i programskim modelom, sve se dešava u kodu. Dve različite .NET UI tehnologije sa istim ciljem, otpr. kao Swing i AWT u Java svetu (ko se seća ovog drugog, nemam pojma da li se to još igde koristi).
Ne postoji jako dobar razlog da danas koristiš Windows Forms, osim ako to nisi koristio do sada i znaš mu sve fore i fazone, a rokovi su pretanki da bi osvajao u procesu novu tehnologiju.
Edit: Ovo je po verovatno najbolja WPF knjiga - WPF Unleashed, tj. bar je bila do pre nekoliko godina, a ovo pamtim kao najbolju Windows Forms knjigu - Windows Forms Programming.
Of course certain Microsoft applications did deliberate use APIs that weren't publicly documented to achieve things there were otherwise impossible.
Any and every bad developer was able to use the same publicly undocumented APIs. The furver started after they were publicly undocumented in Windows Undocumented.
Just because a bad developer is working at Microsoft when he wrongly uses an undocumented API doesn't make it Microsoft's fault.