Re: [Cdrtools-developers] cdrecord insufficient privs on windows 7

[Joerg S. <Joe...@fo...>]

Jim Michaels <jmi...@ya...> wrote:

>          cdrecord: Insufficient 'file read' privileges. You will not be able to open all needed devices.
>           cdrecord: Insufficient 'file write' privileges. You will not be able to open all needed devices.
>           cdrecord: Insufficient 'device' privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.
>           cdrecord: Insufficient 'memlock' privileges. You may get buffer underruns.
>           cdrecord: Insufficient 'priocntl' privileges. You may get buffer underruns.
>           cdrecord: Insufficient 'network' privileges. You will not be able to do remote SCSI.
>           scsidev: '2,0,0'
>           scsibus: 2 target: 0 lun: 0
>           cdrecord: Warning: Cannot read drive buffer.
>           cdrecord: Warning: The DMA speed test has been skipped.
>           Cdrecord-ProDVD-ProBD-Clone 3.01a24 (i686-pc-cygwin) Copyright (C) 1995-2014 Joerg Schilling
>           Using libscg version 'schily-0.9'.
>           Device type    : Removable CD-ROM
>           Version        : 0
>           Response Format: 2
>           Capabilities   : 
>           Vendor_info    : 'PIONEER '
>           Identifikation : 'BD-RW   BDR-209M'
>           Revision       : '1.20'
>           Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
>           Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
>           Driver flags   : MMC-3 SWABAUDIO BURNFREE 
>           Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R LAYER_JUMP
> the guy who writes cdrcord needs to learn how to write code for windows. you can't apply nix sockets (win32 it's wsock2 or winsock and it must be started) an file permissions and groups to windows, also, nix is case sensitive, while NTFS is case insensitive.
> all this stuff listed above is *nix-only and shows it has not been properly coded for the win32 API. there are mutexes, semaphores, and WaitForMultipleObjects() in WIN32 API for locking. I don't know how you would lock memory in windows. ahh here it is: http://msdn.microsoft.com/en-us/library/windows/desktop/aa366895%28v=vs.85%29.aspx
> just search msdn.microsoft.com and use the compiler MSVC++ or mingw-w64+MSYS.internal SATA to mobo.
> win7sp1x64ult retail. I noticed after adding a -reset command to cdrecord in settings and hitting enter and saving, it did not take, -reset is not being issued to cdrecord.
> the option list is being ignored. -------------

The people who implement Cygwin seem to miss to understand that if they 
implement emulations of Linux interfaces, that they need to ake the 
implementation correct, or programmms will fail.

Did you make a bugreport against Cygwin?

Cdrtools is compiled based on the results from a previous autoconf run. If 
Cygwin pretends to have interfaces desogned by Linux, they need to make these 
interfaces behave correctly or to reove them because they are useless.


Regarding to sockets on Win-DOS:

-	please follow the mail rules and reduce line length to less than 80 chars. You 
	send extremely long lines that aare unreaadable.

-	What is your problem related to sockets on Win-DOS? You are not using 
	Win-DOS directly but via Cygwin and Cygwin includes a correctly working
	socket implementation. There is no need to have a special treatment for
	Win-DOS because if you really compile cdrtools uaing cl.exe, you miss 
	all the features that would require sockets.


Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'