#windowsnt4 — Public Fediverse posts

🚀🚀 Because everyone in 2025 is just itching to relive the '90s misery of Windows NT 4 on #Proxmox, right? 🙄💾 Next up: a riveting guide on how to install #AOL on your #Tesla for that retro dial-up experience. 📡🛠️
https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/ #WindowsNT4 #RetroTech #HackerNews #ngated

🚀🚀 Because everyone in 2025 is just itching to relive the '90s misery of Windows NT 4 on #Proxmox, right? 🙄💾 Next up: a riveting guide on how to install #AOL on your #Tesla for that retro dial-up experience. 📡🛠️
https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/ #WindowsNT4 #RetroTech #HackerNews #ngated

🚀🚀 Because everyone in 2025 is just itching to relive the '90s misery of Windows NT 4 on #Proxmox, right? 🙄💾 Next up: a riveting guide on how to install #AOL on your #Tesla for that retro dial-up experience. 📡🛠️
https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/ #WindowsNT4 #RetroTech #HackerNews #ngated

🚀🚀 Because everyone in 2025 is just itching to relive the '90s misery of Windows NT 4 on #Proxmox, right? 🙄💾 Next up: a riveting guide on how to install #AOL on your #Tesla for that retro dial-up experience. 📡🛠️
https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/ #WindowsNT4 #RetroTech #HackerNews #ngated

🚀🚀 Because everyone in 2025 is just itching to relive the '90s misery of Windows NT 4 on #Proxmox, right? 🙄💾 Next up: a riveting guide on how to install #AOL on your #Tesla for that retro dial-up experience. 📡🛠️
https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/ #WindowsNT4 #RetroTech #HackerNews #ngated

How to Install Windows NT 4 Server on Proxmox

https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/

#HackerNews #WindowsNT4 #Proxmox #ServerInstallation #TechTutorial #Virtualization

How to Install Windows NT 4 Server on Proxmox

https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/

#HackerNews #WindowsNT4 #Proxmox #ServerInstallation #TechTutorial #Virtualization

How to Install Windows NT 4 Server on Proxmox

https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/

#HackerNews #WindowsNT4 #Proxmox #ServerInstallation #TechTutorial #Virtualization

How to Install Windows NT 4 Server on Proxmox

https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/

#HackerNews #WindowsNT4 #Proxmox #ServerInstallation #TechTutorial #Virtualization

How to Install Windows NT 4 Server on Proxmox

https://blog.pipetogrep.org/2025/05/23/how-to-install-windows-nt-4-server-on-proxmox/

#HackerNews #WindowsNT4 #Proxmox #ServerInstallation #TechTutorial #Virtualization

I got the three RedHat Linux 2.1 floppies written using #RawWrite #rawrite on #WindowsNT4 on the 1996 #IBM #Thinkpad, but the first ramdisk floppy was bad. I'm using a stock of floppies individually sealed in plastic since 1998. Taking a fresh one, I formatted it to (waves hands) refresh the magnetic material and was able to write a valid image and confirm it was correct using an md5sum binary I found at https://www.pc-tools.net/win32/md5sums/

I got the three RedHat Linux 2.1 floppies written using #RawWrite #rawrite on #WindowsNT4 on the 1996 #IBM #Thinkpad, but the first ramdisk floppy was bad. I'm using a stock of floppies individually sealed in plastic since 1998. Taking a fresh one, I formatted it to (waves hands) refresh the magnetic material and was able to write a valid image and confirm it was correct using an md5sum binary I found at https://www.pc-tools.net/win32/md5sums/

I got the three RedHat Linux 2.1 floppies written using #RawWrite #rawrite on #WindowsNT4 on the 1996 #IBM #Thinkpad, but the first ramdisk floppy was bad. I'm using a stock of floppies individually sealed in plastic since 1998. Taking a fresh one, I formatted it to (waves hands) refresh the magnetic material and was able to write a valid image and confirm it was correct using an md5sum binary I found at https://www.pc-tools.net/win32/md5sums/

I got the three RedHat Linux 2.1 floppies written using #RawWrite #rawrite on #WindowsNT4 on the 1996 #IBM #Thinkpad, but the first ramdisk floppy was bad. I'm using a stock of floppies individually sealed in plastic since 1998. Taking a fresh one, I formatted it to (waves hands) refresh the magnetic material and was able to write a valid image and confirm it was correct using an md5sum binary I found at https://www.pc-tools.net/win32/md5sums/

