Make your application startup on system startup

KEY_LOCAL_MACHINE\Init contains executables to run during device startup. Executables are listed under LaunchXX keys, where XX determines the run order to use. Another key, DependXX, allows specifying dependencies (ie. Launch50 can’t run unless Launch40 was successful).

Create a new key under HKEY_LOCAL_MACHINE\Init named Launch60 (or anything greater than Launch50) , and supply the executable name to run. If you want the exe to launch only if the shell successfully started, create Depend60 and set the value to 32h (hex for 50).

An easier way to start an application on system startup is to put a link to your application in the \Windows\StartUp folder.

2.to change the size of the object store

The functions GetSystemMemoryDivision and SetSystemMemoryDivision allow you to change the relationship between memory and the object store.

The prototypes are:

BOOL GetSystemMemoryDivision(LPDWORD storePages, LPDWORD ramPages, LPDWORD pageSize);

DWORD SetSystemMemoryDivision(DWORD storePages);

The function returns SYSMEM_CHANGED if executed successfully.
The function returns SYSMEM_FAILED if storePages is out of range.
If SYSMEM_FAILED is returned, you can get further information by calling GetLastError.
If a reboot is necessary for the change to take effect, the function returns SYSMEM_MUSTREBOOT.
If a previous call returned SYSMEM_MUSTREBOOT, the function returns SYSMEM_REBOOTPENDING. In this situation, the boundary cannot be adjusted further until the reboot occurs.

You cannot shrink system memory or the object store memory beyond 256K each, including space for existing files and records.