Do you have linuxcoin final? Everything should just work with it.
[/quote]

No, I'm sticking with v0.2b, since it's working ok for me and I don't need all the network boot stuff.

spiccioli.

Windows version is on hold while we await the developer who is working on it to show up.

On one of my boxes it works perfectly. On another I get the 0 byte whatever error.

So, sort of.

No offense, but do read up on pkgconfig a little bit before commenting. For how long have you been involved in packaging? I've told what's the correct way of doing it with pkconfig and locally built binaries.

Yes, I did but I guess you're not on Windows since there's no Windows binary for 1.5.3 yet.

Also remember that I really don't have any cl-device in my system.

If you have been building software for that long, it should have taught you that building complex software with many dependencies without an unified system for discovering library paths, compile, link flags etc. (which is exactly what pkg-config is) is a living hell of hooking up each and every library to the build system via crappy third-party autotools macros for which no decent unified and maintained archive exists. And in this particular instance, these macros were even unable to resolve version requirements for which reason (I guess) they were finally nuked in favor of pkg-config.

It could be that your system doesn't ship pkg-config (which I would doubt, unless it's Windows), but since you've been building software since vax days, it would certainly take you near-zero effort to build pkg-config in addition to cgminer. I bet there are even third-party repositories with pre-build binaries somewhere around.

There any other way to set affinity and lock down the usage to a single core?  Might help with the 100% bug.

Use the following in your  .bat file to launch cgminer, will force cpu affinity to a single core.. which will max only that specific core out to 100%.

Nice, looks like that works.  If anyone is using Windows 7 and want's something similar to what I'm doing I added the batch file code below.  Basically I've created a single batch file that includes all the information needed to launch the cgminer processes for all of my miner's and stuck it in a network share.  I then set up a scheduled task on the mining machines set to run at login and launch the batch file in the network share.

This way I can make mass configuration changes all in one location instead of having to jump to individual boxes and modify each one.


I don't believe the timeout function is available on other versions of windows, but this seems to work fine on W7.  It can easily be expanded out for multiple boxes as well by just replicating the host variable checks and subroutines for more machines.

No, it's happening on 3 machines, any of which have SDK 2.4 on them.  I'm trying to roll back to 2.1 on some of them, but they're giving me some issues.