Auto Filename Completion in #WindowsNT4

> Most of us developers who are used to bash under Linux or other powerful shells are also used to the immensely helpful feature there of filename completion: if you press TAB after typing in a part of a filename, the shell will complete it for you. Moreover, if you press TAB again and again, the shell will cycle through all the file names that match the partial name. Sadly, this feature is lacking (or so it seems) in the Command Prompt shown by Windows NT.
>
> Not really! Now you can enable this feature in NT by doing the following: open regedit and look for the key `HKEY_CURRENT_USER\Software\Microsoft\Command Processor`, look for the value named `CompletionChar` and change its value to `9` (ASCII code for the TAB character), and you're done! That's all there is to it.

http://rmathew.com/articles/wnt.html#autocomplete

Auto Filename Completion in #WindowsNT4

> Most of us developers who are used to bash under Linux or other powerful shells are also used to the immensely helpful feature there of filename completion: if you press TAB after typing in a part of a filename, the shell will complete it for you. Moreover, if you press TAB again and again, the shell will cycle through all the file names that match the partial name. Sadly, this feature is lacking (or so it seems) in the Command Prompt shown by Windows NT.
>
> Not really! Now you can enable this feature in NT by doing the following: open regedit and look for the key `HKEY_CURRENT_USER\Software\Microsoft\Command Processor`, look for the value named `CompletionChar` and change its value to `9` (ASCII code for the TAB character), and you're done! That's all there is to it.

http://rmathew.com/articles/wnt.html#autocomplete

Auto Filename Completion in #WindowsNT4

> Most of us developers who are used to bash under Linux or other powerful shells are also used to the immensely helpful feature there of filename completion: if you press TAB after typing in a part of a filename, the shell will complete it for you. Moreover, if you press TAB again and again, the shell will cycle through all the file names that match the partial name. Sadly, this feature is lacking (or so it seems) in the Command Prompt shown by Windows NT.
>
> Not really! Now you can enable this feature in NT by doing the following: open regedit and look for the key `HKEY_CURRENT_USER\Software\Microsoft\Command Processor`, look for the value named `CompletionChar` and change its value to `9` (ASCII code for the TAB character), and you're done! That's all there is to it.

http://rmathew.com/articles/wnt.html#autocomplete

Auto Filename Completion in #WindowsNT4

> Most of us developers who are used to bash under Linux or other powerful shells are also used to the immensely helpful feature there of filename completion: if you press TAB after typing in a part of a filename, the shell will complete it for you. Moreover, if you press TAB again and again, the shell will cycle through all the file names that match the partial name. Sadly, this feature is lacking (or so it seems) in the Command Prompt shown by Windows NT.
>
> Not really! Now you can enable this feature in NT by doing the following: open regedit and look for the key `HKEY_CURRENT_USER\Software\Microsoft\Command Processor`, look for the value named `CompletionChar` and change its value to `9` (ASCII code for the TAB character), and you're done! That's all there is to it.

http://rmathew.com/articles/wnt.html#autocomplete

Auto Filename Completion in #WindowsNT4

> Most of us developers who are used to bash under Linux or other powerful shells are also used to the immensely helpful feature there of filename completion: if you press TAB after typing in a part of a filename, the shell will complete it for you. Moreover, if you press TAB again and again, the shell will cycle through all the file names that match the partial name. Sadly, this feature is lacking (or so it seems) in the Command Prompt shown by Windows NT.
>
> Not really! Now you can enable this feature in NT by doing the following: open regedit and look for the key `HKEY_CURRENT_USER\Software\Microsoft\Command Processor`, look for the value named `CompletionChar` and change its value to `9` (ASCII code for the TAB character), and you're done! That's all there is to it.

http://rmathew.com/articles/wnt.html#autocomplete

I finally got a #CompactFlash to #IDE adapter working in my gorgeous and rugged #IBM #Thinkpad760CD from 1996! The IDE disk continues to work beautifully, but using CF gives me more options to quickly switch operating systems.

I'd ddrescued the IDE disk at various points along the way as I experimented with #MSDOS622, #Windows98 and finally most recently and most successfully, #WindowsNT4.

