🌈 Social 📸 Photography 🌈

Richard CarlssonThe 1990s are still alive and feebly kicking. <a href="https://mastodon.nu/tags/windowsnt" class="mention hashtag" rel="nofollow noopener" target="_blank">#windowsnt</a>

Wilfredo 💬<a href="https://mastodon.social/@itsfoss" class="u-url mention" rel="nofollow noopener" target="_blank">@itsfoss</a>I'm grateful for my first contact with the <a href="https://fosstodon.org/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> world in 1998, in the college <a href="https://fosstodon.org/tags/computer" class="mention hashtag" rel="nofollow noopener" target="_blank">#computer</a> lab... despite the <a href="https://fosstodon.org/tags/WindowMaker" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowMaker</a> <a href="https://fosstodon.org/tags/WindowManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowManager</a> heheheThe previous year we used the <a href="https://fosstodon.org/tags/lab" class="mention hashtag" rel="nofollow noopener" target="_blank">#lab</a> of another <a href="https://fosstodon.org/tags/college" class="mention hashtag" rel="nofollow noopener" target="_blank">#college</a> in the same <a href="https://fosstodon.org/tags/university" class="mention hashtag" rel="nofollow noopener" target="_blank">#university</a> running <a href="https://fosstodon.org/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> <a href="https://fosstodon.org/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> 3.51In 1999 I tried using Linux on my personal computer, and since 2001 I definitively used the <a href="https://fosstodon.org/tags/Brazilian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Brazilian</a> <a href="https://fosstodon.org/tags/distro" class="mention hashtag" rel="nofollow noopener" target="_blank">#distro</a> <a href="https://fosstodon.org/tags/Conectiva" class="mention hashtag" rel="nofollow noopener" target="_blank">#Conectiva</a> (now defunct)

Wesley Moore:windows95: They flipped the order, but nearly 30 years later it's almost the same UI.First: Windows NT 4 (1996), Second: Windows 11 (2025)<a href="https://mastodon.decentralised.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://mastodon.decentralised.social/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a> <a href="https://mastodon.decentralised.social/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a>

JdeBP<a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener" target="_blank">@cks</a> Well, yes. It's Windows NT.Everything in the Native API always returns an explicit NTSTATUS separately from (mostly via "out" parameters) actual result values.OS/2 was the same, and it's one of the things that Microsoft and IBM did right. Albeit that POSIX Threads got this right, too.The dates on all of those show that by the late 1980s people already knew that one could do better than setting errno or the result from one value according to a flag bit.<a href="https://tty0.social/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> <a href="https://tty0.social/tags/NativeAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#NativeAPI</a>

