Testing....

[gd_barnes]

Max,

No it CANNOT wait any longer than the 10 days that it has already waited. The clients have been released! Nor can loading port 6000 wait.

But the CRUS results that I didn't really need, those got processed right away. Priorities straight please!

I'll do both of them on Sunday during my business trip.


Gary

[mdettweiler]

Originally Posted by gd_barnes

Max,

No it CANNOT wait any longer than the 10 days that it has already waited. The clients have been released! Nor can loading port 6000 wait.

But the CRUS results that I didn't really need, those got processed right away. Priorities straight please!

I'll do both of them on Sunday during my business trip.


Gary

Thanks, that works. (I ididn't know about port 6000 though. )

As for the CRUS results, whoops, sorry about that...I'd completely forgotten about the readme thing. I've been especially busy over the last week or so and that's why I didn't remember, whereas the results processing jobs came to mind right when I had just enough time to squeeze them in...hence why they got done and the readme didn't.

[gd_barnes]

Originally Posted by gd_barnes

Just a note for you guys:

Weekends on business trips are insanely busy for me. I'll likely only make it on to answer pressing questions in the forums and in Email and to report primes; perhaps for a half-hour at most.

I will be back late Monday but have some family matters to tend to. By Tuesday, I'll be back in full swing of the projects. I kind of had to "pay the piper" finally for spending 3-4 hours/day on the projects almost non-stop for the month before I left and this busy time is my payment. lol Unfortunately I'm not retired just yet but I know I'll stay busy when I am. :-)

Either one of you, if you can help answering any others questions or anything else adminstratively on the proejcts at this time, that would be greatly helpful.

Max, you might keep an eye on the public and private servers. I think you usually do anyway. It appears that port 6000 will need loading up before Monday.

Thanks again guys.


Gary

So I guess the above was not clear enough about port 6000, huh?

Doing the README would have taken 10-15 mins. Are you telling me that the results would have taken less? I think not. The README was asked for 3 different times. How could it keep getting forgotten?

Priorities please!

So I've now lost an hour out of my business trip. I've now loaded up port 6000 and updated the drive, which took way longer than it should have because of the terrible remote access that I now have. That's why I asked you to do it.

Karsten is busier than either of us. Maybe we need to give him remote access to my machines to load up servers. You know, if you need something done, give it to a busy person. It will get done!

Attached is the updated Linux README. Karsten, can you review the 1st line of the 1st para. and the updated para. about your patches to the Windows binary values. I made sure to note that the any Linux changes would be "similar" but not necessarily the same as the example that Max originally put in there. After doing the review, can you update it in your Linux client link? That's what I've been hoping for all along.

I don't have any more time to review the Windows documentation. I'll do that late Tuesday. Max, you don't need that on your plate. In the future, if I need something non-technical done, I'll just do it myself. It's far easier. I've spent 30 mins. in reminders and explanations about what we needed on the README and it only took me 10 mins. to change it. That's a no-brainer.


Gary

[kar_bon]

Originally Posted by gd_barnes

Attached is the updated Linux README. Karsten, can you review the 1st line of the 1st para. and the updated para. about your patches to the Windows binary values.

1st line looks better now!

the patches are ok, too.
i've decided not to show the addresses of the patches (will be different with new cLLR-version!), only the texts supressed in an extra note.

[mdettweiler]

Originally Posted by gd_barnes

So I guess the above was not clear enough about port 6000, huh?

Doing the README would have taken 10-15 mins. Are you telling me that the results would have taken less? I think not. The README was asked for 3 different times. How could it keep getting forgotten?

Priorities please!

So I've now lost an hour out of my business trip. I've now loaded up port 6000 and updated the drive, which took way longer than it should have because of the terrible remote access that I now have. That's why I asked you to do it.

Karsten is busier than either of us. Maybe we need to give him remote access to my machines to load up servers. You know, if you need something done, give it to a busy person. It will get done!

Attached is the updated Linux README. Karsten, can you review the 1st line of the 1st para. and the updated para. about your patches to the Windows binary values. I made sure to note that the any Linux changes would be "similar" but not necessarily the same as the example that Max originally put in there. After doing the review, can you update it in your Linux client link? That's what I've been hoping for all along.

I don't have any more time to review the Windows documentation. I'll do that late Tuesday. Max, you don't need that on your plate. In the future, if I need something non-technical done, I'll just do it myself. It's far easier. I've spent 30 mins. in reminders and explanations about what we needed on the README and it only took me 10 mins. to change it. That's a no-brainer.


Gary

Ah, that would explain it...I believe I semi-skimmed that post (very bad habit ) and thought "oh, Monday, that's a ways off". DUH.

The readme looks good. I'll upload it right now...yes, really, right now. lol Edit: done