Displaying 20 results from an estimated 5000 matches similar to: "microsoft developer studio, files changed problem"
1998 Nov 03
0
visual studio + oplocks
Hi,
I wonder if anyone else has seen this problem with visual studio 5.0.sp3
We are running NT4.0 sp3 + some updates such as euro etc.
The problem is a bit of a surprise as it makes vc++ unusable on a samba share with oplocks on.
it is surprising because I have definitely used vc++ in this configuration in the past.
It occurs with all versions of samba 1.9.18 from p3 which we use as standard
2005 May 16
0
Re: Slashdot: "Could Microsoft buy Red Hat?" -- this is a joke made by the clueless
From: Nigel Kendrick <support-lists at petdoctors.co.uk>
> Sorry if it wraps:
> http://linux.slashdot.org/article.pl?sid=05/05/16/1758249&tid=109&tid=163&tid=110&tid=98&tid=218
This has _nothing_ to do with Microsoft possibly buying Red Hat.
People who even suggest this only expose their *0* understanding of business.
Microsoft has an alliance with Sun.
Why?
2000 Oct 16
2
ssh2 authentication and ip forwarding
I'd been hoping to move all of our site to ssh protocol 2 whilst we are
still small enough to do this without serious pain, however the lack of
authentication and connection forwarding is making that difficult at
present.
I see the current (2.2.0p1) code base does not have the code on either
client or server side for ssh2 to handle tunneled connections or
authentication agent. Is this
2012 Jun 21
2
ACLS without winbind (but WITH correct user mapping)
Thanks to some of the guys on #samba-technical (obnox in particular!), I
now have a working samba configuration.
The environment:
In our setup each user has an entry in both openldap (no samba schemes)
and AD. Each account has the same name and even has a Unix UID entry in
AD. Our users ssh into Linux boxes, authenticating off of openldap.
Files are shared via samba.
Due to the account
2001 Mar 21
2
Challenge response authentication and PAM
As an experiment I set up Challenge/response authentication on a Linux
system with PAM using a pam_opie module (this module works fine with
console logins and su).
I can log into the box using the opie password, *but* it does not give
me the challenge - which can make things a little tricky :-)
I can well believe this might be a fault in the PAM pam_opie module I
am using, so has anyone got
2000 Nov 27
1
StrictHostKeyChecking
Long ago, when I wrote the ssh config file on my desktop box, ssh
(which might have been the non-openssh one) took 3 possible values for
the StrictHostKeyChecking option - yes, no & ask.
Today, when I attempted to connect to a new machine, with no DNS
entries (so using IP address) from my desktop box, ssh (now 2.3.0p1)
SEGVed. Looks like there is some subtle interaction between having an
2008 Nov 03
0
No subject
4) Subtract 1 from the keyframe, then repeat step 3).
5) Begin reading from the frame discovered in step 4. Drop any packets
which are output on the first page. Count down until we reach the
keyframe, dropping packets until then.
6) Continue counting down until we reach the target frame, we are now
decoding each frame/packet. At the target frame produce the YUV
output.
Steps 4 and 5 are
2008 Nov 03
0
No subject
<br>
4) Subtract 1 from the keyframe, then repeat step 3).<br>
<br>
5) Begin reading from the frame discovered in step 4. Drop any packets<br>
which are output on the first page. Count down until we reach the<br>
keyframe, dropping packets until then.<br>
<br>
6) Continue counting down until we reach the target frame, we are now<br>
decoding each
2002 Mar 01
2
RH7.2 journal creation
Stephen et al,
You may remember me raising the point that the new e2fsprogs (1.25 as I
remember) griped about old journals not having all the appropriate
fields zeroed.
I've just discovered that the RH 7.2 installer produces journals (ie on
partitions created as ext3 from within the installer) that flag these
warnings with a modified 1.25 e2fsck (the mods being to clear the errors
rather
1999 Oct 08
0
FW: Microsoft Visual Dev Studio
> -----Original Message-----
> From: Tony Boucher [mailto:tboucher@abio.com]
> Sent: Friday, October 08, 1999 10:57 AM
> To: 'samba@samba.org'
> Subject: FW: Microsoft Visual Dev Studio
>
>
>
>
> > Well hello there all,
> >
> > Thank you all for Samba ! With out it our development
> > environment would be much harder to manage.
2013 Oct 29
2
Problem Building opus-1.0.3 on Microsoft Visual Studio 2012
I am using mvs 2012 but the .sln provided is of msv 2010 so on opening .sln
it tries to update libraries which is successful but I am unable to build
(compile) it as it gives series of errors. I am pretty new to these things
so can anyone tell me if I am doing anything wrong or how to create(.lib
and .dll) files so I can use them in my project. Please forgive me if I
have asked something foolish.
2013 Oct 29
0
Problem Building opus-1.0.3 on Microsoft Visual Studio 2012
On 2013-10-29 2:39 PM, Akshit Jain wrote:
> Thanks a lot for replying. This is the output
>
>>------ Build started: Project: celt, Configuration: Debug Win32 ------
> 1> fatal: No names found, cannot describe anything.
> 1> The system cannot find the file C:\Users\user\Desktop\mUOn\Audio.
> 1> #define OPUS_VERSION ""=">
2007 Mar 09
2
[LLVMdev] LLVM with Microsoft Visual Studio
I just wonder that Visual Studio .NET 2003 is the most compatible one among various MS Visual Studio versions for LLVM.
Thank you
Seung Jae Lee
2007 Mar 10
0
[LLVMdev] LLVM with Microsoft Visual Studio
It is, if only because it's the version I use, but 2005 is supposed to
work also. That being said, I wouldn't be surprised to learn that it
doesn't due to recent STL issues. Versions prior to 2003 won't work.
Seung Jae Lee wrote:
> I just wonder that Visual Studio .NET 2003 is the most compatible one among various MS Visual Studio versions for LLVM.
>
> Thank you
>
2007 Mar 10
0
[LLVMdev] LLVM with Microsoft Visual Studio
On Sat, 2007-03-10 at 23:40 +0100, Andreas Fredriksson wrote:
> On 3/10/07, Jeff Cohen <jeffc at jolt-lang.org> wrote:
> > It is, if only because it's the version I use, but 2005 is supposed to
> > work also. That being said, I wouldn't be surprised to learn that it
> > doesn't due to recent STL issues. Versions prior to 2003 won't work.
>
>
2007 Mar 10
0
[LLVMdev] LLVM with Microsoft Visual Studio
No, the problem with StoreSDNode was that an argument as being called
Value, which hid the class Value later on in the argument list. This
also broke 2003 and was fixed a while ago.
_WIN32_WINNT is not supposed to be predefined, so that warning
shouldn't be occurring. I have never seen it myself, and a predefined
value could be inappropriate.
Most of the other changes seem to be about
2007 Mar 12
1
[LLVMdev] LLVM with Microsoft Visual Studio
On 3/12/07, Jeff Cohen <jeffc at jolt-lang.org> wrote:
> Just to make clear, there are no problems building 1.9 with VS 2003, nor
> are there any problems as I write this.
I'm fairly sure we grabbed the 1.9 tarball off the website, but I
could be wrong.
> That's what we do. We define it in llvm/lib/System/Win32/Win32.h, which
> in included by every file that uses the
2007 Mar 17
1
[LLVMdev] LLVM with Microsoft Visual Studio
Can Microsoft Visual Studio be a good tool for making a backend for an architecture?
Thanks,
Seung
---- Original message ----
>Date: Mon, 12 Mar 2007 12:44:48 -0700
>From: Jeff Cohen <jeffc at jolt-lang.org>
>Subject: Re: [LLVMdev] LLVM with Microsoft Visual Studio
>To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>
>Andreas Fredriksson wrote:
>>
2007 Sep 20
0
[LLVMdev] Building with Microsoft Visual Studio
Richard Smith wrote:
> I am working on a port of LLVM targeting a proprietary VM. Thus far
> development has been under Linux and Cygwin. Cygwin licensing would appear
> to require that LLVM built under Cygwin would have to be released under the
> GPL, so alternatives are being investigated.
>
> Using MS Visual Studio and following the instructions at
>
2007 Sep 20
0
[LLVMdev] Building with Microsoft Visual Studio
On 9/20/07, Richard Smith <richard.smith at antixlabs.com> wrote:
> Many thanks. Yes, this question has slightly sidetracked on the license
> issue, which was mostly an aside as to why we wish to use something other
> than Cygwin.
>
I totally understand. :-) I just wanted to bring it back on a technical track.
> On the make issue, I am very interested to know what it is