Helshad

Got the same problem in Lord of the rings with these new drivers... works fine othewise though...

Quote: symantec is great if you only use their corporate edition software. I would like to disagree on this... Not when it comes to finding viruses and running in general but when it comes to installation and upgrade. Corp Ed 7.6 to 8.0 sucks badly. You need to hack the registry like crazy to manage to upgrade or reinstall their client software. And not only that. You have to find all the folders spread out on the disk too. I am very disapointed at symantec regarding upgrade and install... But I am very impressed at the performance and detection of viruses. Thats why I still run it... hehehe

Try and remove gimme.dll from the games main folder. It worked for me

I tested it and it workes great... No beta... Its final version... Atleast there are no strange buildnumbers on it...

Could anyone confirm if this is the swedish version of SP1 for XP? I found it and downloaded it when I messed around with the Danish release today. I just changed the DA to SV in the folderpath and in the exe file. I have no idea if this is the final release either. http://download.microsoft.com/download/whistler/SP/SP1/WXP/SV/xpsp1_sv_x86.exe

Thank you very much for that link....

Hi Ewaite and Clutch... Firstly, I cant get to the loggon screen at all... It craches before I even get there... One more detail could be that this happend when they installed it on a computer wich has been running for a rather long time without service... If I make a clean copy of win2000 on the computers there is never a problem... No, there is no PCAnywhere on them... Only I and and 2 more uses that kind of software, but in our case PC-DUO, but on the other hand... We use a rather lot of software on our client machines in our work so it could be anything.... I am just puzzled... I have no clue what could cause this error...

I have come across a strange error after installing SP3 on Win 2000 machines... On 2 machines, so far, I got an error on winlogon.exe file when they tried to loggon for the first time after installation. It just say that winlogon.exe created an error and reboots over and over again.. I cant get to the logon screen and safemode is just the same... No error log is created... It just keep rebooting at the same place all the time.. I have installed it on the same type of machines 10 times now and 2 of them got this error... I cant find anything on microsofts support pages or anywhere else... Anyone else seen this happend?? and someone knowing what to do about it??? Replacing the winlogon.exe dosnt do the trick... hehehe

Have anyone tried it yet?? I know it hasnt been out long yet but I would be intrested to know if its working properly...

I dont know exactly how this works but I have tried with both Sygates personal firewall pro and Zone Alarm pro with the exakt same result. (Latest versions of both) When I install Symantecs VPN client it somehow disconects the settings of the firewall and suddenly all my other applications cant get access to the internet. After a while they get back online again but with problems... Without any reason they could be blocked again and nothing works... My FTP server is impossible to reach from outside as long as the VPN client is installed... after uninstalling it and a reboot it works again... The normal scenario is that, when the VPN client is closed (not uninstalled), the connection to the internet gets blocked... randomly and is impossible to reverse... The only way is to close the firewall and restart it... then it works for a period of time and then blocks again... Anyone got a reason for this?? I am walking in the dark here... I have no or little experience with VPN clients... I have no idea what they do to the system... Except that they have a service running... and even if that service is closed it still causes these problems... Well, any suggestions is welcome... /Helshad

Your welcome... 8)

Installed it without any trouble... Need the original CD though. It is now version 2002 (10.4219.4219) SP2 If you have versions before 2002 (10.4---.3---) SP1 you might run into trouble... Read on other forums that SP2 told them that they had wrong versions and stuff... probably beta... You better have the original CD... Anyway... Just wanted to say that its a good update... no strange stuff so far...

Well, its works in WinXP for sure... How it will work with your graphics I cant say for sure... depends on drivers... But the graphics in the game itself is poor... very poor so I would guess it will...

This is the closest thing I could find to your question on microsofts helppages... http://support.microsoft.com/default.aspx?scid=kb;en-us;Q158623 How to Establish NetMeeting Connections Through a Firewall The information in this article applies to: Microsoft NetMeeting 2.0, 2.1, 2.11, 3.01 for Windows 95 Microsoft Windows 98 Microsoft Windows 98 Second Edition Microsoft NetMeeting 2.1, 2.11, 3.01 for Windows 98 Microsoft NetMeeting 2.1, 2.11, 3.01 for Windows NT 4.0 Microsoft NetMeeting 3.01 for Windows 2000 Summary This article describes how to use Microsoft NetMeeting to establish connections over the Internet when you use a firewall to connect to the Internet. More Information When you use NetMeeting to establish a connection over the Internet, NetMeeting uses several IP ports to communicate with other meeting participants. If you use a firewall to connect to the Internet, the firewall must be configured so that the ports used by NetMeeting are not blocked. NetMeeting uses the following Internet Protocol (IP) ports: Port Purpose ------------------------------------- 389 Internet Locator Server [Transmission Control Protocol (TCP)] 522 User Location Server (TCP) 1503 T.120 (TCP) 1720 H.323 call setup (TCP) 1731 Audio call control (TCP) Dynamic H.323 call control (TCP) Dynamic H.323 streaming [Realtime Transport Protocol (RTP) over User Datagram Protocol (UDP)] To establish outbound NetMeeting connections through a firewall, the firewall must be configured to do the following: Pass through primary TCP connections on ports 522, 389, 1503, 1720 and 1731. Pass through secondary UDP connections on dynamically assigned ports (1024-65535). NOTE: Some firewalls are capable of passing through TCP connections on specific ports, but are not capable of passing through secondary UDP connections on dynamically assigned ports. When you establish NetMeeting connections through these firewalls, you are unable to use the audio features of NetMeeting. In addition, some firewalls are capable of passing through TCP connections on specific ports and secondary UDP connections on dynamically assigned ports, but are not capable of virtualizing an arbitrary number of internal IP addresses, or are not capable of doing so dynamically. With these firewalls, you are able to establish NetMeeting connections from computers inside the firewall to computers outside the firewall and you are able to use the audio features of NetMeeting, but you are unable to establish connections from computers outside the firewall to computers inside the firewall. The H.323 call setup protocol (over port 1720) dynamically negotiates a TCP port for use by the H.323 call control protocol. Also, both the audio call control protocol (over port 1731) and the H.323 call setup protocol (over port 1720) dynamically negotiate User Datagram Protocol (UDP) ports for use by the H.323 streaming protocol, called the real time protocol (RTP). In NetMeeting, two ports are determined on each side of the firewall for audio and video streaming. These dynamically negotiated ports are selected arbitrarily from all ports that can be assigned dynamically. NetMeeting directory services require either port 389 or port 522, depending on the type of server you are using. Internet Locator Servers (ILSs), which support the lightweight directory access protocol (LDAP) for NetMeeting 2.0 or later, require port 389. User Location Servers (ULSs), developed for NetMeeting 1.0, require port 522.

I did that too... I installed it over my old and restarted with strange vga result... then I tried again but no luck... My computer never recoverd.... ;( Well... I hope the other way works....