On 3/28/07, Dave Korn <[EMAIL PROTECTED]> wrote:
On 27 March 2007 21:13, Ken Fast wrote:
> My problem now is that your fix does not seem to apply to my case. I do
> not have a
> c:\windows\system32\dla\dlactrlw.exe, but instead have a tfswctrl.exe. In
> the Sonic help
> there is information o
On 27 March 2007 21:13, Ken Fast wrote:
> My problem now is that your fix does not seem to apply to my case. I do
> not have a
> c:\windows\system32\dla\dlactrlw.exe, but instead have a tfswctrl.exe. In
> the Sonic help
> there is information on DLA. It would appear that I have it turned on fo
On March 20 Marc Campere wrote:
>> Well, it seems I've found the problem, or at least a big component of
the problem.
>> Turns out it is likely not (directly) related to cygwin code but some
other interaction
>> between cygwin and the OS as a result of a Sonic Solutions DLA process
running.
>> DL
Marc Compere wrote:
cygcheck: dump_sysinfo: GetVolumeInformation() for drive E: failed: 2
cygcheck: dump_sysinfo: GetVolumeInformation() for drive Y: failed: 53
cygcheck: dump_sysinfo: GetVolumeInformation() for drive Z: failed: 53
These wouldn't be drive letters assigned by your Sonic DLA, wo
well, I have this problem too occasionally.
normally caused if its an SP2 machine. never have this problem on sp1
or noSP. also, if I disable the DLA sysyem, i cant access flash disks.
another thing to think about is, what does bash do with $0 or ARGV[0]
? if it sees its "bash" then its gonna ac
On 20 March 2007 08:17, Marc Compere wrote:
> Well, it seems I've found the problem, or at least a big component of
> the problem. Turns out it is likely not (directly) related to cygwin
> code but some other interaction between cygwin and the OS as a result of
> a Sonic Solutions DLA process run
Marc Compere wrote:
Dave Korn wrote:
On 18 March 2007 13:28, Marc Compere wrote:
The recent setup.exe update has caused bash.exe to have startup times
approx. 10x longer than before. sh.exe starts pretty quickly but
bash.exe
[...]
Running XP sp2 on a fresh, plain vanilla cygwin install. an
Thrall, Bryan wrote:
Marc Compere wrote on Sunday, March 18, 2007 8:28 AM:
The recent setup.exe update has caused bash.exe to have startup times
approx. 10x longer than before. sh.exe starts pretty quickly but
bash.exe via cygwin.bat takes ~30 seconds to start. Took just a
couple of seconds be
Marc Compere wrote on Sunday, March 18, 2007 8:28 AM:
> The recent setup.exe update has caused bash.exe to have startup times
> approx. 10x longer than before. sh.exe starts pretty quickly but
> bash.exe via cygwin.bat takes ~30 seconds to start. Took just a
> couple of seconds before. Cpu is now
* Marc Compere (Sun, 18 Mar 2007 13:27:31 + (UTC))
> The recent setup.exe update has caused bash.exe to have startup times approx.
> 10x longer than before. sh.exe starts pretty quickly but bash.exe via
> cygwin.bat takes ~30 seconds to start. Took just a couple of seconds before.
>
> Cp
On 18 March 2007 13:28, Marc Compere wrote:
> The recent setup.exe update has caused bash.exe to have startup times
> approx. 10x longer than before. sh.exe starts pretty quickly but bash.exe
> via cygwin.bat takes ~30 seconds to start. Took just a couple of seconds
> before. Cpu is nowhere near
11 matches
Mail list logo
