|
Post by emarkay on Jul 6, 2006 19:01:28 GMT
Just curious.
Thanks.
MRK
|
|
|
Post by aerofoto - HJG Admin on Jul 6, 2006 21:48:11 GMT
I presume you mean in relation to the B707 panels ! I've been trying to get responses on certain issues all week .... but none have yet been forthcomming From what I've learned through my own private investigations though, folks using WINDOWS XP shouldn't have any problems at all .... which has been my personal experience as well as that of many others I'm in contact with .... but I can't vouch for absolutely everyone of course. I think we can forget about any possibility of WINDOWS 98 compatibility. It's just no gonna happen .... more so considering MS are about to completly dump support for that particular operating system .... if I understand correctly There's not really much more I can add I'm afraid Mark C AKL/NZ
|
|
|
Post by emarkay on Jul 7, 2006 0:05:26 GMT
Yes that is correct - On July 11, it's all over. But I am prepared www.emarkay.com/win98se/windowsupdatedata.html( I have some final updates/corrections this weekend...) Still it's strange - the first OS specific issue I know of in FS9... At least the CV990 is OK - and I think you folks had a nice 707-320 (TWA 1967 I recall) last year I'll hunt for it someday. Thanks again! MRK
|
|
|
Post by garryrussell on Jul 7, 2006 1:13:25 GMT
They are ditching Windows ME as well.
Garry
|
|
|
Post by George Carty - HJG on Jul 7, 2006 8:05:10 GMT
Perhaps I need to recompile my gauges using different compiler settings. Are problems like this one reason why many panel designers are moving to XML? I started constructing my panel under FS2000 (when there was no alternative to C++), and anyway I think C++ is better for a complex panel such as my 707 panel.
|
|
|
Post by emarkay on Jul 7, 2006 13:09:51 GMT
George, BTW, Fantastic work!
I have some add on aircraft with XML gauges that run OK on Win98, and I still can't understand how a compiler could add routines that are OS specific. I think the XML thing is just an evolution, and prob something MS can use to add more features, and keep bloatware to a managable level?
Regardless, no need to do 2 versions if there TRULY is an OS issue, but maybe see what can be done with the older panels in the newer aircraft out of curiosity?
Thanks again, and to all at HJG!
MRK
|
|
|
Post by Harerton Dourado - HJG on Jul 7, 2006 19:19:28 GMT
C++ surely is currently a better option to program custom things like George's B707. But I'm sure MS will develop new ways to explore what XML can give, especially in terms of programming simplicity.
And yes, different compiler versions and options can make a big difference on the final result on different systems!
|
|
|
Post by George Carty - HJG on Jul 10, 2006 8:16:32 GMT
This weekend I confirmed that the panel is indeed incompatible with Windows 98. I can't see any obvious problem in the makefile though I also noticed that my older 707-436 package b707-436v22.zip is also incompatible, while b707-436v21.zip does work on Win98. I wonder if the custom autopilot code is to blame?
|
|
|
Post by George Carty - HJG on Jul 12, 2006 16:44:41 GMT
I now think that an "insufficient resources" problem is to blame. When I went from b707-436v21.zip to b707-436v22.zip I replaced the "regional" gauges clusters (basics, gyros, centre, overhead, flight engineer panel) with a single megagauge. I now suspect that this megagauge is simply too big for Win98 to handle. Thanks Roy Chaffin!
|
|
|
Post by emarkay on Jul 13, 2006 14:42:48 GMT
OK, thanks for the diagnostics - may want to make a posting in the download area to this effect.
Does this mean that (in theory of course) that Win98 users can use the b707-436v21.zip and all other CURRENT files to get a V6 707 in win98? If so can that panel be made available, as a token?
I note that the filedates are dated "tomorrow" (an interesting fact of "Dateline Down Underers"), so there have been some updates today. Would it be posible to put a "change notice" somewhere so users know if it's essential to download the most recent version - this may save on bandwidth and "ifitaintbrokedontfixit" tech support...
|
|
|
Post by George Carty - HJG on Jul 13, 2006 14:59:03 GMT
The old 707-420 panel can be used with any current HJG base packs, but its engine and fuel gauges will not give realistic readings.
|
|
|
Post by emarkay on Jul 14, 2006 0:39:22 GMT
Yes! The panel and gauges from file b707-436v2.zip seems to work fine in WIN98 with the v6 aircraft - at least the engine displays and throttles work (that's all I had time to mess with on my "test" PC - Just happy to see it load!)
BTW, maybe the problem is compiling all the gauges into one large 13Mb file instead of breaking them out individially - maybe try 4 or 5 seperate gauge files for each 'view'as a test?
|
|