It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
General discussionWhen it's 1 BC...(30 posts)(30 posts)
(30 posts)
Pages:
1
2
This is my favourite topic
Posted December 01, 2017
Sorry to bump this, but I believe I might have figured out when this bug happens.

When after clicking "Post my message" the window gets stuck, but your message gets posted nonetheless, then the last date sets to Nov -1, until a newer properly created thread corrects it.
Posted December 03, 2017
avatar
ZFR: Sorry to bump this, but I believe I might have figured out when this bug happens.

When after clicking "Post my message" the window gets stuck, but your message gets posted nonetheless, then the last date sets to Nov -1, until a newer properly created thread corrects it.
You could maybe send that to GOG support, for them to note down about this bug. Might save someone some time if/when they get around to fixing it. They know about the issue, but it isn't even medium priority on their To Do list.
Posted December 03, 2017
yeah it's all over the game subforums for me

when I first saw it my thought was "oh more broken crap on the gog forums no surprise!" and moved on along
Posted December 04, 2017
avatar
Bookwyrm627: You could maybe send that to GOG support, for them to note down about this bug. Might save someone some time if/when they get around to fixing it. They know about the issue, but it isn't even medium priority on their To Do list.
It's just the latest, and most prolific, trigger for this bug. It also happens when GOG renames/"renames" a forum. Occasionally, it happens for no apparent reason I can see.
Posted December 04, 2017
I blame the y2k bug on this one.
Posted December 04, 2017
avatar
DreamedArtist: I blame the y2k bug on this one.
I blame the y2k38 bug.
Posted December 04, 2017
avatar
DreamedArtist: I blame the y2k bug on this one.
avatar
Maighstir: I blame the y2k38 bug.
Just looked that one up and was like great another one coming soon XD
Posted December 04, 2017
Quite an interesting bug...
Posted December 04, 2017
avatar
Maighstir: I blame the y2k38 bug.
avatar
DreamedArtist: Just looked that one up and was like great another one coming soon XD
Well, it's 20 years away, and the relevant people are aware and working on it. It'll be fine. Possibly except for unpatched legacy systems.
Post edited December 04, 2017 by Maighstir
Posted December 04, 2017
avatar
Maighstir: Well, it's 20 years away, and the relevant people are aware and working on it. It'll be fine. Possibly except for unpatched legacy systems.
In 20 years from now you'll probably have as many 32-bit systems in use around as there are 16-bit systems in use as we speak. If you're not running Cold War era software, ancient SOCs or satellite/space-station hardware I'd say you'll be safe.

Anyway, you're still not looking far enough into the future!
Posted December 04, 2017
avatar
Maighstir: Well, it's 20 years away, and the relevant people are aware and working on it. It'll be fine. Possibly except for unpatched legacy systems.
avatar
WinterSnowfall: In 20 years from now you'll probably have as many 32-bit systems in use around as there are 16-bit systems in use as we speak. If you're not running Cold War era software, ancient SOCs or satellite/space-station hardware I'd say you'll be safe.

Anyway, you're still not looking far enough into the future!
Legacy operating systems, even if not on original hardware, are frequently emulated.
Posted December 04, 2017
avatar
Maighstir: Legacy operating systems, even if not on original hardware, are frequently emulated.
... and perhaps they'll be emulating Windows 3.11 on the starship Enterprise as well, with its system clock still stuck in the 1980s. I'm sure nobody will mind, since nobody will be crazy enough to run mission-critical applications on it (except on the holodeck).

My point is that limitations are to be expected and the emulation software should know how to take care of any special needs of this sort.
Post edited December 04, 2017 by WinterSnowfall
Posted December 04, 2017
avatar
Maighstir: Legacy operating systems, even if not on original hardware, are frequently emulated.
avatar
WinterSnowfall: ... and perhaps they'll be emulating Windows 3.11 on the starship Enterprise as well, with its system clock still stuck in the 1980s. I'm sure nobody will mind, since nobody will be crazy enough to run mission-critical applications on it (except on the holodeck).

My point is that limitations are to be expected and the emulation software should know how to take care of any special needs of this sort.
Or they create replacements for the clock libraries/applications, but yeah.
Posted December 04, 2017
somewhere some programmer misplaces a bracket

and the internet breaks forver
Posted December 05, 2017
avatar
Maighstir: Well, it's 20 years away, and the relevant people are aware and working on it. It'll be fine. Possibly except for unpatched legacy systems.
avatar
WinterSnowfall: In 20 years from now you'll probably have as many 32-bit systems in use around as there are 16-bit systems in use as we speak. If you're not running Cold War era software, ancient SOCs or satellite/space-station hardware I'd say you'll be safe.

Anyway, you're still not looking far enough into the future!
Holy shit another one that long from now haha ok I give up XD I will let the other generations deal with that one.
Pages:
1
2
This is my favourite topic
Community
General discussionWhen it's 1 BC...(30 posts)(30 posts)
(30 posts)