# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 17
# self = https://watcher.sour.is/conv/5tn7q7q
Found an OEM version of Windows 3.1 in a basement. The disks still work, except for disk number 3. It appears the corrupt sectors only affect CALENDAR.EX_, there’s an area of NUL bytes in it. I was still able to install Windows and most things appear to work – except for the calendar. It crashes the whole thing. 🥴
Windows 3.1 running in QEMU on MS-DOS 6.0. Program manager in the background, clock showing the current data in the lower left corner. Info screen on the right, showing the Windows version.
Segmentation fault after trying to run `CALENDAR.EXE`.
Found an OEM version of Windows 3.1 in a basement. The disks still work, except for disk number 3. It appears the corrupt sectors only affect CALENDAR.EX_, there’s an area of NUL bytes in it. I was still able to install Windows and most things appear to work – except for the calendar. It crashes the whole thing. 🥴
Windows 3.1 running in QEMU on MS-DOS 6.0. Program manager in the background, clock showing the current data in the lower left corner. Info screen on the right, showing the Windows version.
Segmentation fault after trying to run `CALENDAR.EXE`.
Found an OEM version of Windows 3.1 in a basement. The disks still work, except for disk number 3. It appears the corrupt sectors only affect CALENDAR.EX_, there’s an area of NUL bytes in it. I was still able to install Windows and most things appear to work – except for the calendar. It crashes the whole thing. 🥴
Windows 3.1 running in QEMU on MS-DOS 6.0. Program manager in the background, clock showing the current data in the lower left corner. Info screen on the right, showing the Windows version.
Segmentation fault after trying to run `CALENDAR.EXE`.
Wow! my first version was Win 3.11, and had good memories as a kid learning computing with my grandpa. Feeling nostalgic of watching those screenshots again.
I remember that almost never used the calendar. Scheduling wasn't important when I was a kid, I guess...
Wow! my first version was Win 3.11, and had good memories as a kid learning computing with my grandpa. Feeling nostalgic of watching those screenshots again.
@eapl.me Lovely memories, aren’t they? 😊
I was young, too, and rarely used the calendar. But I did do it at some point to plan a birthday. 😅
I just checked and CALENDAR.EXE isn’t present in my installation of Win 3.11. 🤔 That’s a little weird, it should be.
@eapl.me Lovely memories, aren’t they? 😊
I was young, too, and rarely used the calendar. But I did do it at some point to plan a birthday. 😅
I just checked and CALENDAR.EXE isn’t present in my installation of Win 3.11. 🤔 That’s a little weird, it should be.
@eapl.me Lovely memories, aren’t they? 😊
I was young, too, and rarely used the calendar. But I did do it at some point to plan a birthday. 😅
I just checked and CALENDAR.EXE isn’t present in my installation of Win 3.11. 🤔 That’s a little weird, it should be.
@movq Wow that hilarious 😆🤯 Publish the disk images or hard disk as a QEMU image to play with?
@movq Wow that hilarious 😆🤯 Publish the disk images or hard disk as a QEMU image to play with?
@movq Wow that hilarious 😆🤯 Publish the disk images or hard disk as a QEMU image to play with?
@movq My first taste of Windows was also Windows 3.1 and later Windows 3.11 for workgroups
@movq My first taste of Windows was also Windows 3.1 and later Windows 3.11 for workgroups
@movq My first taste of Windows was also Windows 3.1 and later Windows 3.11 for workgroups
@prologic I’m way too scared of copyright shit to upload something like this. 🤣 (But needless to say, it’s already easy to find on various sites.)
@prologic I’m way too scared of copyright shit to upload something like this. 🤣 (But needless to say, it’s already easy to find on various sites.)
@prologic I’m way too scared of copyright shit to upload something like this. 🤣 (But needless to say, it’s already easy to find on various sites.)