@K0rky

Tried it few minutes... very funny as years ago.

@bean

Quote:

Heh, no problem, take your time, Rome wasn't taken doen in one day either (or something like that)

I'll do the test with AmigaAmp, ANR is a nogo for me.
"ClassicGUI" is crashing on me badly

@Raziel

Can you please try doing the same tests with both AmigaAmp and ANR and then PM me? Please test for some time as well.

The skinnable interface is my major concern at the moment, I'm already a day overdue!

Cheers,
Bean.

P.S. Whilst developing I do have TuneNet running (usually playing the Groove Salad station ), along with iBrowse and Simple Mail. But then I am using the latest compiles.. Ho humm...

@afxgroup

Quote:


What is the difference between Mencoder & ffmpeg? They both appear to do the same things.

@bean

Quote:

I can add YAM (most surely) to the list of programs crashing
due to TuneNet running...

That should not be a drag-down of TuneNet, i love this program
and will use it furhtermore, even it other programs crash.

First i thought it was crashing because it is old (I'm using 2.4p1
here, will update as the update becomes available) but then i
realized it was crashing ONLY when TuneNet was running with a
radio stream OR was running and closed down (with a radio stream)
Just like the case with AWeb

Yam is crashing with amissl.library, but only when fetching
mail AND TuneNet is running

Looks like it can't inherit the TCP stack to fetch mail
^^^^^^^^
(No coder here, so i may be completely wrong)

Thanks bean for that awesome program

@bean

Any update on the AWeb crash issue?

...and what on earth is a Gataux?
Sounds like a hairy middle-age french man to me!

@Swisso

Ah well, just don't go yet.

I must pesker you with questions ... no, you can't run, already tied you to that marvellous uncomfortable chair

Ready?

/me turning the light right into Swisso's face



Ok, here we go.

1. It's (7457 @ 1.267 Ghz - 512 Kb 2nd level cache) this version, isn't it?

2. What do you use for temperature measurement? @joerg's CPUTemp docky?
2.1. Where did you get the base temperature (TEMPOFFSET) from?
2.2. Where did you get the factor (TEMPFACTOR) from?
2.3. How do you know that it is the right temperature at all?
2.4. Is the temp measureing chip(?) useable in OS4 then?

3. Which heatsink/fan combination do you use?

4. How long did the repairing (in the plant) last for your module?

5. Do you crack for Team 200?

6. Do you want me to untie you?



Thanks for your time

@orgin

Deleted some unconfirmed users from april.

@Swisso

NICE!

Do you notice any speed improvements in Quake 3?

@Swisso

So tell us about the repair/upgrade. How much, how long did it take, etc?

[or post a URL to any previous discussion I may have missed]

@Swisso

Please make a speed entry with your very fast amigaone.

OGR databse:
http://n0cgi.distributed.net/speed/qu ... pe=all&arch=2&contest=ogr

RC5 database:
http://n0cgi.distributed.net/speed/qu ... =all&arch=2&contest=rc572

Make a speed entry:
http://n0cgi.distributed.net/speed/form.php

Great! Thanks for letting us know.

@Swisso

How fast is that. Wow. My 933Mhz runs at 27C. Should I clock it more as I have an extra one;)

Edit: had;)

Hi all,
just a quick note to let you all know that the 7457 processor module has now been running my A1 continuously since March25th. you can see my d-net contribution under raoul.penel both for OGR25 and RC572.
The cooling temperature has remained a steady 34 degrees, and there have been no glitches.

@ChrisH

As this is a general thread on AOS and its evolution, could you say a little bit more about "dynamic compilation"?

I presume it means that a generalised assembler like language, TAO's VP, is compiled to the particular processor on the fly, but that it is compiled for a particular configuration?

For a number of reasons I see scripting taking a central place. However, specifically compiled generalised code is a necessity (whether statically or dynamically - TAOs efforts have convinced me that the loss of speed in doing this is real, but practically negligible).

I would break things down into a number of connected but essentially independent aspects.

1) Hardware agnosticism, whether dealt with by "easy" porting or dynamic compilations. This translates into forms of software permanency as well as widespread application.

2) Software bloat, not just in terms of size, but overburdened functionality, needless code duplication, an intractable barrier for efficient usage.

3) Off the shelf do everything applications (related to point two), which effectively means adapting work to fit the the program, rather than evolve the apps to fit the needs of real world tasks.

4) Making the user into a mere appendage to software design (the cultural aspect of point two and three), the user needs the tools to dissemble and reassemble software components to fit tasks.

Obviously this last point will take time to evolve, but it begins by separating out the elements common to all software - the processing engine, from the form of presentation (GUI), the flow of data from pre-designed engines. Data handling and general flow control needs to be something that the experienced user can adapt and change.

I am against using scripting as a cure-all, it is not. Rather I want it to be the glue between high performance engines that can be harnessed together practically. There, if things are done properly, the processing overheads of the interpreted language, the simple flow control involved, is no deficit to speed at all - ideally, despite the interpretation, the processing is done within the manual mouse click (it is slower than compiled code but placed where this does not matter).

The design trick is in making truly generalised compiled processing "engines", cut down to their most efficient form.

A scripting language that is easy to learn (and remember) flexible, syntactically consistent (no specials), unbloated: Like LAU or REBOL, but not like Python, which has become overburdened by special extensions.

The last two bits:

5) A minimalist OS, to run all this.

6) A file system which "tames" and organises all the multitude of "bits and pieces" being shared.

I know what your thinking, not another Amiga related site!! But this one should be a bit diffrent. I have wanted to do this for a long time. My site theme is one that will allow all Amiga type systems on one portal. It will have areas for all of us to post and talk about the latest and greatest.

What I need is help setting up Xoops so the site looks clean and polished like this one and the others. i need art, help with the modules in Xoop and getting the layout correct and things of this nnature. Are you up for it? The drop by and take a look at it so far. I know its ugly, so help get it better!

http:www.acill.com

(once the name is deided the domain will change and match it as best it can)

@ktadd

what a powerful program.........

@Snuffy

Quote:
Do you mean the (by default black) line/border around the shapes or the blue "selected object" highlight?
By default the black borders are 10 units (1mm) thick, which is reasonable on most levels of magnification here. Thinner borders don't really scale well when zoomed really far out as I have to draw at least 1 pixel. Nearly time to rewrite the drawing engine...

How much memory are you using? Is it related to zoom in/out or other operations as well?


Thanks for bringing up these points, Snuffy.

@Snuffy

The "Object" tab on the diagram properties dialogue (RA+?) is for setting default values for new objects to be created, whereas the Object properties dialogue (RA+I) is for changing the currently selected objects.
Try this:Start with a blank diagram. Open the diagram properties, change the fill colour on the object tab and hit apply. Now add a shape to the diagram. Is it filled in with the new colour? Now use the Object properties to change it to something different.
If this doesn't work, drop me an email.

@Jurassicc

and if you add and omit VTS_01_5.VOB:

dvd://1 -dvd-device a1ide.device:1

it reads from the dvd disk

BYE