Very Computer

1. _IO_QIOCTL message "17 01 03 00 01 00 04 00 01 00 04 80 00"

    So as I develop my I/O Manager, I've encountered this QIOCTL message:

    17 01 03 00 01 00 04 00 01 00 04 80 00

    Parsed as per struct _io_qioctl:

    type:       0117 (I/O message QIOCTL)
    fd:         0003 (file-descriptor)
    request:    0001 (?)
    nbytes:     0004 (size of data)
    zero:       80040001 (yeah, whatever)
    data:       ...

    /usr/include/sys/qioctl.h doesn't help; there's no request==1 in the
enum __qioctl_type.  The Process Manager delivers this message after I
satisfy its _IO_OPEN request, but only on some machines.  Proc, Slib, etc
are the same versions.  I call qioctl() myself, but with requests starting
at 0x4301, not 0x0001.  Why does the ProcMan send me this 0x0001 request?
What does it mean?  How do I respond?  Where do I look for the info, as
it's *got* to be somewhere in the docs/include/...?  aTdHvAaNnKcSe

    L8r, P8r.

=;)

2. sound recognition

3. Babble from caustic@00.00.00.00

4. XORing Text Onto DC

5. Is there anyway to convert a lotus 1-2-3 v4.x file to an excel 97/00 or works 4/00 file?

6. NTDS KCC ERROR

7. :ODBC 0.43 tests failed under cygwin perl 5.8.0 DBI 1.30 on N T4 SP 6a MERANT 5 32 bit ODBC driver 0.52.00.00

8. Satisfied with Epson 600 print quality, but who designed those drivers?

9. DBD::ODBC 0.43 tests failed under cygwin perl 5.8.0 DBI 1.30 on N T4 SP 6a MERANT 5 32 bit ODBC driver 0.52.00.00

10. LPT.VXD version 4.00.955

11. UNOFFICIAL XBOX FAQ, v4.00

12. where can i get the x-box at the price of the website (299,00)