Zugg Software :: View topic

Beginner Joined: 13 Aug 2003 Posts: 10

hi
my friend showed me the ctrl+q command, which is suppossed to run all triggers etc in the settings, so u can see how long it takes if it slows u down etc...
His takes about 4 seconds, mine took 40!
I reinstalled and imported some triggers which made it 10-12 seconds
Now, just to try it i deleted all settings i did - #killall -
it takes 4 seconds also to run all triggers etc, which arent here.
After i started making/importing triggers zmud started to slow down again.
I wonder if there is any option/general settings setting which may make it slow
since my friend has a full set of trigs and it still works fast, whereas my zmud just becomes slow with triggers :P

thankx
terl

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

It's probably not taking 4-40 seconds (check it with a watch). The number displayed at the end of the test isn't seconds, milliseconds seems more likely.

If your friend's computer takes 4 with a "full" set of triggers, and yours takes 4 with no triggers, then your friend's computer is faster than yours and it doesn't do much good to compare his speed with yours. If your triggers are causing noticeable lag, you'll already know that without using Ctrl-Q. If they aren't, it doesn't really matter how long Ctrl-Q takes.

Beginner Joined: 13 Aug 2003 Posts: 10

hi. Thanks lightbulb for your reply.

i'm aware of the miliseconds, i was actually checking both - the connect time and the time in miliseconds -
anyways nevermind this!
My biggest problem atm is the re-occuring crashes!!
always a fault in the stack something or other.. i paste:

ZMUD caused an invalid page fault in
module ZMUD.EXE at 016f:0040bbdd.
Registers:
EAX=00b48f0c CS=016f EIP=0040bbdd EFLGS=00010213
EBX=00000001 SS=0177 ESP=00b47ed0 EBP=00b48ecc
ECX=00b48f34 DS=0177 ESI=1a7c9fb4 FS=3e4f
EDX=1a7c9fb4 ES=0177 EDI=2ab01420 GS=0000
Bytes at CS:EIP:
50 83 c4 f4 53 56 89 4d f8 89 55 fc 8b f0 bb 02
Stack dump:

Could some1 who knows error messages tell me what this is about or point me to some link of error messages?

Thank you
Terl

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Frequent crashes are generally caused by a driver/interface w/ driver problem. Since no one (even Microsoft) can test all driver interfaces we will assume that the interface follows standards.

The particular operation at which it failed was a MOV which shows a memory assignment/pointer problem. Since all the segment and address pointers look valid (allocations can varily vastly even in systems running the same OS) I would have to suggest that this is due to a driver or API DLL problem. Check for updates to your system.