My Vendetta playing time is about to be drastically reduced. The machine that I've been spending most of my time playing VO on is literally burning itself out, (severe timing and signal transmission problems) and even time that I would have been spending on VO on my other comps is being poured into trying to fix this computer.
-:sigma.SB

:o

What motherboard? Just so I never, ever buy one.

Some pile of dirt German import which was apparently chosen to cut costs...I guess you get what you pay for. (no, I didn't build/choose this comp, I inherited it when my boss was arrested, and even severely messed up it's better than my 180MHz 604 that I had before...)
-:sigma.SB

There's the start of a great story when you hear "I inherited it when my boss was arrested........". LOL

I was just thinking the exact same thing sarahanne. :)

Post that story in off topic for us sometime solra. :)

Ok, As for the hiccups, can you do an experiment for me to see if it helps you?
copy vendetta.rlb to vo.exe (or something similar). then run 'vo -b' from a DOS prompt. Make sure you are in the directory where VO is installed to. (ie. same directory as vo.exe, media.rlb, etc...)
That uses a different timer mechanism and maybe it will help.

This assumes you are in Windows. If you are in OS X, then please ignore this message.

What about if Sol uses Linux? =D

Have you ever seen a linux system with temporal hiccups? Doesn't Linux keep the system time separate from the RTC anyhow? After I do a rdate -s, I always need to sync the hardware clock with the software clock, so I figured so...

> What about if Sol uses Linux? =D
The machine in question is a Linux machine, yes... http://slashdot.org/comments.pl?sid=125735&cid=10531105
-:sigma.SB

Just out of curiosity, have you done a kernel recompile lately? If so you might wanna double check your .config

Do the follwoing and tell us what you see:

gunzip -c /proc/config.gz | grep RTC

Assuming that you have CONFIG_IKCONFIG_PROC enabled...

> have you done a kernel recompile lately?
Yes.

> gunzip -c /proc/config.gz | grep RTC
CONFIG_RTC=y
# CONFIG_SENSORS_RTC8564 is not set

I'm posting from the machine that's having problems right now, and it seems to have forgotten about its soundcard.
-:sigma.SB
Edit: Someone move this to the Linux forum.

Maybe the new kernel is using a different cpu scheduler? What kernel is it?

I've been using the same kernel source I originally downloaded oh so long ago...
sbizna ~$ uname -r
2.6.8-gentoo
-:sigma.SB

What scheduler? CFQ? Anticipatory? Deadline? I use CFQ with no problems.

No idea...whatever 'make menuconfig' sets without intervention.
-:sigma.SB

I think that's anticipatory. You can pass a boot option to change it. For example, my grub.conf boot line reads thusly:

title=Gentoo Linux
root (hd1,1)
kernel (hd1,1)/bzImage root=/dev/hdb4 idebus=50 elevator=cfq video=vesafb:ywrap,mtrr,1024x768-16@60 splash=silent,theme:gentoo

By using elevator=cfq, I switched to the cfq IO scheduler. Pretty cool. I don't think it'd cause your sort of problems, though. It's just an IO Scheduler.