Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.development    |    Operating system development chatter    |    4,255 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,989 of 4,255    |
|    Paul Edwards to All    |
|    UEFI boot basics    |
|    28 Nov 23 00:42:10    |
      From: mutazilah@gmail.com              Hi James.              > Any idea why your reply appears as a new thread?              Oh, that actually happened, did it? In google       groups my posts are appearing in the same thread       normally.              That initially surprised me, but then I thought       it was logical for situations where the reply is       not to anyone specific.              Bottom line is that I am using this crude program:              https://sourceforge.net/p/pdos/gitcode/ci/master/tree/src/pdpnntp.c              (which I wrote) since google groups became read-only.              I don't yet know how to construct a reply properly,       but even if I did, google groups isn't showing me       the raw headers (it used to), so I can't extract       the information I need.              I could get the raw headers via eternal september,       but that is more laborious. And I still don't know       the rules, regardless. I assume it's a simple matter       of getting the message-id from the original message       and then constructing some sort of in-reply-to       header line? If someone can confirm that, I'll try       to do a proper reply for you to confirm.              >> mingw64 has what is required.       >>       >> As does UCX64.              > Well, my development environment is Unix so I am not sure that either       > would fit. More importantly, I think that I can already control what       > goes in to the finished executable and have tried stripping out the       > library code, it's just that there's an unresolved problem with the UEFI       > firmware not liking the result.              Can you not run mingw under Wine to confirm that       you get a better result when you use standard       Windows calling convention and standard PE       executables?              I don't know if mingw64 can be built as a standard       Unix appication, but the tools in UCX64 are all       standard C90 applications except for cc64 which uses       a little bit of C99 (long long), so you need a compiler       with a little bit of C99 support (which you certainly       have), and then you can build native Linux tools that       produce proper PE executables instead of ELF-kludged.              And Wolfgang is probably using Windows so would probably       be better off going a route that doesn't involve the       Linux kludge.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca