Risk of closure because someone wrote facepalm?

Risk of closure because someone wrote facepalm?

yeah, of course SMH

Risk of closure because someone wrote facepalm?

I believe a staff member has turned on the monitoring sign because the OP is talking about using the NOCD crack in FS9. Individuals who use cracked files can be banned from AVSIM as we do not tolerate any form of pirating.

 

 

Yes. But that's what everyone uses. is that a problem?

 

This is what AVSIM's Terms of Service states;

 

Piracy, Key Sharing, Link Sharing, EULA Busting, etc.: Any message, post or topic heading that appears to advocate or perpetuates piracy, shares cracked software, links to or other like material, advocates avoidance of or contravening of End User License Agreements (EULAs) or can be interpreted as approval of piracy or EULA "busting", will be immediately removed and the poster banned. Piracy of software destroys the basis of our hobby and AVSIM enforces anti-piracy policies strictly. If you are a pirate, advocate piracy, or use pirated material, do not register. We place EULA busting in the same category.

 

 

You did read  them?

This is what AVSIM's Terms of Service states;

 

 

You did read  them?

Sorry.

 

Sure, I read them.  About 100 years ago.

ISTR the problem of using the "large address aware" patch was that some clever programmers were using the msb of 32 bit addresses as a "flag" bit (since it was normally ignored).

 

scott s.

.

ISTR the problem of using the "large address aware" patch was that some clever programmers were using the msb of 32 bit addresses as a "flag" bit (since it was normally ignored).

 

scott s.

.

 

I think you mean PAE, not LAA

CAVEAT: Users of the "4GB patch" with legacy (FS9) products from Cloud9 / FSDreamTeam (aka "FSDT") may wish to review info linked from this older tutorial I wrote on use of the "/3GB switch" in 32-bit windows to set the LARGE_ADDRESS_AWARE" flag and increase USERVA with 32-bit executables:

 

http://forum.simflight.com/topic/55994-set-fs-and-winxp-to-use-the-3gb-switch/

 

 

It is possible that newer updates for Cloud9 / FSDreamTeam "may" now support the default MS FS9.exe RTM version 9.0 and the FS9.1 patch / update FS9.exe, so users are advised to check first in the Cloud9 / FSDreamTeam support forums / download areas to confirm what their options are.

 

 

BTW: FS 9.1 "Patch" was the term used for that update package by ACES at that time ...and not 'Service pack'.

 

 

However, please note that as of the time of writing the above referenced tutorial, there were no other options available to end users of Cloud9 / FSDreamTeam to utilize for updating certain files integral to their products ...which would even work with the MSFS default FS9 executable; thus one was required to use "patched" FS9 executables to get their 'FSDT' products to work !  :Whistle:

 

Hope this helps ! :smile:

 

GaryGB

This has been fixed for years - all FSDT/Cloud9 products work with the patched versions of FS9 and FSX today.  In addition to the modification needed to the boot.ini for XP, you will need to use bcdedit for Win7 x32 to make the patch effective.  Instructions are here on the forum if you search.

 

DJ