I've been using Apache 2 on Linux and FreeBSD for about 2 months now (got into it while playing around with Subversion, another project that seems to be making excellent progress), and IMHO it is really going to rock the server world. Some major plusses:
./configure; make; make install (almost). No more APACI, thankfully.
APR. It's already starting to be used by other projects.
Totally rewritten mod_cache, mod_proxy, etc. Works much better now!
Will actually work on Windows (well, some may not see this as a benefit, but whatever).
People have been complaining that Apache 2 is slow to come out, but from what I've seen lurking on the mailing list, it's because they want to ensure the quality of this release. They've also been talking about how they want a lot of beta testers, because (<rumor mode on>)they want to release soon, maybe even from 2.0.32. So get out there and beta test it!
Actually (heh. how OT can this thread get?!) on Win9x VFAT if the computer blue screens or hard locks while it has files open for writing, they'll be filled with crap (rounded up to the next cluster boundary) when you reboot. This caused us no end of problems with DB corruption until somebody figured it out and Used The Source(tm).
You're right, I should have said, "Yeppers, it's the DOS terminate command, and it's unique just like all the other ones!" That doesn't have the same ring to it though.
Int 20h is just for compatibility with old programs though. From drdos.net:
If any file that has changed in length is not closed prior to an INT 20H, the directory entries for its length, date, and time will not be correctly recorded (see the Close File (10H) and Close a File Handle (3EH) calls in Chapter 4, DR-DOS System Calls). If you want your program to pass an error or completion code before terminating, use Terminate a Process (4CH).
YMMV. Who programs in DOS nowadays anyway? (Well obviously a few people, look at the size of this thread!)
Geez, looks like it disappeared. OK, well originally it was a link to the same page that's now in my .sig.
---
Have you crashed Windows XP with a simple printf recently? Try it!
I've been using Apache 2 on Linux and FreeBSD for about 2 months now (got into it while playing around with Subversion, another project that seems to be making excellent progress), and IMHO it is really going to rock the server world. Some major plusses:
People have been complaining that Apache 2 is slow to come out, but from what I've seen lurking on the mailing list, it's because they want to ensure the quality of this release. They've also been talking about how they want a lot of beta testers, because (<rumor mode on>)they want to release soon, maybe even from 2.0.32. So get out there and beta test it!
---
Have you crashed Windows XP with a simple printf recently? Try it!
You bastard, your .sig crashed my Windows XP box! :)
That's pretty cool, I think I'll put it in mine.
Actually (heh. how OT can this thread get?!) on Win9x VFAT if the computer blue screens or hard locks while it has files open for writing, they'll be filled with crap (rounded up to the next cluster boundary) when you reboot. This caused us no end of problems with DB corruption until somebody figured it out and Used The Source(tm).
Int 20h is just for compatibility with old programs though. From drdos.net:
If any file that has changed in length is not closed prior to an INT 20H, the directory entries for its length, date, and time will not be correctly recorded (see the Close File (10H) and Close a File Handle (3EH) calls in Chapter 4, DR-DOS System Calls). If you want your program to pass an error or completion code before terminating, use Terminate a Process (4CH).
YMMV. Who programs in DOS nowadays anyway? (Well obviously a few people, look at the size of this thread!)
Yeppers, it's the one and only DOS terminate command. Don't leave home without it (or you'll never get back!)
Dude, it depends on the processor mode.
V86 + real mode: B8 00 4C = mov ax, 4c00h; CD 21 = int 21h
protected mode: B8 00 4C CD 21 = mov eax, 21cd4c00h