Incoming9000

It will come out when Duke Nukem does.

I was just laying CMBO, not CMAK I know, but I did manage to get a Serman V to damage the gun of a Panther G with a frontal shot and force the crew to abandon it just a few minutes ago. The scenario was "Death of the Titans", and I won with a minor victory after destroying all the german tanks: 4 Tigers 2 Panthers, one G and one A, and a turretless PzIV. The majority of the kills were achieved by Sherman Vs even though I had fireflys.

http://wio.ru/tank/capt/capt.htm Anyone knows what was the average ratio of used captured equipment on the russian front?

What's your mobo chipset?

Thanks for all the help guys. I belive I have found the problem but unfortunatly it's more complex than just heat or drivers. I have posted an explanation at the Tech Forum here: Tech Help Thread Thanks for everything!

Thanks for all the help guys. I belive I have found the problem but unfortunatly it's more complex than just heat or drivers. I have posted an explanation at the Tech Forum here: Tech Help Thread Thanks for everything!

After having exausted all other options I decided to simply remove my SBLive! Value and, for the first time, use the onboard sound capabilities of my mobo. The sound works great and honestly I can't really notice any diference from before, but I did notice something very interesting. The crashes almost dissapeared completly. They still occur ocasinally but not within minutes or seconds as before. Now it can take an hour or even more. After some research I discovered that my mobo chipset, the Via Apollo KT-133A with the VT82C686B south bridge, has a know bug that occasionally can cause crashes in certain circumstances. This seems to occur more oftem in conjuction with Nvidia and SBlive Boards. This does bug does not occur with every program as it depends on certain specific conditions making hard to determine what is causing it. It is common for it to make it look like the issue lies with either the GFX card or the Sound Board as the error occurs when there's exchange of data within the PCI bus using those peripherals. Without the SBLive the problem is now much less notisable and since it only afftes CMBO and CMBB, at least for me, I will leave things as they are, at least for now. Thanks for all the help!

Since the Battlefront FAQ says my problemn is with a corrupt DX file I installed DX9b SDK in the hope it would replace all DX files and install utilities that would give me more info on what might be wrong. So far no good! So I defragemented my HDs, C and D (I've got a 80GB and 40GB HDs). I defraged them several times in the hope it would fix it. Nope. Then I did something I very rarely do. Something that if not done properly can literally screw up the system. A BIOS upgrade. Well, it went fine. And now my mobo can handle AMD CPUs all the way to 2600XP but it still didn't work! :mad: The good news about all this is that now my system seems to work smoother, and possibly even faster. The defrag must have optimized the HD acess time and the new drivers and settings make the system more stable. But CM still doesn't work! But I did find something interesting. If I point the view to the edge of the map away from the center were all the objects are located it takes longer for it to crash. One time it took nearly 30 minutes. But as soon as I point it to the center it only takes a few minutes or seconds. Interesting... Anyway thanks for all the help I'll just keep on trying.... PS: What chipset do you guys have? Mine is a VIA Apollo KT133A and the board is a Soltek SL-75KAV. TIA [ October 25, 2003, 01:05 PM: Message edited by: Incoming9000 ]

Thanks for the replies. But do you guys use Nividia cards? or a SB Live! board? Maybe it's not DX9b, but the conjuction of certain hardware and software... :confused:

I am posting this here and in the CMBO forum because they have more posts that the tech help forum, and I am getting desperate. Latelly, I have been unable to play either CMBO or CMBB in my system without random CTDs or blue screens of death after a few minutes or sometimes seconds. After trying everything I could think of and following some advices from the Tech help forum I'm starting to think that DirectX9b might be the culprit. But since I'm not sure, I ask if anyone here has DX9b installed, and does it work on their system with CMBO and CMBB? TIA! PS: Sorry for doing this. I don't like to flood multiple forums with the same post, it's just I'm running out of options. [ October 24, 2003, 06:22 PM: Message edited by: Incoming9000 ]

I am posting this here and in the CMBO forum because they have more posts that the tech help forum, and I am getting desperate. Latelly, I have been unable to play either CMBO or CMBB in my system without random CTDs or blue screens of death after a few minutes or sometimes seconds. After trying everything I could think of and following some advices from the Tech help forum I'm starting to think that DirectX9b might be the culprit. Since I'm not sure, I ask if anyone here has DX9b installed, and does it work on their system with CMBO and CMBB? TIA! PS: Sorry for doing this. I don't like to flood multiple forums with the same post, it's just I'm running out of options. [ October 24, 2003, 06:21 PM: Message edited by: Incoming9000 ]

According to the CMBO and CMBB FAQs the errors I've been encountering are caused by a corrupt file in DX so I decided to download the full DirectX 9.0b SDK in the hope that It would make a complete reinstallation of all DX files in my system rather than a upgrade from previous version. Besides since the SDK also has several apps that the retail verion doesn't have, I migh find out something more about what's wrong. I installed it, but still no good. FS9, a DX intensive game, works flawlessly and according to DX diag all's well with my system, but I'm still getting random CTDs and blue screens of death. Could this be caused by DX9b? Could there be something in the new relese that causes incompatibility with CMBO and CMBB? Does anyone else have DX9b installed? Does it work? [ October 24, 2003, 05:53 PM: Message edited by: Incoming9000 ]

Yes, I use Nasty File Remover before installing new drivers. My mobo is a Soltek SL-75KAV With a VIA Apollo KT133A Series Chip. I've disabled all shadowing and caching, PCI Pipelining, P2C/C2P Concurrency, Fast R-W Turn arround, CPU to PCI Write Buffer, PCI Dynamic Bursting, PCI Master 0 WS Write, PCI Delay Transaction, PCI#2 Access #1 Retry, AGP Master 1 WS Write and Read. The AGP has a 64MB apperture and it's in 4X mode. I've fiddled them and altered the settings a few times and nothing changed. I use FS9 to check and see if DX works, and it does, flawlessly. I havent had a crash yet in FS9, so I belive this as nothing to do with drivers at least not the display drivers. My guess is that it must be the Live! board. The drivers are a year old and there aren't any new drivers available for it. I seems Creative has stoped developing the Live! series drivers and concentrated on the Audigy series.

I tried reducing the hardware accel, the sample quality and disabeling the sound in the game. None worked. I've also defragmented my HD checked for error reainstalled GFX, VIA 4in1, DX9B and Sound Drivers. Nothing worked. The blue screem shows the error 0X00000005 which the CM support says it's a corrupted DX file. But after reinstalling all drivers the problem persists. Thanks for all the help but I'm still stuck! Danm! Is there anyone else with a same or similar problem? [ October 23, 2003, 06:38 PM: Message edited by: Incoming9000 ]

It's not just CMBO, CMBB also has the same problem, and about modding, none of them are modded. No FSAA either. I know It causes problems so I have it disabled. I do have the anisotropic filtering on but it doesn't make any diference because the problem still happens with it off. I did notice that wen the blue screen shows up, more often than not, the file nv4_disp.dll appears as where the problem occured with a "Page_fault_in_nonpaged_area" message. Still it doesn't mean it's that particular file that is causing the problem. Update: I updated my drivers to 52.16 WHQL and still the same error with the same file. I don't think it's the drivers. A tleast not directly. I belive it's something with the PCI buffer. [ October 22, 2003, 09:29 PM: Message edited by: Incoming9000 ]