I wrote those images to CF cards but bloody hell I dunno how many times I faced the dreaded error 174 early in POST (which indicates "no hard disk detected") while trying out different Compact Flash cards and adapters.

I finally hit on the right combination today, quite by accident, as I probably moved a jumper on one of the adapters that had failed for me before. This after very close reading of the Thinkpad Legacy Hardware forum on https://forum.thinkpads.com/

This CF card is a little bit faster than the original disk; I'd just picked the first 2GB one I found in my collection. I have benchmarked all of them so the next OS will go on the fastest one I can find. Probably an ancient Linux or IBM OS/2 Warp 4.

It's hard to describe the satisfaction of getting old kit like this working again! #retrocomputing

I finally got a #CompactFlash to #IDE adapter working in my gorgeous and rugged #IBM #Thinkpad760CD from 1996! The IDE disk continues to work beautifully, but using CF gives me more options to quickly switch operating systems.

I'd ddrescued the IDE disk at various points along the way as I experimented with #MSDOS622, #Windows98 and finally most recently and most successfully, #WindowsNT4.

I wrote those images to CF cards but bloody hell I dunno how many times I faced the dreaded error 174 early in POST (which indicates "no hard disk detected") while trying out different Compact Flash cards and adapters.

I finally hit on the right combination today, quite by accident, as I probably moved a jumper on one of the adapters that had failed for me before. This after very close reading of the Thinkpad Legacy Hardware forum on https://forum.thinkpads.com/

This CF card is a little bit faster than the original disk; I'd just picked the first 2GB one I found in my collection. I have benchmarked all of them so the next OS will go on the fastest one I can find. Probably an ancient Linux or IBM OS/2 Warp 4.

It's hard to describe the satisfaction of getting old kit like this working again! #retrocomputing

I finally got a #CompactFlash to #IDE adapter working in my gorgeous and rugged #IBM #Thinkpad760CD from 1996! The IDE disk continues to work beautifully, but using CF gives me more options to quickly switch operating systems.

I'd ddrescued the IDE disk at various points along the way as I experimented with #MSDOS622, #Windows98 and finally most recently and most successfully, #WindowsNT4.

I wrote those images to CF cards but bloody hell I dunno how many times I faced the dreaded error 174 early in POST (which indicates "no hard disk detected") while trying out different Compact Flash cards and adapters.

I finally hit on the right combination today, quite by accident, as I probably moved a jumper on one of the adapters that had failed for me before. This after very close reading of the Thinkpad Legacy Hardware forum on https://forum.thinkpads.com/

This CF card is a little bit faster than the original disk; I'd just picked the first 2GB one I found in my collection. I have benchmarked all of them so the next OS will go on the fastest one I can find. Probably an ancient Linux or IBM OS/2 Warp 4.

It's hard to describe the satisfaction of getting old kit like this working again! #retrocomputing

I finally got a #CompactFlash to #IDE adapter working in my gorgeous and rugged #IBM #Thinkpad760CD from 1996! The IDE disk continues to work beautifully, but using CF gives me more options to quickly switch operating systems.

I'd ddrescued the IDE disk at various points along the way as I experimented with #MSDOS622, #Windows98 and finally most recently and most successfully, #WindowsNT4.

I wrote those images to CF cards but bloody hell I dunno how many times I faced the dreaded error 174 early in POST (which indicates "no hard disk detected") while trying out different Compact Flash cards and adapters.

I finally hit on the right combination today, quite by accident, as I probably moved a jumper on one of the adapters that had failed for me before. This after very close reading of the Thinkpad Legacy Hardware forum on https://forum.thinkpads.com/

This CF card is a little bit faster than the original disk; I'd just picked the first 2GB one I found in my collection. I have benchmarked all of them so the next OS will go on the fastest one I can find. Probably an ancient Linux or IBM OS/2 Warp 4.

It's hard to describe the satisfaction of getting old kit like this working again! #retrocomputing

I finally got a #CompactFlash to #IDE adapter working in my gorgeous and rugged #IBM #Thinkpad760CD from 1996! The IDE disk continues to work beautifully, but using CF gives me more options to quickly switch operating systems.

I'd ddrescued the IDE disk at various points along the way as I experimented with #MSDOS622, #Windows98 and finally most recently and most successfully, #WindowsNT4.

