frekk, sorry about your 38 min wait time but if you were playing civ1 on an 8086 processor that was your problem. i also had an 8086 and i can't ever remember trying to pay civ1 on it. 8086 was old for even civ1 standards. i can't find my manual for civ1 but i did find the manual for civnet (civ1 multiplayer) and minimum requirements for it was 486 33mhz. recomended was 66mhz.
Yah yah ... i know ... it was nothing short of a miracle that it ran at all. I learned how to overclock just to run it. And it still took 38 mins to load, counting from the starting screens (may have been another 5 or 10 mins to
get to the starting screens, can't remember).
But the point is that a 486/66 was the latest and greatest when Civ1 first came out. It was an expensive high-end machine and very few people - well ok, very few young people in their early 20s - had them. My XT was pretty much junk even then, but most people I knew at the time who were into PCs had a 386. I knew exactly one person with a 486, and it was a 486/33. At the time, it was unbelievably awesome - it could run anything. In fact, I was using that exact same machine myself in 1997 and it was still a satisfactory machine for the time, a little dated but serviceable. Overclocked it ran civ2 just fine. It even ran Age of Empires without a hitch.
Anyhow, in my experience, RAM and cpu speed have extremely little bearing on how fast Civ 4 turns go by. Like I said, it runs better on my 1800 Mhz cpu with 768 m ram than it does on my 3000 Mhz cpu with 2 g ram. Much, much faster (although admittedly on the older machine I'm running a much less bloated OS, processes are pared down to a minimum, and graphics settings are a bit lower).
please include system specs, map size, number of players and graphics setting so there is some sort of baseline to compare.
I'm fairly certain we'd get wildly variable results even with this information. Some people will be running clean, with few processes in the background, and others will be running dozens of unnecessary processes. Some people's registry will be a tangled mess and others will be running from a freshly installed OS. Mhz has not been a reliable indicator of processing power for years. And so on ...
People with 4 gigs of ram on relatively new machines are reporting 10 min wait times ... that seems insane. I don't think I could make either of my less powerful machines take that long if I tried to replicate the problem. I'd really like to see what processes these people have running, more than what sort of machine they're using, I think.