I need some help troubleshooting a problem I'm having with RC3 installed on a client PC and linked via the current version of WideFS.Everything works fine until about 30-40 min into the flight when the client PC goes blank - the video is completely off and cannot be restored. The PC requires a hard restart to recover.The client PC is a 1.0Ghz P3 with a Radeon 8500 AIW and 100Mbit NIC. WideFS is running in IP mode. I'm using FSUIPC 2.95 and WideFS 5.3. Both machines use XP Pro. The UI aircraft is a POSKY 762 with PIC. I have a large quantity of AI and listen to MS ATC in the background.While I'm not currently using this client for WidevieW, it runs completely stable as a WidevieW client so my first guess isn't the hardware. I also sometimes run this machine as a streaming media player (via broadband) or for DVD "in flight" movies with no problems, so I think it's pretty stable. At first I thought the conflict was with Active Sky wxRE (running on the server, not the client in question), but I've experience it two times in a row without Active Sky running, so that's ruled out also. I just installed it on my server so we'll see if that makes any difference. It doesn't seem to occur at the exact same spot on the plan (+/- 60 miles) so I don't think it's flight plan related, but I'd be happy to post the plan as well (KSLC-KPDX).Any ideas?

Same thing occurred (when using client for RC3) on a KRNO-KPDX flight, so it's not a problem with a particular waypoint (if fact it has never occurred at a waypoint).

i'm not ignoring, i'm thinking. still thinking....

Two things to check.Check the power management in the BIOS (at boot, press the "Del" key or whatever to get into Setup). Make sure there's no inactive timers or screen savers or drive shut-downs. Just make sure power management is disabled.In windows, right-click on the desktop, then properties, then screen-saver, then Settings. Make sure everything's set to "Never".I have the problem you describe on my old PII if it thinks the screen is inactive (which it is most of the time), and especially the drives shut down. If the drives shut down (even one I'm really not using), then that's it, no more responses - ever. It would sometimes happen with screen blanking as well.

Three times after installing RC3 (after 5-6 flights) I have experienced what appeared to be total melt-downs. I think the display went black on one occasion. And I'm sure it just froze in another; not even mouse cursor would move. The sound also dissappeared.However, I could press ctrl-alt-del and open Windows 2000's TaskManager. In there I selected to switch to the FS2002 application, et voil

APM was my first thought too. The only setting was to have the monitor turn off after 1 hour. I have since disabled all APM and screen savers but the problem continues. I will, however, check the BIOS. The mobo is an ASUS P3BF which does have PM settings. I would think that XP would handle this, but there may be a conflict. I was also thinking that there may be a video/NIC IRQ conflict. I believe the NIC on that machine is on a shared IRQ PCI slot so perhaps a relocate would help. But it's very odd that no other application has caused this problem.

Because RC3 is running on a client machine, I haven't had the slow speach problem, and have consequently been able to leave the priority set to "normal". Ctrl-alt-del doesn't bring up task manager in this case. What's weired is that even though the screen is completely blank, the monitor doesn't go into "sleep" mode.

Dennis,I also have had these types of problems with cards having the same interrupts. The problems are more prevalent on the PII than the PIII, but I've just learned to spend time finding the best combination of cards and interrupts.A lot of stuff interfered with the video interrupt.I also had a circumstance where the main system blanked and died with the TCP/IP WideClient connection. I have no idea why, and Pete could find no reason for it (well, he didn't even try). I eventually found that since I had initially used FS_Meteo on the main system on the second monitor, that when I started FS_Meteo on the client system, it was trying to put the display on a non-existent monitor, and it crashed the main system.So, if moving cards doesn't solve it, it can be anything. Check everything, one by one, running one program at a time. Then when the system blanks, you know which it is. If it's the first one, it could be WideClient.

Scott,I disabled APM in the BIOS and now everthing appears to be working OK. Thanks for your help. Still curious as to why this was never a problem with WidevieW...

Dennis,With WideView the display is constantly updating, but who knows. I have this "Because it's Tuesday" rule, as in: "It works today because it's Tuesday".I'm glad you got it working!