Sidebanding and fast writes are hardware techniques to increase communication performance between the chipset and the video board, but are known to cause problems in some cases. The first advice you get in tracing AGP related errors is to disable both.meerkatt said:Never buy a pre-built again, will build my own like always have. But some the questions you asked on my system specs, not sure about a couple of them on what you mean. Sidebanding? , fast writes? AGP aperture size
As far as I know, it was no problem upto and including 512 MB. Only above 512 MB gets Win9x into trouble. Heck, I have 512 MB myselfjdrou said:Are you sure you have 512MB? That could be the problem. Win98 & WinME need some tweaking to handle that much properly. I believe you need to add to your system.ini file:
[Vcache]
MaxFileCache=65,536
The largest value you should use is 524,288 even if you have 1-2GB RAM.
A couple of people here with Win98 reported their CTDs stopped after adding this tweak so it's worth trying. It's mostly a performance enhancer; as you've posted before you want to maximize the amount of RAM available to the game and that's what this does. The real problem is probably the game's memory usage and/or other processes running on their PCs taking up memory. I haven't used Win98/ME with more than 256MB myself but researched it a bit for a friend who was looking at upgrading to 512MB. If you have over 512MB then it seems to be required rather than just a tweak.jpd said:As far as I know, it was no problem upto and including 512 MB. Only above 512 MB gets Win9x into trouble. Heck, I have 512 MB myself
Jan Peter
Interesting. Changing the refresh rate and the DirectX problems with a Paradox game vanish. It looks similar to what I found out myself, documented here:meerkatt said:I do have 512 ram and my video card GeForce4 has 128mb. I did a couple of tweaks to my video card. Switch from adapter default to optimal refresh rate. Have no idea how it got switch to adapter default and another tweak - played the game and no CTD or ddhelp error this time. Weird.
A crash inside DDHelp will effectively disable DirectX until a reboot. It's responsible for interacting with the AGP service, amongst other things. Given that in your case it's not just HoI, it is likely that something is not right with your config.Frank W. said:Just for the record, i have the DDhelp prob, too !
i will try the tipps you gave above.
btw: have reeinstalled directx, also the directx diagnostics say "no error", have scanned for viruses, AGP aperture size 64mb, sideband on, fast write off ( not supported by I815 chipset ), perhaps it runs with your tipps above.
i also had the ddhelp error sometimes, when i close my browser ( mozilla ). after this no game will start it seems, must reboot then.
my driver is 3.10 which caused me some trouble already ( windows doesn´t boot ), AGP only 2x instead 4x etc.. but i think i had the ddhelp error also with my old 3.7 driver......
This definately suggests that under normal settings your AGP subsystem is overstretched. Lowering the accelleration in effect disables certain features of the GPU, and possibly the AGP speed and addressing modes (like fast write and sidebanding, that's up to the driver). Besides making your system slower, it vastly reduces it's power consumption, and with it heat dissipation.Frank W. said:o think setting the hardware acceleration ledger far to
the left in the system configuration prevents the crash
with my current HOI, but all is quite slow now.... at least
i have played without crash for 3-4 hours.