This is a copy of a posting on the 352FG site.
None of the hardware is state -of- the art nor very old[
quote] Hello Guys,
I think that the period of bumbling and fumbling is now pretty much over. I have The HP Win 10 computer functioning and I am able to find my way around on it. I have a whole lot still to learn. I have another Video card to try out. I am making preparations for shifting EAW onto the Win 10 machine, I thought that I would check out all the installs of EAW that I have on my Dell machine so that I would have some standards and benchmarks to go by. I ended up finding that EAW v1.28a causes a system lock up when it is checked by my Avast Antivirus. I have been able to exclude that version from the avast check so that is not a problem. I had problems with the joystick that were cured by putting a standard INI file on all the installs. The first step that I made was to put a copy of my EAW v1.50 install onto the Win 10 system. I wanted to see what it would do when I tried to play it on the on-board video. I was very surprised when it ran fine. I will make a lot more tests before I install the new video card. Before I get very much deeper into things, I am going to sort out what I have put on the system so far and create a rational organization of related functions and processes.
I haven’t been doing much EAW flying for quite a while and there are a lot of things that I have to brush up on.
Believe it or not! I just transfered the EAW V1.2 from my dell to my HP and it ran Ok I tried OAW on it and got run time and other faults but the basic fact is that it did run at least this time
Back again! I transfered the run time files and ran them and put the correct path into the OAW selector. I picked out my JackSprat P51d and my 352FG main screen and had them placed into the root folder. It all seemed to work OK. The plane viewing feature didn't show the plane, just a black screen
[/quote]