Some days the wsxservice.exe program reports a very high I/O Other number in taskmgr (more than 20 millions) while other days it is very low, less than a couple of thousand. I am running Windows 7 and Winstep 12.02.1037. When this happens I usually kill that process. Why would be report soo high in taskmgr?

i know when workshelf.exe does that all you need to do is open and close preferences to get it to lower the amount of ram being used. you can try opening the workshelf preferences when that happens with wsxservice.exe to see if it lowers the amount of ram being used. or if that doesn't work try the nextstart.exe preferences before killing the wsxservice.exe.

Sigh.

Don't kill that service - it's the service that allows you to do *everything* that would require a UAC prompt otherwise.

As for number of I/Os, ignore it, those are not I/Os to disk but to a *memory* mapped file (that's how the service communicates with other Winstep applications).

If Jorge doesn't mind, I'd like to add my 5 cents here. Just to make things clearer, he didn't say anything wrong (obviously).
The field "I/O other" in the task manager is NOT bytes. It's "number of accesses" (there's a different field named "I/O Other Bytes" for that). But even if it were bytes, it doesn't mean that a programme is actually *using* that amount of bytes in memory or disk. It just counts the times (or bytes) written by that process since Windows booted up.
Consider this scenario: you have a programme that will check the temperature of the CPU 10 times per second. That means that every second, it will do 10 transfers of 4 bytes (32-bit floating point temperature data). After just one hour, that programme will have 36000 accesses and 144000 bytes of transferred data.
Now, imagine that you're not just reading *one* temperature, but also temperatures of your 4 hard disks, the temperatures and voltages of each core in your 8-core system, the temperature of your GPU (video card) and also 8 voltages in the computer and also 4 fan speeds. The aforementioned numbers will be multiplied by 32. Which means, after just one hour of operation, that "I/O Other" will register 1152000 accesses and 4608000 bytes.
However, that doesn't mean that it will *use* 4 megabytes of memory per hour or anything, since that data is just used once and then discarded.
Consider another example: a programme that does a surface check of your hard disks. That programme will read every single byte on the surface of your hard disk, and then report on errors. After just one run on a medium size hard disk (say, 500GB), its usage will be a few million accesses and (obviously) 500 billion bytes accessed. That doesn't mean that it's occupying 500GB in your RAM -- obviously, since you don't *have* that much RAM -- but that it *accessed* that amount of data since you started that programme.

All in all: accesses mean nothing on their own. Any browser will reach millions of accesses after a couple of hours of internet surfing. Windows Explorer itself will have tens of millions of reads, writes and "others", even if you never open an explorer window.
So, indeed, like Jorge said, don't kill processes just because they're doing their job. If you want memory usage, check the "Memory - Working Set", "Memory - Private Working Set" and "Memory - Commit Size" columns.

Cheers!