MacroQuest64

PC Specs:
P4 2.8GHz
1GB of RAM
ATI Radeon 9800 Pro

Problem:
The longer the computer is on the load time it takes MacroQuest2 to load increases.

Example:
Steps with loading EverQuest first:
1. Load EverQuest to world or character screen
2. Load MacroQuest2
3. ALT+TAB back into EverQuest
4. Time:
4a. Fresh PC boot it takes .5 second(s) maybe less to load.
4b. two days later it takes 1 - 2 seconds to load.
4c. week later it takes 10 seconds to load.
4d. etc...

Steps with loading MacroQuest2 first:
1. Load MacroQuest2
2. Load EverQuest
3. Time:
3a. Fresh PC boot it takes .5 second(s) maybe less to load.
3b. two days later it takes 1 - 2 seconds to load.
3c. week later it takes 9 - 10 seconds to load.
3d. etc...

Once it loads everything seems to run fine, but I find this to be very annoying.

I reboot now once MacroQuest2 starts taking around 30 seconds to load MacroQuest2.

First, I have to wonder why you're running EQ before the injector...nothing wrong with this per-se, but as it's the injector's job (as such) to "wait for" eqgame.exe to appear in the process list, this is a bit ass-backwards.

Otherwise it's a safe bet that the problem is tied to what the computer's doing during the time it's on..MQ has no code that I know of that says "hrm, it's been another 30 minutes, let's slow things up for lowjack by another 10%"

Things get more fragmented and take longer to execute as you use your computer, that's just how things work. Memory (of all kinds, ram, video ram, hard disk, cpu cache) gets allocated, then it's no longer needed and it gets freed, leaving a hole perhaps not quite big enough for the next needed allocation...is it more efficient to shuffle everything around or just cut of a chunk of a part farther down the list of unused space and work with that? The answer will change as circumstances vary. The OS, drivers, and software all have to work (and often compete) with each other to deal with this issue..some schemes handle it more efficiently than others, and all it takes is one "stray" program along the way to munge things up for the rest unless the OS rules everything with an iron fist, which isn't always convenient. *shrug* My only guess is that something like this is what you're seeing.

I reboot now once MacroQuest2 starts taking around 30 seconds to load MacroQuest2.

Your computer reboots and loads everquest in <30 seconds? Or do you just enjoy poking yourself in the eye? :)

What does dbgview show during the delay?
How much free memory do you have right after boot vs when it takes 30 seconds to load?