Topic: Vista users.. Need testers to verify Vista Fix for Dynaverse

[Lepton]

I tried to run starfleetop.exe from CompatAdmin with your fixes.  When I clicked Log In after clicking multiplayer, it crashed to desktop.

[Bonk]

Dumb question, how does one apply these fixes that you've enclosed in the sdb file?  I've opened the file in the Compatibility Administrator, but I don't see any option to apply the fixes other than running the starfleetop.exe from the CompatAdmin.

I think that is it, just select the "Starfleet Command Orion Pirates" entry in the Custom database in the Compat admin, the select the StarFleetOP.exe in the pane on the right and press the run button in the toolbar. I have not had a chance to test and see if these compaitibilty shims remain in place when the Compat Admin is not running. (If so there should be a console window that pops up and disappears as you start OP from outside the compat admin  - but you may need to edit the StarFleetOP.exe entry to point to your install location for that to work - pure speculation - also note none of these settings has provided the desired effect, but the NoVirtualisation setting can only help as far as I am concerned)

[Bonk]

I tried to run starfleetop.exe from CompatAdmin with your fixes.  When I clicked multiplayer, it crashed to desktop.

Interesting, it does not crash for me with these settings. Try removing a bunch of the fixes, and just leave the straightforward ones, novirtualisation, nothemes, noanimations, etc... if you don't know what a fix means try removing it. THere may be fixes there that do not apply to your setup (i.e. if you have disabled aero.. etc.)

Part of what we are dealing with here is that Vista is not one operating system, but many, as evidenced by the various states of crippledness (if you will) of each version.

Which version of Vista do you have?

Also bear in mind I have had no success as yet, this is all trial and error.

[FCM_SFHQ_XC]

