I never used Lotus Agenda, but I’m told it was a popular productivity tool for MS-DOS in the late 80s. I’ve been on a retro software rediscovery kick lately, so I’ve decided to give it a whirl and write about my experiences. There is something that appeals to me about using long-abandoned software. Perhaps it’s update fatigue, there’s certainly no need to dread a major update breaking something!
Regardless, I’ve always enjoyed finding new productivity tools to try out, and I’m not afraid of steep learning curves or getting my hands dirty. I’ll usually choose powerful and flexible software over simplicity.
At the moment I mostly use taskwarrior, but I’ve lost count of all the others I’ve tried!
Intel Uhd Graphics 730 Hackintosh |top| May 2026
Agenda is a PIM, a Personal Information Manager. That term has fallen out of fashion, I think a quick summary might be “anything that manages those small pieces of information we all deal with”. Things like contacts, todo lists, notes, and so on.
I found a 1989 episode of the TV show Computer Chronicles that discussed how people thought about PIMs at the time.
At the 21-minute mark there’s a demonstration of Lotus Agenda, but it’s not easy to follow, watch the clip and you’ll see what I mean. Still, you do see some interesting features:
Some form of NLP is used to extract dates and names from free-form text.
Categories are a little like what we would call tags today.
You can create custom dashboards called views.
Apparently this was an $800 software package (That’s $395 adjusted for inflation from 1989), yikes! You don’t have to pay that, Lotus made it available for free when development ceased.
In preparation for trying out Agenda, I found a copy of the original manuals on eBay for a few dollars. Just look at this monster, the user guide alone is over 700 pages, that’s not including the supplementary guides. The supplements I have are Working with Macros, Working with Definition Files, Setting up Agenda, and a few miscellaneous leaflets.
I guess that’s my bedtime reading taken care of for a while. I actually received the macro reference still in the original shrink wrap, it almost seems a shame to open it!
None. macOS does not recognize the UHD 730 architecture.
This does not provide full native acceleration and can lead to system instability. 3. Basic "Safe Mode" Usage
It attempts to inject older drivers or universal patches to resolve the "7MB VRAM" issue.
The primary issue stems from the and the XeLP architecture found in 11th Gen CPUs. These changes disrupted how macOS handles primary buffer mapping and communication with the graphics hardware, leading to: Black screens on boot. No video output through HDMI or DisplayPort.
Since the UHD 730 cannot be fully "fixed" for native-like performance, Hackintosh enthusiasts typically choose one of the following paths:
Not possible natively. Without drivers, the system will rely on VESA (software) rendering, resulting in a slow, laggy interface with only ~7MB of recognized VRAM.
If you are planning a Hackintosh build using an 11th Gen (Rocket Lake) or 12th Gen (Alder Lake) Intel processor, the is a major hurdle. Unlike its predecessors, this specific integrated GPU (iGPU) lacks native support in macOS, leading to significant performance issues if not addressed correctly. The Reality of Intel UHD 730 Compatibility
If you only need macOS for non-graphical work (like coding or server management), you can run it without acceleration by using the iigfxcfg=def boot argument or disabling the iGPU entirely. Be prepared for a very choppy user interface.
Intel UHD Graphics 730 Hackintosh Guide: Compatibility and Solutions
The Intel UHD 730 is based on the , which was introduced after Apple began its transition to Apple Silicon. Because Apple never used these specific Xe-based iGPUs in their own Intel-based Macs, they never wrote drivers for them.
Intel Uhd Graphics 730 Hackintosh |top| May 2026
You probably need to use other applications or services, and sync your data with your phone. Writing and reading files from outside DOSEMU is no problem, so if you just want to sync files this is no problem.
As it’s a terminal application you can also just SSH in and run it.
You probably also want to have your appointments sync with your calendar or something.
Export
There are two ways to export data from Agenda. If you have a commandline tool that you can pass arguments to, then you can write a macro that will invoke it. intel uhd graphics 730 hackintosh
Otherwise, you can export your data to a file.
Files
Agenda can export items to a format called STF, Structured Text File. The specification for that format is (mostly) documented in the manual, but it didn’t catch on.
And so on, there are more examples in the README. If you can exchange data with other apps, you can now use stfjson to generate the correct format.
You can automate exports, Agenda has “Special Actions” in the category options. Alternatively, if it’s just a one off or for a macro, you can use the Transfer > Export command. they never wrote drivers for them.
Commands
In DOSEMU, the UNIX command will invoke a shell command on the host.
C:\>unix uname
Linux
If there is a commandline tool that will import data, e.g. a TaskWarrior user might use task add drop off laundry at dry cleaners, then you can create a macro in Agenda that simply launches that command.
You can use something like {F10}ULUNIX task {TYPE;%TASKTEXT}.
Import
Surprisingly, Agenda supports importing arbitrary text data. One of the manuals that came with agenda was Working with Definition Files, which explains how to write a configuration file that allow Agenda to parse anything.
It even has a Regular Expression tutorial, pretty impressive for a 1980s consumer product.
Intel Uhd Graphics 730 Hackintosh |top| May 2026
I quite like Agenda. It does many things well, but it’s absolutely true you could replicate most of it’s functionality with modern tools. However, I do enjoy using it, and I’m a big enough nerd that I quite like the challenge of using retro software.
I think the closest modern equivalent to Agenda would be taskwiki. It’s not a perfect match, but if you liked some of what you saw here but are not interested in retro software, try it out!
I’m still using Agenda after two weeks, and about 40% of the way through the manual 😂
None. macOS does not recognize the UHD 730 architecture.
This does not provide full native acceleration and can lead to system instability. 3. Basic "Safe Mode" Usage
It attempts to inject older drivers or universal patches to resolve the "7MB VRAM" issue.
The primary issue stems from the and the XeLP architecture found in 11th Gen CPUs. These changes disrupted how macOS handles primary buffer mapping and communication with the graphics hardware, leading to: Black screens on boot. No video output through HDMI or DisplayPort.
Since the UHD 730 cannot be fully "fixed" for native-like performance, Hackintosh enthusiasts typically choose one of the following paths:
Not possible natively. Without drivers, the system will rely on VESA (software) rendering, resulting in a slow, laggy interface with only ~7MB of recognized VRAM.
If you are planning a Hackintosh build using an 11th Gen (Rocket Lake) or 12th Gen (Alder Lake) Intel processor, the is a major hurdle. Unlike its predecessors, this specific integrated GPU (iGPU) lacks native support in macOS, leading to significant performance issues if not addressed correctly. The Reality of Intel UHD 730 Compatibility
If you only need macOS for non-graphical work (like coding or server management), you can run it without acceleration by using the iigfxcfg=def boot argument or disabling the iGPU entirely. Be prepared for a very choppy user interface.
Intel UHD Graphics 730 Hackintosh Guide: Compatibility and Solutions
The Intel UHD 730 is based on the , which was introduced after Apple began its transition to Apple Silicon. Because Apple never used these specific Xe-based iGPUs in their own Intel-based Macs, they never wrote drivers for them.
