02-17-2004, 11:19 AM
02-17-2004, 12:31 PM
Well, you have to compile it, and find a server that runs 16-bit dos programs. that's all cgi programs are, anyways, just console programs. The server takes their output and sends it to the person viewing the page.
I think the one jqb45 was called 'xitami' or something along that line...
I think the one jqb45 was called 'xitami' or something along that line...
02-17-2004, 06:06 PM
It is xitami, and http://www.xitami.com. I use it with my old win95 100mhz laptop, where it's fast, but doesn't matter to much when ie5 isn't heh...
02-17-2004, 07:25 PM
Cool, I used Xitami with my '95 120 MHZ laptop...Meh.
Anyway, as I remember it from some tutorial on how these scripts work, is that you send regular requests to compile/interpret them and then they do whatever they want...file operations, etc, etc, and usually the also print stuff to something called Standard Output. In QB, you would use PRINT for this - naturally, it wouldn't print to the screen. It would print to Standard Output, which is redirected from a screen to you, the one requesting the cgi program.
See?
Oh, and when passing form data, it gets stored in regular msdos environment variables. And you can access it from QB like that.
Hmmm..That renewed my old enthusiasm...I'm going to try it again.
Anyway, as I remember it from some tutorial on how these scripts work, is that you send regular requests to compile/interpret them and then they do whatever they want...file operations, etc, etc, and usually the also print stuff to something called Standard Output. In QB, you would use PRINT for this - naturally, it wouldn't print to the screen. It would print to Standard Output, which is redirected from a screen to you, the one requesting the cgi program.
See?
Oh, and when passing form data, it gets stored in regular msdos environment variables. And you can access it from QB like that.
Hmmm..That renewed my old enthusiasm...I'm going to try it again.