Hi!
Liam is right; AI-generated answers are not welcome on this email list. Generative AI is often *mostly* correct ...
This AI is wrong in an INTERESTING way. It basically sounds like somebody *thinking aloud* while browsing normal search results related to the problem at hand, but failing to dig deeper or properly work out any of the possible approaches. It first suggests to install a proxy on a separate Linux PC to translate between HTTPS and HTTP, giving requirements for at least 4 proxy server apps. Then it mentions that you could (probably telnet or ssh) to a Linux PC and use wget, curl or a text-based browser running THERE, but also complains about limitations of those. Next, it suggests a cloud, apparently implying that you download the HTTPS website and upload your copy to your own HTTP cloud webspace. More explicitly, another AI suggestion says you could download the website on another PC and then carry a copy to your DOS PC (sneakernet). Between, it mentions that packet drivers, email clients (unrelated!) and TCP/IP libraries exist, but may have outdated TLS/SSL support or may need modern CPU and more RAM than ancient DOS users had, so finally it sort of gives up, telling us it is too hard :-p If the above sounds like incoherent ramblings, then this might be because they are the summary of exactly that, although the AI uses more words and loves to add fun details as item lists. Cheers, Eric ;-) PS: We ship at least 4 browsers plus curl, wget and htget. Have you tried whether any of them supports that HTTPS website? DoJS might contain some unexpected abilities regarding HTTPS as well. https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/report.html _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
