Are we there yet mommy?

[Roj]

I've been away from the forum for a while and was just wondering how close to the final is Build 75.

Thanks...

[Hanzo]

Are we there yet mommy?
... LOL !!! ;)

I remember Paul mentioning something about up to B80 or something... I'm not sure and of course I might be wrong

[acozz]

Seems like it's past the point of new features being added and is in bug fix mode.

[Rex_Mundi_Incarnit]

No more new features! :shocked:

Now come to think of it, i couldn't think of any more ;)

QCD HAS IT ALL!!

[Roj]

Seems like it's past the point of new features being added and is in bug fix mode.I generally do NOT run dev builds. That being said, I've been running Build 75 (I finally broke down and couldn't resist the resizable playlist) for days, have hammered the hell out of it and it's remarkably solid. The only thing I've found is that it tends to skip *backwards* if I'm doing insane things vis a vis disk I/O and CPU utilization (I mean "bring my Athlon XP 2600+ Barton to its knees" type of insane). While I find that strange, I suppose that's the least to be expected when I'm 1) burning and verifiying a DVD at 4x, 2) decoding large (50Mb apiece) Usenet binaries 3) refreshing the 1.6 million message header database that represents the alt.binaries.dvdr group with its appellate housekeeping and expiring of dead articles 4) playing QCD with a playlist located across my network 5) downloading with 8 concurrent threads from two Usenet servers (hence the decoding and header refresh mentioned above) and finally 6) reconstructing a 4.5Gb DVD ISO with PAR2 files (THAT alone will eat CPU like no tomorrow). All simultaneously, of course.

In short Paul, not too damn shabby! :) :) :)

[acozz]

If it skips back like that I'm pretty sure that means the buffer didn't get filled so it just repeats it. Obviously this only occurs if there isn't enough resources to fill the buffer.

[Roj]

If it skips back like that I'm pretty sure that means the buffer didn't get filled so it just repeats it. Obviously this only occurs if there isn't enough resources to fill the buffer.
Thanks for the head's-up as to the reason. I kind of figured it was something like that - I mean, c'mon - at that point my CPU is pegged at 100% and I'm flagellating my Western Digital JBs into oblivion (the hard drive light remains continuously on for about 15 minutes or so)! :)

[blackspawn]

Thanks for the head's-up as to the reason. I kind of figured it was something like that - I mean, c'mon - at that point my CPU is pegged at 100% and I'm flagellating my Western Digital JBs into oblivion (the hard drive light remains continuously on for about 15 minutes or so)! :)
eh eh don't forget to use pretective clothing (in case sudden combustion ocurrs) ;)