PUFF88
Scharfuehrer
Posts: 388
|
Post by PUFF88 on May 7, 2003 8:30:06 GMT -5
|
|
|
Post by Keith Heitmann on May 7, 2003 21:57:32 GMT -5
Looks nice. It's going to have to be pretty good to get people away from the old standard Red Baron 3D though. The scenery is definitely superior, but only time will tell.
|
|
|
Post by Keith Heitmann on May 10, 2003 19:17:26 GMT -5
|
|
PUFF88
Scharfuehrer
Posts: 388
|
Post by PUFF88 on May 11, 2003 2:59:20 GMT -5
that one looks nice to. i like WW1 flying games. red baron2 would not run on my pc, i bought it, and no matter what i did it would drop to the desktop or lockup about as soon as flight started. i had rented a old flying game for either nintendo or super nintendo i dont remember which, but it was a lot of fun. single player only though. i think it was called wings.....of something :-(.
|
|
|
Post by Keith Heitmann on May 11, 2003 11:53:31 GMT -5
If you got the error message at startup:
"Engine start mfc app has encountered a problem and will now close"
There was an update put out to fix that problem and a few others.
Another problem at startup was:
Problem: When I launch the program I get an error message that references "ddraw.dll"
Solution: This program is using DirectX to change screen and color resolutions on the fly. If you experience an error such as: GPF or IPF in DDraw.dll, right when you try to start the game this is probably due the fact that either DirectX is not installed on the computer OR the video card drivers are not DirectX compatible. Try installing the latest version of DirectX available at Microsoft's DirectX site. If problems persist you may need to update your video card drivers. Contact the manufacturers of your video card for the latest drivers for your hardware. Many manufacturers update their drivers every three months. Updating your drivers usually eliminates conflicts, expands features, increases stability and will include application specific bug fixes that the manufacturer chooses to address.
If you were running under Win3.x the problem may have been
Protection Fault in module Damessag.dll running under Windows 3.x.
Solution: The next most common cause of a General Protection Fault in module Damessag.dll is a video driver (software Windows uses to work with your graphics card) that is not able to play the graphics in our program or installation program.
There was also a problem with Win3.x and a Diamond Viper card with QEMM/MEMMAKER.
The Diamond Viper video card can cause GPF error messages. The VIPER card is produced in four versions. The versions and current drivers are: PRO with VPO301.exe, SC with SCO201.exe, PCI with VPRPCI.exe and VLB with VPRVB.exe. The PCI, VLB and PRO versions of the VIPER are PCI type cards that require different drivers. The PCI and VLB cards have beta versions of their new drivers. The card/driver combinations are: PCI/VPC310.exe and VLB/VVL310.exe. When using QEMM or MEMMAKER then the video area must be excluded. The video addresses are A000-C7FF. When these cards are used in STEALTH option then the switch /STM:XST=C000 must be used. After changed are made to exclude memory or include the switch then memory must be reoptimized, i.e. re-execute memmaker or qemm's optimize. So the lines must be: ...\QEMM /X=A000-C7FF /STM:XST=C000 then execute memmaker or qemm's optimize(1/11/95)
I ran Red Baron 3D not RB2 and I didn't have any problems.
|
|
PUFF88
Scharfuehrer
Posts: 388
|
Post by PUFF88 on May 11, 2003 17:37:07 GMT -5
if i ever find where i put it, i may try again, i dont remember what version of windows or video card i had at the time.
|
|