I wrote those images to CF cards but bloody hell I dunno how many times I faced the dreaded error 174 early in POST (which indicates "no hard disk detected") while trying out different Compact Flash cards and adapters.

I finally hit on the right combination today, quite by accident, as I probably moved a jumper on one of the adapters that had failed for me before. This after very close reading of the Thinkpad Legacy Hardware forum on https://forum.thinkpads.com/

This CF card is a little bit faster than the original disk; I'd just picked the first 2GB one I found in my collection. I have benchmarked all of them so the next OS will go on the fastest one I can find. Probably an ancient Linux or IBM OS/2 Warp 4.

It's hard to describe the satisfaction of getting old kit like this working again! #retrocomputing

A couple of screenshots made on my #IBM #Thinkpad760CD, one contrasting the #WindowsNT4 system properties dialog with the output of neofetch from my daily-driver desktop that's already a few years old (running in the latest puTTY, built for ancient 32-bit Windows); the other screenshot shows a Wikipedia page rendered perfectly in #InternetExplorer2, thanks to wrp, the Web Rendering Proxy. (The latter has its limitations; it's not possible to enter text, or download files. It's perfect for navigating and reading, though, and quick enough. The server running wrp is a tiny HP machine from 2011!)

#retrocomputing #vintageComputing #

A couple of screenshots made on my #IBM #Thinkpad760CD, one contrasting the #WindowsNT4 system properties dialog with the output of neofetch from my daily-driver desktop that's already a few years old (running in the latest puTTY, built for ancient 32-bit Windows); the other screenshot shows a Wikipedia page rendered perfectly in #InternetExplorer2, thanks to wrp, the Web Rendering Proxy. (The latter has its limitations; it's not possible to enter text, or download files. It's perfect for navigating and reading, though, and quick enough. The server running wrp is a tiny HP machine from 2011!)

#retrocomputing #vintageComputing #

A couple of screenshots made on my #IBM #Thinkpad760CD, one contrasting the #WindowsNT4 system properties dialog with the output of neofetch from my daily-driver desktop that's already a few years old (running in the latest puTTY, built for ancient 32-bit Windows); the other screenshot shows a Wikipedia page rendered perfectly in #InternetExplorer2, thanks to wrp, the Web Rendering Proxy. (The latter has its limitations; it's not possible to enter text, or download files. It's perfect for navigating and reading, though, and quick enough. The server running wrp is a tiny HP machine from 2011!)

#retrocomputing #vintageComputing #

A couple of screenshots made on my #IBM #Thinkpad760CD, one contrasting the #WindowsNT4 system properties dialog with the output of neofetch from my daily-driver desktop that's already a few years old (running in the latest puTTY, built for ancient 32-bit Windows); the other screenshot shows a Wikipedia page rendered perfectly in #InternetExplorer2, thanks to wrp, the Web Rendering Proxy. (The latter has its limitations; it's not possible to enter text, or download files. It's perfect for navigating and reading, though, and quick enough. The server running wrp is a tiny HP machine from 2011!)

#retrocomputing #vintageComputing #

I'm really getting much more of a chuckle from the puzzles thrown up by trying to use a #VintagePC on a modern network than I ever expected!

Modern #puTTY binaries won't run on #WindowsNT4; ancient binaries from January 2000 are available and will run, but can't connect to a modern #SSH server. Most effective for file transfer is a combination of #telnet specially installed on my daily driver #Linux machine and python3 -m http.server.

Netscape 4.7 works nicely with the Python HTTP server, and the telnet client that comes with Windows NT4 supports VT100 so on opening a shell on my Linux machine, I find the w3m command line web browser is just about usable - good enough to download ancient binaries and installers onto the Linux machine that can be served via Python's HTTP server.

I've also given #wrp, the Web Rendering Proxy, a spin; it's surprisingly effective. Runs on a Linux machine on the network and serves pages as GIFs with clickable image maps.

https://github.com/tenox7/wrp

I'm really getting much more of a chuckle from the puzzles thrown up by trying to use a #VintagePC on a modern network than I ever expected!

Modern #puTTY binaries won't run on #WindowsNT4; ancient binaries from January 2000 are available and will run, but can't connect to a modern #SSH server. Most effective for file transfer is a combination of #telnet specially installed on my daily driver #Linux machine and python3 -m http.server.

