#28 Security Access Violation Win2K

open
nobody
5
2001-08-22
2001-08-22
Anonymous
No

The following command

cdrdao write -v 2 --speed 4 --device 0,0,0 --driver
generic-mmc --eject videocd.cue

works fine on a Win 98 machine using external USB HP
8200 CD-Writer.

The same command on Win 2K fails and gives a Security
Access Violation.

I assume I have got the device SCSI-ID wrong for Win
2K. Thus, I would be very grateful if someone could
tell me how to find out the SCSI-ID of an external USB
CD Writer.

What I have below is
what I have been able to find about the USB Universal
Host Controller from the machine.

Device
Intel 82371AB/EB PCI to USB Universal Host Controller

PNP Device ID
PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01
\3&61AAA01&0&3A

Thanks!

Discussion

  • Logged In: NO

    Small note to non-Win2k developers:
    hen Windows NT/2000/XP/2003 encounters a bad pointer
    dereference (the kind that would cause sig11 under UNIX),
    it displays a very technical error message refering to the error
    as a (memory) "access violation". Many end users get confused
    and report such errors as "security violations". So this bug
    is probably just a pointer handling error in cdrdao or one
    of the system libraries.

    Also note, that at least some versions of the cdrecord libschily
    scsi library is known to experience this error when trying to use
    the Adaptec ASPI interface. ASPI is a roxio product once
    used as the cross-vendor API for SCSI drivers under DOS, OS/2,
    Netware servers and others. But under NT/2000/XP/2003 it is
    just an emulation layer running on top of the official ioctl based
    interface which is part of the kernel on these systems.

    Thus this may be a libschily porting issue, and might not be
    a cdrdao issue.

    Friendly, jbj@image.dk