You won't harm your system by using most of the memory techniques listed (well except if you mess up the boot.ini file). You're only adjusting software here.

MSConfig should be used as a TEST to see if you need to go to Boot.ini, if you suspect you have a RAM issue.

Now the WAC method (aka MSCompatability automated) is the best bet, but not for everyone.
It doesn't limit your system RAM globally, just for this one game, which is perfect.

I use the MS Compat ToolKit with the LB2 library that +G made long ago.

Works great on all my WinXP systems. The idea is that when the LB2 application is used, it limits the RAM to 366MB for just the time the game is running. So its an application sensitive RAM switching mechanism. Doesnt affect any other game or application.

Well ,, I'm in the process of installing, I have completed the "Basic Installation" section, and I'm on the next page "Ram". The 1st sentence says
"Almost everyone needs to adjust their PCs RAM settings, to some degree. If you're one of the lucky ones, congratulations!"

Now am I to assume by this that I should be able to open up the game at this point? Because I cant ! I get that Windows error message, do I want to send or not?

Fakum, I haven't actually done it yet, but if I understand Speicht's instructions correctly, this is where you need to try one of the memory limiting methods. If you mean "do I want to send or not" a notice to Microsoft about the error message, I would say there is no reason to notify MS. The memory error is experienced by a majority of people, hence the various workarounds. While you don't say if you're running XP, I presume you likely are and, like AV8R said, would benefit from following PositiveG's instructions listed under the heading "Windows Application Compatibility (WAC) Toolkit 3.0 Method". We're very fortunate to have such knowledgeable assistance from these guys. I hope I roundup LB2 soon and give it a whirl myself.

Thanks 4 the response,,,I wound up experimenting a bit, and I'm up and running so far. I wasnt meaning that i didnt know whether or not to send the error to MS, I realize now how one would have interpreted it as that,,hahaha ,, sorry. Anyway, I am successful so far, and the only ram settings I have done is through msconfig. I read about the wac procedure, but was confused about the section that said "Done, move on" was sure if it was a requirement after you instal wac, or just an option. As far as the graphic settings go, and yes, im running XP, I have an ATI All in Wonder 9700 pro 128 mb. the only setting that works well is the Direct 3D set @ Dont Know. Wish me luck , I'm going back in and tinker,,

the game wont run on WinXP until:
(their are exceptions, but in general)

1. LB2 Software installed with patches
2. RAM limiting (game can only address 366mb)
3. Windows Compatibility, use one of the methods. I use the Toolkit
3. If using Glide, use the dgVoodoo glide wrapper and settings as shown in this forum, no extra switches.
4. Make appropriate d3d.cfg edits if using D3D and not Glide
5. Make appropriate CA.INI file edits for HEAP variable.

Give it a "whirl" for the whirly burd.

Thanks AV8R, So far, the graphics look decent, the only way i hav compared so far is going into quick mission and pulling back on the stick to view the clouds, if there blocky,, no good, smooth , ok! So far I found a D3D setting that shows the clouds pretty smooth on the edges. I dont know if I shound continue to mess with anything else as far as glide d3d cfgs or not ???

I prefer GLIDE not only for the graphics, but also because the dgVoodoo utility controls the game speed so that for fast systems the game runs correctly. If you run D3D, youre gunna have to use one of the throttling methods to slow down the game.

Post your picture in game if you want a qualitative opinion.

Glad it works for ya

Thats using the "dgVoodoo utility controls", I found it to be a bit sharper, but when I pull the stik back to look at the clouds,, they look good, but bounce,, I think its worth it though,,, thx ,, still gonna tweakit a bit,, I have the resolution maxed out now.