|
|
No. It's logging in under the local system account... Does that matter?
If I would set it to Network Service, would the other executed application inherit the rights of the service?
_outp(0x64, 0xAD);
and
__asm mov al, 0xAD __asm out 0x64, al
do the same... but what do they do?? 
(doesn't work on NT)
|
|
|
|
|
From the MSDN docs:
Using the Local System Account
The local system account does not require a password, does not have network access rights in Windows NT 4.0 and Windows 2000, and restricts your SQL Server installation from interacting with other servers.
Good music: In my rosary[^]
-- modified at 17:00 Monday 29th August, 2005
|
|
|
|
|
The System and LocalService accounts don't have network access by design. If you need the network, NetworkService is what you should use.
Child processes inherit the security and access of their parents, so that part should work.
--Mike--
Visual C++ MVP 
LINKS~! Ericahist | 1ClickPicGrabber | NEW~! CP SearchBar v3.0 | C++ Forum FAQ
There is a saying in statistics that a million monkeys pounding on typewriters would eventually create a work of Shakespeare. Thanks to the Internet, we now know that this is not true.
|
|
|
|
|
Hello all !
I have a little problem with VC++ 2005 beta.
The problem is with styles of controls.
I can't make them in modern style (I mean style of XP ).
What can I do to make them in modern style ?
|
|
|
|
|
it is not a VC++2005 problem.
you have to insert a manifest into your project...
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
I have to write something in *.rc
file or just add the manifest to the project ?
|
|
|
|
|
Just create a file called MyApp.manifest, or something like that, and copy the following text into it:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="x86" name="App" type="win32" />
<description>Application</description>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"/>
</dependentAssembly>
</dependency>
</assembly>
I know that in Visual C++ 6, you just have to import it as a resource, and when it asks for the resource type, you enter "24", and then change the resource's ID to "1". I'm not sure if it will work similarly in the 2005 beta, but it should be something along those lines.
[Insert witty and relevant signature here]
|
|
|
|
|
Hello,
Is it an imported project or a new one? I've had no such problems when I was using the beta..
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
|
In that case, the new styles manifest should be linked in automatically with your executable after the normal link step. What does the output window of your build display?
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
Generating Code...
Compiling resources...
Compiling manifest to resources...
Linking...
Embedding manifest...
Build log was saved at "file://c:\Documents and Settings\Admin\??????? ????\now\Prog\Prog\Debug\BuildLog.htm"
Prog - 0 error(s), 2 warning(s)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
That's what I have.
-- modified at 1:39 Thursday 1st September, 2005
|
|
|
|
|
Did you use MFC? I used MFC inmy project andeverything worked like a charm. I autmatically used the user settings for the windows styles (XP style or old style).
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
|
I don't know what is going wrong with your project. Do you have the new styles enabled in XP or do you have the old styles enabled for performance reasons? Otherwise, I don't know what might be wrong.
Behind every great black man...
... is the police. - Conspiracy brother
Blog[^]
|
|
|
|
|
both dialog-box and MDI-Document window are childs of another windows. but the former can be moved out of the client area of its parent, the latter can not; it goes unappeared.
which style differentiates these two child windows?
|
|
|
|
|
-- modified at 11:30 Monday 29th August, 2005
|
|
|
|
|
|
A dialog box is an owned window, not a child window. Only child windows are restricted to their parent's client area.
--Mike--
Visual C++ MVP
LINKS~! Ericahist | 1ClickPicGrabber | NEW~! CP SearchBar v3.0 | C++ Forum FAQ
"That probably would've sounded more commanding if I wasn't wearing my yummy sushi pajamas."
-- Buffy
|
|
|
|
|
|
|
hmm, I would ask what's up with replying to deleted messages? 
I posted a reply and got a server error  so I hit back and submitted again; but the first reply was actually received by the server, so that explains the two posts.
--Mike--
Visual C++ MVP
LINKS~! Ericahist | 1ClickPicGrabber | NEW~! CP SearchBar v3.0 | C++ Forum FAQ
|
|
|
|
|
I have a problem.
In my Server application method OnDraw CServerItem is called only once at startup, then
Some initialization occur in server.
How I Can update te representation of server in conteiner?
May be anyone know how it works?
And where OnDraw is called?
|
|
|
|
|
Tree controls seem to be eating WM_LBUTTONUP messages if drag and drop is enabled. If I turn drag and drop support off (using TVS_DISABLEDRAGDROP), I get the WM_LBUTTONUP messages fine but with it turned on, I stop getting them. Instead I get a TVN_BEGINDRAG message that lets me know if a drag was started but I need the WM_LBUTTONUP if no drag was done.
Anyone know how to force the tree control to give me the WM_LBUTTONUP if a drag operation was not started?
The two most common elements in the universe are Hydrogen and stupidity. - Harlan Ellison
Awasu 2.1.2 [^]: A free RSS reader with support for Code Project.
|
|
|
|
|
With drag and drop enabled, I get a WM_LBUTTONUP message if I move the mouse prior to releasing, and the release point is within the tree control:
1) Click
2) Move/drag within control
3) Release
4) WM_LBUTTONUP
If I don't move/drag, or I drag but release outside the control, I get nothing:
1) Click
2) Don't move or move/drag outside tree control
3) Release
4) Nothing
Strangely, NM_CLICK is fired if I don't move the mouse at all.
1) Click
2) Release
3) NM_CLICK
Perhaps a mouse capture in the begin drag routine would work.
He is smart. He will make our Windows go.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