JdeBP<a href="https://mas.to/@mroach" class="u-url mention" rel="nofollow noopener" target="_blank">@mroach</a> <a href="https://mastodon.scot/@ColinHaynes" class="u-url mention" rel="nofollow noopener" target="_blank">@ColinHaynes</a> In the meantime, Microsoft tried to ruin everyone's fun by making Windows NT 10.0 be the same version number as used by the marketing people.But it's alright. It has slipped again. Windows NT version 10.0.26100 is is not called that by the marketing people.One is not immune in the non-Microsoft world, though. Place these in the correct order:Buster Etch Forky Jessie Potato Sarge Sid Wheezy Trixie(-:<a href="https://mastodonapp.uk/tags/MicrosoftWindows" class="mention hashtag" rel="nofollow noopener" target="_blank">#MicrosoftWindows</a> <a href="https://mastodonapp.uk/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> <a href="https://mastodonapp.uk/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a>

Kevin Karhan :verified:<a href="https://mas.to/@DenOfEarth" class="u-url mention" rel="nofollow noopener" target="_blank">@DenOfEarth</a> <a href="https://mastodon.sdf.org/@ytc1" class="u-url mention" rel="nofollow noopener" target="_blank">@ytc1</a> <a href="https://mastodon.social/@aka_pugs" class="u-url mention" rel="nofollow noopener" target="_blank">@aka_pugs</a> well <a href="https://infosec.space/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> owned the workstation market because <a href="https://infosec.space/tags/Vendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vendors</a> like <a href="https://infosec.space/tags/SGI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SGI</a> & <a href="https://infosec.space/tags/Sun" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sun</a> failed to innovate...<ul><li>Abeit sgi hals self-inflicted that by removing the reasons to buy their stuff when they switched to <a href="https://infosec.space/tags/Itanium" class="mention hashtag" rel="nofollow noopener" target="_blank">#Itanium</a> <a href="https://infosec.space/tags/CPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPU</a>|s and <a href="https://infosec.space/tags/nvidia" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvidia</a> <a href="https://infosec.space/tags/GPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPU</a>|s and not developing <a href="https://infosec.space/tags/IRIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#IRIX</a> any further! </li></ul><a href="https://infosec.space/tags/SunMicrosystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#SunMicrosystems</a> at least didn't stall in terms of <a href="https://infosec.space/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a>, but once <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oracle</a> acqured them and started shaking down Sun Technology users for "<a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> infringement" and "License Violations" they basically made using anythibg but <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> a bad choice on <a href="https://infosec.space/tags/Servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Servers</a>!<ul><li>Meanwhile <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> to this day doesn't even halfass <a href="https://infosec.space/tags/Servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Servers</a> anymore and is constantly giving customers and espechally professionals the middle finger in terms of <a href="https://infosec.space/tags/Repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Repairability</a> & <a href="https://infosec.space/tags/Maintainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Maintainability</a>!</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.sdf.org/@ytc1" class="u-url mention" rel="nofollow noopener" target="_blank">@ytc1</a> <a href="https://mas.to/@DenOfEarth" class="u-url mention" rel="nofollow noopener" target="_blank">@DenOfEarth</a> <a href="https://mastodon.social/@aka_pugs" class="u-url mention" rel="nofollow noopener" target="_blank">@aka_pugs</a> I know.And espechally in <a href="https://infosec.space/tags/ScientificComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScientificComputing</a> a lot of researchers loved working with <a href="https://infosec.space/tags/SunMicrosystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#SunMicrosystems</a> and when <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oracle</a> took over that relationship got sour'd instantly due to <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oracle</a> <a href="https://infosec.space/tags/CEO" class="mention hashtag" rel="nofollow noopener" target="_blank">#CEO</a> <a href="https://infosec.space/tags/LarryEllison" class="mention hashtag" rel="nofollow noopener" target="_blank">#LarryEllison</a>...-> <a href="https://infosec.space/@kkarhan/114682503920794745" translate="no" rel="nofollow noopener" target="_blank">https://infosec.space/@kkarhan/114682503920794745</a>One of the big successes of <a href="https://infosec.space/tags/Sun" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sun</a> was that they basically declared a unilateral "ceasefire" in terms of <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> & <a href="https://infosec.space/tags/Patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#Patents</a> re: <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>. Whereas Oracle didn't seem willing to honour that.<ul><li>Without that cooperative atmosphere we saw <a href="https://infosec.space/tags/OpenOffice" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenOffice</a> devs literally forking off into <a href="https://fosstodon.org/@libreoffice" class="u-url mention" rel="nofollow noopener" target="_blank">@libreoffice</a> and projects like <a href="https://infosec.space/tags/illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#illumos</a> and <a href="https://mastodon.social/@openzfs" class="u-url mention" rel="nofollow noopener" target="_blank">@openzfs</a> scramble to save what was OpenSource'd and also rescue that.</li></ul>Obviously <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> with it's <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2only</a>-Kernel and most of it's Userland could not get 'closed-sourced' like <a href="https://infosec.space/tags/OpenSolaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSolaris</a> which instantly got stomped out by Oracle as they wanted to sqeeze <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solaris</a> for profits and milk their clients in typical Oracle fashion...<ul><li>Which is sad because <a href="https://infosec.space/tags/competition" class="mention hashtag" rel="nofollow noopener" target="_blank">#competition</a> breeds <a href="https://infosec.space/tags/innovation" class="mention hashtag" rel="nofollow noopener" target="_blank">#innovation</a> and a lot of stuff like <a href="https://infosec.space/tags/Zones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zones</a> in Solaris really were at their time really forcing <a href="https://infosec.space/tags/KVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#KVM</a>, <a href="https://infosec.space/tags/bhyve" class="mention hashtag" rel="nofollow noopener" target="_blank">#bhyve</a> and <a href="https://infosec.space/tags/BSDjails" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSDjails</a> to up their game for good.</li></ul>Now granted, I do know someone who for most of their life made their money dealing with the intricacies of setting up <a href="https://infosec.space/tags/postfix" class="mention hashtag" rel="nofollow noopener" target="_blank">#postfix</a>, <a href="https://infosec.space/tags/sendmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#sendmail</a> and <a href="https://infosec.space/tags/courier" class="mention hashtag" rel="nofollow noopener" target="_blank">#courier</a> <a href="https://infosec.space/tags/MailServers" class="mention hashtag" rel="nofollow noopener" target="_blank">#MailServers</a> on Solaris and if I ask said person about that they give me a kilometer stare, so OFC like a <a href="https://infosec.space/tags/SysV" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysV</a> - <a href="https://infosec.space/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> systems Solaris and <a href="https://infosec.space/tags/SunOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SunOS</a> really are one of the reasons <a href="https://infosec.space/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> won the "<a href="https://infosec.space/tags/WorkstationWar" class="mention hashtag" rel="nofollow noopener" target="_blank">#WorkstationWar</a>" and why - if anyone - <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> won the last "<a href="https://infosec.space/tags/UnixWar" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnixWar</a>"...<ul><li>Still I do am sad that I declined that <a href="https://infosec.space/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a> position at a leading research center I'm not at liberty to name and I do know there's OFC still some critical infrastructure running even older Solaris servers...</li></ul><a href="https://mastodon.sdf.org/@ytc1/114689337148586939" rel="nofollow noopener" translate="no" target="_blank">https://mastodon.sdf.org/@ytc1/114689337148586939</a>

C.Those who fail to understand Unix are doomed to forever keep trying to turn it into Windows NT.<a href="https://mindly.social/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> <a href="https://mindly.social/tags/UnixPhilosophy" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnixPhilosophy</a> <a href="https://mindly.social/tags/simplicity" class="mention hashtag" rel="nofollow noopener" target="_blank">#simplicity</a> <a href="https://mindly.social/tags/OneJob" class="mention hashtag" rel="nofollow noopener" target="_blank">#OneJob</a> <a href="https://mindly.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://mindly.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://mindly.social/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a>

MikeMicrosoft of the 90s: you can't install a database server because your web browser needs to be updated.<a href="https://mas.to/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> <a href="https://mas.to/tags/SQLServer7" class="mention hashtag" rel="nofollow noopener" target="_blank">#SQLServer7</a>

Mark GardnerDid I just do a <a href="https://social.sdf.org/tags/Markdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#Markdown</a> conversion of Mark Russinovich’s seminal 1998 article on <a href="https://social.sdf.org/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> (and by extension, all modern versions of <a href="https://social.sdf.org/tags/MicrosoftWindows" class="mention hashtag" rel="nofollow noopener" target="_blank">#MicrosoftWindows</a>)’ debt to <a href="https://social.sdf.org/tags/DEC" class="mention hashtag" rel="nofollow noopener" target="_blank">#DEC</a>’s <a href="https://social.sdf.org/tags/VMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VMS</a> <a href="https://social.sdf.org/tags/OperatingSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#OperatingSystem</a>? Just so I could have a decent copy apart from the dusty carried-over archived version at <a href="https://www.ITProToday.com/server-virtualization/windows-nt-and-vms-the-rest-of-the-story" rel="nofollow noopener" translate="no" target="_blank">https://www.ITProToday.com/server-virtualization/windows-nt-and-vms-the-rest-of-the-story</a> ?Why yes, yes I did. Why not?<a href="https://social.sdf.org/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://social.sdf.org/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#RetroComputing</a> <a href="https://social.sdf.org/tags/VAX" class="mention hashtag" rel="nofollow noopener" target="_blank">#VAX</a>

Benjamin Carr, Ph.D. 👨🏻‍💻🧬How OS/2 flop went on to shape modern <a href="https://hachyderm.io/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#software</a> <a href="https://hachyderm.io/tags/Windows3" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows3</a> beat <a href="https://hachyderm.io/tags/OS2" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS2</a> because <a href="https://hachyderm.io/tags/IBM" class="mention hashtag" rel="nofollow noopener" target="_blank">#IBM</a> insisted that OS/2 ran on #80286, which crippled the new <a href="https://hachyderm.io/tags/OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS</a>. IBM's determination to serve its customers with 80286 PS/2s, and keep a promise, resulted in OS/2 being a failure. That is what allowed <a href="https://hachyderm.io/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> <a href="https://hachyderm.io/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> to gain the upper hand. Soon after Windows 3.0 turned out to be a hit, OS/2 NT was rebranded as <a href="https://hachyderm.io/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a>. Even ardent Linux enthusiasts must concede Windows NT did quite well. <a href="https://go.theregister.com/feed/www.theregister.com/2025/01/05/microsoft_os2_flop_future/" rel="nofollow noopener" translate="no" target="_blank">https://go.theregister.com/feed/www.theregister.com/2025/01/05/microsoft_os2_flop_future/</a>

Ramin HonaryWeird question about Microsoft ExcelSo I have been wanting to learn more about how to use Microsoft Excel so I can teach other people about some of the more advanced programming techniques (EDIT: 1-on-1 lessons on their own computer with their own licensed copies of Excel). I want to teach myself more about Excel so I was going to install it on my own computer and do some advanced tutorials. But then I really do not want to burn up all of that disk space just to run Wine and Excel.So I got to thinking:<ol><li>is there an older version of Microsoft Excel I could use instead?</li><li>The “ribbon” UI/UX asside, how far back in time (in Excel software versions) would I have to go before the formula language and cell computation engine became too different from the most recent Excel that it would not be very useful for me as a learning/teaching tool?</li><li>Would it take less disk space to run this in a minimal Windows NT 2000 or Windows XP instance on QEMU than it would take on Wine?</li></ol><a class="hashtag" href="https://fe.disroot.org/tag/excel" rel="nofollow noopener" target="_blank">#Excel</a> <a class="hashtag" href="https://fe.disroot.org/tag/microsoftexcel" rel="nofollow noopener" target="_blank">#MicrosoftExcel</a> <a class="hashtag" href="https://fe.disroot.org/tag/msexcel" rel="nofollow noopener" target="_blank">#MSExcel</a> <a class="hashtag" href="https://fe.disroot.org/tag/spreadsheet" rel="nofollow noopener" target="_blank">#Spreadsheet</a> <a class="hashtag" href="https://fe.disroot.org/tag/software" rel="nofollow noopener" target="_blank">#software</a> <a class="hashtag" href="https://fe.disroot.org/tag/tech" rel="nofollow noopener" target="_blank">#tech</a> <a class="hashtag" href="https://fe.disroot.org/tag/linux" rel="nofollow noopener" target="_blank">#Linux</a> <a class="hashtag" href="https://fe.disroot.org/tag/linuxwine" rel="nofollow noopener" target="_blank">#LinuxWine</a> <a class="hashtag" href="https://fe.disroot.org/tag/qemu" rel="nofollow noopener" target="_blank">#QEMU</a> <a class="hashtag" href="https://fe.disroot.org/tag/emulation" rel="nofollow noopener" target="_blank">#Emulation</a> <a class="hashtag" href="https://fe.disroot.org/tag/windowsxp" rel="nofollow noopener" target="_blank">#WindowsXP</a> <a class="hashtag" href="https://fe.disroot.org/tag/windowsnt" rel="nofollow noopener" target="_blank">#WindowsNT</a> <a class="hashtag" href="https://fe.disroot.org/tag/retrocomputing" rel="nofollow noopener" target="_blank">#RetroComputing</a>

JdeBP<a href="https://digipres.club/@foone" class="u-url mention" rel="nofollow noopener" target="_blank">@foone</a> <a href="https://wandering.shop/@cstross" class="u-url mention" rel="nofollow noopener" target="_blank">@cstross</a> And *your* kernel already had a proper access control system that prevents unprivileged processes from overwriting disc volumes directly. (-:<a href="https://mastodonapp.uk/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a>

Mark Gardner<a href="https://liberdon.com/@kpeace" class="u-url mention" rel="nofollow noopener" target="_blank">@kpeace</a> Kinda.If you’re talking about current <a href="https://social.sdf.org/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> and its NT heritage, it was bought *engineering*, specifically <a href="https://social.sdf.org/tags/DEC" class="mention hashtag" rel="nofollow noopener" target="_blank">#DEC</a> developers led by Dave Cutler.Therefore, many elements of <a href="https://social.sdf.org/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a>’s design were inspired by DEC’s <a href="https://social.sdf.org/tags/VMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VMS</a>, <a href="https://social.sdf.org/tags/VAXELN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VAXELN</a>, <a href="https://social.sdf.org/tags/RSX11" class="mention hashtag" rel="nofollow noopener" target="_blank">#RSX11</a>, and (unreleased) <a href="https://social.sdf.org/tags/MICA" class="mention hashtag" rel="nofollow noopener" target="_blank">#MICA</a> operating systems.<a href="https://social.sdf.org/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> eventually paid off DEC and supported NT on the latter’s <a href="https://social.sdf.org/tags/Alpha" class="mention hashtag" rel="nofollow noopener" target="_blank">#Alpha</a> architecture machines rather than face a lawsuit.

JdeBP<a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@GossiTheDog</a> It's an idea that superficially sounds good, but in practice it has a whole shedload of implementation problems that make it unfeasible as it stands. A précis of just a few:1. Drivers for writable persistent storage might not have been loaded yet. 2. Your driver might be part of the writable persistent storage stack. 3. You really don't want to be writing to a corrupted filesystem before AUTOCHK. 4. File access has to be at PASSIVE_LEVEL.<a href="https://mastodonapp.uk/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> <a href="https://mastodonapp.uk/tags/DeviceDrivers" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeviceDrivers</a>

Apple Product CollectionWhere can we find PowerPC software for Windows NT?Perhaps there’s another handsome black laptop we can look to for inspiration…(The IBM ThinkPad 800 series was an obscure line of PowerPC-based ThinkPads from the late 90s) <a href="https://bitbang.social/tags/windowsnt" class="mention hashtag" rel="nofollow noopener" target="_blank">#windowsnt</a> <a href="https://bitbang.social/tags/powerpc" class="mention hashtag" rel="nofollow noopener" target="_blank">#powerpc</a>

Apple Product CollectionWindows NT for PowerPC boots!<a href="https://bitbang.social/tags/windowsnt" class="mention hashtag" rel="nofollow noopener" target="_blank">#windowsnt</a> <a href="https://bitbang.social/tags/powerpc" class="mention hashtag" rel="nofollow noopener" target="_blank">#powerpc</a>

Apple Product CollectionCopying files!<a href="https://bitbang.social/tags/windowsnt" class="mention hashtag" rel="nofollow noopener" target="_blank">#windowsnt</a> <a href="https://bitbang.social/tags/powerpc" class="mention hashtag" rel="nofollow noopener" target="_blank">#powerpc</a>

Apple Product CollectionAlright, I’ll bite.<a href="https://bitbang.social/tags/windowsnt" class="mention hashtag" rel="nofollow noopener" target="_blank">#windowsnt</a> <a href="https://bitbang.social/tags/powerpc" class="mention hashtag" rel="nofollow noopener" target="_blank">#powerpc</a>

Mark GardnerRemembering when <a href="https://social.sdf.org/tags/ByteMagazine" class="mention hashtag" rel="nofollow noopener" target="_blank">#ByteMagazine</a> carried water for <a href="https://social.sdf.org/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a>'s 1990s FUD: <a href="https://archive.org/details/byte-magazine-1992-09" rel="nofollow noopener" translate="no" target="_blank">https://archive.org/details/byte-magazine-1992-09</a>These days the <a href="https://social.sdf.org/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a>-derived <a href="https://social.sdf.org/tags/Darwin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Darwin</a> powering <a href="https://social.sdf.org/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a>'s operating systems has about the same installed base as <a href="https://social.sdf.org/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>. Adding the de facto Unix <a href="https://social.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> and derivatives like <a href="https://social.sdf.org/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> easily eclipses Microsoft's efforts several times over.<a href="https://social.sdf.org/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> <a href="https://social.sdf.org/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> <a href="https://social.sdf.org/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#RetroComputing</a>

Recent searches

Search options

Administered by:

Server stats:

#windowsnt