humm, well I've only had a little time to work with this, but I'm getting more stable results by starting via the default of SFCOP.exe instead of StarfleetOP.exe o.O
So far though I move slower then usual in movement, but nothing really bad(doesn't lag at all, just takes about an extra second to move from hex to hex then it did on XP).. no lag when coming out of missions either.
so far the only thing Vista really takes its time with is when I move at the same time news generates..
will continue testing

[Bonk]

That sounds promising, but I have had similar experiences, randomly serverlist login works sometimes and not others, sometimes movement and supply is fine and not others...

I'm trying this approach now:

Stopped Services:

Windows Firewall
UPnP Device Host (+ Windows Media Network Sharing Service)
Base Filtering Engine (+ IPSec Policy Agent + IKE and AuthIP IPsec Keying Modules)

A non-crippled version of vista should be able to configure these services with policies instead of just stopping the services.

[Bonk]

I've removed the XP sockets dlls from my OP folder.

Stopping those services is getting me past the firewall check reliably now (was having a heck of a time all night with that).

I'm paring down my compatibilty fixes list. (Lepton, there is a service that chaches them and applies them I believe - so they should still be in effect when riining StarFleetOP.exe from outside the compat admin).

But now the security check won't start and I get the countdoen on server login. I'll try restarting the Base Filtering Engine (+ IPSec Policy Agent + IKE and AuthIP IPsec Keying Modules) services, but leaving the Windows Firewall and UPnP Device host stopped.

[Bonk]

I tried to run starfleetop.exe from CompatAdmin with your fixes.  When I clicked Log In after clicking multiplayer, it crashed to desktop.

Note, I'm running the CompatAdmin as admin.

I'm not having much luck tonight though, I starting to think that running under Wine on Kubuntu is a better bet. There have been a number of new Wine versions since I last tested it.

I'll keep kicking Vista around for a while though. I think I better cleanup, reboot and start fresh in the morning though, as now I cannot even get logged into the server.

[FCM_SFHQ_XC]

Keep trying. It takes me about 2 or 3 "join" attemts before it lets me in.. sometimes it starts to "initilize security" right away, but most of the time I'm finding it take 2 to 3, sometimes up to 5 before it'll do it. Usually initilizes around counter countdown between 1:45-1:27 for me.

[Bonk]

Keep trying. It takes me about 2 or 3 "join" attemts before it lets me in.. sometimes it starts to "initilize security" right away, but most of the time I'm finding it take 2 to 3, sometimes up to 5 before it'll do it. Usually initilizes around counter countdown between 1:45-1:27 for me.

I'm considering that a compatibility failure, similar to the behaviour observed when actually logged in.

But I will definitely give it another round tomorrow. So far, Vista 1, Bonk 0. 

[Bonk]

I'm going to try an be a little more systematic about it today. Here is the list of dependencies of StarFleetOP.exe on Vista (generated by PE Explorer):

// File name: C:\SFC\Taldren Software Inc\Starfleet Command Orion Pirates\StarFleetOP.exe
// Created  : 22:11:2008 08:23
// Type     : Dependencies


activeds.dll      c:\windows\system32\activeds.dll
adsldpc.dll      c:\windows\system32\adsldpc.dll
advapi32.dll      c:\windows\system32\advapi32.dll
advpack.dll      c:\windows\system32\advpack.dll
apphelp.dll      c:\windows\system32\apphelp.dll
atl.dll         c:\windows\system32\atl.dll
authz.dll      c:\windows\system32\authz.dll
bcrypt.dll      c:\windows\system32\bcrypt.dll
browseui.dll      c:\windows\system32\browseui.dll
cabinet.dll      c:\windows\system32\cabinet.dll
certcli.dll      c:\windows\system32\certcli.dll
cfgmgr32.dll      c:\windows\system32\cfgmgr32.dll
clbcatq.dll      c:\windows\system32\clbcatq.dll
comctl32.dll      c:\windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6001.18000_none_5cdbaa5a083979cc\comctl32.dll
comdlg32.dll      c:\windows\system32\comdlg32.dll
credui.dll      c:\windows\system32\credui.dll
crypt32.dll      c:\windows\system32\crypt32.dll
cryptui.dll      c:\windows\system32\cryptui.dll
cscapi.dll      c:\windows\system32\cscapi.dll
dbghelp.dll      c:\sfc\taldren software inc\starfleet command orion pirates\dbghelp.dll
dciman32.dll      c:\windows\system32\dciman32.dll
ddraw.dll      c:\windows\system32\ddraw.dll
devmgr.dll      c:\windows\system32\devmgr.dll
dhcpcsvc.dll      c:\windows\system32\dhcpcsvc.dll
dhcpcsvc6.dll      c:\windows\system32\dhcpcsvc6.dll
dinput.dll      c:\windows\system32\dinput.dll
dnsapi.dll      c:\windows\system32\dnsapi.dll
dsound.dll      c:\windows\system32\dsound.dll
duser.dll      c:\windows\system32\duser.dll
dwmapi.dll      c:\windows\system32\dwmapi.dll
efsadu.dll      c:\windows\system32\efsadu.dll
feclient.dll      c:\windows\system32\feclient.dll
fwpuclnt.dll      c:\windows\system32\fwpuclnt.dll
gdi32.dll      c:\windows\system32\gdi32.dll
gdiplus.dll      c:\windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6001.18065_none_9e7abe2ec9c13222\gdiplus.dll
gpapi.dll      c:\windows\system32\gpapi.dll
gpsvc.dll      c:\windows\system32\gpsvc.dll
iertutil.dll      c:\windows\system32\iertutil.dll
imagehlp.dll      c:\windows\system32\imagehlp.dll
imm32.dll      c:\windows\system32\imm32.dll
iphlpapi.dll      c:\windows\system32\iphlpapi.dll
kernel32.dll      c:\windows\system32\kernel32.dll
ktmw32.dll      c:\windows\system32\ktmw32.dll
linkinfo.dll      c:\windows\system32\linkinfo.dll
mfc42u.dll      c:\windows\system32\mfc42u.dll
mlang.dll      c:\windows\system32\mlang.dll
mmdevapi.dll      c:\windows\system32\mmdevapi.dll
mpr.dll         c:\windows\system32\mpr.dll
mprapi.dll      c:\windows\system32\mprapi.dll
msasn1.dll      c:\windows\system32\msasn1.dll
msctf.dll      c:\windows\system32\msctf.dll
msiltcfg.dll      c:\windows\system32\msiltcfg.dll
msimg32.dll      c:\windows\system32\msimg32.dll
msrating.dll      c:\windows\system32\msrating.dll
mss32.dll      c:\sfc\taldren software inc\starfleet command orion pirates\mss32.dll
mssign32.dll      c:\windows\system32\mssign32.dll
msvcrt.dll      c:\windows\system32\msvcrt.dll
ncrypt.dll      c:\windows\system32\ncrypt.dll
netapi32.dll      c:\windows\system32\netapi32.dll
netplwiz.dll      c:\windows\system32\netplwiz.dll
netrap.dll      c:\windows\system32\netrap.dll
newdev.dll      c:\windows\system32\newdev.dll
nlaapi.dll      c:\windows\system32\nlaapi.dll
normaliz.dll      c:\windows\system32\normaliz.dll
nsi.dll         c:\windows\system32\nsi.dll
ntdll.dll      c:\windows\system32\ntdll.dll
ntdsapi.dll      c:\windows\system32\ntdsapi.dll
ntshrui.dll      c:\windows\system32\ntshrui.dll
odbc32.dll      c:\windows\system32\odbc32.dll
ole32.dll      c:\windows\system32\ole32.dll
oleacc.dll      c:\windows\system32\oleacc.dll
oleaut32.dll      c:\windows\system32\oleaut32.dll
oledlg.dll      c:\windows\system32\oledlg.dll
powrprof.dll      c:\windows\system32\powrprof.dll
printui.dll      c:\windows\system32\printui.dll
propsys.dll      c:\windows\system32\propsys.dll
psapi.dll      c:\windows\system32\psapi.dll
puiapi.dll      c:\windows\system32\puiapi.dll
query.dll      c:\windows\system32\query.dll
rasapi32.dll      c:\windows\system32\rasapi32.dll
rasdlg.dll      c:\windows\system32\rasdlg.dll
rasman.dll      c:\windows\system32\rasman.dll
regapi.dll      c:\windows\system32\regapi.dll
rpchttp.dll      c:\windows\system32\rpchttp.dll
rpcrt4.dll      c:\windows\system32\rpcrt4.dll
rtutils.dll      c:\windows\system32\rtutils.dll
samlib.dll      c:\windows\system32\samlib.dll
scecli.dll      c:\windows\system32\scecli.dll
secur32.dll      c:\windows\system32\secur32.dll
setupapi.dll      c:\windows\system32\setupapi.dll
shdocvw.dll      c:\windows\system32\shdocvw.dll
shell32.dll      c:\windows\system32\shell32.dll
shlwapi.dll      c:\windows\system32\shlwapi.dll
slc.dll         c:\windows\system32\slc.dll
sysntfy.dll      c:\windows\system32\sysntfy.dll
tapi32.dll      c:\windows\system32\tapi32.dll
urlmon.dll      c:\windows\system32\urlmon.dll
user32.dll      c:\windows\system32\user32.dll
userenv.dll      c:\windows\system32\userenv.dll
uxtheme.dll      c:\windows\system32\uxtheme.dll
version.dll      c:\windows\system32\version.dll
w32topl.dll      c:\windows\system32\w32topl.dll
winbrand.dll      c:\windows\system32\winbrand.dll
windowscodecs.dll   c:\windows\system32\windowscodecs.dll
winhttp.dll      c:\windows\system32\winhttp.dll
wininet.dll      c:\windows\system32\wininet.dll
winmm.dll      c:\windows\system32\winmm.dll
winnsi.dll      c:\windows\system32\winnsi.dll
winscard.dll      c:\windows\system32\winscard.dll
winspool.drv      c:\windows\system32\winspool.drv
winsta.dll      c:\windows\system32\winsta.dll
wintrust.dll      c:\windows\system32\wintrust.dll
wldap32.dll      c:\windows\system32\wldap32.dll
ws2_32.dll      c:\windows\system32\ws2_32.dll
wsock32.dll      c:\windows\system32\wsock32.dll
wtsapi32.dll      c:\windows\system32\wtsapi32.dll
xmllite.dll      c:\windows\system32\xmllite.dll

The text report does not show the tree, nor all the function calls, but that info is available through the UI with a PE loaded in the program. (see attached images)

I'm going to dig through all the calls and see what fixes are in the Compatibility Administrator for them.

I'm thinkning about the OLE, RPC and GDI calls as the main suspects right now. GDI might be a really good candidate (as SFHQ indicated in a PM, this could all just be a UI issue) since there have been major changes to GDI in Vista. (also the suspect for Artifex [and virtualisation])

[Bonk]

Not much luck going that route today...

I am now running wireshark to analyse the network traffic, but Hardcore is not in the serverlist at the moment. It will take some time to analyse the captures but it might provide some useful information.

[Pestalence_XC]

Hardcore is back up.. I just took a few moments to update my NVidia 8800GTX vid card.

GeForce Release 180 WHQL
Version: 180.48
Release Date: November 19, 2008
Operating System: Windows Vista 64-bit
Language: U.S. English
File Size: 90.9 MB

Exciting New Features:

•Enables NVIDIA SLI technology on SLI-certified Intel X58-based motherboards with the following GPUs: GeForce GTX 280, GeForce GTX 260, GeForce 9800 GX2, GeForce 9800 GTX+, and GeForce 9800 GTX. Learn more here.
•Enables NVIDIA SLI Multi-monitor support, giving you the ability to use two monitors with your GeForce graphics cards in SLI mode. Now you can easily switch between multi-monitor desktop mode and full screen 3D gaming mode. Learn more here.
•Enables NVIDIA PhysX acceleration on a dedicated GeForce graphics card. Use one card for graphics and dedicate a different card for PhysX processing for game-changing physical effects. Learn more here. (Note: GPU PhysX is supported on all GeForce 8-series, 9-series and 200-series GPUs with a minimum of 256MB dedicated graphics memory. This driver package automatically installs PhysX System Software version 8.10.13).

Blazing Fast Performance:

•Boosts performance in numerous 3D applications. The following are some examples of improvements measured with Release 180 WHQL drivers vs. Release 178 WHQL drivers (results will vary depending on your GPU, system configuration, and game settings):
◦Up to 10% performance increase in 3DMark Vantage (performance preset)
◦Up to 13% performance increase in Assassin's Creed
◦Up to 13% performance increase in BioShock
◦Up to 15% performance increase in Company of Heroes: Opposing Fronts
◦Up to 10% performance increase in Crysis Warhead
◦Up to 25% performance increase in Devil May Cry 4
◦Up to 38% performance increase in Far Cry 2
◦Up to 18% performance increase in Race Driver: GRID
◦Up to 80% performance increase in Lost Planet: Colonies
◦Up to 18% performance increase in World of Conflict

And More:

•Supports single GPU and NVIDIA SLI technology on DirectX 9, DirectX 10, and OpenGL, including 3-way and Quad SLI technology.
•Supports CUDA.
•Supports Folding@home distributing computing application. Download the high performance client for NVIDIA GPUs here and join the NVIDIA team: #131015.
•Supports GPU overclocking and temperature monitoring by installing NVIDIA System Tools software.
•Includes numerous 3D application compatibility fixes. Please read the release notes for more information on product support, features, driver fixes and known compatibility issues.



Anyhow.. while I was at it, I updated by system drivers as well.. plus added the new NVidia EAS Performance toolkit (this one gives control of your GPU cooling fan back for 8 and 9 series cards.. a great plus since the driver default is 60% instead of 100%)

This thing has returned to being smoking fast on applications agin.

[FCM_SFHQ_XC]

I'm not going to have enough time this week to fully explore possible issues with actual UI updating till after about the 16th of December when Ill then have 3 weeks off to work on it some more, but I just really if it is network issues based on the behavior of Vista on OP Dyna and looking at my network activity, and indeed what were seeing is shadowing onto the network side of client code, making it appear to be issues with network communication(will do a bit more exploring after I've had dinner.. for right now though I'm starving! ).

[Bonk]

Looking at the packet trace of a firewall detected login, two things jump out at me:

- I see one of the old Taldren IPs (must still be in one of the directory,firewall,chat server configs): 216.203.248.212 (I think that is what it is?)
- I see SSDP (UPnP related crap) packets right in the middle of a discussion with heimdall...

(I'm running OP with no compatibilty settings at all, just installed to C:\SFC\*)

I will now take another look at the directory servers settings to find any of the old Taldren IPs (I thought I killed them all).
And I will stop the SSDP service on my Vista install.

But first I'm going to get another pack of smokes and some pop and chips, I'll need them.

P.S. I have modified my WONServerSetup.gf like so:

[WONDirectoryServer/Addresses]
0="client.sfc.dynaverse.net:15101"
//1="client.dynaverse.net:15101"
//2="sfc2.directory.stasis.ca:15101"

[Bonk]

Well, I can't find that IP address anywhere in the configs, it must be hard-coded in.

And stopping the SSDP service did not get rid of the SSDP spam packets. Something else in Vista must be responsible for them.

And my ginger-ale tastes more like garlic-ale, I can't drink it!     

I'm thinking I'll install Kubuntu, investigate the current state of OP on Wine and run wireshark on it to compare the results to see if it is really Vista to blame or if it is my router.

[FCM_SFHQ_XC]

every couple of times I do get
A firewall has been detected
Unable to locate directory services

message. I'm including my wireshark log for that particular message if you wish to compare it to yours(.pcap file)

[Bonk]

Cool, thanks, I'll take a look at that. A capture log from a successful XP login would probably be useful too.

[FCM_SFHQ_XC]

humm, well I think I still have my XP wireshark here I did a while ago on this same connection(cant get on my XP box right now to do it again) let me look for it...

[FCM_SFHQ_XC]

Ah! found it! Remembered I uploaded it up to the server a while ago for safe keeping
http://www.xenocorp.net/sfhq/Thedebug2.txt
is the wireshark log I did a while ago after you killed the other firewall entries and on my XP box on this same connection.

[Bonk]

Good work SFHQ!

Interesting, there are a few SSDP packets at the beginning, but none in the middle of the negotiation with the directory server like we see on Vista. (and the 216.203.248.212 IP address is present in both...)

I'm beginning to think that UPnP/SSDP/VistaNetworkDiscovery may be the issue here, still pure speculation at this point though.

A wireshark log of a session on the hardcore server correlating the times of slow movement etc., with the packet capture log time index might be instructive, but tricky to pull off, would need an accurate digital stopwatch and a fast hand.