Netscape 4.7 works nicely with the Python HTTP server, and the telnet client that comes with Windows NT4 supports VT100 so on opening a shell on my Linux machine, I find the w3m command line web browser is just about usable - good enough to download ancient binaries and installers onto the Linux machine that can be served via Python's HTTP server.

I've also given #wrp, the Web Rendering Proxy, a spin; it's surprisingly effective. Runs on a Linux machine on the network and serves pages as GIFs with clickable image maps.

https://github.com/tenox7/wrp

I'm really getting much more of a chuckle from the puzzles thrown up by trying to use a #VintagePC on a modern network than I ever expected!

Modern #puTTY binaries won't run on #WindowsNT4; ancient binaries from January 2000 are available and will run, but can't connect to a modern #SSH server. Most effective for file transfer is a combination of #telnet specially installed on my daily driver #Linux machine and python3 -m http.server.

Netscape 4.7 works nicely with the Python HTTP server, and the telnet client that comes with Windows NT4 supports VT100 so on opening a shell on my Linux machine, I find the w3m command line web browser is just about usable - good enough to download ancient binaries and installers onto the Linux machine that can be served via Python's HTTP server.

I've also given #wrp, the Web Rendering Proxy, a spin; it's surprisingly effective. Runs on a Linux machine on the network and serves pages as GIFs with clickable image maps.

https://github.com/tenox7/wrp

I'm really getting much more of a chuckle from the puzzles thrown up by trying to use a #VintagePC on a modern network than I ever expected!

Modern #puTTY binaries won't run on #WindowsNT4; ancient binaries from January 2000 are available and will run, but can't connect to a modern #SSH server. Most effective for file transfer is a combination of #telnet specially installed on my daily driver #Linux machine and python3 -m http.server.

Netscape 4.7 works nicely with the Python HTTP server, and the telnet client that comes with Windows NT4 supports VT100 so on opening a shell on my Linux machine, I find the w3m command line web browser is just about usable - good enough to download ancient binaries and installers onto the Linux machine that can be served via Python's HTTP server.

I've also given #wrp, the Web Rendering Proxy, a spin; it's surprisingly effective. Runs on a Linux machine on the network and serves pages as GIFs with clickable image maps.

https://github.com/tenox7/wrp

I'm really getting much more of a chuckle from the puzzles thrown up by trying to use a #VintagePC on a modern network than I ever expected!

Modern #puTTY binaries won't run on #WindowsNT4; ancient binaries from January 2000 are available and will run, but can't connect to a modern #SSH server. Most effective for file transfer is a combination of #telnet specially installed on my daily driver #Linux machine and python3 -m http.server.

Netscape 4.7 works nicely with the Python HTTP server, and the telnet client that comes with Windows NT4 supports VT100 so on opening a shell on my Linux machine, I find the w3m command line web browser is just about usable - good enough to download ancient binaries and installers onto the Linux machine that can be served via Python's HTTP server.

I've also given #wrp, the Web Rendering Proxy, a spin; it's surprisingly effective. Runs on a Linux machine on the network and serves pages as GIFs with clickable image maps.

https://github.com/tenox7/wrp

UA: Я тут бавився з встановленням WindowsNT4 на QEMU і натрапив на цю біду. Тут хтось є, хто стикався зі схожою помилкою в новій версії QEMU? Я не пам'ятаю щоб раніше таке було

EN: I was playing around with installing #WindowsNT4 in #QEMU but I faced this issue. Is there anybody who has faced a similar error with newer version of QEMU? I don't remember there was anything like that

#virtualization #vm #virtualmachine #windows #winnt #retro #retropc #90s #1990s #nostalgia

UA: Я тут бавився з встановленням WindowsNT4 на QEMU і натрапив на цю біду. Тут хтось є, хто стикався зі схожою помилкою в новій версії QEMU? Я не пам'ятаю щоб раніше таке було

EN: I was playing around with installing #WindowsNT4 in #QEMU but I faced this issue. Is there anybody who has faced a similar error with newer version of QEMU? I don't remember there was anything like that

#virtualization #vm #virtualmachine #windows #winnt #retro #retropc #90s #1990s #nostalgia

