Event JSON
{
"id": "6681c59a593e519080b16b4de382cc9cfa05861fedd90f96a6837d1d90e91af7",
"pubkey": "43fb5b901c8fc0f040ae9b1167d8a46d2ccaf0e41f7396728df43579a3d15f77",
"created_at": 1724284929,
"kind": 1,
"tags": [
[
"t",
"86box"
],
[
"t",
"retrocomputing"
],
[
"t",
"adminlife"
],
[
"t",
"emulation"
],
[
"imeta",
"url https://files.techhub.social/media_attachments/files/113/002/736/049/245/342/original/7a31ab884574d99f.jpg",
"m image/jpeg"
],
[
"proxy",
"https://techhub.social/@dfx/113002737129219418",
"web"
],
[
"t",
"msdos"
],
[
"proxy",
"https://techhub.social/users/dfx/statuses/113002737129219418",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://techhub.social/users/dfx/statuses/113002737129219418",
"pink.momostr"
],
[
"-"
]
],
"content": "Okay, I just learned something.. but it also gave me quite a headache!\n\nI had received an \"Incorrect MS-DOS version\" error message from EDLIN.EXE, when running it from an official MS-DOS 6 Supplemental Disk from within MS-DOS 6. That... shouldn't happen.\n\nTook me a few moments to figure that one out. Several days ago, I had upgraded that very 86Box installation from MS-DOS 5.0 to 6.0. Because of this, SETVER.EXE still remembered EDLIN.EXE to be a \"5.00\" application, which confused the modern EDLIN.EXE to throw that error message. It worked fine again after I removed it from the version table.\n\nLet's just say, I had the urge to slam my head into a wall for a moment.\n\nThat was fun!\n\n#MSDOS #RetroComputing #AdminLife #86Box #Emulation\nhttps://files.techhub.social/media_attachments/files/113/002/736/049/245/342/original/7a31ab884574d99f.jpg\n",
"sig": "04325ccef5c4a07054374098d43288891472531b4fe8dc3ac8f787688ab6b8050d362b437791410aa27f6fce550cd50adf268ac84a7df021ada534c75dd45cad"
}
