Failed to Initiate

[simpleviet]

I download everything that was required for the Spht bot to work and made sure that I ment the requirements.

SphtBotv3 requires an operating system with a NT kernel (Windows NT 4.0/2000/XP/Server 2003/Longhorn).
    * Visual Basic 6 runtimes
    * To install the following, simply extract them to your Windows \System32\ directory.
    * MSCOMCTL (Microsoft Windows Common Controls 6.0 SP4)
    * RICHTX32 (Microsoft Rich Textbox Control 6.0)
    * Visual C++ 7 runtimes

I placed the MSCOMCTL, RICHTX32 and both files from Visual C++ 7 runtimes into where the bot files are. In the end, it says "Failed to Initiate". What can I do to get it working?

[Mangix]

it coudlnt have said only failed to initiate. what else?

[simpleviet]

It says " Failed to initalize (Error 7:1000007) Exception caught in Sphtbotv3 (0) Out of memory. I'm not sure what that means.. If it talks about ram.. I have 1 GB of ram.

[Topaz]

Your computer needs more RAM.

[Mangix]

lol if you really have 1GB memory, then this is hillarious as shit. all your other programs must be using all of your 1GB memory

[MyndFyre]

Mangix, when you understand how Windows assigns RAM, come back.  Every program running under Windows has access to a full 4 gb of virtual memory, whether or not the system has it physically.

[PaiD]

MyndFyre: I didnt know that, But how is that possible if the user doesnt have 4gbs?

[MyndFyre]

MyndFyre: I didnt know that, But how is that possible if the user doesnt have 4gbs?

It's been that way since the 386 enabled virtual memory.

(I want to point out that user-mode address space is actually 2gb in Win32 unless you tack on the /3GB switch in your boot.ini file; in 64-bit Windows, it is 8tb.  But this is still true even if you have only 256mb of physical RAM).

[PaiD]

Wow so i have up to 6 tds >.< How big is 1 tb?

[Warrior]

This is done by using swap files which can be saved to the HD and by using a smaller storage space to represent bigger sections of memory, by providing them with rulesets for protection (present/not present, user/supervisor, global/non global, dirty/non dirty, etc..) you can access a full virtual 4GB to make processes appear to be alone in the kernel and whenever you address virtual memory marked as non present you generate a pagefault which usually triggers a new page to be selected from the disk and marked as present.

This is straight off of my head, not at home so can't view the intel docs to verify it down to the last word but that's a rough idea.

Using this it is possible to put your kernel at the 3GB mark and leave anything under 3GB to programs (provided you map the entire kernel into the processes address space)

[Topaz]

tb = 1000 gigabytes

[Blaze]

tb = 1000 gigabytes

1024, unless we are talking about decimal bytes...

[simpleviet]

well none of my programs are using up my 1gb...I have 23 processes and it uses up to 98.8mb that leaves a big gab =D. Plus I am so curious about this 3gb memory..... How will I be able to open it up to have the vast amount of ram? Unless it is already enabled....  For failed initiation...Thats absurd --" So what do I have to do to get this bot working?

[simpleviet]

NM I think it is already enabled. Somehow my computer printed some information about this computer and it states that.... Total Physical Memory - 512.00MB Available Physical Memory 925.2 MB Total Virtual Memory 2.92GB Available Virtual Memory 2.74GB Not sure... Suddenly my computer printed this random crap..

[MyndFyre]

well none of my programs are using up my 1gb...I have 23 processes and it uses up to 98.8mb that leaves a big gab =D. Plus I am so curious about this 3gb memory..... How will I be able to open it up to have the vast amount of ram? Unless it is already enabled....  For failed initiation...Thats absurd --" So what do I have to do to get this bot working?

You don't need to "open it up."  The memory listed as used in Task Manager is what is presently being used in the applications' "working set."  You'll notice that for many GUI-oriented programs, a program uses significantly less memory when it is minimized than when it is displayed.  "Opening it up" as you suggest wouldn't make the programs use any more memory -- that's all they need at the time, and that's good.  Higher memory usage means that, when all of your physical RAM is used, swapping to/from the disk (because these memory "pages" are marked "dirty," which (as Warrior says) triggers a "page fault" which prompts the OS to read the page back from the disk), which is always slower than using physical RAM.  That's why your RAM amount and FSB speed are such critical factors to the speed of your computer, moreso (IMHO) than the type/speed of your processor.

Enabling the /3GB switch won't do anything for user-mode applications unless they are compiled with the /LARGEADDRESSAWARE:YES switch.  They default to using the lower 2gb of virtual address space.

One of the efficient things that Windows (and other OSes including Linux) does is share module code in shared pages.  For example, the same kernel code memory (not necessarily object memory, though) is shared among all processes -- so the pages of memory in the upper 2gb of virtual address space in kernel memory are generally shared among processes, and user-mode code that is shared (such as DLL exports from modules like comctl32.dll, kernel32.dll, user32.dll, etc.) is also shared among processes.