|
wildelf wrote:
I dont understand how crackers break the .exe files and they are making cracks, it has to be a way to do it . Am i right?
Yep, but not with source code, they know assembler and EXE formats.
Max.
Maximilien Lincourt
For success one must aquire one's self
|
|
|
|
|
where can i find someone who knows assembly an exe formats?
|
|
|
|
|
 Beleive me, in many cases it is faster to re-write the source code then disassemble the exe (unless your exe not so big as MS Windows.
I'm not sure but I think if you included debug information in your exe, it could slightly simplify your task.
|
|
|
|
|
i don't know it for sure, but.... there is a way the decompile a program, right? i've seen someone do it once in visual something(i was a turbo pascal nerd than so i didn't understand anything of visual studio), he decompiled the explorer.exe and changed the start menu its logo's....
[]D [] []D []
|
|
|
|
|
In my OnBUttonOK() I calls CDialog OnOK();
I want to "delete this". Where does this line go...before the CDialog OnOK(); or after it, so that it is the last line in the function?
Appreciate your help,
ns
|
|
|
|
|
i suggest if u don't know how to use "delete this" u should not use it.
at the very least we need more information to determine what your trying to accomplish and therefore how/where you should use it.
"No matter where you go, there your are..." - Buckaoo Banzi
-pete
|
|
|
|
|
I created a modeless dialog with a new in a VIew cLass. Then after its spwaned and I press the OK button I have on the CDialog, it doe ssome stuff and then calls
CDialog::OnOK();
THe pointer I created with the new is the one i want to delete, so i was wondering if I should do it before or after the base call to OnOK....
Appreciate your help,
ns
|
|
|
|
|
just call DestroyWindow() where you want to end the dialog, and override the virtual function PostNcDestroy()(or handle WM_NCDESTROY if you dont use mfc) and write "delete this or some stuff" in it.
hope it works
|
|
|
|
|
I think I almost have a complete handle on this "new" stuff. Thanks for the info....also I read a CP article om modeless dlgs that helped..
Appreciate your help,
ns
|
|
|
|
|
I was a bit unsure with some info in it, but I am going to try it and see if I interpreted it correctly. Thanks for helping
Appreciate your help,
ns
|
|
|
|
|
I lost the exact syntax, but sometimes I'l make a copy of a perfectly fine project and when I load the new copuy, it says : error , and resource.rc. could not be...
How does one fix this and why does this happen?
Appreciate your help,
ns
|
|
|
|
|
Hi,
I am calling a Dialog box from a propery page. The dialog box contains an edit box which takes in numbers as user inputs. I then want these numbers to be used on the property page.
However, as I "OK" the dialog box and go back to it, the numbers have changed back to what the constructor contains.
I have used UpdataData(TRUE); but it continues to revert back to the original numbers.
void CMyPropPage::OnCallMyDlgButton() <br />
{<br />
UpdateData(TRUE);<br />
CMyDlg ViewData;<br />
ViewData.DoModal();<br />
UpdateData(FALSE);<br />
}
Have I missed something out?
kash
|
|
|
|
|
Kash wrote:
Have I missed something out?
Yep!
MSDN[^]says:
The framework automatically calls UpdateData
with bSaveAndValidate set to FALSE when a modal
dialog box is created in the default implementation
of CDialog::OnInitDialog. The call occurs before
the dialog box is visible. The default
implementation of CDialog::OnOK calls this member
function with bSaveAndValidate set to TRUE to
retrieve the data, and if successful, will close
the dialog box. So you Do not have to call UpdataData() yourself:
void CMyPropPage::OnCallMyDlgButton()
{
CMyDlg ViewData;
if (ViewData.DoModal()==IDOK)
m_Number = ViewData.m_Number;
}
My opinions may have changed, but not the fact that I am right.
|
|
|
|
|
yep that works, but when I re-open the dialog box, the changes have been lost. I want to keep the changes fixed and not for it to revert to the constructor values of the dlg box.
kash
|
|
|
|
|
Kash wrote:
I want to keep the changes
Then you can set the desired value before the DoModal(), as palbano suggested.
My opinions may have changed, but not the fact that I am right.
|
|
|
|
|
CMyDlg ViewData;
ViewData.m_number = 10; // set data to previous value
ViewData.DoModal();
m_viewdatanumber = ViewData.m_number; // capture data from dialog
"No matter where you go, there your are..." - Buckaoo Banzi
-pete
|
|
|
|
|
|
hi all!
how can i read a file line by line using fscanf() in a win32 api program
and then display each line in a text control!
Someone here told to use fscanf() rather than fgets()
(I don't remember who..)
Thanks for any answer!!!
|
|
|
|
|
If you are writing code specific from Windows using the Win32 API, why not use the platform API which encapsulates much more support for file access (especially when wanting to get return codes)? Calls like CreateFile(), WriteFile(), ReadFile() are designed with more functionality (such as DACL support etc) which make it more robust.
With that said, if you really want to use fscanf read this article from MSDN:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_fscanf.2c_.fwscanf.asp[^]
If you scroll down there is an example on how to use fscanf. A note though, if you are wanting to read line by line, fgets() may be more appropriate, and you get the control of defining the max size of the buffer you will read at any one time.
Just a thought. YMMV.
Good luck.
- Dana 
|
|
|
|
|
When I want to use a COM Interface, like the Microsoft XML DOM Parser I can use the #import keyword (like #import "msxml3.dll") and than use the simple Interface Pointer, like IXMLDOMDocumentPtr or IXMLDOMNodePtr.
Ok... but how can I use this method (#import and I???Ptr) with some other COM Interfaces, like the DirectShow COM Interface?
Where can I found the DLL I have to inlude (#import "xxx.dll")?
(I have not found a DLL like dshow.dll)
Daniel 
---------------------------
Never change a running system!
|
|
|
|
|
Actually, what you #import is the type library, which is usually included in the DLL (but can also be a separate).
There's a problem with the DirectX stuff, though: I've already searched up & down for a TLB of it, and couldn't find any (even asking here didn't help ) So unless I missed something, you're basically stuck with the ugly MS header files.
OTOH, there are some DirectX "helper" ActiveX (looks like they are intended for VB et. al.), which expose the core functionality and provide their own TLB. Haven't delved deeper into it, as I was looking for full functionality...
However, maybe someone comes up with some better info, maybe the "DirectX 8 for VB" allows to access the entire model by some clever QueryInterfacing...
If you go to war, you will destroy a great country a stoned greek chick to the richest man of the world
[sighist] | [Agile Programming] [doxygen]
|
|
|
|
|
Watch out a file named interop2.cs in your VS.NET cd. It's a sample which interops the Quartz type-library (DirectShow).
|
|
|
|
|
Thanks!
Daniel
---------------------------
Never change a running system!
|
|
|
|
|
The DirectShow engine is in quartz.dll
|
|
|
|
|
Thanks! I will try it!
Daniel
---------------------------
Never change a running system!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
