@nubechecorre

What news do you expect?

@Snuffy

Quote:

Quake3 on the other hand fails to even start with Cygnix assigns, and there are some others too with such problems.

@cygnusEd

Quote:

I get the idea. But please keep it in the todo list, because currently X11 interferes with a lot of programs, not just the OS4 SDK. For example it took me ages to find out that Quake3 no longer works because of the assigns Cygnix makes.

Quote:

Then I would suggest to remove the lines from the install script, which adds those lines to the user-startup, or it'd be even better to make the installer remove it if it finds such in the user-startup from an older Cygnix installation.

@afxgroup

Yes, with the second solution it'd good to remember the old assigns and restore it at exit. It's not a nice solution but it'd be better than the way it is currently, having to edit the user-startup and reboot each time we want to run Cygnix.

For the mapping solution I meant Cygnix:bin, etc. not Cygwin, this is what happens to you when you use PCs at work for too long... :/

@cygnusEd

Is it not possible to map accesses to bin, usr, etc. to a seperate directory, instead of using an assign? So that programs would reference them as Cygwin:bin/ Cygwin:usr/ , etc.? Or use assigns like cygbin:, cygusr:, etc. It should be just a matter of mapping to a different path/assign.

If no such solution is possible, then at least you could only make those assigns when the user executes the Start_Cygwin.bat script, instead of directly in the user-startup. This way it would not interfere with other programs, unless you actually start Cygwin.

@joerg

I was thinking of it being only optional of course. I tested CPUTemp.docky 52.10 and added "dnetc crunch #1" to the tasks to ignore and it works! I see that you display a dimmer graph which includes all tasks and a brighter one with tasks filtered out, this is nice. Although the two percentage values I don't really like (I'd prefer to have only the filtered out version displayed) but I can live with it for now :) Thanks!

@abalaban

I had a chat with joerg about how he does CPU usage measurement in his CPUTemp docky and with that approach it'd be easy to filter out some tasks so I'll see if I can add this to CPUInfo.docky when I get some time, maybe via a tooltype where the user can specify a task name to filter out.

@Raziel

Quote:

Exec's idle task also eats all idle CPU time, something always runs in the background, the idea of dnetc is that it makes the CPU do something useful in this idle time rather than just busy looping. You don't notice whether the idle CPU time is spent in a simple busyloop or something else like crunching dnetc. This is why it's a good idea if a CPU meter can filter out the dnetc task so that with dnetc running in the idle time I can still see how much CPU time is really used when I start 3 instances of dvplayer or whatever. Filtering out dnetc task should be optional of course, some people might for some reason prefer to look at a constant 100% gauge all the time.

@joerg

I know that your CPUTemp docky uses some exec hooks to power down the CPU during idle time on 750 CPUs, but even on other CPUs where this cannot be done and exec's idle task busyloops in the idle time, most people don't want to look at a constant 100% CPU gauge, but rather to see CPU usage spent outside of idle time.

@MichaelMerkel

dnetc runs in the idle time, when nothing else runs. Without dnetc running the idle time is spent in exec's idle task. The idle task also uses CPU time, but still we don't want to see 100% CPU usage even when nothing but the idle task runs. Same with dnetc, I know that it's crunching in the idle time of my system, but I want to see the CPU time that my real applications use.

@joerg

And how does your current code monitor CPU usage? I suppose it's a more accurate approach than what CPUClock docky does? Would it be difficult to add the possibility to filter dnetc, so that the CPU usage meter is still usable when you have dnetc running in the background? I've been told that most CPU meter tools on MorphOS do this already.

@Troels

Take a look at the Lunapaint Homepage (especially the 'features' section . It looks comparable to Photogenics, but it also has animation support and it's free. Its development is progressing really fast.

So, is anyone porting this to OS4?

@joerg

hehe, I get 8 degrees :)

@joerg

A cpu.library is a very good idea, we need some central API which can be used by anything that wants to get information about the CPU (temperature, current CPU usage, etc.) although personally I think that such functionality belongs to exec.library.

@joerg

CPUInfo.docky is the same as CPUClock.docky, I just modified the part which produced the output of the measured data. It would be good to combine CPUInfo.docky and CPUTemp.docky into a single docky, which displays the temperature next to the CPU usage.

@Raziel

No, it's not a game. It's a system for people to communicate over the internet, but using a 3D virtual world instead of the old chat windows and such. Everyone has a 3D avatar which they can customize, etc. It seems to be heading for great success. You can read about it on wikipedia

Now that it's open-sourced (see here), is anyone porting this to OS4?

Hmmm, the CPUClock docky sources I have do not display the date, maybe it was updated since I asked for the sources. It'd be very easy though for me to enable displaying of the clock together with the CPU percentage. It'd be even better to be able to change some parameters of the docky (size, colours, etc.) but I don't have much time to have a look into how that can be done for dockies (tootypes or prefs window maybe)...

@mufa

You mean have all that crammed into the docky? You wouldn't be able to see the graph anymore.

@orgin

OK, thanks.