Skip to content

Paltalk Timer

Viewing 15 posts - 106 through 120 (of 143 total)
1 2 3 … 7 8 9 10
  • Author
    Posts
  • July 22, 2013 at 6:21 pm #186032
    cyberpunk
    Member

    I have two machines and two copies of Express, I have only been working with this one machine the other one has some code with a stripped down version of the AdminBot that i want to now get working like this one. Welcome to my manic mind Chike. I apologize in advance lol

    But I hear you i should probably crank up the timers,

    Just trying to abide by the if it ain’t broke rule lol

    July 22, 2013 at 6:32 pm #186031
    Chike
    Member

    There is a type QWORD lol they prolly have their reasons.
    Anyway converting from a signed integer value to a larger integer value, signed or unsigned, without converting it first to unsigned short integer extends the sign to reflect the actual value.

    @ManicMike
    You don’t even need the timer, just add the lines I have posted, and debug them.

    July 22, 2013 at 6:58 pm #186030
    Departure
    Member

    Yes there is but microsoft don’t call it that, but at the end of the day its size of memory allocated, I normally see types as the following because when i do programing I tend to spent alot of time in ollydebug

    byte = 1 byte = 8 bits aka Byte
    word = 2 bytes = 16 bit aka short Integer
    dword = 4 bytes = 32bits aka Integer,
    Fword = 6 bytes = 48bits aka ?
    QWord = 8 bytes = 64bit aka long integer

    Now for your singed Integers ect.. I am not sure how it works but I think its little endian and big endian that determines signed and unsigned, BUT the point being its still the same amount of memory allocated which is 32bit aka dword aka Integer

    July 22, 2013 at 7:00 pm #186029
    cyberpunk
    Member

    lol, but then i would have to shut down my first baseline with the tweaked MEM_DECOMMIT, anyway it was not that long of a wait for me to update the other machine’s copy, the results are in paratheses and yes they are the results after it leaves the line assigned to it,

    (1) result = VirtualFreeEx(pHandle, pStrBufferMemory, 0, MEM_DECOMMIT)
    
(0) result = VirtualFreeEx(pHandle, pStrBufferMemory, 0, MEM_RELEASE)
    
(0) result = VirtualFreeEx(pHandle, pStrBufferMemory, 0, MEM_RELEASE)
    

    
I went ahead and added these too
    
(1) result = VirtualFreeEx(pHandle, pMyItemMemory, 0, MEM_DECOMMIT)
    
(0) result = VirtualFreeEx(pHandle, pMyItemMemory, 0, MEM_RELEASE)
    
(0) result = VirtualFreeEx(pHandle, pMyItemMemory, 0, MEM_RELEASE)
    July 22, 2013 at 7:13 pm #186028
    cyberpunk
    Member

    I was going to crank up the timer on the other copy to see if it might crash Paltalk, because as it is i hardly notice my Timer’s memory usage now. but it is functioning as expected

    July 22, 2013 at 7:20 pm #186027
    Chike
    Member

    Why do you insist to wate time when you can have the answer in few minutes?
    If you realy want to test it surround the alloc/free code with a 1 to million loop.

    Does my code looks like it’s a code to add to your code? I said debug it.

    July 22, 2013 at 7:25 pm #186026
    cyberpunk
    Member

    Because I am a noob dude. last thing I want to do is fry my laptop by doing something stoopid lol

    I have already wound up with a Soltaire cascade of pop windows lol

    July 22, 2013 at 7:35 pm #186025
    cyberpunk
    Member

    @Chike wrote:

    Why do you insist to wate time when you can have the answer in few minutes?
    If you realy want to test it surround the alloc/free code with a 1 to million loop.

    I will work on setting up the loop up and get back to you.

    @Chike wrote:

    Does my code looks like it’s a code to add to your code? I said debug it.

    Actually, yeah, I figured you had your reasons, you want to see Error codes, gotcha.

    July 22, 2013 at 7:40 pm #186024
    Chike
    Member

    @ManicMike wrote:

    @Chike wrote:

    Does my code looks like it’s a code to add to your code? I said debug it.

    Actually, yeah, I figured you had your reasons, you want to see Error codes, gotcha.

    You can add GetLastError calls if you want, but we can make some “safe” assuptions(oops i’m not doing as i preach) without them.

    July 22, 2013 at 8:10 pm #186023
    cyberpunk
    Member

    I did both. the GetlastError as I expected a 20 digit number as error,
    but GetLastWin32Error return error 87 as you probably expected

    July 22, 2013 at 8:21 pm #186022
    Chike
    Member

    Where when what?
    Code is about specificities (is there such word) .
    Describe exactly what results you had, try to make a conclusion.

    July 22, 2013 at 8:33 pm #186021
    cyberpunk
    Member

    @Chike wrote:

    Where when what?
    Code is about specificities (is there such word) .
    Describe exactly what results you had, try to make a conclusion.

    'deallocate the memory and close the process handle
    
