Don't know if this is the latest patch, or a setting I've changed in Innerspace. In the last couple of days I've noticed my framerate has dropped right down.
Now I did turn off the Innerspace FPS limiters earlier in the week to see how my boxed toon worked on my 2nd processor, but since then I've put everything back how it used to be.
If I load the game without Innerspace it seems smoother, no figures but it feels like it's running at the normal 25-40 fps. When I load it through Innerspace I'm averaging 10 fps and the game is noticably choppy.
Anybody else with EQ1 able to test this out? Have I messed something up or is it SoE?
EQ 1 suddenly very choppy? 8-12 fps
Moderators: Lavish Software Team, Moderators
Are you sure you put the FPS limiters back how they used to be? Foreground should be limit of 60, in Calculate mode. Background should be 30, in Constant mode -- though you can switch that to Calculate mode for better background performance (which helps for background autofollow)
I logged in real quick to check, and I'm getting 40 FPS in the nexus.
I logged in real quick to check, and I'm getting 40 FPS in the nexus.
Well I found out what's causing the problem and it does seem to be linked to Innerspace. It wasn't drivers or a patch though, it's enabling dual screen mode on my graphics card 
Without Innerspace, EQ runs fine whether I'm running in single or dual screen mode. Innerspace however, with just a single EQ session loaded, and with that session running at the same resolution on the same screen, reports 45-50fps in single screen mode and 10-15fps in dual screen mode. All that I need to do to see a fourfold decrease in performance is enable the 2nd monitor by clicking "Extend my windows desktop onto this monitor". I don't have any extra programs running, and there's not even anything on screen on the 2nd monitor.
I'm not low on memory (1.5GB free even with both EQ sessions running), and it doesn't seem to be CPU related. There is higher CPU usage when IS is loaded, but not enough to explain a fourfold decrease in performance. With IS, average CPU usage with IS looks to be around 95% for core 1, and 25% for core 2. Without IS, it's nearer 90% core 1, 10% core 2.
I'm running an ATI Radeon 1950Pro graphics card. It's a dual head card, so even with two screens active I'm using the same drivers, etc...
The only other post I can find talking about dual screen fps is this one, posting it for my own reference really - other than general DirectX info it doesn't seem too relevant:
http://www.lavishsoft.com/forum/viewtop ... screen+fps
Without Innerspace, EQ runs fine whether I'm running in single or dual screen mode. Innerspace however, with just a single EQ session loaded, and with that session running at the same resolution on the same screen, reports 45-50fps in single screen mode and 10-15fps in dual screen mode. All that I need to do to see a fourfold decrease in performance is enable the 2nd monitor by clicking "Extend my windows desktop onto this monitor". I don't have any extra programs running, and there's not even anything on screen on the 2nd monitor.
I'm not low on memory (1.5GB free even with both EQ sessions running), and it doesn't seem to be CPU related. There is higher CPU usage when IS is loaded, but not enough to explain a fourfold decrease in performance. With IS, average CPU usage with IS looks to be around 95% for core 1, and 25% for core 2. Without IS, it's nearer 90% core 1, 10% core 2.
I'm running an ATI Radeon 1950Pro graphics card. It's a dual head card, so even with two screens active I'm using the same drivers, etc...
The only other post I can find talking about dual screen fps is this one, posting it for my own reference really - other than general DirectX info it doesn't seem too relevant:
http://www.lavishsoft.com/forum/viewtop ... screen+fps
Ok, after reading that thread I've done some more testing. It seems it is the DirectX problem after all.
I loaded WinEQ2 instead of Innerspace, and loaded both characters from there. Even with dual screen mode active it worked perfectly with frame rates as high as 45fps. However both sessions were running on the primary display and as soon as I dragged my boxed char to my 2nd monitor frame rates on both dropped to 11fps.
I'd seen the Display settings in WinEQ2 though, so quit out and configured it to load one session on the primary display, and the other on the secondary. This time each copy of EQ started on the correct screen and each could hit 45fps without problems.
That also solved my autofollow problems. Loading EQ on it's own or through Innerspace I can't autofollow at all with my boxed account. Using WinEQ2, autofollow stuck like glue although the screen on the background session was very choppy, it reported 17fps but looked more like 1-2. I can live with that though if autofollow works!
So, it looks like I have two questions:
I loaded WinEQ2 instead of Innerspace, and loaded both characters from there. Even with dual screen mode active it worked perfectly with frame rates as high as 45fps. However both sessions were running on the primary display and as soon as I dragged my boxed char to my 2nd monitor frame rates on both dropped to 11fps.
I'd seen the Display settings in WinEQ2 though, so quit out and configured it to load one session on the primary display, and the other on the secondary. This time each copy of EQ started on the correct screen and each could hit 45fps without problems.
That also solved my autofollow problems. Loading EQ on it's own or through Innerspace I can't autofollow at all with my boxed account. Using WinEQ2, autofollow stuck like glue although the screen on the background session was very choppy, it reported 17fps but looked more like 1-2. I can live with that though if autofollow works!
So, it looks like I have two questions:
- 1. Is there any way to force sessions to a particular monitor as they load? It seems DirectX doesn't like you changing monitor after a program has started.
2. Is there any way to run WinEQ2 within Innerspace and use that to manage the FPS throttling to fix my autofollow?
lol, think I just found it.
There's a setting in EQ1 'allow window resizing'. On a hunch I enabled that and shrunk the window down so it fits perfectly in screen 1. As soon as I did that the frame rates shot up and I'm getting a solid 45fps. Still getting slower results than WinEQ2 with both accounts loaded, but it's a huge improvement.
It seems that EQ with window resizing turned off, is slightly bigger than you can fit on a single monitor (probably to hide the resize elements...).
WTG SoE
There's a setting in EQ1 'allow window resizing'. On a hunch I enabled that and shrunk the window down so it fits perfectly in screen 1. As soon as I did that the frame rates shot up and I'm getting a solid 45fps. Still getting slower results than WinEQ2 with both accounts loaded, but it's a huge improvement.
It seems that EQ with window resizing turned off, is slightly bigger than you can fit on a single monitor (probably to hide the resize elements...).
WTG SoE
Inner Space will allow you to launch the game on a specific display much the same way WinEQ will. If you create an additional profile for EverQuest, the profile configuration has a display option, which defaults to Application-controlled (e.g. what the game picks is what it uses). You can select the secondary display for any given profile.
When you drag a Direct3D window from one monitor to the other in Windows XP, it becomes software rendered instead of hardware rendered. This is because Direct3D9 assumes that the displays are handled by different video cards (in other words, it does not separately handle the case where your video card has dual outputs). On Windows Vista on the other hand, video resources are managed differently, and so it is actually possible to have full hardware rendering when dragging the game window to the other monitor, or even on both monitors, as long as it's using a dual output video card.
Also, for keeping your session on one monitor, both WinEQ 2 and Inner Space have window sizing features that work with or without the blessing of the game. You can hit SHIFT+ALT+F (default) in either to use "full screen emulation", which sizes the window perfectly to your desktop resolution.
When you drag a Direct3D window from one monitor to the other in Windows XP, it becomes software rendered instead of hardware rendered. This is because Direct3D9 assumes that the displays are handled by different video cards (in other words, it does not separately handle the case where your video card has dual outputs). On Windows Vista on the other hand, video resources are managed differently, and so it is actually possible to have full hardware rendering when dragging the game window to the other monitor, or even on both monitors, as long as it's using a dual output video card.
Also, for keeping your session on one monitor, both WinEQ 2 and Inner Space have window sizing features that work with or without the blessing of the game. You can hit SHIFT+ALT+F (default) in either to use "full screen emulation", which sizes the window perfectly to your desktop resolution.
Thanks, I must have missed that setting while looking through all this, I'll go create a 2nd profile tonight. That resizing feature sounds perfect too, I thought it switched the game to full screen mode, didn't realise it just resizes it.
Do you know if there's any way I can run WinEQ2 inside Innerspace? The frame rates using that were far higher, and autofollow worked better too. If I could use WinEQ2 for managing the frame rates and Innerspace for everything else that would be perfect for me.
Do you know if there's any way I can run WinEQ2 inside Innerspace? The frame rates using that were far higher, and autofollow worked better too. If I could use WinEQ2 for managing the frame rates and Innerspace for everything else that would be perfect for me.
You cannot run WinEQ 2 through IS, no. However, here's some information that will help you.
The sole difference between WinEQ 2 and Inner Space's FPS limiting features is that WinEQ 2 comes with EQPlayNice, and EQPlayNice has an EQ-specific Rendering Limiting feature. EQPlayNice is compatible with Inner Space, and in fact, if you have WinEQ 2 running in the system tray, EQPlayNice is FPS limiting every session of EverQuest. This means that not only would Inner Space be applying FPS limiting, so would EQPlayNice, and this is the only reason your FPS might be different between the two if you have them both set to use the same settings.
So here's what you can do:
1. Have WinEQ 2 running in the system tray so that EQPlayNice is doing the framerate limiting in EverQuest
2. Disable Inner Space's FPS limiting
Then your framerate should be identical to what it would be if you were using WinEQ 2.
The sole difference between WinEQ 2 and Inner Space's FPS limiting features is that WinEQ 2 comes with EQPlayNice, and EQPlayNice has an EQ-specific Rendering Limiting feature. EQPlayNice is compatible with Inner Space, and in fact, if you have WinEQ 2 running in the system tray, EQPlayNice is FPS limiting every session of EverQuest. This means that not only would Inner Space be applying FPS limiting, so would EQPlayNice, and this is the only reason your FPS might be different between the two if you have them both set to use the same settings.
So here's what you can do:
1. Have WinEQ 2 running in the system tray so that EQPlayNice is doing the framerate limiting in EverQuest
2. Disable Inner Space's FPS limiting
Then your framerate should be identical to what it would be if you were using WinEQ 2.
Bleh, EQPlayNice was what I meant. Sorry, not used to thinking of it as separate from WinEQ 
I was actually trying that yesterday having seen you say the same to somebody else (in a 2005 thread lol), but WinEQ has been crashing every time I attempt it. I'll re-install both programs tonight and see if that resolves the crashing.
I was actually trying that yesterday having seen you say the same to somebody else (in a 2005 thread lol), but WinEQ has been crashing every time I attempt it. I'll re-install both programs tonight and see if that resolves the crashing.
Ok, re-installing WinEQ2 didn't solve the crashing, but re-installing InnerSpace afterwards did seem to cure it.
I'm getting occasional EQPlayNice timeouts if I tab to something else while launching the 2nd session, but I I don't think there's any pressing need for you to look into that - it seems to work ok otherwise.
Before I re-installed it was crashing all over the place. I'm guessing that's because I installed WinEQ2 after Innerspace. I probably didn't have a problem before because I was careful not to run the two together, but if you're going to have them both loaded it seems it's important to have Innerspace installed last.
Just in case it's helpful to someone else in the future I'll report the details here. Before I re-installed it was working occasionally (maybe 1 time in 5), but most of the time it was taking ages to start EQ, and then crashing out before the logon screen even appeared.
The full text of the crash dump from when that happened is:
Many, many thanks for all your help Lax. Hopefully that's me all sorted now so you won't need to babysit me so much 
I'm getting occasional EQPlayNice timeouts if I tab to something else while launching the 2nd session, but I I don't think there's any pressing need for you to look into that - it seems to work ok otherwise.
Before I re-installed it was crashing all over the place. I'm guessing that's because I installed WinEQ2 after Innerspace. I probably didn't have a problem before because I was careful not to run the two together, but if you're going to have them both loaded it seems it's important to have Innerspace installed last.
Just in case it's helpful to someone else in the future I'll report the details here. Before I re-installed it was working occasionally (maybe 1 time in 5), but most of the time it was taking ages to start EQ, and then crashing out before the logon screen even appeared.
The full text of the crash dump from when that happened is:
Code: Select all
Software: Inner Space Session 1.09 (Sat Dec 08 14:39:30 2007)
Crash: 0x040041D7: Exception 0xc0000005 writing to address 0x00000000 in module InnerSpace.dll
Registers:
-----------------------------------
eax=00000000 ebx=7C801AD0 ecx=0013EE78 edx=0000000B
edi=01FD0000 esi=00000000 ebp=01A724F0 esp=0013EE58
Stack:
-----------------------------------
0013EE78 01A75228 01A7521C 4794FB11 01A33681 00000002 01A75228 00000070
00000000 04055728 FFFFFFFF 01A32BC0 00000001 04004160 04055728 0013EE7C
00000000 0013FF64 00000000 0000007C 0000000B 01A7521C 01A43894 FFFFFFFF
01A30001 00000000 01A4387C 00161F08 FFFFFFFF 00000000 00000000 00000000
00000000 00000000 00000000 01A73FE8 00000000 00000800 00000000 00000000
00000000 00000000 01A43884 00000000 006E006F 00161F30 FFFFFFFF 00000000
00000000 00000000 00000000 00161F58 FFFFFFFF 00000000 00000000 00000000
00000000 00000000 78656E55 74636570 4D206465 28206773 20293931 00000045
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 6E755200 676E696E 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 BB735B05 040050B3 0000000A 0403190C 04004160 04055728
01C42280 FFFFFFFF 006CC669 000000BF 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 0013F0E4
00000000 7C9105C8 00154280 0013F1B0 7C910551 00151CA8 7C91056D 00000000
00000000 00154288 0000A953 0013F0F4 7C90EE18 0013F180 7C90EE18 7C913290
FFFFFFFF 7C913288 7C9166F1 00000001 0A8C005B 7C91657E 00000000 00000000
00154288 02160054 7C97CE28 00000000 00000000 02080000 000003B0 7C97CE28
7FFDFC54 7FFDFC54 0A8C005B 0013F100 7FFDFC4E 00000000 00251EC0 0180E3DC
00150000 7C80E038 0013F1EC 7C90EE18 7C9166B0 FFFFFFFF 0001657E 00000076
0013F0F4 00154288 0013F1EC 7C90EE18 7C910570 FFFFFFFF 7C91056D 7C80E68F
00150000 00000000 7C80E4A4 00000000 7FFDFC00 00000002 7FFDF000 00000000
00154288 0013F440 00400000 0013F1C4 0013F3B4 0013F670 7C839AA8 7C80E4A8
FFFFFFFF 7C80E4A4 7C80E5AB 7C80E62B 01C42280 7C80DDF5 000000BF 01000000
00000000 7FFDF000 7FFDF000 0013F6A0 00000000 00000000 00560054 7FFDFC00
02080000 0013F45C 02080000 0013F254 00000000 00000000 00400000 0013F2F0
0013F2F0 00000020 00000020 00000020 00F100F0 00F300F2 00F500F4 00F700F6
00F900F8 00FB00FA 00FD00FC 00FF00FE 00000100 01C42D58 003A0043 0050005C
006F0072 00720067 006D0061 00460020 006C0069 00730065 0053005C 006E006F
005C0079 00760045 00720065 00750051 00730065 005C0074 00710065 00610067
0065006D 0065002E 00650078 00130000 7C90EE18 0013F360 00650000 006E0072
006C0065 7C913281 7C913288 00000000 7C97D04A 7C97CE28 0000A953 0013F304
7C90EE18 0013F390 7C90EE18 7C913290 FFFFFFFF 7C913288 7C9166F1 00000001
0A8C0054 7C91657E 00000000 00000000 00000002 02160018 7C97CE28 00000000
00000000 02080000 7C97CC20 7C97CE28 7FFDFC10 7FFDFC10 0A8C0054 7C916500
00000000 00000000 00251FC0 0113F410 0013F340 0013F3DC 0013F3FC 7C90EE18
7C9166B0 FFFFFFFF 7C91657E 7C91659E 00000001 00000001 00000000 0013F440
0013F3F0 0013F40C 7C80E494 00000001 00000000 0013F440 7C80E4A4 00000000
7FFDFC00 00000002 0013F414 00150000 7C910732 00000007 001507D8 00150000
001550E0 0013F3EC 7C839AA8 0013F630 7C90EE18 7C910738 FFFFFFFF 7C910732
7C9106AB 7C9106EB 0013F694 0013F68C 00000000 7FFDF000 7C90D4EA 7C9116FF
FFFFFFFF 0013F644 00000000 7C92812F 01C40608 7C9106EB 003B0000 00000000
7C9105D4 000000BF 7C800000 7C800000 03010302 02100248 02100210 02100210
02100210 02100210 02100312 02100210 02100210 02100210 02140214 03120210
02100210 02140210 02100312 02100210 02100210 03010301 03010301 03010301
03010301 03010301 03010301 03010301 03010301 03010301 01C40050 03010301
01C40050 00000000 01C50000 03010301 03020301 00150640 03020302 03020302
03020302 03020302 7C90E288 7C801875 00000144 00000000 00000000 00000000
0013F540 01C50020 003B0000 00000000 7C801898 04056880 000000A8 00000000
0F0E0D0C 13121110 00000000 003B0000 00000008 23222120 0013F52C 01C40520
0013F5E0 7C839AA8 7C90DA54 7C918331 FFFFFFFF 0013F624 0013F63C 00008000
01C40000 01C50000 00000000 0013F658 0013F598 00000000 7C9105C8 01C42278
0013F664 7C910551 01C40778 7C91056D 01C42280 01C42280 000000BF 040293C0
040293C8 BFE268CC 00000000 000000A8 04056880 7C90D592 00000000 00000003
00000000 04020F6D 01C40050 01C42704 01C40050 01C50000 0402105C BFE26B00
00008000 0403C030 00000000 00000028 00000000 0013F5F4 003B0000 0013F66C
0401B6E0 BBF212F4 01C40000 01C50000 0401AAA0 01C40000 00000000 00000000
00010FA0 003B1000 0013F59C 0001F690 00000005 0013F5A8 7C910570 0013F694
Module addresses in stack:
-----------------------------------
Lavish.dll+3681
InnerSpace.dll+55728
Lavish.dll+2BC0
InnerSpace.dll+4160
InnerSpace.dll+55728
Lavish.dll+13894
Lavish.dll+1
Lavish.dll+1387C
Lavish.dll+13884
eqgame.exe+2E006F
InnerSpace.dll+50B3
InnerSpace.dll+3190C
InnerSpace.dll+4160
InnerSpace.dll+55728
eqgame.exe+2CC669
ntdll.dll+105C8
ntdll.dll+10551
ntdll.dll+1056D
ntdll.dll+EE18
ntdll.dll+EE18
ntdll.dll+13290
ntdll.dll+13288
ntdll.dll+166F1
ntdll.dll+1657E
ntdll.dll+7CE28
ntdll.dll+7CE28
kernel32.dll+E038
ntdll.dll+EE18
ntdll.dll+166B0
ntdll.dll+EE18
ntdll.dll+10570
ntdll.dll+1056D
kernel32.dll+E68F
kernel32.dll+E4A4
kernel32.dll+39AA8
kernel32.dll+E4A8
kernel32.dll+E4A4
kernel32.dll+E5AB
kernel32.dll+E62B
kernel32.dll+DDF5
eqgame.exe+160054
js3250.dll+60043
eqgame.exe+10005C
eqgame.exe+2F0072
eqgame.exe+320067
eqgame.exe+2D0061
eqgame.exe+60020
eqgame.exe+2C0069
eqgame.exe+330065
eqgame.exe+13005C
eqgame.exe+2E006F
eqgame.exe+1C0079
eqgame.exe+360045
eqgame.exe+320065
eqgame.exe+350051
eqgame.exe+330065
eqgame.exe+1C0074
eqgame.exe+310065
eqgame.exe+210067
eqgame.exe+25006D
eqgame.exe+25002E
eqgame.exe+250078
ntdll.dll+EE18
eqgame.exe+250000
eqgame.exe+2E0072
eqgame.exe+2C0065
ntdll.dll+13281
ntdll.dll+13288
ntdll.dll+7D04A
ntdll.dll+7CE28
ntdll.dll+EE18
ntdll.dll+EE18
ntdll.dll+13290
ntdll.dll+13288
ntdll.dll+166F1
ntdll.dll+1657E
ntdll.dll+7CE28
ntdll.dll+7CC20
ntdll.dll+7CE28
ntdll.dll+16500
ntdll.dll+EE18
ntdll.dll+166B0
ntdll.dll+1657E
ntdll.dll+1659E
kernel32.dll+E494
kernel32.dll+E4A4
ntdll.dll+10732
kernel32.dll+39AA8
ntdll.dll+EE18
ntdll.dll+10738
ntdll.dll+10732
ntdll.dll+106AB
ntdll.dll+106EB
ntdll.dll+D4EA
ntdll.dll+116FF
ntdll.dll+2812F
ntdll.dll+106EB
ntdll.dll+105D4
ntdll.dll+E288
kernel32.dll+1875
kernel32.dll+1898
InnerSpace.dll+56880
kernel32.dll+39AA8
ntdll.dll+DA54
ntdll.dll+18331
ntdll.dll+105C8
ntdll.dll+10551
ntdll.dll+1056D
InnerSpace.dll+293C0
InnerSpace.dll+293C8
InnerSpace.dll+56880
ntdll.dll+D592
InnerSpace.dll+20F6D
InnerSpace.dll+2105C
InnerSpace.dll+3C030
InnerSpace.dll+1B6E0
InnerSpace.dll+1AAA0
plc4.dll+1000
ntdll.dll+10570
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.070227-2254
System Physical RAM: 2448/3326MB
Page File: 3162/3932MB
Virtual Memory: 1987/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) D CPU 2.66GHz @ 2666MHz
CPU 2: Intel(R) Pentium(R) D CPU 2.66GHz @ 2666MHz
CPU Affinity Mask: 0x3
Video 1: //./DISPLAY1/Radeon X1950 Pro
Video 2: //./DISPLAY2/Radeon X1950 Pro Secondary
Video 3: //./DISPLAYV1/LogMeIn Mirror Driver
Video 4: //./DISPLAYV2/NetMeeting driver
Video 5: //./DISPLAYV3/RDPDD Chained DD
Sound: Logitech USB Headset
DirectX: 4.09.00.0904
Internet Explorer: 7.0.5730.11
Loaded Modules:
-----------------------------------
Module 0x00330000-0x00339000: C:/WINDOWS/system32/Normaliz.dll (Thu Jun 29 15:05:42 2006)
Module 0x00340000-0x003A8000: C:/Program Files/Sony/EverQuest/js3250.dll (Fri Jan 26 02:56:04 2007)
Module 0x003B0000-0x003B8000: C:/Program Files/Sony/EverQuest/plc4.dll (Fri Jan 26 02:53:41 2007)
Module 0x003C0000-0x003C6000: C:/Program Files/Sony/EverQuest/plds4.dll (Fri Jan 26 02:53:37 2007)
Module 0x00400000-0x00A05000: C:/Program Files/Sony/EverQuest/eqgame.exe (Thu Jan 17 00:27:49 2008)
Module 0x00A10000-0x00C70000: C:/WINDOWS/system32/d3dx9_30.dll (Fri Mar 31 19:32:20 2006)
Module 0x019C0000-0x01A05000: C:/Program Files/WinEQ2/EQPlayNice.dll (Fri Nov 16 19:28:10 2007)
Module 0x01A30000-0x01A4E000: C:/Program Files/WinEQ2/Lavish.dll (Tue Oct 30 17:12:23 2007)
Module 0x01BF0000-0x01BFF000: C:/Program Files/Logitech/SetPoint/lgscroll.dll (Tue Apr 24 01:41:39 2007)
Module 0x04000000-0x0405D000: C:/Program Files/InnerSpace/InnerSpace.dll (Sat Dec 08 14:39:30 2007)
Module 0x05000000-0x05148000: C:/Program Files/InnerSpace/ISUI.dll (Mon Aug 20 16:25:03 2007)
Module 0x10000000-0x1063B000: C:/Program Files/Sony/EverQuest/xul.dll (Fri Jan 26 03:38:38 2007)
Module 0x21100000-0x2115F000: C:/Program Files/Sony/EverQuest/mss32.dll (Tue Jul 09 21:33:51 2002)
Module 0x30000000-0x30028000: C:/Program Files/Sony/EverQuest/nspr4.dll (Fri Jan 26 02:53:36 2007)
Module 0x42990000-0x429D5000: C:/WINDOWS/system32/iertutil.dll (Wed Oct 10 23:55:57 2007)
Module 0x42C10000-0x42CDF000: C:/WINDOWS/system32/WININET.dll (Wed Oct 10 23:56:00 2007)
Module 0x5AD70000-0x5ADA8000: C:/WINDOWS/system32/uxtheme.dll (Wed Aug 04 07:56:43 2004)
Module 0x5D090000-0x5D12A000: C:/WINDOWS/system32/COMCTL32.dll (Fri Aug 25 15:45:58 2006)
Module 0x662B0000-0x66308000: C:/WINDOWS/system32/hnetcfg.dll (Wed Aug 04 07:56:16 2004)
Module 0x6CE10000-0x6CE48000: C:/WINDOWS/system32/DINPUT8.dll (Wed Aug 04 07:56:32 2004)
Module 0x71A50000-0x71A8F000: C:/WINDOWS/system32/mswsock.dll (Wed Aug 04 07:59:20 2004)
Module 0x71A90000-0x71A98000: C:/WINDOWS/System32/wshtcpip.dll (Wed Aug 04 07:57:49 2004)
Module 0x71AA0000-0x71AA8000: C:/WINDOWS/system32/WS2HELP.dll (Wed Aug 04 07:57:39 2004)
Module 0x71AB0000-0x71AC7000: C:/WINDOWS/system32/WS2_32.dll (Wed Aug 04 07:57:38 2004)
Module 0x71AD0000-0x71AD9000: C:/WINDOWS/system32/WSOCK32.dll (Wed Aug 04 07:57:51 2004)
Module 0x71BF0000-0x71C03000: C:/WINDOWS/system32/SAMLIB.dll (Wed Aug 04 07:56:29 2004)
Module 0x73000000-0x73026000: C:/WINDOWS/system32/WINSPOOL.DRV (Wed Aug 04 07:56:38 2004)
Module 0x74720000-0x7476B000: C:/WINDOWS/system32/MSCTF.dll (Wed Aug 04 07:57:30 2004)
Module 0x76390000-0x763AD000: C:/WINDOWS/system32/IMM32.dll (Wed Aug 04 07:56:30 2004)
Module 0x763B0000-0x763F9000: C:/WINDOWS/system32/comdlg32.dll (Wed Aug 04 07:56:32 2004)
Module 0x76B40000-0x76B6D000: C:/WINDOWS/system32/WINMM.dll (Wed Aug 04 07:57:10 2004)
Module 0x76BF0000-0x76BFB000: C:/WINDOWS/system32/PSAPI.DLL (Wed Aug 04 07:56:58 2004)
Module 0x76D60000-0x76D79000: C:/WINDOWS/system32/iphlpapi.dll (Fri May 19 12:59:41 2006)
Module 0x76F20000-0x76F47000: C:/WINDOWS/system32/DNSAPI.dll (Mon Jun 26 17:37:10 2006)
Module 0x76F60000-0x76F8C000: C:/WINDOWS/system32/WLDAP32.dll (Wed Aug 04 07:56:43 2004)
Module 0x76FB0000-0x76FB8000: C:/WINDOWS/System32/winrnr.dll (Wed Aug 04 07:56:35 2004)
Module 0x76FC0000-0x76FC6000: C:/WINDOWS/system32/rasadhlp.dll (Mon Jun 26 17:37:10 2006)
Module 0x773D0000-0x774D3000: C:/WINDOWS/WinSxS/x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03/comctl32.dll (Fri Aug 25 15:45:55 2006)
Module 0x774E0000-0x7761D000: C:/WINDOWS/system32/ole32.dll (Tue Jul 26 04:39:47 2005)
Module 0x77690000-0x776B1000: C:/WINDOWS/system32/NTMARTA.DLL (Wed Aug 04 07:57:02 2004)
Module 0x77C00000-0x77C08000: C:/WINDOWS/system32/VERSION.dll (Wed Aug 04 07:56:39 2004)
Module 0x77C10000-0x77C68000: C:/WINDOWS/system32/msvcrt.dll (Wed Aug 04 07:59:14 2004)
Module 0x77DD0000-0x77E6B000: C:/WINDOWS/system32/ADVAPI32.dll (Wed Aug 04 07:56:23 2004)
Module 0x77E70000-0x77F01000: C:/WINDOWS/system32/RPCRT4.dll (Mon Jul 09 13:16:16 2007)
Module 0x77F10000-0x77F57000: C:/WINDOWS/system32/GDI32.dll (Tue Jun 19 13:31:19 2007)
Module 0x77F60000-0x77FD6000: C:/WINDOWS/system32/SHLWAPI.dll (Mon Oct 23 15:34:21 2006)
Module 0x78130000-0x781CB000: C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700/MSVCR80.dll (Sat Dec 02 06:50:32 2006)
Module 0x7C340000-0x7C396000: C:/Program Files/Sony/EverQuest/MSVCR71.dll (Fri Feb 21 12:42:20 2003)
Module 0x7C420000-0x7C4A7000: C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700/MSVCP80.dll (Sat Dec 02 06:52:56 2006)
Module 0x7C800000-0x7C8F5000: C:/WINDOWS/system32/kernel32.dll (Mon Apr 16 15:52:53 2007)
Module 0x7C900000-0x7C9B0000: C:/WINDOWS/system32/ntdll.dll (Wed Aug 04 07:56:36 2004)
Module 0x7C9C0000-0x7D1D7000: C:/WINDOWS/system32/SHELL32.dll (Fri Oct 26 03:33:59 2007)
Module 0x7E410000-0x7E4A0000: C:/WINDOWS/system32/USER32.dll (Thu Mar 08 15:36:28 2007)