UA: Я тут бавився з встановленням WindowsNT4 на QEMU і натрапив на цю біду. Тут хтось є, хто стикався зі схожою помилкою в новій версії QEMU? Я не пам'ятаю щоб раніше таке було

EN: I was playing around with installing #WindowsNT4 in #QEMU but I faced this issue. Is there anybody who has faced a similar error with newer version of QEMU? I don't remember there was anything like that

#virtualization #vm #virtualmachine #windows #winnt #retro #retropc #90s #1990s #nostalgia

UA: Я тут бавився з встановленням WindowsNT4 на QEMU і натрапив на цю біду. Тут хтось є, хто стикався зі схожою помилкою в новій версії QEMU? Я не пам'ятаю щоб раніше таке було

EN: I was playing around with installing #WindowsNT4 in #QEMU but I faced this issue. Is there anybody who has faced a similar error with newer version of QEMU? I don't remember there was anything like that

#virtualization #vm #virtualmachine #windows #winnt #retro #retropc #90s #1990s #nostalgia

UA: Я тут бавився з встановленням WindowsNT4 на QEMU і натрапив на цю біду. Тут хтось є, хто стикався зі схожою помилкою в новій версії QEMU? Я не пам'ятаю щоб раніше таке було

EN: I was playing around with installing #WindowsNT4 in #QEMU but I faced this issue. Is there anybody who has faced a similar error with newer version of QEMU? I don't remember there was anything like that

#virtualization #vm #virtualmachine #windows #winnt #retro #retropc #90s #1990s #nostalgia

It was 28 years ago today that Microsoft released Windows NT 4.0 to manufacturing, the last step before retail release. It was the first version of Windows NT to achieve really widespread success. In this blog post, we look at why that was. #windowsnt #windowsnt4 #retropc #retrocomputing https://dfarq.homeip.net/windows-nt-4-0-released-to-manufacturing-july-31-1996/

It was 28 years ago today that Microsoft released Windows NT 4.0 to manufacturing, the last step before retail release. It was the first version of Windows NT to achieve really widespread success. In this blog post, we look at why that was. #windowsnt #windowsnt4 #retropc #retrocomputing https://dfarq.homeip.net/windows-nt-4-0-released-to-manufacturing-july-31-1996/

It was 28 years ago today that Microsoft released Windows NT 4.0 to manufacturing, the last step before retail release. It was the first version of Windows NT to achieve really widespread success. In this blog post, we look at why that was. #windowsnt #windowsnt4 #retropc #retrocomputing https://dfarq.homeip.net/windows-nt-4-0-released-to-manufacturing-july-31-1996/

It was 28 years ago today that Microsoft released Windows NT 4.0 to manufacturing, the last step before retail release. It was the first version of Windows NT to achieve really widespread success. In this blog post, we look at why that was. #windowsnt #windowsnt4 #retropc #retrocomputing https://dfarq.homeip.net/windows-nt-4-0-released-to-manufacturing-july-31-1996/

It was 28 years ago today that Microsoft released Windows NT 4.0 to manufacturing, the last step before retail release. It was the first version of Windows NT to achieve really widespread success. In this blog post, we look at why that was. #windowsnt #windowsnt4 #retropc #retrocomputing https://dfarq.homeip.net/windows-nt-4-0-released-to-manufacturing-july-31-1996/

I cannot believe this is giving me so much pleasure.

#WindowsNT4 #TridentVideo #GraphicsDrivers #RetroComputing

I cannot believe this is giving me so much pleasure.

#WindowsNT4 #TridentVideo #GraphicsDrivers #RetroComputing

I cannot believe this is giving me so much pleasure.

#WindowsNT4 #TridentVideo #GraphicsDrivers #RetroComputing

I cannot believe this is giving me so much pleasure.

#WindowsNT4 #TridentVideo #GraphicsDrivers #RetroComputing

I've just realised that #LibreOffice inherited the names of the applications in its suite directly from #SunMicrosystems #StarOffice.

#RetroComputing #WindowsNT4

I've just realised that #LibreOffice inherited the names of the applications in its suite directly from #SunMicrosystems #StarOffice.

#RetroComputing #WindowsNT4

I've just realised that #LibreOffice inherited the names of the applications in its suite directly from #SunMicrosystems #StarOffice.

#RetroComputing #WindowsNT4