BigRick

Nope! I leave my PCs on all the time. The 2 desktops anyway. The 2 laptops I turn off. I'll leave it at that since I don't want to start that major debate about "leave them on/turn them off" that I've seen for YEARS. Take it easy. -Rick

Alright, well, I got both of my laptops to connect with no problem. So, seems to be just my main FS util computer. After beating my head against the table for about 10 minutes, I decided to try something simple. I rebooted the machine. And lo! It connects! Sometimes knowing quite a bit about computers can make you overlook the simple solution. That will teach me. Thanx anyway! -Rick

Here is the server ini file: [Config] AdvertiseService=1 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port=8002 Port2=9002 RestartTime=10 SendTimeout=15 TCPcoalesce=No Very basic and no changes made by me. Here is the client ini file: [Config] ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port=8002 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Window=476,32,601,85 ServerName=Ricks-Toy Protocol=TCP All I changed to try to get it to work again is specifying the Servername and Protocol. Other than that, it's default. I can access all FOUR of my computers thru my home network with no problems. Each can communicate with the other. It's specifically WideFS that seems to have the prob. One thing I have not done yet is put it on one of my other computers and try to connect to the server located on my FS machine that way. That's next, I suppose. If it DOES connect, that would narrow the prob down to a single computer. As a side note, it was working and then went down in the middle of the flight. Connection was fine until then. After that, it would not reconnect. -Rick

What? Can't deduce problems with 1/2 the story? lol I thought about that other log after I posted the 1st one. Here's the server log: ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 20/03/09, Time 13:26:00.092: Server name is RICKS-TOY 101557 Initialising TCP/IP server 101573 Initialising IPX/SPX server 101573 IPX/SPX socket() failed [Error=10044] Socket type not supported 101573 Failed to start IPX/SPX Server 101573 Initialising UDP/IP server 102680 Broadcasting service every 1000 mSecs 113148 Restarting service due to total lack of use 113164 Failed to start IPX/SPX Server 150307 Closing down now ... Memory managed: Offset records: 0 alloc, 0 free Read buffer usage: 0 alloc, 0 free, max in session: 0 Write buffer usage: 0 alloc, 0 free, max in session: 0 Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed ********* Not sure if the IPX/SPX is the problem since that seems to be failing. -Rick

Well, I'm at a loss. Suddenly WideFS is not wanting to connect between my computers. I get no connect message from either the client or the server. This is in the log file: ********* WideClient Log [version 6.782] Class=FS98MAIN ********* Date (dmy): 20/03/09, Time 13:17:41.406: Client name is VISTA_64 141 Attempting to connect now 7157 Trying TCP/IP host "Ricks-Toy" port 8002 ... 7157Okay, IP Address = 192.168.0.100 28157 Error on client pre-Connection Select() [Error=10060] Connection timed out 28157 Ready to try connection again 29204 Attempting to connect now 52672 ****** End of session performance summary ****** 52672 Total time connected = 0 seconds 52672 Reception maximum: 0 frames/sec, 0 bytes/sec 52672 Transmission maximum: 0 frames/sec, 0 bytes/sec 52672 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 52672 **************** Individual client application activity **************** 52672 Client 3312 requests: 5 (Ave 5/sec), Data: 270 bytes (270/sec), Average 54 bytes/Process 52672 ********* Log file closed (Buffers: MaxUsed 1, Alloc 5 Freed 5 Refused 0) ********* Now before anyone hollers "it must be your firewall", bear in mind that I've turned the Windows firewall OFF and no change. Still wont connect. Also, with the firewall on, I've set up port 8002 with TCP on BOTH machines to be allowed to pass thru the firewall. In addition, in the ServerName and Protocol are defined in the WideClient.Ini file. I've also tried it without defining them. In addition, I'm running no other firewall. It WAS working fine for over 4 yrs, then suddenly BOOM, down she went. I made no changes at all to my system. I'm running the most current versions and both are registered. Suggestions? I'm basically shut down now since ALL my FS utilities run on my 2nd computer. Thanx. -Rick

Maybe someone in here can help me out. I'm running FS2Crew, but I'm using FSUIPC to control all my yoke/throttle/pedal functions. it's disabled in FS. The newer version of FS2Crew is looking to capture the button press of my yoke to trigger certain things to happen (Red and Green button). Now, since I don't define these 2 button presses in FSUIPC as actually DOING anything, FS2Crew is not capturing anything. As for as it is concerned, the buttons I have picked don't exist since it's not defined in FSUIPC. I don't want FSUIPC to pass anything (command or what have you), I just want it to pass the hex code that's specified for that particular button so FS2Crew can catch it. Is there a way to accomplish this? Thanx in advance! -Rick

Morning Pete. I'm having a little problem here. I've got both FSUIPC and WideFS for FS9. Now, I purchased these at separate times and in separate states, so my registered email for each program is different. When trying to register WideFS, it's defaulting to the same address I registered FSUIPC. Is there a way around that? I've tried editing the .KEY file and adding WideFS to it with the correct email address, but no go. Appreciate your help. -Rick Schaefer

I'm sure it is caused by the 2nd of your two reasons. PFE will make me tune to the ATIS on a resume (this is something I think Dave needs to fix). Naturally, the majority of the time I'm over 80mi away from where the ATIS is active, so that would trigger the crash. I'll let Dave know about this. -Rick

Morning Pete. Had something crop up here and it was suggested that I contact you as well. I'm running Proflight Emulator 2.7 (I'm one of the beta-testers) and FSUIPC 3.829. One of the new features for PFE is to resume a flight. When I do so, FS9 will crash with an error in the ATC.DLL file. Now, I have RemoveATC=Yes in my INI file and I thought that fixed that particular problem. Any suggestions? I've got Dave March looking at the PFE side. BTW, I'm running Vista 32 and FS9. -Rick

ASv6 starts processing and updating the weather as soon as the opening start menu comes up, not when I'm actually sitting on the cockpit at the airport. That's why I was asking Pete about when FSUIPC reported that FS was ready for input of weather. I'll take this back over to the HiFiSim support area. -Rick

Evening Pete. I'm running the registered version of FSUIPC and have noticed something here lately. I use ActiveSky 6.5 and, when I load up FS9, ASv6 goes active at the main FS screen rather than waiting until I'm actually sitting at the airport. It didn't used to do this in the past. I've contacted AS support and they said all they are doing is checking the status stating if FS is ready or not. When does FSUIPC flag FS as ready? At the main screen or once the flight is loaded and you are sitting in the cockpit? Right now I have to exit out of ASv6 and load FS, THEN load AS to get it to update correctly. I'm also running registered WideFS and ASv6 is on the same computer as FS. Thanx a lot. -Rick

0=None, 1=left, 2=right, 3=center, and w=water. -Rick