• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
I had exactly this same of problem, I reported it, tried everything, and still nothing worked. I hadn't paritioned the drive, and I did try it with some of my old drivers. Nothing. :( AND I have these resolution problems as well, combined with frequent aborts to the desktop whenever I quit a game - if the resolution changes, I can change it back via the control panel before I can run anything, because programms either won't work, or they suffer from image problems.

Quite frankly, It all pees me off substantially.

I haven't heard the province 'click' more than once in a game for about 5 months now. Ho hum.
 
Originally posted by Vincent Julien
I had exactly this same of problem, I reported it, tried everything, and still nothing worked. I hadn't paritioned the drive, and I did try it with some of my old drivers. Nothing. :( AND I have these resolution problems as well, combined with frequent aborts to the desktop whenever I quit a game - if the resolution changes, I can change it back via the control panel before I can run anything, because programms either won't work, or they suffer from image problems.

Quite frankly, It all pees me off substantially.

I haven't heard the province 'click' more than once in a game for about 5 months now. Ho hum.

Perhaps you could start a new thread and give me complete system specs and a detailed description of exactly what's happening and maybe we can trace it down. I'd prefer to do it in a new thread, though, since I find it slightly easier to keep tabs on where we are and what we've tried that way.



jpd: Yep, I think you're right that it's a different sound...funny how when you've been playing with it for a long time you sort of forget what the differences are. Keep me posted if you run into any major anomalies.
 
Well, another update to this problem.

Today it reappeared again, with a vengance. What happened? Well, to check my speaker calibration after returning form a LAN party (had to use 2 speakers, instead of the 6.1 set), I noticed that the speaker calibration program refused to run.

Also, the other support programs didn't work. All complained about missing and/or incorrect drivers. So I checked the device driver manager. No problems. Then I started the creative diagnostics. All test but the hardware and directX failed ?!?.

So, I pulled out the driver CD and reinstalled the drivers. Sounds simple enough, doesn't it? Well, after the reboot, the diagnostics all passed, the support programs worked again, but the EU2 sound problem also surfaced again. And this was with the WDM drivers, not the VxD's.

Since I had recently upgraded to EU2 1.06, I had to make sure that that wasn't causing the problems. So booted into Win2K, and started EU2. Worked flawlessly.

Rebooted to Win98SE, and used the creative driver CD to completely uninstall everything. Then rebooted, and reinstalled the lot, again with the WDM drivers. One more reboot, and now EU2 worked as it should.

I am baffled. Something, obviously, must have gone wrong somewhere, that even the diagnostic tools were unable to catch.

Jan Peter
 
Truly mystifying. Perhaps your Win98 partition is possessed and what you need is an exorsist? :p Seriously, though, I wish I could think of a good reason for this but I'm completely devoid of ideas.
 
As am I. Must have something to do with the ever increasing complexity of both the hardware and the driver software. Just checked the Audigy drivers. Drivers + support software is a bloated 145 MB. The drivers alone are over 50 MB in size.

Maybe those drivers took a wrong turn somewhere, when I connected my two speaker portable set at the LAN party last saturday, without first explicitly changing the speaker calibration to match. The sound worked flawlessly at that time, though.

Jan Peter
 
Originally posted by jpd
Drivers + support software is a bloated 145 MB. The drivers alone are over 50 MB in size.
:eek:

*collapses on floor!*

Yup...I now, more and more often, look at that dusty C64 with fondness. ;)
 
Indeed. I have spend many, many hours gaming on that compie. In fact, it is still sitting on a shelf somewhere at my home.

For it's time, it had amazing sound and video capabilities.

Jan Peter
 
Did you try your hand at programming games on it as well? I did and I remember the joys of having to poke values to a higher register and then changing the screen display from the bottom 16k to one of the other 3...and then you'd have the inevitable crash and end up with a black screen and no idea what caused it, plus you then had to type 4 long poke commands "blind" just to get the register back to normal.

Ah...the good ol' days. Seems things haven't changed all that much. :p
 
No, I didn't program on the C64.

However, I have machine coded a PacMan game on my old, blank and white Z80 micro. I did have the help of a rudimentary assembler, so only a limited amount of POKEing was involved.

Jan Peter