9 ms·
One Dog vs. the Windows 3.1 Graphics Stack
- drooopy 2y agoThat title was... slightly confusing. That said, I will always feel a sense of awe when I read about how those old, DOS-based versions of Windows worked behind the scenes. Everything is held together by software duct tape, yet somehow it works.
- immibis 2y agoGo listen to Casey Muratori talk. We've created a giant pile of abstractions but we don't actually need them and all they is make performance worse.
- bmicraft 2y agoNow I'm interested, which talk do you mean? Edit: I might have read that wrong, but I'm interested in specific recommendations nonetheless.
- codetrotter 2y agoSee for example this playlist of videos of his with some videos from 2021 where he implements a terminal emulator. As he says himself, this project is not so much about terminals as it is about software development practices in general. https://youtube.com/playlist?list=PLEMXAbCVnmY6zCgpCFlgggRkrp0tpWfrn https://youtube.com/playlist?list=PLEMXAbCVnmY6zCgpCFlgggRkr... See also this video of his: “Clean” Code, Horrible Performance https://youtu.be/tD5NrevFtbU https://youtu.be/tD5NrevFtbU
- pjmlp 2y agoWe would already be much better if folks actually bother to learn a bit about data structures, algorithms, and not shipping Electron garbage. Abstractions aren't the problem, rather how they are used nowadays, by plenty of folks that only went through JavaScript bootcamps. To note they aren't at fault, rather those that teach on those factories.
- jsheard 2y ago> That title was... slightly confusing. There's nothing in the rules that says a dog can't use Ghidra.
- donatj 2y agoI was expecting something about the dog from Microsoft Bob, like a war story from an MS veteran about making the characters work on Windows 3.1
- KMnO4 2y agoAlright; I’ll bite. Where’s the dog? I’m still confused.
- amenhotep 2y agoThe author is a furry, and the dog being referred to is himself (Do other kink subcultures do this stuff??)
- Kye 2y agoIt's not a kink subculture. There are kink subcultures within it, but the only common factor among all the subcultures inside it is an appreciation for anthropomorphism.
- qdot76367 2y agoHi fox.
- wolfgang42 2y agoFurries do tend to be more open about kink (as part of the community’s general culture of acceptance), but to describe furry as a “kink subculture” is misleadingly reductive at best.
- indrora 2y agoLess kink and more “if you’re on the internet why NOT pretend to be a walking talking dog?” See also, VTubers, manga artists (who often represent themselves as characters), and our tendency to anthropomorphize computers (“it’s gotta think”)
- userbinator 2y agoIt reminded me of the old comic with the phrase "on the Internet, nobody knows you're a dog".
- vzqx 2y agoThe author has a fursona, so I think the author himself is the dog.
- throw930404 2y ago[flagged]
- ComputerGuru 2y agoSVGA support aside, it will never cease to astound me that you can load Windows 3.x on a modern standards-supporting PC and get basic VGA working out-of-the-box but you cannot do the same on modern Linux/BSD to get a basic software-accelerated VGA framebuffer supported by Xorg/Wayland if you don't have the right drivers installed (and the correct configuration files manually set up). (the dead xfree86 project was probably the closest attempt to making this "just work" though it had a long way to go; this approach was not preserved in the Xorg fork)
- kevin_thibedeau 2y agoXorg is Xfree86 with a cleaned up build system.
- immibis 2y agoIt's specialization. Windows 3.x runs with a GUI on an IBM PC. XFree86-era Linux runs with any UI on an IBM PC. Xorg-era Linux runs with any UI on any computer. Therefore you have to specify what kind of configuration you require, and don't get it out of the box. But note that every distribution that runs on IBM PCs with a VGA GUI does come with that configuration out of the box, because they are re-specialized for that system. And Wayland requires a GPU as far as I know, since the entire protocol is based on passing GPU memory buffers around and compositing then. Deleting the backwards compatibility for software rendering was half the point of creating Wayland.
- shakna 2y ago> it can't even run most up-to-date Linux distros due to its lack of x86_64 support My Eee is successfully chugging along with 32bit Debian. Firefox is too heavyweight to do much but lag, but mpv works well enough to stream video. But I mostly use it when I'm running behind on a book and basically need a typewriter that can run pandoc, and fewer distractions.
- cout 2y agoI totally agree on having a computer with minimum distractions when writing -- for that I use a PS/2 386SX running WordPerfect 5.1. I loved my EEE, super portable, but the keyboard is too small for serious typing IMO.
- pavlov 2y agoIs that a PS/2 55SX? That was the computer I had between ages 9 and 14. I wish I had one now.
- cout 2y agoNo, it's a PS/2 50Z, which comes with a 10MHz 286. It was my first computer, second hand from my dad. When I got it, I saved up and bought the 386SX/Now!, a 25Mhz 386SX that fits into a 286 slot.
- darkwater 2y agoOh, I had that too, just never upgraded the CPU. Selling it in 1996 for a few bucks was probably the worst mistake I did in my computer life. The second worst error was also getting rid of my Asus EEE also featured in the OP.
- cout 2y ago> Selling it in 1996 for a few bucks was probably the worst mistake I did in my computer life. Why do you say that? They are great machines (mine has lasted forever) but finding parts was hard even when they were new due to the microchannel architecture.
- 101008 2y agoUnrelated to the actual article, but so refreshing seeing a website with a design/structure that reminded me of the best years of internet. How I miss left sidebars, tables and more!
- devops99 2y ago[dead]
- a1o 2y agoThat is fun, I have an EEEPC 207g, those smaller ones. It still works, but I never thought about retro gaming with it - mine is just "collecting dust", it would be fun to try these things on it!
- nosrepa 2y agoYou mean the 701? 207g isn't a model of eeepc.
- a1o 2y agoIt may be a 701, but I need to find which box it's in to actually check. It has a 7 inch screen, it's old but still holds charge in the battery for 2h at least, has a long charging cable, my only "mod" was to upgrade the RAM to 2GB, and it has a 4GB SSD I think - I have a card in it with 16GB and it runs a never updated version of crunchbang that was installed I really don't remember when - it doesn't go online ever, so it's fine. The last thing I did in it was to replay Illusion of Gaia using an emulator.
- copper_think 2y agoThe author mentions the screen being corrupted when a DOS prompt is opened in windowed mode. This can happen because the DOS prompt runs in a separate VM (in V86 mode), and makes calls into the VGA ROM BIOS via INT 10h. The VGA ROM BIOS on this machine is probably a wrapper over VBE; that is, it probably contains IN and OUT instructions that talk to the VBE I/O ports, 0x1CE and 0x1CF. These reads and writes from the DOS VM will, by default, be allowed to reach the physical hardware if they are not virtualized by the VMM. This is a common problem that authors of Windows 3.x/9x display drivers had to handle, although the specific I/O port numbers to be virtualized vary by graphics adapter. There are samples in the Win95 DDK that show how to use the VMM services Install_IO_Handler and Enable/Disable_Global_Trapping to set up I/O port traps, and VDD_Get_VM_Info from within the trap handler to determine the VM that currently owns the CRTC. This allows the trap handler to reach a decision about whether to allow an I/O to reach the hardware, or to virtualize the access in some way. A good virtualization policy to start with is probably just to drop any writes from non-CRTC-owner VMs. Any additional needed complexity can be added from there.
- NikkiA 2y agoI remember when the ET4000H came out and it was not supported by Windows 3.1 at the time, I had to call MS tech support and they sent me a driver disk that arrived 8 hours later. Best support I've ever had for a pirated product.
- NikkiA 2y agoTo clarify... the ET4000H was the same ET4000ax that was supported by Windows 3.0 and 3.1 already, but with the HiDAC (15/16bit truecolour) fitted instead of the 256 colour DAC. My recollection is fuzzy, but ISTR that it worked with the default driver in 16 colour mode, but not 256 or better, resolution selection may have been limited too. MS claims that the driver that supported HiDAC came out the 3rd week of April 1992, which would have been 1-2 weeks after the time period I'm remembering, so it sounds about right.
- metadat 2y agoThat old Windows 3.1 GUI looks so much more intuitive, efficient, and usable compared to what we've got today. https://wuffs.org/user/pages/02.blog/windows-3x-graphics/640x480.jpg https://wuffs.org/user/pages/02.blog/windows-3x-graphics/640... What would Win11 even look like on a lower-resolution display such as in TFA? The Win11 Start Menu is borderline unusable beyond typing in a keyword and praying to the circuits. What happened? Naive hypothesis: Windows NT and 2k hit a sweet spot, then product managers have been working their magic ever since. KDE and Gnome are looking more and more appealing over time, despite not changing much. :)
- XorNot 2y agoFlat design has been an absolute pox on the industry. Skeumorphism was also pretty bad (since it was basically just flat design with pictures). Windows Forms got a lot right: I think the one missing symbol was "active but not editable".
- Dwedit 2y agoBlinking cursor in textbox with gray background? That would be one case of "active and not editable".
- Dalewyn 2y agoIn Windows, the text cursor no longer blinks (more accurately it stops blinking after a few seconds, becoming static) in the interests of battery saving. At least I think it was battery saving, been months since I read it and my memory is foggy because it's fucking stupid. Even on desktops that don't have batteries.
- XorNot 2y agoThe problem is grey usually means "disabled" which also implies that data may be stale. As it is you can set a text box read only but active, but it does waste time since it doesn't code that it's not interactable visually (i.e. you have to make up a scheme). Basically it would've been nice to have a consistent background color or other visual cue which says "this will update, this is live, but you can't type here".
- exikyut 2y agoIdly comparing the silly little annotations, I notice the following state changes you've probably also stared at to the point of semantic satiation... Functional GUI: M_LIN8 G800x600 > 800x600 @00000+100+Dch4 Functional DOS: M_TEXT T80x25 > 720x400 @00000+050-W Broken GUI: M_VGA G400x600 > 400x600 @00000+200-Dch4 Broken DOS: M_TEXT T80x25 > 720x400 @00000+250-W Pattern analysis: - Broken DOS and Broken GUI are 200 or 250, functional are 100 or 050. What's that address? - Broken GUI is somehow in M_VGA mode instead of LIN8. How and why did it get like that, and is that related to why it somehow got into 400x600, horizontally half of 800x600 (??). (True "textmode" is actually 720x400, as seen in both DOS modes.)
- userbinator 2y agoThe Virtual Display Device (VDD) runs as part of the underlying virtual machine manager, and acts somewhat like a multiplexer for the video hardware. If a DOS app is full screen, its commands are directly sent to the ‘real’ VGA adapter; otherwise, they’re emulated by the VDD. It's interesting to see others (re)discover this architecture, which IMHO was quite ahead of its time, since it predates modern hypervisors with hardware pass-through. The Windows 3.x GUI itself, including its preemptively-multitasked processes, effectively runs as an extended (protected-mode) DOS process inside a VM running DOS, and the hypervisor kernel, VMM32, is what multiplexes between it and other VMs running DOS processes. Thus one part of the display driver sits under GDI and interacts with the "hardware", while the other part in ring 0 virtualises the hardware and multiplexes it with the other VMs. This would fix it for DOSBox, but that fix would be tied to whichever video adapter it's emulating. I don't want that, I'm trying to make the generic VBE patch work better! Having written a Win9x VESA framebuffer driver for the Intel GMA950 as well, and added basic acceleration (blitter and fill commands), and encountering basically the same issue, I realised what may be the reason Win9x never came with a generic VESA driver: the VDD needs to know how to save and restore the GPU state, the details of which are obviously vendor-dependent. I did come up with some ideas on how that could be done generically, i.e. emulate/trace the VBIOS and see which ports/MMIOs it touches on each mode switch, but never got around to implementing it. While on DOSBox I get text mode with lots of corrupted characters, on the Eee PC I get a broken version of the GUI where some of the colours have disappeared. That looks like the palette registers didn't get saved and restored correctly. Also, the corruption at the top of the screen can be avoided by moving the high-res display plane up by 256K, so as to leave the first 256K of VRAM for the VGA plane and VGA emulation. Fortunately the Intel GMA has a bunch of publicly available documentation (although not for the 900 nor 950, and only for the 810/815 and 965+ but the majority of the registers and commands have not changed) you can refer to for the details.
- roytam87 2y agodon't know if article's author is watching this, but I told patch's author about this article. https://www.bttr-software.de/forum/board_entry.php?id=22124#p22230 https://www.bttr-software.de/forum/board_entry.php?id=22124#...