'**************************************************
    
(1)     result = VirtualFreeEx(pHandle, pStrBufferMemory, 0, MEM_DECOMMIT)
    
(0)     result = VirtualFreeEx(pHandle, pStrBufferMemory, 0, MEM_RELEASE)
    
If result = 0 Then
    
(87)        result = Marshal.GetLastWin32Error
    
'result = GetLastError()
    
End If
    
(0)    result = VirtualFreeEx(pHandle, pStrBufferMemory, 0, MEM_RELEASE)
    
If result = 0 Then
    
(87)      result = Marshal.GetLastWin32Error
    
'result = GetLastError()
    
End If

    The only conclusion i can draw from this at this point is that the parameters are not being satisfied adequately for the MEM_RELEASE to process properly. I suspect the clue is in how you felt that removing that S from MEM_RELEASE would fix it it lol

    Yes, I was reading the exchange between you and Departure and I suspect I more clues lie in that exchange. I will play around with trying to get MEM_RELEASE to work by removing the S and see what happens before I form any conclusions. then if that also works I will have to figure out which one is best. My gut originally was that MEM_RELEASE made more sense.

    July 22, 2013 at 8:44 pm #186020
    cyberpunk
    Member

    I just realized why you thought that I was thinking I was supposed to add that code…it is because I took the initiative to add the lines to that other statement earlier, i assumed you were troubleshooting and I wanted to be torough, I knew you were adding those lines to troubleshoot, but I really thought you just wanted to see the return codes I did not realize you wanted full debug of the reason. And yes I totally understand and have for awhile now that the MEM_RELEASE is not liking the parameters but as you pointed out the only one that is not used elsewhere is the dwFreeType. so either I need to USE the MEM_DECOMMIT which just does not make sense to me based on the docs, though i get DECOMMIT would work. Now if it is about that S thing then that is totally new to me and I will be honest and admit that my eyes glossed over a little when I was reading that exchange since it was stuff I kinda understand and get it is going to be really important late on down the road lol but for now I just want to fix my timer so I can get back to my features lol just kidding. it is ALL really great stuff guys. I can see you guys know your stuff and I have no problem learning along the way…in fact, I insist on it lol

    July 22, 2013 at 8:46 pm #186019
    cyberpunk
    Member

    did you guys see the mania kick in at the end there? what a run-on sentence that was lol, That is what it is like in my head. Trust me you do not want to go there lol

    Okay removing the S does fix the issue too I think. now I got a dilemma lol

    July 22, 2013 at 8:51 pm #186018
    Chike
    Member

    I don’t know how you figured the S is a problem but it is so just get rid of it and debig those 3 lines.

  • Author
    Posts

Related

Viewing 15 posts - 106 through 120 (of 143 total)
1 2 3 … 7 8 9 10
  • You must be logged in to reply to this topic.