@DaveAE

Is this test with the SB Live! ?

_________________
After a decade away from the scene, I am back!

@amipal

I'm testing with a SB Live, been playing for 20 mins now, dl'ing 5 iso's and playing mp3's over the network. Normally I crash after just 10 mins or so.

@DaveAE

Seems good so far, will leave it over the night playing downloading iso's...

Regards,
Jocke 'Zerohero' Birging

_________________
Common sense - So rare it's almost like a super power

@amipal

yes

_________________
Audio Evolution
http://www.audio-evolution.com

@DaveAE
That's great, fingers crossed. Let me know if you need a system to run around the clock.

_________________
Are we not done with the same silly arguments and flames yet??!

uuuumh I just can't wait to see how will this end
Holding my fingers crossed.

_________________
You can crack anything with your head, even the head itself.
--------------------------------
...proud AOS user since 1993
--------------------------------

@DaveAE

This is looking extremely positive!!!

I've been running this test for Davy now overnight. Streaming with TuneNet & downloaded 4 x 612mb ISO's.

So far, my uptime doing this is 8 Hours.

I'm going to leave this running while I go to work today too. That'll be a further 11 hours soak test.

Fingers crossed.

FuZion.

@FuZion

Quote:

Streaming with TuneNet & downloaded 4 x 612mb ISO's. So far, my uptime doing this is 8 Hours.

Just to warn you there is a bug in the current beta TuneNet which can cause "Grims" after a period of playing time (it's to do with the Tune information that gets updated with shoutcast streams). The latest version which I'm desperately trying to get into a releasable state, fixes this and a load of other problems too.

Anyway, just so you know; a crash after 8 hours could be down to TuneNet.

Cheers,
Bean.

_________________
OS4.1 + SAM Flex
RIP my A1XE.. that used to have an appetite for batteries!

@Bean

Ok cheers. I'll switch to playing audio from my hard drive for the next 8 hours or so then.

FuZion.

@DaveAE

So far it looks good. Lousy weather here, so took a power hit after 1hr 30 mins of no problems (no UPS on the A1). Now up for 3hours 30 minutes and still going while downloading 8 ISOs simultaneously. Normal ETA to crash in these conditions has been ~30 minutes for me.

What was changed?

_________________
Are we not done with the same silly arguments and flames yet??!

@wegster

no problems here ran amp all day and d/loaded yld3 and a few large divx movies

sblive 5.1
sii0680ide.device
A1XE@1000mhz core voltage 1.79v
1gig redgestred self error checking ram
update3
radeon 7000

maybee the sil card fixes the problem ?

@poweramiga2002

No, sii680 isn't the cure. At least not here. Somewhere in this or the original thread it was ruled out.

Jack

_________________

"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg

@Steff

Quote:

Don't know what you think is so funny here. We have an experimental board that hasn't had the operating system it was supposed to be used for testing until at least a year after it was produced. Many of these "bugs" that have shown up are "known" bugs from the PC world (so it has no exclusivity to the amiga) that had there own workarounds (fixes) at the time they had the problems. Most of the these problems revolve around the Via southbridge which Via has been less than generous in making public all of it's drawbacks as well as not sharing any info pertaining to the "fixes" for any eventual "bugs"! The PC world is often just as full with "fixes" and "bugs" that you just aren't aware of.

These PC “fixes” doesn’t quite compromise the fundamental claimed feature or it will place the HW provider open to consumer refunds/remedy/law suites. PC BIOS with VIA 82C686B fix is materially different to A1’s fixes i.e. PC’s NB has enough programmability to compensate for basic functional issues. 686B's DMA issues don’t apply with motherboard sporting an AMD 761 and 750 Northbridges.

With AMD and VIA viewpoint, VIA will not acknowledge that their 686B is at fault i.e. blames motherboard manufactures for incorrectly setting VIA's Northbridge.

PS; VIA's 8235 SB (with K8T800 NB e.g. MiTac 8355) works fine with standard MS WinXP UDMA IDE drivers.

Last edited by Hammer on 20-Jul-2005 at 10:32 AM.
Last edited by Hammer on 20-Jul-2005 at 10:27 AM.
Last edited by Hammer on 20-Jul-2005 at 10:26 AM.

_________________

@DaveAE

Seems to be working fine here. Been playing all night and most of the day, will continue with the tests.

@ all testers of DaveAE's new discovery

I get some glitches in the sound, but I'm not sure they weren't there before since I didn't play that much music becuase of the bug. Can anyone confirm this behaviour? From memory I didnt have them before, it almost seems like it skips a bit when the crash normally should happen...

Regards,
Jocke 'Zerohero' Birging

_________________
Common sense - So rare it's almost like a super power

any chance the topic can be change from this increasingly wrong one we have now?

im sure a few ppl have indeed chucked their current sb's out and bought new ones, while the problem has been worked on, and it seems is on its way to be a problem of the past.

moderators have power here, and this topic can cause more harm (to ppl's wallets) than you may think.

now back to the show...

_________________

@DaveAE
Still playing (and downloading) after 9 hrs 30 mins. Looks good.

_________________
Are we not done with the same silly arguments and flames yet??!

@testers

Good to hear the results. FYI, you are testing with a year old eth3com. Now I only need to test with about 15 revisions to see in which one it went wrong. Unfortunately I became ill (nothing serious) today and tomorrow I would be having my holiday on Crete. I hope very much I can make my flight tomorrow. I'll get to the bottom of this after my holiday, so see ya in August.

_________________
Audio Evolution
http://www.audio-evolution.com

@DaveAE
Quote:

Good to hear the results. FYI, you are testing with a year old eth3com. Now I only need to test with about 15 revisions to see in which one it went wrong. Unfortunately I became ill (nothing serious) today and tomorrow I would be having my holiday on Crete. I hope very much I can make my flight tomorrow. I'll get to the bottom of this after my holiday, so see ya in August.

Thanks for all your work on this DaveAE. Now go and have a rest on Crete!

_________________
After a decade away from the scene, I am back!

@DaveAE

Hi Dave,

The eth3com.device I was using before where I was still getting the crash was '51.12 (05/05/2005)'. I also have an older '50.9 (03/03/2004)' (This may have been my update 2 version). I used to crach with this file in use too if that helps.

As for this current test. I've just got home. She's been running for almost 20 hours, online, downloading & playing audio. Nice find

FuZion.

@Derfs
Considering no fix is immediately available, and the fact we're still not sure of the root cause here (DaveAE? ), I'm not sure the title still isn't accurate. I'll update it tho a bit.

_________________
Are we not done with the same silly arguments and flames yet??!

@DaveAE

Ok, ran from midnight until 7pm, so 19 hours, downloaded 18GB of files simultaneously while playing mp3s, identical tests as before that locked up in ~30 minutes before.

Now..autopsy?

PS- the 'new' driver is like 3x the size of the other, assuming this is a debug/non-stripped driver?

Last edited by wegster on 21-Jul-2005 at 01:07 AM.

_________________
Are we not done with the same silly arguments and flames yet??!